back up route

[coniglio]

I've already posted about the fact that one of my T1s is down and I asked how come my users couldn't call out over my back-up route. I mentioned this in passing just now to a colleague of mine and he said it's probably because the T1 is disabled, as opposed to busy. I thought that if the circuit was busy OR disabled outbound calls would go over my second route (POTS). Is it true that that only happens if the circuit is BUSY? Please advise. Thank you.

 

[PERRYPJ]

ON A MERIDIAN IT DOESN'T MATTER EITHER WAY IF THERE DISABLED OR BUSY IT WILL GO TO THE SECOND ROUTE AS LONG AS IT'S IN THE RLI

OLD ROLMEN WORKING ON NORTELS

 

[coniglio]

thank you. that's what I thought. My PBX tech is onsite and trying to determine why they can't call out over that route. I'd like to ask you one more question if I may. The first member in my backup route was punched down to xxx-yyy-1234, which the main number, which is now ported over our T1. I thought this might be why they couldn't call out over this route so I outted this first member but it didn't help. If this first member is punched down to a POTS that is now ported, it would never work, correct?

 

[johnpoole]

not sure as to the term ported.. if you have a working outbound trunk on that member it should step to that route. get on the port with a butt set to test. if i redirect the inbound to a t1, the out bound is not blocked. almost (but not) the same as forwarding my home phone to my cell. I can still call out on the analog home pots. your back up route should be referenced in your rli as a secondary entry. if entry 1 points to your t1, it's down or busy, all else equal, the call takes entry 2..

john poole
bellsouth business
columbia,sc

 

[coniglio]

This wound up being my fault. I had Verizon disconnect the last five POTS lines a few weeks ago in the route (leaving me with the first five) but I never outted them in LD 14. You live and learn. thanks to all for your help.