acejavelin

This is an overview of new enhancments in the 3300ICP Release 10 software, codenamed "Series X" and now officially called Mitel Communications Director v4.0 (MCD 4.0). It is probably one of the biggest changes in software from one release to another ever done.

If anyone would like to see the full release notes, shoot me a PM and I can email then to you.

Enhancements introduced in Mitel Communications Director (MCD) 4.0 include:
• Personal Ring Groups - an association of two or more devices (max of 8 ) under a single Directory Number (DN), are added in this release. The devices ring simultaneously (Ring All) when called.
• External Hot Desk User – Hot Desk functionality is extended to external devices, such as cell phones, allowing such devices to appear as another extension on the system and to access system resources, including voice mail and outgoing trunks.
• Group Presence - allows members of hunt, ring, personal ring, or ACD groups to control their availability to take group calls.
• Variable RTP – Sip voice stream (RTP) packet rate on the 3300 ICP can now be configured to provide improved inter-operability with SIP service provider networks.
• ACD enhancements - The following enhancements have been made to the Automatic Call Distribution (ACD) feature:
o Hot desk ACD agents can now log into any Hot Desk or ACD enabled set by entering their Agent ID followed by their User Personal Identification Number (PIN). After the hot desk ACD agent logs into the set, the agent has access to his or her set profile and the ACD phone functions.
o Hot desk ACD agents can use the hot desk Feature Access Codes (FACs) to login to, or logout from, an agent session.
o Note: ACD Call Centers Currently using PrairieFyre ACD Reporting Package Must check with PrairieFyre for the Lastest Release to Support MCD 4.0
• ACD Licenses Dynamically allocated - In MCD Release 4.0 and later, ACD licenses are dynamically allocated to ACD agents from the pool of available licenses. When an agent (either a traditional agent or hot desk ACD agent) logs in, the agent is given a license from the available pool of licenses. Tradition ACD enabled sets still require ACD licenses.
• Back up and restore enhancements - You can now Back up the system database to a file on an FTP server or restore a database file from an FTP server to the system.
• Administrative groups - The System Data Synchronization (SDS) feature allows you to share data among administrative groups. SDS Administrative Groups support Multi-Node Management applications. In the Administrative Group Assignment form, you can move elements into groups and share data among the group members at the administrative group scope. Support for network groups has also been added. However, in MCD Release 4.0, all elements belong to one network group.
• Multi-Node Management - applications are supported for SDS Administrative Groups. The following applications are available:
o Application Reach Through provides programming access to the forms on all the member elements in an Administrative Group from a single System Administration Tool session on any element in the group.
o Fault Management provides the overall alarm status of the elements in an Administrative Group, and a summary of the alarm severity for all the member elements in an Administrative Group.
o MNM Backup and Restore allows you to perform database backups and restores from a System Administration Tool session on any member element in the Administrative Group. From a System Administration Tool session on a local element, you can
 back up the database of another member element, or back up the databases of all member elements in the Administrative Group to an FTP server.
 restore a database to any element in the Administrative Group.
o System Administration tool enhancements to support the new Multi-Node Management applications, These enhancements appear in the user interface even when Multi-Node Management applications are not used:
 The Alarm Status shown at the top of the System Administration Tool frame is displayed in the format of "Node <Login node name> Alarm Status <date time>".
 The Selection menu for the form tree displays the name of the login node in brackets
 The title of a form that is displayed in the right frame includes the name of the login node in the format of "<Form name> on <Login node name>".
 The DN to search field allows you to search for a directory number across the databases of the Administrative Group elements.
 The Show form on menu appears in the top right corner of the form. If Multi-Node Management is not supported, "Not Accessible" appears in the menu.

• Remote Directory Number (RDN) Synchronization ( or known as Common Distributed Data model)
-supports the synchronization of telephone directory entries across all the element databases in a network or cluster without the requirement for OPS Manager. If a network or cluster has been migrated to support Remote Directory Number (RDN) Synchronization, any telephone directory entries that you add, modify, or delete at an element through the System Administration Tool are automatically distributed as shared data updates to the other elements. The updates are distributed via System Data Synchronization (SDS).
 Local only DN - Within a cluster, you can program directory numbers that are local only to the member elements. A user on the same element can call a local-only directory number by just dialing its extension number. However, a user on a remote element cannot. To call a local-only directory number, a user on a remote element must dial the CEID digits followed by the local-only extension digits.
• Embedded Resilient Device Support - allows you to configure IP Phone and IP Console resiliency from the System Administration Tool of the local (home) element. OPS Manager is no longer mandatory to support device resiliency.

Important Note:
1. Traditional way of updating Telephone Directory via OPS Manager is known as “Classic” database. 3300 Database converted to support RND synchronization/Common Distributed Data model is not compatible with “Classic” model or vice versa.
2. 3300 system in Classic mode can be converted to Common Distributed Data mode.
3. 3300 system in Common Distributed Data mode cannot be converted back.
To convert back to classic mode, one must perform Full Installation and select “Classic” mode. Please see screenshot at the last page of this document for proper selection.
4. During Full Installation, the selection between Classic mode vs Common Distributed Data mode is prompted (See screenshot at Appendix A – last page of the document)
5. For Online/Offline upgrade, 3300 system remains in Classic mode by default.
6. “Import Spreadsheet” between Classic and Common Distributed are not compatible.
7. Compatibility table between 3300 system /database in classic and non classic mode as follows:

3300 System Mode 3300 database from
Classic system 3300 database from
Common Distributed Data system
Telephone Directory Sync. Via SDS
(known as Common Distributed Data) Cannot be restored OK to restore
Telephone Directory Sync. Via OPS manager ( known as Classic) OK to restore Cannot be restored

Note: If you have a standard template database in Classic mode ( i.e. from Rel 9.0, make sure that you select Classic Mode)

• Time Zone, Daylight Savings Time, and Simple Network Time Protocol Synchronization - Supports automatic synchronization of time and date, including Daylight Savings Time, between 3300 ICP controllers, and supports meaningful timestamps in logs. 3300 ICP controllers synchronize with an NTP server in the network based on Coordinated Universal Time (UTC).
• CESID for SIP – SIP phone interoperability between the 3300 ICP and third-party devices is improved and support for CESID and peer trunk status is added.
• ACD Express Groups - Call answer groups similar to a Hunt Groups and equivalent to an ACD 2000 path containing a single ACD 2000 Agent Skill Group. ACD Express Groups also have more limited RADs, embedded media, and Interflow.
• HTML Toolkit Release 2 - Support for applications developed using the HTML Toolkit (Release 2) is now licensed on a per user (DN) basis. Applications are assigned in the User Configuration and Multiline IP Set Configuration forms, which have been expanded to support the additional capabilities provided by the toolkit.
• Online upgrade support for CX/CXi and AX - One-step online upgrades are now supported on smaller platforms.
.

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.