[asterisk-bugs] [JIRA] (ASTERISK-24178) [patch]fromdomainport used even if not set

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Jul 27 10:30:20 CDT 2016


     [ https://issues.asterisk.org/jira/browse/ASTERISK-24178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-24178:
-------------------------------------

    Target Release Version/s: 14.0.0

> [patch]fromdomainport used even if not set
> ------------------------------------------
>
>                 Key: ASTERISK-24178
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24178
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: SVN
>            Reporter: Elazar Broad
>            Severity: Minor
>      Target Release: 1.8.31.0, 11.13.0, 12.6.0, 13.0.0-beta2, 14.0.0
>
>         Attachments: fromdomainport_fix.diff
>
>
> Long story short, we set fromdomainport to STANDARD_SIP_PORT if it is not set by the user in fromdomain(see http://doxygen.asterisk.org/trunk/df/df0/chan__sip_8c-source.html#l30599). The issue is, in two places, we do the following:
> int ourport = (p->fromdomainport) ? p->fromdomainport : ast_sockaddr_port(&p->ourip);
> Which means we will always use fromdomainport even if it wasn't actually set by the user. A side effect of this is when using SIP over TLS, an MWI response will always include port 5060 in the Message-Account field even though TLS uses 5061 (see http://doxygen.asterisk.org/trunk/df/df0/chan__sip_8c-source.html#l15086). 
> The attached patch resolves this issue. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list