SPN 011 - Opt11C to DMS-100 NI-2 2

[ba7389]

There are several similar posts on this subject, but...Is anyone with an Option 11 C currently running an NI-2 PRI into a DMS-100 (more specifically, with Global Crossing)?

This is a LEC PRI configured for NI-2 call-by-call, no mins or maxes (all channels both ways). Our current LEC interface is also NI-2, but into a 5E. We are preparing to cutover to this DMS-100, and have no swing equipment on the PBX side. During testing yesterday, all call types other than international worked fine. I turned on D-Channel messaging in the PBX and found that we are not sending the 011 international access code toward the DMS. The carrier’s engineer advised me that they needed to see the 011. I created a DMI to insert 011, pointed the PBX route list index toward that entry, and made a test call. The 011 was sent toward the DMS, but the call did not complete. When the call dropped, the channel locked out, and the PBX generated a restart message toward the CO that the CO did not acknowledge. Repeated attempts locked out additional channels, and only disabling the D-Channel and the loop would allow the channels to be reset.

The engineer is asking that we move to a DMS interface on the PRI, which we will not be doing for a number of reasons, including interface with BRI-based video equipment on the station side of the PBX. This would be a last fallback position, as we have worked this way before. We have also worked NI-2 into a DMS previously, so would really like to just figure this out.

DCH 6 UIPE_OMSG CC_SETUP_REQ REF 000023C6 CH 1 23 TOD 7:15:22
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:3019442055 NUM PLAN: E164 TON: NATL
CALLED #:17036066282 NUM PLAN: E164 TON: NATL

DCH 6 UIPE_IMSG CC_PROCEED_IND REF 000023C6 CH 1 23 TOD 7:15:24

DCH 6 UIPE_IMSG CC_PROGRESS_IND REF 000023C6 CH 1 23 TOD 7:15:24
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 6 UIPE_IMSG CC_SETUP_CONF REF 000023C6 CH 1 23 TOD 7:15:34

DCH 6 UIPE_OMSG CC_DISC_REQ REF 000023C6 CH 1 23 TOD 7:15:38
CAUSE: #16 - NORMAL CALL CLEARING

DCH 6 UIPE_IMSG CC_RELEASE_IND REF 000023C6 CH 1 23 TOD 7:15:38

DCH 6 UIPE_OMSG CC_RELEASE_RESP REF 000023C6 CH 1 23 TOD 7:15:38

DCH 6 UIPE_OMSG CC_SETUP_REQ REF 000023C7 CH 1 23 TOD 7:15:58
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:2055 NUM PLAN: PRIVATE TON: UNKNOWN
CALLED #:011442085103010 NUM PLAN: PRIVATE TON: INTL

DCH 6 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 7:16:10
TYPE: INDICATED CHANNEL

For digit manipulation, I tried various call types, but all gave same symptom – call does not go to reorder, it just times out after no response from CO. Someone suggested that the call type be configured as NCHG, which I did not try, but think that is going to send an INTL, similar to below, so don’t think that is the answer.

This is D-Channel message with NCHG option set on DMI on a different switch at same software release.

DCH 6 UIPE_OMSG CC_SETUP_REQ REF 00001741 CH 1 23 TOD 6:56:40
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:3016344646 NUM PLAN: E164 TON: INTL
CALLED #:011442085103010 NUM PLAN: E164 TON: INTL

Appreciate any ideas.

Thanks,

Bruce

 

[curtismo]

Just a thought...looking at your test International call that failed, your calling number is in an odd (2055) and marked private. Have you checked that you don't have a CLID issue that the DMS is more sensitive about?

Reason I asked is that I had a user once that couldn't make local calls out our PRI (LD didn't go out a PRI at the time). Found that this person I screwed up their custom CLID table entry and sent 8 digits rather than 7 and the switch would reject it. This was on NI-2 but to a GTD5.

 

[Fleisch]

I had maybe a similar problem with a Verizon Business PRI a couple of years ago. Although the implementation manager swore up and down the PRI was set to handle INTL calls, there was a some restriction table on their end that needed to have our DID number range added to.

The only way I ever got this resolved was to request a head to head test with one of their network engineers to have him verify what digits I was sending him and where the fail point was.

Once I had him confirm I was sending 011 to their end then. I went back to the implementation manager- and "oh yeah-there it is"
--------------------------------

Here is also a dch config from the original circuit I had with sbc Pac Bell that had no issues processing INTL calls

ADAN DCH 4
CTYP DCHI
CARD 08
PORT 1
DES
USR PRI
DCHL 8
OTBF 127
DRAT 64KC
CLOK EXT
IFC D100
SIDE USR
CNEG 1
RLS ID 36
RCAP
MBGA NO
OVLR NO
OVLS NO
T23 20
T200 3
T203 10
N200 3
N201 260
K 7

 

[hawks]

The only problem with the above config is if you set
IFC = D100

Then your are not using the NI-2 protocol.

 

[ba7389]

Thanks to both for feedback.

On the extension number only being shown as the CLID - That concerns me for other reasons, but other calls from other locations that displayed the full 10-digit caller ID still had same symptom. That particular set has three MCR appearances of the same line, and sends only the extension number on buttons 1 or 2 if there is a call on hold on button 1. Think I probably do have something not right in the CLID reference.

On the possibility of needing to register the DID station ranges to allow international - I have had that trouble with Verizon local with switched LD with AT&T. This is a little different in that international calls to not appear to be blocked - the calls just time out and relese the channel. Will bring up that possibility with Global Crossing though.

 

[ba7389]

This is the D Channel, as currently configured. Note that I do not have a RLS ID specified. Since this is the channel working NI-2 into the 5E currently, could it be that I need to specify a release number for the DMS??

