dial_exec_full: Unable to create channel of type 'zap'

Asterisk Asterisk Support
1
  • card: te120p
  • asterisk 1.4.1
  • zaptel 1.4.4
  • libpri 1.4.1
  • fedora core 5 (2.6.15)

===== zap show status =======
Description Alarms IRQ bpviol CRC4
Wildcard TE12xP Card 0 OK 34 0 0

===== ztcfg -vv ====
[root@localhost ~]# ztcfg -vv

Zaptel Version: 1.4.4
Echo Canceller: MG2
Configuration

SPAN 1: ESF/B8ZS 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: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Clear channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18)
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: D-channel (Default) (Slaves: 24)

24 channels configured.

==== cli output ====
– Executing [38889100@incoming:2] Answer(“SIP/192.168.1.19-09ab4fc0”, “”) in new stack
– Executing [31189100@incoming:3] Dial(“SIP/192.168.1.19-09ab4fc0”, “zap/g1/28882760”) in new stack
[Jul 29 20:10:02] WARNING[17635]: app_dial.c:1090 dial_exec_full: Unable to create channel of type ‘zap’ (cause 0 - Unknown)
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [38889100@incoming:4] Hangup(“SIP/192.168.1.19-09ab4fc0”, “”) in new stack

==== zaptel.conf ====
loadzone=us
defaultzone=us
span=1,0,0,esf,b8zs
bchan=1-23
dchan=24

======= zapata.conf =====
group=1
signalling=pri_cpe
switchtype=ni1 ( also tried national )
context=incoming
channel=1-23

==== extensions.conf ====
[38889100]
exten => ${38889100},1,Wait(1)
exten => ${38889100},2,Answer
exten => ${38889100},n,dial(zap/g1/28882760)
exten => ${3889100},n,Hangup

pls kindly advise.

2

After contacted with telco, the d-channel is still not up. The physical connection should be ok because led is green.

zttool shows that
sync source is "internally clocked"
irq miss: 58

confirmed with telco that b8zs, esf are correct.

pls advise what is wrong with the zaptel.conf

3

I have the same issue using Ubuntu 6.

Zttool give the same error (internally clocked) and 0 IRQ missed.

Configuration is (protocols have been checked with Telco and E1s have been resetted on Telco’s side).

zaptel.conf

Carte analogique

fxoks=1
fxsks=2-4
loadzone=fr
defaultzone=fr

Carte dual span E1/T1 TE210P

span=1,1,0,ccs,hdb3
bchan=5-19
dchan=20
bchan=21-35
loadzone=fr
defaultzone=fr

span=2,1,0,ccs,hdb3
bchan=36-50
dchan=51
bchan=52-66
loadzone=fr
defaultzone=fr

forgot some information about Asterisk:
Asterisk SVN-branch-1.4-r77795

Looks like a bug in the Zap management