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!

Opt81C to Cisco CM, Fast Busy

Status
Not open for further replies.

Telco01

Technical User
Jan 11, 2006
121
US
Have an Opt81C connected to a CCM via PRI T-1 for about a year now. About 5 to 7 times in the past year I will get a call that anyone on the 81C trying to call a phone on the CCM gets a fast busy. I check things out and the user is correct, fast busy. I disable/enable the D-channel and all is well.

We have a call in to Cisco but I'm sure they will point it back to the 81C.

I hate "mongrels"!

Anyone else ever had this problem?
 
I've had to set the same thing up in the past few years. I used both NI2 and QSIG and have not had any problems. You can go to Cisco's website and pull doc's on config for both types. You or they could have some faulty hardware also.
 
QSIG is the way to go between the two, seems the most stable and supported. Are the loops in the nortel switch taking hits during this time? (LD 60, lcnt_loop #)
What do the b-channels look like on the loop, IDLE< BUSY< MSBY?
 
The loop runs clean, all zeros.

At the time of the fast busy I believe the channels are both idle and busy because someone may be on a previously established call.

IFC is set to ISGF.
 
look at the d channel msgs.. does this happen both directions? post both configs, cisco and nortel.. we have the same setup without problems... does not sound like a serv msg problem, ld 96 stat serv, i would check trmb, set that to no, fdec and ndec the eth... (but those are usually assosiated with channel lockouts)

1st thing i would do is ld 96 dis msdl x all, then enl msdl x fdl.. reload the msdl, and from your post i would assume that you know to check the msdl to see how many devices you will be turning off.. killing the msdl does not drop calls, it does stop setup and tear down.. if you have a backup d, the end user will not notice the d dropping.. (if everything is built right)

john poole
bellsouth business
columbia,sc
 
Here's how I have things configured.


ADAN DCH 34
CTYP MSDL
GRP 1
DNUM 4
PORT 0
DES Cisco_HPC
USR PRI
DCHL 34
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID **
RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWI
PR_TRIGS DIV 2 3
CNG 2 3
CTR2 2 3
PR_RTN NO
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7


DES TO CISCO SERVER
TN 034 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 3
RTMB 5 1
B-CHANNEL SIGNALING
TGAR 0
AST NO
IAPG 0
CLS CTD DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 3 MAR 2009


TYPE RDB
CUST 00
ROUT 5
DES CISCO
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ISGF
SBN NO
PNI 00001
NCNA NO
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPFXS YES
DAPC NO
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 1005
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096



PAGE 002

IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR YES
INC YES
LAST YES
QREC NO
OAL YES
AIA NO
OAN YES
OPD NO
CDRX NO
NATL YES
VRAT NO
MUS YES
MRT 4
RACD 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
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO


 
Code:
ADAN     DCH 19
  CTYP MSDL
  GRP  2
  DNUM 11
  PORT 1
  DES  QSIG
  USR  PRI
  DCHL 19
  OTBF 32
  PARM RS422  DTE
  DRAT 64KC
  CLOK EXT
  IFC  ISGF
    PINX_CUST 0
    ISDN_MCNT 300
  CLID OPT0
  CO_TYPE  STD
  SIDE NET
  CNEG 1
  RLS  ID  **
  RCAP COLP NDI QMWI
  MBGA NO
  OVLR NO
  OVLS NO
  T310 120
  T200 3
  T203 10
  N200 3
  N201 260
  K    7

Code:
REQ: prt
TYPE: rdb
CUST 0
ROUT 19

TYPE RDB
CUST 00
ROUT 19
DES  QSIG
TKTP TIE
M911P NO
ESN  NO
CNVT NO
SAT  NO
IDEF NET
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
    MODE PRA
    IFC  ISGF
    SBN  NO
    PNI  00001
    NCNA NO
    NCRD NO
    CHTY BCH
    CTYP UKWN
    INAC NO
    ISAR NO
    CPFXS YES
    DAPC NO
    INTC NO
DSEL VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB NO
STEP
ACOD 804890
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC  YES
DCNO 3
NDNO 3 *
DEXT NO
DNAM NO
ANTK
SIGO STD
ICIS YES
TIMR ICF  512
     OGF  512
     EOD  13952
     NRD  10112
     DDL  70
     ODT  4096
     RGV  640
     GRD  896
     SFB  3


PAGE 002

     NBS  2048
     NBL  4096

     IENB  5
     TFD  0
     VSS  0
     VGD  6
DRNG NO
CDR  NO
VRAT NO
MUS  NO
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
CBQ  NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART  0
SGRP 0
ARDN NO
AACR NO


Code:
REQ: prt
TYPE: tnb
TN   19 1
DATE
PAGE
DES

DES  QSIG
TN   019 01
TYPE TIE
CDEN SD
CUST 0
TRK  PRI
PDCA 1
PCML MU
NCOS 3
RTMB 19 1
B-CHANNEL SIGNALING
TGAR 1
AST  NO
IAPG 0
CLS  CTD DTN CND ECD WTA LPR APN THFD HKD SPCD
     P10 VNL
TKID
FCAR NO
AACR NO
DATE 12 JAN 2009


john poole
bellsouth business
columbia,sc
 
i don't see anything on yours that does not mirror mine. it's been up over a year, with the only outage when the cisco boys boot.. (which is the only thing they know about trouble shooting)..

your rcap is a little more loaded, but that should not cause the pronlem.. i would like to see, enl msgo/msgi with call attempts in each direction when the trouble occurs.. that may be the only way to determine which end is rejecting the call, as well as the reason code.. this type of problem can be tough, you can't duplicate the problem and when it fails, they want it fixed..

when it fails will a shut/noshut bring it back up? or does it always take a dis dch and a disl?

john poole
bellsouth business
columbia,sc
 
Yep, I thought it looked pretty good and I think that is what Cisco asked for a year ago.

I just noticed that the card is an NT5D12AB. When we upgraded to FIJI the dual loop T-1 cards had to be upgradede to AH if I remember correctly. The AB came from gray market and was probably cheaper than new for the customer. Might be my issue.

And yes I can't duplicate it so I can't work on it but, when it is broke I better get fixed and quickly.

shut/noshut: not familiar with this term. Is that Cisco talk?

 
yes, it is cisco for disl enll.. i would swap the card with a working ah to see if the problem moves.. when we went figi, i went with all ah cards, since i'm onsite 5 days a week i do not need trouble..

customers usually save a dime to waste a dollar..

john poole
bellsouth business
columbia,sc
 
I agree John! I'll order up an AH and swap it out and then give it a "wait & see" what happens.

Thanx for the assist!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top