[asterisk-bugs] [JIRA] (ASTERISK-28876) Wrong next hop for INVITEs with PJSIP and PATH

Thu May 7 11:01:25 CDT 2020

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

Serge edited comment on ASTERISK-28876 at 5/7/20 11:00 AM:
-----------------------------------------------------------

The OPTIONS (asterisk qualifies) have the right Route header and are sent to the right next hop (edge proxy):

U 2020/05/07 11:49:06.242868 PBXIP:5060 -> PROXYIP:5060
OPTIONS sip:777 at 192.168.2.100:56859;rinstance=0ea0111d4d7fe2b9 SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;rport;branch=z9hG4bKPj7964a211-2840-4ec5-a4b4-b7818d329727
From: <sip:777 at PBXIP>;tag=e129bd14-9bf1-4532-a7c5-a9ee5f7fae97
To: <sip:777 at 192.168.2.100;rinstance=0ea0111d4d7fe2b9>
Contact: <sip:777 at PBXIP:5060>
Call-ID: c4f41755-4394-48fb-9e6b-26f3191331b3
CSeq: 19787 OPTIONS
Supported: path
Route: <sip:proxy.mydomain.net:5060;lr;received=sip:173.XX.XX.XX:56859;r2=on>
Route: <sip:proxy.mydomain.net;lr;received=sip:173.XX.XX.XX:56859;r2=on>
Max-Forwards: 70.
User-Agent: Asterisk
Content-Length:  0

The INVITE is sent incorrectly to the Contact URI directly, no Route header present:

U 2020/05/07 11:54:36.139189 PBXIP:5060 -> 192.168.2.100:56859
INVITE sip:777 at 192.168.2.100:56859;rinstance=0ea0111d4d7fe2b9 SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;rport;branch=z9hG4bKPj95dc5492-818d-484d-bde3-e44815fda513
From: "MYID" <sip:3051111111 at PBXIP>;tag=516f16a6-a417-4ea5-8592-46978dfd0372
To: <sip:777 at 192.168.2.100;rinstance=0ea0111d4d7fe2b9>
Contact: <sip:asterisk at PBXIP:5060>
Call-ID: 20e29359-4b51-46bf-9f34-86337773f0a1
CSeq: 20715 INVITE
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, REFER, MESSAGE
Supported: 100rel, timer, replaces, norefersub, path
Session-Expires: 1800
Min-SE: 90
Max-Forwards: 70
User-Agent: Asterisk
Content-Type: application/sdp
Content-Length:   417

was (Author: zeusca):
The OPTIONS (asterisk qualifies) have the right Route header and are sent to the right next hop (edge proxy):

U 2020/05/07 11:49:06.242868 PBXIP:5060 -> PROXYIP:5060
OPTIONS sip:777 at 192.168.2.100:56859;rinstance=0ea0111d4d7fe2b9 SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;rport;branch=z9hG4bKPj7964a211-2840-4ec5-a4b4-b7818d329727
From: <sip:777 at PBXIP>;tag=e129bd14-9bf1-4532-a7c5-a9ee5f7fae97
To: <sip:777 at 192.168.2.100;rinstance=0ea0111d4d7fe2b9>
Contact: <sip:777 at PBXIP:5060>
Call-ID: c4f41755-4394-48fb-9e6b-26f3191331b3
CSeq: 19787 OPTIONS
Supported: path
Route: <sip:proxy.mydomain.net:5060;lr;received=sip:173.246.28.83:56859;r2=on>
Route: <sip:proxy.mydomain.net;lr;received=sip:173.XX.XX.XX:56859;r2=on>
Max-Forwards: 70.
User-Agent: Asterisk
Content-Length:  0

The INVITE is sent incorrectly to the Contact URI directly, no Route header present:

U 2020/05/07 11:54:36.139189 PBXIP:5060 -> 192.168.2.100:56859
INVITE sip:777 at 192.168.2.100:56859;rinstance=0ea0111d4d7fe2b9 SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;rport;branch=z9hG4bKPj95dc5492-818d-484d-bde3-e44815fda513
From: "MYID" <sip:3051111111 at PBXIP>;tag=516f16a6-a417-4ea5-8592-46978dfd0372
To: <sip:777 at 192.168.2.100;rinstance=0ea0111d4d7fe2b9>
Contact: <sip:asterisk at PBXIP:5060>
Call-ID: 20e29359-4b51-46bf-9f34-86337773f0a1
CSeq: 20715 INVITE
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, REFER, MESSAGE
Supported: 100rel, timer, replaces, norefersub, path
Session-Expires: 1800
Min-SE: 90
Max-Forwards: 70
User-Agent: Asterisk
Content-Type: application/sdp
Content-Length:   417

> Wrong next hop for INVITEs with PJSIP and PATH
> ----------------------------------------------
>
>                 Key: ASTERISK-28876
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28876
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.18.3
>         Environment: Linux 2.6.32-39-pve x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Serge
>            Severity: Minor
>
> When endpoints register via an edge proxy in front of Asterisk running PJSIP, the edge proxy adds a PATH header (https://www.rfc-editor.org/rfc/rfc3327.txt) so that Asterisk knows how to route out-of-dialog requests back to the proxy.
> When calling that endpoint, it appears though that INVITEs are sent to the Contact URI directly instead of being sent to the proxy with a preset Route header. Strangely, this happens only to INVITEs. Other requests such as the OPTIONS qualify initiated by Asterisk are sent correctly to the proxy with the proper Route header.
> When using chan_sip this problem does not occur.
> Asterisk certified/13.18-cert3
> PJ_VERSION : 2.7.2
> AOR/support_path : true
> Endpoint/rewrite_contact : false
> Endpoint/force_rport : false

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