Abstract: Systems (100) and methods (500) for connecting network resources of a first network (116) to network resources of a second network (118). The second network is different from the first network. The methods involve receiving a first message (302, 402) from a first network resource (106) of the first network. The first message has a first protocol format. In response to the first message, a second message (308, 408) having a web service request format is dynamically generated. The second message is communicated to a third network resource (112) of the second network for conversion into a third message (314). The third message has a second protocol format different from the first protocol format. The first network can be an SIP network. The second network can be an SS7 network.

Abstract: The present invention discloses use of resource lists to invoke multiple services in an IMS environment. More specifically, SIP clients can exchange XML content with each other and/or with SIP servers that includes an XCAP resource list. A list entry can exist for each service that is to be included within a communication session. Each service specifying entry can include sub-attributes for the service, which comprise attribute-value pairs able to be read using standard conventions. Use of the resource lists alleviates a need to define a schema and write custom code each time a new service is developed. In one embodiment, additional nested XCAP resource lists can be used to define content that is to be shared among multiple services. For example, a resource list can be used to define a participant list, which is shared as common input data across the multiple services.

Abstract: An apparatus, system, and method are disclosed for validating application server replication errors. The method includes receiving a first information message with a test sequence from a caller. The caller is engaged in a communication session with a callee according to a communication protocol and the communication session is managed by a first application server. The method also includes storing the test sequence in a replicable data structure on the first application server. The replicable data structure is replicated to a second application server to form a replicated data structure and both servers operate within an active-active configuration. The method also includes receiving a second information message from the caller. The second information message includes a confirmation sequence. In addition, the method includes determining a replication error in response to comparing the stored test sequence in the replicated data structure with the confirmation sequence.

Abstract: An apparatus, system, and method are disclosed for validating application server replication errors. The method includes receiving a first information message with a test sequence from a caller. The caller is engaged in a communication session with a callee according to a communication protocol and the communication session is managed by a first application server. The method also includes storing the test sequence in a replicable data structure on the first application server. The replicable data structure is replicated to a second application server to form a replicated data structure and both servers operate within an active-active configuration. The method also includes receiving a second information message from the caller. The second information message includes a confirmation sequence. In addition, the method includes determining a replication error in response to comparing the stored test sequence in the replicated data structure with the confirmation sequence.

Abstract: The present invention discloses use of resource lists to invoke multiple services in an IMS environment. More specifically, SIP clients can exchange XML content with each other and/or with SIP servers that includes an XCAP resource list. A list entry can exist for each service that is to be included within a communication session. Each service specifying entry can include sub-attributes for the service, which comprise attribute-value pairs able to be read using standard conventions. Use of the resource lists alleviates a need to define a schema and write custom code each time a new service is developed. In one embodiment, additional nested XCAP resource lists can be used to define content that is to be shared among multiple services. For example, a resource list can be used to define a participant list, which is shared as common input data across the multiple services.