Home » Forums » Community Edition » Trunks

Dual Digium cards. Analog and Digital

The Fonze73
Posts: 15
 Member Since:
2010-06-30
Submitted by The Fonze73 on Fri, 08/13/2010 - 1:51am.

Hi all

I am running trixbox CE 2.8.0.4
I have just installed a Digium TE121 w/Echo Can in E1 mode.
The system has an existing TDM2400 with 16 FXO ports installed.

Since physically installing the TE121 Asterisk see's the TE121 as 'Span 1' and the TDM as 'Span 2'

As far as I am aware this has changed the Zap/DAHDI channel numbers on the TDM from 1 - 16 to 32 - 47.
My issue is I have changed the channel numbers in the trixbox GUI under 'PBX Settings - Trunks' from Zap/1 to Zap/32 and so on for the remaining channels. I also checked my outbound routes which had automatically changed to the the new channel numbers.

I cannot make an outbound call. In the CLI for all channels i get something like
------------------------------------------------------------------------------------------------------------------------------
"Executing [s@macro-dialout-trunk:19] Dial("SIP/200-00000003", "DAHDI/32/60855512345,300,") in new stack
== Everyone is busy/congested at this time (1:0/0/1)"
------------------------------------------------------------------------------------------------------------------------------
I also have Incoming Routes set through 'PBX Settings - Zap Channel DID's' which I have also amended.

The inbound calls are also not being routed.

I have not yet configured the digital card but would like to get the TDM up and running first.

I am quite new to Asterisk. What did I miss?

Here is a copy of my 'system.conf' after running 'setup-pstn'

----------------------------------------------------------------------------------------------------------
# Autogenerated by /usr/sbin/dahdi_genconf on Fri Aug 13 16:56:20 2010
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER)
span=1,1,0,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
echocanceller=mg2,1-15,17-31

# Span 2: WCTDM/0 "Wildcard TDM2400P Board 1"
fxsks=32
echocanceller=mg2,32
fxsks=33
echocanceller=mg2,33
fxsks=34
echocanceller=mg2,34
fxsks=35
echocanceller=mg2,35
fxsks=36
echocanceller=mg2,36
fxsks=37
echocanceller=mg2,37
fxsks=38
echocanceller=mg2,38
fxsks=39
echocanceller=mg2,39
fxsks=40
echocanceller=mg2,40
fxsks=41
echocanceller=mg2,41
fxsks=42
echocanceller=mg2,42
fxsks=43
echocanceller=mg2,43
fxsks=44
echocanceller=mg2,44
fxsks=45
echocanceller=mg2,45
fxsks=46
echocanceller=mg2,46
fxsks=47
echocanceller=mg2,47
# channel 48, WCTDM/0/16, no module.
# channel 49, WCTDM/0/17, no module.
# channel 50, WCTDM/0/18, no module.
# channel 51, WCTDM/0/19, no module.
# channel 52, WCTDM/0/20, no module.
# channel 53, WCTDM/0/21, no module.
# channel 54, WCTDM/0/22, no module.
# channel 55, WCTDM/0/23, no module.

# Global data

loadzone = us
defaultzone = us
----------------------------------------------------------------------------------------------------------

‹ Follow Me CID Trixbox v2.8 roll-over from SIP Trunk to ZAP Trunk Issue ›


The Fonze73
Posts: 15
 Member Since:
2010-06-30
Anyone?????
Sun, 08/15/2010 - 12:42am

Anyone?????



SkykingOH
Posts: 9541
 Member Since:
2007-12-17
What is the output of 'dahdi
Sun, 08/15/2010 - 7:00am

What is the output of 'dahdi show channels' ???

--

Scott

aka "Skyking"



The Fonze73
Posts: 15
 Member Since:
2010-06-30
Thanks for the reply Scott I
Mon, 08/16/2010 - 1:33am

Thanks for the reply Scott

I have had to remove the TE121 so that we had an operational PBX during work hours so I will give it another go tomorrow night after office hours.

Here is the 'dahdi show channels' with only the TDM2400 installed (with 16 FXO ports)

I wil post the result with the TE121 tomorrow.

Many Thanks

Nick

---------------------------------------------------------------------------------------------

Chan Extension Context Language MOH Interpret Blocked State
pseudo default au default In Service
1 from-zaptel au default In Service
2 from-zaptel au default In Service
3 from-zaptel au default In Service
4 from-zaptel au default In Service
5 from-zaptel au default In Service
6 from-zaptel au default In Service
7 from-zaptel au default In Service
8 from-zaptel au default In Service
9 from-zaptel au default In Service
10 from-zaptel au default In Service
11 from-zaptel au default In Service
12 from-zaptel au default In Service
13 from-zaptel au default In Service
14 from-zaptel au default In Service
15 from-zaptel au default In Service
16 from-zaptel au default In Service



The Fonze73
Posts: 15
 Member Since:
2010-06-30
After instlling the TE121
Tue, 08/17/2010 - 2:51am

After instlling the TE121 and running 'setup-pstn'
From the trixbox CLI 'dahdi show channels' returns the following!!!

No such command 'dahdi show channels' (type 'help dahdi show' for other possible commands)



stechnique
Posts: 733
 Member Since:
