[asterisk-bugs] [Asterisk 0006335]: [patch] Realtime call control
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Sep 17 19:28:41 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=6335
======================================================================
Reported By: KNK
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 6335
Category: Applications/app_dial
Reproducibility: N/A
Severity: feature
Priority: normal
Status: assigned
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 56340
Disclaimer on File?: No
Request Review:
======================================================================
Date Submitted: 01-24-2006 02:45 CST
Last Modified: 09-17-2007 19:28 CDT
======================================================================
Summary: [patch] Realtime call control
Description:
Adds new variables to the L option of Dial application to recheck the call
limit during the call.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0007531 [patch] call not terminated after timel...
======================================================================
----------------------------------------------------------------------
greyvoip - 09-17-07 19:28
----------------------------------------------------------------------
Sorry my mistake I should have said extra thread not extra channel. It was
a couple of months ago I tested the patch. I've checked my notes as well
and one other minor thing I came across was that since the AGI app was
executing on the same channel I used to get the occassional channel lock
error messages flash up on the console. I believe this was being caused
because of a lock that pbx_exec uses conflicting with the bridge activity.
I did not ever have a situation where the call duration did not get updated
properly I was jsut a bit nervous that maybe an audio frame did not get
bridged because a lock was missed (or maybe I just didn't grasp what was
going on well enough).
Issue History
Date Modified Username Field Change
======================================================================
09-17-07 19:28 greyvoip Note Added: 0070710
======================================================================
More information about the asterisk-bugs
mailing list