MiVoice Office Application Suite - Technical Manual
6900 Handset General Settings
Configuration > Features > Mitel 6900 Handset Support Overview > 6900 Handset General Settings

The following settings relate to some of the interaction between the MCS and any Mitel 6900 Handsets.

Setup PIN

The setup PIN is used to when rolling out 6900 handsets. It provides access to the setup dialog which allows an engineer to configure a newly installed 6900 handset and link it to a SIP device on the telephone system. The PIN can be configured to be any combination of keypad digits.

Default: ***

 

Send DND Notifications

When 6900 handsets make calls to other extensions (MiNET, Digital, SIP or Analogue) that are in DND, they show a 'Busy' message on the screen and do not give the caller any information about the DND state.

MCS provides the DND (and Presence information if relevant) to the caller so that they can see why they are receiving a busy response to the call.

Default: Enabled

The timeout on the Toaster style notification is not currently configurable.

 

Send Hunt Group Camp-on Notifications

When calls are queuing at ACD/UCD hunt groups, MCS can notify logged in members that there are calls waiting.

This is a system-wide feature currently and cannot be enabled/disabled on a per hunt group basis. This feature does not work on ACD Extension groups, only ACD Agent Groups.

Default: Enabled

The timeout on the Toaster style notification is not currently configurable.

 

Show Chat Notification Preview

When enabled, a preview of the chat message received will be displayed in the notification toaster that displays on the 6900 phone.

Default: Disabled

Chat notifications will appear on the phone even when it is locked.

 

Override Dial Plan

The MCS server will provide each 6900 handset with a dial plan based on the Dial Plan configured on the server. This dial plan is designed to allow the user to dial internal numbers, external numbers and service codes (including emergency numbers). The dial plan that is automatically sent to the handset can accommodate 3 & 4 digit dialing and will automatically workout the length of internal extensions based on the devices configured.

If 3 digit dialing is required, ensure all internal extensions that begin with the same number are the same length. For example, for 3 digit dialing of extensions beginning 1, ensure all extensions beginning 1 are 3 digits long. This includes the built in modem extension.

In addition, the dial plan is designed so that the user does not need to enter the outgoing access code, it will automatically be entered for them when the dial plan detects an external number has been entered.

To manually assign a dial plan, enable the override and enter the dial plan required.

Default: Disabled

 

The outgoing access code will only be automatically entered if the external number being dialed starts with the toll digit. To dial numbers without the toll digit, the outgoing access code must still be entered.
The default Dial Plan for dialing any number is 'x+#|xx+*'
The Live Dialpad and SIP Dial Plan Terminator can be used to force the phone to evaluate the dial plan after every digit is entered and dial automatically when a match is made. Please refer to the Configuration Options section for more information.
Please refer to the 6900 Series Administration Guide for information on 'sip dial plans' and how to configure them.
By changing the Dial Plan passed to the phones, it is possible to prevent the handset from being able to make emergency calls. Ensure that all dial plan changes are thoroughly tested before rolling out.

 

Enable SRTP on Remote Handsets

When enabled, the MCS server will instruct any remote 6900 handsets to use SRTP for audio connections back to a MiVoice Border Gateway.

For more information on enabling SRTP, please refer to the Manual Teleworker Provisioning.

If SRTP is not enabled on both the MBG configuration and the MCS configuration then calls will fail. The handsets will be able to make calls but not receive them.

Default: Disabled

 

Auto Detect Non-Internal Addresses as Remote 

When enabled, the system will class any handset that does not have an IP address in the range 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 as being a remote handset.

Handsets that are connecting through a MiVoice Border Gateway (MBG) will show up with internal addresses. To correctly identify these as remote, the internal address(es) of the MBG will need to be configured in the Phone Systems section.

Default: Enabled

 

Send Phone System Alarms to Admin Phones

When enabled, any phone system alarms will automatically be send to Mitel 6900 Handsets that have been configured as Administrator on the telephone system.

Default: Enabled

For more granular control over which alarms get sent to handsets, use the Alarm Notification feature.

 

Call Mode for Softkey Screens

This setting controls the behavior of the phone if a call starts alerting when the user is in a softkey screen (changing presence or DND for example). If set to 'Notify via Toaster', the user will be left in the softkey screen but will be notified of the call via a toaster message. If set to 'Call Overrides Softkey', the softkey screen will be closed down and the call details screen will be displayed.

Default: Notify via Toaster

 

Device BLF Label Option

This settings controls the automatic labeling of BLF softkeys. The description or the username from the telephone system can be used as a BLF softkey label.

Default: Description

If the device description contains a comma. It is assumed that the format is "last name, first name". This will automatically be converted to "first name last name" before being applied to a BLF label.

 

