Mitel Forums - The Unofficial Source
Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: NTEDave on October 23, 2017, 09:34:42 AM
-
What's New in this Release?
Release 6.3
This section briefly describes the new features, hardware, and enhancements available on the MiVoice Office 250 when equipped with the v6.3 software release.
Support of 6900 SIP phones with MiVoice Office Application Suite 5.1
Mitel 6920, 6930 and 6940 SIP Phones are supported in conjunction with MiVO AppSuite 5.1. For further information, refer to the MiVoice AppSuite 5.1 documentation.
The MiVoice Office 250 R6.3 supports additional SIP extension and trunk features, handset flags, and security improvements.
Divert/Accept UCD Calls, when using SIP devices
SIP devices now support the Hunt Group Remove/Replace feature. Incoming calls to Hunt Groups containing SIP devices can be diverted by using the feature code (322 HG Remove, 323 HG Replace, 324 Toggle HG Remove/Replace).
SIP Reverse Transfer
Calls on hold or ringing at a SIP device can now be picked-up (Reverse Transfer).
Direct Page
Direct Page is an enhancement to the existing Page feature, which allows you to page to the loudspeaker of an individual IP/ Digital Phone instead of a whole Paging Zone.
To configure an IP/ Digital Phone as a destination for Direct Page the phone must be assigned to a Paging Zone, which has the Use zone for Direct Page option enabled (This is disabled by default).
A Direct Page is then activated by dialing 7 (Default Feature Code for Paging), followed by the configured Paging Zone, and then the extension number of the phone you want to Direct Page.
Direct Page can only be activated by Phones that have the Initiate Direct Page flag set to Yes.
Analog and SIP phones cannot receive a Direct Page, but can initiate a Direct Page to an IP/ Digital Phone.
Flexible SIP Header Configuration to SIP Trunk Provider
There are new fields available in the SIP Trunk Group configuration that allows to define which Caller ID information is sent to the SIP provider.
Restricted CLI in SIP Header
The caller identification can be withheld within the SIP header.
Display only Caller Identification instead of Transfer Information
A new Phone flag allows you to suppress transfer information and instead display caller identification and name when the incoming call is ringing.
Alternate Lamp Indication on Phone/ PKM Keys
A new system flag allows you to change the default lamp indications.
Release Key
The Release Key can be assigned to any programmable key (including PKM) and allows you to release a call in progress.
Notification of no Primary or Local Attendant Configured
The Primary or local Attendant is important to system behavior. When a user unintentionally removes these from the Database configuration, a warning message appears.
SSL Certificate
You can generate a Certificate Signing Request (CSR) and then upload/ import a customer’s own Certificate.
Security Updates
New OpenSSL version 1.0.2l
Improvements have been made to the existing Firewall, including the ability to save and restore settings. Firewall configuration options have been extended to include the PS-1.
-
NTEDave,
Are you crazy enough to do a beta site?!?!
Nice,
TE
-
If anyone learned any lessons from 6.0 and 6.2, never run the initial releases anywhere except at the bench. Fine to test it there, but don't let your customers "test" it.
Also, full backups before each upgrade. Back in the pre-6.0 days you could be lazy about this, but not anymore. You might find your DB default, corrupt, VM disconnected, or your chassis identifying as "CS Controller" when it is really HX until you do a default DB. I had this happen at a large site with 10 controllers. Each one needed special attention + Mitel tech support to get going again due to defects in the load they were at. Never had that happen in the 5.x days and before
-
Why Why Why no MWi to a key? Boggles my mind to still not have Message Indicator Key on a modern phone system...but we did get a Release Key
-
Why Why Why no MWi to a key? Boggles my mind to still not have Message Indicator Key on a modern phone system...but we did get a Release Key
Wouldn't that be nice? I don't think that will ever happen on this system. The first and main reason is the Voice Processor. It's code hasn't changed hardly at all since the Axxess days. It is a separate entity from Call Processing. It doesn't know any extensions unless there is a mailbox or an extension ID to tie it with. To light a key would require a line appearance that voice processor could "light" under the message wait selection of a mailbox. This ability is absent in voice processor since only a phantom or a physical device can be chosen here, so the correct MWI protocol (MiNET, etc) is used. It cannot use any other form of MWI. Also defining an arbitrary single line appearance on a key, is absent in Call Processing, not being a true PBX but more of a hybrid key system. Unfortunately other forms of MWI (analog, FSK, DC/AC) will also never appear in this system.
The release key takes me back to warm memories of working on Nortel systems. Those are the only customers I ever met who understood the release key. Teaching it to console attendants for Mitel is always an adventure.
-
I know it’s Apple and oranges but Mitel 200 ICP and Mitel 3300 both have partitioned voicemails similar to Mitel 250...and you can add them all day long...plus you can add Nupoint Voicemail to 250 but still no Message Indicator Key. We have lost sells because of that.
Release key was way overdue too and we replace lots of Norstar systems
-
I honestly can't see myself wasting a button for a Release key.
-
I honestly can't see myself wasting a button for a Release key.
You don’t have to waste a key if you can do features without special key...you can reprogram circle x or infinity key with release key
-
I will never install a system without requiring the Special key for feature codes. Been there, done that, got the bruises.
-
I know it’s Apple and oranges but Mitel 200 ICP and Mitel 3300 both have partitioned voicemails similar to Mitel 250...and you can add them all day long...plus you can add Nupoint Voicemail to 250 but still no Message Indicator Key. We have lost sells because of that.
Release key was way overdue too and we replace lots of Norstar systems
The 200ICP and the 3300 use the exact same embedded VM platform, express messenger. That code also hasn't changed much in 30 years. They just ported it to work on the 3300. But yes, can change the light destination to a single line and make a MWI to a single line, or change the light destination to a phone. This is made possible because he 200ICP and 3300 are true PBXs. The 250 is closer to a key system.
Granted there are plenty of key systems out there they can do a MWI button. I think we agree it would be a nice feature to have, but I doubt it will appear on the 250. Maybe a nice surprise one day
-
What license is required for the 6900 set?
-
What license is required for the 6900 set?
If I’m not mistaken 6900 sets require phone manager and license per 6900 set if not in SIP Mode
-
I honestly can't see myself wasting a button for a Release key.
You don’t have to waste a key if you can do features without special key...you can reprogram circle x or infinity key with release key
You still need a special key to activate features in-call...
-
[/quote]
You still need a special key to activate features in-call...
[/quote]
Yes correct...Sorry
-
What license is required for the 6900 set?
If I’m not mistaken 6900 sets require phone manager and license per 6900 set if not in SIP Mode
Sorry.... Mivoice Office Application Suite is require for 6900 series phones in SIP mode....MiNet not available
-
Guys,
Isn't the SIP only version considered to be the 6800 series not the 6900 series?
Thanks,
TE
-
What does MiNet "not available" mean?
-
The 6900 series phones only work in Non-sip mode otherwise known as Minet on 3300 /mivoice business 8.0. The phones wasn’t released in SIP mode. Now it is available in SIP mode via tftp upgrade but will only work in SIP mode on 3300 and now Mitel 250 and Mitel One and Mitel 400. The 6900 series do resemble 6800 series however you can’t add any Mitel made cordless devices such as dect / Bluetooth handset and headset to 6800 series phone. 6800 series phones will work on any sip platform. 6900 series phone even in sip mode will only work on Mitel platforms can connect to Broadsoft or other soft switches
-
Thanks!!!
-
I'm confused here... so the 6900 series will ONLY work in SIP mode to the 5000 and only with MiVOAS?!?! Is this a temporary thing until they fully implement MiNET mode for them in the 5000 in release 7.0 (or 6.3.1 or whatever)?
We have a couple systems proposed but are waiting for the 6900 series phones to be available, reconfigure, and re-bid... they have seen the 6900 series on the 3300 and don't want the "old" 5300 series phones after seeing the new ones. Our fear is if it takes too long they will look at a different product.
-
I'm confused here... so the 6900 series will ONLY work in SIP mode to the 5000 and only with MiVOAS?!?! Is this a temporary thing until they fully implement MiNET mode for them in the 5000 in release 7.0 (or 6.3.1 or whatever)?
We have a couple systems proposed but are waiting for the 6900 series phones to be available, reconfigure, and re-bid... they have seen the 6900 series on the 3300 and don't want the "old" 5300 series phones after seeing the new ones. Our fear is if it takes too long they will look at a different product.
Trust me I’m in same boat. I have given up on 6900 minet on 5000. If it is available you will be required to purchase MAS/phone manager and a phone manager license for each 6900. The problem is the 6900 series phones eat up resources in minet and the 5000 runnng on a flash isn’t enough. The 3300 can’t handle to tftp duties once you get past 100 phones. Not to mention the 6900 series phones will be odd on a 5000 unless it’s a 6940...screen is small and not enough buttons to emulate a 5340/ 8568 unless you use a 6940
-
BlackSunshine,
The 3300 can’t handle to tftp duties once you get past 100 phones.
Since when it that a thing? I have 2 systems with well over 200 phones per and haven't had any issues with TFTP on either one. The only issue I have had with TFTP with the 6900 on a 3300 was when the firmware load was too low on the 6900 and it wouldn't upgrade. Once the phone was brought up to a version of firmware that would upgrade off the 3300 the problem went away.
Thanks,
TE
-
BlackSunshine,
The 3300 can’t handle to tftp duties once you get past 100 phones.
Since when it that a thing? I have 2 systems with well over 200 phones per and haven't had any issues with TFTP on either one. The only issue I have had with TFTP with the 6900 on a 3300 was when the firmware load was too low on the 6900 and it wouldn't upgrade. Once the phone was brought up to a version of firmware that would upgrade off the 3300 the problem went away.
Thanks,
TE
I would have to agree... we have systems with hundreds of phones that the 3300 does the TFTP duties with no issues, one site I know of has just over 700 IP phones phones registered to one MXeII controller. Granted it gets a little slow immediately following an upgrade as the phones update, but the system has no issues handling the job. We also have more than one virtual 3300 dealing with 500-1000 phones with no problems.
-
BlackSunshine,
The 3300 can’t handle to tftp duties once you get past 100 phones.
Since when it that a thing? I have 2 systems with well over 200 phones per and haven't had any issues with TFTP on either one. The only issue I have had with TFTP with the 6900 on a 3300 was when the firmware load was too low on the 6900 and it wouldn't upgrade. Once the phone was brought up to a version of firmware that would upgrade off the 3300 the problem went away.
Thanks,
TE
Sorry it’s 100 for an AX page 30 of Mitel mivoice business engineering guideline 8.0....its 200 -6900 on MXE Controller page 35 of engineering guideline 8.0....also page 176 of same guide
-
BlackSunshine,
The 3300 can’t handle to tftp duties once you get past 100 phones.
Since when it that a thing? I have 2 systems with well over 200 phones per and haven't had any issues with TFTP on either one. The only issue I have had with TFTP with the 6900 on a 3300 was when the firmware load was too low on the 6900 and it wouldn't upgrade. Once the phone was brought up to a version of firmware that would upgrade off the 3300 the problem went away.
Thanks,
TE
Sorry it’s 100 for an AX page 30 of Mitel mivoice business engineering guideline 8.0....its 200 -6900 on MXE Controller page 35 of engineering guideline 8.0....also page 176 of same guide
Yes, and virtual controllers can handle the TFTP duties for 1500 sets of the 6900 series.... without going to an external TFTP server. The issue isn't with the operation of the phones or the resources they use in operation, but in the massive TFTP services they need. A MiVO250 could just as easily configured for a external TFTP server as any other Mitel system.
We could argue this all day, and interpret the engineering guide in several different ways for various scenarios, but it isn't really the point and we are not here to fight are we?
I remember the Inter-tel 5000 v1.2... it supported ~25 IP phones, through tweaks and refinements it's capacity increased 10 fold. I am sure Mitel will figure out a way to implement the 6900 series phones on the 5000 platform, or find an alternative that doesn't require a separate Phone Manager server, but the information we have this far seems to reinforce the fact it won't be happening any time soon.
-
acejavelin,
My understanding is that the new release for the MiVO-250 won't be until sometime in Feb 2018 at the earliest. That gives them plenty of time to figure that issue out.
Besides the compact flash couldn't possibly be the drawback to implementing the 69xx series phone as a MiNet phone. The compact flash is just the hard drive and the size of the files for the 69xx series phones are not large enough to fill up what is leftover after implementing a system. Even if that were the case you could put in an external TFTP as you had already stated.
It is more likely the HTML aspect of the phone is going to cause problems with processing power than anything else.
At this point I believe it is a wait and see moment. Oh!! Oh!! They could bring back the 7000 and that would work great with these new SIP phones. ;)
Thanks,
TE
-
SIP R5.0 Firmware for MiVoice 6900 Phone Family & Mitel 6800 Phone Family Upgrade PDF FAQ
7.1.7 Can 6900 phones be used with any Call Manager?
No. The 6900 firmware is locked so that it will only work with Mitel platforms. If a user attempts to
configure and connect to a third-party server (e.g. Broadsoft) then the SIP accounts will not register.
7.1.8 Are 6800 phones locked if we install R5.0 or still open to all Call Managers?
The 6800 series phones are sold into Open Standards market (Broadsoft, Asterisk etc.) as well as behind
Mitel solutions (MX-ONE, 5000, 400, Telepo, etc.). They will continue to be open and R5.0 does not lock
them to Mitel platforms.
-
v6.3 will not be released until Feb. 2018?
-
Is there anyway to get the Beta release before then? Also can anyone point me to the application 5.1 documentation? I can't seem to find it anywhere.
-
Is there anyway to get the Beta release before then? Also can anyone point me to the application 5.1 documentation? I can't seem to find it anywhere.
No, the only way to get it is to be part of Mitel's beta group, even if you got the software and programmer somehow you couldn't use it because you can't generate a license key for it.
Just use 6.2 documentation, it is the same and if something doesn't apply to older software it should be noted in the documentation.
-
Anyone have any update on the 6900 series phones on the 5000? Does it look like SIP mode with Phone Manager is the ONLY way these phones will be implemented in the 5000 or will they be MiNet phones?
My sales guys are just looking for some info and Mitel isn't telling them anything other than "first quarter of 2018"... nothing about SIP mode or requiring the MiVoice Office Application Server.
-
Mitel Connect is showing info on 250 V6.3 and Phone Manager V5.1 as 'coming soon'
-
Having 6900 series phones in sip mode only and required to have phone manager isn’t much of a upgrade for me...might as well use 5300 series
-
https://www.gobsb.com/pdf/technology-expo/2017/mivoice-office-phone-manager-enterprise-capabilities-smb.pdf
-
So Mitel is requiring people purchase a server and services they don't want in order to get the latest phones... This is my problem with this, and in the general direction Mitel is headed recently, of making people get something they don't want. In the last say 2 years since they have been pushing Phone Manager we have installed maybe 40-50 MiVO systems and TWO had Phone Manager installations with them, and one of those was a customer who got MiCollab and hated it so much that we had to give them an alternative or pull the system. I think we added one to an existing 5000 because their old UCA server crashed and they wanted to upgrade to something newer.
-
acejavelin,
Since we have started selling the Mitel Phone Manager we have sold quite a few of them. Of course we didn't start until 4.3, but most customers like the added features they get with it.
I am not so sure about Mitel requiring it to be sold with the 6900 sets to get all of the features, as not all of our customers bought Phone Manager, but I think it is their way of adding features without making too many changes to how the MiVO-250 functions as a standalone system; much like Intelligent Router.
I do like the fact that they will be adding some resiliency functionality in the future for the 6900 series phones which isn't even a possibility with any of the current offers. Maybe they will start making the MiVO-250 more of a SIP server than the MiVB or MiVB-X servers; who knows.
Thanks,
TE
-
So out of curiosity to anyone in the beta program for the 6900 series phones (assuming your not under a NDA), how is the functionality of the sets on the 5000 compared to the 5330/5340 series phones? We know that SIP phones on the 5000 are a bit limited, are there many functional limitations of the 6900 series on the 5000?
-
acejavelin,
I am not in the beta program, thank the phone gods, but from what I have been reading it looks as though they are expanding the SIP capabilities of the MiVO-250 with the Phone Manager MCS which is why it is a requirement I believe to get all of the functionality of the new SIP 6900 series phones.
Thanks,
TE
-
Hello
Went to a Road Show for Mitel MiVoice Office Application Suite 5.1 roadshow which touched on 6900 series support in MiVo Office 6.3.
Basically the 6900 series connects to the 250 as a SIP Endpoint with a CAT F license and will work as a 'dumb' phone.
If used in conjunction with a MiVoice Office App Suite server it basically runs a cut down Mitel Phone Manager on the screen of the 6900 phone if you have an Outlook or above user license. This allows you presence, directory access etc.
5.1 is due the end of February.
-
In my opinion the last feature-rich software release was v5.1 in 2011. Since then there has been minimal development on the 5000/250.
-
jmarcwsp1,
I don't necessarily agree with your statement there, but I am pretty sure the majority of the R&D is going to the MiVoice Business and not the MiVoice Office. With that being said there would be a noticeable difference in the amount of updates and changes to the respective product lines. We also have to keep in mind the target audience that Mitel believes that each system is designed for.
What features do you think would need to be added to the MiVO-250 to make a "feature-rich" software release for its target audience?
Thanks,
TE
-
Hey Guys,
I haven't seen anything on the site yet, but 6.3 was released yesterday.
I've been playing with it and Application Suite on my lab system today.
-
Any updates on the release?
-
Any updates on the release?
It was released on the 22nd, I have it running on 2 systems so far.
The 6900 series integration with Application Server (Phone Manager) works really well.
-
Thanks Magpie!
-
jmarcwsp1,
I don't necessarily agree with your statement there, but I am pretty sure the majority of the R&D is going to the MiVoice Business and not the MiVoice Office. With that being said there would be a noticeable difference in the amount of updates and changes to the respective product lines. We also have to keep in mind the target audience that Mitel believes that each system is designed for.
What features do you think would need to be added to the MiVO-250 to make a "feature-rich" software release for its target audience?
Thanks,
TE
G.722/Wideband audio... Better ability to manage conference calls from 5360 IP Phones (it is a wreck of a phone when making a conference call), more than 12 characters for usernames displayed on phone; ability to show direct-dial number on screen if desired; getting rid of the "OUTGOING" button and standardizing the system like every other system by utilizing "9" as the external line digit; more intuitive voicemail - ability to transfer to VM by using the envelope key and then the extension of the user; changing the redial/conference key to actually work as a conference button - rather than just a redial button; the "X" button does nothing - make that work. I could go on and on, but Mitel could spend some time and energy putting time into this system and blend it together with the smaller ShoreTel systems for greater sales.
-
G.722/Wideband audio... Better ability to manage conference calls from 5360 IP Phones (it is a wreck of a phone when making a conference call), more than 12 characters for usernames displayed on phone; ability to show direct-dial number on screen if desired; getting rid of the "OUTGOING" button and standardizing the system like every other system by utilizing "9" as the external line digit; more intuitive voicemail - ability to transfer to VM by using the envelope key and then the extension of the user; changing the redial/conference key to actually work as a conference button - rather than just a redial button; the "X" button does nothing - make that work. I could go on and on, but Mitel could spend some time and energy putting time into this system and blend it together with the smaller ShoreTel systems for greater sales.[/color]
How recent is your certification on this platform?
-
jdobnerjr,
Well, if you don't mind I will try to answer some of this for you now. I am not sure when you last worked on one of these though.
1. G.722/Wideband audio...: Look under IP Configurations there is a wideband codec called BroadVoice 32 in later versions.
2. Better ability to manage conference calls from 5360 IP Phones (it is a wreck of a phone when making a conference call): Not sure what you mean here as it works the same as all the other 53xx series phones. To be honest it has worked the same way on all phones since the Axxess days.
3. more than 12 characters for usernames displayed on phone: I haven't had too many issues with that limitation to date, but how many would you want to have; 16?
4. ability to show direct-dial number on screen if desired: There is a feature called [Outside Party Call Information has Priority] are you request a feature code to be able to change that on the fly?
5. getting rid of the "OUTGOING" button and standardizing the system like every other system by utilizing "9" as the external line digit: This has been available since the Axxess days as 8 is just a feature code and you can change it to whatever you want it to be; just like ARS is a feature code. Inter-Tel standardized on dial 8 to reduce misdialing 911 which by the way is also a feature code.
6. more intuitive voicemail - ability to transfer to VM by using the envelope key and then the extension of the user: The ability to program the buttons as you want has been around since the Axxess day and didn't change with the 53xx series phones; you can make that a DSS/BLF of Voice Mail if you want.
7. changing the redial/conference key to actually work as a conference button - rather than just a redial button: I am not sure which phone type you are referring to here but it doesn't matter as the features for Redial, Conference, and Transfer are separate in the Axxess on thru to the MiVO-250. There is a Transfer/Conference key on the 3300 is that what you are referring to?
8. the "X" button does nothing - make that work: The X button on the MiVO-250 is preprogrammed to be the Special Key [SPCL], but you can make it whatever you want it to be just like all of the other keys on the phone; except the dial pad keys that is.
I could go on and on, but Mitel could spend some time and energy putting time into this system and blend it together with the smaller ShoreTel systems for greater sales.
I am going to out on a limb here and say that you are most likely a ShoreTel technician that is struggling with this product since it isn't like the other Mitel designed systems; or the ShoreTel systems since they are similar to the Mitel systems.
I am not saying that the MiVO-250 is the greatest system out there, as I don't believe there is one, but I do think it does well for the niche it is designed to work in. They have also started coming out with a few new features in 6.3 that are similar to the 3300; i.e. Direct Page.
Thanks,
TE
-
#TErocks!!
-
jdobnerjr,
Well, if you don't mind I will try to answer some of this for you now. I am not sure when you last worked on one of these though.
1. G.722/Wideband audio...: Look under IP Configurations there is a wideband codec called BroadVoice 32 in later versions.
2. Better ability to manage conference calls from 5360 IP Phones (it is a wreck of a phone when making a conference call): Not sure what you mean here as it works the same as all the other 53xx series phones. To be honest it has worked the same way on all phones since the Axxess days.
3. more than 12 characters for usernames displayed on phone: I haven't had too many issues with that limitation to date, but how many would you want to have; 16?
4. ability to show direct-dial number on screen if desired: There is a feature called [Outside Party Call Information has Priority] are you request a feature code to be able to change that on the fly?
5. getting rid of the "OUTGOING" button and standardizing the system like every other system by utilizing "9" as the external line digit: This has been available since the Axxess days as 8 is just a feature code and you can change it to whatever you want it to be; just like ARS is a feature code. Inter-Tel standardized on dial 8 to reduce misdialing 911 which by the way is also a feature code.
6. more intuitive voicemail - ability to transfer to VM by using the envelope key and then the extension of the user: The ability to program the buttons as you want has been around since the Axxess day and didn't change with the 53xx series phones; you can make that a DSS/BLF of Voice Mail if you want.
7. changing the redial/conference key to actually work as a conference button - rather than just a redial button: I am not sure which phone type you are referring to here but it doesn't matter as the features for Redial, Conference, and Transfer are separate in the Axxess on thru to the MiVO-250. There is a Transfer/Conference key on the 3300 is that what you are referring to?
8. the "X" button does nothing - make that work: The X button on the MiVO-250 is preprogrammed to be the Special Key [SPCL], but you can make it whatever you want it to be just like all of the other keys on the phone; except the dial pad keys that is.
I could go on and on, but Mitel could spend some time and energy putting time into this system and blend it together with the smaller ShoreTel systems for greater sales.
I am going to out on a limb here and say that you are most likely a ShoreTel technician that is struggling with this product since it isn't like the other Mitel designed systems; or the ShoreTel systems since they are similar to the Mitel systems.
I am not saying that the MiVO-250 is the greatest system out there, as I don't believe there is one, but I do think it does well for the niche it is designed to work in. They have also started coming out with a few new features in 6.3 that are similar to the 3300; i.e. Direct Page.
Thanks,
TE
I'm actually a client of TechElectronics!!! :)
-
SIP R5.0 Firmware for MiVoice 6900 Phone Family & Mitel 6800 Phone Family Upgrade PDF FAQ
7.1.7 Can 6900 phones be used with any Call Manager?
No. The 6900 firmware is locked so that it will only work with Mitel platforms. If a user attempts to
configure and connect to a third-party server (e.g. Broadsoft) then the SIP accounts will not register.
7.1.8 Are 6800 phones locked if we install R5.0 or still open to all Call Managers?
The 6800 series phones are sold into Open Standards market (Broadsoft, Asterisk etc.) as well as behind
Mitel solutions (MX-ONE, 5000, 400, Telepo, etc.). They will continue to be open and R5.0 does not lock
them to Mitel platforms.
The 6900 series still not work with 3rd party SIP plattforms?
-
SIP R5.0 Firmware for MiVoice 6900 Phone Family & Mitel 6800 Phone Family Upgrade PDF FAQ
7.1.7 Can 6900 phones be used with any Call Manager?
No. The 6900 firmware is locked so that it will only work with Mitel platforms. If a user attempts to
configure and connect to a third-party server (e.g. Broadsoft) then the SIP accounts will not register.
7.1.8 Are 6800 phones locked if we install R5.0 or still open to all Call Managers?
The 6800 series phones are sold into Open Standards market (Broadsoft, Asterisk etc.) as well as behind
Mitel solutions (MX-ONE, 5000, 400, Telepo, etc.). They will continue to be open and R5.0 does not lock
them to Mitel platforms.
The 6900 series still not work with 3rd party SIP plattforms?
Correct, it will not... It only takes to Mitel systems.