View previous topic :: View next topic |
Author |
Message |
covici at ccs.covici.com Guest
|
Posted: Mon Feb 25, 2008 5:38 pm Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
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 |
|
Back to top |
|
|
sruffell at digium.com Guest
|
Posted: Mon Feb 25, 2008 6:01 pm Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
Hi John,
John Covici wrote:
Quote: | 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 |
|
Back to top |
|
|
covici at ccs.covici.com Guest
|
Posted: Mon Feb 25, 2008 6:28 pm Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
How would I use that with kernel 2.6.24?
on Monday 02/25/2008 Shaun Ruffell(sruffell at digium.com) wrote
Quote: | Hi John,
John Covici wrote:
Quote: | 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
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
--
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 |
|
Back to top |
|
|
sruffell at digium.com Guest
|
Posted: Mon Feb 25, 2008 6:47 pm Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
John covici wrote:
Quote: | How would I use that with kernel 2.6.24?
|
Ok...good point. Tonight I'll make a patch for issue 11855 to fix this,
even if it means removing the dtmf-twister code until I can figure out
what is going on as pat suggested. |
|
Back to top |
|
|
sruffell at digium.com Guest
|
Posted: Tue Feb 26, 2008 8:19 pm Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
John Covici wrote:
Quote: | 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? |
|
Back to top |
|
|
covici at ccs.covici.com Guest
|
Posted: Tue Feb 26, 2008 8:48 pm Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
I updated zaptel and I can dial out, but when someone calls in it
won't hangup unless my extension hangs up, which was not true before.
This is a better state than before, thanks much for fixing so far.
on Tuesday 02/26/2008 Shaun Ruffell(sruffell at digium.com) wrote
Quote: | John Covici wrote:
Quote: | 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?
|
--
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 |
|
Back to top |
|
|
tzafrir.cohen at xorco... Guest
|
Posted: Wed Feb 27, 2008 5:07 am Post subject: [asterisk-users] cannot dial out with latest zaptel and kern |
|
|
On Tue, Feb 26, 2008 at 07:19:58PM -0600, Shaun Ruffell wrote:
Quote: | John Covici wrote:
Quote: | 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.
|
Asterisk has always[0] had alarms on channels. It just doesn't properly
report them to the user:
Here's the original method, before the new interface added in zaptel
1.4.8 and used by Asterisk 1.6:
Zaptel reports the fact that a channel is in alarm on specific channels.
But the type of alarms could only be set on spans.
So:
1. driver sets channel in alarm (no alarm on span).
2. Asterisk gets notified of the alarm.
3. Asterisk asks the span what alarm is there.
4. Span answers that there's no alarm.
5. Asterisk reports that the alarm is called "no alarm".
The channel is still in alarm and e.g will not accept calls.
Before we noticed that this trick works, only drivers where there is 1
port per span (all the digital ones, and, well, the X100P) supported
notifying red alarm when the line disconnected.
The newer interface adds on the kernel side a per-channel place to save
the alarm state of the channel (so we can remember the alarm state of
each port separately) and allows userspace to ask about them. The newer
version of Asterisk can use that and ask for a channel alarm if it got
an alarm event and the span has no alarm set.
[0] That is: as long as I can remember. It worked well in 1.2, and I
suppose it was there much ealier
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir |
|
Back to top |
|
|
|