[asterisk-bugs] [JIRA] (ASTERISK-26851) res_pjsip_sdp_rtp: RTP instance does not use same IP as explicit transport

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-26851:
------------------------------------------------

Change 5199 merged by Joshua Colp:
res_pjsip_sdp_rtp: RTP instance does not use same IP as explicit transport

[https://gerrit.asterisk.org/5199|https://gerrit.asterisk.org/5199]

> res_pjsip_sdp_rtp: RTP instance does not use same IP as explicit transport
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-26851
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26851
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_sdp_rtp
>    Affects Versions: 13.14.0
>         Environment: Centos 7
>            Reporter: Richard Begg
>            Severity: Minor
>         Attachments: bind_rtp_to_transport.patch
>
>
> When establishing an RTP session, unless the endpoint has a defined media_address, pjsip will bind the local socket to a wildcard address.  This works fine where we can rely on the OS routing table to determine the correct interface, however it doesn't necessarily provide the correct behaviour in situations where there are multiple interfaces - especially if the host has multiple IP addresses on the same subnet (common in HA deployments).
> If the endpoint is bound to a transport which is then bound to a specific local IP address, I would expect that the RTP socket should follow the behaviour of the SIP socket and ensure that all traffic is sent/received from this address.  Unfortunately this is not what happens.
> Attached is a patch which attempts to fix this.  In short, in the absence of a media_address on the endpoint, and if the transport has a bound IP address - it will use this address for the local end of the RTP socket.
> Note: This issue is probably a duplicate of that logged in the closed ticket: ASTERISK-26656.



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