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-Channels Idle *

Status
Not open for further replies.

cowherjohn

Technical User
Jun 27, 2005
6
US
I have built a new equipment tie line, with a PRI, IFC type is 5ess, the span and dchannel come up with no errors and calls go into the Option 11 just fine, but cannot dial out. When the trunks/channels come up they are displaying "Idle *"

Can someone input why they come up with the * , I can also see the PBX try to make calls go out by viewing the dchannel, by viewing the MSGI/MSGO. It appears as though calls are going out but there is no audio, the other end actually rings, when the caller picks up it is dead air???
 
the * is because it's a pri. post the config and the d, and maybe we can help

john poole
bellsouth business
columbia,sc
 
Thanks here's part let me know if you'd like to see more, just so you know it is an E1 interface

REQ: PRT
TYPE: RDB
CUST 0
ROUT 1

TYPE RDB
CUST 00
DMOD
ROUT 1
TKTP TIE
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00000
SRVC NNSF
NCNA YES
NCRD NO
CTYP UKWN
INAC NO
ISAR NO
TGAR 0
PTYP DTT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 653
TCPP NO
TARG
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
SIGO STD
TIMR ICF 1920
OGF 1920
EOD 13952
LCT 256
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
PRPS 800
NBS 2048
NBL 4096
NRAG 30
IENB 5
TFD 0
DTD NO

SCDT NO
2 DT NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP 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
CBQ NO
AUTH NO
TTBL 0
PLEV 2
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 653 1
SGRP 0


TN 001 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI2
PDCA 1
PCML A
NCOS 0
RTMB 1 1
B-CHANNEL SIGNALING
TGAR 0
CLS UNR DIP WTA LPR APN XREP
P10 VNL
TKID

ADAN DCH 14
CTYP DCHI
CARD 01
PORT 1
DES CISCO
USR PRI
DCHL 1
OTBF 32
DRAT 64KC
CLOK EXT
NASA NO
IFC ESS5
SIDE USR
CNEG 1
RLS ID **
RCAP ND2
MBGA NO
T23 20
T200 3
T203 10
N200 3
N201 260
K 7

REQ

 
for testing turnof nd2 onthe rcap and trmb to no. in ld 96 star serv, that may needs to toggle.. it could be you've missed dis msdl 1 all, enl msdl 1 fdl to load your software onto the msdl card.. that takes down ALL channels on a msdl, map dch will show the usage on that card

john poole
bellsouth business
columbia,sc
 
Make sure that CLID table 0 is programed. Some carriers need to see all 10 digits.
 
Thanks for your response,

johnpoole: I have turned off nd2 on the rcap, and trmb to no,

I am not certain what you mean " in ld 96 star serv, " ?

This system has the DCHI card with the dchannel daughterboard not a MSDL card, does your map dch still pertain.

I am seeing that the Nortel Puts the Dchannel on channel 31 when you do a stat in LD 60, and not on channel 15 like normal E1, is there a way to change that?
 
Usually with 5ess you need to enable service messages on the D-channel to help recovery of the D channel after an interruption (eventhought I don't think this is the problem)
Disable the d channel (ld 96 dis dch 14)
Disable the loop (ld 60 disl 1)
Disable MSDL 1
Enable services on d-channel (ld 96 stat serv (to see) ld 96 enl serv 14)
enl MSDL 1 fdl

I noticed on your D channel the label "Cisco", is this a VoIP interface ? If so, chances are that your problem is IP routing not enabled on the Cisco, that causes one-way audio problems and likewise, (you reported ring and dead air)

Also, the D on channel 31 has to be right, otherwise you would not ring thru. (And again, never done E1 myself)
 
yes the map does still work, the above post covers serv msg. stat serv.. an you have to enl the card with a fdl, without that your changes are local, and do not go in effect. i did notice the mismatch des, but when you stat x in load 60 the correct d shows on your last port

john poole
bellsouth business
columbia,sc
 
I had the same problem one year ago.
Also follow the mluckie1 recomendation (Make sure that CLID table 0 is programed. Some carriers need to see all 10 digits). In my case the CISCO was waiting more digit and I was sending only four.

I see also that you are using A law in the trunk.
In the route you have TTBL=0. Can you see if the table have all tones and cadences for A law (LD 56).
The trunk have CLS DIP. Can you change to DTN.

For a best troubleshooting, enable the debug option in the CISCO for follow the process for a call.

Regards,

Javier
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top