General question, when trunks are full what are some good practice? 2

[surferdude949]

When your main incoming and outgoing trunks are full, what are some "back up" routing that can be done?
I understand it all depends on your infrastructure but I'd would like some general practices being used.

Running S8700 cm5 with 2 T1 for outgoing and incoming and several H.323 trunks to remote gateways.

 

[SF0751]

Ummmm..... Get more trunks. Now.

Do the remote gateways have their own inbound/outbound trunk groups?

Susan
“Before you criticize someone, you should walk a mile in their shoes.
Then, when you criticize them, you are a mile away ...
and you have their shoes.”

 

[surferdude949]

Yes, mostly analog lines. And one has a PRI. Any routing I can do besides getting more trunks? The trunks don't usually reach full capacity. It's just at some instances.

 

[98Converter]

Outbound diversity can be done utilizing your WAN and inbound would have to be done on the Service Provider side... With SIP trunking from the SP, you can do inbound diversity fairly easily - although not too sure how SP's play together with DID ranges. I think you would have to carry all your DID's on the same Service Providers network to really get it done 100%

Like you said though, WAN infrastructure is key, and if not properly provisioned it could be a whole new nightmare. Sometimes a rejected call is better than a really poor quality call in my opinion.

Or get some CO lines and build a small overflow CO Trunk for outbound calling. You could also offload your 800 outbound traffic over that too...



Thanks,
98C

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[Textron68]

Sounds like you need to run some 'peak hour' trunk analysis. Ideally you would want your peak hours to be right around 90% of capacity giving some extra room for those exception days when you have a tad more traffic. If your running at 97% or more, than it's time to look at adding capacity. You can do some overflow to your remote gateways. Be aware of the types of calls being overflowed. If your talking about sites that are long distance from your home location, you wouldn't want to overflow local calls and have them passed as long distance calls from a remote site.

 

[uzumaki]

Ok this is how we do it on my client.

My client is a well know bank that has multiple branches in different regions (APAC, EMEA, CALA, NAR)

Now each countries have their own avaya system. Practically S87xx.

Now, for them to perform long distance calls without adding a charge on their local PSTN, they are utilizing their WAN connectivity as their means of communication. Let say country A branch wants to call Country B brach or Country C. These Cisco WANs routers are under control of a single Cisco Call Manager.

Each Avaya PBX on different countries have a tieline going to a their local router. (Please also take note that each country has their own ISDN line terminated on their avaya system - this ISDN lines have their own DID range)

Also take note that each user on each of the countries have their own DID number.

The dialing algorithm performed is if User A (In Country A) tries to call User B (In Country B) they need to dial the ff: format:

Country exit code + Country Code + area code + Telephone Number

The routing algorithm perform is i will pass the DTMF tones dialed by the user on the Cisco Tieline first, then if Cisco tieline is not available due to some circumstances, it will route to local PSTN, AND ALSO Let say, if users try to dial NON DID number, it will route to Cisco gateway but if the Cisco voice gateway cannot understand the digits thrown by Avaya, it will pass the signal back to avaya and will say I cannot process this, then avaya will rehunt another channel available on the next trunk which is the local PSTN. (Route Pattern Manipulation)