MiVoice Office 250. Release Notes Release 6.3 SP2 ( )

Transcription

1 MiVoice Office 250 Release Notes Release 6.3 SP2 ( ) October 2018

2 About this document This RN (Release Note) is intended for Customer Service and Installation Personnel involved in the installation and maintenance of the Mitel MiVoice Office 250 product. 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 regard 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. 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 others. 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:

3 Table of Contents Release Notes for MiVoice Office 250 Release 6.3 SP Functional changes and Security Updates... 4 Release Notes for MiVoice Office 250 Release 6.3 SP Functional changes and Security Updates... 5 Release Notes for MiVoice Office 250 Release Functional changes and Security Updates... 6 Essential installation and upgrade information for MiVoice Office SP Hardware Platform Requirements... 8 Mitel Product Compatibility Requirements... 9 Application, OS and Browser Requirements Pre-Installation and Upgrade Checklist Post Installation and Upgrade Checklist Upgrading to Release 6.3 SP2 from an earlier release Where to find the latest information Software release history Product areas improved in this release DHCP Options for 6900 Handsets Known Issues... 21

4 Release Notes for MiVoice Office 250 Release 6.3 SP2 This document describes the following components related to MiVoice Office 250 Release 6.3 SP2: Product enhancements and functional changes Requirements and upgrade information Where to find the latest version of our guides Software release history Product areas improved in this release Known issues We strongly recommend you review the information and instructions found in the MiVoice Office 250 Installation and Administration and MiVoice Office 250 Features and Programming Guides along with the hardware and software requirements found in the MiVoice Office 250 Engineering Guide before downloading, installing, or upgrading your software. Functional changes and Security Updates This following table describes functional changes and security updates for MiVoice Office 250 Release 6.3 SP2: Product area Security Updates Description MiVO 250 offers TLS 1.2 on all secured system connections. The applications "System Administration" (Sys Ad) and "Data base programming" (DBP) applications connect with TLS 1.2 to MiVO 250. (Default value of SSH/OAI/WEB/ SIP ports are set to disabled. They need to be enabled before they can be used. An upgrade of an existing system will keep the setting as before. Intercom can be dialed on the keypad of 69xx SIP phone. (This improvement also needs MiVoice Office Application Suite Release 5.1 SP2 or higher) Improved Functionality for SIP Phones (Especially 69xx Phones) Default value for SIP devices "audio for calls camped onto this device" is set to 'Ringback' instead of 'MOH'. When 'MOH' was not yet installed, there was only silence. An upgrade of an existing system will keep the setting as before. When adding off-node devices to 'hunt groups' or 'ring in destinations' the device type 'IP / Digital' is renamed to 'IP / Digital / SIP / 6900' to make it clear that this needs to be selected for 69xx SIP Phones. The default values for device type '6900 SIP phone' are also perfect for the Phone Manager clients. It is renamed to '6900/Phone Manager SIP phone'. 4

5 Release Notes for MiVoice Office 250 Release 6.3 SP1 This document describes the following components related to MiVoice Office 250 Release 6.3 SP1: Product enhancements and functional changes Requirements and upgrade information Where to find the latest version of our guides Software release history Product areas improved in this release Known issues We strongly recommend you review the information and instructions found in the MiVoice Office 250 Installation and Administration and MiVoice Office 250 Features and Programming Guides along with the hardware and software requirements found in the MiVoice Office 250 Engineering Guide before downloading, installing, or upgrading your software. Functional changes and Security Updates This following table describes functional changes and security updates for MiVoice Office 250 Release 6.3 SP1: Product area Description Single Provisioning: Once a 6900 phone has been created in the MiVO250, it will automatically generate authentication details. Using encryption, MiVO AppSuite can import the 6900 device authentication details. Improved OAI functionality to assist with 6900 SIP Phone Deployment When configuration changes are made to 6900 SIP Phone Group(s) the MiVO250 will notify MiVO AppSuite via OAI. Page zone numbers: With improved OAI functionality 6900 phones can now select a Page Zone ID in Keymap profiles on MiVO AppSuite. Note: If CT Gateway is in use, this will need to be upgraded to to allow the new OAI functionality to be used. Other Updates AWP shows the 69xx SIP phone as separate device type in the Device General tab. New OpenSSL version 1.0.2n Meltdown/Spectre: The new Bios on PS-1 Dell R230 servers is supported. Security Updates General Data Protection Regulation (GDPR) documents are available as part of the Release 6.3 SP1 documentation. Inbound Authentication is now available for SIP Voic . When creating a SIP Voic we strongly recommend populating Inbound Authentication credentials to avoid any unauthorized access to MiVO250. 5

6 Release Notes for MiVoice Office 250 Release 6.3 This document describes the following components related to MiVoice Office 250 Release 6.3: Product enhancements and functional changes Requirements and upgrade information Where to find the latest version of our guides Software release history Product areas improved in this release Known issues We strongly recommend you review the information and instructions found in the MiVoice Office 250 Installation and Administration and MiVoice Office 250 Features and Programming Guides along with the hardware and software requirements found in the MiVoice Office 250 Engineering Guide before downloading, installing, or upgrading your software. Functional changes and Security Updates This following table describes functional changes and security updates for MiVoice Office 250 Release 6.3: Product area Support of 6900 SIP phones in conjunction with MiVoice Office Application Suite 5.1 Divert/Accept UCD Calls, when using SIP devices SIP Reverse Transfer Direct Page Flexible SIP header configuration to SIP trunk provider Restricted CLI in SIP header Display only Caller Identification instead of Transfer information Alternate Lamp Indication on Phone / PKM keys Release Key Notification of no Primary or Local Attendant configured. Description Mitel 6920, 6930 and 6940 SIP Phones are supported in conjunction with MiVO App Suite 5.1. The 6900 SIP phone configuration is supported with a new 6900 SIP phone type, that can be used instead of the generic SIP phone type. SIP devices support the Hunt Group Remove/Replace feature. The incoming hunt group calls to SIP phones can be stopped with the DBP flag, or by using the feature code (322 HG Remove, 323 HG Replace, 324 Toggle HG Remove/Replace). Calls on hold or calls ringing at a SIP phone can now be picked up by another device on the system. Direct Page is an enhancement to the existing Page feature, which allows you to page to the loudspeaker of an individual IP / Digital Phone instead of a whole Paging Zone. There are new fields available in the SIP Trunk Group configuration that allow you to define which caller id information is sent to the SIP provider. The caller identification can be withheld within the SIP header. A new Phone flag allows you to suppress transfer information and instead display caller identification and name (during ringing of incoming call) A new system flag "Use alternate key lamp indication for Phone status" allows a clearer difference for lamp indication (ringing: slow, hold from anyone: moderate, active calls: continuously lit). It is now possible to configure the "release call functionality" on any phone key. The Primary or Local Attendant is important to system behavior. When the Administrator unintentionally removes 6

7 SSL certificate. Product area Security updates Discontinuation of UCX (Unified Communicator Express. Description these from the database configuration a warning message will appear. The MiVO 250 now supports the installation of a third-party web SSL certificate. New OpenSSL version 1.0.2l Firewall improvements & configuration in Admin Web Portal (AWP) Several improvements were made for current firewall settings and the firewall configuration to the PS-1 server was extended. Unified Communicator Express was discontinued in May It is now removed from MiVoice Office 250 R6.3 documentation. 7

8 Essential installation and upgrade information for MiVoice Office SP2. The following section includes a description of the requirements for the hardware platform, application, and server software, Application integration details, an installation and upgrade checklist, and notes for upgrading from a previous release. Hardware Platform Requirements Please refer to the MiVoice Office 250 Engineering Guidelines for further details Product area HX Controller Base Server PS1 Server Releases All variants Dell PowerEdge R210 / R220 / R230 Server CPU - Intel Core i3 Class (2 GHz minimum) or Higher OS Linux Debian v2.6 or higher Hard disk - Non-redundant 250GB SATA RAM - 8GB ECC DDR3 For server specifications and characteristics please refer to Requires vsphere 5.0, 5.1 or 5.5 vps1 Server For server specifications and characteristics please refer to CS Platform No longer supported as of release 6.2 8

9 Mitel Product Compatibility Requirements You must meet the minimum software level requirements for each product listed below so that the applications will function correctly with this Release. MiVoice Office 250 PBX Application Minimum Software Level 6.3 SP2 ( ) SP5 PR1 Mitel CloudLink 1.1.0, MiVoice Office Application Suite (MCS) 5.1 SP2 (5.1.20), 5.1 SP1, 5.1, , 4.3 MiVoice Office Phone Manager 5.1 SP2, 5.1 SP1, 5.1, 5.0, 4.3 MiVoice Office Phone Manager Mobile for Android 10.0 (for Oreo), MiVoice Office Phone Manager Mobile for ios 10.0 (for ios 11), Mitel SIP phone 6920, 6930, ( ) incl. AppSuite 5.1 SP2 5.0 SP2 ( ) incl. AppSuite 5.1 SP1 5.0 GA ( ) incl. AppSuite 5.1 MiVoice Business 9.0, 8.0 MiCollab 8.1, 8.0, 7.3, MiCollab Client - Legacy Desktop Client 7.3, MiCollab Client - Next Gen Clients (PC client, Mac Client, Web Client, Mobile Clients) Not Supported MiVoice Border Gateway 10.1 SP1, 10.1, 10.0 MiCollab unified messaging (NuPoint) , , MiContact Center Office 6.2 SP1, 6.2 CT Gateway , Attendant Console , IP phones series 86xx and 53XX , Digital phones 85XX and redesigned digital phones F Mitel phones (5603,5604,5607,5613,5614) 4.2 IP DECT (IPBS1) 7.0 Softphone (8602) SIP phone (X-Lite) SIP phone (Bria) Single line phone - IP SLA/SLA - IPDECT RTX (8430) CX UCX discontinued (3.1) MiVoice Video Phone (UC360) , Mitel SIP DECT RFP (Base Station) 8.0, 7.0, 6.2, 6.1 Mitel SIP DECT phones (632d,612d,622d,650c) 7.0, 6.2, 6.1 Mitel 5624 WiFi Phone

10 StreamLine 1.1 (sw: 3.1.8) HTML Toolkit 2.2 Application, OS and Browser Requirements You must meet the minimum software level requirements for each application listed below so that the applications will function correctly with this Release. Application Windows OS (Clients) Windows OS (Server) (CT Gateway only) Minimum Software Level Windows 10 Enterprise 32 / 64 bit Windows 8.1 Enterprise 32 / 64 bit Windows 8 Professional 32 / 64 bit Windows 8 Enterprise 32 / 64 bit Windows 8 Standard 32 / 64 bit Window 7 SP1 Professional 32 / 64 bit Window 7 SP1 Enterprise 32 / 64 bit Windows 2012 Server R2, R1 Windows 2008 Server R2, R1 Windows 2003 Server R2, R1 Microsoft Exchange 2016, 2013 Gmail Online latest available GroupWise 2014 Lotus Notes 9.0 Office 365 Online latest available OAI Command Interface 10.2 Microsoft Internet Explorer (IE) 11 Microsoft Edge Mozilla Firefox Chrome Safari Latest Latest Not supported Not supported 10

11 Pre-Installation and Upgrade Checklist The following table outlines a check list that must be followed as part of the MiVoice Office 250 installation or upgrade procedure for upgrading to v6.x systems: Check Component How to Check Action if required Is your CF at least 1G? Does your CF have more than 125 MB available? Does your CF meet your voice data storage requirements? Does your TFTP server support larger file transfers? Note that the largest package in the core_upgrade set of packages is approximately 25 MB. Does your PC meet the necessary system and browser requirements? Do you have a current save of the system database? Do you have a current save of the voice mail data and file-based MOH files (via AWS), if applicable? Do you have the latest SysAd\DB Programming version installed? Launch SysAd and on the System Status tab look at the System Utilization content control. Launch SysAd and on the System Status tab look at the System Utilization content control. Launch DB Programming and go to the Voice Processor folder. Look at the Total Storage Used on the System field. Check documentation or help for the TFTP server. Check the browser and corresponding version information. Check your backup files. Check your backup files. Compare the installed versions to the versions listed in the software versions of the release notes. You need to purchase a new 1G or greater CF before proceeding with the upgrade. You need at least 125 MB available on the CF before proceeding with the upgrade. Delete unneeded voice mail messages, languages, MOH files, etc. to free up space, or upgrade to a larger compact flash-type memory card, and then start the system upgrade. Compare the amount currently used to the amount allowed per Compact Flash as listed in Table 1 above. Use a 1 or 2 GB Compact Flash if additional storage is needed. Use a TFTP server that supports larger files transfers. Make sure you are using one of the following supported browsers. Perform a Database backup and a Database save using DB Programming. (For details, refer to the latest MiVoice Office 250 installation manual, part number ). Back up the voice mail data and file-based MOH files (via AWS/AWP), if applicable. Install the latest SysAd and DB Programming. Do you have a database Open your saved database in Use the DB Converter utility in 11

12 Check Component How to Check Action if required converted to the current v6.x version? Does your saved and converted database have any errors? Do you have the appropriate version software license? Offline mode and verify the version in DB Programming. Launch SysAd, from the Utilities button select the MiVoice Office 250 Test & Repair option. Select the saved database that you would like to test and Start testing. SysAd to convert the database to match the current DB Programming version. If any errors are found they will be reported in the utility and can be repaired on an individual basis. Note: The MiVoice Office 250 Test & Repair utility removes unused items from the database (e.g., unused trunk groups, or extension lists or hunt groups with no assigned extensions). For this reason, you may want to run it in Test mode only, and then view the changes in the log. If the changes will not negatively impact the database, then run DB Test again in Test and Repair mode. Generate the latest license from the AMC account for the specific Application Record. 12

13 Post Installation and Upgrade Checklist The following table outlines a check list that must be followed as part of the MiVoice Office 250 installation or upgrade procedure for upgrading to v 6.0 systems: Check Component How to Check Action if required Is your CF at least 1G? Does your CF have more than 125 MB available? Does your CF meet your voice data storage requirements? Does your TFTP server support larger file transfers? Note that the largest package in the core_upgrade set of packages is approximately 25 MB. Does your PC meet the necessary system and browser requirements? Do you have a current save of the system database? Do you have a current save of the voice mail data and file-based MOH files (via AWS/AWP), if applicable? Do you have the latest SysAd\DB Programming version installed? Do you have the appropriate version Power down the system and extract the CF. Launch AWS webpage and go to System Status tab. On the left select Memory Usage and look at the Flash Available value. Launch DB Programming and go to the Voice Processor folder. Look at the Total Storage Used on the System field. Check documentation or help for the TFTP server. Check the browser and corresponding version information. Check your backup files. Check your backup files. Compare the installed versions to the versions listed in the software versions of the release notes. You need to purchase a new 1G or greater CF before proceeding with the upgrade. You need at least 150 MB available on the CF before proceeding with the upgrade. Delete unneeded voice mail messages, languages, MOH files, etc. to free up space, or upgrade to a larger compact flash-type memory card, and then start the system upgrade. Compare the amount currently used to the amount allowed per Compact Flash as listed in Table 1 above. Use a 1 or 2 GB Compact Flash if additional storage is needed. Use a TFTP server that supports larger files transfers. Make sure you are using one of the following supported browsers. Perform a Database backup and a Database save using DB Programming. (For details, refer to the latest MiVoice Office 250 installation manual, part number ). Back up the voice mail data and file-based MOH files (via AWS/AWP), if applicable. Install the latest SysAd and DB Programming. Generate the latest license from the AMC account for the specific 13

14 Check Component How to Check Action if required software license? Application Record. Upgrading to Release 6.3 SP2 from an earlier release Please adhere to the following guidelines before upgrading: NOTE: Always take a backup before starting any upgrade procedure. Please check the AMC for entitlement to the intended version, and to download the license file before carrying out the upgrade. 6.3.x 6.2.x From To This Release Comment Yes Yes Requires database conversion as the DB Schema version is changed in this newer version. Requires database conversion as the DB Schema version is changed in this newer version x Yes Requires database conversion as the DB Schema version is changed in this newer version x An interim upgrade of the DB and system No software to 6.1 SP1 PR3 is required before the upgrade to x No An interim upgrade of the DB and system software to 6.1 SP1 PR3 is required before the upgrade to x No An interim upgrade of the DB and system software to 6.1 SP1 PR3 is required before the upgrade to No Requires 1 GB minimum compact flash card for upgrade. Please refer to the upgrade instructions for more details. Pre 4.0 See comment The database can be converted directly to v6.0. A 1 GB compact flash card must first be upgraded to v4.0 or v5.0; otherwise the system will require a new v6.0 CF (1 GB Minimum) to successfully complete the upgrade. 14

15 Where to find the latest information You can access the most up-to-date versions of the following documents from MiVoice Office 250 Installation and Administration Guide MiVoice Office 250 Features and Programming Guide MiVoice Office 250 Engineering Guidelines MiVoice Office 250 System Administration & Diagnostics Guide MiVoice Office 250 Message Print Diagnostics Guide MiVoice Office 250 UVM Synchronization Administrator Guide Installation Quick-Start Guide Program Planning Sheets Administrator Phone Guide Voice Mail Administrator Guide UVM Synchronization User Guide Phone User Guide Supplement Phone User (and Quick Reference) Guides Voice Mail User Guide User Guides [ For answers to frequently asked questions, troubleshooting information, post-release hotfixes, and technical bulletins, see the Mitel Knowledge Base accessible through Mitel Online. Login through the Mitel Connect portal: Software release history The following table details software releases for the MiVoice Office 250: Release Level Release Name Call Control Version Release Date 6.3 SP2 MiVoice Office 250 v6.3 SP October SP1 MiVoice Office 250 v6.3 SP June MiVoice Office 250 v March SP2 MiVoice Office 250 v6.2 SP April SP1 MiVoice Office 250 v6.2 SP October MiVoice Office 250 v June SP1 MiVoice Office 250 v6.1 SP January MiVoice Office 250 v October SP3 PR1 MiVoice Office 250 v6.0 SP3 PR June SP3 MiVoice Office 250 v6.0 SP March SP2 MiVoice Office v6.0 SP August

16 Release Level Release Name Call Control Version Release Date 6.0 SP1 MiVoice Office v6.0 SP March SP5 Mitel 5000 CP v October Mitel 5000 CP v June SP4 Mitel 5000 CP v November SP3 Mitel 5000 CP v5.1 (Australia support) August SP2 Mitel 5000 CP v July SP1 Mitel 5000 CP v June Mitel 5000 CP v December SP2 Mitel 5000 CP v September SP1 Mitel 5000 CP v May Mitel 5000 CP v February (MR) Mitel 5000 CP v March (MR) Mitel 5000 CP v March

17 Product areas improved in this release The following customer-reported issues were resolved in MiVoice Office SP2 Tracking Number MN MN MN Description Phone call logs show missed call when call was answered with secondary ext key DB programming crash when edit forced account codes with win10 pc Unusual entries appearing in MP during a DB restore or when logging into DBP MN PCI Compliant issue MIVO MN MN MN MN MN UM Delivers messages again after they are deleted MiVO 250 not responding with 200 OK to SIP INFO messages during video call there are too many open file descriptors for AVDAP process Customer system resetting - Reset Due to Too Many Sequential Exceptions Dialing external numbers gives ringback or MOH over ringback The following customer-reported issues were resolved in MiVoice Office SP1 Tracking Number MN MN MN MN MN MN MN MN MN MN MN MN Description Adds a SIP Authentication Query for MiVoice Office Application Suite (Phone Manager). Adds a db change event for authentication and ip address changes. Adds Page zone return values numbers. Security improvements via updating the OpenSSL version to 1.0.2n. Toll fraud prevention improvements to support additional authentication settings. Adds media sdp attributes in sip INVITE for t.38 fax calls for Centurylink IQ providers. Hunt group longest idle agents not presented calls properly if system forwarding enabled. An oai FE event not generated for sip phones when activating or deactivating agent help. Major Reset: Call Processing Exited - Unknown Cause with sip, faxing and t.38. Increases the size of the inbound authentication password box in sip voic s phone improved park key behavior for one step transfer on sip devices. Low or no audio on new 8528 and 8568 digital phones. 17

18 The following customer-reported issues were resolved in MiVoice Office Tracking Number MN MN MN MN MN MN MN MN MN MN MN Description Outside callers hear users press the Mute key from the 8568 / 8528 digital phones on loop start lines. Pauses in voice mail audio prompts on PS1 equipped systems. Prompts start to play, then pause for a few seconds, then audio resumes playing. PKM units connected to 8568 / 8528 digital phones go offline and do not come back online until the attached device for that phone in DB programming is toggled to none and back to PKM. Call park feature recall calls incorrectly using the transfer attendant timer instead of the park recall timer for calls that are transferred to park locations by phones with the attendant flag set. Loop start trunks fail to clear in a timely manner when outside caller hangs up due to voice mail not correctly identifying busy tone from the trunk. Conference call failing after 30 seconds on sip phones and 53xx IP phones. When the 53xx phone hangs up from the conference, the two sip phones are disconnected 30 seconds later. Networked systems crash with error message Call Processing Exited - Unknown Cause when the database timer incorrectly set in System \ System Information \ Off- Node Status \ Throughput Limit. The default value of 10 should be used. System Reset due to too many sequential exceptions caused by a sip trunk that has a camped-on call. Enhancements to the systems unique ssh host key generation. SIP calls stuck and showing in System Administration and Diagnostics - Call Activity - Current Calls - with an outcome code of 88. When changing from divert hunt group calls and DND to accept hunt group calls, the hunt group calls do not ring the phone. MN One way video between Polycom TRIO and Polycom VVX MN MN MN MN MN MN MN Conference assistant in hunt group causes resets when hunt group called. Cannot assign same to the different mailbox, getting an error in 6.2 SP2. No audio on call recordings when the MiVoice Office 250 is used with the Mitel Border Gateway MBG MiVoice Office 250 incorrectly changes RTP ports back and forth when the port rotation is normally initiated by MBG. Cannot use hunt group call pickup by dialing 4 and the hunt group pilot number from a sip phone using Mitel Phone Manager. System rebooted itself in the middle of the day - phone lockup reverse transfer. Digital 8528 and 8568 phones lose hands-free audio in the conference assistant after 5 minutes and 20 seconds. System resetting from receiving large numbers of duplicate acknowledgement messages (ip packets) on ports to

19 Tracking Number MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN Description New 8528 and 8568 Digital Phones cannot dial DTMF digits when in speakerphone mode. Phone firmware revision F9 works. IMAP not working on local Exchange 2016 server. Support for TLSv1_2 is added to IMAP functionality. Cannot restore converted databases to the system. Applications Loading showing on 5320E Teleworker phones intermittently between the idle display. Error adding firewall rules to the system web page firewall if the current rules were deleted using the reset_iptables command from the Linux shell. Agents in hunt groups unable to answer internal calls from sip phones. CPU showing 100% utilization due to the kipmi0 process. Using UC360 with video on sip trunks and getting a 500 Server Internal Error message back from the carrier when the Use Peer-To-Peer Media flag is disabled on the network group. SSH port 22 inaccessible when a new compact flash card on 6.2 is downgraded to 6.0 software. Users cannot modify their calling party number or emergency calling party number via the webpage interface. Inbound PRI call to a phantom forwarded to a sip trunk group stays ringing at phantom and does not forward to the sip trunk group that is connected to a fax finder device. No Number is displayed under Call Key when making outbound calls. An agent logged into a SIP phone does not get any agent wrap up mode when they transfer a hunt group call to another extension System reboots with resource reconciliation failure. Single line circuits lock up and stay busy on SLM-8 boards in DEI units. Reception phones randomly have to press the call keys to answer incoming sip trunk group calls after lifting the handset to answer the incoming call. ACD agent login and logout issue when using the OAI Command Interface. MiCollab Client outbound call to Mitel 5000 via SIP trunk CLI issue. CS System Utilities package not upgrading to 6.2 SP2 PR3 as shown on the webpage. Poor audio quality on 8568 and 8528 digital phones. New firmware is included in the 6.2 SP2 PR4 software for the 8568 and 8528 digital phones. Pauses not working in system speed dial numbers on PRI trunks. Caller id not displaying the last 2 digits on inbound calls. MSG waiting lights on top of phone not working. Unable to restore databases to 6.2 SP2 PR systems. 19

20 Tracking Number MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN MN Description File Based Music on Hold switches from music to ringing on off node hunt recall. No audio when Handoff feature is used for P2P configuration. No Number is displayed under Call Key when making outbound calls - MN Agents receiving hunt group calls when they are supposed to be in wrap up mode. System Administration and Diagnostics not connecting to system from a SSL/TLS error. DEE Handoff, individual line key stays lit flashing after DEE call finishes on system. Upgrades from 6.1 CS Chassis to 6.2 HX Chassis, remote phones experience delays when answering calls. MiVoice 250 not sending a sip ACK, in response to, 200 OK from a Polycom Video Conferencing Unit. MiVo250 wrongly changes RTP ports back and forth when port rotation is normally initiated by MBG (RFC3264 SDP offer/answer model violation) Bria sip phones report dropped sip calls, no audio, slow respond on PS1 system. Database programming taking much longer to connect after upgrade Web portal across nodes for off node mailboxes The 'Add' button is not available within DBP MiVo250: Subsequent Sip Trunk Register message is not sending out by MiV0250 after it receives 404 or 403 responses for that Trunk MiVo250: * (star) in a dial string, using SIP trunks. Engineering guidelines V6.2 SP2 refers to out dated OAI application in the OAI guideline table System Monitoring stuck on "Loading..." until you refresh DB test advises changing an invalid extension number but unable to find the extension DND event message does not have message number Add a new pop-up box with troubleshooting information in an error message whilst downloading logs SIP devices use 'American English' messages regardless of the language set against the device MN SysAd Diags SSL/TLS error on SysAd connection to MiVoice Office 250 MN MN MN MN Continuation of DB Programming Issue (Old DPAR MN ) Since upgrade to getting keylist error when save messages to USB 911 Routing out of system 2 hour RAC that is forward and copy from mailbox fails 20

21 DHCP Options for 6900 Handsets The following section describes configuring DHCP options for 6900 handsets in MiVoice Office 250 release 6.3 SP1: 1. When using the MiVoice Office 250 embedded DHCP server, please bear in mind the following: (1) If the 6900 is running Minet firmware, please see the MiVoice Office Handset Engineering Guideline" for details on how to upgrade to SIP Firmware. Available on edocs under MiVoice Office Application Suite [ (2) The MiVoice Office 250 embedded DHCP server options must be configured as follows: Remove option 43 and add option 66 Set the Format to ASCII In the String Value, enter the IP Address of the MiVoice Office Application Suite server. Known Issues The following section describes known issues in MiVoice Office 250 release 6.3, 6.3 SP1 and 6.3 SP2: 1. Since the 69xx MobileLink feature and incoming intercom call (handsfree auto-answer enabled and barge-in disabled) both share the same resources, these features should not be configured on a device at the same time Multi-Node Hot-desking is supported for co-located nodes only. Due to Emergency Services restrictions, nodes located in different physical addresses are not supported. 3. MiVO Basic Kit licenses for multi-node configurations will require manual licensing assistance from Mitel Product Support. Please follow instructions in the MiVoice Office Application Suite Site_id certificate which comes included with the MiVoice Office Base Kit. 21

22 22