Methods and apparatus for multistage routing of packets using call templates

• US 8,755,371 B2
• Filed: 03/26/2010
• Issued: 06/17/2014
• Est. Priority Date: 12/31/2004
• Status: Active Grant

• Current Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Original Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Inventors: Ramachandran, Sridhar, Tyagi, Paritosh, Mallesan, Saravanan, Kulshreshtha, Gaurav, Shetty, Sohan, Raman, Rohini, Bhatia, Medhavi
• Primary Examiner(s): Nawaz, Asad
• Assistant Examiner(s): Ansari, Najeebuddin
• Application Number:
  US12/748,321
• Publication Number:
  US 20100309906A1
• Time in Patent Office: 1,544 Days
• Field of Search: 370/352, 370/229, 370/230, 370/231, 370/235
• US Class Current: 370/352
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/3065 for real time traffic
• CPC Class Codes: H04L 47/00 Traffic control in data switching networks arrangements for detecting or preventing errors in the information received H04L1/00
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/1072 Discovery involving ranked list compilation of candidate peers
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 7/126 Interworking of session control protocols

Abstract

A method for multistage routing of packets using call templates is disclosed. An ingress call is filtered based on a plurality of ingress-call parameter values. A parameter value for the ingress call is modified based on a plurality of ingress-call-peer parameter values. A filtered ingress-call parameter value and at least one filtered ingress-call-peer parameter value from a plurality of ingress-call-peer parameter values are converted to an egress-call parameter value and an egress-call-peer parameter value, respectively. An egress call is filtered based on a plurality of egress-call parameter values. A parameter value for the egress call is modified based on a plurality of egress-call-peer parameter values.

Claims

1. A method, comprising:

filtering an ingress call based on a plurality of ingress-call parameter values, wherein filtering includes identifying a source of the ingress call and applying a common source policy to the ingress call based on the source, the common source policy including match parameters for matching ingress call parameters and set parameters for modifying ingress call parameters, wherein applying a common source policy includes modifying an ingress-call parameter of the ingress call based on one of the set parameters;

converting a filtered ingress-call parameter value to an egress-call parameter value;

filtering an egress call based on a plurality of egress-call parameter values, the plurality of egress-call parameter values including the egress-call parameter value;

modifying a parameter value for the egress call based on a plurality of egress-call-peer parameter values;

tagging the ingress call based on the ingress-call parameter values and the egress-call-peer parameter values, the modifying for the egress call being based on the tagged ingress call; and

associating the ingress call with an ingress call peer based on the ingress-call parameter values and ingress-call-peer parameter values.

2. The method of claim 1 wherein applying the common source policy to the ingress call based on the source includes:

filtering the identified ingress call based on the common source policy.

3. The method of claim 1, further comprising selecting a first destination from an identified group of destinations for the ingress call based on a criterion, the criterion being at least one selected from a filter priority, a call-peer priority, a filter match strength, or an administration filter policy.

4. The method of claim 1, further comprising selecting a first destination from an identified group of destinations for the ingress call based on time-of-day filtering or load-balancing.

5. The method of claim 1, further comprising selecting a first destination from an identified group of destinations for the ingress call based on at least one of a least recently used destination or a percent utilization of a destination.

6. The method of claim 1, further comprising selecting a first destination from an identified group of destinations for the ingress call based on at least one of an ISDN/SIP response code for run-time or a redirect.

7. The method of claim 1, further comprising mapping an error code for a dropped call when the error code is returned back to a caller, the mapping including at least one of ceasing attempts to terminate the ingress call or redirecting the ingress call.

8. The method of claim 1, further comprising associating the ingress call with an ingress call peer based on an automatic number identification (ANI) associated with the ingress call.

9. The method of claim 1, further comprising associating the ingress call with an ingress call peer based on the plurality of ingress-call parameter values, the plurality of ingress-call-peer parameter values and an automatic number identification (ANI) associated with a call origination and common to all terminations.

10. The method of claim 1, further comprising:

associating the ingress call with an ingress call peer based on the plurality of ingress-call parameter values and the plurality of ingress-call-peer parameter values, and an automatic number identification (ANI) associated with the ingress call;

instantiating the egress call based on the tagged ingress call; and

filtering the egress call based on the tagged ingress call.

11. The method of claim 1, further comprising associating the ingress call with an egress call peer based on the plurality of egress-call parameter values, the plurality of ingress-call-peer parameter values and an automatic number identification (ANI) associated with a call termination and common to all originations.

12. The method of claim 1, further comprising:

tagging the ingress call based on a required class of service, the modifying the parameter value for the ingress call being based on the tagged ingress call.

13. The method of claim 1, further comprising:

tagging the ingress call based on automatic number identification (ANI associated with the ingress call; and

selecting a termination based on the tagged ingress call.

14. The method of claim 1, further comprising:

tagging the ingress call based on a dialed number identification; and

terminating the ingress call based on a tag applied during the tagging.

15. The method of claim 1, further comprising:

selecting a first destination for the ingress call among an identified group of destinations based on a criterion; and

abandoning a call attempt to the first destination when a maximum number of call attempts for a call source has been reached.

16. The method of claim 1, further comprising:

selecting a first destination for the ingress call among an identified group of destinations based on a criterion; and

abandoning a call attempt to the first destination when a maximum post-dial delay for a call source has been reached.

17. The method of claim 1, further comprising instantiating a call peer and a device based on the plurality of ingress-call parameter values, the plurality of egress-call-peer parameter values, and the plurality of egress-call parameter values when the call peer does not exist and when the device does not exist.

18. The method of claim 1, further comprising:

identifying a source of the ingress call based on at least one of a layer 2 qualifier or a layer 3 qualifier; and

applying a routing policy to the ingress call based on the source.

19. The method of claim 1, further comprising:

identifying a source of the ingress call based on a virtual LAN identifier associated with the ingress call; and

applying a routing policy to the ingress call based on the source.

20. The method of claim 1, further comprising:

identifying a source of the ingress call based on at least one of a layer 2 qualifier or a layer 3 qualifier; and

applying a marker to the ingress call based on the source, the marker adapted to be used by an egress network for quality of service.

21. The method of claim 1, further comprising:

identifying the source of the ingress call based on a DiffServ/TOS marking associated with the ingress call; and

applying a routing policy to the ingress call based on the source.

22. The method of claim 1, further comprising:

identifying a source of the ingress call based on a priority-bit identifier associated with the ingress call; and

applying a routing policy to the ingress call based on the source.

23. A computer program stored on a non-transitory computer-readable medium, the computer program comprising:

an identifying instruction configured to identify a source associated with an ingress call;

an applying instruction configured to apply a common source policy to the ingress call based on the source, the common source policy including match parameters for matching ingress call parameters and set parameters for modifying ingress call parameters, wherein applying a common source policy includes modifying an ingress-call parameter of the ingress call based on one of the set parameters;

a tagging instruction configured to tag a parameter value associated with the ingress call based on the common source policy to produce a tagged parameter value, wherein the tagging instruction is configured to tag the ingress call based on the tagged parameter value and egress-call-peer parameter values;

a matching instruction configured to match an egress call with a corresponding ingress call based on the tagged parameter value;

a modifying instruction configured to modify the egress call based on the tagged ingress call; and

an associating instruction configured to associate the ingress call with an ingress call peer based on the ingress-call parameter values and ingress-call-peer parameter values.