I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2
I've got a 2 port T2XXP card attached with on T1 currently plugged in.
Inbound calls work fine, but outbound fail with the rather cryptic:
[May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to
create channel of type 'DAHDI' (cause 0 - Unknown)
There are similar threads I've found on the net but they tend to be related
to dahdi not being loaded or similar. In my case dahdi is loaded and
channels visible.
I've rsync'd a configuration (/etc/asterisk and /etc/dahdi) from another
server that is currently working fine. But still no luck.
Any hints would be appreciated. In particular if someone can suggest some
documentation on what _could_ cause a (cause 0 - Unknown) then I can
investigate those.
Some details below:
geriatrix ~ # dahdi_scan
[1]
active=yes
alarms=OK
description=T2XXP (PCI) Card 0 Span 1
name=TE2/0/1
manufacturer=Digium
devicetype=Wildcard TE210P (4th Gen)
location=Board ID Switch 0
basechan=1
totchans=24
irq=48
type=digital-T1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF
[2]
active=yes
alarms=RED
description=T2XXP (PCI) Card 0 Span 2
name=TE2/0/2
manufacturer=Digium
devicetype=Wildcard TE210P (4th Gen)
location=Board ID Switch 0
basechan=25
totchans=24
irq=48
type=digital-T1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF
geriatrix ~ # cat /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Tue May 19 17:37:11 2009 -- do
not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) B8ZS/ESF
ClockSource
span=1,1,0,esf,b8zs
# termtype: te
bchan=1-23
dchan=24
echocanceller=mg2,1-23
# Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" B8ZS/ESF RED
span=2,2,0,esf,b8zs
# termtype: te
bchan=25-47
dchan=48
echocanceller=mg2,25-47
# Global data
loadzone = us
defaultzone = us
geriatrix ~ # lsmod
Module Size Used by
dahdi_echocan_mg2 5128 0
wct4xxp 285696 48
dahdi 180904 100 dahdi_echocan_mg2,wct4xxp
geriatrix*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret
pseudo default default
1 DID_span_1 default
2 DID_span_1 default
3 DID_span_1 default
4 DID_span_1 default
5 DID_span_1 default
6 DID_span_1 default
7 DID_span_1 default
8 DID_span_1 default
9 DID_span_1 default
10 DID_span_1 default
11 DID_span_1 default
12 DID_span_1 default
13 DID_span_1 default
14 DID_span_1 default
15 DID_span_1 default
16 DID_span_1 default
17 DID_span_1 default
18 DID_span_1 default
19 DID_span_1 default
20 DID_span_1 default
21 DID_span_1 default
22 DID_span_1 default
23 DID_span_1 default
25 DID_span_2 default
26 DID_span_2 default
27 DID_span_2 default
28 DID_span_2 default
29 DID_span_2 default
30 DID_span_2 default
31 DID_span_2 default
32 DID_span_2 default
33 DID_span_2 default
34 DID_span_2 default
35 DID_span_2 default
36 DID_span_2 default
37 DID_span_2 default
38 DID_span_2 default
39 DID_span_2 default
40 DID_span_2 default
41 DID_span_2 default
42 DID_span_2 default
43 DID_span_2 default
44 DID_span_2 default
45 DID_span_2 default
46 DID_span_2 default
47 DID_span_2 default
--
Kal
Can you make an outbound call after your first incoming call? That's what I
experienced with 1.4.24.
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Kal Feher
Sent: Tuesday, May 19, 2009 9:48 AM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Unable to make outbound calls
I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2
I've got a 2 port T2XXP card attached with on T1 currently plugged in.
Inbound calls work fine, but outbound fail with the rather cryptic:
[May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to
create channel of type 'DAHDI' (cause 0 - Unknown)
There are similar threads I've found on the net but they tend to be related
to dahdi not being loaded or similar. In my case dahdi is loaded and
channels visible.
I've rsync'd a configuration (/etc/asterisk and /etc/dahdi) from another
server that is currently working fine. But still no luck.
Any hints would be appreciated. In particular if someone can suggest some
documentation on what _could_ cause a (cause 0 - Unknown) then I can
investigate those.
Some details below:
geriatrix ~ # dahdi_scan
[1]
active=yes
alarms=OK
description=T2XXP (PCI) Card 0 Span 1
name=TE2/0/1
manufacturer=Digium
devicetype=Wildcard TE210P (4th Gen)
location=Board ID Switch 0
basechan=1
totchans=24
irq=48
type=digital-T1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF
[2]
active=yes
alarms=RED
description=T2XXP (PCI) Card 0 Span 2
name=TE2/0/2
manufacturer=Digium
devicetype=Wildcard TE210P (4th Gen)
location=Board ID Switch 0
basechan=25
totchans=24
irq=48
type=digital-T1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF
geriatrix ~ # cat /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Tue May 19 17:37:11 2009 -- do
not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) B8ZS/ESF
ClockSource
span=1,1,0,esf,b8zs
# termtype: te
bchan=1-23
dchan=24
echocanceller=mg2,1-23
# Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" B8ZS/ESF RED
span=2,2,0,esf,b8zs
# termtype: te
bchan=25-47
dchan=48
echocanceller=mg2,25-47
# Global data
loadzone = us
defaultzone = us
geriatrix ~ # lsmod
Module Size Used by
dahdi_echocan_mg2 5128 0
wct4xxp 285696 48
dahdi 180904 100 dahdi_echocan_mg2,wct4xxp
geriatrix*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret
pseudo default default
1 DID_span_1 default
2 DID_span_1 default
3 DID_span_1 default
4 DID_span_1 default
5 DID_span_1 default
6 DID_span_1 default
7 DID_span_1 default
8 DID_span_1 default
9 DID_span_1 default
10 DID_span_1 default
11 DID_span_1 default
12 DID_span_1 default
13 DID_span_1 default
14 DID_span_1 default
15 DID_span_1 default
16 DID_span_1 default
17 DID_span_1 default
18 DID_span_1 default
19 DID_span_1 default
20 DID_span_1 default
21 DID_span_1 default
22 DID_span_1 default
23 DID_span_1 default
25 DID_span_2 default
26 DID_span_2 default
27 DID_span_2 default
28 DID_span_2 default
29 DID_span_2 default
30 DID_span_2 default
31 DID_span_2 default
32 DID_span_2 default
33 DID_span_2 default
34 DID_span_2 default
35 DID_span_2 default
36 DID_span_2 default
37 DID_span_2 default
38 DID_span_2 default
39 DID_span_2 default
40 DID_span_2 default
41 DID_span_2 default
42 DID_span_2 default
43 DID_span_2 default
44 DID_span_2 default
45 DID_span_2 default
46 DID_span_2 default
47 DID_span_2 default
--
Kal
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
> Can you make an outbound call after your first incoming call? That's what Iexperienced with 1.4.24. No I can't. I saw similar threads while searching for a solution, but in my case outbound calls are never possible. Regardless, thank you for your suggestion. On 19/5/09 4:47 PM, "Kal Feher" <kalman.feher at melbourneit.com.au> wrote:>> I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2 >> >> I've got a 2 port T2XXP card attached with on T1 currently plugged in. >> >> Inbound calls work fine, but outbound fail with the rather cryptic: >> [May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to >> create channel of type 'DAHDI' (cause 0 - Unknown) >> >> There are similar threads I've found on the net but they tend to be relatedto>> dahdi not being loaded or similar. In my case dahdi is loaded and channels >> visible. >> >> I've rsync'd a configuration (/etc/asterisk and /etc/dahdi) from another >> server that is currently working fine. But still no luck. >> >> Any hints would be appreciated. In particular if someone can suggest some >> documentation on what _could_ cause a (cause 0 - Unknown) then I can >> investigate those. >> >> Some details below: >> <removed in reply to keep email readable>-- Kal