[Asterisk-Users] HFC BRIstuff woes

[Tzafrir Cohen]

On Sun, Jul 17, 2005 at 09:55:57PM +0200, Zoltan Szecsei wrote:
> Hi All,
> It's broken !!  (drat)

Naturally this is a bug in zaptel/bristuff/whatever, right?

> 
> Asterisk if failing to load with the following error (taken from end of 
> /var/log/asterisk/full) after adding bristuff.
> 
> Can anyone help please?
> 
> Jul 17 19:57:54 VERBOSE[2503]:   == Registered channel type 'Phone' 
> (Standard Linux Telephony API Driver)
> Jul 17 19:57:54 VERBOSE[2503]:  [chan_zap.so]Jul 17 19:57:54 
> VERBOSE[2503]:  [chan_zap.so] => (Zapata Telephony w/PRI)
> Jul 17 19:57:54 VERBOSE[2503]:   == Parsing '/etc/asterisk/zapata.conf': 
> Jul 17 19:57:54 VERBOSE[2503]:   == Parsing '/etc/asterisk/zapata.conf': 
> Found
> Jul 17 19:57:54 VERBOSE[2503]:   == Parsing 
> '/etc/asterisk/zapata_additional.conf': Jul 17 19:57:54 VERBOSE[2503]:   
> == Parsing '/etc/asterisk/zapata_additional.conf': Found
> Jul 17 19:57:54 VERBOSE[2503]:   == Parsing 
> '/etc/asterisk/zapata-auto.conf': Jul 17 19:57:54 VERBOSE[2503]:   == 
> Parsing '/etc/asterisk/zapata-auto.conf': Not found (No such file or 
> directory)
> :-(  Jul 17 19:57:54 WARNING[2503]: Unable to specify channel 1: Device 
> or resource busy
> :-( Jul 17 19:57:54 ERROR[2503]: Unable to open channel 1: Device or 
> resource busy
> :-( here = 0, tmp->channel = 1, channel = 1
> :-( Jul 17 19:57:54 ERROR[2503]: Unable to register channel '1-2'
> :-( Jul 17 19:57:54 WARNING[2503]: chan_zap.so: load_module failed, 
> returning -1

You have a problem with the definitions of channels 1,2 in zapata.conf .
This stops asterisk from starting.

> :-( Jul 17 19:57:54 VERBOSE[2503]:   == Unregistered channel type 'Tor'
> :-( Jul 17 19:57:54 VERBOSE[2503]:   == Unregistered channel type 'Zap'
> :-( Jul 17 19:57:54 WARNING[2503]: Loading module chan_zap.so failed!
> 
> Here's some background:
> Loaded a new AAH 1.1 Centos 3.4 on a PIII with 2 pci HFC ISDN - Asterisk 
> loaded & I could play with internal extensions.
> Added bristuff-0.2.0-RC8h which did a wget and updated to asterisk 1.0.8 
> - all seemed OK & I could load asterisk.
> Did make load manually (by running the steps in zaphfc/Makefile) and 

Do you use the patched versions of zaptel, libpri annd asterisk?

> ztcfg returned:
> 
> [root at asterisk1 zaphfc]# ztcfg -v
> Zaptel Configuration
> ======================
> SPAN 1: CCS/ AMI Build-out: 399-533 feet (DSX-1)
> 3 channels configured.
> ZT_SPANCONFIG failed on span 1: Invalid argument (22)

Can't configure the zaptel channel. Fix this before trying to load
chan_zap

What relevant cards do you have, exactly?

cat /proc/zaptel/1 , please

> [root at asterisk1 zaphfc]#
> 
> The original /etc/zaptel.conf was empty so I added the one from zaphfc/
> The original /etc/asterisk/zapata had a whole lot of stuff in it so I 
> *patched in* the details from zaphfc/zapata.conf
> 
> So, I'm looking for help on what's gone wrong.
> 
> Couple of thoughts:
> Before I added the bristuff I had a zap/g0 channel - given I had only 2 
> IAX IP phones and an x-lite SIP softphone from my XP box, is this 
> channel even used?
> 
> There are 2 HFC cards in the box - yet zaptel.conf only has:
> span=1,1,3,ccs,ami
> bchan=1-2
> dchan=3
> Surely that only relates to one of the ISDN cards?
> 
> 
> Here is a listing of my (hybrid) zapata.conf that I patched with the 
> bristuff zaphfc/zapata.conf. Can anyone tell me what I should have 
> deleted - I am nervous to mess up all the facilities that came 
> preconfigured with AAH1.1, but I'm sure some of the lines will clash 
> with the ISDN needed stuff. What should/must I delete?

zapata.conf is not (yet) relevant here. No matter what channels you
define in zapata.conf, they first must be configured by ztcfg.

-- 
Tzafrir Cohen         | tzafrir at jbr.cohens.org.il | VIM is
http://tzafrir.org.il |                           | a Mutt's  
tzafrir at cohens.org.il |                           |  best
ICQ# 16849755         |                           | friend