Issues Resolved In Release 2.5.3; Release 2.5.3 - Aastra 67XXI Release Note

Sip ip phone release 2.5.3
Hide thumbs Also See for 67XXI:
Table of Contents

Advertisement

Issues Resolved in Release 2.5.3

This section describes the issues resolved on the IP Phones in Release 2.5.3. The following table
provides the issue number and a brief description of each fix.

Release 2.5.3

Issue Number
Description of Fix
SIP
CLN19852
The phone was randomly freezing during calls and in the idle state. After a re-subscribe only a
NOTIFY was sent to the phone - not an OK response. This NOTIFY worked fine but the next NOTIFY
that was sent caused a freeze on the phone.
This is now corrected.
DEF17372
When using RTP Control Protocol Extended Report (RTCP-XR) in a network, the Network Packet
Loss Rate (NLR), Burst/Gap densities & durations were reported incorrectly.
This is now corrected.
DEF17514
The IP Phones set the VLAN ID according to the Type-Length-Values (TLV) when receiving a civic
location TLV alone. When ELIN is enabled (an additional location TLV with ELIN info), the phone
cannot set the VLAN ID according to the network-policy.
This issue has been corrected.
DEF18682
A REINVITE from G.722 to G.711 codecs resulted in the "Hi-Q" icon staying on the phone's screen.
This has now been corrected and the "Hi-Q" icon now correctly goes away.
DEF18707
A REINVITE from G.711 to G.722 codes does not display the Hi-Q icon on the Phone UI.
This has been corrected and the HI-Q icon now displays as expected.
DEF19258
When the IP Phone uses persistent Transport Layer Security (TLS) with an intermediate certificate
that has been signed by the root Certificate Authority (CA), the intermediate CA then issues the
server certificate. However, a TLS session cannot be established. After the TLS Handshake, the
phone sends a Transmission Control Protocol Finished (TCP FIN).
This is now corrected. The phone now registers and connects with any Common Name (CN) used for
the proxy and registrar server name.
DEF19416
If TLS is used on the phone, it uses the SIPS URI scheme for all requests such as REGISTER,
INVITE, and SUBSCRIBE. However, REFERs are sent using SIP URI scheme. As a result, a call
transfer may not work properly when using TLS.
This is now corrected. A SIP REFER is now correctly sent using SIPS URI scheme.
RN-001029-04, Release 2.5.3, Rev 05
SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series Phones Release Note 2.5.3
Note: Unless specifically indicated, these resolved issues apply to all
phone models.
Issues Resolved in Release 2.5.3
5

Advertisement

Table of Contents
loading

Table of Contents