This document was generated from CDN thread
Created by: Sherif Amer on 03-11-2009 10:18:55 AM
we did CTI integration with Cisco IPCC using Java SDK which provided by Cisco¿and I have a problem with fail over scenario. Please check the below scenarios:
Scenario A ¿ successful
If the agent in the not ready status and the fail over occurred from server A to server B or reverse versa. The status is not changed remain not ready.
Scenario B ¿ Failed.
If the agent in the ready status and the fail over occurred from server A to server B or reverse versa. The status is changed to not ready.
Scenario C ¿ Failed.
If the agent in the log out status and the fail over occurred from server A to server B or reverse versa. The status is changed to not ready.
Scenario D ¿ successful
If the agent in the talking status and the fail over occurred from server A to server B or reverse versa. The status is not changed remain talking.
--------------------------------------------------------------------------
As I know and found in the Cisco document (developer guide document)¿ that the failover handling is SDK back process which I have no control on it¿please find some parts in the document which related to the issue.
· CTI OS brings several major advances to developing custom CTI integration solutions. The CIL provides an object-oriented and event driven application programming interface (API), while the CTI OS server does all the `heavy-lifting¿ of the CTI integration: updating call context information, determining which buttons to enable on softphones, providing easy access to supervisor features, and automatically recovering from failover scenarios.
· upon recovery from a failure, the CIL will automatically reconnect to another CTI OS (or reconnect to the same CTI OS after restart), reestablish the session, and recover all objects for that session.
· In addition, the Session object provides automatic fault tolerance and failover recovery.
--------------------------------------------------------------------------
In case if the fail over occurred It should be transfer from a server to another server with the same status. This scenario applied for scenario A and D. But in the scenario B and C the status changes which is against the customer requirement.
In case if the agent status is log out the fail over should not occurred (The agent should not be connected again to any server as long as he is logged out).
I hope that I make the issue clear for you¿I am waiting your feedback and I am really appreciate toy support .
Subject: RE: New Message from Sherif Amer in Computer Telephony Integration Object S
Replied by: David Lender on 03-11-2009 03:29:26 PM
Sorry I don't understand. Are the scenarios you listed what you expect
or what is occuring?
Subject: RE: New Message from Sherif Amer in Computer Telephony Integration Object S
Replied by: Sherif Amer on 13-01-2010 06:40:38 AM
it is what is occuring now