Limitations

Issue

Use Case

Comment

Work Around

Dialing state changed to Connected

  • Agent dials customer Number

  • Agent Refreshes the browser

  • The call state should remain dialing

The dialing state should remain the same until the customer accepts the call, whether the user refreshes the browser

This issue occurs only when the user dials an actual number

UI (Not showing dialled Number)

  • Agent dials the wrong customer Number

  • The number should be shown with the call state

The Number or extension should be shown with the call state, whatever agent dials

When Dial Extension is not regeisterd its show an Error message, but does not show that number with the call state

GetState Event 

  • Agent dials customer Number

  • Agent phone goes in Dialing & Customer goes in Ringing state

  • Call getState, agent state should dialing

GetState command will always return talking State whether it is in dialing or talking if the receiver phone is other than CUCM's Phone!

The use of getState is only in case of a refresh scenario,
So, this limitation will only affect the application in case of an outage or Re-Login!

System Limitations

Summary 

Description

Related Features 

After Failover, User A start showing the dialing state when on consult call.

When failover happened during a consult call, the User who initiated the consult call started showing the Dialing state instead of the call controls div.

Failover

User unable to perform any action when any connector comes up after the complete blackout.

When any connector comes after both went down, User is unable to perform any action on the interface.

Failover