|Summary:||ASTERISK-19467: Error should always be logged if SIP message fails compliance check|
|Date Opened:||2012-03-02 12:03:42.000-0600||Date Closed:|
|Versions:||188.8.131.52 13.18.4||Frequency of|
|Description:||Since 1.8 b5 default value for "pedantic" variable in sip.conf is set to "yes". This turns on comprehensive check of SIP headers and causes many incompatibilities with user agents that do not follow RFCs strictly enough. Current behavior is not to report any error upon receipt of SIP REGISTER message that fails validation. This causes much trouble while diagnosing incompatibilities. Asterisk should always report an error if it catches SIP message that fails validation of "pedantic" check.|
Try sending this to Asterisk:
REGISTER sip:192.168.0.211 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.19:5060;rport;branch=z9hG4bKu34ay0vs511tw077vo7x
CSeq: 325 REGISTER
There is no "tag" in "From" header. Asterisk will silently ignore this registration request. Correct behavior would be to output an error.
|Comments:||By: Eugene (varnav) 2012-03-06 01:31:03.637-0600|
Maybe it worth setting default value of "pedantic" back to no? Setting it to yes slows down processing and introduces incompatibilities.
By: Eugene (varnav) 2013-02-27 09:01:27.303-0600
Hello! Any news about this one?
By: Matt Jordan (mjordan) 2013-02-27 09:13:31.297-0600
Your issue is in queue, please be patient, and we will get to it as time permits and developer resources become available.
Please note that a patch that adds the desired logging message would help speed up this issue.