[asterisk-bugs] [JIRA] (ASTERISK-26656) PJSIP fails to handle NAT clients on multihomed boxes

[Private Name (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Private Name updated ASTERISK-26656:
------------------------------------

    Attachment: pjsip-config.txt

The box has two IPs, on the same network. Everything works if I send a call to eth0, then RTP is sent to the public IP of the client. If I send the call to eth1, the second IP, then PJSIP sends back media to the private IP of the client.

> PJSIP fails to handle NAT clients on multihomed boxes
> -----------------------------------------------------
>
>                 Key: ASTERISK-26656
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26656
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_multihomed
>    Affects Versions: 13.12.2
>         Environment: Linux 64
>            Reporter: Private Name
>         Attachments: pjsip-config.txt
>
>
> In PJSIP, we have these 3 settings for an endpoint located behind a NAT
>     rtp_symmetric - Send media to the address and port from which Asterisk receives it, regardless of where SDP indicates that it should be sent
>     force_rport - Send responses to the source IP address and port as though port were present, even if it's not
>     rewrite_contact - Rewrite SIP Contact to the source address and port of the request so that subsequent requests go to that address and port.
> If the machine has one interface, PJSIP correctly determines the public IP of the client, rewrites the contact and sends RTP back to the public IP. If the machine has more than one network interface, on the same network (my case), then PJSIP gets confused and send the RTP to the private IP, this the client never gets the media.
> All this can be seen with 
> rtp set debug on
> This issue has the tragic consequence of not allowing for any load balancing, since we can effectively have on single network interface.



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