[asterisk-bugs] [JIRA] (ASTERISK-19467) Error should always be logged if SIP message fails compliance check

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203505#comment-203505 ] 

Matt Jordan commented on ASTERISK-19467:
----------------------------------------

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.
                
> Error should always be logged if SIP message fails compliance check
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-19467
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19467
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.9.3
>            Reporter: Eugene
>            Severity: Minor
>
> 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
> From: <sip:5555 at 192.168.0.211>
> To: <sip:5555 at 192.168.0.211>
> Call-ID: 561n97f2o3z0a683151d-6 at 192.168.0.211
> CSeq: 325 REGISTER
> MAX-Forwards: 70
> Contact: <sip:5555 at 192.168.0.19:5060>
> Expires: 900
> Content-Length: 0
> There is no "tag" in "From" header. Asterisk will silently ignore this registration request. Correct behavior would be to output an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira