[asterisk-users] [URGENT] Zap channels fail to load

Tzafrir Cohen tzafrir.cohen at xorcom.com
Tue Feb 26 06:21:04 CST 2008


Note: [Urgent] is generally not a good way to escalate the issue on a
public mailing list. We're all here for the fun of it and demanding
prompt reply may actually serve the other way.

If you have paid to get support (e.g: by buying hardware), this may be a
good time to use it.

That said, your message looks interesting. So see my reply inline :-)

On Tue, Feb 26, 2008 at 10:44:27AM +0000, Andres Jimenez wrote:
> I have spent some time this morning trying to add an Astribank to our
> current Asterisk, but it failed, 

Contact me privately :-)

> so I just removed the hardware,
> restore the config files to the original setup and started asterisk.;
> 
> I could see that no Zap channels are started so I did load chan_zap.so:
> pbx*CLI> module load chan_zap.so

You probably needed 'module unload chan_zap.so' before that. The module
was loaded, but it has bailed out before registering the CLI commands.

> [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application:
> Already have an application 'ZapSendKeypadFacility'
>   == Parsing '/etc/asterisk/zapata.conf': Found
> [Feb 26 10:32:18] WARNING[3809]: chan_zap.c:904 zt_open: Unable to
> specify channel 1: Device or resource busy
> [Feb 26 10:32:18] ERROR[3809]: chan_zap.c:7186 mkintf: Unable to open
> channel 1: Device or resource busy
> here = 0, tmp->channel = 1, channel = 1
> [Feb 26 10:32:18] ERROR[3809]: chan_zap.c:10527 build_channels: Unable
> to register channel '1-15'
> 
> Fair enough. I did unloaded chan_zap.so (because of the first error)
> and tried again:
> 
> pbx*CLI> module load chan_zap.so
> [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application:
> Already have an application 'ZapSendKeypadFacility'
>   == Parsing '/etc/asterisk/zapata.conf': Found
> [Feb 26 10:32:18] WARNING[3809]: chan_zap.c:904 zt_open: Unable to
> specify channel 1: Device or resource busy
> [Feb 26 10:32:18] ERROR[3809]: chan_zap.c:7186 mkintf: Unable to open
> channel 1: Device or resource busy
> here = 0, tmp->channel = 1, channel = 1
> [Feb 26 10:32:18] ERROR[3809]: chan_zap.c:10527 build_channels: Unable
> to register channel '1-15'
> 
> It looks like the problem is in the zap card's first channel:
> 
> pbx:~# cat /proc/zaptel/1
> Span 1: WCT1/0 "Wildcard TE12xP Card 0" HDB3/CCS
>         IRQ misses: 36
> 
>            1 WCT1/0/1 Clear (In use)
>            2 WCT1/0/2 Clear

The symptom is expelained in the following report that I filed earlier
today (unrelated to this one)

  http://bugs.digium.com/12071

Channel 1 was left open from a failed configuration attempt

So the real error hides earlier in your logs. Look for 'chan_zap' in the
logs from the startup of Asterisk. And sadly you must restart Asterisk
to fix the error.

>            3 WCT1/0/3 Clear
>            4 WCT1/0/4 Clear
>            5 WCT1/0/5 Clear
>            6 WCT1/0/6 Clear
>            7 WCT1/0/7 Clear
>            8 WCT1/0/8 Clear
>            9 WCT1/0/9 Clear
>           10 WCT1/0/10 Clear
>           11 WCT1/0/11 Clear
>           12 WCT1/0/12 Clear
>           13 WCT1/0/13 Clear
>           14 WCT1/0/14 Clear
>           15 WCT1/0/15 Clear
>           16 WCT1/0/16 HDLCFCS
>           17 WCT1/0/17 Clear
>           18 WCT1/0/18 Clear
>           19 WCT1/0/19 Clear
>           20 WCT1/0/20 Clear
>           21 WCT1/0/21 Clear
>           22 WCT1/0/22 Clear
>           23 WCT1/0/23 Clear
>           24 WCT1/0/24 Clear

Is this a fractional E1, indeed?

Or is the range in zaptel.conf incorrect? I noticed in your config file
that you changed it. Was this change made after Asterisk was started?

>           25 WCT1/0/25
>           26 WCT1/0/26
>           27 WCT1/0/27
>           28 WCT1/0/28
>           29 WCT1/0/29
>           30 WCT1/0/30
>           31 WCT1/0/31
> 
> 
> Is there any change any Astribank related stuff can be causing this?
> 
> I have ensured that no Astribanks modules are loaded and even rebooted
> the box, but no success.

I'm not sure how an Astribank module would have affected this one. The
Astribank spans tend to be the last ones, hence it should not have
misplaced your hardware.

If the module is loaded but no hardware is present, your system should
not be affected.

> 
> 
> pbx:~# cat /etc/zaptel.conf
> # CRC off
> #
> loadzone = uk
> defaultzone = uk
> 
> span=1,1,0,ccs,hdb3
> bchan=1-15
> dchan=16
> bchan=17-24
> 
> #or this with crc on
> #
> #loadzone = uk
> #defaultzone = uk
> 
> #span=1,1,0,ccs,hdb3,crc4
> #bchan=1-15
> #dchan=16
> #bchan=17-24
> 
> pbx:~# cat /etc/asterisk/zapata.conf
> language=en
> internationalprefix = 00
> nationalprefix = 0
> switchtype = euroisdn
> pridialplan = local
> priindication = outofband
> usecallerid = yes
> hidecallerid = no
> callwaiting = yes
> usecallingpres = yes
> callwaitingcallerid = yes
> threewaycalling = yes
> transfer = yes
> cancallforward = yes
> callreturn = yes
> group = 1
> callgroup = 0
> pickupgroup = 0
> immediate = no
> echotraining = yes
> echocancel = yes
> echocancelwhenbridged = no
> facilityenable = yes
> musiconhold = default
> ;overlapdial = yes
> overlapdial = no
> immediate = no
> txgain = -4.0
> rxgain = -4.0
> signalling = pri_cpe
> channel => 1-15
> ;channel => 17-32
> channel => 17-24
> ;toneduration=100
> toneduration=300
> ;relaxdtmf=yes

-- 
               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



More information about the asterisk-users mailing list