Mitel 6800/6900 Series SIP Phones

Transcription

1 Mitel 6800/6900 Series SIP Phones REV Release Notes

2 NOTICE The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks Corporation (MITEL ). Mitel makes no warranty of any kind with regards to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The information is subject to change without notice and should not be construed in any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes. No part of this document can be reproduced or transmitted in any form or by any means - electronic or mechanical - for any purpose without written permission from Mitel Networks Corporation. Please iplegal@mitel.com. TRADEMARKS The trademarks, service marks, logos and graphics (collectively "Trademarks") appearing on Mitel's Internet sites or in its publications are registered and unregistered trademarks of Mitel Networks Corporation (MNC) or its subsidiaries (collectively "Mitel") or their respective owners. Use of the Trademarks is prohibited without the express consent from Mitel. Please contact our legal department at legal@mitel.com for additional information. For a list of the worldwide Mitel Networks Corporation registered trademarks, please refer to the website: Customer's use of this product and/or software shall be in accordance with the EULA and /or other accompanying licensing terms. Mitel 6800/6900 Series Phones Release Notes REV00 August 2017, Trademark of Mitel Networks Corporation Copyrights 2017, Mitel Networks Corporation All rights reserved 2

3 Table of Contents About This Document... 5 Release Notes Topics... 5 General Information... 6 Release Content Information... 6 Hardware Supported... 6 Bootloader Requirements... 6 Important Firmware Information Series SIP Phone Firmware Upgrade Information... 8 M685I and M695 Expansion Module Firmware Upgrade and Downgrade Information... 8 New Features in Release Additional Information SIP Support for Select Mitel Call Managers SIP to MiNet Conversion MiNet to SIP Conversion Autoconfigure Line 1 and Line 2 Softkeys Blinking Softkey Icon Support for BLF Keys Blinking Softkey Icon Support for Line Keys Line Labeling with Caller ID Hardkey Remapping Voic Hardkey Support Self-Avatar Display on Idle Screen Auto-Audio Mode Bluetooth Connections Cell Phone Call Handling New Mobile Softkey Configuration Mobile Contacts Sync Hot-Desking and Mobile Integration Support for Bluetooth Cordless Handset Bluetooth Handset Battery Level Display Phone Auto-lock and Unlock on Mobile Proximity

4 Appendix A Supported Headsets Contacting Mitel Support

5 About This Document This document provides details on the new features, enhancements to existing features, and/or issues resolved for the Mitel 6800 Series (6863i, 6865i, 6867i, 6869i, and 6873i) and 6900 Series (6920, 6930, and 6940) SIP Phones for Release Note: This release applies to the phone models mentioned above only. Note: Release is the first release supporting the 6900 Series SIP Phones, the latest addition to Mitel s SIP product portfolio. For detailed information about features associated with each phone, and for information about how to use the phones, see your model-specific SIP Phone Installation Guide and the SIP Phone User Guide. For detailed information about the advanced features, see the Mitel 6800/6900 Series SIP Phones Administrator Guide and the Development Guide XML API For Mitel SIP Phones. Release Notes Topics This release notes includes the following topics: General Information Firmware Upgrade and Downgrade Information New Features in Release Additional Information Contacting Mitel Support 5

6 General Information Release Content Information This section provides release content information about the Mitel 6800 and 6900 Series SIP Phone firmware. Model Release Name Release Version Release Filename Release Date 6863i Generic SIP REV00 August i Generic SIP REV00 August i Generic SIP REV00 August i Generic SIP REV00 August i Generic SIP REV00 August Generic SIP REV00 August Generic SIP REV00 August Generic SIP REV00 August 2017 Hardware Supported This release firmware is compatible with the following Mitel SIP portfolio products: 6863i 6865i 6867i 6869i 6873i Bootloader Requirements 6 This release firmware is compatible with the following Mitel SIP portfolio product bootloader versions: 6863i: Boot and later 6865i: Boot and later 6867i: Boot and later 6869i: Boot and later

7 6873i: Boot and later 6920: Boot and later 6930: Boot and later 6940: Boot and later 7

8 Important Firmware Information 6800 Series SIP Phone Firmware Upgrade Information CAUTION: DO NOT ATTEMPT TO UPGRADE YOUR PHONE TO RELEASE FROM A RELEASE LOWER THAN WHEN IN WEB RECOVERY MODE. DOING SO WILL CAUSE YOUR PHONE TO BECOME NON-OPERATIONAL. M685i and M695 Expansion Module Firmware Upgrade and Downgrade Information If you upgrade your phone from a release lower than to Release and your phone has an M685i Expansion Module attached, the expansion module will also upgrade to align itself with the new UI changes. If you are downgrading your phone from Release to a firmware version of Release or earlier and your phone has an M685i Expansion Module attached, you must first downgrade to Release Hot Fix or Service Pack and then to the Release or earlier firmware version. This ensures that the UI of the M685i Expansion Module is always aligned with the phone UI. Do not plug an M695 into a 6800i model. Ensure that an M695 is plugged into a 6920, 6930 or 6940 Phone. The firmware pushes a new hardware ID into the M695, M685i, and M680i Expansion Modules which requires PKMs to be plugged to the correct phone models. With release, PKMs upgrade to version This version supports a new UI as per release. If you downgrade the phone firmware to SP1 GA release or earlier versions, the PKM does not downgrade which causes a mismatch of UI and icons. This is a known issue. PKM version downgrade is not supported. Note: M695 PKMs are supported only on the 6900 models. M685i and M680i continue to be supported on 6800i models only. M685i and M680i are not supported on 6900 models. 8

