[Home]

Summary:ASTERISK-28509: PJSIP cnonce generated on Linux contains 36 characters, NEC only supports up to 32 characters
Reporter:Dan Cropp (daninmadison)Labels:pjsip
Date Opened:2019-08-20 16:11:01Date Closed:2019-08-22 19:52:37
Priority:MinorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:16.5.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Ubuntu (I believe PJSIP does this for most and possibly all Linux OS).Attachments:
Description:We worked with NEC support to determine SIP Station interface configured with authenticated registration only supports a cnonce of up to 32 characters.  

PJSIP in a Linux environment generates a uuid which is 36 characters (containing hyphens).  We worked with Teluu and they developed a patch for us solve the problem.
Comments:By: Asterisk Team (asteriskteam) 2019-08-20 16:11:01.742-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: Dan Cropp (daninmadison) 2019-08-20 16:27:06.081-0500

I would like to be assigned this issue because we have the patch Teluu developed for us.  

I have run tests with Teluu's patch in our development environment to an NEC switch setup by NEC support staff.  We confirmed Teluu's patch solved the problem.
Teluu's solution was to add a compile time setting to remove hyphens from the cnonce they generate.  They decided to make it remove hyphens by default (which actually matches they behavior on other operating systems).

By: Friendly Automation (friendly-automation) 2019-08-22 19:52:38.245-0500

Change 12772 merged by Friendly Automation:
pjproject: Configurable setting for cnonce to include hyphens or not

[https://gerrit.asterisk.org/c/asterisk/+/12772|https://gerrit.asterisk.org/c/asterisk/+/12772]

By: Friendly Automation (friendly-automation) 2019-08-22 19:57:45.473-0500

Change 12764 merged by Friendly Automation:
pjproject: Configurable setting for cnonce to include hyphens or not

[https://gerrit.asterisk.org/c/asterisk/+/12764|https://gerrit.asterisk.org/c/asterisk/+/12764]

By: Friendly Automation (friendly-automation) 2019-08-22 19:59:46.280-0500

Change 12763 merged by Friendly Automation:
pjproject: Configurable setting for cnonce to include hyphens or not

[https://gerrit.asterisk.org/c/asterisk/+/12763|https://gerrit.asterisk.org/c/asterisk/+/12763]

By: Friendly Automation (friendly-automation) 2019-08-23 06:58:12.348-0500

Change 12765 merged by Joshua Colp:
pjproject: Configurable setting for cnonce to include hyphens or not

[https://gerrit.asterisk.org/c/asterisk/+/12765|https://gerrit.asterisk.org/c/asterisk/+/12765]

By: Friendly Automation (friendly-automation) 2019-08-23 06:58:31.650-0500

Change 12773 merged by Joshua Colp:
pjproject: Configurable setting for cnonce to include hyphens or not

[https://gerrit.asterisk.org/c/asterisk/+/12773|https://gerrit.asterisk.org/c/asterisk/+/12773]