Having an issue with a PRI please sanity check me

[MG2005]

So i have a remote site with a 61C that is getting fast busy's on incoming calls..

the T1 PRI has no alarm but MBUSY on all channels
Took down the Loop and DCH
Brought up the DCH (which enables but gives me a RLS mesaage, no far end response I assume)

But what strikes me odd, is when i go into LD 60 and stat the loop its still disabled - havent been playing with Nortels too much in a while, but if I remember correctly the loop would normally attempt to establish after bringing up the D-channel on my end, regardless of the far end status


But it isnt...it is still disabled when i stat it...so i force it up (ENLL 18) and it comes up but again with MBUSy channels

what can i do to test my equipment before i point at the provider (which if i remember MBUSY channels would almost always point to an issue with the far end/provider)

Thanks

 

[brewerdude]

You always bring up the loop first. When you do that, the pbx will then bring up the d-channel automatically. If you are getting MBSY on the channels, the problem more than likely exists on the far end, b/c the pbx is seeing each channel in a busy state. You can try to enable and disable a couple of individual channels to see if that changes anything

DSCH XX YY (XX = loop, YY = channel)
ENCH XX YY

However, feel free to call your provider and be prepared for them to tell you it's your equipment. ;-)

 

[MG2005]

ahhh i was doing it backward wasn't I!
See when you stop playing with a legacy PBX for a while look what happens - i become dislexic!

still i get Maint Busy on the channels

but when i dis and enl an individual cannel it comes up as idle! what does this mean?

 

[MG2005]

the dch is still saying "oper RLS auto

 

[MG2005]

plus to thicken the plot-
they are getting no incoming or outgoing call abilities
yet they have 3 other T1's (2 are PRI's) that are in service and idle

wonder if they just have no RRB setup or routing or if there is a bigger issue here - look slike they have numerous routes setup, even copper trunks- why would they have no outgoing calling at all?

 

[johnpoole]

i would look at the rlb and maybe remove the route that has the down pri.. should step over a bad pri.. when you do the enll x on the pri, what codes do you get?

john poole
bellsouth business
columbia,sc

 

[brewerdude]

If the d-channel is down then you're going to have issues with being able to place calls across all T-1's.

At this point, you should definitely open a ticket with your carrier. Even if the problem ends up being on your end, they can at least assist you with troubleshooting.

 

[johnpoole]

most carriers will not help, they either don't know your switch or don't seem to care.. if that is your only d, then yes your down... the backup should take over with a single loop down..

john poole
bellsouth business
columbia,sc

 

[brewerdude]

Depends. Just got off a call with AT&T where they busied out some trunks for me that helped me determine I have a bad UT card. They're going to leave them busied out (and the ticket open) for me until I can get a replacement to that site.

Not all carrier techs suck.

 

[MG2005]

yes we called in some tickets-

and of the 4 PRI's they have, now 3 of them are bad...the original one with teh MBUSy channels, another one now has MBUSy channels (and no alarm) and another has DSBL channels and a red alarm -and i made no changes to these other ones...so they have ons single PRI that has idle channels

i have a feeling either the mux (they are all AT&T circuits and terminate on the same mux) or something at their CO is bad

they had NRR configured on all their route entries...so i believe that means no outgoing calls would be able to reroute to an alternate trunk, right?

I'm going to try pointing these calls at a copper trunk (make it entry 0 on all their routes) or change the SBOC to RRA and see what happens

thanks guys

 

[MG2005]

whats teh best way for me to fins out and check what PRI and MSDL cards these PRI's live on? (remotely, im not at this site)

also whats teh best way to find out what Loops correspond with what route entries? LD 90 i guess? By seeing what area codes point to what RLI's I guess?

 

[brewerdude]

to see which loops are on which route goto LD 21 and do an LTM

To see which area codes go to which routes, goto LD 90 and prt the npa to get the RLI. Then go to LD 86 and print the RLI to get the routees.

 

[MG2005]

update:

At&T said they spoke to someone yesterday about an issue with one of these PRI's...and turns out someone told them its an avaya system so AT&T went and reconfig's all these for a different protocol!!

i had him swicth em back to SL1 etc and when i reset all Loops and DCH's they came up!

whew! Fun times

 

[brewerdude]

Nice.

Glad you got it working again.

 

[MG2005]

thanks boys

ironic enough (and im used to this after 7-8 in telecom but still always funny) the AT&T tech's first response was:
(Check your equipment because I can loop back teh smartjack and even see past teh smart jack, and yoru equipment is sending a yellow alarm"...etc etc you know the drill

luckily after he heard me out (That I am getting no D channel response from his end and my equipment is not alarming, etc) he was very helpful and found the issues on his side

usually MCI (formerly known as) and AT&T have the good, helpful techs...but Verizon, well I dread when I have to deal with them on these types of issues...99 out of 100 times it's an issue on their end, but it ALWAYS takes a minimum of 2-3 trouble calls and finger points until they finally look at it seriously on their end and admit to an issue

oh well, another day in the life of a voice guy

 

[johnpoole]

good to see your up.. funny post, your switch sends a yellow (all one's) to tell the far end that i am but can not get a layer 2 response from you...

i've had better luck with mci the few times i've used them, i used to hate to have to call westel.. they were a joke.. i had a tech tell me i had to track off of them before he could enable his end... buddy, have you ever tried to clock off of a down link? at this site, if that was true i would be clocking off of 21 pri's.. that's got to be a long clock command

btw in case your not an old t1 guy, yellow is proof that layer one is up, ie i see the physical layer as good... red is just the opposite,

i usually test a pri to a loop back... pins 1 and 2, looped back to pins 4 and 5... dis dch x, disl x enll x, the d will come up in about 20 seconds, then rel wronge mode... that is 90 percent sure that i have good cards.. the rls is because one end has to be user the other network, with a loop your either one or the other...

john poole
bellsouth business
columbia,sc