SIP service wrap

• US 8,924,567 B1
• Filed: 08/29/2008
• Issued: 12/30/2014
• Est. Priority Date: 08/29/2008
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Simoes, Renato, O'Reilly, Shawn
• Primary Examiner(s): Zele, Krista
• Assistant Examiner(s): DESAI, MARGISHI V
• Application Number:
  US12/201,565
• Time in Patent Office: 2,314 Days
• Field of Search: 370/259, 709/204, 709/227
• US Class Current: 709/227
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

Methods, devices, and systems for creating an intermediate layer between a SIP endpoint and a SIP service. The intermediate layer may operate to provide a greater flexibility in quickly adapting to customer requirements and/or requests of the SIP service that would, without the intermediate layer, have to wait for long release cycles and request changes directly from the SIP service. The intermediate layer provides a way of increasing the set of features provided to SIP endpoints around the SIP service without changing the SIP service itself.

Claims

1. A method, comprising:

receiving, at a service wrap framework, a message from a first endpoint, the message being directed toward a primary service that is wrapped within the service wrap framework, wherein the service wrap framework comprises applications or services that supplement or enhance the primary service, and wherein the service wrap framework comprises routing mechanisms for intercepting and re-routing messages directed toward the primary service before the primary service receives the message;

reviewing, at the service wrap framework, the intercepted message to determine whether a feature has been requested by the first endpoint;

determining, by the service wrap framework, that at least one requested feature is not supported by the primary service;

identifying, by the service wrap framework, an entity that is capable of providing the at least one requested feature not supported by the primary service;

altering sender information associated with the intercepted message;

directing, by the service wrap framework, the intercepted message to the identified entity that is capable of providing the at least one requested feature not supported by the primary service;

receiving, at the service wrap framework, the message back from the identified entity; and

altering, by the service wrap framework, sender information associated with the message received from the identified entity.

2. The method of claim 1, wherein the identified entity that is capable of providing the at least one requested feature not supported by the primary service is a server capable of providing the requested feature;

and

redirecting the message to the identified server instead of immediately forwarding the message to the primary service.

3. The method of claim 2, further comprising:

reviewing the message received back from the identified server to determine whether additional features have been requested by the first endpoint.

4. The method of claim 3, wherein the message received at the service wrap from the identified server includes a plurality of requested features, wherein at least one requested feature of the plurality of requested features is not supported by the primary service, and wherein at least one requested feature of the plurality of requested features is supported by the primary service.

5. The method of claim 1, wherein the message comprises a Session Initiation Protocol (SIP) message and wherein altering the sender information associated with the message comprises replacing the request URI field of the message with an address not associated with the first endpoint.

6. The method of claim 5, wherein the service wrap framework is located between the first endpoint and the primary service and wherein an address of the service wrap framework is placed in the request URI field of the message.

7. The method of claim 1, wherein the primary service comprises a SIP service.

8. The method of claim 1, further comprising:

forwarding the message to the primary service;

receiving a second message back from the primary service; and

forwarding the second message to at least one of the first endpoint and a second endpoint.

9. A non-transitory computer readable medium encoded with processor executable instructions that, when executed, perform the method of claim 1.

10. A communication system, comprising:

a primary service; and

a service wrap framework residing between the primary service and endpoints which utilize the primary service to provide features thereto, wherein the service wrap framework includes a non-transitory computer readable medium containing instructions to intercept a message from a first endpoint to the primary service before the primary service receives the message, review the message to determine whether a feature has been requested by the first endpoint, determine that at least one requested feature is not supported by the primary service, identify an entity that is capable of providing the at least one requested feature not supported by the primary service, alter sender information associated with the intercepted message, direct the intercepted message to the identified entity that is capable of providing the at least one requested feature not supported by the primary service, receive the message back from the identified entity, and alter sender information associated with the message received from the identified entity.

11. The system of claim 10, wherein the identified entity that is capable of providing the at least one requested feature not supported by the primary service is a server capable of providing the requested feature and the non-transitory computer readable medium of the service wrap framework contains instructions to redirect the message to the identified server.

12. The system of claim 11, wherein the non-transitory computer readable medium of the service wrap framework contains instruction to review the message received back from the identified server to determine whether additional features have been requested by the first endpoint.

13. The system of claim 10, wherein the message comprises a Session Initiation Protocol (SIP) message and wherein altering the sender information associated with the message comprises replacing the request URI field of the message with an address not associated with the first endpoint.

14. The system of claim 13, wherein an address of the service wrap framework is placed in the request URI field of the message and wherein the service wrap framework intercepts and analyzes all messages directed to and transmitted from the primary service.

15. The system of claim 10, wherein the primary service comprises a SIP service.

16. The system of claim 10, wherein the non-transitory computer readable medium of the service wrap framework contains instructions to forward the message to the primary service, receive a second message back from the primary service, and forward the second message to at least one of the first endpoint and a second endpoint.

17. The system of claim 10, wherein the message received at the service wrap from the first endpoint includes a plurality of requested features, wherein at least one requested feature of the plurality of requested features is not supported by the primary service, and wherein at least one requested feature of the plurality of requested features is supported by the primary service.

18. A communication device residing between a primary service and a first endpoint, the communication device including a non-transitory computer readable medium containing instructions to intercept all messages from the first endpoint to the primary service before the primary service receives the messages, review the messages to determine that at least one requested feature is not supported by the primary service, identify an entity that is capable of providing the at least one requested feature not supported by the primary service, alter sender information associated with the intercepted message, direct the intercepted message to the identified entity that is capable of providing the at least one requested feature not supported by the primary service, receive the message back from the identified entity, and alter sender information associated with the message received from the identified entity.

19. The device of claim 18, wherein the identified entity that is capable of providing the at least one requested feature not supported by the primary service is a server that is capable of providing the requested feature and the non-transitory computer readable medium of the service wrap framework contains instructions to redirect the message to the identified server.

20. The device of claim 18, wherein the message comprises a Session Initiation Protocol (SIP) message and wherein altering the sender information associated with the message comprises replacing a request URI field of the message with an address not associated with the first endpoint.