[Home]

Summary:ASTERISK-28910: PJSIP: invalid value error exception when parsing 'Contact' header
Reporter:Alan (black0fire7)Labels:
Date Opened:2020-05-21 08:00:29Date Closed:2020-05-21 08:11:35
Priority:MinorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:16.9.0 Frequency of
Occurrence		Constant
Related
Issues:
is related toASTERISK-28899 Upgrade Asterisk to bundled pjproject 2.10
Environment:OpenBSD 6.7Attachments:
Description:by incoming calls, PJSIP complains about the "expires=" value. although its valid in the RFC.

[May 21 13:58:33] ERROR[504612]: pjproject: <?>:               sip_transport.c Error processing 950 bytes packet from UDP xxx.xxx.xxx.xxx:5060 : PJSIP invalid value error exception when parsing 'Contact' header on line 3 col -1:
INVITE sip:XXXXXXXXXX@xxx.xxx.xxx.xxx:5060;transport=udp SIP/2.0
Call-ID: 12529-ON-10f20f6d-289749396@HOST.DOMAIN.de
Contact: <sip:xxx.xxx.xxx.xxx:5060>;expires=4294967295
Content-Type: application/sdp
CSeq: 276069520 INVITE
From: "XXXXXXXX" <sip:XXXXXXXXX@HOST.DOMAIN.de;user=phone>;tag=12529-YY-10f20f6e-723df48f0
Max-Forwards: 28
Record-Route: <sip:xxx.xxx.xxx.xxx:5060;lr>;session=343167
To: <sip:XXXXXXXXXX@xxx.xxx.xxx.xxx:5060;user=phone>
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK-ECBQ-6a2c050d-545126f1
Allow: UPDATE,INFO,REFER,INVITE,ACK,BYE,CANCEL
P-Preferred-Identity: <sip:XXXXXXXX@@HOST.DOMAIN.de;user=phone>
User-Agent: wtnet/ngn (2)
Content-Length: 249
Comments:By: Asterisk Team (asteriskteam) 2020-05-21 08:00:30.653-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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Joshua C. Colp (jcolp) 2020-05-21 08:04:12.976-0500

From RFC 3261:

     expires: The "expires" parameter indicates how long the UA would
          like the binding to be valid.  The value is a number
          indicating seconds.  If this parameter is not provided, the
          value of the Expires header field is used instead.
          Implementations MAY treat values larger than 2**32-1
          (4294967295 seconds or 136 years) as equivalent to 2**32-1.
          Malformed values SHOULD be treated as equivalent to 3600.
By: Joshua C. Colp (jcolp) 2020-05-21 08:09:10.401-0500

Looking at things deeper this was actually fixed by PJSIP in the latest version, 2.10. We are currently working to update Asterisk bundled to this new version after which this will be resolved. I'd suggest following ASTERISK-28899 to see when that change is complete, and then to follow it for when the next releases are made including it.
By: Joshua C. Colp (jcolp) 2020-05-21 08:09:51.547-0500

Closing this out per my last comment.
By: Alan (black0fire7) 2020-05-21 08:11:19.395-0500

Thank you so much for your quick response and support!!
By: Asterisk Team (asteriskteam) 2020-05-21 08:11:19.720-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.