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

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-24615:
----------------------------------------

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Please make sure 'pjsip set logger on' is enabled.

Also provide your pjsip.conf that reproduces this problem.

Note that all of this information is in the issue reporting guidelines [1]. Please follow those instructions when filing an issue.

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> 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
>    Affects Versions: 13.0.1
>            Reporter: David Justl
>
> 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)