[asterisk-users] cannot dial out with latest zaptel and kernel 2.6.24

[Tzafrir Cohen]

On Tue, Feb 26, 2008 at 07:19:58PM -0600, Shaun Ruffell wrote:
> 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.

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