[asterisk-bugs] [Asterisk 0007987]: ooh323 does not work in failover test case if the first destination is an empty/no route device

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=7987 
====================================================================== 
Reported By:                homesick
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   7987
Category:                   Addons/chan_ooh323
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 42765 
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             09-19-2006 16:00 CDT
Last Modified:              01-16-2008 12:05 CST
====================================================================== 
Summary:                    ooh323 does not work in failover test case if the
first destination is an empty/no route device
Description: 
In failover test case, if the first destination is an empty IP/no route
device, asterisk does failover to the second destination after dial
application is timeout. But ooh323 does not send any message to the second
destination for the second dial. After the second dailing is timeout, the
call handups, ooh323 does not send release complete to the source gateway.
====================================================================== 

---------------------------------------------------------------------- 
 russell - 01-16-08 12:05  
---------------------------------------------------------------------- 
This module has been unsupported for a long time.  Now, it is officially
marked as unsupported.  So, only bug reports with patches will be accepted
at this time. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-16-08 12:05  russell        Status                   new => resolved     
01-16-08 12:05  russell        Resolution               open => suspended   
01-16-08 12:05  russell        Assigned To               => russell         
01-16-08 12:05  russell        Note Added: 0080775                          
======================================================================