Firmware Version Upgrade 1

[SNJQuintin]

Good morning. We are currently running a 3300 with 13.2.0.17 firmware on it (7.2).

Can someone point me in the direction of documentation on the latest version, and what improvements/features are in the newest version? Also looking at what the IP Console 5550 looks like with the latest release (or whatever it is called now).

Thanks so much!

Q

 

[meneerB]

V9 is the newest.
5550 does not work anymore.
Upgrade to mivoice business console v9.
Interface is identical, differences is that you have to use usb headsets or handsets.

Btw. 5550 worked very stable.
Mivbc is horrible. Crashes a lot and lots of one way audio issues

 

[SNJQuintin]

Thanks @meneerB. So does 5550 work with V9 then, I take it from your post, that if you upgrade to V9, that 5550 no longer works...I'm OK leaving that machine as Win7, it has no internet access, or anything opened on it, except the 5550 IP Console...but if we can't update the phone system, and leave the 5550, that would be unfortunate...

Thanks,

Q

 

[meneerB]

Reading my post again could cause some confusion

The latest MCD is called MiVoice, which is v9.
5550 consoles do not work anymore when using mivoice v9,
So you have to upgrade the console to mivoice business console (also) v9.

Mivbc v9 runs with USB headsets.

So win7 has nothing to do with that.

I don't know what requirements there are for upgrading a 3300 to v9.
Maybe a technical user can advice.

But if you have esx/hyperv, you can also upgrade to mivb v9 virtual.

PS. Our v8 on a new 3300 used as an internal gateway, is much slower then the virtual mivb v8 with 2000 users

 

[SNJQuintin]

@meneerb. Thanks, very informative

I meant leaving the existing 5550 on a Win7 machine (it won't run on Win10). If we want to upgrade that workstation to Win10, we have to move to Mivbc.

I was hoping that I could still update the MCD to v9, and NOT need Mivbc...doesn't look that way though. Which is too bad, because Mitel won't upgrade the IP Console to Mivbc under our maintenance agreement...so we have to pay for that software, plus, not sure I like the idea of moving to a USB handset...

Thanks again, that gives me food for thought

 

[TheMitelGuy]

Hello every body! Happy Thanksgiving to everyone in the U.S.

[highlight #FCE94F]For SNJQuintin:[/highlight]
---------------
Just curious if you considered the Mitel 5540 IP Console? Granted there is a informational loss when going to the 5540 IP Console (i.e. you cannot get DSS/BLF status like you can with the 5550 IP Console), it does provide similar functionality from a call processing perspective and it is a true VoIP/MiNET hardware endpoint. You can use headsets with it as well (wired or wireless). The functionality between the 5540 and the 5550 are identical - except for the status information that the 5550 IP console provides about users in the system. It may not be ideal in this case, but it is a possible solution if you are looking for a dedicated console device that does not use USB handsets/headsets. It's also not reliant on any OS - you just plug the console in, program it and use it. Rarely a problem.

Let us know if you need other suggestions around the console. I'm positive we can find you a viable solution. Unfortunately you won't be able to continue to use the 5550 IP Console on MiVB (formerly MCD) on 9.x.

[highlight #FCE94F]Just a question for the group:[/highlight]
------------------------------
Would you ever consider installing the MiVoice Business Console software INCONJUNCTION with a 6900 series IP phone? I.e. you would get identical benefits as the 5550 IP Console/MiVoice Business Console (MiVBC), but you would use the MiNET endpoint to stream the audio. So the 6900 series phone and the console software would work together - similar to a 5550 TKB, but just a few more keys on the phone (that you probably wouldn't be able to use)..... Does this suggestion make sense to folks? Do you like it - or just leave it the way it is (no real changes to MiVBC)....????

 

[meneerB]

Greetings to you too TMG!

I even considered using micc.

For us, the biggest issue is the internal phonebook.
Although we manually 'import' the mivb directory to the phonebook, we do need it with a few thousand employees and lots of operators.

BTW it's a shame you have to choose: or a direct link to the mivb phonebook, or a 'console group' phonebook.
Ridiculous that it's not integrated, because we heavely use both:
How hard can it be to implement 1 search field and query both directories.


To all, maybe use a non-Mitel product?

https://www.pridis.com/products/connecsy-enterprise/

https://www.aci-tn.com/productcatalog/mitel/products/business-phones/attendant-consoles.aspx

http://www.intertel-systems.co.uk/D...-Guide-Manual/InterTel-Attendant-Console.aspx

 

[TheMitelGuy]

Hi meneerB!

Question for you... You said "For us, the biggest issue is the internal phonebook. Although we manually 'import' the mivb directory to the phonebook, we do need it with a few thousand employees and lots of operators."

Why did you say this? Just to be clear - you are talking about importing a "phonebook" into the MiVoice Business Console Software? Is that what you are saying you do? If that is the case, why do you have to do this? What is not provided by the regular updates MiVB provides to MiVBC? Again, maybe I don't understand you, so if I'm mistaken, my question won't make any sense and can then be ignored.

Cheers!

 

[SNJQuintin]

Hi TMG. Thanks for your comments and suggestions. I am afraid that the 5540 wouldn't work for us, as the BLF fields are used extensively by our receptionist.

So, I guess the question for you is then, would our receptionist be able to use the same functions as she does now with the MiVoice Business Console software, and a USB handset? I guess then in order to upgrade our phone system to the latest MCD version, we would need to spend some $$ on the IPConsole, both software and hardware, as I understand that our Mitel software agreement does not include the MiVoice Business Console software...

Thanks again for your input.

Q

 

[meneerB]

TMG,
Mivbc has 2 modes: use the mivb directory, and that one only,
Or
Use a local (shared between the mivbc's) phonebook.

We have lots of extra numbers, so numbers the normal users should not use or see.
E.g. private cell numbers of users, pizza, etc, etc.
So we use option 2.
The operators are now also able to update that phonebook.

But the big disadvantage is that they also have to manually update that phonebook changes we do on the mitel (ict admins)

I would prefer to have both.
Commercial products are available, but this cost money.

Technically I probably could do some automation:
Daily export e.g. the users and devices and some others
And merge that with the operator phonebook.
And use the merged phonebook in the mivbc.

Maybe I have time for that project next year;-)