Mitel 5613 Instruction Manual

Mitel 5613 and 5614 2.10.3
Purpose of the release
This is maintenance release for the Mitel 5613 and 5614 DECT handsets.
The 5613 and 5614 are the latest generation DECT handset. They are functionally compatible with
the former 5603 and 5604 respectively and can be used in new as well as existing installations.
Release Notes
October, 2020
Release information
Software version:
2.10.3
This document covers
changes since 2.6.8
Build date:
July 2020
Software name:
5613_v2.10.3.pkg
5614_v2.10.3.pkg

New functionality 2.10.3
•Described in the “CR” and “New Feature” section below
CR
Factory reset shall reset all frequency bands
Components: All Products
Background:
Customer is using different DECT frequency bands depending on where they are. When a certain frequency
has been set in the admin menu, there is currently not possible to change back to any other frequency.
The limitation that factory reset is not making it possible to enter a new frequency band is requested to be
removed.
Solution:
Now it is possible to change the DECT frequency on a factory reset device even if the frequency was
previously set to a certain value
Improvements
Display driver adjustments for DH6
Components: 5613
Background:
Missing pixels can be seen in the display during use of DH6 units equipped with the new displays (display ID:
7c)
Display ID info is found under "Device info > Hardware" menu in the handset.
Solution:
Display driver has been updated to fix a problem with pixels on DH6 LCD
NCR
PDM help text for parameter Settings/Messaging/Call Priority is confusing
Components: 5614
Background:
The PDM parameter help text is unclear and to some extent misleading for the parameter
Settings/Messaging/Call Priority. It can for example be understood as it is possible to suppress the message

being shown on the display during an ongoing phone call
Solution:
PDM help text for parameter Settings/Messaging/Call Priority is clarified
Device "swallows" keypress if the phone is in "standby"
Components: All Products
Background:
If a device has a black display (standby) and you start typing 1234 it happens that the phone only registers
134.
Solution:
Dialing from the black screen now always works correctly
Phone restriction parameter "Turn off sound" mutes device
Components: All Products
Background:
Enabling/ticking the parameter "Turn off sound" under Customization/Phone Restriction and value is set to
"Yes" will mute phone if applied on a device by a template
Solution:
Fixed an incorrect handling of customization parameter "Turn off sound"
Call priority parameter help text does not describe "standard" paging
Components: 5614
Background:
Help text for the PDM parameter Settings/Messaging/Call Priority does not describe functionality for
"standard" (non-interactive) messages

Solution:
The PDM help text has been updated to clarify that the parameter Settings/Messaging/Call Priority has no
effect on a standard (non-IM) message
White display on DH6 during use
Components: 5613
Background:
Display may sometimes turn white on DH6 handsets equipped with the new displays (display ID: 7c)
Display ID info is found under "Device info > Hardware" menu in the handset
Solution:
Fixed a problem with a white screen when an incoming call is made while the phone is in black screensaver
mode.
Out of range notification does not repeat
Components: All Products
Background:
The out of range warning beep is played only once regardless of the parameter "Settings / Sound and
Alerts/Out of range alert" setting. The default value for this parameter is 30 beeps (or repetitions)
Solution:
The out of range warning beep repetition is restored
Bugs
Device restarts when an image from IM is opened right after blackscreen
Components: 5614
Background:
When shortly after waking up the device from the black screensaver you try to open an image from a received
message and doing a few additional key presses to scroll the image - the device restarts with Trap IAD reason.

Solution:
The handset doesn't restart when an image is opened right after the black screensaver state.
Message alert is heard in call when sound indication is disabled
Components: 5614
Background:
The handset gives both vibration and message beeps when a message is received during an ongoing call even
when configured not to beep.
Solution:
Message beep is no longer heard in-band when it is configured not to beep.
Sometimes it takes more than 3 mins for Bluetooth headset to reconnect
Components: 5614
Background:
When going with a Bluetooth headset far from the device so that the Bluetooth connection is lost (headset
says "No device connected") and moving back shortly - it takes more than 3 minutes until the Bluetooth
headset is reconnected again.
Solution:
If a connection with a Bluetooth headset was lost the phone will try to reconnect.
Device can get stuck in Bluetooth headset menu when switching between headsets
Components: 5614
Background:
Sometimes, when switching between the two paired Bluetooth headsets via the Bluetooth menu on the
device, the device can get stuck in this menu with the "Connecting" progress bar.
In this state it is possible to send alarms and receive phone calls, but it is not possible to exit from the menu
without restarting the device

