System and method for integrating session initiation protocol communication in a telecommunications platform

• US 10,051,011 B2
• Filed: 01/25/2016
• Issued: 08/14/2018
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Boerjesson, Jonas, Wolthuis, John, Lawson, Jeffrey, Cooke, Evan
• Primary Examiner(s): Survillo, Oleg
• Application Number:
  US15/005,190
• Publication Number:
  US 20160142446A1
• Time in Patent Office: 932 Days
• Field of Search: 709219, 709227
• CPC Class Codes: H04L 61/106 across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 65/1013 Network architectures, gateways, control or user entities
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 1/2473 Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface) details of API H04M7/0021
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

A system and method for facilitating signaling and media communication at a communication platform that includes receiving a communication request to a resource, wherein the communication request specifies a destination endpoint; establishing signaling and media communication in a session with the destination endpoint of the communication request; registering a callback resource to a signaling event of the session; monitoring signaling messages of the session; detecting the signaling event in the signaling messages of the session; and triggering the callback resource upon detecting the signaling event.

Claims

1. A method comprising:

at a multi-tenant communication platform system that includes a SIP (Session Initiation Protocol) communication router and a callback engine;

detecting, using the callback engine, a SIP signaling event message that is registered in association with a callback URI from a plurality of communicated SIP signaling event messages communicated for a SIP communication session of the SIP communication router, the plurality of communicated SIP signaling event messages including at least one of a SIP signaling event message provided by the communication router and a SIP signaling event message received by the communication router, the callback URI being registered for an account of the communication platform system, the callback URI being a URI of an application of an external system of an account holder of the account;

responsive to detection of the SIP signaling event message by the callback engine, providing an application layer request to the external system of the account holder, the application layer request specifying the callback URI.

2. The method of claim 1,

further comprising, at the platform system and during the SIP communication session, responsive to a signaling message that includes a parameter defining the callback URI:

authenticating tokens included in the signaling message; and

verifying the account,

wherein the callback URI is registered according to the parameter in the signaling message.

3. The method of claim 1, wherein the callback URI is registered responsive to a received application programming interface (API) communication that identifies the SIP communication session and specifies the callback URI.

4. The method of claim 1, wherein the registered SIP signaling event message indicates that media communication is ending.

5. The method of claim 4, wherein responsive to detection of the SIP signaling event message by the callback engine, the platform system enables a communication application mode.

6. The method of claim 5, further comprising, at the platform system, accounting usage by the account in an original communication mode and accounting usage in the communication application mode, wherein usage in the original communication mode is distinct from usage in the communication application mode.

7. The method of claim 5, further comprising, at the platform system, transitioning from the communication application mode to a basic communication mode.

8. The method of claim 1, further comprising, at the platform system, enabling media processing during the SIP communication session, wherein media processing includes selectively enabling media recording during the SIP communication session.

9. The method of claim 1, further comprising:

mapping a destination endpoint specified in an incoming communication signaling request to a primary account routing configuration;

in a case where the primary account routing configuration specifies a signaling endpoint, routing an invitation signal to the signaling endpoint and establishing media communication between an originating endpoint of the incoming communication request and the signaling endpoint; and

in a case where the primary account routing configuration specifies an application resource identifier, retrieving an application specified by the application resource identifier and processing the application in directing media communication of the SIP communication session.

10. The method of claim 9,

wherein the signaling endpoint includes metadata embedded in the endpoint,

the method further comprising:

routing the incoming communication signaling request to a signaling application module;

at the signaling application module, coordinating signaling and media control according to the metadata.

11. The method of claim 9, further comprising:

mapping the destination endpoint to a secondary account routing configuration;

responsive to detection of an error event, establishing media communication of the SIP communication session according to the secondary account routing configuration.

12. A multi-tenant communication platform system comprising:

a SIP (Session Initiation Protocol) communication router; and

a callback engine constructed to detect a SIP signaling event message that is registered in association with a callback URI from a plurality of communicated SIP signaling event messages communicated for a SIP communication session of the SIP communication router, the plurality of communicated SIP signaling event messages including at least one of a SIP signaling event message provided by the communication router and a SIP signaling event message received by the communication router, the callback URI being registered for an account of the communication platform system, the callback URI being a URI of an application of an external system of an account holder of the account,

wherein responsive to detection of the SIP signaling event message by the callback engine, the communication platform system is constructed to provide an application layer request to the external system of the account holder, the application layer request specifying the callback URI.

13. The system of claim 12,

wherein during the SIP communication session and responsive to a signaling message that includes a parameter defining the callback URI, the platform system is constructed to:

authenticate tokens included in the signaling message; and

verify the account, and

wherein the callback URI is registered according to the parameter in the signaling message.

14. The system of claim 12, wherein the callback URI is registered responsive to a received application programming interface (API) communication that identifies the SIP communication session and specifies the callback URI.

15. The system of claim 12, wherein the registered SIP signaling event message indicates that media communication is ending.

16. The system of claim 15, wherein responsive to detection of the SIP signaling event message by the callback engine, the platform system is constructed to enable a communication application mode.

17. The system of claim 15, wherein the platform system is constructed to account usage by the account in an original communication mode and account usage in the communication application mode, wherein usage in the original communication mode is distinct from usage in the communication application mode.

18. The system of claim 15, wherein the platform system is constructed to transition from the communication application mode to a basic communication mode.

19. The system of claim 12, wherein the platform system is constructed to enable media processing during the SIP communication session, wherein media processing includes selectively enabling media recording during the SIP communication session.

20. The system of claim 12, wherein the platform system is constructed to:

map a destination endpoint specified in an incoming communication signaling request to a primary account routing configuration;

in a case where the primary account routing configuration specifies a signaling endpoint, route an invitation signal to the signaling endpoint and establish media communication between an originating endpoint of the incoming communication request and the signaling endpoint; and

in a case where the primary account routing configuration specifies an application resource identifier, retrieve an application specified by the application resource identifier and process the application in directing media communication of the SIP communication session.