Very strange PRI behavior

I have a dual port E1/T1 board from Digium (something 2 years old, not very new). When I make calls to the first port, everything is ok, but when I make calls to the second port, Asterisk only gives me the PROCEEDING message and the the CONNECTED message, although it shows that the channel is connected and everything (on Asterisk’s side) is ok. I tried switching between pri_net and pri_cpe and tried many configurations - nothing works.

Any idea what am I doing wrong?

zaptel.conf:

span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 span=2,2,0,ccs,hdb3,crc4 bchan=32-46,48-62 dchan=47 loadzone = de defaultzone = de

zapata.conf:

[code][channels]
language=de
context=from-zaptel
switchtype = euroisdn
pridialplan=national
echocancel=yes
immediate=no
overlapdial=no

; First PRI
signalling=pri_cpe
context=from-dialogic
channel => 1-15,17-31
musiconhold=default
resetinterval=never
immediate=no

; Second PRI
group=1
context=from-oms
signalling=pri_net
channel => 32-46,48-62
musiconhold=default
resetinterval=never
immediate=no[/code]

Hi

your zapata.conf if a bit adrift.

try

[channels]
language=de
context=from-zaptel
switchtype = euroisdn
pridialplan=unknown
prilocaldialplan=unknown
echocancel=yes
immediate=no
overlapdial=no
resetinterval=never
musiconhold=default

; First PRI to a CO
group=1
signalling=pri_cpe
context=from-dialogic
channel => 1-15,17-31

; Second PRI to a PBX
group=2
context=from-oms
signalling=pri_net
channel => 32-46,48-62

I get the same behavior. One thing I forgot to mention - If I perform an Answer() command in the dialplan, I get the CONNECTED event and immediately after a CALLDROPED event.

Hi

What are you connecting to?

is it as I assumed
cct 1 >>>> PSTN
cct 2 >>>> Another PBX

Ian

Both trunks are connected to Dialogic hardware. I had the same problem with an Aculab board, but on the Aculab board I couldn’t debug anything. I didn’t test it yet with a PSTN connection, but since the first trunk works properly there shouldn’t be any problem with the other trunk.

Ian

If the first works and they are connected to ports that are configured the same on the dialogic then they both should be pri_cpe

to be honest you could just do

[channels]
language=de
context=from-zaptel
switchtype = euroisdn
pridialplan=unknown
prilocaldialplan=unknown
echocancel=yes
immediate=no
overlapdial=no
resetinterval=never
musiconhold=default

; First PRI to a CO
group=1
signalling=pri_cpe
context=from-dialogic
channel => 1-15,17-31
context=from-oms
channel => 32-46,48-62

Like I wrote before, the problem exists whether I configure it as cpe or net.

With Pri_net and Pri_cpe You have to have it correct, you cannot just set it to what you want.

If both ports on the dialogic board are configured the same. then both interfaces on the digium card must be as well.

what is the isdn cause code when the call fails.

are the jumpers correct on the card ? and what does zttool say ?

Ian

The call doesn’t fail, it doesn’t return a CONNECT signal. I don’t know how to use zttool, how should I run it?

Hi

Ok im getting lost now.

to run zttool type zttool

but all the same how is the dialogic card configured?

simple test is swap the leads and see if the problem moves ?

as I said if the dialogic ports are the same they MUST be the same on the digium.

Ian

It seems the problem was in the dialplan. I didn’t know I have to first issue an Answer command for incoming calls on a PRI.

It all depends on what you are doing. but if for example it was an ivr then yes you do

Ian