[asterisk-bugs] [Asterisk 0018331]: ODBC Disconnection if call not briged

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Apr 6 21:06:03 CDT 2011


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18331 
====================================================================== 
Reported By:                apsaras
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18331
Category:                   PBX/pbx_realtime
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.37 
JIRA:                       SWP-2629 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-11-18 09:16 CST
Last Modified:              2011-04-06 21:06 CDT
====================================================================== 
Summary:                    ODBC Disconnection if call not briged
Description: 
We have several versions of Asterisk installed working with realtime via
ODBC on PostgreSQL Database.

We found out that if a call hungup during IVR (before call is briged) we
get DB Errors, Disconnection and Reconnection.
====================================================================== 

---------------------------------------------------------------------- 
 (0133486) lmadsen (administrator) - 2011-04-06 21:06
 https://issues.asterisk.org/view.php?id=18331#c133486 
---------------------------------------------------------------------- 
Closing this per a comment from Tilghman on IRC:

<Corydon76-home> Probably someone put in an extended ASCII character,
which conflicts with how the database expects to receive characters. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-06 21:06 lmadsen        Note Added: 0133486                          
2011-04-06 21:06 lmadsen        Status                   feedback => closed  
2011-04-06 21:06 lmadsen        Resolution               open => no change
required
======================================================================




More information about the asterisk-bugs mailing list