John Covici
2008-Feb-25 22:38 UTC
[asterisk-users] cannot dial out with latest zaptel and kernel 2.6.24
Hi. I am using asterisk 1.4 (latest as of today) and zaptel 1.4 (latest as of today) and I cannot dial out using my 400P card with one fxs module and one fxo module. I am using kernel 2.6.24 and get the following log entries: [Feb 25 17:28:13] VERBOSE[25071] logger.c: -- Executing [s at macro-dialout-trunk:23] Dial("Zap/1-1", "ZAP/4/www411|300|wW") in new stack [Feb 25 17:28:13] DEBUG[25071] chan_zap.c: Dialing 'www411' [Feb 25 17:28:13] DEBUG[25071] chan_zap.c: Deferring dialing... [Feb 25 17:28:13] VERBOSE[25071] logger.c: -- Called 4/www411 [Feb 25 17:28:14] WARNING[25071] chan_zap.c: Detected alarm on channel 4: No Alarm [Feb 25 17:28:14] VERBOSE[25071] logger.c: -- Hungup 'Zap/4-1' [Feb 25 17:28:14] VERBOSE[25071] logger.c: == Everyone is busy/congested at this time (1:0/0/1) Any assistance on this would be appreciated. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici at ccs.covici.com
Shaun Ruffell
2008-Feb-25 23:01 UTC
[asterisk-users] cannot dial out with latest zaptel and kernel 2.6.24
Hi John, John Covici wrote:> Hi. I am using asterisk 1.4 (latest as of today) and zaptel 1.4 > (latest as of today) and I cannot dial out using my 400P card with one > fxs module and one fxo module. >It looks like you might be hitting a regression with DTMF tone generation in the latest zaptel releases. The running commentary on this issue is at: http://bugs.digium.com/view.php?id=11855 Could you try using zaptel version 1.4.7.1 and see if that helps? Shaun
Shaun Ruffell
2008-Feb-27 01:19 UTC
[asterisk-users] cannot dial out with latest zaptel and kernel 2.6.24
John Covici wrote:> Hi. I am using asterisk 1.4 (latest as of today) and zaptel 1.4 > (latest as of today) and I cannot dial out using my 400P card with one > fxs module and one fxo module. I am using kernel 2.6.24 and get the > following log entries: > [Feb 25 17:28:13] VERBOSE[25071] logger.c: -- Executing [s at macro-dialout-trunk:23] Dial("Zap/1-1", "ZAP/4/www411|300|wW") in new stack > [Feb 25 17:28:13] DEBUG[25071] chan_zap.c: Dialing 'www411' > [Feb 25 17:28:13] DEBUG[25071] chan_zap.c: Deferring dialing... > [Feb 25 17:28:13] VERBOSE[25071] logger.c: -- Called 4/www411 > [Feb 25 17:28:14] WARNING[25071] chan_zap.c: Detected alarm on channel 4: No Alarm > [Feb 25 17:28:14] VERBOSE[25071] logger.c: -- Hungup 'Zap/4-1' > [Feb 25 17:28:14] VERBOSE[25071] logger.c: == Everyone is busy/congested at this time (1:0/0/1) > > Any assistance on this would be appreciated. >It looks like this might have been a combination of zaptel generating battery alarms which asterisk 1.4 didn't recognize. Could you try updating just zaptel and see if you still see the alarm?