ADAN DCH 6
CTYP MSDL
CARD 01
PORT 1
DES GCX_DCH
USR PRI
DCHL 1
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
MBGA NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSERV NO

 

[Fleisch]

This is a copy of my current working dch but I think it is a 5E at the far end.

ADAN PRIM DCH 5
BDCH 6
CTYP MSDL
CARD 01
PORT 1
DES VERIZON
USR PRI
DCHL 1
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID 1
RCAP COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO

 

[johnpoole]

in your area, cbc is the same as isa? so you built a isa master route with the min max =to the number of channels..

if the ckts are green and the d's are estb then the route config would be the next step in the puzzle..

here's a isa master, NO members ever

CUST 0
ROUT 35

TYPE RDB
CUST 00
ROUT 35
DES  ADMIN OUT 2
TKTP COT
NPID_TBL_NUM   0
PRIV NO
SAT  NO
IDEF NET
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
    MODE PRA
    IFC  D100
    SBN  YES
    PNI  00001
    NCNA YES
    NCRD NO
    ISAR YES
    RTN  34
    MIN  0
    MAX  72
    NCOS 0
    IEC  ???
    CPUB OFF
    DAPC NO
    BCOT 0
DSEL VCE
PTYP PRI
AUTO NO
DCDR NO
ICOG OGT
RANX NO
SRCH LIN
STEP
ACOD 8235
TCPP NO
TARG
CLEN 1
OABS
TIMR ICF  512
     OGF  512
     EOD  13952
     NRD  10112
     DDL  70
     OOD  1
     ODT  4096
     RGV  640
     FLH  510
     GRD  896
     SFB  3
     CRD  512
     NBS  2048
     NBL  4096

     IENB  5
     TFD  0
     LEXT  100
     VGD  6


PAGE 002

CDR  YES
INC  NO
LAST NO
QREC YES
OAL  YES
AIA  NO
OAN  YES
OPD  YES
CDRX NO
NATL YES
MUS  YES
MRT  10
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
OHQ  NO
OHQT 00
TDET NO
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART  0
SGRP 0
ARDN NO
AACR NO

and here is the rdb you put trunks in

REQ: prt
TYPE: rdb
CUST 0
ROUT 8

TYPE RDB
CUST 00
ROUT 8
DES  ISA MASTER
TKTP ISA
NPID_TBL_NUM   0
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
    MODE PRA
    IFC  D100
    SBN  NO
    PNI  00001
    SVRT 13
         15
         33
    NCRD NO
    NSF  YES
    COTR 15
    WATR
    CHTY BCH
DCDR NO
ICOG IAO
SRCH RRB
TRMB YES
ACOD 8208
TCPP NO
TARG
CLEN 1
BILN NO
OABS
ICIS NO
TIMR ICF  512
     OGF  512
     EOD  13952
     NRD  10112
     DDL  70
     ODT  4096
     RGV  640
     GRD  896
     SFB  3
     NBS  2048
     NBL  4096

     IENB  5
DRNG NO

and here is one trunk[/code]


DES 503565.1
TN 029 01
TYPE ISA
CUST 0
TRK PRI
PDCA 1
PCML MU
RTMB 8 1
B-CHANNEL SIGNALING
TGAR 1
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DTN CND ECD WTA HPR THFD HKD SPCD
P10 VNL
TKID
AACR NO
DATE 13 JAN 2009

[/code]

and the strange des in this case is the ckt numnber for that pri.. port 1 t's get that here.. when we have a ckt down, the number is faster to find

john poole
bellsouth business
columbia,sc

 

[ba7389]

Thanks again to all.

Based on past experience - That D Channel does appear to be working into a 5E, but the CO_Type should actually be ATT vs. STD to avoid occasional bug messages.

On the ISA vs CBCT thing - That ISA interface is the DMS custom version of the National ISDN standard. NI-2 should work, with very minor tweaks, into anything that recognizes the standard.

A note on LD 17 says - "The Release ID is required and supported for connection to Northern Telecom equipment only. For connections to AT&T ESS#4 and ESS#5, set RLS=1. I don't really ever recall doing this in the past, but still hope it might be the answer.

Please keep any ideas coming - will try anything at this point. Thanks

 

[curtismo]

My feeling is that you need to point more strongly at the Global Crossing switch as being the problem. From what I'm seeing you're sending an outbound message to set up the call on the switch, and then you get no response, so 12 seconds later your switch sends out a message to reset the channel.

I'd tell Global I'm sending something to you, why is your switch not responding.

 

[ba7389]

Curtismo -

Nortel has told me the same thing, so I have postponed cutovers. Will be setting up a test environment to use the live circuit with a protocol analyzer to isolate this. Have never had so much trouble with one of these, have verified that NI-2 does work between switches of these types, and have tried just about every option available on my end. Do have a tech sending me all translations for both ends of an Option 11C to DMS NI-2 PRI that does work, but really don't expect that to be the answer. All seems to point toward Global Crossing. Thanks to all for assistance. -Bruce

 

[bulakeno]

ba7389, will this be your first Global Crossings service ? i would say find another carrier. We have them in 10 of our offices here in the US and we are starting to move to another carrier as we had too much headaches with them. Dropped calls, static, cannot call Asia, London, South America & Australia most of the time.

 

[ba7389]

That's not good news. This is mostly a price decision, and this is a first voice experience with them. We have our Internet and MPLS circuits with them, and are very happy. Am a little concerned with them now, based on your comments and this first experience.

BTW - They are now believing that it is their problem, and have made a change to the circuit and released it to me for testing. Will post answer if there is one. Thanks again.