Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Incoming PRI Issue

Status
Not open for further replies.

PHANDL

Technical User
Dec 11, 2012
26
US
Hello everyone, I am having an issue with out Nortel 81c switch that has been ongoing for a few months now. The issue is with one of our DSN PRI trunks. When there is an incoming call on DSN it works for all extensions in the range of 2000-2999 but when an incoming call is made to extension 1000-1999 the calls are being rejected. I monitored the D Channel and this is the message I am receiving when an incoming call is made:

DCH 40 UIPE_IMSG CC_SETUP_IND REF 000008E2 TOD 13:10:26 CK 7927D8D1
CALLED #:1*** NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:2352*** NUM PLAN: UNKNOWN TON: UNKNOWN
PRECLEVEL: #4 - RTN
DOMAIN: 000000
DCH 40 UIPE_IMSG CC_DISC_IND REF 000005BA CH 40 23 TOD 13:10:26 CK 7927D9B9
CAUSE: #21 - CALL REJECTED

DCH 40 UIPE_IMSG CC_RELEASE_CONF REF 000005BA CH 40 23 TOD 13:10:26 7927DA
12

I have been working with our provider and the 1000s and 2000s are being routed the same. I am wondering if there is an issue with how our switch is translating 1000 extensions. Any help would be greatly appreciated.
 
Can you post the DCH messages for a call to a 2xxx number?
Also maybe check whether there is an IDC table applied to trunk route.
 
Here is the message for 2xxx

DCH 40 UIPE_IMSG CC_SETUP_IND REF 000008E4 TOD 13:14:32 CK 792F56E2
CALLED #:2*** NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:2352*** NUM PLAN: UNKNOWN TON: UNKNOWN
PRECLEVEL: #4 - RTN
DOMAIN: 000000
DCH 40 UIPE_MSG CC_ALERT_IND REF 000005BF CH 40 23 TOD 13:14:32 CK 792F57F6
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
 
Only have the incoming messages on, all outgoing calls are working fine.
 
Every call has dch messages going both ways. You need the outgoing messages to see what message your switch is sending to the originator. That will give you a clue why the call was rejected.
 
are you using an IDC table? If yes, are the IDC entries for 1 in the same entries as 2?
If no, show out going message to see why the call is being rejected.
 
Going to turn outgoing on also wil post once it is done, thanks.
 
Here is the outgoing message:


DCH 40 UIPE_OMSG CC_SETUP_REQ REF 00000A52 CH 40 23 TOD 11:59:49 CK 086F8D16
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:2352621 NUM PLAN: PRIVATE TON: UNKNOWN
CALLED #:2351002 NUM PLAN: PRIVATE TON: UNKNOWN
PRECLEVEL: #4 - RTN
DOMAIN: 000000
DCH 40 UIPE_OMSG CC_REKECT_REQ REF 000089C7 CH 40 17 TOD 11:59:49 CK 086F8EF7

CAUSE: #21 - CALL REJECTED

DCH 40 UIPE_OMSG CC_RELEASE_REQ REF 00000A52 CH 40 23 TOD 11:59:49 CK 086F8FB8
 
How do I look at the IDC table to tell whether or not they are in the same entires?
 
Could this be caused by something in the RDB?
 
As John says most likely IDC if its assigned prt your RDB in LD 21 see if IDC set YES and if so what tables are assigned day/night (active one has * against it). Then print that IDC in LD 49

 
when i prt RDB there is no IDC shown so I am assuming I do not have IDC tables setup here.
 
Here is what the RDB of the PRI in question looks like, I noticed ISDN is set to yes and there is no DSEL option.

TYPE RDB
CUST 00
ROUT 0
DES DSN_NI2_PRI
TKTP ATVN
NPID_TBL_NUM 0
ESN NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA​
IFC NI2​
SBN NO​
PNI 00000​
NCNA NO​
NCRD NO​
CHTY BCH​
INAC YES​
CP FXS YES​
CPUB OFF​
DAPC NO​
BCOT 0​
INCT NO​
PTYP PRI
DCDR NO
ICOG IAO
PREM YES
ATVR NO
SRCH LIN
TRMB YES
STEP
ACOD 8
TCPP NO
TARG 01 02 03
CLEN 1
BILN NO
OABS
IABS 0
INST
SIGO STD
MFC NO
ICIS YES
OGIS YES


 
The outgoing msg you provided is not for your rejected call.

DCH 40 UIPE_OMSG CC_REKECT_REQ REF 000089C7 CH 40 17 TOD 11:59:49 CK 086F8EF7

CAUSE: #21 - CALL REJECTED

DCH 40 UIPE_OMSG CC_RELEASE_REQ REF 00000A52 CH 40 23 TOD 11:59:49 CK 086F8FB8
 
Yeah, I used one from a new call. My terminal is a standalone so I have to type the messages out. Its the same outgoing message that comes up for each call.
 
You need to turn on both MSGI and MSGO on DCH then place you inbound call to 1xxx and to 2xxx then post
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top