Display Voicemail Notification on User BLF Softkeys

When enabled, the number of new voicemails notifying a user will be displayed on any User BLF keys that are configured for the user on other phones.

Default: Disabled

 

Use HTTPS for Local Phone Softkeys

By default, all phones are configured to use HTTPS for softkey requests made to the MiVoice Office Application Suite server. This adds an overhead in processing time to each softkey press. Disabling HTTPS on softkey press can improve the user experience and reduce the processing overhead. This option only applies to local phones, not remote.

Default: False

HTTPS will still be used for configuration updates if disabled for softkey requests.

 

Use Enhanced BLF Context Menu

When enabled, users are presented with contextual call control, queue and message options when they press a User or Extension BLF key.

Default: True

This feature can be disabled on an extension by extension basis, please refer to the Phones section for more information.

For more information on the Enhanced BLF Context Menu, refer to the 6900 Softkey Feature Screens section.

 

Leave a Station Message

If 'Use Enhanced BLF Context Menu' is enabled, this setting controls whether the option to leave a station message is displayed on the context menu.

Default: False

 

Enable Multicast DNS

With Multicast DNS enabled, the Auto Discovery feature can be used to enable out-of-the-box 6900 phones to automatically find the MiVoice Office Application Suite server without the need to configure any DHCP options.

Default: True

 

Call History Location

This setting controls whether the call history displayed on 6900 phones is provided by the MCS server or locally by the phone. If 'Server' is selected, a user based call history will be provided by the server to show calls for any of a user's extensions.

Default: Server

A reboot of phones is required before a change to the call history settings will take effect.

 

Exclude Missed Hunt Group Calls From Call History

When excluded, only hunt group calls which are answered will appear in the call history, not missed calls.

Default: True

This setting affects both 69xx and Phone Manager call history.
On All-ring hunt groups (UCD & ACD), missed calls will only show in the first extension's call history.

Use the MCS as local NTP Server

When enabled, the MCS server will enable the Windows Time service on the local server as an NTP server. All local phones will then be provided the IP address of the MCS server as a backup time server (Configuration Time Server 3 is used for this).

Default: True

 

Directory Access

The settings below control the use of LDAP to deliver server based Contact Directories to 6900 phones. By default, users will automatically have access to the phone system directory and their own Phone Manager personal directory through the built in CSV directories of the phone.

In addition to the telephone number fields, the following server directory fields are passed to the phone:

Directory Field Name Phone Field Name
Name First Name
Field 1 Company
Field 2 Job Title
Field 3 Work Address Street
Field 4 Work Address City
Field 5 Work Address State/Province
Field 6 Work Address Zip/Postal Code
Field 7 Work Address Country
Field 8 Email 1
Field 9 Email 2
Field 10 Email 3
The directories on phones will get updated once every 24 hours, new entries will not appear until the phone updates. Check the 'Auto Resync Time' configuration for information on when this occurs.

Make Global Directories available to 6900 handsets

When enabled, 6900 phones will be given access to the global contact directories of the server using an LDAP query. The phones will download a copy of the directories on startup and will use them for contact matches on call or directory searches by the user. Use the Directory Access setting below to restrict which directory the phones have access to.

Default: Enabled

 

Directory Access for Remote Phones

Control how directories are made available to remote phones; No Access, CSV or LDAP. CSV is recommended for remote phone connecting over an unsecured network due to the way LDAP is implemented. Instead the CSV option can be used to merge the server contacts with the local user's contacts which are then provided in CSV format over a secure channel.

Default: None

The LDAP query used to provide server contacts to the phone is not secure. This interface should not be enabled for phones connecting over an unsecured network.

 

Directory Access (& Specified Directory)

This setting provides a way to select which directories are available. By default, all directories are available. When this mode is selected, the system will automatically filter the directories searched based on user permissions. If a specific directory is selected, all phones will be given access to it. Each phone is restricted to only accessing 5,000 directory items. By choosing a specific directory, the number of contacts the phones have access to can be restricted to ensure the 5,000 item limit is not breached.

Default: All Directories

 

Enable Asynchronous LDAP Queries

6900 phones can query the contact directories in one of two ways:

When in cached download mode, the phone will download all contacts from the server and make the local copy available to users when searching the directory or performing contact matches on telephone calls. This method provides the best user experience but is not suitable when there is a large number of contact records (specifically 5,000 records or more). When this threshold is reached, asynchronous queries should be enabled.

When asynchronous mode is enabled, users will still be able to search for contacts using but contact matches on telephone calls will no longer occur.

Default: False (cached mode)

If asynchronous mode is not enabled when there are large numbers of contact records, delays will be experienced by the user while the phone is performing contact match searches.