Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: ralph on May 20, 2014, 08:39:38 AM
-
If you have an MOL account, be sure to check out Product Bulletin PB20140012.
It describes the new features of MCD 7.0
Ralph
-
Well, they weren't kidding... No more SX-2000 Peripheral Bay support.
-
Where did you find it? I am searching on the MKB and edocs but can't find it.
-
It's not in the KB.
I found it in the bulletins.
Ralph
-
One of the things I really like is that DID Inward Dialing Modifications can be applied to a PRI.
I've used this in ver 6.0 for SIP trunks and found it to be "friggin Awesome". No more having to use system speed dials for DID translations.
The one thing I'm not a big fan of is the new User and Device interface.
Maybe it's because I'm now so used to the old one but I found the new one to be cumbersome and annoying.
Ralph
-
I'm with you on the DID thing, I can't believe it wan't implemented years ago... Even the SX200 has had this for some time, the system speed dial way is so archaic. Of all the changes, this is the one major thing I had been hoping to get for years.
-
I'm being a bit thick here, will the DDI improvements be like a 5000, i.e just match a ddi number to a destination? or still rule based as it is in SIP?
-
someone mentioned no more per bay support. Is it I wonder the usual Mitel way that the bays will work but Mitel doesn't support them through any kind of testing? i.e how COV cards continued to work after they were no longer supported.
-
It specifically states in the product bulletin that customers using SX-2000 Peripheral Bays should not upgrade to 7.0, and should find a migration solution out of them before 6.0 is end of lifed next year, so it doesn't look like it's the same thing.
-
I'm being a bit thick here, will the DDI improvements be like a 5000, i.e just match a ddi number to a destination? or still rule based as it is in SIP?
Yep, just like the Axxess/5000 call routing tables where you define the DID==>Destination pairing. It requires setting an option in the trunk attributes otherwise the trunk follows the traditional routing options.
-
I am liking that. :D
-
I noticed that they are replacing the 5550 with a full software console aswell
Sent from my C6903 using Tapatalk
-
Would be great if someone could come up with an IP/SIP adapter for the old DNIC phones, like the old CITELink gateways. Seems like a shame to force longtime customers to buy all new sets just to stay current.
-
Would be great if someone could come up with an IP/SIP adapter for the old DNIC phones, like the old CITELink gateways. Seems like a shame to force longtime customers to buy all new sets just to stay current.
[cough] Cisco [cough]
Sent from my iPhone using Tapatalk
-
[cough] Cisco [cough]
How would that be possible with DNIC phones?
Ralph
-
5550 still available just adding another option.
Agree about the DNIC sets although I would prefer they come up with an ASUII card that supports them rather then individual devices. Thing would be recreating the hardware needed to support the phones. Don't imagine some of the chips on the MC330 cards are easy to get anymore.
-
At one point, back when the ASU II was being announced, we had found a power-point that showed a DNIC card for the ASU II, but it never came out. So we think its something they considered at some point at least.
-
5550 still available just adding another option.
From what I read 5550 will work with mivoice 7 but not 8. They will be officially end of life at the end of the year (stop manufacturing)
-
5550 still available just adding another option.
From what I read 5550 will work with mivoice 7 but not 8. They will be officially end of life at the end of the year (stop manufacturing)
Yep that is my understanding as well
-
Have to keep watch then for a program to upgrade existing 5550 consoles to the new console.
-
One thing I might add, is the document says 2000 nodes aren't supported and nothing regarding the 200. Also the update tests are available.