93
Known Issues
This section includes the known issues with Build 294 of the FLX UC 1000 and
FLX UC 1500.
1.
Call control (i.e. call hang up and answer) not supported for Skype version
6.22 or higher on Mac platforms.
2.
Call control (i.e. call hang up and answer) not supported for Go To Meeting
version 7.1 or higher. Currently supported version is 6.4.12.
3.
When using Vidyo Version 3.5.0 and 3.5.2 and end the call by touching the
hang up cap touch button on the device, and the hang up button is pressed
more than once, the application will display a blank window, and the
application will need to be closed before the application will start working
again.
4.
The FLX UC 1000 uses hotkeys to issue commands to applications that do
not provide an API for call control. When using hotkeys, the softphone
window that is active will have the hotkey issued to it. This may cause the
user to have to press the accept call button multiple times or notice a delay
when attempting to answer an incoming call.
5.
With a Cisco Unified Communications Manager (CUCM), if the session timer
on the FLX UC 1000 is configured for less than the minimum required by
the call manager, call transfer will not operate as expected and will drop the
call.
6.
With certain call managers, third party conference phone support in the call
manager doesn’t provide call ID when forwarding or transferring calls. This
has been seen with CUCM, Asterix, and OnSip.
When a call is forwarded or transferred with the FLX UC 1000, the ID
displayed will be in accordance with the information in the “Call Forwarding
Behavior” section of this document.
7.
When using a third party conferencing application, with Caller A and caller
B in the call, if Caller A places the call on hold, caller B will not get any
indication that the call is on hold. If Caller B then places the call on hold,
the hold status on the dialer will show on hold. Once caller A resumes, the
call will resume but the dialer on Caller B’s side will still show on hold.
