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

[Serge (JIRA)]

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

Serge commented on ASTERISK-28876:
----------------------------------

PJSIP has a outbound_proxy parameter for AoRs. When I add it such as:
outbound_proxy=sip:proxy.somedomain.net;lr
my phone starts ringing, routing of INVITEs works!

However, Asterisk’s quality OPTIONS and other request methods now have two Route headers, one from the set outbound_proxy and the other from the PATH header.

Route: sip:proxy.somedomain.net;lr
Supported: path
Route: sip:proxy.somedomain.net;lr;received=sip:107.xx.xx.xx:59209

Why is it that with PJSIP an outbound_proxy needs to be set at all, considering that a PATH header has been added during Registration and according to RFC3327 (https://www.rfc-editor.org/rfc/rfc3327.txt) should be used for all type of requests when trying to communicate with the registered Contact?

Thanks.

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