asterisk users - Dec 2007 - Zap channels for HFC-S PCI card not responding

Hi list,

After upgrading from Asterisk v1.2 to v1.4.14, all kinds Zaptel error  
messages related to my HFC-S PCI card disappeared, but now I can't  
access the card's resources because it always seems to be busy. Any  
idea why?

Thanks,

Jaap

PS -- Below is some info regarding my configuration.

==========================
Zaptel version: 1.4.7 (incl. firmware and modules).
OS: Debian etch.

Loaded modules:

    zaphfc                 13660  1
    vzaphfc                24984  1
    zaptel                185956  9 xpp,zaphfc,vzaphfc
    crc_ccitt               2560  1 zaptel

# cat /proc/zaptel/*

    Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER)
AMI/CCS

               1 ZTHFC1/0/1 Clear (In use)
               2 ZTHFC1/0/2 Clear (In use)
               3 ZTHFC1/0/3 HDLCFCS (In use)
    Span 2: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]" AMI/CCS

               4 ZTHFC1/0/1 Clear (In use)
               5 ZTHFC1/0/2 Clear (In use)
               6 ZTHFC1/0/3 HDLCFCS (In use)

# ztcfg -vv

    Zaptel Version: 1.4.7-Xorcom-trunk-r5178
    Echo Canceller: MG2
    Configuration
    =====================
    SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
    SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)

    Channel map:

    Channel 01: Clear channel (Default) (Slaves: 01)
    Channel 02: Clear channel (Default) (Slaves: 02)
    Channel 03: D-channel (Default) (Slaves: 03)
    Channel 04: Clear channel (Default) (Slaves: 04)
    Channel 05: Clear channel (Default) (Slaves: 05)
    Channel 06: D-channel (Default) (Slaves: 06)

    6 channels to configure.

/etc/asterisk/zapata-channels.conf after running "genzaptelconf -sd -c
nl":

    group=0,11
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe_ptmp
    channel => 1-2
    group    context=default

    group=0,12
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe_ptmp
    channel => 4-5
    group    context=default

/etc/asterisk/zapata.conf (supposed to work in the Netherlands):

    [trunkgroups]

    [channels]
    language=en
    context=isdn-in
    switchtype=euroisdn
    pridialplan=dynamic
    prilocaldialplan=local
    nationalprefix = 0
    internationalprefix = 00
    overlapdial=yes
    signalling=bri_cpe_ptmp
    rxwink=300
    usecallerid=yes
    hidecallerid=no
    callwaiting=yes
    usecallingpres=yes
    callwaitingcallerid=yes
    threewaycalling=yes
    transfer=yes
    canpark=yes
    cancallforward=yes
    callreturn=yes
    echocancel=yes
    echocancelwhenbridged=yes
    echotraining=100
    rxgain=4.5
    txgain=-3
    group=1
    callgroup=1
    pickupgroup=1
    immediate=yes
    #include zapata-channels.conf

Abbreviated /etc/asterisk/extensions.conf:

    [globals]

    [general]

    [isdn-out]
    exten => _X.,1,Dial(Zap/g0/${EXTEN}@channels,,r)

    [internal]
    exten => 1000,1,Verbose(1|Extension 1000)
    exten => 1000,n,Dial(SIP/1000,30)
    exten => 1000,n,Hangup()

    [phones]
    include => internal
    include => isdn-out

Any attempts to call out result in the following CLI output:

[Dec 30 16:15:41] WARNING[12918]: app_dial.c:1130 dial_exec_full:  
Unable to create channel of type 'Zap' (cause 34 - Circuit/channel  
congestion)
   == Everyone is busy/congested at this time (1:0/1/0)
   == Auto fallthrough, channel 'SIP/1000-081ff9f8' status is
'CONGESTION'
[Dec 30 16:15:41] NOTICE[12918]: cdr.c:434 ast_cdr_free: CDR on  
channel 'SIP/1000-081ff9f8' not posted

CLI> zap show channels:

       Chan Extension  Context         Language   MOH Interpret
     pseudo            default         en         default
          1            from-pstn       en         default
          2            from-pstn       en         default
          4            from-pstn       en         default
          5            from-pstn       en         default

CLI> zap restart:
     Destroying channels and reloading zaptel configuration.
      == Parsing '/etc/asterisk/zapata.conf': Found
      == Parsing '/etc/asterisk/zapata-channels.conf': Found
    [Dec 30 16:32:41] WARNING[13612]: chan_zap.c:1081 zt_open: Unable to
    specify channel 1: Device or resource busy
    [Dec 30 16:32:41] ERROR[13612]: chan_zap.c:7501 mkintf: Unable to open
    channel 1: Device or resource busy
    here = 0, tmp->channel = 1, channel = 1
    [Dec 30 16:32:41] ERROR[13612]: chan_zap.c:12266 build_channels: Unable
    to register channel '1-2'
    [Dec 30 16:32:41] WARNING[13612]: chan_zap.c:11554 zap_restart: Reload
    channels from zap config failed!

Not a good idea, since that results in...

CLI> zap show channels:

       Chan Extension  Context         Language   MOH Interpret


the channels disappearing altogether!

===========================

On Sun, Dec 30, 2007 at 04:48:39PM +0100, Jaap Winius
wrote:
> Hi list,
> 
> After upgrading from Asterisk v1.2 to v1.4.14, all kinds Zaptel error  
> messages related to my HFC-S PCI card disappeared, but now I can't  
> access the card's resources because it always seems to be busy. Any  
> idea why?
What do you mean by "busy"? What exactly do you see?

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