Asterisk to NEC SV8100 E1 (PRI) issue?

Status
Not open for further replies.

Bob1

Forum User
Joined
Nov 4, 2007
Messages
2,400
Reaction score
1
Been a long time since I posted for assistance but I am a little perplexed by this issue.

Just throwing this out there in case someone has come across the issue.

We have a client who has an NEC SV8100 working on E1 without any issues.

We have implemented an Asterisk device with two E1 ports, with the purpose of migrating to Asterisk over a period of time. We cannot get calls from the Asterisk unit to he SV8100 nor from the SV8100 to Asterisk. Using the Asterisk device to call out via the same Carrier E1 and call in, no issues.

We have done this time and time again with no issues but not with a NEC SV8100. Yes we have the correct X-Over cables/ replaced them / confirmed correct CPE/Net config. We even took this unit to another system (with the same carrier - same E1 termination) and the system works with calls in and out.

We have done debugs, PRI Debugs (including comparisons) and the only part we are seeing is the following lines from an intense PRI debug (this is a call from our Asterisk device to the SV8100 E1)

T303 timed out. cref:32773
q931.c:5925 t303_expiry: Call 32773 enters state 0 (Null). Hold state: Idle
Fake clearing. cref:32773
q931.c:9219 pri_internal_clear: alive 1, hangupack 1
-- Span 1: Channel 0/31 got hangup, cause 18

So really asking if anyone has done some work with the NEC SV8100 who may know the issue that we are facing.

Any thoughts would be appreciated...

Regards

Bob
 
Hi Bob

That could be a dial plan issue on the NEC unit, check what is in there for both in and out
 
Hi Bob,
What are you seeing in your pri intense debug when originating a call from the NEC side to Asterisk/Elastix? Are you able to complete a call going in that direction? That could give you some indication of how the NEC is presenting it's numbers to Asterisk and of course confirm if the trunk between the two is nailed-up properly.

I have a feeling this is one of those issues that may need to be addressed by tweaking "pridialplan=" and/or "prilocaldialplan="
 
Status
Not open for further replies.

Forum statistics

Threads
111,858
Messages
589,427
Members
164,698
Latest member
RRusev