[asterisk-bugs] [JIRA] (ASTERISK-22946) Local From tag regression with sipgate.de

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-22946:
----------------------------------------

It looks like sipgate.de is doing the "right thing" here, as it is replying back to each REGISTER request with the same from tag we sent to it with successful responses. It adds a To tag in the 200 OK, which is fine:

{quote}
8.2.6.2 Headers and Tags

   The From field of the response MUST equal the From header field of
   the request.  The Call-ID header field of the response MUST equal the
   Call-ID header field of the request.  The CSeq header field of the
   response MUST equal the CSeq field of the request.  The Via header
   field values in the response MUST equal the Via header field values
   in the request and MUST maintain the same ordering.

   If a request contained a To tag in the request, the To header field
   in the response MUST equal that of the request.  However, if the To
   header field in the request did not contain a tag, the URI in the To
   header field in the response MUST equal the URI in the To header
   field; additionally, the UAS MUST add a tag to the To header field in
   the response (with the exception of the 100 (Trying) response, in
   which a tag MAY be present).  This serves to identify the UAS that is
   responding, possibly resulting in a component of a dialog ID.  The
   same tag MUST be used for all responses to that request, both final
   and provisional (again excepting the 100 (Trying)).  Procedures for
   the generation of tags are defined in Section 19.3.
{quote}


                
> Local From tag regression with sipgate.de
> -----------------------------------------
>
>                 Key: ASTERISK-22946
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22946
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: SVN
>         Environment: Ubuntu 12.04 x64; sipgate.de basic
>            Reporter: Stephan Eisvogel
>            Assignee: Stephan Eisvogel
>            Severity: Critical
>         Attachments: ast11-crypto-override.patch, sipgate.pcap
>
>
> Commit r402605 (chan_sip: keep same local (from) tag for outgoing register requests) causes registration with German sipgate.de to fail with these errors on console:
> [Dec  7 21:10:12] NOTICE[11773]: chan_sip.c:15135 sip_reg_timeout:    -- Registration for 'xxxxxxx at sipgate.de' timed out, trying again (Attempt #2)
> [Dec  7 21:10:18] WARNING[11773]: chan_sip.c:4176 retrans_pkt: Retransmission timeout reached on transmission 30152ad126372ebf6305891d1c567c01 at sipgate.de for seqno 105 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
> Packet timed out after 6400ms with no response
> [Dec  7 21:10:32] NOTICE[11773]: chan_sip.c:15135 sip_reg_timeout:    -- Registration for 'xxxxxxx at sipgate.de' timed out, trying again (Attempt #3)
> [Dec  7 21:10:38] WARNING[11773]: chan_sip.c:4176 retrans_pkt: Retransmission timeout reached on transmission 30152ad126372ebf6305891d1c567c01 at sipgate.de for seqno 106 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
> Packet timed out after 6400ms with no response
> Reverting commit takes Asterisk-11 SVN back to tranquility.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira