MiVoice Office Application Suite - Technical Manual
6900 Handset Connectivity
Each 6900 handset connects to both the MiVO AppSuite and MiVO 250 during normal operation:
| Connection Type | Default Ports Used | Description |
|---|---|---|
| SIP | TCP 5060 | Used for SIP communication to the MiVoice Office 250 |
| UDP 20000-20500 | Used for RTP Audio traffic between the handset and the MiVoice Office 250 | |
| Configuration Server | UDP 69 | TFTP for initial firmware download and configuration |
| TCP 8202/8203 |
HTTPS/HTTP requests from the handset to the MCS. This includes:
|
|
| TCP 80 | HTTP traffic from the MCS to the 6900 handset | |
| UDP 514 | Logging traffic from the 6900 handsets | |
| TCP 8205 | LDAP Directory Queries from the 6900 handsets |
The handsets connect directly to the MiVoice Office 250 via SIP for call control and audio. Each handset has configuration options for how to connect to the telephone system:
The SIP configuration, including authentication details is requested from the MCS configuration server during startup. The configuration server will then pass any updates to the phone when online if configuration changes are made on the server.
If the link to the configuration server is offline for any reason (server reboot, network connectivity, etc..), the 6900 handset will still be able to make/receive calls.
MCS acts as a 'Configuration Server' for the 6900 handsets. In performing this role, it provides the phone with the following:
These features are on top of the telephone system's broad range of SIP features.
MCS will provide firmware updates when they are available/configured for the handset. This can be via TFTP or HTTPS. TFTP updates are generally only used when first configuring a 6900 handset to convert it from MiNET to SIP firmware. Once this has occurred, MCS will instruct the phone to connect via HTTPS only. All future firmware requests will then be performed via HTTPS.
For more information on configuring firmware updates, please refer to the Firmware section of the Mitel Communication Service - Technical Manual.
Each 6900 handset has a set of configuration options that control how the handset operates. These configuration options can be set in one of two ways:
MCS provides configuration profiles so that options can be configured centrally and then applied to multiple handsets.
In addition, MCS controls a subset of the configuration options such as SIP connection details and Dial Plan, to ensure features such as SIP Hot Desking operate correctly, and that the handset operate as closely as possible to their MiNET and Digital counterparts.
For more information on Configuration Profiles, please refer to the Configuration Profile section of the Mitel Communication Service - Technical Manual.
Each handset has a range of softkeys that can be configured to perform any one of a number of features. Keymaps can be configured locally on the handsets, however, to take advantage of any of the MCS provided features (ACD, DND, UCD etc), the keys must be programmed via a keymap profile on the MCS.
Although keys are programmed on the phone centrally, there are two types or classes of softkey that can be add be added to a handset:
The features of phone based keys are provided locally by the handset, with no interaction from the MCS. The features of server based keys rely on updates and responses from the server to operate. Pressing a server based key will cause the handset to request information from the MCS server to action the required feature. Phone based keys will continue to operate if the link to the configuration server is down, server based keys will not.
For more information on Keymap Profiles and features available, please refer to the Keymap Profile section of the Mitel Communication Service - Technical Manual.
Each handset has the ability to show messages and notifications (some will only display in idle mode) and is used by the MCS server to display the following:
These messages are automatically sent by the MCS server to the handset and require no configuration.
In addition to the server based messages, the handset will also show the following messages to the user:
Handsets have the ability to display server provided images in a variety of scenarios:
The MCS server provides the handsets with the images. Where possible it will provide avatars for internal extensions that have been mapped to an MCS user and will also match external numbers to users based on external DEE numbers.
Screen savers and background images can be configured on the MCS and assigned to handsets using configuration profiles.
The handset will cache images locally and will request them again when this cache expires.
Each handset has a feature rich directory facility which allows the user to search for contacts across multiple directory sources at the same time.
The directory sources available include:
The LDAP facility can be used to configure the handsets to lookup an existing customer database.
The CSV import facility is currently used by the MCS to provide the handsets with Internal and System Speed Dial directories from the telephone system.