Page 1 of 1
TATA E1 Configuration Issue - SOLVED

Posted:
Mon Jul 20, 2009 3:12 pm
by tech.php
Hi Forum,
Facing issues with configuring TATA E1 line with Digium TE121p, on asterisk-1.2.26, zaptel-1.2.23 & libpri-1.4.5
As per TATA people here; termination is Pin 1&2 - Rx , Pin 4&5 - Tx. Have put a straight through cable to terminate on the card bracket in similar fashion i.e. Pin 1&2 - Rx , Pin 4&5 - Tx.
Here's my zaptel.conf and zapata.conf
[zaptel.conf]
span=1,1,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
loadzone=uk
defaultzone=uk
[zapata.conf]
[trunkgroups]
[channels]
language=en
context=from-zaptel
switchtype=euroisdn
pridialplan=unknown
priindication=outofband
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
callgroup=1
pickupgroup=1
immediate=no
echotraining=800
echocancel=yes
echocancelwhenbridged=no
relaxdtmf=yes
musiconhold=default
immediate=no
txgain=0.0
rxgain=0.0
group=1
signalling=pri_cpe
channel=>1-15,17-31
overlapdial=yes
Errors received; while starting asterisk:
ERROR[4177]: chan_zap.c:10798 setup_zap: Unknown signalling method 'pri_cpe'
ERROR[4177]: chan_zap.c:10415 setup_zap: Signalling must be specified before any channels are.
WARNING[4177]: loader.c:415 __load_resource: chan_zap.so: load_module failed, returning -1
WARNING[4177]: loader.c:555 load_modules: Loading module chan_zap.so failed!
Help required urgently.
Thanks in advance.

Posted:
Mon Jul 20, 2009 3:35 pm
by diyanat
You may connect the cable in the following way
Tata TE121p
1 -------> 5
2 -------> 4
4 -------> 1
5 -------> 2
Also check with your provider if CRC is on, if so you will need to add crc to zaptel.conf
span=1,1,0,ccs,hdb3,crc4
regards
Diyanat Ali

Posted:
Mon Jul 20, 2009 3:43 pm
by tech.php
Thanx for yoour prompt reply.
Did the changes, the errors went away but the output of "zap show status" has changed from OK to REC.
Attaching output of few, suppose they can be of help:
zap show status
Description Alarms IRQ bpviol CRC4
Wildcard TE121 Card 0 REC 53 0 0
zap show channels
Chan Extension Context Language MusicOnHold
pseudo default en default
/sbin/ztcfg -vvvv
Zaptel Configuration
======================
SPAN 1: CCS/HDB3 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: D-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: Clear channel (Default) (Slaves: 24)
Channel 25: Clear channel (Default) (Slaves: 25)
Channel 26: Clear channel (Default) (Slaves: 26)
Channel 27: Clear channel (Default) (Slaves: 27)
Channel 28: Clear channel (Default) (Slaves: 28)
Channel 29: Clear channel (Default) (Slaves: 29)
Channel 30: Clear channel (Default) (Slaves: 30)
Channel 31: Clear channel (Default) (Slaves: 31)
31 channels configured.

Posted:
Mon Jul 20, 2009 3:47 pm
by diyanat
did u make a cable as per the diagram ?
regards
Diyanat

Posted:
Mon Jul 20, 2009 4:13 pm
by tech.php
Yes, have changed the connectors as per your suggestions.
Also, had a word with NOC people, they say they are receiving LOOP(heck i don't know what that means).
Also, when i try to dial through a soft phone, i receive the following:
Executing Dial("SIP/901-b700db30", "Zap/g1/12127773456|55|tTo") in new stack
Jul 20 14:39:05 NOTICE[4083]: app_dial.c:1076 dial_exec_full: Unable to create channel of type 'Zap' (cause 0 - Unknown)
== Everyone is busy/congested at this time (1:0/0/1)
The extensions conf has been done as per the guide.

Posted:
Mon Jul 20, 2009 4:35 pm
by tech.php
Hi,
Still getting these errors:
Parsing '/etc/asterisk/zapata.conf': Found
Jul 20 15:04:42 WARNING[3829]: chan_zap.c:11062 setup_zap: Ignoring switchtype
Jul 20 15:04:42 WARNING[3829]: chan_zap.c:11062 setup_zap: Ignoring signalling
Jul 20 15:04:42 WARNING[3829]: chan_zap.c:11062 setup_zap: Ignoring overlapdial
Jul 20 15:04:42 ERROR[3829]: chan_zap.c:10493 setup_zap: Unable to reconfigure channel '1-15'
Jul 20 15:04:42 WARNING[3829]: chan_zap.c:11255 reload: Reload of chan_zap.so is unsuccessful!

Posted:
Mon Jul 20, 2009 4:44 pm
by diyanat
If its creating a loop, put back your old cable, remove CRC from zaptel
did u install libpri
reinstall it in this order
libpri, zaptel, asterisk
regards
Diyanat

Posted:
Mon Jul 20, 2009 4:47 pm
by diyanat
libpri-1.4.5
you seem to have install wrong version of libpri, install the correct version for asterisk 1.2

Posted:
Tue Jul 21, 2009 2:59 am
by tech.php
Hi Diyanat,
Thanks for your prompt replies, it helped me.
Now some strange messages are being displayed on asterisk console.
I'm pasting the output here:
Jul 21 01:19:45 WARNING[9442]: chan_zap.c:9151 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too.
Jul 21 01:19:46 WARNING[9442]: chan_zap.c:9151 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too.
Jul 21 01:19:47 WARNING[9442]: chan_zap.c:9151 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too.
Jul 21 01:19:48 WARNING[9442]: chan_zap.c:9151 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too.
When I issue the "zap show status" command, this is the output:
Description Alarms IRQ bpviol CRC4
Wildcard TE121 Card 0 OK 54 0 0
I tried to dial a number directly through softphone, this is the console output:
-- Executing Dial("SIP/901-b700ed90", "Zap/g1/12127773456|55|tTo") in new stack
Jul 21 01:19:58 NOTICE[9938]: app_dial.c:1076 dial_exec_full: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)
== Everyone is busy/congested at this time (1:0/1/0)

