[Home]

Summary:ASTERISK-24949: res_pjsip_outbound_registration: Backport line functionality
Reporter:Joshua C. Colp (jcolp)Labels:
Date Opened:2015-04-09 08:05:18Date Closed:2015-05-05 13:15:36
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Resources/res_pjsip_outbound_registration
Versions:13.3.2 Frequency of
Occurrence
Related
Issues:
is related toASTERISK-24852 [patch] new res_pjsip module to identify endpoint for an incoming call with a trunk that has outbound registration.
Environment:Attachments:
Description:Line functionality was placed into trunk long ago. This functionality allows INVITEs received as a result of an outbound registration to be associated with an endpoint if the remote SIP server does not manipulate or strip information from the Contact URI. This is useful since it removes the requirement to do IP based matching on an ITSP, and also allows multiple outbound registrations to be individually identified.

This issue is for backporting of this functionality into 13. This requires a test to be created.
Comments:By: Dmitriy Serov (Demon) 2015-05-08 05:24:48.215-0500

Question:
Why was used "rdata->msg_info.to->uri", not "rdata->msg_info.msg->line.req.uri"?

My tests with different servers failed. The reason: option "line" is not added to "to" line.

cutted pjsip.conf:
[srv_d228]
type=registration
line=yes
endpoint=srv_d228

cutted SIP packet on inbound call:
INVITE sip:srv_d228@85.142.148.80:5070;line=uusollx SIP/2.0
Via: SIP/2.0/UDP 212.53.40.40:5060;branch=z9hG4bK514972-kmbdctn;cgp=etc.tario.ru;rport
From: "PhonerLite" <sip:demon_iv@sipnet.ru>;tag=AF8FA0BE-7476-5577F0E0_kmbdctn-44B1
To: <sip:talk37.ru@sipnet.ru>
Contact: <sip:signode-7476-5577F0E0_kmbdctn-44B1@212.53.40.40>

What I understood incorrectly? How do I make it work?

By: Joshua C. Colp (jcolp) 2015-05-08 05:29:48.864-0500

It depends on the underlying setup. Some setups will have a different request URI, not what you provided. An additional check for using the request URI could be added in addition to the To header. Create a new issue instead of overloading this one.

By: Dmitriy Serov (Demon) 2015-05-08 08:56:45.181-0500

Issue ASTERISK-25072 was created.
Thanks