2008-02-21
The module isn't loaded in
Tue, 08/17/2010 - 5:22am

The module isn't loaded in asterisk, which probably means a misconfigured chan_dahdi.conf file.



The Fonze73
Posts: 15
 Member Since:
2010-06-30
Problem Solved sort of...
Thu, 08/26/2010 - 10:06pm

Everytime I would run 'setup-pstn' with both cards installed it would kill dahdi. Even with a fresh install.

I downgraded from 2.8.0.4 to 2.8.0.2

and Presto

All working.



The Fonze73
Posts: 15
 Member Since:
2010-06-30
DAHDI BROKEN AGAIN!!!
Tue, 08/31/2010 - 3:10am

After downgrading to 2.8.0.2 CDR stopped logging calls and tbm-backup module stopped working. thinking that in 2.0.8.4 something in the 'setup-pstn' script was killing my trunks I did a 'yum update' hoping it would sort out the backup and CDR issuse without killing the digium cards as they were alrady configured.

WRONG!!

Back to square 1.

From the trixbox CLI 'dahdi show channels' returns the following!!!
no such command 'dahdi show channels' (type 'help dahdi show' for other possible commands)

If I reinstall 2.8.0.2 I cannot restore the backup (so have to manually configure everything again) and CDR won't work.

A fix for 2.8.0.4 would be fantastic....

Here is my 'chan_dahdi.conf'

;
; DAHDI telephony
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
;echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include setup-pstn configs
#include dahdi-channels.conf

group=1

;Include PBXconfig configs
#include chan_dahdi_additional.conf

Here is my 'dahdi-channels.conf'

; Autogenerated by /usr/sbin/dahdi_genconf on Thu Aug 26 22:23:49 2010
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER) HDB3/CCS/CRC4 REDClockSource
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel => 1-15,17-31
context = default
group = 63

; Span 2: WCTDM/0 "Wildcard TDM2400P Board 1"
;;; line="32 WCTDM/0/0 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 32
callerid=
group=
context=default

;;; line="33 WCTDM/0/1 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 33
callerid=
group=
context=default

;;; line="34 WCTDM/0/2 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 34
callerid=
group=
context=default

;;; line="35 WCTDM/0/3 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 35
callerid=
group=
context=default

;;; line="36 WCTDM/0/4 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 36
callerid=
group=
context=default

;;; line="37 WCTDM/0/5 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 37
callerid=
group=
context=default

;;; line="38 WCTDM/0/6 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 38
callerid=
group=
context=default

;;; line="39 WCTDM/0/7 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 39
callerid=
group=
context=default

;;; line="40 WCTDM/0/8 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 40
callerid=
group=
context=default

;;; line="41 WCTDM/0/9 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 41
callerid=
group=
context=default

;;; line="42 WCTDM/0/10 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 42
callerid=
group=
context=default

;;; line="43 WCTDM/0/11 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 43
callerid=
group=
context=default

;;; line="44 WCTDM/0/12 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 44
callerid=
group=
context=default

;;; line="45 WCTDM/0/13 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 45
callerid=
group=
context=default

;;; line="46 WCTDM/0/14 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 46
callerid=
group=
context=default

;;; line="47 WCTDM/0/15 FXSKS (SWEC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 47
callerid=
group=
context=default



The Fonze73
Posts: 15
 Member Since:
2010-06-30
CANNOT LOAD chan_dahdi module
Tue, 08/31/2010 - 4:04am

[trixbox1.localdomain /]# ldd /usr/lib/asterisk/modules/chan_dahdi.so
linux-gate.so.1 => (0x009e3000)
libtonezone.so.2.0 => /usr/lib/libtonezone.so.2.0 (0x00364000)
libpri.so.1.4 => /usr/lib/libpri.so.1.4 (0x00256000)
libss7.so.1 => /usr/lib/libss7.so.1 (0x00ccf000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00e03000)
libc.so.6 => /lib/libc.so.6 (0x0055c000)
libm.so.6 => /lib/libm.so.6 (0x001fc000)
/lib/ld-linux.so.2 (0x00e5b000)

trixbox1*CLI> module load chan_dahdi
Unable to load module chan_dahdi
Command 'module load chan_dahdi' failed.
== Parsing '/etc/asterisk/chan_dahdi.conf': == Found
== Parsing '/etc/asterisk/dahdi-channels.conf': == Found
== Parsing '/etc/asterisk/chan_dahdi_additional.conf': == Found
== Parsing '/etc/asterisk/users.conf': == Found
trixbox1*CLI>



The Fonze73
Posts: 15
 Member Since:
2010-06-30
ANYONE?????
Tue, 09/07/2010 - 1:01am

still no luck



sak71
Posts: 3
 Member Since:
2007-07-01
Same problem
Thu, 11/11/2010 - 10:18am

Hi, Fonze73

I have the same problem. Have you ever solved? Any suggestion?

Thanks



The Fonze73
Posts: 15
 Member Since:
2010-06-30
Hey sak71 I ended up
Thu, 11/11/2010 - 5:18pm

Hey sak71

I ended up reverting to back to trixbox 2.8.0.2 and both cards just worked after a clean install.

yum update would kill the cards.

CDR stopped working but everything else seems to be OK



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.