9 New Features in Release Mitel 6800/6900 Series SIP Phones Release Notes This section describes the new features in SIP Phone Release The following table summarizes each new feature and provides a link to more information about the feature. Each feature also specifies whether it primarily concerns administrators, users, or XML developers. Feature 6900 SIP Support for Select Mitel Call Managers (For administrators) SIP to MiNet Conversion (For users and administrators) Autoconfigure Line 1 and Line 2 Softkeys (For users and administrators) Blinking Softkey Icon Support for BLF Keys (For users) Blinking Softkey Icon Support for Line Keys (For users) Description In Release 5.0.0, the 6900 Series SIP phones will operate with select Mitel Call Managers. The following call managers are supported: MiVoice 5000 MiVoice MX-ONE MiVoice Office 400 New for all 6900 Series SIP Phones In Release 5.0.0, it is possible to roll back 6900 Series phone models from SIP to MiNet. New for all 6900 Series SIP Phones The Line 1 and Line 2 softkeys are autoconfigured in the 6900 Series SIP Phones because there are no Line 1 and Line 2 hard keys. New for all 6900 Series SIP Phones With Release 5.0.0, the 6873i and 6940 phones provide blinking softkey icons for the Busy Lamp Field (BLF) keys. This feature allows slow blink when on hold state and fast blink for ringing state. New for all 6873i and 6940 SIP Phones With Release 5.0.0, the 6873i and 6940 phones provide blinking softkey icons for the Line keys in regular and in shared mode. This feature allows slow blink when on hold state and fast blink for ringing state. New for all 6873i and 6940 SIP Phones Line Labeling with Caller ID In Release 5.0.0, caller ID is displayed on the top softkeys and on the expansion modules (M685i and M695) for incoming calls. For 6873i and 6940 phone models, the caller ID is displayed in the two lines; one displaying name and other, the number. (For administrators) A new configuration parameter line show caller id is introduced which when enabled displays the caller ID on the softkeys. New for all 6800 and 6900 Series SIP Phones 9

10 Hardkey Remapping (For users and administrators) Voic Hardkey Support (For users) Self-Avatar Display on Idle Screen (For users and administrators) Auto-Audio Mode (For users) In Release 5.0.0, the hardkey layout for 6900 Series SIP Phones is redesigned and mapped as follows: Hold key is hardkey 1 Redial is hardkey 2 Goodbye Key is hardkey 3 Options Key is hardkey 4 Voic is hardkey 5 Callers is hardkey 6 Directory is hardkey 7 Note: Goodbye and Options keys cannot be remapped. New for all 6900 Series SIP Phones In Release 5.0.0, the 6900 Series SIP Phones provide a hardkey for configuring voic . In 6800 Series SIP Phones, the voic is configured through softkeys. New for all 6900 Series SIP Phones In Release 5.0.0, the 6873i and 6940 phone models allow users to display a self-picture ID on the idle screen attached to the focused line. A new configuration parameter idle screen avatar is created, which when enabled displays the line picture. New for all 6873i and 6940 SIP Phones In Release 5.0.0, the 6940 phone model supports auto-audio mode when pairing with a USB or Bluetooth headset. New for 6940 SIP Phones Bluetooth Bluetooth Connections (For users) New Mobile Softkey Configuration In Release 5.0.0, the 6900 Series SIP Phones support Bluetooth connections to several devices specifically the Bluetooth handset, Bluetooth headset, and mobile phones. New for 6930 and 6940 SIP Phones Release supports Bluetooth mobile integration between a SIP phone and a mobile phone. The user can configure a new softkey type mobile for BT phones on top softkeys or on LCD expansion modules through configuration files and the web UI. (For users and administrators) New for 6930 and 6940 SIP Phones 10

11 Cell Phone Call Handling In Release 5.0.0, only incoming calls are supported through the cellular network. When a cellphone contact is dialed, the outgoing call is routed through the SIP landline and not through the mobile carrier network. (For users) Mobile Contacts Sync (For users and administrators) Hot-Desking and Mobile Integration (For users and administrators) Support for Bluetooth Cordless Handset (For users) Bluetooth Handset Battery Level Display (For users) Phone Auto-lock and Unlock on Mobile Proximity (For users and administrators) New for 6930 and 6940 SIP Phones With BT-mobile integration, users can access the mobile phone directory and import mobile contacts into the SIP Phone. The mobile contacts are then available for look up and dial and for identification through caller ID. New configuration parameters mobile contacts enabled and mobile contacts name are created which allow users to enable or disable the mobile contacts import and allows to give a custom name to the mobile contacts folder in the directory. New for 6930 and 6940 SIP Phones In Release 5.0.0, mobile integration is supported for hot-desking accounts. After logging in, hot desk users can pair, connect, and import contacts from the mobile phone. New for 6930 and 6940 SIP Phones The BT Cordless Handset is supported in Release 5.0 and is a standard accessory for the 6940 SIP phone and an optional accessory for the 6930 and 6873i SIP phones. New for 6940, 6930 and 6873i SIP Phones In Release 5.0.0, users can view the battery level of the BT handset through icons in the status bar and battery warning or critical level toaster notification or indication on the screen saver. New for 6930, 6940 and 6873i SIP Phones With mobile integration in Release 5.0.0, the phone automatically locks or unlocks after a preconfigured delay when a paired mobile phone is disconnected or reconnected. This feature can be configured through the following new configuration parameters: proximity lock proximity unlock proximity lock delay proximity unlock delay New for 6930 and 6940 SIP Phones XML Background color change for XML UI The background color for the following UI XML 11

