Connect Trixbox to NEC NEAX IPS 2000

Yes I have integrated my NEC systems to Trixbox via PRI with no problems

Nobody is going to help you with the way you are asking the questions.

The other user already told you they have a PRI up between the machines. This assumes you know how to configure a trunk in both machines. If you don't you need to learn.

If you have a SIP license for the NEC you can also trunk directly with IP.

Hi ,

I'm trying to integrate my asterisk (trixbox) with our NEC 2400 EMS... (much older I beleive), but the concept should be the same
I linked them both with a PRI. and worked with our integrator on the NEC side to get this up and running

So we have
AST tribox (TE121B) NEC (PA-24DTG)

so far we are able to make a call form the NEC to a sip extension on the Ast*, however the extension rings and then hangs up right away.
Digging into the PRI logs, it seems to be a PRI issue.

Looking at my debug trace below I found the following:
Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: Private network serving the local user (1)

However I'm no ISDN Q931 signaling export and the various google I did so far did not get me very far.

Note:
# Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER) B8ZS/ESF ClockSource
span=1,1,0,esf,b8zs
# termtype: te
bchan=1-23
dchan=24
echocanceller=mg2,1-23

; Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER) B8ZS/ESF ClockSource
group=0,11
context=from-internal
switchtype = national
signalling = pri_net
channel => 1-23
context = default
group = 63

Anyone's help will be much appreciated.

Thanks

-- Making new call for cr 111
-- Processing Q.931 Call Setup
-- Processing IE 4 (cs0, Bearer Capability)
-- Processing IE 24 (cs0, Channel Identification)
-- Processing IE 30 (cs0, Progress Indicator)
-- Processing IE 112 (cs0, Called Party Number)
q931.c:3551 q931_receive: call 111 on channel 1 enters state 6 (Call Present)
q931.c:2816 q931_call_proceeding: call 111 on channel 1 enters state 9 (Incoming Call Proceeding)
> Protocol Discriminator: Q.931 (8) len=10
> Call Ref: len= 2 (reference 111/0x6F) (Terminator)
> Message type: CALL PROCEEDING (2)
> [18 03 a9 83 81]
> Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0
> ChanSel: As indicated in following octets
> Ext: 1 Coding: 0 Number Specified Channel Type: 3
> Ext: 1 Channel: 1 ]

-- Processing IE 8 (cs0, Cause)
-- Processing IE 20 (cs0, Call State)
q931.c:2844 q931_alerting: call 111 on channel 1 enters state 7 (Call Received)
> Protocol Discriminator: Q.931 (8) len=9
> Call Ref: len= 2 (reference 111/0x6F) (Terminator)
> Message type: ALERTING (1)
> [1e 02 81 88]
> Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
> Ext: 1 Progress Description: Inband information or appropriate pattern now available. (8) ]
-- Processing IE 8 (cs0, Cause)
q931.c:3801 q931_receive: call 111 on channel 1 enters state 0 (Null)
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Release Request
> Protocol Discriminator: Q.931 (8) len=9
> Call Ref: len= 2 (reference 111/0x6F) (Terminator)
> Message type: RELEASE COMPLETE (90)
> [08 02 81 e0]
> Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: Private network serving the local user (1)
> Ext: 1 Cause: Mandatory information element is missing (96), class = Protocol Error (e.g. unknown message) (6) ]
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null
NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null