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

• US 9,282,124 B2
• Filed: 03/13/2014
• Issued: 03/08/2016
• 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:
  US14/208,920
• Publication Number:
  US 20140274086A1
• Time in Patent Office: 726 Days
• Field of Search: 709/219, 709/227
• US Class Current: 1/1
• 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, a communication application module, and a callback engine, the callback engine being constructed to monitor SIP signaling event messages of the SIP communication router and communicate with a registered callback resource in response to detection of at least one SIP signaling event message specified for the registered callback resource at the callback engine, the registered callback resource being registered for an account of the multi-tenant communication platform system;

at the SIP communication router, receiving an incoming SIP communication request of an originating endpoint;

establishing, using the communication router, a media communication of a SIP communication session according to the incoming SIP communication request;

at the communication platform system, registering a callback resource in association with a SIP signaling event message of a plurality of SIP signaling event messages, the registered callback resource being registered for the account of the communication platform system, the callback resource including a URI of an application of an external system of an account holder of the account;

detecting, using the callback engine, the signaling event message registered in association with the callback resource from a plurality of communicated SIP signaling event messages communicated for the SIP communication session, 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;

triggering, using the callback engine, the callback resource responsive to detection of the SIP signaling event message by the callback engine,

wherein triggering the registered callback resource comprises;

making an application layer request to the URI of the application of the external system of the account holder.

2. The method of claim 1, wherein the SIP communication session is between the originating endpoint and at least one destination endpoint specified in the SIP communication request, the callback resource being different from the originating endpoint and the at least one destination endpoint.

3. The method of claim 2, wherein triggering the callback resource comprises making an application layer communication to an external resource specified by the callback resource, wherein the application layer communication includes metadata of the SIP communication session.

4. The method of claim 2, further comprising, during the SIP communication session, receiving a signaling message that includes a parameter defining the callback resource;

authenticating tokens included in the signaling message and verifying an account; and

wherein registering a callback resource comprises registering the callback resource according to the parameter in the signaling message.

5. The method of claim 2, further comprising, receiving an application programming interface (API) communication that identifies the SIP communication session and specifies the callback resource.

6. The method of claim 2, wherein the SIP signaling event message signals that a connected endpoint is ending media communication.

7. The method of claim 6, wherein triggering the callback resource comprises, enabling a second communication application mode.

8. The method of claim 7, further comprising accounting usage by an 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.

9. The method of claim 7, further comprising transitioning from the second communication application mode to a basic communication mode.

10. The method of claim 2, further comprising enabling media processing during the SIP communication session, wherein media processing can selectively enable media recording during the SIP communication session.

11. The method of claim 2, further comprising:

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

determining whether the primary account routing configuration specifies a signaling endpoint or an application resource identifier;

in a case where it is determined that the primary account routing configuration specifies a signaling endpoint, using the communication router to establish a media communication of the SIP communication session comprises routing an invitation signal to the signaling endpoint and establishing the media communication from an originating endpoint of the incoming communication request and the signaling endpoint;

in a case where it is determined that the primary account routing configuration specifies an application resource identifier, using the communication router to establish a media communication of the SIP communication session comprises retrieving an application specified by the application resource identifier and processing the application in directing the media communication.

12. The method of claim 11, wherein the signaling endpoint includes metadata embedded in the endpoint;

and further comprising routing the incoming communication request to a signaling application module;

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

13. The method of claim 11, further comprising mapping the destination endpoint to a secondary account routing configuration;

detecting an error event;

if an error event is detected, using the communication router to establish a media communication of the SIP communication session according to the secondary account routing configuration.

14. The method of claim 2, wherein the destination endpoint is a SIP address.

15. The method of claim 2, wherein the callback resource is an application hosted by an application server external to the communication platform.

16. The method of claim 15,

wherein the destination endpoint is an application URI of a communication application,

wherein the communication application includes at least one of a an application to play recordings, an application to perform TTS (Text to Speech), an application to capture input, an application to record messages, an application to connect other endpoints, and an application to control interactions during a SIP communication session, and

wherein the communication application is hosted by the communication platform.