Posted:
Tue Jul 21, 2009 3:35 am
by diyanat
did u change signaling to pri_net in your zapata.conf ? it needs to be pri_cpe
post your zapata.conf again
Diyanat

Posted:
Tue Jul 21, 2009 3:50 am
by tech.php
Hi,
Output when I do "reload chap_zap.so"
*CLI> reload chan_zap.so
-- Reloading module 'chan_zap.so' (Zapata Telephony w/PRI)
== Parsing '/etc/asterisk/zapata.conf': Found
Jul 21 02:15:51 WARNING[9425]: chan_zap.c:11062 setup_zap: Ignoring switchtype
Jul 21 02:15:51 WARNING[9425]: chan_zap.c:11062 setup_zap: Ignoring priindication
Jul 21 02:15:51 WARNING[9425]: chan_zap.c:11062 setup_zap: Ignoring signalling
-- Reconfigured channel 1, PRI Signalling signalling
-- Reconfigured channel 2, PRI Signalling signalling
-- Reconfigured channel 3, PRI Signalling signalling
-- Reconfigured channel 4, PRI Signalling signalling
-- Reconfigured channel 5, PRI Signalling signalling
-- Reconfigured channel 6, PRI Signalling signalling
-- Reconfigured channel 7, PRI Signalling signalling
-- Reconfigured channel 8, PRI Signalling signalling
-- Reconfigured channel 9, PRI Signalling signalling
-- Reconfigured channel 10, PRI Signalling signalling
-- Reconfigured channel 11, PRI Signalling signalling
-- Reconfigured channel 12, PRI Signalling signalling
-- Reconfigured channel 13, PRI Signalling signalling
-- Reconfigured channel 14, PRI Signalling signalling
-- Reconfigured channel 15, PRI Signalling signalling
-- Reconfigured channel 17, PRI Signalling signalling
-- Reconfigured channel 18, PRI Signalling signalling
-- Reconfigured channel 19, PRI Signalling signalling
-- Reconfigured channel 20, PRI Signalling signalling
-- Reconfigured channel 21, PRI Signalling signalling
-- Reconfigured channel 22, PRI Signalling signalling
-- Reconfigured channel 23, PRI Signalling signalling
-- Reconfigured channel 24, PRI Signalling signalling
-- Reconfigured channel 25, PRI Signalling signalling
-- Reconfigured channel 26, PRI Signalling signalling
-- Reconfigured channel 27, PRI Signalling signalling
-- Reconfigured channel 28, PRI Signalling signalling
-- Reconfigured channel 29, PRI Signalling signalling
-- Reconfigured channel 30, PRI Signalling signalling
-- Reconfigured channel 31, PRI Signalling signalling
[zapata.conf]
[trunkgroups]
[channels]
language=en
context=default
switchtype=euroisdn
;pridialplan=unknown
priindication=outofband
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
callgroup=1
pickupgroup=1
immediate=no
echotraining=800
echocancel=yes
echocancelwhenbridged=no
relaxdtmf=yes
musiconhold=default
immediate=no
txgain=3.0
rxgain=6.0
;group=1
signalling=pri_cpe
;channel=>1-15,17-31
;overlapdial=yes
group = 1
channel => 1-15
channel => 17-31
[zaptel.conf]
span=1,1,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
loadzone=uk
defaultzone=uk
Thanks in advance

Posted:
Tue Jul 21, 2009 4:22 am
by diyanat
your zapata.conf looks ok, try rebooting your server and the PRI modem box and try making a call
as far as i know tata PRI needs a different cable then the straight one, try using the cable you made earlier
for more details check
http://74.125.153.132/search?q=cache:sh ... +PRI+cable
check with your provider as to what message they see on their side
regards
Diyanat

Posted:
Wed Jul 22, 2009 2:58 am
by tech.php
Hi,
Issue resolved. The problem was at provider's end only.
Appreciate the guidance and support.
Thanks.