Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: august on March 12, 2013, 07:51:21 PM
-
I have a customer with a special need.
They have an Mxe Server (1500 ip phones) located in 4 different building.
They ask me to program a single number for emergency (5555) and they want this number to ring a key on a phone (security) only in the building where the call was initiated.
Since all the phone are in the same MxeServer, do you have an idea how I can do this?
-
Out of a single server? No, I don't think this is possible, maybe with tenanting but even then I don't know.
-
With MCD 6.0 there is Location Based Routing available. You'll have to configure a zone for each building.
Otherwise, I don't think it is possible. Maybe with some advanced ARS (a different COR for each building and loopback IP-XNET zone), but I would consider upgrading to 6.0 before that.
-
Could do it using visual workflow manager or something that will allow some type of perfered agent routing (this is really only an option is you have it already install for something else as I doubt it will be cheap)
-
It is possible but a major PITA.
- First create a unique number for each building such a 4444, 6666 etc that rings on the special phones.
- Next you have to create a loop back trunk.
- The in the default account code index put create an index for each building. For the account code use the cluster element ID + XXXX. So if the element ID is 1234 what you will put in your default account code table is '1234444'.
- Assign the default code index to each phone based on the building it's in.
- Create an ARS route to route the call through the loop back trunk.
- In the digit mod table absorb all digits and insert '<d>'
- Now point the digits dialed i.e. 5555 to this new ARS route.
Now when the call goes out the ARS route, it deletes the 5555 and inserts the cluster element ID and the special number.
If you don't need the cluster element ID you can simple put the special number in the default account code table. i.e. 4444
Now like PFM, when someone dials 5555 it will route the call to the proper building.
Ralph
-
Thanks marcolive and Ralph.
The problem with upgrading to rls 6.0 is that the customer use a 3rd party application using Mitai and they are not ready for rls 6.0. But thanks, this is what I need.
If I cannot upgrade, I will try to setup the Ralph's Option with default account code.
Thanks a lot!!!!!
-
Send beer. ::)
Ralph
-
I wonder if location based routing would have even worked. Thought it was for a cluster with multiple 3300's so you can send 911 info out the correct 3300. This is a single MXe server.
Ralph would the looped turnk not need to be a dial in and not a LS copper?
-
Ralph would the looped turnk not need to be a dial in and not a LS copper? (http://Ralph would the looped turnk not need to be a dial in and not a LS copper?)
If I understand your question, the loop back trunk is using IP trunking - no copper involved.
Ralph