PRI trunk to trunk outbound calling

[BrokenBear]

Hello,

I have a VoIP system tied to a Nortel 81c via PRI TIE circuit. I am trying to get outbound calls from the VoIP system to go out the Nortel PBX PRIs.
All calling from VoIP system to Nortel extensions work fine. (See below)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

DCH 10 UIPE_IMSG CC_SETUP_IND REF 00000082 CH 50 13 TOD 9:59:30
CALLED #:7733 NUM PLAN: E164
CALLING #:978XXX7446 NUM PLAN: E164

DCH 10 UIPE_OMSG CC_PROCEED_REQ REF 00008082 CH 50 13 TOD 9:59:30

DCH 10 UIPE_OMSG CC_ALERT_REQ REF 00008082 CH 50 13 TOD 9:59:30
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 10 UIPE_OMSG CC_SETUP_RESP REF 00008082 CH 50 13 TOD 9:59:36
PROGRESS: TERMINATING END IS NOT ISDN

DCH 10 UIPE_IMSG CC_SETUPCOMP_IND REF 00000082 CH 50 13 TOD 9:59:36

DCH 10 UIPE_OMSG CC_DISC_REQ REF 00008082 CH 50 13 TOD 9:59:38
CAUSE: #16 - NORMAL CALL CLEARING

DCH 10 UIPE_IMSG CC_RELEASE_IND REF 00000082 CH 50 13 TOD 9:59:38
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

ACTIVE TN 004 1 04 08
ORIG 050 17 DID RMBR 4 17
TERM DN 7733
TDTN 48 SLOT 14 PTY SLOT 14
DIAL DN 7733
MAIN_PM RING AUX_PM
TALKSLOT ORIG 14 TERM 14 JUNCTOR ORIG6 TERM0
QUEU RING
CALL ID 0 3166


---- ISDN PRA CALL (ORIG) ----
CALL REF # = 386
BEARER CAP = VOICE
HLC =
CALL STATE = 7 CALL RCV
CALLING NO = 978XXX7446 <-- My VoIP phone
CALLED NO = 7733 <--- Nortel phone

PDCA 1 PAD 0 0 PCML MU MU
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

I had the VoIP system admin set up an access code that inserted the 91 in front of the outbound number so it would go trunk to trunk outbound. However, it only recognizes the last 4 digits of the whole number and terminates the call to either the attendant, because the number might not be dialable, or it terminates to an extension that exists. (See below)
I'm trying to call my cellphone 91978XXX7720. All the digits are being sent, but it's terminating on extension 7720.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
DCH 10 UIPE_IMSG CC_SETUP_IND REF 00000202 CH 50 18 TOD 10:12:40
CALLED #:91978XXX7720 NUM PLAN: E164
CALLING #:978XXX7446 NUM PLAN: E164

DCH 10 UIPE_OMSG CC_PROCEED_REQ REF 00008202 CH 50 18 TOD 10:12:40

DCH 10 UIPE_OMSG CC_ALERT_REQ REF 00008202 CH 50 18 TOD 10:12:40
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 10 UIPE_IMSG CC_DISC_IND REF 00000202 CH 50 18 TOD 10:12:46
CAUSE: #16 - NORMAL CALL CLEARING

DCH 10 UIPE_OMSG CC_RELEASE_REQ REF 00008202 CH 50 18 TOD 10:12:46

DCH 10 UIPE_IMSG CC_RELEASE_CONF REF 00000202 CH 50 18 TOD 10:12:46

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
ACTIVE TN 004 1 01 12
ORIG 050 16 DID RMBR 4 16
TERM DN 7720
TDTN 48 SLOT 26 PTY SLOT 27
DIAL DN 7720
MAIN_PM RING AUX_PM
TALKSLOT ORIG 27 TERM 25 JUNCTOR ORIG5 TERM7
QUEU RING
CALL ID 0 583


---- ISDN PRA CALL (ORIG) ----
CALL REF # = 770
BEARER CAP = VOICE
HLC =
CALL STATE = 7 CALL RCV
CALLING NO = 9784617446
CALLED NO = 91978XXX7720

PDCA 1 PAD 0 0 PCML MU MU

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

I hope I clearly stated what is happening. I will elaborate upon request.

