[Home]

Summary:ASTERISK-19466: NSGate 39xx series gateway will not register with pedantic=yes
Reporter:Eugene (varnav)Labels:
Date Opened:2012-03-02 10:20:49.000-0600Date Closed:2015-08-11 04:17:22
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:1.8.9.3 Frequency of
Occurrence
Constant
Related
Issues:
is related toASTERISK-19467 Error should always be logged if SIP message fails compliance check
Environment:Doesn't matterAttachments:
Description:Asterisk will ignore registration request from NSGate 39xx series gateways if pedantic=yes (that is default value since 1.8 b5) is set.
The example registration request that will never receive the reply:

REGISTER sip:192.168.0.211 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.19:5060;rport;branch=z9hG4bKu34ay0vs511tw077vo7x
From: <sip:5555@192.168.0.211>
To: <sip:5555@192.168.0.211>
Call-ID: 561n97f2o3z0a683151d-6@192.168.0.211
CSeq: 325 REGISTER
MAX-Forwards: 70
Contact: <sip:5555@192.168.0.19:5060>
Expires: 900
Content-Length: 0

Setting pedantic=no in sip.conf fixes the issue.
Comments:By: Walter Doekes (wdoekes) 2012-03-02 10:43:28.366-0600

You're missing a From-tag.
pedantic=yes likes the SIP to be valid.

By: Eugene (varnav) 2012-03-02 11:34:54.463-0600

Thanks to Walter Doekes who pointed out that NSGate violates RFC3261 8.1.1.3 not passing "tag" in "from" header.

But default value of "pedantic" set to "yes" is still questionable.

By: Eugene (varnav) 2015-08-11 04:17:22.743-0500

It's a bug of the hardware. Workaround is to turn off strict SIP checking.