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!

Long distance calls giving a fast busy after weekend power outage

Status
Not open for further replies.

TheTural

IS-IT--Management
Aug 21, 2017
3
US
I'm having an issue with my Nortel CS1000 system this morning after a power outage over the weekend, where long distance calls are going straight to a fast busy without ringing. We have auth codes set up, if that matters. We don't really have anyone on-site who is knowledgeable about the Nortel system (myself included), and our provider (Windstream) won't offer support on it any longer. I know I've had this issue in the past and a tech had come out and was in-and-out pretty quickly, so I don't think it's a difficult fix, I just have no idea where I need to look for the cause of this or what I might need to restart/check. Any help would be appreciated.
 
Do you have remote access to the system?

If yes, access the system and verify the LD trunks are up. A quick check in LD 60 will tell you if you have trunks disabled or out of service.
 
As suggested above, a serial port access is probably the best way to get onto the system. LD 60 is useful as you can enter in "STAT" to find out what circuits are in service.

Also go into LD 96 and key in "STAT DCH". You might find that one link is down. Then go back to LD 60 and try "ENL xx" (xx being the loop number of any circuits not showing IDLE" etc.

There is more to tell, but it's best to try and contact someone who knows the programming.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
In LD 60 I have:

[pre]PRI* TRK LOOP 2 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
TRACKING
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - BUSY DID VOD * CH 02 - BUSY DID VOD *
CH 03 - BUSY DID VOD * CH 04 - IDLE DID VOD *
CH 05 - IDLE DID VOD * CH 06 - BUSY DID VOD *
CH 07 - IDLE DID VOD * CH 08 - IDLE DID VOD *
CH 09 - IDLE DID VOD * CH 10 - IDLE DID VOD *
CH 11 - IDLE DID VOD * CH 12 - IDLE DID VOD *
CH 13 - IDLE DID VOD * CH 14 - IDLE DID VOD *
CH 15 - IDLE DID VOD * CH 16 - IDLE DID VOD *
CH 17 - IDLE DID VOD * CH 18 - IDLE DID VOD *
CH 19 - IDLE DID VOD * CH 20 - IDLE DID VOD *
CH 21 - IDLE DID VOD * CH 22 - IDLE DID VOD *
CH 23 - IDLE DID VOD * CH 24 - DCH 2

DTI TRK LOOP 3 - ENBL
FFMT/LCMT/YALMT: D4/ AMI/DG2
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : RED
CH 01 - DSBL TIE VCE CH 02 - DSBL TIE VCE
CH 03 - DSBL TIE VCE CH 04 - DSBL TIE VCE
CH 05 - DSBL TIE VCE CH 06 - DSBL TIE VCE
CH 07 - DSBL TIE VCE CH 08 - DSBL TIE VCE
CH 09 - DSBL TIE VCE CH 10 - DSBL TIE VCE
CH 11 - DSBL TIE VCE CH 12 - DSBL TIE VCE
CH 13 - DSBL TIE VCE CH 14 - DSBL TIE VCE
CH 15 - DSBL TIE VCE CH 16 - DSBL TIE VCE
CH 17 - DSBL TIE VCE CH 18 - DSBL TIE VCE
CH 19 - DSBL TIE VCE CH 20 - DSBL TIE VCE
CH 21 - DSBL TIE VCE CH 22 - DSBL TIE VCE
CH 23 - DSBL TIE VCE CH 24 - DSBL TIE VCE

PRI* TRK LOOP 18 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - IDLE DID VOD * CH 02 - IDLE DID VOD *
CH 03 - IDLE DID VOD * CH 04 - IDLE DID VOD *
CH 05 - IDLE DID VOD * CH 06 - IDLE DID VOD *
CH 07 - IDLE DID VOD * CH 08 - IDLE DID VOD *
CH 09 - IDLE DID VOD * CH 10 - IDLE DID VOD *
CH 11 - IDLE DID VOD * CH 12 - IDLE DID VOD *
CH 13 - IDLE DID VOD * CH 14 - IDLE DID VOD *
CH 15 - IDLE DID VOD * CH 16 - IDLE DID VOD *
CH 17 - IDLE DID VOD * CH 18 - IDLE DID VOD *
CH 19 - IDLE DID VOD * CH 20 - IDLE DID VOD *
CH 21 - BUSY DID VOD * CH 22 - BUSY DID VOD *
CH 23 - BUSY DID VOD * CH 24 - DCH 18

PRI* TRK LOOP 19 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - IDLE DID VCE * CH 02 - IDLE DID VCE *
CH 03 - IDLE DID VCE * CH 04 - IDLE DID VCE *
CH 05 - IDLE DID VCE * CH 06 - IDLE DID VCE *
CH 07 - IDLE DID VCE * CH 08 - IDLE DID VCE *
CH 09 - IDLE DID VCE * CH 10 - IDLE DID VCE *
CH 11 - IDLE DID VCE * CH 12 - IDLE DID VCE *
CH 13 - IDLE DID VCE * CH 14 - IDLE DID VCE *
CH 15 - IDLE DID VCE * CH 16 - IDLE DID VCE *
CH 17 - IDLE DID VCE * CH 18 - IDLE DID VCE *
CH 19 - IDLE DID VCE * CH 20 - IDLE DID VCE *
CH 21 - IDLE DID VCE * CH 22 - IDLE DID VCE *
CH 23 - IDLE DID VCE * CH 24 - DCH 19

PRI* TRK LOOP 22 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - BUSY TIE 3VCE * CH 02 - BUSY TIE 3VCE *
CH 03 - BUSY TIE 3VCE * CH 04 - IDLE TIE 3VCE *
CH 05 - BUSY TIE 3VCE * CH 06 - BUSY TIE 3VCE *
CH 07 - IDLE TIE 3VCE * CH 08 - IDLE TIE 3VCE *
CH 09 - BUSY TIE 3VCE * CH 10 - IDLE TIE 3VCE *
CH 11 - IDLE TIE 3VCE * CH 12 - IDLE TIE 3VCE *
CH 13 - IDLE TIE 3VCE * CH 14 - IDLE TIE 3VCE *
CH 15 - IDLE TIE 3VCE * CH 16 - IDLE TIE 3VCE *
CH 17 - IDLE TIE 3VCE * CH 18 - IDLE TIE 3VCE *
CH 19 - IDLE TIE 3VCE * CH 20 - IDLE TIE 3VCE *
CH 21 - IDLE TIE 3VCE * CH 22 - IDLE TIE 3VCE *
CH 23 - IDLE TIE 3VCE * CH 24 - DCH 22[/pre]

In LD 96:

[pre]DCH 002 : OPER EST ACTV AUTO DES : DID_DOD_L2
DCH 018 : OPER EST ACTV AUTO DES : DID_DOD_L18
DCH 019 : OPER EST ACTV AUTO DES : LD_PRI
DCH 022 : OPER EST ACTV AUTO DES : QSIG
DCH 040 : OPER EST ACTV AUTO DES : IPDCHN40[/pre]
 
DISL 3 and then ENLL 3 brings it back to the same status. I tried manually enabling each channel as well but no change in the ability to call, and if I DISL/ENLL the loop after that, the channels all go back to disabled.
 
It might be that loop 3 is or was a tie line circuit that isn't in use any more as the indication is set to RED.

You will need to find out what D Channel is associated with that bearer. From deducting the DCH mentioned in your printout, it might be DCH 40, although I'm guessing that this may be an IP link and not a physical one.

Your other loops all look to be OK.

Perhaps, you need to look at this in a different way by extracting your networking data and compiling it in an excel spreadsheet to find out what route is being used for long distance calls.

Use the link
Instructions are given in there on what to do. Once you know what digits are being dialed, then you can work out the outgoing trunks.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top