Paul Belanger
2008-Jun-11 13:38 UTC
[asterisk-users] decrease the time it takes for asterisk (fxsks) to answer
Morning list, Was curious if it is possible to decrease the time asterisk takes to answer an incoming call to a zaptel interface. Example: [Jun 11 09:33:06] VERBOSE[4489] logger.c: -- Starting simple switch on 'Zap/2-1' [Jun 11 09:33:10] NOTICE[4489] chan_zap.c: Got event 18 (Ring Begin)... [Jun 11 09:33:12] NOTICE[4489] chan_zap.c: Got event 2 (Ring/Answered)... [Jun 11 09:33:12] VERBOSE[4489] logger.c: -- Executing [s at from-zap:1] Dial("Zap/2-1", "SIP/sv0071iv") in new stack Asterisk first sees the incoming call at 09:33:06, but +4 seconds later it detects the ring, then +2 more seconds it answers and execute our extensions.conf programming.
Paul Belanger
2008-Jun-11 14:03 UTC
[asterisk-users] decrease the time it takes for asterisk (fxsks) to answer
Here is our zapata.conf: --- [channels] language=en context=from-zap usecallerid=yes busydetect=yes busypattern=500,500 busycount=3 callprogress=yes progzone=us signalling = auto group = 1 channel => 1-24 group = 2 channel => 25-48 --- Thought immediate=yes might fix the problem, but seems to have no affect. Below is its description. --- ; ; Specify whether the channel should be answered immediately or if the simple ; switch should provide dialtone, read digits, etc. ; Note: If immediate=yes the dialplan execution will always start at extension ; 's' priority 1 regardless of the dialed number! ; ;immediate=yes --- On Wed, Jun 11, 2008 at 9:38 AM, Paul Belanger <pabelanger at gmail.com> wrote:> Morning list, > > Was curious if it is possible to decrease the time asterisk takes to > answer an incoming call to a zaptel interface. > > Example: > > [Jun 11 09:33:06] VERBOSE[4489] logger.c: -- Starting simple > switch on 'Zap/2-1' > [Jun 11 09:33:10] NOTICE[4489] chan_zap.c: Got event 18 (Ring Begin)... > [Jun 11 09:33:12] NOTICE[4489] chan_zap.c: Got event 2 (Ring/Answered)... > [Jun 11 09:33:12] VERBOSE[4489] logger.c: -- Executing > [s at from-zap:1] Dial("Zap/2-1", "SIP/sv0071iv") in new stack > > Asterisk first sees the incoming call at 09:33:06, but +4 seconds > later it detects the ring, then +2 more seconds it answers and execute > our extensions.conf programming. > > From start to finish it take 6 seconds for asterisk to process an > incoming call... is there any way to shorten this time frame? > > Thanks, > PB >