[asterisk-bugs] [JIRA] (ASTERISK-24615) When Multiple Transports Exist in pjsip.conf, Incorrect External Addresses is Used in SIP Packets When Responding to INVITE

[David Justl (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224408#comment-224408 ] 

David Justl commented on ASTERISK-24615:
----------------------------------------

After performing some additional testing, it appears this is affected by at least two factors:

1. If both transports are bound to different ports on the same IP address (Or to 0.0.0.0), the order they appear in pjsip.conf matters...the information in the transport that is listed second is used.

2. If each transport is bound to a different IP address, the lower address is used (e.g. 1.1.1.1 vs. 1.1.1.2), regardless of the order they appear in pjsip.conf.

> When Multiple Transports Exist in pjsip.conf, Incorrect External Addresses is Used in SIP Packets When Responding to INVITE
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24615
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24615
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.0.1
>            Reporter: David Justl
>            Assignee: David Justl
>         Attachments: 121214.log, pjsip.conf.121214
>
>
> Say pjsip.conf is configured with two transports, one bound to port 5060 and one bound to port 5061, each with completely different external_signaling_address and external_media_address values. Then say each is mapped to a different VoIP provider's endpoint. When Asterisk receives an INVITE from the provider that is configured to use the transport bound to port 5061, it is using the external_signaling_address and external_media_address values from the transport bound to port 5060 in the Header Contact and in the Message Body Session Description Protocol portions of the OK response. There is nothing in pjsip.conf tying the given endpoint to the port 5060 transport. This causes the provider to send RTP and other signaling packets to the wrong IP.



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