17. The method of claim 1, wherein SIP signaling event messages include at least one of a SIP Trying message, a SIP INVITE message, a SIP Ringing message, a SIP OK message, and a SIP BYE message.

18. The method of claim 1, further comprising monitoring the plurality of communicated SIP signaling event messages, wherein detecting the signaling event message comprises detecting at least one of the monitored plurality of communicated SIP signaling messages as the SIP signaling event message registered to the callback resource.

19. The method of claim 1,

further comprising, at the communication platform, registering a second callback resource in association with a second SIP signaling event message of the plurality of SIP signaling event messages,

wherein the second callback resource is triggered responsive to detection of the second SIP signaling event message by the callback engine, the second SIP signaling message being detected from the plurality of communicated SIP signaling event messages.

21. The method of claim 14, wherein the SIP session is between an originator of the communication request and at least one destination endpoint including the specified destination endpoint, the callback resource being different from the originator and the at least one destination endpoint.

22. The method of claim 21, wherein the at least one destination endpoint is a SIP address.

23. The method of claim 22, wherein triggering the callback resource comprises making an application layer communication that includes metadata of the session to an external resource specified by the callback resource.

24. The method of claim 23, triggering the callback resource further comprises receiving a response to the application layer communication, wherein the response includes communication instructions;

further comprising processing the communication instructions in directing the media communication.

25. The method of claim 24, wherein the communication request is received through an application programming interface (API) request that specifies one destination endpoint to contact;

and wherein processing the communication instructions comprises establishing media communication with a second endpoint specified in the communication instructions and bridging the media communication of the second endpoint and the destination endpoint.

26. The method of claim 23, wherein the signaling event message signals that a connected endpoint is ending media communication.

27. The method of claim 26, wherein triggering the callback resource comprises, enabling a second communication application mode.

28. The method of claim 27, further comprising metering usage in the second communication application mode distinct from metering usage in a basic communication mode.

29. The method of claim 27, further comprising receiving a directive when in the second communication application mode;

and transitioning to a basic communication mode of routing a media communication between at least two endpoints.

30. The method of claim 22, further comprising enabling media processing during the SIP session, wherein media processing can selectively include media recording during the SIP session.

31. The method of claim 22, wherein registering the callback resource comprises registering the callback resource in the SIP session according to account settings associated with the communication.

32. The method of claim 22, further comprising:

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

determining whether the primary account routing configuration specifies a signaling endpoint or an application resource identifier;

in a case where it is determined that the primary account routing configuration specifies a signaling endpoint, using the communication router of the communication platform to establish media communication of the SIP session comprises routing an invitation signal to the signaling endpoint and establishing the media communication from an originating endpoint of the incoming communication request and the signaling endpoint;

in a case where it is determined that the primary account routing configuration specifies an application resource identifier, using the communication router of the communication platform to establish media communication of the SIP session comprises retrieving and processing an application specified by the application resource identifier to direct the media communication.

33. The method of claim 32, wherein the signaling endpoint includes metadata embedded in the endpoint;

and further comprising routing the incoming communication request to a signaling application module;

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

34. The method of claim 22, wherein the communication request includes an authentication token;

further comprising identifying an account of the communication platform that is mapped to a domain identifier of the originating endpoint;

verifying the authentication token of the user account;

if the credentials are successfully verified, establishing media communication with the destination of the communication, wherein the destination is defined by the a username identifier of the destination endpoint.

35. The method of claim 34, wherein the communication request further includes feature headers;

and further comprising enabling communication augmentation features in accordance with the feature headers.

36. The method of claim 34, wherein the communication request includes a parameter defining the callback resource registered to the SIP signaling event message of the SIP session.

37. The method of claim 22, further comprising, during the SIP session, receiving a signaling message that includes a parameter defining the callback resource, wherein registering a callback resource comprises registering the callback resource according to the parameter in the signaling message.

38. The method of claim 22, further comprising, during the SIP session, receiving an application programming interface (API) communication that identifies the SIP session and specifies the callback resource.

20. A method comprising:

