Telephony web event system and method
US-2015127723-A1 · May 7, 2015 · US
US12261981B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12261981-B2 |
| Application number | US-202318544171-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 18, 2023 |
| Priority date | Oct 1, 2008 |
| Publication date | Mar 25, 2025 |
| Grant date | Mar 25, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An embodiment of the system for publishing events of a telephony application to a client includes a call router that generates events from the telephony application and an event router that manages the publication of events generated by the call router and that manages the subscription to events by clients. The system can be used with a telephony application that interfaces with a telephony device and an application server.
Opening claim text (preview).
We claim: 1. A method comprising: generating, by a call router, an event from a telephony application or a telephony device during a communication session between the telephony application and the telephony device; publishing, by the call router, the generated event to an event router; identifying, by the event router, an application server for the published event; and sending the published event from the event router to the identified application server. 2. The method of claim 1 wherein the call router generates the event responsive to an instruction of the telephony application. 3. The method of claim 2 , wherein the call router receives the instruction of the telephony application from an external telephony application server. 4. The method of claim 3 , wherein the call router receives the instruction of the telephony application from the external telephony application server via an application programming interface (API). 5. The method of claim 3 , wherein the call router receives the instruction of the telephony application from the external telephony application server via one of an HTTP protocol and an HTTPS protocol. 6. The method of claim 3 , wherein the sending of the published event to the identified application server comprises sending the published event to the external telephony application server. 7. The method of claim 6 , wherein the event router sends the published event to the external telephony application server via an application programming interface (API) of the external telephony application server. 8. The method of claim 2 , wherein the instruction is an instruction to dial a phone number. 9. The method of claim 1 , wherein the telephony application controls interaction between the telephony device and the call router. 10. The method of claim 1 , wherein the generating of the event is based on the call router dialing a number. 11. The method of claim 1 , wherein the generating of the event is based on the call router starting a Text-To-Speech conversation. 12. The method of claim 1 , wherein the generating of the event is based on the call router gathering telephony input. 13. The method of claim 1 , wherein the generating of the event is based on the call router playing an audio file. 14. A system comprising: an event router; and a call router configured to perform operations comprising: generating an event from a telephony application or a telephony device during a communication session between the telephony application and the telephony device; and publishing the generated event to the event router; wherein the event router is configured to perform operations comprising: identifying an application server for the published event; and sending the published event to the identified application server. 15. The system of claim 14 , wherein the call router generates the event responsive to an instruction of the telephony application. 16. The system of claim 15 , wherein the call router receives the instruction of the telephony application from an external telephony application server. 17. The system of claim 16 , wherein the call router receives the instruction of the telephony application from the external telephony application server via an application programming interface (API). 18. The system of claim 16 , wherein the call router receives the instruction of the telephony application from the external telephony application server via one of an HTTP protocol and an HTTPS protocol. 19. The system of claim 16 , wherein the sending of the published event to the identified application server comprises sending the published event to the external telephony application server. 20. The system of claim 19 , wherein the event router sends the published event to the external telephony application server via an application programming interface (API) of the external telephony application server.
Details of addressing, directories or routing tables · CPC title
Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location (diverting calls from one subscriber to another subscriber, i.e. two different subscriptions H04M3/54; selecting arrangements in intelligent networks H04Q3/005) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Call detail recording · CPC title
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) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.