Zap problems with 1.4.4/1.4.2.1

Asterisk Asterisk Support
1

Hi everyone,

I am having major problems with zap channels & I can’t figure out why! When I start asterisk I have no dial tone and can’t call zap devices. I have specifically configured 1.4.4 --with-zaptel

Here is my configuration

[root@asterisk rob]# cat /proc/zaptel/*
Span 1: WCTDM/0 “Wildcard TDM400P REV I Board 1”

       1 WCTDM/0/0 
       2 WCTDM/0/1 FXOKS (In use) 
       3 WCTDM/0/2 FXOKS 
       4 WCTDM/0/3

Span 2: WCFXO/0 “Wildcard X100P Board 1” RED

       5 WCFXO/0/0 FXSKS (In use)

[root@asterisk rob]# cat /proc/zaptel/*
Span 1: WCTDM/0 “Wildcard TDM400P REV I Board 1”

       1 WCTDM/0/0 
       2 WCTDM/0/1 FXOKS (In use) 
       3 WCTDM/0/2 FXOKS 
       4 WCTDM/0/3

Span 2: WCFXO/0 “Wildcard X100P Board 1” RED

       5 WCFXO/0/0 FXSKS (In use)

[root@asterisk etc]# more /etc/zaptel.conf
fxoks=2
fxoks=3
fxsks=5
loadzone=us
defaultzone=us

[root@asterisk asterisk]# more /etc/asterisk/zapata.conf
[trunkgroups]

[channels]
; hardware channels
; default
usecallerid=yes
hidecallerid=no
callwaiting=no
threewaycalling=no
transfer=yes
echocancel=yes
echotraining=yes

;define channels
context=world
signalling=fxs_ks
language=en
channel => 5 ;

context=trusted
signalling=fxo_ks
language=en
channel => 2 ;

context=trusted
signalling=fxo_ks
language=en
channel => 3 ;

[root@asterisk asterisk]# more extensions.conf
[world]
exten => s,1,Dial(SIP/101)
exten => 101,1,Dial(SIP/101)

[trusted]
exten => 101,1,Dial(SIP/101)
exten => 102,1,Dial(SIP/102)
exten => 103,1,Dial(SIP/103)
exten => 105,1,Dial(SIP/105)
exten => 106,1,Dial(SIP/106)
exten => 107,1,Dial(SIP/107)
exten => 109,1,Dial(SIP/109)
exten => 110,1,Dial(SIP/110)
exten => 111,1,Dial(SIP/111)
exten => 112,1,Dial(SIP/112)
exten => 113,1,Dial(SIP/113)
exten => 114,1,Dial(SIP/114)
exten => 115,1,Dial(SIP/115)
exten => 120,1,Dial(ZAP/0)
exten => 121,1,Dial(ZAP/1)
exten => 122,1,Dial(ZAP/2)
exten => 123,1,Dial(ZAP/3)
exten => 124,1,Dial(ZAP/4)
exten => 125,1,Dial(ZAP/5)
exten => 150,1,Dial(SIP/150)

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

[root@asterisk asterisk]# /usr/sbin/asterisk -r
Asterisk 1.4.4, Copyright © 1999 - 2006 Digium, Inc. and others.
Created by Mark Spencer markster@digium.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.
Connected to Asterisk 1.4.4 currently running on asterisk (pid = 24249)
Verbosity is at least 3
– Remote UNIX connection
– Executing [122@trusted:1] Dial(“SIP/101-08ecd6e8”, “ZAP/2”) in new stack
[May 15 06:26:49] WARNING[24614]: channel.c:3099 ast_request: No channel type registered for ‘ZAP’
[May 15 06:26:49] WARNING[24614]: app_dial.c:1099 dial_exec_full: Unable to create channel of type ‘ZAP’ (cause 66 - Channel not implemented)
== Everyone is busy/congested at this time (1:0/0/1)
== Auto fallthrough, channel ‘SIP/101-08ecd6e8’ status is ‘CHANUNAVAIL’

Anyone have any ideas?

2

First of all, determine if Asterisk is compiled with zaptel.

See what’s the output.

3

As I mentioned in my post I did compile it --with-zaptel

module load chan_zap gives me:

asterisk*CLI> module load chan_zap
[May 17 16:09:23] WARNING[19103]: pbx.c:2946 ast_register_application: Already have an application ‘ZapSendKeypadFacility’
== Parsing ‘/etc/asterisk/zapata.conf’: Found
– Registered channel 5, FXS Kewlstart signalling
– Registered channel 2, FXO Kewlstart signalling
[May 17 16:09:23] WARNING[19103]: chan_zap.c:904 zt_open: Unable to specify channel 3: No such device
[May 17 16:09:23] ERROR[19103]: chan_zap.c:7144 mkintf: Unable to open channel 3: No such device
here = 0, tmp->channel = 3, channel = 3
[May 17 16:09:23] ERROR[19103]: chan_zap.c:10442 build_channels: Unable to register channel ‘3’

4

Sorry did not notice --with-zaptel.

This is bad. What’s the output of ztconfig -vv? Should use zttool to try to resolve the RED alert. Is the line on? Connected to the right socket?

5

The line is red because the line is not connected. I’m really just worried about the fxs ports now, not the fxo.

[root@asterisk rob]# /sbin/ztcfg -vv

Zaptel Version: 1.4.2.1
Echo Canceller: MG2
Configuration

Channel map:

Channel 02: FXO Kewlstart (Default) (Slaves: 02)
Channel 03: FXO Kewlstart (Default) (Slaves: 03)
Channel 05: FXS Kewlstart (Default) (Slaves: 05)

3 channels configured.

Any suggestions?

6

I must be doing something obviously wrong, no ? Someone must know…!!!