LD 60 stat output appears different

[hunter462003]

When I do a ld 60 on my pri loop I get the following output:

.stat 3

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

When I do the same command on my other loop I get a different output:
stat 2

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

My question is:
On loop 3 what does the *(asterisk) indicate? And what does the word tracking indicate?

Both loops are on the same card, NT5D97

We are currently experiencing intermittent one-way speech path problems, which have been occurring since our carrier took down our pri (loop 3) to make changes for an Nxx routing issue. In all cases we can hear the caller, but the caller cannot hear us. And it only seems to be external calls and it doesn't seem to matter if we make an outbound call or if the call is inbound, the external party cannot hear us. Any and all help is greatly appreciated. Thanks in advance.

 

[bigindian65]

3 is tracking because it is a clock Ref loop. Is loop 2 an internal TIE, not to PSTN? I think that has something to do with whether you see an * or not.

Mato' Was'aka

 

[hunter462003]

loop 2 is our DSN connection. But you are correct, it doesn't go to the PSTN. I'm very much a nortel novice, so please excuse my ignorance, but what is a clock ref loop? I'm looking to get to the bottom of our intermittent one-way speech path problem and I'm trying to rule-out our gear before I call the carrier. Along with the one-way speech path issue, we experience intermittent low volumn and intermittent "garbled", muffled or the caller sounds as though they're speaking under water. Thank you for your response. Again, any and all assistance is very much appreciated. Any thoughts on the one-way speech path issue? And as I mentioned before, this issue started after our carrier took down our pri to fix an Nxx routing issue.

 

[hunter462003]

What type of problems might I experience if both the carrier and us are providing clocking?

 

[bigindian65]

don't look too mauch at that, you both are not, it is Ext - external and a must for PRI operation for talkslot/timeslot multiplexing synchronization.

when you do a lcnt in ld 60 are you seeing any or a lot of errors on that circuit?

Mato' Was'aka

 

[hunter462003]

.lcnt 3

PRI LOOP 3
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000

.lcnt 2

DTI LOOP 2
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000

No errors.
So, when you say external, that means that the carrier is providing the clock for our pri? Sorry, I interpeted the "tracking" as us providing clock.

ssck 0
ENBL
CLOCK ACTIVE
CLOCK CONTROLLER - LOCKED TO LOOP 3
PREF - 3
SREF - 2
AUTO SWREF CLK - ENBL
NO ERROR

Thank you for your assistance. I'm running out of places to look, to resolve our intermittent one-way speech path issue. The more I investigate this issue the more I realize how much I don't know. I've got my work cut-out for me.
Thanks again.

 

[johnpoole]

you both can't provide.. user net or side determines which diriction the switch looks for clock sync.. if you matched that with the provider the d would estb, then rls wronge mode/..

you software a pri as clock.. it does not have a clock.. it looks at the far end, then syncs the clock card with the provider.. the only time the interal clock is master clock is in free run... if you have t's they would slip..

john poole
bellsouth business
columbia,sc