Superloop_Long Distance

[limitbreak]

Hello all,
I have a customer out in New Orleans whose Option 81C took a bath a while back.
The onsite was able to replace rectifiers to get the switch back in an 'operable' state.
The one issue we are running into is that certain phones cannot dial long distance.
I checked the RLI on 1xxx NPA's, and verified that the phones are allowed to dial LD via NCOS. I also checked the TARG on RLB to ensure no conflicts were happening.

A phone with TN 0 0 4 7 can complete LD no problem, however a phone with TN 76 1 5 12 cannot. Both phones have the same TGAR and NCOS settings, as well as CTD in CLS. My question is "Would a phone on a different Superloop be denied access in any way, and would this be a hardware issue that was missed during 'mop up'?

 

[johnpoole]

hardware would be almost impossible to block just ld. (there's no ld 90 cable). do you have tennant service? i would almost have to test that on site to even believe it.

john poole
bellsouth business
columbia,sc

 

[johnpoole]

one thing that helps with trouble shooting is when are those phones getting the busy? after 9, after 9 1, or after all digits?

john poole
bellsouth business
columbia,sc

 

[unkalary]

I just had the same problem on a switch I just cutover. Found the problem to be CLID on the phone that could not dial long distance. The CLID table number was invalid on key 0. Example KEY 0 SCR 6616 175. There was no CLID table 175. OTM put the number on it when I sent the phone to the switch. Fixed the CLID on the key and the subscriber was able to call long distance.

 

[johnpoole]

clid can break ld, don't otm but didn't know you could enter a clid that wasn't in the clid table.. maybe post the station... cls fre could break a set

john poole
bellsouth business
columbia,sc

 

[limitbreak]

*UPDATE*
Apparently the phones that can't dial LD can't dial local either.
We did some testing on telephones on site and this is what we determined.
I built a 3904 set on TN: 60-1-2-15
Test called local and long distance, no problem.
Moved above 3904 to TN: 68-0-2-4
Test called local/LD, NO GO!

We have a plan in place to move all sets with TN's on Superloops higher than 60, to those available on Superloops lower than 60. Most of this PBX is dead, meaning the switch is too big for the staff who is currently occupying the space.

 

[jhenley]

I just went thru a similar situation a couple of days ago. Only 1 group in the switch was having problems. I had a trunk in a PRI loop in same group that was giving users a fast busy when they dialed out. When I accessed the line thru Maint set it gave me dial tone but then locked up the maint set. I disabled the trunk and trouble cleared. The trouble also cleared on the trunk when I brought it back up for more testing. Just a thought, in a multi- group switch the sets will seize a trunk within their own group first. 68 and 76 are in the same group.

 

[johnpoole]

in my 81, stations take the next vacant trunk from the bottom of a 200 plus pri route.. they don't use the protion of that route that is in the same group.. could be a program option.. i would check the cable from the cni's backplane.. could save a lot of moves

john poole
bellsouth business
columbia,sc

 

[limitbreak]

*UPDATE*
After extensive calls with Tier 2 support, this is what we accomplished:
Replaced Superloop Network Card for SL 84, did not fix.
Replaced Controller Card for shelf 84-0, did not fix.
Now we are about to attempt to replace a 3PE card, really not looking forward to that after reading procedure.

 

[johnpoole]

that cni is the same card that i asked about the cable on.. history seems to say, from the rear of that card to the inter group module.. could be a problem.. but it's friday so might be better to wait until tuesday,

john poole
bellsouth business
columbia,sc

 

[limitbreak]

johnpoole,
That makes sense now, let me see if I got this right:
If I stat cni in LD:135...

cni 1 12 0: remote = group 3 ENBL
cni 1 12 1: remote = group 0 ENBL
cni 1 13 0: remote = group 1 ENBL
cni 1 13 1: remote = group 2 ENBL

cni 0 12 0: remote = group 3 ENBL
cni 0 12 1: remote = group 0 ENBL
cni 0 13 0: remote = group 1 ENBL
cni 0 13 1: remote = group 2 ENBL

...and the problem TN's are in SL's higher than 60... that would put those Superloops in Network Group 2, correct?
So judging by the info on CNI's above, that would be card 13 in core 0 and 13 in core 1?

 

[limitbreak]

*UPDATE*
I would first like to thank everyone for their help on this situation, especially johnpoole, who nailed the problem.

We ended up replacing the CNI card 1 13 1, the same one that was showing disabled after the first rinse cycle.
We had an issue restoring the Redundancy, but a sysload solved that pretty quickly.

Thanks again to all that posted!!