at a multi-tenant communication platform system that includes a SIP (Session Initiation Protocol) communication router, a communication application module, and a callback engine, the callback engine being constructed to monitor SIP signaling event messages of the SIP communication router and communicate with a registered callback resource in response to detection of at least one SIP signaling event message specified for the registered callback resource at the callback engine, the registered callback resource being registered for an account of the multi-tenant communication platform system;

at the communication platform system, receiving a communication request to a resource, wherein the communication request specifies a destination endpoint;

establishing, using the SIP communication router, signaling and media communication in SIP session with the destination endpoint of the communication request;

at the communication platform system, registering the callback resource in association with a SIP signaling event message of a plurality of SIP signaling event messages, the registered callback resource being registered for the account of the communication platform system, the callback resource including a URI of an application of an external system of an account holder of the account;

monitoring a plurality of communicated SIP signaling event messages communicated for the SIP session, 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;

detecting, using the callback engine, at least one of the monitored plurality of communicated SIP signaling messages as the SIP signaling event message registered to the callback resource; and

triggering, using the callback engine, the registered callback resource responsive to detection of the SIP signaling event message by the callback engine,

wherein triggering the registered callback resource comprises;

making an application layer request to the URI of the application of the external system of the account holder.

39. A method comprising:

at a multi-tenant communication platform system that includes a SIP (Session Initiation Protocol) communication router, a communication application module, and a callback engine, the callback engine being constructed to monitor SIP signaling event messages of the SIP communication router and communicate with a registered callback resource in response to detection of at least one SIP signaling event message specified for the registered callback resource at the callback engine, the registered callback resource being registered for an account of the multi-tenant communication platform system;

at the SIP communication router, receiving an incoming SIP communication request of an originating endpoint;

establishing, using the communication router, a media communication of a SIP communication session according to the incoming SIP communication request;

at the communication platform system, registering the callback resource in association with a SIP signaling event message of a plurality of SIP signaling event messages, the registered callback resource being registered for the account of the communication platform system, the callback resource including a URI of an application of an external system of an account holder of the account;

monitoring a plurality of communicated SIP signaling event messages communicated for the SIP communication session, 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;

detecting, using the callback engine, at least one of the monitored plurality of communicated SIP signaling messages as the SIP signaling event message registered to the callback resource;

triggering, using the callback engine, the registered callback resource responsive to detection of the SIP signaling event message by the callback engine,

wherein triggering the registered callback resource comprises;

making an application layer request to the URI of the application of the external system of the account holder,

wherein the plurality of SIP signaling event messages include at least one of a SIP Trying message, a SIP INVITE message, a SIP Ringing message, a SIP OK message, and a SIP BYE message.

40. The method of claim 39, further comprising, during the SIP communication session, receiving a signaling message of the account that includes a parameter defining the callback resource;

authenticating tokens that are included in the signaling message; and

verifying the account; and

wherein registering a callback resource comprises registering the callback resource according to the parameter in the signaling message.

41. The method of claim 39, further comprising, receiving an application programming interface (API) communication of the account, the API communication identifying the SIP communication session and specifying the callback resource.

42. The method of claim 39, wherein registering the callback resource comprises registering the callback resource for the SIP communication session according to account settings of the account that are associated with the SIP communication session.

43. The method of claim 39, wherein the communication request includes a parameter defining the callback resource.

44. The method of claim 39, further comprising:

at the communication platform system, registering a communication mode transition signal resource in association with a SIP signaling event message of a plurality of SIP signaling event messages, the registered communication mode transition signal resource being registered for the account of the communication platform system; and

triggering, using the callback engine, the registered communication mode transition signal resource responsive to detection of the SIP signaling event message registered for the communication mode transition signal resource, triggering the registered communication mode transition signal resource comprising;

initiating a transition signal to change a communication mode of the SIP communication session, the communication mode including one of an application communication mode and a basic communication mode, the platform system using the communication application module to process the SIP communication session in the application communication mode, and the platform system using a SIP trunking service to process the SIP communication session in the basic communication mode.

45. The method of claim 44, further comprising:

accounting usage by the account in the basic communication mode and accounting usage by the account in the application communication mode, wherein usage in the basic communication mode is distinct from usage in the application communication mode.