[asterisk-bugs] [JIRA] (ASTERISK-29235) Contact Header Rewrite is set to NO, not taking effect
Brian Paboojian (JIRA)
noreply at issues.asterisk.org
Wed Jan 6 17:15:16 CST 2021
[ https://issues.asterisk.org/jira/browse/ASTERISK-29235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Paboojian updated ASTERISK-29235:
---------------------------------------
Attachment: eth1-NAT.pcap
eth1-EM.pcap
I have attached 2 pcaps from the WAN side of the “eSBC” (Edgemarc 2900E) and a simple “NAT” device (Mikrotik).
Asterisk IP: 192.168.60.239
SIP phone behind the eSBC:192.168.1.151
SIP phone behind the NAT: 192.168.6.253
eSBC WAN IP: 192.168.60.228
NAT WAN IP: 192.168.60.102
eSBC file name: eth1-EM.pcap
shows 192.168.60.228 to 192.168.60.239 contact header as sip:1000 at 192.168.60.228:5060;transport=udp
The return 200 OK contact header is sip:1000 at 192.168.60.239:5060;transport=udp
NAT pcap file name eth1-NAT.pcap
shows 192.168.60.102 to 192.168.60.239 contact header as sip:1000 at 192.168.60.102:5060;transport=udp
The return 200 OK contact header is sip:1000 at 192.168.60.239:5060;transport=udp
According to the Ribbon support engineer this is a violation of the RFC 3261. When not using the SD-wan the eSBC just passes the information. But when using SD-Wan all traffic must go through the B2BUA and that logic causes the registration to drop because the contact header is being rewritten on the way back.
I have verified this in both Asterisk 16 and 13.
> Contact Header Rewrite is set to NO, not taking effect
> ------------------------------------------------------
>
> Key: ASTERISK-29235
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-29235
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip_nat, Resources/res_pjsip_registrar
> Affects Versions: 13.36.0, 16.13.0
> Environment: Freepbx 15 distro
> Reporter: Brian Paboojian
> Assignee: Brian Paboojian
> Severity: Minor
> Attachments: eth1-EM.pcap, eth1-NAT.pcap
>
>
> I am testing SD-Wan with my Ribbon Edgemarc. The phone is sending the registration to the eSBC and then the SBC forwards the registration onto the Freepbx 15 system. Asterisk is rewriting the contact header when it sends the registration back to the phone and the Edgemarc is blocking it because this rewrite is a violation of RFC 3261. I have turned off contact rewrite in extension advanced settings. In reviewing the pcap reveal the contact header is still being rewritten.
> I have confirmed this setting in the config file Pjsip.endpoint.conf;
> rewrite_contact=no
> I worked with a Freepbx Engineer and he agrees this is an Asterisk bug.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list