Method and system for implementing a stateless back to back user agent

1. A method for providing a stateless Session Interface Protocol (SIP) back to back user agent (B2BUA) comprising:

receiving a SIP message;

determining if said SIP message is a SIP request;

determining if said SIP message is a SIP response;

transforming one or more determined said SIP request, a first record-route header being inserted into selected SIP requests to a user agent server;

transforming one or more determined said SIP response, wherein transforming SIP messages replaces SIP dialog state information in each transformed message, said first record-route header being inserted into selected SIP responses to a user agent client, said first record-route header including Uniform Resource Identifiers (URIs) from an original said SIP dialog state information;

transmitting each said transformed SIP request to a new destination; and

transmitting each said transformed SIP response to a request originator.

2. The method of claim 1 , further comprising inserting a first via header into said selected SIP requests.

3. The method of claim 2 , further comprising inserting said first via header into said selected SIP responses, said first via header including sufficient information to reconstruct original headers.

4. The method of claim 3 , wherein said first record-route header and said first via header are suitable for transferring SIP dialog state data to an endpoint.

5. The method of claim 4 , wherein said first record-route header and said first via header are suitable for reconstructing said SIP dialog state data on a receiving second record-route header or a second via header in a subsequent SIP message received from said endpoint.

6. A method for providing a stateless Session Interface Protocol (SIP) back to back user agent (B2BUA) comprising:

receiving a SIP message;

determining if said SIP message is a SIP request, said SIP request further comprising a request to create an original SIP dialog or a request for an existing SIP dialog;

determining if said SIP message is a SIP response, said SIP response further comprising a provisional SIP response or a final SIP response;

transforming one or more said SIP request, a first record-route header being inserted into selected SIP requests to a user agent server;

transforming one or more said SIP response, wherein transforming SIP messages replaces SIP dialog state information in each transformed message, said first record-route header being inserted into selected SIP responses to a user agent client, said first record-route header including Uniform Resource Identifiers (URIs) from an original said SIP dialog state information;

transmitting each said transformed SIP request to a new destination; and

transmitting each said transformed SIP response to a request originator.

7. The method of claim 6 , further comprising inserting a first via header into said selected SIP requests.

8. The method of claim 7 , further comprising inserting said first via header into said selected SIP responses, said first via header including sufficient information to reconstruct original header values.

9. The method of claim 8 , wherein said first record-route header and said first via header are suitable for transferring SIP dialog state data to an endpoint.

10. The method of claim 9 , wherein said first record-route header and said first via header are suitable for reconstructing said SIP dialog state data on a receiving second record-route header or a second via header in a subsequent SIP message received from said endpoint.

11. A system comprising:

a back-to-back user agent, said back-to-back user agent further comprising:

a user agent server and

a user agent client, said user agent client concatenated with said user agent server to form said back-to-back user agent;

wherein said back-to-back user agent is suitable for replacing SIP dialog state information in each SIP message and for inserting a record-route header and a via header in both selected SIP requests to said user agent server and selected SIP responses to said user agent client, said record-route header and said via header suitable for transferring SIP dialog state data to an endpoint and reconstructing said SIP dialog state data on a receiving record-route header and a receiving via header in a subsequent SIP message received from said endpoint.

12. The system of claim 11 , wherein said user agent server receives a request having an original source and destination header.

13. The system of claim 12 , wherein said back-to-back user agent is suitable for performing a transformation on said request, and wherein transforming SIP messages replaces SIP dialog state information in each transformed message.

14. The system of claim 13 , wherein said transformation replaces a From header and a To header.

15. The system of claim 12 , wherein said transformation is performed utilizing static rules configured for said request.

16. The system of claim 11 , wherein said receiving via header is identical to said receiving record-route header and is suitable for reconstructing said request if a negative response from said endpoint is received.