MiVoice Office Application Suite - Technical Manual
6900 Handset Feature Comparison
Engineering Guidelines > 6900 Handset Engineering Guidelines > 6900 Handset Feature Comparison

When using 6900 handsets in conjunction with a MiVoice Office 250, many of the features available are configured through profiles on the MCS server rather than on the telephone system. In addition, many of the features have slightly different names than those traditionally used on the MiVoice Office 250.

This section of the manual is designed to review features of the MiVoice Office 250 and provide information about what they are called and how they are configured. In addition, it highlights features of the MiVoice Office 250 that are not yet available on the 6900 handsets or have restrictions to their use.

MiVoice Office 250 Feature Supported on 6900 Handsets 6900 Handset Equivalent
ACD Agent Yes ACD agents are supported on 69xx phones with softkeys for login/logout and end wrap. Auto answer is not natively supported but can be implemented using the Phone Manager 'Auto-answer hunt group calls' feature.
Account Codes - All Calls Following Yes N/A
Account Codes - Optional Yes N/A
Account Codes - Forced No N/A
Agent Help Yes N/A
Background Music No N/A
Calling Party Name / Number Yes N/A
Class of Service Yes N/A
Do Not Disturb Yes Do Not Disturb works but not DND Override
Dynamic Extension Express Partial Push and Pull features are available on 6900 phones but work differently to 53xx phones. Calls which are pushed/pulled are sent back to ring the DEE main extension so the user can re-answer on the required device.
Group Listen No N/A
Hot Desking Yes SIP Hot Desking can be used in place of Mitel Hot Desking but, they are not interchangeable. You cannot log onto a 6900 handset with a Mitel Hot Desk Phantom or visa versa.
House Phone Yes Auto Dial - Configured using a Configuration Profile
Keymaps Yes Configured using Keymap Profiles
Language Yes Language - Configured using a Configuration Profile
Manual Forwarding Yes Accessible to the user via a softkey
Message Waiting Notification Yes N/A
Network Time Protocol (NTP) Yes NTP is supported but needs configuring in the Configuration Profile used by the 6900 handset (the setting is not inherited from the PBX). In Configuration Profiles set Time Server 1 to 3
Paging Yes Paging from 6900 handset works as normal. Paging to 6900 handsets only works from other 6900 handsets.
Record-A-Call Partial This feature does not currently work in conjunction with SIP devices. A softkey can be used to initiate a local conference to the Record-A-Call application which will successfully record the call but cannot be used to toggle the recording off.
Remote Feature Programming Partial A dedicated softkey has been provided for configuring the forward state of a remote extension, Other remote features programming is not available.
Station Monitor Yes N/A
Supervised Transfer Yes Transfer to connect is supported. Transfer to Hold/Ring are not supported.
System Forwarding Yes N/A
System Hold / Trunk Pickup No System hold is not available on 69xx phones and subsequently it is not possible to pickup trunk calls from another phone. Park keys should be used instead to move calls between users.
UCD Hunt Groups Yes N/A
Voicemail / Mailbox Yes N/A
Where the '6900 Handset Equivalent' column is set to N/A, the feature works with standard MiVoice Office 250 configuration.

MiVoice Office 250 Configuration

When configuring the MiVoice Office 250 to support 6900 handsets, the following DB programming items should be checked.

DID/E&M Receive Busy Instead of Camp-On

If this setting is enabled, when transferring a call from a 6900 handset to an extension that is already busy, it will not be possible to complete the transfer.

 

Audio for Calls Camped-On/Ringing/On Hold

By default, this setting is configured to the MOH port for the system on each device created on the telephone system. To ensure that the 6900 handsets get audible feedback when ringing other extensions that are busy, ensure there is audio on the MOH port or change this setting to ringback for all devices.

 

OAI 3rd Party Call Control

When used on the MiVO 250, 69xx phones work in SIP mode and do not support the same feature set as their MiNET/Digital counterparts.

In addition to the unsupported features listed in the previous section, not all the available ‘3rd Party OAI Call Control’ commands are supported in conjunction with 69xx phones.

Due to these 3rd Party OAI Call Control limitations, the following solutions for the MiVO 250 cannot be used in conjunction with 69xx phones:

Attendant Console and CTI Clients such as Client Go, Callviewer and Connection Assistant will not operate with 69xx phones.

Mitel Phone Manager applications will continue to operate when paired with a 69xx phone but without the ‘Merge’ call feature.

The following OAI Commands can still be used are unaffected by or can be used in conjunction with SIP phones on the MiVO 250:

Commands not listed here DO NOT work with 69xx or SIP phones (e.g. Make Call (_MC), Hold Call (_HC), Retrieve Call (_RV).