Cisco Cisco Unified Communications Integration for Cisco WebEx Connect
Resolved Issues in the 7.2.6 Release
4
Resolved Issues in the 7.2.6 Release
The following issues were resolved in the version 7.2.6 release of Cisco WebEx Connect:
CSCui66605
Changing the audio device after a call has been established causes the subsequent calls to end
automatically.
CSCui36545
After switching the network (such as from wireless to wired) the Cisco WebEx Connect application cannot
establish connectivity to the Cisco Unified Communication Manager (CUCM) automatically.
CSCui36627
The Cisco WebEx Connect plug-in for Microsoft Excel does not work with Excel 2013.
CSCui26846
After a network disconnect and reconnect, the Cisco WebEx Connect application tries to register with
CUCM twice.
CSCui26842
After a call terminates due to a network disconnect, the Cisco WebEx Connect application cannot
reestablish connectivity to CUCM on network reconnect.
CSCui13366
A user with P2P audio and video enabled cannot place a call to a user with only P2P audio enabled.
CSCzu51137
Upgrading the Cisco WebEx Connect application causes local chat history to be inaccessible.
CSCzu80341
The Cisco WebEx Connect application may hang when voicemails are deleted.
CSCuh53595
A PC has both wired and wireless network interfaces turned on, and network connectivity is via the wired
connection. When the wired connection is disabled, the PC switches to the wireless connection, but
connectivity to CUCM is not established.
connectivity to CUCM is not established.
CSCub64805
An incorrect call is listed in the call history when on a multiparty call.
CSCub09344
In some situations, there is no audio in a PC-to-PC VoIP call (iSAC).
CSCzu81030
Users are unable to dial using FAC codes.
CSCuh57125
When Use desk phone is selected, the Cisco WebEx Connect application will not reconnect to CUCM
automatically after a network disconnect.
CSCto97156
The Cisco WebEx Connect application needs to be restarted to enable device mobility.
CSCui58495
Sometimes restarting the Cisco WebEx Connect application will cause it to not detect the network.
Resolved Issues in the 7.2.5 Release
The following issues were resolved in the version 7.2.5 release of Cisco WebEx Connect:
CSCuh55712
In situations where a network disconnect causes a phone call (Cisco Unified Communications Manager
call or Click-to-Call) to abruptly disconnect, and the user makes a new call subsequently within a short
time period of the disconnect, the audio from the previous call may mix with the new call.
CSCui21881
In some situations, on network disconnect and reconnect (wired to wireless), the Cisco WebEx Connect
application does not detect an IP address change.
CSCui16084
If the user selects the “Do not disturb” after a call has been initiated, the “Do not disturb” status is not sent
to the Cisco Unified Communications Manager (CUCM).
to the Cisco Unified Communications Manager (CUCM).
CSCui16109
After a network disconnect, the Cisco WebEx Connect application tries to initiate a call with an instance of
the Communications Manager (CUCM) it was registered with before the network disconnect, and not the
the Communications Manager (CUCM) it was registered with before the network disconnect, and not the
instance of the Communications Manager it registered with after the network reconnect.