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!

PRI TIE INCOMING OK, NO OUTGOING ACROSS NET

Status
Not open for further replies.

624lata

Technical User
Aug 1, 2005
12
US
We have OPTION 61C with Succession 4 and tried running both QSIG and 5ESS for tieline in-house.

1. TIE OK when far end (Cisco) calls this end (61C).
2. Loop counters clean.
3. DCH up and running clean.

DCH traffic shows up when far end calls the 61C and everything looks good on both switches.

When 61C tries to call the far end, we get about 6 sec delay and then a fast busy. We have circumvented NARS/BARS by hitting the Route ACOD when calling the far end. No DCH traffic shows originating at the 61C nor do we see any incoming DCH traffic on the Cisco side.

SHOULDN'T I AT LEAST SEE SOME TYPE OF DCH TRAFFIC ATTEMPTED FROM THE 61C OUTBOUND?

I have sneaking suspicion it could be RDB issue but everything else looks good. Does anybody have any ideas?



 
IN LD 96, turn on the D-Channel messages to see what is being sent.

Code:
ENL MSGI xx <-- D-Channel Number
ENL MSGO xx

This will at least tell you if the D-Channel is process calls on the span, or if the issue is a RDB issue, the D-Channel won't show anything.

Scott M.
 
That's what we did in LD96 to monitor DCH traffic.

There is no DCH traffic when call originates from 61C to Cisco.

There is DCH traffic when call originates from Cisco to 61C.

My RDB is identical to another 61C at another site. Is there any way to monitor what is happening at the route level? The LD80 TRAC doesn't tell us anything useful.

 
Can you try it using NARS? I know with my PRI circuit here I can not use just the ACOD. If I do I get the same result that you get.
 
Did you configure a DSC in LD 87 pointing to a RLB with your TIE or QSIG Route.
 
In the LD86 RLB, we created the respective RLI that points to the route (18).

In turn, in LD87 CDP, we created a DSC to point to the RLI.

I've always thought the ACOD would be a good low level test vehicle to make sure routes work properly taking NARS/BARS out of the picture.

There is a possibility we were too strung on using the ACOD last week after hours and hours of troubleshooting. I will have the group try it again via NARS to the far end.

Any other ideas to try?
 
Check your route, also look at the trunk members. Make sure the CLS on the members has DTN not DIP, pulse.

Duke BB!
Go Blue Devils!
 
at times the problem with acod is the trag/tgar default is 1 for everything, blocking an acod access. would it help if i posted my rdb between my 81c and a ccm, with qsig?

john poole
bellsouth business
columbia,sc
 
That would be swell. I'm trying to get a hold of all the config to post.
 
Route:


REQ: prt
TYPE: rdb
CUST 0
ROUT 100

Code:
TYPE RDB
CUST 00
ROUT 100
DES  CISCO LOCAL
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  00000
    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 RRB
TRMB YES
STEP
ACOD 8760
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
     IENB  5
     TFD  0
     VSS  0
     VGD  6
DRNG NO
CDR  NO
VRAT NO
MUS  YES
MRT  10
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
Trunk:

Code:
DES  CISCO LOCAL
TN   100 01
TYPE TIE
CDEN SD
CUST 0
TRK  PRI
PDCA 1
PCML MU
NCOS 1
RTMB 100 1
B-CHANNEL SIGNALING
TGAR 1
AST  NO
IAPG 0
CLS  CTD DTN WTA LPR APN THFD HKD
     P10 VNL
TKID
FCAR NO
DATE 24 FEB 2005
Dch:

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

john poole
bellsouth business
columbia,sc
 
didn't post as i expected due to a copy and paste, but that is a working cisco qsig interface

john poole
bellsouth business
columbia,sc
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top