User's Manual

A
vaya 2050 IP Softphone for Windows PC Release
4.1 (Build 41) General Availability – Global
Revision History
Date Revision # Summary of Changes
29 October 2010 Original bulletin This is the original publication
Introduction
Avaya is pleased to announce the general availability of the 2050 IP Softphone 2050 Release 4.1 (Build 4.01.0041) for Windows PC.
This maintenance release does not include any additional features; however it does deliver several significant fixes.
This release is being provided as a no charge update to all customers who have purchased or upgraded to Release 3.x or 4.x.
Quality Improvements
The Avaya 2050 IP Softphone Release 4.1 contains numerous resolved issues and closed cases. The list of resolved customer
reported issues since Release 4.0 are listed below.
Case ID Description
100624-64923
Corrects an issue where the 2050 IP Softphone could become unresponsive if a
user presses Answer/Headset/Line key and then presses "Release". The
application could only be closed only via the Windows Task manager.
N/A
Corrects a timing issue on CS2100 systems using the CRQM (IP Call Recorder)
application where the RTP streams from the near-end and far-end were not
synchronized in the recording.
091210-67218
091216-70624
100402-24717
Corrects an issue introduced in Release 4.0 where the MSI installation file was not
a real MSI installation as compared to the previous versions. This prevented the
use of the Microsoft SCCM environment for managing installations, de-installations
and upgrades.
With Release 4.1, the MSI file is again a true MSI installation file.
100430-38625
Fixes an issue with call recording where the duplicate media stream was not closed
at the end of the call, leading to a large amount of network traffic and performance
degradation of the PC.
100616-60946
Fixes an issue where the pre-dial window was not showing the "city/area
code"(HNTN/HLCL) saved and hence the incomplete number was being dialed.
100628-66330
Corrects a problem on CICM (CS2100) systems where one way transmission was
occurring on IP to IP and IP to TDM calls.
1

Summary of content (8 pages)