Solution:
The "Connecting" bar is not shown if Bluetooth is already connected/disconnected.
"Subscribing" pop-up does not disappear from the screen when the subscription is canceled
Components: All Products
Background:
"Subscribing. Please wait." pop-up does not disappear from the screen when the subscription is canceled, it is
not possible to go to the idle screen.
The only way to remove this pop-up is to put the handset in the charger.
Solution:
Fixed an issue with freezing pop-up "Subscribing. Please wait."
Incorrect behavior after subscribing
Components: All Products
Background:
After a successful subscription the screen where Park & AC are entered does not disappear for some time (2-4
sec). During this short period of time, if you press the left button (Next/Yes) several times, the phone restarts
Solution:
Keypresses are ignored while showing pop-up "Subscribing successful".
Time area is too close to missed call icon on a display
Components: 5613
Background:
Time area is too close to the “missed call” icon on a display when 12-hour time format is used, making them
overlapping
Solution:
Added extra spacing between the “missed call” icon and the clock on display

Only 23 digits can be observed and edited, should be 24
Components: All Products
Background:
If editing a 24-digit number from the call list only 23-digits are shown
Solution:
All digits from the call list are now shown in pre-dial screen
Call log displays incorrectly in conference call
Components: All Products
Background:
When phone A creates a conference call with phone B and phone C (A calls B, then A calls C and joins them
into a conference (R3)), and then disconnects - call log for B and C parties will be missing the info about
incoming call from A.
Solution:
Call log displays correctly in the conference call
Unexpected restart when receiving messages during roaming
Components: 5614
Background:
Sometimes an unexpected restart of handset can happen when receiving messages during roaming
Solution:
Fixed an unexpected restart in case when new message arrives during roaming between the base stations

It is possible to accept and reject the same acknowledge message
Components: 5614
Background:
It is possible to accept a paging with confirmation message during a short period after you have already
rejected it.
Both statuses (accepted and rejected) will be received by Unite system
Solution:
Soft keys are blocked after acting on the message and before its closure, so that only one option can be
chosen for particular message
Unexpected restarts during device software update in DP1
Components: All Products
Background:
When updating the device SW using WinPDM and DP1 it may end up with unexpected restart during or after
the upgrade procedure.
Solution:
Fixed unexpected restarts in DP1 during SW upgrade

Limitations and Known issues
•Note! If updating a handset running 1.3.0 or 1.3.1 updating to an intermediate version
1.48.88 or 1.48.89 may be required in order to go around a bug that prohibits software
updates.
•Wideband audio will only work with IPBS2/IPBS3 and a PBX with support for the voice
codec G.722.2.
•Device management with DC4 requires the user to press the mute button when the phone
is inserted in the charger. The button can be released after a pop up is confirming that the
phone is in the charger.
If a license was moved from Device#1 to Device#2 and the SW on Device#1 is after that
downgraded to a version earlier than 2.6.7 –the Device#1 will boot with a license error.
To recover from this problem the device needs to be upgraded to release 2.6.7 or later
•Updating from a SW version 2.6.8 or earlier to a SW version 2.10.3 or newer will result in
the call list content being erased.
Same applies for the downgrade path between the abovementioned versions
•If a connection between a Bluetooth headset and the device is lost for the period longer
than 10 minutes - some headsets may not re-connect automatically. Manual re-connect
may be needed in this case.
•A muted handset becomes un-muted if it is restarted
Compatibility
•Configuration with WinPDM from version 3.13.0.
•There is a new programmer DP1 for the new DECT handsets. Due to larger software size,
this is the recommended programmer product. The old programmer DC4 and the charging
rack CR3 can still be used for programming but with lower performance.
•The UPAC product based on IMS2 is not supported
•In order to meet GDPR requirements for unauthorized use, we recommend that the Phone
lock feature is activated on the handsets. It is also recommended to clear message and
call lists when put in a charger
Ascom Wireless Solutions
Grimbodalen 2
402 76 Gothenburg
Sweden
Phone: [phone]
www.ascom.com/ws
!
X