Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: BlackSunshine on July 06, 2017, 05:46:47 PM
-
I am about to cluster 4 -3300's together running 8.0 software. I have clusterd several using IP Trunks but never used the Direct IP Route option to cluster. Can anyone the me any disadvantages of using Direct IP Route over using IP Trunking?....I assume Direct IP Route is SIP based clustering? Any help appreciated
-
I am about to cluster 4 -3300's together running 8.0 software. I have clusterd several using IP Trunks but never used the Direct IP Route option to cluster. Can anyone the me any disadvantages of using Direct IP Route over using IP Trunking?....I assume Direct IP Route is SIP based clustering? Any help appreciated
Direct IP trunking is exactly that... simple, and largely pre-defined, and it makes routing calls a breeze... Read the help on it, I see ZERO advantage to doing it any other way especially in a new installation.
-
The advantage that I see in using XNET trunks is that you can get SMDR between systems. With IP Direct you can't.
I use SMDR all the time and when it's not there it creates more work when troubleshooting.
Ralph
-
If Direct IP Route is SIP based will that mean my calls between the 3300's will be first name initial last name? example instead of John Smith it would be J. Smith
-
If Direct IP Route is SIP based will that mean my calls between the 3300's will be first name initial last name? example instead of John Smith it would be J. Smith
As far as I'm aware this happens across the cluster elements regardless of if it is Direct IP or XNET. (i.e. J. Smith)
-
Full name is delivered between clustered 3300's using IP Trunking....I have several using IP Trunking
-
Full name is delivered between clustered 3300's using IP Trunking....I have several using IP Trunking
Direct IP Route is not SIP based, it is essentially the same as XNET trunking just a lot of the configuration is done for you.
I haven't done a cluster any other way for at least 2 years and haven't seen any real drawbacks or any difference between the "old way" of doing XNET.
-
AceJavelin....do your Direct IP Route trunks deliver full name?
-
"Full name" v. "inital.Surname" is about whether you have the foreign language support option ticked.
-
AceJavelin....do your Direct IP Route trunks deliver full name?
We have systems all over the world, typically just get F.Lastname, but I have never had a request to do it differently. The system knows the name before you dial it already from the shared telephone directory so I don't know why the method of delivering voice would be different.
-
"Full name" v. "inital.Surname" is about whether you have the foreign language support option ticked.
Hi VinceWhirlwind,
Can you elaborate on where this option is?
-
Sorry, I don't have a controller in front of me.
I think it's in the controller System Settings (not CoS) and it's called something like "Multilingual Display".
Obviously "Multilingual Display" doesn't mean "Display the full first name instead of just the initial", but ticking this is in fact the solution for displaying full name for some reason.
-
Sorry, I don't have a controller in front of me.
I think it's in the controller System Settings (not CoS) and it's called something like "Multilingual Display".
Obviously "Multilingual Display" doesn't mean "Display the full first name instead of just the initial", but ticking this is in fact the solution for displaying full name for some reason.
Got me wondering so I looked it up...
System Options - Multilingual Name Display
Description:
Select "Yes" to enable the Multilingual Name Display feature, allowing User and Services Configuration (USC) Names, which include UTF-8 encoded, to be displayed on various endpoints within the cluster, instead of the Telephone Directory Names, which support ASCII characters only.
Notes:
User and Services Configuration (USC) Names will be displayed in full where space is available.
For SIP calls, you must also enable this option in the SIP Peer Profile and/or SIP Device Capabilities form.
Default value:
No
-
One thing I like about Xnet/IP is you have control over compression
-
OK, Multilingual Name Display was only introduced in MCD 7.1.
In the past we had to program the users full name in the 'last name' field so that it would display correctly across a cluster.