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

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-24178:
------------------------------------

    Assignee: Elazar Broad
      Status: Waiting for Feedback  (was: Open)

[~ebroad] please go ahead and follow the [Code Review |https://wiki.asterisk.org/wiki/display/AST/Code+Review] process. You'll probably want to go ahead and get the patch up on Reviewboard as mentioned in the process. Remember to edit this issue and add the Reviewboard link in the appropriate field as well.

> [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
>            Assignee: Elazar Broad
>            Severity: Minor
>         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)