Messages

1

Mitel MiVoice Business/MCD/3300 / Emergency Call Notification Across Members in a Cluster

« on: May 16, 2013, 11:29:42 AM »

Since you cannot have resilient Emergency Hunt Groups nor add members who are not on your home element to an Emergency Hunt  Group (we've tried), and without having to purchase the ERA server, does anyone have an idea on how to notify a central site that users made a 911 call?  CESID not being used in this scenario.

What I've done is to bounce the call from the calling site to the monitoring site and back out again.


Monitoring Site <---------IPXNet--------------> Remote Site 911 Calls go out their local PSTN connection

Remote site calls 911

Route List that goes out the IP/XNET link first, if that is down, go out the local PSTN connection second.  No warning tone so there is no delay.

Remote Site inserts a digit into the string (like , to the call leave the remote site to the monitoring site as 8911

Call comes in as 8911 to the monitoring site.

I immediately take that call and send it out a Direct IP Route flagged as Emergency.

Call comes in as 8911 to the remote site.

I send out the 8911 call, and on the Digit Mod, strip off the 8.

So, 911 is dialed.

Leaves to the monitoring site as 8911

Call comes in to the monitoring site as 8911

Call goes out a Direct IP Route as an emergency call.

Successful emergency notification to emergency hunt groups and console, also showing that the correct extension as to who made the call.

Call enters the remote site as 8911.

Call goes out emergency route, stripping off the 8, leaving as 911.

Does anyone know of a simpler way of doing it?  Local Emergency notification only alerts if you traverse route on that local system flagged as emergency, not on remote systems, even in a cluster.

2

Mitel MiVoice Business/MCD/3300 / Load Balancing Across Trunking Gateway

« on: May 16, 2013, 11:22:08 AM »

I am looking for a quick sanity check on programming for a customer site.

Layout is 4 controllers

TDM Gateway  A<---------------> User Gateway A
MXEIII                                     vMCD

TDM Gateway B <--------------> User Gateway B
MXEIII                                     vMCD


All four controllers will be in a cluster.  2 tdm gateways, 2 pri links each, 23 channels per link. 
What I am looking to do is for outbound calls through the TDM gateway is to try to load balance.  What I've come up with is this:

Divide the users between the two User gateways, 425 each.  Users on Gateway A will have ARS planned for the different categories of calls, 911, Local, LD and so on.  For each category of call, I'll have a route list - Try Gateway A first, then go to Gateway B.  COR assigned at the User gateway on the IP/XNET route.

Reverse that on User Gateway B.  Try TDM Gateway B first, then Gateway A.  That should, in theory, put my calls at roughly 50% each outbound.  In the even one of my User Gateways fails, I know have 850 users following the same rule, but it would be for a short while.

On the TDM Gateway, I then need to take into account what to do if my 2 PRI links are saturated (all four links from the same carrier).  So on my TDM Gateway, I'll also have a list - Try my 2 PRI spans first, if those are down or saturated, out the IP /XNET link between me and the other gateway, and vice versa.

So, if it works the way I think it should, I'll have load balancing for outbound calls, 50% on each controller unless I am in a failover state, then at the TDM Gateway, I've taken into account what happens if I run out of PRI channels or that link is down. 

Thoughts?