IP Library Granted Patent US 10,148,820
Granted Patent B2
US 10,148,820 · App. 15/785,049 · Granted Dec 4, 2018

Call transfer using session initiation protocol (SIP)

Inventors: Vyacheslav I. Zhakov (Burlingame, CA); Vyacheslav V. Sayko (Walnut Creek, CA); Aleksandr V. Tikin (Pleasant Hill, CA)
H04M3/5232H04L29/06027H04L65/1006H04L65/1043H04L65/1096H04L65/4007H04L67/24H04L67/327H04M3/5183H04M3/5191H04M3/523H04M3/5237H04M3/58H04M7/0075H04M3/42323H04M3/42374H04M3/493H04M3/56H04M7/006H04Q3/72
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,148,820
App. No.
15/785,049
Granted
Dec 4, 2018
Kind
B2
Abstract

A system is provided for providing communication event routing and transfer capability in a multi-site communication-center environment. The system utilizes a presence protocol application and a routing application for determining availability of an agent or system and for setting up the transfer from a point of transfer on a network to a destination of transfer on the same or connected network. In a preferred use the presence protocol application is shared by communication-center sites cooperating in the transfer and routing of events and the presence protocol enables at least one event-handling process normally performed by the routing application.

Claims (40)

1. A system for routing communication events for a customer contact center comprising:

a processor; and

a memory, wherein the memory has stored therein instructions that, when executed by the processor, cause the processor to:

receive a first message from a first server in response to a communication event being detected by the first server, wherein the first message includes data for routing the communication event, the first message adhering to a first communication protocol;

receive a second message from a second server separate from the first server, in response to the communication event being detected by the first server, wherein the second message includes a request for agent availability for handling the communication event, the second message adhering to a second communication protocol different from the first communication protocol;

concurrently process the first and second messages for determining whether to allow transfer of the communication event from the first server;

transmit a first response and a second response to respectively the first and second servers in response to the processing; and

receive a transfer of the communication event in response to transmitting the first and second responses.

2. The system of claim 1 , wherein the first communication protocol is a non-standard based protocol and the second communication protocol is a standards-based protocol.

3. The system of claim 2 , wherein the standards-based protocol is a session initiation protocol (SIP).

4. The system of claim 3 , wherein the second message that adheres to SIP includes parameters concerning requested call initiation procedures and permission for transferring the communication event.

5. The system of claim 3 , wherein the second message is configured to prompt a SIP-based response indicative as to whether transfer is permitted.

6. The system of claim 1 , wherein the first and second responses are indicative that transfer is allowed.

7. The system of claim 2 , wherein the standards-based protocol is an instant messaging and presence protocol (IMPP).

8. The system of claim 1 , wherein the first and second messages each include an identifier associated with the communication event.

9. The system of claim 8 wherein the instructions further cause the processor to match the identifier included in the first and second messages for identifying the corresponding communication event.

10. The system of claim 1 , wherein the second message is configured to be sent via a first data link and the first message is configured to be sent via a second data link different from the first data link.

11. The system of claim 1 , wherein the first response is according to the first communication protocol and the second response is according to the second communication protocol.

12. The system of claim 1 , wherein the instructions further cause the processor to forward a portion of the data for routing the communication event to an agent device for display thereon.

13. The system of claim 1 , wherein the processor is further configured to exchange signaling data with the second server for establishing a data communication session.

14. The system of claim 1 , wherein the data for routing the communication event is devoid of requirements for requesting agent availability information.

15. A method for routing communication events for a customer contact center comprising:

receiving, by a processor, a first message from a first server in response to a communication event being detected by the first server, wherein the first message includes data for routing the communication event, the first message adhering to a first communication protocol;

receiving, by the processor, a second message from a second server separate from the first server, in response to the communication event being detected by the first server, wherein the second message includes a request for agent availability for handling the communication event, the second message adhering to a second communication protocol different from the first communication protocol;

concurrently processing, by the processor, the first and second messages for determining whether to allow transfer of the communication event from the first server;

transmitting, by the processor, a first response and a second response to respectively the first and second servers in response to the processing; and

receiving, by the processor, a transfer of the communication event in response to transmitting the first and second responses.

16. The method of claim 15 , wherein the first communication protocol is a non-standard based protocol and the second communication protocol is a standards-based protocol.

17. The method of claim 15 , wherein the standards-based protocol is a session initiation protocol (SIP).

18. The method of claim 17 , wherein the second message that adheres to SIP includes parameters concerning requested call initiation procedures and permission for transferring the event.

19. The method of claim 17 , wherein the second message prompts a SIP-based response indicating whether transfer is permitted.

20. The method of claim 15 , wherein the first and second responses are indicative that transfer is allowed.

21. The method of claim 16 , wherein the standards-based protocol is an instant messaging and presence protocol (IMPP).

22. The method of claim 15 , wherein the first and second messages each includes an identifier associated with the communication event.

23. The method of claim 22 further comprising matching the identifier included in the first and second messages for identifying the corresponding communication event.

24. The method of claim 15 , wherein the second message is configured to be sent via a first data link and the first message is configured to be sent via a second data link different from the first data link.

25. The method of claim 15 , wherein the first response is according to the first communication protocol and the second response is according to the second communication protocol.

26. The method of claim 15 further comprising forwarding a portion of the data for routing the communication event to an agent device for display thereon.

27. The method of claim 15 further comprising exchanging signaling data with the second server for establishing a data communication session.

28. The method of claim 15 , wherein the data for routing the communication event is devoid of requirements for requesting agent availability information.

Assignments (4)
NOTICE OF SUCCESSION OF SECURITY INTERESTS AT REEL/FRAME 04814/0387 Recorded Feb 5, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: GOLDMAN SACHS BANK USA, AS SUCCESSOR AGENT
Reel/Frame 070115/0445 →
CHANGE OF NAME Recorded May 13, 2024
From: GENESYS TELECOMMUNICATIONS LABORATORIES, INC.
To: GENESYS CLOUD SERVICES, INC.
Reel/Frame 067391/0081 →
SECURITY AGREEMENT Recorded Feb 22, 2019
From: GENESYS TELECOMMUNICATIONS LABORATORIES, INC.; ECHOPASS CORPORATION; GREENEDEN U.S. HOLDINGS II, LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 048414/0387 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 27, 2017
From: ZHAKOV, VYACHESLAV I.; SAYKO, VYACHESLAV V.; TIKIN, ALEKSANDR V.
To: GENESYS TELECOMMUNICATIONS LABORATORIES, INC.
Reel/Frame 043972/0079 →
Continuity (6)
Continuation 14703772 · May 4, 2015
Continuation 11929766 · Oct 30, 2007
Continuation 11257896 · Oct 24, 2005
Continuation 10242250 · Sep 11, 2002
Provisional Application 60389703 · Jun 17, 2002
Related Publication 20180041636A1 · Feb 8, 2018