[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=228932#comment-228932 ] 

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

It's been fixed with the addition of some new options to go in the endpoint. From what George has told me, I'd expect it in 13.8.0.
Or you can download the patch and apply it yourself.

Unfortunately, the patch will not make Asterisk automatically use the floating IP. 
It will allow you to make Asterisk bind to the floating IP using media_address=YOUR_FLOATING_IP and bind_rtp_to_media_address=yes in the endpoint settings. You can have different floating IPs for each endpoint if required.

The side effect of this is that endpoints will not be able to move from a public external floating IP to a private internal floating IP. Might be problematic if you have users who connect to Asterisk from within the network and also from outside the network. In this case, I would fix things with routing.

> 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)