Ethernet Routing Switch 8600 Software Release v7.1.3.1
Avaya has released software v7.1.3.1 for the Ethernet Routing Switch 8600/8800.
- L3VSN default route was not correctly installed in the RTM when it was received via ISIS. As a result L3VSN traffic that needs to use the default route was being dropped. This problem is specific to L3VSN only. It did not affect GRT default routes via ISIS. (wi00996566)
Please refer to the release notes for all the details.
Avaya IP Softphone 2050 Release 4.3
Avaya has released the IP Softphone 2050 Release 4.3.081 for Microsoft Windows.
There is specific mention of support for 64bit versions of Microsoft Windows 7 and Microsoft Windows Vista;
Important Note : It is strongly recommended to install the next updates for Microsoft Windows 7 to the PC
including the specific updates noted below. Failure to install these Windows 7 updates may cause the
2050 IP Softphone to crash or not work as intended.
KB981679 (part of Service Pack 1 for Windows 7)
KB979303
The following issues are resolved;
- wi00715416 External – Improved robustness of Licensing Server in releasing licenses, if IP Connection drops
- wi00903652 External – Issue with node-locked licensing not working with CS1000 R7.5 and 2050 R4.2
wi00906095 - wi00867565 External – Error message when starting IP Softphone on Windows 7™
- wi00908928 External – Graphics issue on Windows 7™
- wi00896132 External – Dual stream recording does not work properly with 2050 after a call is transferred to the 2050
- wi00951184 External – 2050 reverts to PC speaker and soundcard instead of USB device when PC is restarted
- wi00889263 External – SR 1-1462175541: IP Softphone trace route shows only final destination, not intermediate hops.
Please refer to the release notes for all the details.
Cheers!
Emerenziano says
Does anyone have the magic receipt to get the i2050 running on Windows 7 32bit in a stable manner? Eeven with 4.3 I’m experiencing configuration loeses and some software instability. E.g. the sound volume level behaves in strange ways (sometimes).
Michael McNamara says
Hi Emerenziano,
We’re still running on Windows XP here with version 3.2 of the IP 2050 softphone and agents are working all day long with very few issues.
If you are referring to volume settings you need to be careful where you set the volume. I’ve seen the issue even with Windows Media Player where if you set the volume in Media Player it will not over-ride the volume setting of the audio card.
Cheers!
Rob says
Hi Mike,
On the day you announced the 2050 Release 4.3 (4.03.081) Avaya Announced the Softphone 2050 Release 4.3 SP1 (4.03.085). :P
I have installed Release 4.03.081 on several laptops with great success over release 4.2. The audio levels still remain a mystery. It looks like windows behavior with multiple audio devices. If a USB headset remains plugged in all the time, the audio devices remain consistent. If you start the PC without the USB headset connected, then connect to different port, well, now its a “new” USB headset. Open the Softphone settings and re-check.
I found another interesting caveat. The Headset device bleeds a little white noise even while the softphone is idle. The Handsfree speaker device does not. I started using Plantronics Voyager Pro UC v2 kits with the Softphones and the 1140E sets with the USB dongle. Our Remote agents get an ASA-5505 VPN Appliance, an 1140E, a 2050 Softphone, a Voyager USB/Bluetooth and an Avaya Mobile USB kit. I connect the dongle and headset to my PC and open Spokes to configure the set to link on audio detection. The user doesn’t need the Spokes software to use the headset. I set the 1140E for USB headset and plug in the dongle. Choosing between wired and wireless on either phone is simplified to a USB connection. There is no call control capability with the Voyager Pro UC. The Audio detection starts the headset when you answer a call or make one. When the call has ended, the headset disconnects less than 5 seconds later. It behaves the same way on the 2050 Softphone if it is designated as the “Speaker Device”. If it is set as the “Headset Device”, it will start up for a call but it will remain linked up even though the phone is idle. It will disconnect if you close the softphone app.