Abstract: A method is described for communicating changes in a main database to a database cache associated with a client application. The main database is stored on a server that is remote from and in communication with the database cache. The method includes: receiving, at an emitter associated with the main database, a set of changes in the main database, each change in the set of changes having a transaction identifier (ID) associated with an atomic transaction; queuing, at the emitter, the received set of changes until a commit associated with the atomic transaction is received; and in response to receipt of the commit, sending a transaction notification from the emitter to a publisher, the transaction notification corresponding to all changes associated with the atomic transaction and having the same transaction ID. Advantageously, transaction-level notifications are sent, rather than row-level notifications.

Abstract: A solution for the Network Address Translation (NAT) traversal problem for Real Time Protocol (RTP) is provided, which uses an RTP Proxy (e.g., a Session Border Controller (SBC)), instead of being logically located between the NAT and the Feature Server (FS), but instead, for devices which use a protocol unsupported by the SBC, having these devices first signal the Feature Server, which determines whether and how an RTP proxy should be invoked. An RTP proxy should be invoked by the FS if Both endpoints (e.g., devices) are behind different NATs (or one of the endpoints is behind a NAT and the other is not) and neither of the endpoints are already signaled through an RTP proxy. For example, the SBC is interposed (at least logically) between the Feature Server and other shared components.

Abstract: The solutions offered herein include introducing a mediator in the codec: negotiation process. Rather than having the endpoints negotiate codecs directly, the mediator receives signaling from the endpoints relating to the establishment of a communication session which requires codec negotiation, and influences the selection of a codec based on codec policy criteria which depends on known topology information.

Abstract: A solution for the Network Address Translation (NAT) traversal problem for Real Time Protocol (RTP) is provided, which uses an RTP Proxy (e.g., a Session Border Controller (SBC)), instead of being logically located between the NAT and the Feature Server (FS), but instead, for devices which use a protocol unsupported by the SBC, having these devices first signal the Feature Server, which determines whether and how an RTP proxy should be invoked. An RTP proxy should be invoked by the FS if Both endpoints (e.g., devices) are behind different NATs (or one of the endpoints is behind a NAT and the other is not) and neither of the endpoints are already signaled through an RTP proxy. For example, the SBC is interposed (at least logically) between the Feature Server and other shared components.

Abstract: A system for enabling multiple types of end user devices to access an Internet-based application, the system comprising: an AMI component communicating with the application; a DMI component communicating with the devices; a broker module communicating with the DMI component and with the AMI component, wherein the DMI component converts end data received from the broker module into a format suitable for the devices; the DMI component transmits replies to prompts from the broker module based on an end user's input into the devices; the broker module emulates a sequence of events and decisions followed by the application; the broker module requests application data from the AMI component based on the broker module emulating the application; the AMI component receives requests from the broker module and transmits replies to the requests to the broker module based on original data from the application, the broker module transmits end date to the DMI component, the end data being based on at least one factor chosen