12 objects objects can be set to a different color from white: TextMenu TextScreen FormattedTextScreen ImageScreen ImageMenu InputScreen IconMenu For more information, see the Development Guide, XML API for Mitel SIP Phones. (For XML developers) Add API to access toaster notifications New for 6867i, 6869i, and 6873i and all 6900 Series SIP Phones A new toaster notification is introduced to display screen notifications for XML notifications. For more information, see the Development Guide, XML API for Mitel SIP Phones. (For XML developers) Undisrupted XML session on incoming call (For XML developers) Simulate keypress for expansion module pages (For XML developers) New icons for MiNet like softkeys New for 6867i, 6869i, and 6873i and all 6900 Series SIP Phones A new tag is created in XML objects to keep the XML session running when there is an incoming call even if the XML object is in LockedIn mode. For more information, see the Development Guide, XML API for Mitel SIP Phones. New for all 6800 and 6900 Series SIP Phones This feature allows a XML application to simulate the keypress of expansion module pages to position the expansion module on the required page. For more information, see the Development Guide, XML API for Mitel SIP Phones. New for all 6800 and 6900 Series SIP Phones The following new predefined icons are added to the base firmware: "Icon:CallFwdActive" "Icon:CallFwdInactive" "Icon:DndActive" Icon:DndInactive" "Icon:MakeBusyActive" "Icon:MakeBusyInactive" "Icon:NightServiceActive" "Icon:NightServiceInactive" "Icon:PhoneLockActive" 12

13 "Icon:PhoneLockInactive" "Icon:StateActive" "Icon:StateActive2" "Icon:StateInactive" "Icon:RecordingOn" "Icon: RecordingOff" For more information, see the Development Guide, XML API for Mitel SIP Phones. (For XML developers) XML enhancements New for all 6867i, 6869i, and 6873i and all 6900 Series SIP Phones In Release 5.0, enhancements are made on the XML phone softkey and picture ID. For more information, see the Development Guide, XML API for Mitel SIP Phones. (For XML developers) New XML command to delete mobile directory and disable Bluetooth pairing New for all 6867i, 6869i, 6873i and 6900 Series SIP Phones In Release 5.0, a new XML command Command: ClearMobile is introduced to delete mobile contact directory and disable the Bluetooth pairing with all Bluetooth devices (including mobile phones), except for the Bluetooth handset. For more information, see the Development Guide, XML API for Mitel SIP Phones. (For XML developers) New for 6930 and 6940 SIP Phones 13

14 Additional Information 6900 SIP Support for Select Mitel Call Managers In Release 5.0.0, the 6900 Series SIP phones will operate with select Mitel call managers. The following call managers are supported: MiVoice 5000 MiVoice MX-ONE MiVoice Office 400 The Mitel SIP phone checks if the phone is connected to any of the above-mentioned call managers and if not supported, the account is blocked and the phone returns a SIP 606 error. SIP to MiNet Conversion In Release 5.0.0, it is possible to roll back 6900 Series phone models from SIP to MiNet. This release supports SIP to MiNET conversion through the following methods: DHCP options Firmware Download Server configured through TUI or configuration file Manual firmware update through Web UI Note: Using these conversion methods, 6900 SIP Series phones search for SIP firmware files (69xx.st) and if not found, search for MiNet firmware. Procedure for SIP to MiNet Conversion In Release 5.0.0, it is possible to roll back 6900 series phone models from SIP to MiNet. The SIP image has a key to encrypt the MiNet image header and supports decryption of the MiNet image. Following is the procedure for 6900 series SIP to MiNet conversion: 1. Copy and save the MiNet (MINET_69XX-enc.st) on TFTP server directory for each 6900 series phone model. 2. From the SIP phone's Web UI, navigate to Advanced Settings/Firmware Update form and enter respectively: Filename as MINET_69XX-enc.st, Download Protocol as TFTP and the TFTP server IP address information (add path and port if required) and press Download Firmware. Note: During TFTP download of a MiNet firmware file exceeding 32M, ensure to set the lease expiry time of the DHCP server to at least 30 mins to prevent possible download failure. 14

15 3. The phone TUI updates with Checking For Firmware. 4. After the firmware has been uploaded, the phone will restart in MiNet mode. 5. Once the phone boots up in MiNet mode, enter the PIN to log in or register the phone as required by the TUI screen message. 6. If the phone was not previously configured, enter minimal static settings such as the Call Server IP Address. 7. Press the Option key, select the Advanced softkey, and enter admin login credentials. 8. Navigate to Network Settings and enter the Call Server IP Address and click Save. 9. Navigate to the TUI screen and enter the respective PIN request to log in or register a specific user: ***XXXX. 15

