For anyone looking to use a Digium TE110P with the current release of TB (NOT the 2.2. beta), here is how I finaly got it to actually work.
1. The zaptel kernel modules in the 2.0+ release of TB simply DO NOT SUPPORT the TE110P and PRI... at least in the states.
No matter what config I tried, doing a 'pri show span 1' in asterisk, would identify the pri as
----------
Primary D-channel: 24
Status: Provisioned, Down, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T313 Timer: 4000
N200 Counter: 3
-----------------
talking with the provider, the digium card would not 'sync' with the telco switch on the D channel.
The 'release' version of TB uses zaptel-1.2.9, and working support for the TE110P started around 1.2.10 or 12
update the version of asterisk and zaptel with
yum update asterisk
reboot
this will install asterisk-1.2.18 and zaptel-1.2.17.1 - nothing gets broken (that I've discovered yet), and your TE110P will now show the pri as
............
Primary D-channel: 24
Status: Provisioned, Up, Active
...
...
After that, the configs for my provider that worked are
/etc/zaptel.conf
span=1,1,0,esf,b8zs
bchan=1-23
dchan=24
loadzone = us
defaultzone = us
/etc/asterisk/zapata.conf
[trunkgroups]
[channels]
language=en
context=from-zaptel
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=256
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
..
..
/etc/asterisk/zaptel-auto.conf
callerid=asreceived
group = 1
switchtype=national
signalling=pri_cpe
context=from-zaptel
channel=>1-23
==================================================================
NOTICE the value for "group" - I was unable to get things to work with group set to 0... go just go and change the 'Trunks', 'Inbound' and 'Outbound' routes to use "g1" instead of "g0"
Disclaimer....
This worked for ME, it may not work for YOU... if it doesn't, I cannot offer any additional help... everything I found is here in this post.
Good Luck
Mark
Member Since:
2006-05-31