[asterisk-bugs] [Asterisk 0013770]: Asteris never responce ACK for 487 Request Terminated

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13770 
====================================================================== 
Reported By:                Sahria Hao
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13770
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-23 06:34 CDT
Last Modified:              2008-10-27 19:46 CDT
====================================================================== 
Summary:                    Asteris never responce ACK for 487 Request
Terminated
Description: 
When Asteris received 487 Request Terminated,
but Asterisk never responce ACK.

[Oct 23 20:23:25] DEBUG[29206]: chan_sip.c:16243 sipsock_read: Invalid SIP
message - rejected , no callid, len 364

Attached console debug with:

core set debug 15
core set verbose 15
sip debug
====================================================================== 

---------------------------------------------------------------------- 
 (0094322) blitzrage (administrator) - 2008-10-27 19:46
 http://bugs.digium.com/view.php?id=13770#c94322 
---------------------------------------------------------------------- 
I don't see where in your dialog where the 487 Request Terminated actually
happens...

Also, can you please attach this as a file, rather than as a paste into
the bug? It makes working with the bug extremely difficult. For now I will
leave what you have, but I'd prefer actually a PCAP capture (i.e. wireshark
or tcpdump) so that it is easier to look at the trace.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-27 19:46 blitzrage      Note Added: 0094322                          
======================================================================