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

Patent metadata

Field	Value
Publication number	US-11637876-B2
Application number	US-202117302605-A
Country	US
Kind code	B2
Filing date	May 7, 2021
Priority date	Mar 14, 2013
Publication date	Apr 25, 2023
Grant date	Apr 25, 2023

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.

First claim

What is claimed is:

1. A method comprising:
based on detecting a Session Initiation Protocol (SIP) message for a SIP communication session, identifying a callback identifier registered to the SIP communication session;
transmitting a message directed to the callback identifier, the message including data related to the detected SIP message;
receiving a response to the message directed to the callback identifier, the response including instructions to modify an operating mode of the SIP communication session from a trunking mode to enable application processing; and
performing the modifying of the operating mode of the SIP communication session from the trunking mode to enable application processing based on the instructions included in the response.

2. The method of claim 1 , further comprising:
based on detecting an occurrence of a signaling event, identifying a second callback identifier registered to a second SIP communication session associated with the detected occurrence of the signaling event; and
transmitting a second message directed to the second callback identifier, the second message including data related to the detected occurrence of the signaling event.

3. The method of claim 1 , further comprising:
receiving an Application Programming Interface (API) communication that specifies the callback identifier and a client device that sent the SIP message;
registering the callback identifier to an account associated with the SIP communication session; and
associating the callback identifier with e client device ending the SIP communication session.

4. The method of claim 1 , wherein the message directed to the callback identifier is a HyperText Transfer Protocol (HTTP) message that includes parameters from the SIP communication session as parameters within the message.

5. The method of claim 4 , wherein the parameters from the SIP communication session include data from a header field of a SIP transaction message from the SIP communication session.

6. The method of claim 1 , wherein the instructions were generated based on the data related to the detected SIP message that was included in the message directed to the callback identifier.

7. A system comprising:
one or more computer processors; and
one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the system to perform operations comprising:
based on detecting a Session initiation Protocol (SIP) message for a SIP communication session, identifying a callback identifier registered to the SIP communication session;
transmitting a message directed to the callback identifier, the message including data related to the detected SIP message;
receiving a response to the message directed to the callback identifier, the response including instructions to modify an operating mode from a trunking mode of the SIP communication session to enable application processing; and
performing the modifying of the operating mode of the SIP communication session from the trunking mode to enable application processing based on the instructions included in the response.

8. The system of claim 7 , the operations further comprising:
based on detecting an occurrence of a signaling event, identifying a second callback identifier registered to a second SIP communication session associated with the detected occurrence of the signaling event; and
transmitting a second message directed to the second callback identifier, the second message including data, related to the detected occurrence of the signaling event.

9. The system of claim 7 , the operations further comprising:
receiving an Application Programming Interface (API) communication that specifies the callback identifier and a client device that sent the SIP message;
registering the callback identifier to an account associated with the SIP communication session; and
associating the callback identifier with the client device ending the SW communication session.

10. The system of claim 7 , wherein the message directed to the callback identifier is a HyperText Transfer Protocol (HTTP) message that includes parameters from the SIP communication session as parameters within the HTTP message.

11. The system of claim 10 , wherein the parameters from the SIP communication session include data from a header field of a SIP transaction message from the SIP communication session.

12. The system of claim 7 , wherein the instructions were generated based on the data related to the detected SIP BYE message that was included in the message directed to the callback identifier.

13. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of one or more computing devices, cause the one or more computing devices to perform operations comprising:
based on detecting a Session Initiation Protocol (SIP) message for a SIP communication session, identifying a callback identifier registered to the SIP communication session;
transmitting a message directed to the callback identifier, the message including data related to the detected SIP message;
receiving a response to the message directed to the callback identifier, the response including instructions to modify an operating mode from a trunking mode of the SIP communication session to enable application processing; and
performing the modifying of the operating mode of the SIP communication session from the trunking mode to enable application processing based on the instructions included in the response.

14. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
based on detecting an occurrence of a signaling event, identifying a second callback identifier registered to a second SIP communication session associated with the detected occurrence of the signaling event; and
transmitting a second message directed to the second callback identifier, the second message including data related to the detected occurrence of the signaling event.

15. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
receiving an Application Programming Interface (API) communication that specifies the callback identifier and a client device that sent the SIP message;
registering the callback identifier to an account associated with the SIP communication session; and
associating the callback identifier with the client device ending the SW communication session.

Assignees

• Twilio Inc

Inventors

• Boerjesson Jonas
• Wolthuis John
• Lawson Jeffrey
• Cooke Evan

Classifications

• H04L65/1069 Primary

  Session establishment or de-establishment · CPC title

• H04L65/1073

  Registration or de-registration · CPC title

• H04L65/1104 Primary

  Session initiation protocol [SIP] · CPC title

• H04L65/1013

  Network architectures, gateways, control or user entities · CPC title

• H04L67/14

  Session management (for real-time applications in data packet communications networks H04L65/1066) · CPC title