[Home]

Summary:ASTERISK-26033: PJSIP unable to register or qualify to IMS Trunk using outbound proxy
Reporter:Steve Akerman (stevenA)Labels:
Date Opened:2016-05-18 00:55:35Date Closed:2016-05-18 08:36:11
Priority:MajorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:13.8.2 13.9.0 13.9.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:RasPBXAttachments:( 0) Debug_Output_PJSIP.txt
( 1) PJSIP_Configuration.txt
Description:Asterisk using PJSIP fails to Register or qualify to an IMS system that uses outbound proxy and a non DNS searchable registrar.

It appears to ignore the outbound proxy, and to fail on a DNS lookup of the registrar, but keeps trying to send packets (DNS fail not seen when preparing the supports for this issue, but previously observed and attached at the end of debug output).

TCPDump shows nothing leaving the Asterisk server for the outbound proxy

Using PJSUA built with Asterisk (bundled Pjproject) and the config that is attached at the end of debug output, Registers are successful.

Comments:By: Asterisk Team (asteriskteam) 2016-05-18 00:55:35.790-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Steve Akerman (stevenA) 2016-05-18 00:57:50.447-0500

Running PJSIP configuratio
By: Steve Akerman (stevenA) 2016-05-18 01:10:52.615-0500

PJSUA config file included at end
By: Joshua C. Colp (jcolp) 2016-05-18 05:11:49.762-0500

Your outbound proxy does not appear to be configured correctly. What does the actual file contain? If "sip:" is not at the front of it then it is an invalid SIP URI, as "sip:" needs to be there.
By: Steve Akerman (stevenA) 2016-05-18 07:57:07.448-0500

I have prefixed the proxy with SIP:, and it now shows correctly in all of the show SIPS.

More importantly, it is now on the wire......

However, the Register address is to the proxy, and not to the registrar, so there are no replies

{noformat}
REGISTER sip:internet.p-cscf.sfr.net:5064 SIP/2.0
Via: SIP/2.0/UDP MYPUBLICIP:5060;rport;branch=z9hG4bKPjbc705e14-725a-44e6-ba83-8f61aecbb151
From: <sip:+3399XXXXXXXXXX@ims.mnc010.mcc208.3gppnetwork.org>;tag=22eabb1c-63e0-45ec-b01d-7a5666ed3533
To: <sip:+3399XXXXXXXXXX@ims.mnc010.mcc208.3gppnetwork.org>
Call-ID: 486cb3ab-1a32-49f4-8e6a-0c9db67f3336
CSeq: 43529 REGISTER
Contact: <sip:+3399XXXXXXXXXX@MYPUBLICIP:5060>
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REGISTER, REFER
Route: <sip:+3399XXXXXXXXXX@ims.mnc010.mcc208.3gppnetwork.org>
Max-Forwards: 70
User-Agent: FPBX-13.0.119(13.9.1)
Content-Length:  0

{noformat}
By: Joshua C. Colp (jcolp) 2016-05-18 08:00:52.951-0500

Add \;lr to the end of the URI. Example:

sip:test.sip.com\;lr

That will enable loose routing.
By: Steve Akerman (stevenA) 2016-05-18 08:16:33.860-0500

OK Asterisk is now registered! Thanks.

I had the ;lr in before, but without the SIP: it was ignored.

Now the issue remains the Qualify (AOR section has correct proxy but is otherwise same as submitted)

{noformat}[2016-05-18 15:08:40] ERROR[4401]: res_pjsip.c:2946 create_out_of_dialog_request: Unable to create outbound OPTIONS request to endpoint SFR_Lys_PJ
[2016-05-18 15:08:40] ERROR[4401]: res_pjsip/pjsip_options.c:350 qualify_contact: Unable to create request to qualify contact sip:+3399XXXXXXXXXX@ims.mnc010.mcc208.3gppnetwork.org
{no format}

By: Joshua C. Colp (jcolp) 2016-05-18 08:26:05.763-0500

I'm closing this out since the original reported issue was configuration related. For OPTIONS I'd suggest using the community resources such as the community site[1] to debug further before considering it an issue. You may also want to watch ASTERISK-26026 as they too are having a problem with OPTIONS.

[1] https://community.asterisk.org/
By: Steve Akerman (stevenA) 2016-05-18 08:27:55.765-0500

And more importantly, Asterisk crashes if I try to use the trunk. How can I enable the backtrace to give you details (there is nothing in the logs even with debug and verbose set at 4)
By: Asterisk Team (asteriskteam) 2016-05-18 08:27:55.939-0500

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.
By: Joshua C. Colp (jcolp) 2016-05-18 08:36:04.439-0500

Instructions for getting a backtrace are on the wiki[1]. I'd suggest opening a new issue instead of morphing this one into something else.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace