Communicating with session initiation protocol (SIP) application sessions using a message-oriented middleware system

• US 8,331,351 B2
• Filed: 01/05/2007
• Issued: 12/11/2012
• Est. Priority Date: 01/05/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gilfix, Michael, Ulerich, Rhys D.
• Primary Examiner(s): Patel, Chandrahas
• Assistant Examiner(s): CHANG, STEPHANIE L
• Application Number:
  US11/620,454
• Publication Number:
  US 20080165762A1
• Time in Patent Office: 2,167 Days
• Field of Search: 370/352, 370/229, 370/401, 370/467, 709/207, 709/206, 709/227
• US Class Current: 370/352
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

A messaging service communicates with a Session Initiation Protocol (SIP) application session by registering the SIP application session with a messaging server, and then publishing an addressable messaging endpoint corresponding to the SIP application session in response to registering the SIP 15 application session with the messaging server. Consequently, communication with the SIP application session can occur via messages directed to the published addressable messaging endpoint.

Claims

1. A computer-implemented method of communicating with a Session Initiation Protocol (SIP) application session using a messaging service comprising:

defining an SIP application server as an application specific point-to-point queue;

creating, using an SIP servlet, an SIP application session on an SIP client and on an SIP application server, wherein the SIP servlet implements a Java Message Service (JMS) message listener and a SIP application session message listener, wherein the SIP application session message listener instantiates a SIP application message listener object, wherein the SIP application message listener object implements a JMS listener interface and holds a reference to the SIP application session;

providing an SIP application session identification;

registering the SIP application session message listener with the SIP application server using a selector requiring that a JMS application identification header equals the SIP application session identification;

storing the SIP application session message listener within the SIP application session as an attribute;

publishing an addressable messaging endpoint corresponding to the SIP application session in response to registering the SIP application session message listener with the SIP application server; and

communicating between the SIP application server and the SIP application session on the SIP client via messages directed to the published addressable messaging endpoint through a JMS transport and an SIP transport linking the SIP application session on the client and on the SIP application server.

2. The computer-implemented method of claim 1 wherein the messages are Web services or hypertext transport protocol (HTTP) requests and responses.

3. The computer-implemented method of claim 1 wherein registering the SIP application session with the messaging server includes subscribing the SIP application session to a message topic.

4. A computer program product on one or more computer readable tangible storage devices for allowing for communication with a Session Initiation Protocol (SIP) application session using a messaging service comprising:

program instructions stored on one or more computer readable tangible storage devices for defining an SIP application server as an application specific point-to-point queue;

program instructions stored on the one or more computer readable tangible storage devices for creating, using an SIP servlet, an SIP application session on an SIP client and on an SIP application server, wherein the SIP servlet implements a Java Message Service (JMS) message listener and a SIP application session message listener, wherein the SIP application session message listener instantiates a SIP application message listener object, wherein the SIP application message listener object implements a JMS listener interface and holds a reference to the SIP application session;

program instructions stored on the one or more computer readable tangible storage devices for providing an SIP application session identification;

program instructions stored on the one or more computer readable tangible storage devices for registering the SIP application session message listener with the SIP application server using a selector requiring that a JMS application identification header equals the SIP application session identification;

program instructions stored on the one or more computer readable tangible storage devices for storing the SIP application session message listener within the SIP application session as an attribute;

program instructions stored on the one or more computer readable tangible storage devices for publishing an addressable messaging endpoint corresponding to the SIP application session in response to registering the SIP application session message listener with the SIP application server; and

program instructions stored on the one or more computer readable tangible storage devices for communicating between the SIP application server and the SIP application session on the SIP client via messages directed to the published addressable messaging endpoint through a JMS transport and an SIP transport linking the SIP application session on the client and on the SIP application server.

5. The computer program product of claim 4 wherein the messages are Web services or hypertext transport protocol (HTTP) requests and responses.

6. The computer program product of claim 4 wherein registering the SIP application session with the messaging server includes subscribing the SIP application session to a message topic.

7. A computer system for communicating with a Session Initiation Protocol (SIP) application session using a messaging service comprising:

one or more processors, one or more computer readable memories, and one or more computer readable tangible storage devices;

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for defining an SIP application server as an application specific point-to-point queue;

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for creating, using an SIP servlet, an SIP application session on an SIP client and on an SIP application server, wherein the SIP servlet implements a Java Message Service (JMS) message listener and a SIP application session message listener, wherein the SIP application session message listener instantiates a SIP application message listener object, wherein the SIP application message listener object implements a JMS listener interface and holds a reference to the SIP application session;

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for providing an SIP application session identification;

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for registering the SIP application session message listener with the SIP application server using a selector requiring that a JMS application identification header equals the SIP application session identification;

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for storing the SIP application session message listener within the SIP application session as an attribute;

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for publishing an addressable messaging endpoint corresponding to the SIP application session in response to registering the SIP application session message listener with the SIP application server; and

program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more computer readable memories for communicating between the SIP application server and the SIP application session on the SIP client via messages directed to the published addressable messaging endpoint through a JMS transport and an SIP transport linking the SIP application session on the client and on the SIP application server.

8. The computer system of claim 7 wherein the messages are Web services or hypertext transport protocol (HTTP) requests and responses.

9. The computer system of claim 7 wherein registering the SIP application session with the messaging server includes subscribing the SIP application session to a messaging topic.