On Thu, 2011-11-03 at 18:50 +0530, amit anand wrote:
Hi you can use Absoulte timeout to set the time limit feature for the channel
Hi,
Thanks for the suggestion. It's good to know that absolute timeout
exists (I'd not noticed that before). However, it won't help here
because we're setting up
Hi,
DAHDI and LIBPRI are the standard versions from the Asterisk web site.
The Asterisk server has a Sangoma E1 card in it and the line is regular
ISDN30.
Cheers,
Kingsley.
On Thu, 2011-11-03 at 08:14 -0500, Danny Nicholas wrote:
Please elaborate on your flavor of DAHDI and LIBPRI and what
Hi,
We're trying to time-limit some calls by specifying L(x:y:z) as an
option to the Dial command.
If we set the limit to a fairly short duration (eg 120 seconds) then
Asterisk seems to issue the hangup at about the right time.
However, for longish calls we're seeing quite a bit of overspill.
Please elaborate on your flavor of DAHDI and LIBPRI and what type of DAHDI
service you are using (PSTN, T1, etc). Speaking from a POTS line point of
view, there can easily be a 7-10 second delay in the processing of DAHDI
information (which would make your 1347 second call within tolerance).
On Thu, Nov 3, 2011 at 18:44, Danny Nicholas da...@debsinc.com wrote:
Please elaborate on your flavor of DAHDI and LIBPRI and what type of
DAHDI
service you are using (PSTN, T1, etc). Speaking from a POTS line point of
view, there can easily be a 7-10 second delay in the processing of DAHDI
If you dial to a Local/Context and use your time limits on that and then do
your dial to your DAHDI device inside that context does that have any
effect on the time limits working. We have used time limits with
Local/Context dials and had them work with out any known issues.
Thanks
Bryant
+1 Bryant - by using the Local/Context you are introducing some overhead to
the process, but eliminating the dependence on DAHDI timing (not that
there's anything wrong with that per se, but you can't control the Space
Shuttle with a Bearcat Scanner (or can you?) ).
From:
