[asterisk-bugs] [Asterisk 0014838]: [patch] Asterisk cannot process calls if it cannot reach the voicemail database

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14838 
====================================================================== 
Reported By:                moliveras
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14838
Category:                   Applications/app_voicemail/ODBC
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-06 16:12 CDT
Last Modified:              2009-05-05 17:13 CDT
====================================================================== 
Summary:                    [patch] Asterisk cannot process calls if it cannot
reach the voicemail database
Description: 
I am using asterisk 1.4.24 built with ODBC voicemail. If network
connectivity is lost between asterisk and the voicemail database, asterisk
cannot process calls.  It seems that while asterisk is trying to establish
the tcp connection to the DB is it blocking. Can this be changed?
====================================================================== 

---------------------------------------------------------------------- 
 (0104278) tilghman (administrator) - 2009-05-05 17:13
 http://bugs.digium.com/view.php?id=14838#c104278 
---------------------------------------------------------------------- 
Unfortunately, I cannot even look at the 8.1.11 source, as it has been
removed from the PostgreSQL website and is no longer supported by them.  I
would recommend that you upgrade to the latest 8.1 release (8.1.17), if you
want to continue to use that series or upgrade to the latest 8.3 release
(8.3.7) otherwise.  It appears to be a bug in that version, which is likely
fixed in a later version, given that the backtrace given does not match
even 8.1.15 source. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-05 17:13 tilghman       Note Added: 0104278                          
======================================================================