DID's going to Attendant 4

[jlk53]

There is a CS1000 with a PRI from Carrier A that is working fine. It is set up as a TIE. The carrier is sending 4 digits. I installed a second PRI from carrier B. I have it set up as a DID. I can make outbound calls OK but when calling in on a DID it goes to the attendant. I assume that this means that the PBX does not know where to send the call so it defaults to the attendant. I turned on DCH messaging and this is what I see on my PRI DCH 10.

DCH 10 UIPE_IMSG CC_SETUP_IND REF 00000E80 CH 1 1 TOD 18:01:36 CK D22E861E
CALLED #:4059 NUM PLAN: UNKNOWN TON: UNKNOWN
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:2426774511 NUM PLAN: E164 TON: NATL

DCH 10 UIPE_IMSG CC_FAC_IND REF 00000E80 CH 1 1 TOD 18:01:36 CK D22E86FD

DCH 10 UIPE_IMSG CC_DISC_IND REF 00000E80 CH 1 1 TOD 18:02:16 CK D22FBC4D
CAUSE: #16 - NORMAL CALL CLEARING

DCH 10 UIPE_IMSG CC_RELEASE_CONF REF 00000E80 CH 1 1 TOD 18:02:16 CK D22FBCF6

CAUSE: #16 - NORMAL CALL CLEARING

This is what I see on Carrier A's PRI(DCH 3):

DCH 3 IMSG SETUP REF 00008D8E CH 3 1 TOD 18:03:58
PROGRESS: CALL IS NOT END TO END ISDN
CALLING #:2426764731 NUM PLAN: E164/NATIONAL / NPA
CALLED #:7067 NUM PLAN: E164/SUBSCRIBER (NXX)/LOCL

DCH 3 IMSG CONN ACK REF 00008D8E CH 3 1 TOD 18:04:18

DCH 3 IMSG STATUS REF 00008D8E CH 3 1 TOD 18:04:18
CAUSE :USER INFO DISCARDED
STATE : CALL ACTIVE STATE

DCH 3 IMSG DISC REF 00008D8E CH 3 1 TOD 18:04:22
CAUSE :NORMAL CALL CLEARING

DCH 3 IMSG REL COMP REF 00008D8E CH 3 1 TOD 18:04:22

I can see differences but not sure what to look at. Can anyone shed some light for me.

 

[GHTROUT]

Any dial repeating trunk that comes in from the outside should be DID. This because TIE is inherently unrestricted - it assumes the calls is between your own sites. If you ever study the restrictions matrix, you will see this... I know this is not the solution to today's issue - it only means that one day you should change your Carrier A to be DID. DID and TIE are functionally the same - the exception is restrictions.

But, the first thing I would do is compare your Route Data Blocks. For example, make sure ICOG=IAO on the DID Route. Then compare TN 1-1 to TN 3-1





~~
Gene at www.GHTROUT.com

 

[Splic3d]

Do you have a LDN key programmed on the console with a 4 digit DN. I usually use one of the DID numbers in the DID range. It needs to be programmed even if you don't have a physical console hooked up.

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[GHTROUT]

LOL, that is a great point Splic3d - good catch! It won't work without an LDN the same length as your DNs

~~
Gene at www.GHTROUT.com

 

[Splic3d]

Learned that one the hard way. LOL

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[jlk53]

Thanks for the quick replies. The LDN has a 4 digit DID in LDN0. Here is a TN from my DID route. Should the STRI/STRO be there. It is not in the channels for the TIE PRI.
TN 001 01
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 1 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DTCR NO
AACR NO
DATE 9 SEP 2013

Here is my RDB:
TYPE RDB
CUST 00
DMOD
ROUT 1
DES CABLE
TKTP DID
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC D100
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 8
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
MFC NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GTO 896
GTI 896
SFB 3


PAGE 002

NBS 2048
NBL 4096

IENB 5
VSS 0
VGD 6
DTD NO
SCDT NO
2 DT NO
DDO NO
DRNG NO
CDR NO
CCO NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS NO
PANS YES
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
OHQ NO
OHQT 00
TTBL 0
ATAN NO
PLEV 2
OPR NO
PRDL NO
EOS NO
DNSZ 0
RCAL NO
MCTS NO
ALRM NO
BTT 30
ACKW NO
ART 0
TIDY 8 1
SGRP 0
CCBA NO
ARDN NO
AACR NO

Any help is greatly appreciated

 

[Splic3d]

Do you Ext's match the DID dns ?

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[GHTROUT]

Hmm... You could try STRI IMM and STRO IMM (instead of OWK)

Are the DID calls just going straight to phones? Not over other trunks, like to another system? If there is another system at play, the NCOS of the TN 1-1 and TN 3-1 should be compared.

As another last resort, build a new IDC Table (LD49) with nothing in it. Then set the Route's DCNO and NDNO to that IDC table.





~~
Gene at www.GHTROUT.com

 

[jlk53]

Update: I cannot explain it but I removed everything, channels,RDB,and DCH. I then rebuilt them and the DID's worked. Go figure.

 

[Splic3d]

Been there done that, as long as you got it.

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx