[asterisk-bugs] [Asterisk 0011467]: [patch] h extension not executing, zap channel getting stuck
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Dec 6 22:26:09 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11467
======================================================================
Reported By: jmls
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11467
Category: Core/Channels
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 90876
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 12-04-2007 15:51 CST
Last Modified: 12-06-2007 22:26 CST
======================================================================
Summary: [patch] h extension not executing, zap channel
getting stuck
Description:
If either func_curl or func_odbc is executed, and during the time it takes
to execute the function the caller hangs up, then the h extension is not
executed, and the zap channel the call came in on gets "stuck"
======================================================================
----------------------------------------------------------------------
blitzrage - 12-06-07 22:26
----------------------------------------------------------------------
In the case of ODBC, I want the process to finish for sure if I'm doing an
insert or an update. In the case of a select I probably don't care that
much... but to be safe, I'd say let the process finish with something like
rtptimeout where you will kill something if it doesn't return within a
period of time.
Is that possible?
Issue History
Date Modified Username Field Change
======================================================================
12-06-07 22:26 blitzrage Note Added: 0074999
======================================================================
More information about the asterisk-bugs
mailing list