[asterisk-bugs] [JIRA] (ASTERISK-29235) res_pjsip_nat: Contact is rewritten on REGISTER responses with external_signaling_address

Friendly Automation (JIRA) noreply at issues.asterisk.org
Thu Aug 12 10:22:34 CDT 2021


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

Friendly Automation commented on ASTERISK-29235:
------------------------------------------------

Change 16279 merged by Friendly Automation:
res_pjsip_nat: Don't rewrite Contact on REGISTER responses.

[https://gerrit.asterisk.org/c/asterisk/+/16279|https://gerrit.asterisk.org/c/asterisk/+/16279]

> res_pjsip_nat: Contact is rewritten on REGISTER responses with external_signaling_address
> -----------------------------------------------------------------------------------------
>
>                 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: Joshua C. Colp
>              Labels: fax, webrtc
>      Target Release: 16.17.0, 18.3.0
>
>         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