Telephony web event system and method
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.
1. A method comprising:
receiving, from a client device and via a network, a request to subscribe to events of one or more event types, the request including an account identifier and having an appended first verification token;
determining, by one or more processors and based on the account identifier, an encryption key;
generating, based on the encryption key and the request, a second verification token;
based on the appended first verification token matching the second verification token, establishing a subscription to events of the one or more event types;
detecting, by an event proxy server, an occurrence of an event of the one or more event types; and
based on the subscription having been established, sending a notification of the event from the event proxy server to the client device.
2. The method of claim 1 , wherein the first verification token comprises a hash of data comprising one or more subscription filters, the subscription filters including the one or more event types.
3. The method of claim 2 , wherein the subscription filters include characteristics of the one or more event types.
4. The method of claim 1 , wherein the request is sent to a Uniform Resource Locator (URL) that encodes a subscription URL and a filter.
5. The method of claim 4 , wherein the first verification token comprises a hash of data comprising the subscription URL.
6. The method of claim 1 , wherein the detecting of the occurrence of the event comprises receiving a notification from a message broker.
7. The method of claim 1 , further comprising determining that the client device is authorized to view events for the identified account.
8. A system comprising:
a computing device configured to perform operations comprising:
receiving, from a client device and via a network, a request to subscribe to events of one or more event types, the request including an account identifier and having an appended first verification token;
determining, based on the account identifier, an encryption key;
generating, based on the encryption key and the request, a second verification token;
based on the appended first verification token matching the second verification token, establishing a subscription to events of the one or more event types; and
an event proxy server configured to perform operations comprising:
detecting an occurrence of an event of the one or more event types; and
based on the subscription having been established, sending a notification of the event to the client device.
9. The system of claim 8 , wherein the first verification token comprises a hash of data comprising one or more subscription filters, the subscription filters including the one or more event types.
10. The system of claim 9 , wherein the subscription filters include characteristics of the one or more event types.
11. The system of claim 8 , wherein the request is sent to a Uniform Resource Locator (URL) that encodes a subscription URL and a filter.
12. The system of claim 11 , wherein the first verification token comprises a hash of data comprising the subscription URL.
13. The system of claim 8 , wherein the detecting of the occurrence of the event comprises receiving a notification from a message broker.
14. The system of claim 8 , wherein the computing device is further configured to determine that the client device is authorized to view events for the identified account.
15. A non-transitory machine-readable medium that stores instructions that, when executed by a computing device, cause the computing device to perform operations comprising:
receiving, from a client device and via a network, a request to subscribe to events of one or more event types, the request including an account identifier and having an appended first verification token;
determining, based on the account identifier, an encryption key;
generating, based on the encryption key and the request, a second verification token;
based on the appended first verification token matching the second verification token, establishing a subscription to events of the one or more event types;
detecting, by an event proxy server, an occurrence of an event of the one or more event types; and
based on the subscription having been established, sending a notification of the event from the event proxy server to the client device.
16. The non-transitory machine-readable medium of claim 15 , wherein the first verification token comprises a hash of data comprising one or more subscription filters, the subscription filters including the one or more event types.
17. The non-transitory machine-readable medium of claim 16 , wherein the subscription filters include characteristics of the one or more event types.
18. The non-transitory machine-readable medium of claim 15 , wherein the request is sent to a Uniform Resource Locator (URL) that encodes a subscription URL and a filter.
19. The non-transitory machine-readable medium of claim 18 , wherein the first verification token comprises a hash of data comprising the subscription URL.
20. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise determining that the client device is authorized to view events for the identified account.