Re: T1 Redundancy

[jaclarke]

Good day,
I am a PBX administrator for a Nortel Meridian system at a financial Institution. We have 6 t1's and two of those are actually PRI's. The problem that we have been having lately is that one of those PRI's have been going to a MBSY status, which I know is a problem in the exchange with TELCO. The problem with this is that we have traders on this PRI and when or if this happens there phones are down externally and they cannot receive calls from customers who want to make trades, and in todays market, this is not a good thing.

We are looking for a solution in regards to how can we get a secondary telco to bring in an additional T1, so that if this happens again and for redundacy purposes how can we reroute traffic to the seondary or redundant T1, so that it maybe as seemless as possible to the Traders?

James

 

[phonz1]

One question, why when the T-1 goes down are the phones not ringing in? DID's point to a trunk group and not specifically a T-1....

Now, for your question: another telco will not be able to give you the same DID numbers on a secondary T-1, how is your system currently configured, could you post the RDB and the DCH for the problem spans??

 

[jaclarke]

Here you go,
The traders are on loop 7, and when this happens they are unable to receive calls coming because when you call it never rings on there end. Loop 8 is a new PRI we just installed and whe they try to bring this up 7, goes down.

PRI* TRK LOOP 7 - 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 - IDLE DID VOD * CH 22 - IDLE DID VOD *
CH 23 - IDLE DID VOD * CH 24 - DCH 10
.

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

.stat dch
DCH 005 : OPER EST ACTV AUTO DES : L005_STM_VOIP
DCH 010 : OPER EST ACTV AUTO DES : FAXDCH
DCH 011 : OPER EST ACTV AUTO DES : localpstn
DCH 012 : OPER EST ACTV AUTO DES : TURRETPBX

 

[phonz1]

ok, that makes sense. I would have these "new" did's added to the same trunk group as the first group is, that way when one span drops, they'll still be able to get calls

 

[jaclarke]

So with the redundant T1 the users we want to identify to get priority still wont be able to get the same DID's from a different TELCO?

 

[phonz1]

no, each Telco owns the numbers so...... The only thing you could do to get a second telco, would be to port the numbers over, if they do number portabilty where you are. But it would get complicated if you start breaking chunks out of a block of DID's. I would think the keeping your current Telco and having all DID's on one trunk group would handle your issues, still it is up to them to repair that span or install a new one to replace it

 

[tnphoneman]

Just get a second T1 from your local telco provider. This is done all over the country and works fine.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[johnpoole]

another possible work around would be to add itg trunks via a second provider.. we have 3 routes for inbound from the unique central offices.. all from the same provider but still not all on the same far end term.. we have never had all 3 drop at once..

and in ld 87 you can push calls to the overflow routes BUT, your inbound is tied to that office.. you can check with them to see if they can overflow to a second provider..

i know how you feel, this is a hosp with 60 pri's.. never a good time to not be able to rec calls

john poole
bellsouth business
columbia,sc