16 MiNet to SIP Conversion By factory default, the 6900 series IP phones have the MiNet firmware pre-installed. All 6900 phones will need to be upgraded to SIP R5.0 to become interoperable with Mitel s SIP-based solutions. SIP Upgrade options for phones with Minet firmware prior to Use the following methods to upgrade IP phones pre MiNet firmware to SIP firmware. Method 1: use static settings for a TFTP server 1. Place the SIP firmware files on the TFTP Server (ensure that no MiNet files are present). 2. Press the Gear button to go into Settings on the 6900 IP phone. 3. Select Advanced Settings (default password is 73738). 4. Select Network and Static Settings. 5. Enter the IP address of the TFTP server (ensure your IP phone has an IP address assigned) 6. Select Restart through the Settings App. 7. The IP phone will attempt to download MiNet firmware from the TFTP server. When not found, it will subsequently download the SIP firmware. 8. Once the 6900 phone is upgraded to the SIP build, optionally remove the files from the TFTP directory. Method 2: use DHCP option Place the SIP firmware files on the TFTP Server. Alternatively, an FTP Server can be used (ensure that no MiNet files are present). 2. Configure DHCP option 43 parameter sw_tftp tag for location of the firmware files (e.g. id:ipphone.mitel.com; tftp:// /firmwarefilesdir; ftp://test:aastra123@ / ). 3. Power up the phone. 4. The phone will attempt to download MiNet firmware from the TFTP/FTP server (not found), and will subsequently download the SIP firmware. Note that the config file will not download. 5. Reboot the phone it will follow existing SIP procedures for configuration and firmware upgrades. Method 3: use DHCP option Place the SIP firmware files on the TFTP Server. Alternatively, an FTP Server can be used (ensure that no MiNet files are present). 2. Configure DHCP option 66 with TFTP server URL (e.g. tftp:// /firmwarefilesdir; ftp://test:aastra123@ / ). 3. Power up the phone. 4. The phone will attempt to download MiNet firmware from the TFTP/FTP server (not found). It will subsequently download the SIP firmware. Note that the config file will not be downloaded. 5. Reboot the phone it will follow existing SIP procedures for configuration and firmware upgrades. 16

17 Method 4: use RCS 1. SIP 5.0 firmware will be available at RCS at GA time. 2. Add the MAC address for the phone to RCS. 3. Configure RCS to use SIP 5.0 firmware for the phone s MAC. 4. Power up the phone. 5. The phone will contact RCS and if its MAC is found on RCS it will download the firmware. 6. Reboot the phone it will follow existing SIP procedures for configuration and firmware upgrades. Autoconfigure Line 1 and Line 2 Softkeys The Line 1 and Line 2 softkeys are autoconfigured in the 6900 Series SIP Phones because there are no Line 1 and Line 2 hardkeys. The default values for top softkey 1 and top softkey 2 are set to Line 1 and Line 2. Blinking Softkey Icon Support for BLF Keys The 6873i and 6940 touchscreen phones do not have a LED attached to the soft keys. In Release 5.0.0, the 6873i and 6940 phones provide blinking softkey icons for the Busy Lamp Field (BLF/BLF List) keys. The phones display fast blink for ringing state and slow blink for hold state. The color of the softkey icon changes to yellow for ringing and yellow hold icon for hold state. 17

18 fast blinking Ringing state Hold state slow blinking Blinking Softkey Icon Support for Line Keys The 6873i and 6940 touchscreen phones do not have a LED attached to the soft keys. In Release 5.0.0, the 6873i and 6940 phones provide blinking softkey icons for the Line keys in regular and in shared mode. The phones display fast blink for ringing state and slow blink for hold state. The color of the softkey icon changes to yellow for ringing and yellow hold icon for hold state. fast blinking slow blinking Ringing state Regular/Shared Mode Hold state Regular/Shared Mode Line Labeling with Caller ID In Release 5.0.0, the caller ID displays on the line and mobile top softkeys and expansion modules (M685i and M695) for an incoming call. For 6873i and 6940 phone models, the caller ID is displayed in two lines; one displaying the name and other, the number. Administrators can enable this functionality by defining the line show caller id parameter as 1 in the configuration files. Enabling or Disabling Line Labeling with Caller ID Using the Configuration Files Use the following parameter to enable or disable the caller ID display on the 6800 and 6900 series phones. Parameter Description Configuration Files Format line show caller id Enable or disable the caller ID display on the line and mobile softkeys. startup.cfg, [mac].cfg Boolean Default Value 1 (enabled) for 6900, 0 (disabled) for 6800 Range disable 1 - enable Example line show caller id:1 18

19 Hardkey Remapping In Release 5.0.0, the hardkey layout for 6900 Series SIP Phones is redesigned and mapped as follows: Hardkey Function 1 Hold 2 Redial 3 Goodbye 4 Options 5 Voic 6 Callers 7 Directory The default configuration parameter values for 6900 series SIP Phones are as follows: hardkey1 type: hold hardkey2 type: redial hardkey3 type: goodbye hardkey4 type: options hardkey5 type: voic hardkey6 type: callers hardkey7 type: directory Note: Goodbye and Options keys cannot be remapped. Voic Hardkey Support In Release 5.0.0, the 6900 Series SIP Phones provide a hardkey for configuring voic . In 6800 Series SIP Phones, the voic is configured through softkeys. Note: Voic is not supported on the mobile line. 19

20 The following Voic functions are configured on the hardkey: On the SIP phone, pressing the Voic hardkey and dialing the Voic number (configured via parameter sip vmail ) connects the call to Line 1 Voic box. In the mobile line, pressing the Voic hardkey displays an error message on the SIP phone screen - Voic access of Mobile Phone not supported. In the mobile line, when the call is received from the mobile phone, pressing the Voic hardkey results in no action since the mobile line is in connected state and displays an error message on the SIP phone screen - Voic access of Mobile Phone not supported. In the mobile line, when the call is received from the SIP phone, pressing the Voic hardkey results in no action since the mobile line is in connected state but no error message is displayed. Self-Avatar Display on Idle Screen In Release 5.0.0, the 6873i and 6940 phone models allow users to display a self-picture ID on the idle screen attached to the focused line. When this feature is enabled, the phone requests image from the server if the picture was not previously downloaded and displays the image corresponding to the focused line. 20 For example, if Line1 of the SIP phone is configured with extension 1234, the phone requests an image from the server corresponding to the SIP account extension and 1234.png is displayed when the phone is focused on Line1. Note: The display of the line picture is supported only if the image server uri is configured.

21 If a user has multiple SIP accounts configured on the phone, the avatar on the idle screen changes when the user switches to a different account and the username.png of the focused line is displayed. Users and administrators can enable this feature using the Mitel TUI and configuration files. Enabling or Disabling Self-Avatar Display on Idle Screen Using Configuration Files Use the following parameter to enable or disable self-picture ID display on idle screen in 6873i and 6940 SIP Phones. Parameter Description Configuration Files Format idle screen avatar Enable or disable the self-picture ID display attached to the focused line. startup.cfg, [mac].cfg Boolean Default Value 0 Range disable 1 - enable Example idle screen avatar: 1 Enable or Disable Self-Avatar Display using TUI Use the following procedure to configure self-picture ID using the Mitel TUI: 1. Press (Options) key on the phone to enter the Settings menu. 2. Select or tap the Display icon. 3. Press or tap the Show Picture checkbox. 4. Press or tap Save to save your changes. 21

22 Auto-Audio Mode In Release 5.0.0, the 6940 phone model supports auto-audio mode when pairing with a USB or Bluetooth headset. Note: Auto-Audio mode is already available in the 6873i SIP phone. In the default (Speaker) audio mode, if a USB headset is connected, or if Bluetooth is enabled and a Bluetooth headset is paired, the phone automatically switches the audio mode to Headset/Speaker. You can manually change the audio mode to any of the other audio modes, but if you change it to Speaker, upon reboot, the phone will detect the headset and revert back to the last known Headset-related audio mode. If a headset is not connected, you can manually change the audio mode from Speaker to any of the other audio modes, but upon reboot, the phone will detect that there is no headset and revert back to Speaker audio mode. Note: Manually setting up audio mode without connecting any headset results in call failure. Operations On connecting a USB or Bluetooth headset, the audio mode is set to headset/speaker. On disconnecting the headset, the audio reverts to speaker only mode. Manual Override When a headset is connected to the 6940 or 6873i SIP IP phone, you can manually override the default audio mode on headset connected to headset/speaker mode. This override is retained even after the headset is disconnected and connected again. Bluetooth Connections In Release 5.0.0, the 6930 and 6940 Series SIP phones support Bluetooth connections to several devices specifically the Bluetooth handset, Bluetooth headset, and mobile phones. With Release 5.0.0, the 6873i SIP phone supports Bluetooth handset. Note: After upgrading the firmware from 4.x to 5.0.0, the Bluetooth headsets must be paired again with the 6873i SIP phone. This re-pairing is required due to the new Bluetooth implementation in Release 5.0 for 6873i phones. For 6940 SIP phone, the default bluetooth value is set to 1 and hence Bluetooth is always enabled. The Bluetooth connectivity for Bluetooth handset is retained on the phone even after a factory reset. The following software versions are validated for Release 5.0.0: ios (9.3.5, ) Android (6.0.1, 7.1.2) Note: The Bluetooth connectivity with SIP Phones is not restricted to the above-mentioned software. 22

23 Note: Mobile integration with the SIP desktop phones does not support any softphone client application on the mobile phones. For information on supported headsets, see Appendix A Supported Headsets. The 6930 and 6940 phones scan for previously paired Bluetooth devices including the mobile phones. If a previously paired mobile phone has Bluetooth enabled and is within discoverable Bluetooth range, the Mitel 6900 series phone auto-connects to the mobile phone. Bluetooth Pairing Use the following procedure to connect your SIP phone to a Bluetooth device: 1. Swipe the Bluetooth toggle switch to the right to enable Bluetooth functionality. A list of Paired Devices and Available Devices is displayed on the phone screen. 2. Select a Bluetooth device from the list of Available Devices that you require to pair with your SIP Phone and press Pair softkey on the phone. On successful connection, a Connection Successful message displays on the phone screen. 23

24 After the device is paired and connected, the phone screen returns to the Paired Devices tab. You can pair multiple mobile phones with the SIP IP phone, but only one mobile phone can be connected at a time. For example, if you try to pair and connect mobile phone-2 when mobile phone-1 is connected then mobile-phone-1 will be disconnected before connecting to mobile phone-2. Note: After upgrading the phone from MiNet firmware to SIP 5.0.0, the Bluetooth handset pairing with the phone is lost. Note: For 6873i SIP phone, after upgrading the phone firmware version from to 5.0.0, the Bluetooth headset (JABRA EVOLVE 65 version 2.2.1) stops functioning with the phone. If JABRA EVOLVE 65 is running , then there is no issue. This issue is related to new firmware version of JABRA and there is no fix available at this time. This also applies to 6940 and 6930 models. Disconnect or Unpair Bluetooth Device 1. User can disconnect or reconnect paired Bluetooth devices by pressing or selecting the devices from the Paired Devices list. 2. User can unpair Bluetooth devices by pressing or selecting the Forget bottom softkey from the Paired Devices list. Cell Phone Call Handling In Release 5.0.0, only incoming calls are supported through the cellular network. When a cell phone contact is dialed, the outgoing call is routed through the SIP landline and not through the mobile carrier network. Cell phone call handling feature works when the cell phone is paired and connected to the SIP desktop phone. When there is an incoming call on the cell phone, both the cell phone and the desktop phone ring. The user can pick up the call on either the cell phone or the desktop phone. When there is an incoming call on both SIP line and the mobile line and you lift the SIP terminal handset, the IP call takes priority over the mobile call. Note: During an active Bluetooth mobile call, the call hold reminder tone will not be heard even if the Call Hold Reminder option is enabled on the phone. 24

25 Mute and Hold Call When mobile phones are paired and integrated with Mitel desktop phones, control and operations are seamless and optimized by using the control function of Mitel phones. However certain individual mobile device functions such as transfer of audio or hold cell phone call might not be always processed by Mitel phones and can lead to unhandled states on Mitel phones. To prevent this, when a mobile phone call is active on a Mitel desktop phone, use the mute/hold call feature only on the Mitel desktop phone. When a mobile phone call is active on a mobile phone, use the mute/hold call feature only on the mobile phone. Bluetooth Mobile Pull and Push Call Behavior When the cell phone call audio is on the desktop phone, press the Push Call softkey to push audio to the cell phone. When the cell phone call audio is on the cell phone, press the Mobile softkey to pull audio to the desktop phone. When an incoming call on a Bluetooth connected mobile is answered by either pressing the speaker or mobile softkey on the SIP IP phone, the audio goes to the preferred device. For example, when the audio mode is in speaker/headset mode and a Bluetooth mobile call is answered, by preferred mode the audio goes to the speaker. If the user changes the audio mode to headset, consecutive pull and push call action from/to the mobile phone retains audio with the headset and does not change to the speaker mode each time the mobile softkey is pressed on the SIP IP phone. New Mobile Softkey Configuration Release supports Bluetooth mobile integration between a SIP phone and a mobile phone. The user can configure a new softkey type mobile for BT phones on top softkeys or on LCD expansion modules through configuration files and the Web UI. The following table summarizes the behavior of mobile softkey based on the Bluetooth connectivity. Condition TUI Display Softkey function BT disabled or BT enabled and no mobile phone paired Pressing the softkey opens the Options->Bluetooth screen. BT enabled and mobile phone paired but not connected Pressing the softkey opens the Options->Bluetooth screen. BT enabled and mobile phone paired and connected, mobile phone idle BT enabled and mobile phone paired and connected, mobile phone ringing Pressing the softkey results in no action. Pressing the softkey answers the call 25

26 Configure Mobile Softkey Using Configuration Files Use the top softkeyn type parameter to configure mobile softkey on 6930 and 6940 SIP phones using the startup.cfg and [mac.cfg] configuration files. For example, top softkey4 type: mobile Configure Mobile Softkey Through Mitel Web UI Use the following procedure to configure mobile softkey on 6930 and 6940 SIP phones through Mitel Web UI. 1. Click on Operation > Softkeys and XML > Top Keys 2. Select a top softkey. 3. In the Type field, select Mobile. 4. Click Save Settings. Goodbye Key Behavior for BT Mobile Line When a BT Mobile line is established with the SIP phone, the Goodbye key functions as follows based on the SIP line and Mobile line state If the first SIP line has an active call and the second SIP line is ringing - Pressing Goodbye key cancels the ringing line when Goodbye Key Cancels Incoming Call is enabled. - Pressing Goodbye key cancels the active call line when Goodbye Key Cancels Incoming Call is disabled. If the first line has an active BT Mobile call and the SIP line is ringing Mobile Contacts Sync - Pressing Goodbye key cancels the ringing line when Goodbye Key Cancels Incoming Call is enabled. - Pressing Goodbye key cancels the BT mobile line if audio is on the desk phone and cancels the ringing line if audio is on the mobile phone call when Goodbye Key Cancels Incoming Call is disabled. 26 With BT-mobile integration, users can access the mobile phone directory and import mobile contacts into the SIP Phone. The mobile contacts are then available for look up and dial and for identification through caller ID.

27 New configuration parameters mobile contacts enabled and mobile contacts name are created which allow users to enable or disable the mobile contacts import and allows to give a custom name to the mobile contacts folder in the directory. Parameter Description Configuration Files Format mobile contacts enabled Enable or disable the mobile contacts import. startup.cfg, [mac].cfg Boolean Default Value 1 Range disable 1 - enable Example mobile contacts enabled: 1 (to enable mobile contacts) Parameter Description Configuration Files Format Default Value Range Example mobile contacts name Override the default folder name Mobile Contacts provide a customized name to the mobile contacts folder. startup.cfg, [mac].cfg String Empty Not applicable mobile contacts name: iphone (to name the mobile directory folder iphone ) Hot-Desking and Mobile Integration In Release 5.0.0, mobile integration is supported for hot-desking accounts. After logging in, hot desk users can pair, connect, and import contacts from the mobile phone. On logging out, the mobile phone is disconnected and unpaired from the desk phone, and the mobile phone contacts removed from the desk phone. On the next login using the same desk phone, any Bluetooth device that was earlier paired and connected, is automatically paired and connected with the phone and the mobile phone contacts are imported from the server. With hot desking, a desk phone can retain 30 Bluetooth device pairings per user. Of these, two are special pairings; the pairing with handsets and speakers. Handsets and speakers can be paired with the desk phone only when logged out of the hot-desking account and the paired state is preserved between any hot desk log in and log out. Note: In hotdesking mode, the Bluetooth parameter is always saved in the local.cfg configuration file instead of the user-local.cfg configuration file. 27

28 Support for Bluetooth Cordless Handset The Bluetooth Cordless Handset is a standard accessory for the 6940 SIP phone and an optional accessory for the 6930 and 6873i SIP phones. The following are the features of the BT cordless handset: Uses BT 4.1 technology to provide HD voice quality Enables call answer, hang up, mute, and volume up/down through buttons on the side of handset Plays ringtone on handset and base phone Recharges in-built battery through contacts built into base phone Indicates charge status through LED display After an upgrade from MiNet to SIP firmware, the Bluetooth Cordless Handset pairing info may not be retained. Users must again pair the Bluetooth Cordless Handset with the 6940, 6930 or 6873i SIP phones. BT Cordless Handset Pairing Use the following procedure to connect your SIP phone to a BT handset: 1. Swipe the Bluetooth toggle switch to the right to enable Bluetooth functionality on the phone. A list of Available Devices is displayed on the phone screen. 2. Select or tap the BT Cordless Handset from the list of Available Devices to pair with your SIP Phone. On successful connection, a Connection Successful message displays on the phone screen. 28

29 3. Click OK. Bluetooth Handset Battery Level Display In Release 5.0.0, users can view the battery level of the BT handset through the following: icons in the status bar battery warning or critical level toaster notification battery warning or critical on the screen saver Phone Auto-lock and Unlock on Mobile Proximity With mobile integration in Release 5.0.0, the 6930 and 6940 phones automatically lock or unlock after a preconfigured delay when a paired mobile phone is disconnected or reconnected. Users and administrators can configure this feature through the Mitel Web UI, TUI and configuration files using the following new configuration parameters: proximity lock proximity unlock proximity lock delay proximity unlock delay 29

30 When the proximity lock and unlock feature is enabled, users and administrators can perform the following configurations on the phones supporting mobile integration: Automatically lock the phone when a connected mobile is disconnected after a configurable delay. Automatically unlock the phone when a paired mobile is reconnected after a configurable delay. Define different configuration and delay time for phone auto-lock and unlock. Note: This feature does not function when the user disables the Bluetooth connection or manually connects, disconnects or unpairs the mobile phone from the TUI. Enabling or Disabling the Phone Automatic Lock and Unlock on Mobile Proximity Using the Configuration Files Use the following parameters to enable or disable the proximity lock and unlock feature on the 6930 and 6940 phones. Parameter Description Configuration Files Format proximity lock Enable or disable phone automatic lock on proximity detection startup.cfg, [mac].cfg Boolean Default Value 0 Range disable 1 - enable Example proximity lock: 1 (to enable the feature) Parameter Description Configuration Files Format Default Value Range Example proximity lock delay When proximity lock is enabled, delay after proximity event detection before locking the phone. startup.cfg, [mac].cfg Integer 0 (no delay) 0 to 1440 minutes proximity lock delay: 5 (wait for 5 minutes before phone lock) 30

31 Parameter Description Configuration Files Format proximity unlock Enable or disable phone automatic unlock on proximity detection startup.cfg, [mac].cfg Boolean Default Value 0 Range disable 1 - enable Example proximity unlock: 1 (to enable the feature) Parameter Description Configuration Files Format Default Value Range Example proximity unlock delay When proximity unlock is enabled, delay after proximity event detection before unlocking the phone. startup.cfg, [mac].cfg Integer 0 (no delay) 0 to 1440 minutes proximity unlock delay: 5 (wait for 5 minutes before phone unlock) Enabling or Disabling the Phone Automatic Lock and Unlock on Mobile Proximity Using TUI Use the following procedure to enable or disable the proximity lock and unlock feature on the 6930 and 6940 phones using the TUI. 1. Press on the phone to view the Options list. 2. Navigate to the Lock icon and press Settings. 3. Enable or disable the Proximity auto-lock and Proximity auto-unlock fields using the checkbox. 4. Enter the required delay time (minutes) in the Delay before auto-lock and Delay before auto-unlock fields. 5. Press Save to save your changes. 31

32 Enabling or Disabling the Phone Automatic Lock and Unlock on Mobile Proximity Using Mitel WebUI Use the following procedure to enable or disable the proximity lock and unlock feature on the 6930 and 6940 phones using the WebUI. 1. Click on Operation -> Phone Lock. 2. Enable or disable the Proximity auto-lock and Proximity auto-unlock fields using the checkbox. 3. Enter the required delay time (minutes) in the Delay before auto-lock and Delay before auto-unlock fields. 4. Click Save Settings to save your changes. 32

33 Appendix A Supported Headsets The following headsets are supported in Release 5.0.0: Plantronics Black wire C725 USB headset Plantronics Legend Bluetooth headset Jabra Pro 9400BS DHSG headset Analog headsets from different vendors Mitel 6800/6900 Series SIP Phones Release Notes 33

34 Issues Resolved in Release This section describes the issues resolved on the SIP phones in Release The following table provides the issue number and a brief description of each issue. DEFECT DESCRIPTION RESOLUTION DEF43521 DEF41383 DEF43985 DEF44355 ENH43573 DEF43882 DEF44035 In the Chariot setup for 6800 series phones, when a VDP logged-in user is in an active call, it was observed that the TUI does not reflect the active call information and instead displays an idle state sporadically. However, the context sensitive keys (drop, conf, xfer) are available and the L1 LED blinks during the call. When a 6867i SIP phone is connected to a primary server using TCP, it was observed that if the server goes down, the phone REGISTERs to the backup SIP server but the TCP retransmits continue to occur to the primary server. After the user ends an active call, the primary server comes up and one of the retransmits receives a TCP ACK. The phone then sends an INVITE to the primary server for the completed call but no call is indicated on the TUI. For Telepo, it was observed that during a CTI initiated call, the phone displays the correct Callee information in the ringing state but as soon as the Callee answers the call, incorrectly displays the PAI information. When a Bluetooth headset was connected to a 6940 SIP phone, it was observed that there was no dial tone on the speaker after connecting or disconnecting the Bluetooth headset. When configuring a speed dial soft key through the TUI, the keypad did not offer the + sign to set a value as (647+). On the 6867i and 6873i SIP phones, it was observed that if you navigate to the Ring Tones screen on the phone and quit after the custom ring tone ended playing, the phone does not ring on the next incoming call. When using the MNS key on the second page of the phone along with a connected USB headset, it was observed that the phone continues to send INVITEs even after a call is terminated. Also, when dialing through MNS on DIR 100 and switching between the Headset and Speaker, a dial tone is always heard after the switch. An enhancement is made where in the numeric mode, pressing and holding the = sign offers = + sign options. 34

35 DEF43995 DEF44067 DEF38467 DEF42073 DEF43984 DEF43982 DEF44380 DEF43657 ENH44362 DEF43491 ENH43722 DEF43599 DEF39843 DEF43863 On the 6800 SIP phones, when the call waiting tone period is set to 0, the phone continuously plays beep tone on answering the second call. On the 6869i an 6873i SIP phones, the SCA icon configured on top softkey for shared remote user is cut off. On the 6869i SIP phone, when both Call Hold Reminder and Call Hold Reminder During Active Call are disabled, there is no Call Hold Reminder ring splash on held line after the active line is ended locally. When dialing a number without using the live dialpad, the screen clears after a time regardless of the dialing state. On the 6900 SIP phones, it was observed that when manually switching between the different audio modes, the ring tone changes by itself. For BLF list on MiVoice 400, the icon color is lost after receiving a NOTIFY from the server. On MiVoice 400, the alarm melody feature does not work if audio mode is set to headset or headset/speaker. On the 6865i SIP phone, it was observed that when a M685 module is connected to the phone, the backlight does not completely turn off on the M695 module even after the configuration parameter inactivity brightness level is set to 0. When the SIP phone has 21 accounts configured with explicit MWI enabled and 13 line keys configured on the expansion module, the line keys are not displayed on the expansion module after the phone boots up. A typo was observed in the last certificate that is "-" is missing before ----BEGIN CERTIFICATE for last certificate. When switching a phone, there was no simple way to transfer the local directory data. Though the directory can be exported through the Web UI, there was no simple way to import it to the new phone. The SIP phone fails to play ringback when G729 is negotiated as the codec. The 6867i SIP phone always queries the NTP server twice. On the SIP phone, when the user was on an active call, it was observed that the phone TUI An enhancement is made by queuing and sending MWI requests in the same way as BLF keys. An enhancement is made wherein the local directory can be exported and imported from the Web UI. by initiating the time module and call server time update once. 35

36 displays loading language file and then reboots. DEF43879 On the 6867i SIP phone, when hardkeys 8 (redial) and 9 (callers) are remapped, the phone screen gets locked in the callers list. DEF44224 DEF43549 DEF44376 DEF44326 DEF41281 DEF44472 DEF41460 When trying to enable the Rport on Web UI, it disables itself automatically after switching the page. The background image is lost on the SIP phone after check-resync without reboot. When a user imports directory from the Mobile into the Mobile directory on the phone, the directory displays erroneous characters instead of 'white space' for some dial numbers, without impacting the dial. The local language settings are not saved using the VDP login. The language settings are set back to values in the configuration file and not to what the user had selected. The 6867i SIP phone always sends SDP with all pre-configured codecs to refresh the sessions. Hence the phone sends in-call re-invite with different set of codecs but with the same Session Version ID. On MiVoice 5000, a key defined as lock is not programmed on the 6800/6900 terminals. In MiVoice Office 400, the 6867i and 6869i SIP phones do not disconnect after receiving a XML PhoneExecute item Key:Goodbye. by reinitializing language in the language callback by creating exception for parameters containing the locked keyword. 36

37 Mitel 6800/6900 Series SIP Phones 5.0 Release Notes Contacting Mitel Support If you have read this release note, consulted the Troubleshooting section of your phone model s manual, and still have problems, please contact Mitel Support through one of the following methods: North America Toll free at Online at Outside North America Please contact your regional Mitel Technical Support. 37

38