[asterisk-bugs] [Asterisk 0010756]: NOTIFY contains invalid To header

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10756 
====================================================================== 
Reported By:                goestelecom
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10756
Category:                   Channels/chan_sip/Subscriptions
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 82835 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-18-2007 14:57 CDT
Last Modified:              10-11-2007 12:36 CDT
====================================================================== 
Summary:                    NOTIFY contains invalid To header
Description: 
In response to a SUBSCRIBE request the NOTIFY that is generated contains a
To header that starts: "To: <sip:sip:..."
====================================================================== 

---------------------------------------------------------------------- 
 ibercom - 10-11-07 12:36  
---------------------------------------------------------------------- 
This happens too on my production system on 1.4.11.
When Thomson ST2030 receive the wrong NOTIFY it reply:

<------------>
Reliably Transmitting (no NAT) to 172.xx.xx.xx:5060:
NOTIFY sip:20012 at 172.xx.xx.xx:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 172.ss.ss.ss:5060;branch=z9hG4bK008b7684;rport
From: "asterisk" <sip:asterisk at domain:5060>;tag=as0f1fe753
To: <sip:sip:20012 at 172.xx.xx.xx:5060;user=phone>;tag=c0a80101-2255
Contact: <sip:asterisk at 172.ss.ss.ss>
Call-ID: 446f-c0a80101-d-2 at 172.xx.xx.xx
CSeq: 121 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 87

Messages-Waiting: yes
Message-Account: sip:*99 at domain:5060
Voice-Message: 2/0 (0/0)

---
<--- SIP read from 172.xx.xx.xx:5060 --->
SIP/2.0 481 CallLeg/Transaction Does Not Exist
Via: SIP/2.0/UDP 172.ss.ss.ss:5060;branch=z9hG4bK008b7684;rport
From: "asterisk"<sip:asterisk at domain:5060>;tag=as0f1fe753
To: <sip:sip at 172.xx.xx.xx:5060;user=phone>;tag=c0a80101-2255
Call-ID: 446f-c0a80101-d-2 at 172.xx.xx.xx
CSeq: 121 NOTIFY
Content-Length: 0


<------------->

And Asterisk log:

[Oct 11 19:44:50] WARNING[21869] chan_sip.c: Remote host can't match
request NOTIFY to call '446f-c0a80101-d-2 at 172.19.11.226'. Giving up. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-11-07 12:36  ibercom        Note Added: 0071825                          
======================================================================