Page 1 of 1

Connect more E1 trunk to vicidial

PostPosted: Wed Apr 18, 2012 11:26 am
by sherkan
Hi everybody
My vicidial setup is a Goautodial, simple HP Pavillon used as a server, T405P card PCI

I have installed everything correctly, the first E1 connection from MTN was well configured, inbound and outbound calls.
Now I m tryin to add a second E1 connection from another Telco, they have given me the setting which was actually the same as the previous E.
#PRI settings
span=1,1,0,ccs,hdb3,crc4
bchan=1-15,17-31
dchan=16

for both E1s to work on my system, here are my zaptel and zapata configuration:
ZAPTEL.CONF

#MTN E1
span=1,1,0,ccs,hdb3,crc4
bchan=1-15
dchan=16
bchan=17-31

#Tigo E1
span=2,1,0,ccs,hdb3,crc4
bchan=32-46
dchan=47
bchan=48-62

ZAPATA.CONF(I have been using these settings for MTN, It was okay)

[channels]
context=trunkinbound
switchtype=euroisdn
;pridialplan=unknown
;prilocaldialplan=unknown
;overlapdial=yes
signalling=pri_cpe
;rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
;transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=no
echocancelwhenbridged=no
rxgain=0.0
txgain=0.0
group=2
;callgroup=1
;pickupgroup=1
immediate=no

#PRI 1
channel => 1-15
channel => 17-31

#PRI 2
channel => 32-46
channel => 48-62
________________________

I have been trying other ways to it, but the 2nd spanis still down.
when i PRI SHOW SPANS i get:
PRI span 1/0: Provisioned, Up, Active
PRI span 2/0: Provisioned, In Alarm, Down, Active


Any help would be much appreciated

Re: Connect more E1 trunk to vicidial

PostPosted: Wed Apr 18, 2012 8:49 pm
by williamconley
Gardo is excellent at T1/E1 configuration (lots of experience). As is Kumba, but this is a GoAutoDial installation, yes? Gardos domain.

Have you tried "switching" them? IE: Since you say the configuration is the same ... it would stand to reason that you could switch the connections and the "live" one would die and the dead one would wake up ... at least that would demonstrate that the new one WORKS and that you have a configuration issue or a dead PCI port as opposed to a possible dead inbound T1 (which cannot be fixed by configuration changes ...).

Also: I moved this to support as it is obviously not a general discussion. :)

Re: Connect more E1 trunk to vicidial

PostPosted: Thu Apr 19, 2012 1:04 am
by striker
make sure physical line is up on span 2
what is the output of
zap show status or (zaptel show status)

Re: Connect more E1 trunk to vicidial

PostPosted: Mon Apr 23, 2012 1:42 am
by sherkan
Thanks, sorry i figured it out later... it was a physical line issues as u mentionned, thanks
I had build a E1 crossover cable, though I should have used a straight E1 cable , with only 4 pins... after few googling i got the solution

Re: Connect more E1 trunk to vicidial

PostPosted: Mon Apr 23, 2012 10:22 am
by sherkan
Physical problem was fixed, all PRI are now ACTIVE and UP... but left with a small issue, and i guess it's a very small problem, here's the problem:
the new E1 is connected, I did exactly as I did on the first E1, add new DID and set it to CALL_MENU, then instead of hearing the Welcome message I set on the IVR, it's silent
Check the CLI i get:


*CLI> -- Accepting call from '0722537919' to '4455' on channel 0/1, span 2
-- Executing [4455@trunkinbound:1] AGI("Zap/32-1", "agi-DID_route.agi") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
-- AGI Script agi-DID_route.agi completed, returning 0
-- Executing [99909*1*@default:1] Answer("Zap/32-1", "") in new stack
-- Executing [99909*1*@default:2] AGI("Zap/32-1", "agi-VDAD_ALL_inbound.agi") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
-- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
-- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Apr 23 14:11:46] WARNING[27075]: res_musiconhold.c:660 get_mohbyname: Music on Hold class 'default' not found
[Apr 23 14:11:46] WARNING[27075]: res_musiconhold.c:660 get_mohbyname: Music on Hold class 'default' not found
-- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
-- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
-- Playing 'generic_hold' (escape_digits=) (sample_offset 0)
[Apr 23 14:11:51] WARNING[27075]: res_musiconhold.c:660 get_mohbyname: Music on Hold class 'default' not found
[Apr 23 14:11:51] WARNING[27075]: res_musiconhold.c:660 get_mohbyname: Music on Hold class 'default' not found
-- Channel 0/1, span 2 got hangup request, cause 31
== Spawn extension (default, 99909*1*, 2) exited non-zero on 'Zap/32-1'
-- Executing [h@default:1] DeadAGI("Zap/32-1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----31---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
-- Hungup 'Zap/32-1'
_____________

Wondering why that call is not redirected to the CALL_MENU! I think the only thing would have been to Add the new IVR, redirect to the CALL_MENU! Am I skipping something?

Re: Connect more E1 trunk to vicidial

PostPosted: Mon Apr 23, 2012 10:36 am
by sherkan
Sorry it's when i call the new number(E1) that I get the above CLI... meaning it's physically correct, the problem resides on the configuration that I tried to do, but still failing

Thanks!!

Re: Connect more E1 trunk to vicidial

PostPosted: Wed Apr 25, 2012 1:56 am
by sherkan
Hey I got the reason why it could'nt work
For this new E1, I was using all the 10 digits the TELCO gave me, that's why it was not working( they haven't told me i should have used only the last 4 digits)
I tried it this morning, it was okay, NOW both E1 goes to the IVR, and agents can respond... :)