Service path routing between session border controllers

• US 8,761,160 B2
• Filed: 02/16/2011
• Issued: 06/24/2014
• Est. Priority Date: 06/25/2010
• Status: Active Grant

• Current Assignee: Acme Packet Incorporated (Oracle Corporation)
• Original Assignee: Acme Packet Incorporated (Oracle Corporation)
• Inventors: MeLampy, Patrick J., Penfield, Robert F., Gray, David, Benitez Pelaez, Mariana, Koss, Ryan, Commerford, Peter, Timmons, Patrick
• Primary Examiner(s): Nawaz, Asad
• Assistant Examiner(s): Yang, Zhaohui
• Application Number:
  US13/028,355
• Publication Number:
  US 20110317689A1
• Time in Patent Office: 1,224 Days
• Field of Search: 370352-356
• US Class Current: 370/356
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1036 at the edge
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• 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/1056 Multi-site
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

Systems and methods of establishing IP telephony sessions between enterprises are disclosed. A first enterprise requests an association with a second enterprise. Both enterprises and the second enterprise belong to the same federation. The association request is accepted, to establish an association between the first and second enterprises. In response to the acceptance, a direct routed path is established between the first enterprise and the second enterprise. One of the associated enterprises requests activation of an IP telephony service. If the request to activate references the association, an IP telephony session is established using the direct routed path.

Claims

1. A method, performed in a session border controller, of establishing Internet Protocol (IP) telephony sessions between enterprises, the method comprising:

learning a route path for reaching a first enterprise from a second enterprise, the first enterprise and the second enterprise both belonging to a federation and obtaining IP telephony services from the same service provider, wherein the service provider comprises a Public Switched Telephone Network (PSTN) gateway that provides telephone calls from the first enterprise to a PSTN;

identifying an IP telephony session as a federated communication, wherein the IP telephony session is between a first communication device of the first enterprise and a second communication device of the second enterprise; and

tagging the identified IP telephony session so that the identified IP telephony session traverses the learned route path, wherein the tagging indicates a federated communication and wherein the learned route path bypasses the PSTN gateway;

wherein learning the route path comprises receiving at the session border controller located at the service provider a watcher event comprising a list of associated enterprises and session initiation protocol (SIP) headers comprising a route traversed by the watcher event, and parsing the SIP headers to determine the route path from the second enterprise to the first enterprise;

wherein the first enterprise is coupled to the service provider via a first pair of session border controllers and a first SIP trunk, and the second enterprise is coupled to the service provider via a second pair of session border controllers and a second SIP trunk.

2. The method of claim 1, further comprising:

conveying signaling packets of the IP telephony session over the learned route path.

3. The method of claim 1, further comprising:

conveying media packets of the IP telephony session over the learned route path.

4. The method of claim 1, wherein the learned route path does not include TDM equipment.

5. The method of claim 1, wherein the learned route path does not include components that normalize traffic associated with telephony services provided by the IP telephony service provider.

6. The method of claim 1, wherein the learned route path is confined to a particular set of Session Border Controllers operated by the same IP telephony service provider.

7. The method of claim 1, wherein the learned route path is confined to traversal of a pair of enterprise Session Border Controllers and a pair of service provider Session Border Controllers, each of the pairs operated by the same IP telephony service provider.

8. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to establish Internet Protocol (IP) telephony sessions between enterprises, the establishing comprising:

learning a route path for reaching a first enterprise from a second enterprise, the first enterprise and the second enterprise both belonging to a federation and obtaining IP telephony services from the same service provider, wherein the service provider comprises a Public Switched Telephone Network (PSTN) gateway that provides telephone calls from the first enterprise to a PSTN;

identifying an IP telephony session as a federated communication, wherein the IP telephony session is between a first communication device of the first enterprise and a second communication device of the second enterprise; and

tagging the identified IP telephony session so that the identified IP telephony session traverses the learned route path, wherein the tagging indicates a federated communication and wherein the learned route path bypasses the PSTN gateway;

wherein learning the route path comprises receiving at a session border controller located at the service provider a watcher event comprising a list of associated enterprises and session initiation protocol (SIP) headers comprising a route traversed by the watcher event, and parsing the SIP headers to determine the route path from the second enterprise to the first enterprise;

wherein the first enterprise is coupled to the service provider via a first pair of session border controllers and a first SIP trunk, and the second enterprise is coupled to the service provider via a second pair of session border controllers and a second SIP trunk.

9. The computer-readable medium of claim 8, the establishing further comprising:

conveying signaling packets of the IP telephony session over the learned route path.

10. The computer-readable medium of claim 8, the establishing further comprising:

conveying media packets of the IP telephony session over the learned route path.

11. A system for establishing Internet Protocol (IP) telephony sessions between enterprises, the system comprising:

a processor coupled to a storage device, the processor executing functionality comprising;

learning a route path for reaching a first enterprise from a second enterprise, the first enterprise and the second enterprise both belonging to a federation and obtaining IP telephony services from the same service provider, wherein the service provider comprises a Public Switched Telephone Network (PSTN) gateway that provides telephone calls from the first enterprise to a PSTN;

identifying an IP telephony session as a federated communication, wherein the IP telephony session is between a first communication device of the first enterprise and a second communication device of the second enterprise; and

tagging the identified IP telephony session so that the identified IP telephony session traverses the learned route path, wherein the tagging indicates a federated communication and wherein the learned route path bypasses the PSTN gateway;

wherein learning the route path comprises receiving at a session border controller located at the service provider a watcher event comprising a list of associated enterprises and session initiation protocol (SIP) headers comprising a route traversed by the watcher event, and parsing the SIP headers to determine the route path from the second enterprise to the first enterprise;

wherein the first enterprise is coupled to the service provider via a first pair of session border controllers and a first SIP trunk, and the second enterprise is coupled to the service provider via a second pair of session border controllers and a second SIP trunk.

12. The system of claim 11, further comprising:

conveying signaling packets of the IP telephony session over the learned route path.

13. The system of claim 11, the establishing further comprising:

conveying media packets of the IP telephony session over the learned route path.