Mitel 6863i Release Notes page 72

Mitel 6800 Series SIP Phones 4.2.0 SP1 Release Notes
ISSUE NUMBER
DEF41407
DEF41475
DEF41839
Network
ENH35605/ENH41831
DEF41804
DEF41904
DEF41482/DEF41721/
CLN41587
Troubleshooting
ENH41926
XML
DEF40546
DEF41073
68
DESCRIPTION
An issue was observed whereby the phone would mute the handset when
a BLF-monitored extension received a call if the phone was configured to
play a BLF ring splash during an active call. This issue has been corrected.
When using the phone with the MiVoice MX-ONE call manager, if the
phone was configured to use asymmetric RTP ports, one-way audio could
be observed after a call was held and then retrieved. This issue has been
resolved.
When the phone was configured to play a custom ring tone, if an incoming
call was answered immediately (e.g. within one second of the phone
ringing), one-way audio could, at times, be observed. This issue has been
fixed.
Multiple DCHP server support was not functioning as expected in previous
releases. This issue has been corrected and the phones can now receive
messages (specifically messages related to Options 43, 66, 159, and 160)
from multiple DHCP servers. Additionally, DHCP-related tasks are now
logged in the phone's syslog, allowing Administrators the ability to monitor
and debug the DHCP process.
Note: If the DHCP servers do not have any of the Options (43, 66, 159, and
160) configured, the phone's boot up process will increase by up to six
seconds.
In certain network environments with very short DHCP lease times and
when using the phone with the Metaswitch call manager, an issue was
observed whereby the phone would lose registration intermittently. This
issue has been resolved.
An issue was observed whereby a phone with 802.1x certificates
downloaded previously did not attempt 802.1x authentication after a reboot
if the 802.1x certificates were not available on the configuration server. This
issue has been corrected.
Changes have been implemented in Release 4.2.0 SP1 to improve security
robustness.
A reboot logging feature was introduced in a previous release whereby
information regarding phone reboots were added to a reboot.log file and
viewable on the System Messages section of the Troubleshooting menu
through the phone's Web UI.
In Release 4.2.0 SP1, for purposes of clarity, the AutoResync::NeedResync
and AutoResync::Timeout reboot codes have been renamed to
AutoResync::ForceResync and AutoResync::TimeForResync respectively.
Configuration of the custom ringtone feature using the XML API was not
functioning correctly in previous releases. This issue has been resolved.
6867i and 6869i: An issue was observed whereby if the phone was in an
XML FormattedTextScreen or InputScreen and the Lockin parameter was
defined as "yes", users were still able to navigate to the Options menu by
pressing the Options button. This issue has been fixed.