Abstract:
A method for communicating from an integration platform to a server that executes object request broker (ORB) software includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server. The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the data to the server.
Abstract:
The present invention is directed to a telephony system that includes a first network and a second network. The system includes a first network call control system configured to provide intelligent network control services to the first network. The first network call control system is also configured to store intelligent network control data corresponding to the intelligent network control services. A second network call control system is configured to provide control services to the second network. A secure channel couples the first network call control system to the second network call control system. The secure channel is configured to securely transmit intelligent network control data from the first network call control system to the second network call control system. As a result, the second network call control system provides the intelligent network control services to the second network.
Abstract:
A method for communicating from an integration platform to a directory server includes receiving user-entered information at the integration platform (1140). The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the directory server (1150). The connector receives the event information (1160), transforms the event information to a format compatible with the directory server (1170) and establishes communications with the directory server (1180). The connector downloads the information to the directory server and the directory server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the directory server.
Abstract:
A method for communicating from an integration platform to a profile management server (610) includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector (310) associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server via hypertext transfer protocol (HTTP). The connector downloads the information to the server and the server updates its database (615). The connector may also determine whether at least one other system received the event information before downloading the information to the server.
Abstract:
A method for communicating from an integration platform to a directory server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the directory server. The connector receives the event information, transforms the event information to a format compatible with the directory server and establishes communications with the directory server. The connector downloads the information to the directory server and the directory server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the directory server.
Abstract:
A method for communicating from an integration platform to a profile management server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server via hypertext transfer protocol (HTTP). The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the server.
Abstract:
A method for communicating from an integration platform to a server that executes object request broker (ORB) software includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel (1150) subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server (1170) and establishes communications with the server. The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the data to the server.
Abstract:
An operational support system (OSS) (130) updates a lightweight directory access protocol (LDAP) database (334) based on changes made to a second database such as the operational data store (ODS) (332). The system determines differences between Internet Protocol (IP) communication service records stored in the second database (332) and IP communication service records stored in the LDAP database (334). Then creates a transaction file based on the differences. The system updates the LDAP database (334) using the transaction file.