[asterisk-bugs] [JIRA] (ASTERISK-25632) res_pjsip_sdp_rtp: RTP is sent from wrong IP address when multihomed

[Daniel Journo (JIRA)]

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

Daniel Journo commented on ASTERISK-25632:
------------------------------------------

Scenario:
Server with two NICs.
NIC1 configured with an internal static IP: 10.10.10.1
NIC1 also has a floating IP: 10.10.10.3
NIC2 configured with an external static IP: 212.123.123.1
NIC2 also has a floating IP: 212.123.123.3

Before the patch, you would connect an external endpoint to 212.123.123.3 but when you make calls, the RTP data comes out of 212.123.123.1 which is the primary IP for that NIC.
After the patch, if you don't make any config changes, the same issue will occur.

After the patch, add the following config to an endpoint 'media_address=212.123.123.3' and 'bind_rtp_to_media_address=yes', this will fix things so that RTP data comes out of the floating IP for data going to that endpoint.

However, take that endpoint and plug it into the internal network and point it to the internal private floating IP 10.10.10.3, the audio will still try to go out of 212.123.123.3 until you change 'media_address=212.123.123.3' to 'media_address=10.10.10.3'

Unfortunately, there doesn't appear to be a way around this apart from playing with routing on the system.

> res_pjsip_sdp_rtp: RTP is sent from wrong IP address when multihomed
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-25632
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25632
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_sdp_rtp
>    Affects Versions: 13.6.0
>         Environment: Centos 7
>            Reporter: Olivier Krief
>            Assignee: George Joseph
>
> Setup is a cluster of two Asterisk boxes. Each box has several Ethernet interfaces and both share a set of floating IP addresses (pacemaker/corosync).
> One box is volontarily powered off.
> The remaining box send an outbound call to a PJSIP trunk.
> Within SDP portion of INVITE message, I can read:
> IN IP4 10.20.143.100
> where 10.20.143.100 is a floating IP.
> The INVITE message itself also comes from 10.20.143.100
> A bit later, as captured with tcpcump, I can see outbound RTP is sent from 
> 10.20.143.101 (non-floating IP).
> Trunk's transport is configured with:
> external_media_address     : 10.20.143.100
> I must add I'm new to clusters.
> My question is:
> is this feature supported (use of floating IP addresses)
> Regards



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