Thanks to you all!

 

[nhphoneguy]

Is the other sytem a Nortel box? What type of signalling and dialing plan are you using. If the call comes across as CDP and you have the digits set to 4, that might explain it.

Also, make sure that the NPA/NXX is not mapped as LDID, that would have the same effect as turning an outbound call into an internal 4 digit call.

other stuff-

Assuming 9 is your AC1 for BARS/NARS, make sure the class of service on the incoming tie lines from your Voip system allows calling out - NCOS and CLS, or if 9 is the actual trunk access code, check TGAR/TARG; Also, in the CDB- NET section, make sure DITI is yes. FTOP may also influence this if you've got trunk barring set up.
Sorry for the rambling, alot of different things could cause this.

 

[BrokenBear]

Thanks for the response nhphoneguy.

The other system is an Asterisk based system on a linux box.
It is connected to a Cantata IMG, converted to an MSP, so the routing and circuits are configured in the Asterisk-based software.

The Nortel is connected to the Cantata via a PRI with NI2 signaling. I spoke with my Nortel vendor and he says that the called party numbering plan needs to be NATIONAL instead of E164:

DCH 10 UIPE_IMSG CC_SETUP_IND REF 00000202 CH 50 18 TOD 10:12:40
CALLED #:91978XXX7720 NUM PLAN: E164 <== Needs to be NATIONAL
CALLING #:978XXX7446 NUM PLAN: E164


I tried to rout 1978 NPA to copper as a test instead of trying to send it out PRI and that didn't work either.

9 is the AC1 for BARS/NARS in the Nortel.


Should I try different signaling like Lucent 5ESS?

 

[nhphoneguy]

Im not sure I agree with explanation of the numbering plan-
You can have e164, but the type of call needs to be npa-

That needs to be sent from the Asterisk box.

Here is a clip from a call on one of my switches:

CALLING NO = 603xxxxxxx NUM_PLAN:E164 TON:NATIONAL ESN:NPA
CALLED NO = 91xxxxxxxxxx NUM_PLAN:E164 TON:NATIONAL ESN:NPA

Check the NXX of your cell to make sure there is no LDID set up. Also could you post the RDB of the route connected to the voip box?

 

[BrokenBear]

Ok. So the E164 is fine, we just need the NATIONAL/NPA to be delivered to the Nortel?

Here is the RDB:

TYPE RDB
CUST 00
ROUT 4
DES ENTICE_TIE
TKTP DID
SAT NO
RCLS INT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 6
SBN NO
NCNA YES
NCRD YES
CHTY BCH
CPFXS NO
HNTN
HLCL
DAPC NO
BCOT 0
INTC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 6600
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 2 *
NDNO 2
DEXT NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DRNG NO
CDR YES
INC YES
LAST YES


PAGE 002

QREC NO
OAL YES
AIA YES
OAN YES
OPD NO
NATL YES
MUS YES
MRT 20
RACD NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

Thanks again nhphoneguy!

 

[BrokenBear]

This is how the trunks are programmed:

TN 050 01
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 6
RTMB 4 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DIP CND WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 21 DEC 2006

 

[nhphoneguy]

Assuming NCOS 6 allows a call to go out, the route and trunk look ok.
I guess I'm confused at what is manipulating the last 4 digits to terminate locally. Does this happen to any number, or just your cell number?

 

[BrokenBear]

Any number. It just so happens that the last 4 digits of my cell fall into our DID dialplan. Basically, whatever number you dial, the PBX only looks at the last 4 digits. If the number isn't programmed in the PBX, the call will go to the attendant.

 

[nhphoneguy]

I guess at this point I would work on the other end sending National for a type of number....

 

[terryjames]

I would check your TGAR which is set to 1.
Aslo you have in the RBD ICIS set to YES?
I would ask them to prefix a call to you using a RDB acess code instead of 91npanxx-xxxx to see if it works?
Fine the less restricted number in your system such as
411 or 611 where there is no NCOS or TGAR applied.

 

[PareshTC]

I would suggest you configure the TIE as a TIE and not a DID. Due tot eh DID config, the system is thinking the incoming digits are for a DID call, and based on your LDN string length, it is selecting only the last 4 digits for processing.