[asterisk-bugs] [Asterisk 0012700]: Zaptel channel detects hangup, but does not hangup bridged SIP channel

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12700 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12700
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta8 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-21-2008 11:13 CDT
Last Modified:              06-01-2008 04:53 CDT
====================================================================== 
Summary:                    Zaptel channel detects hangup, but does not hangup
bridged SIP channel
Description: 
Having an odd issue with Asterisk-1.6-beta9.

Zaptel <-> Asterisk <-> SIP

We place a call into Zaptel card, Asterisk rings SIP channel, call
connects.  We hangup from Zaptel side, Asterisk detects hangup, drops
zaptel, but SIP channel is still active.  Not until the call is
disconnected from SIP side, does the asterisk detect the hangup.
====================================================================== 

---------------------------------------------------------------------- 
 rjain - 06-01-08 04:53  
---------------------------------------------------------------------- 
Wondering if this could be due to the 'maddr' parameter presented in the
Contact header in the 200 OK:

CONTACT:
<sip:sv0071iv.internal.xxx:5070;transport=Tcp;maddr=10.0.3.71>;automata

You may want to try disabling maddr if possible, or running a scenario
where maddr is used in conjunction w/ UDP. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-01-08 04:53  rjain          Note Added: 0087604                          
======================================================================