Abstract: An embodiment of a method includes determining a customer service plan identifier from information associated with a received call, determining a route plan associated with the identified customer service plan, and routing the call on a trunk group identified in the determined route plan. The method may further include determining a jurisdiction of the call based on a dialed number identified in the call, determining a local routing number (LRN) associated with the call, and using a portion of the LRN to determine the trunk group. An embodiment of a system includes a switch operable to select a route for routing a call received on an ingress trunk associated with a customer that subscribes to a service plan, wherein the switch is further operable to select the route based on the service plan subscribed to by the customer associated with the ingress trunk.

Abstract: An embodiment of a method includes generating one or more route plans, each route plan being associated with a service plan, and provisioning the one or more route plans on a core routing engine accessible by a softswitch for routing calls according to the one or more route plans. The one or more route plans may include an on-net route plan and an off-net route plan. An embodiment of a system includes a local route manager (LRM) configured to generate one or more route plans associated with one or more respective service levels that customers can subscribe to. The system may further include an inventory of trunk groups containing a plurality of trunk group identifiers (IDs), wherein trunk group IDs are marked as either on-net or off-net.

Abstract: An embodiment of a method includes determining a customer service plan identifier from information associated with a received call, determining a route plan associated with the identified customer service plan, and routing the call on a trunk group identified in the determined route plan. The method may further include determining a jurisdiction of the call based on a dialed number identified in the call, determining a local routing number (LRN) associated with the call, and using a portion of the LRN to determine the trunk group. An embodiment of a system includes a switch operable to select a route for routing a call received on an ingress trunk associated with a customer that subscribes to a service plan, wherein the switch is further operable to select the route based on the service plan subscribed to by the customer associated with the ingress trunk.

Abstract: An embodiment of a method includes determining a customer service plan identifier from information associated with a received call, determining a route plan associated with the identified customer service plan, and routing the call on a trunk group identified in the determined route plan. The method may further include determining a jurisdiction of the call based on a dialed number identified in the call, determining a local routing number (LRN) associated with the call, and using a portion of the LRN to determine the trunk group. An embodiment of a system includes a switch operable to select a route for routing a call received on an ingress trunk associated with a customer that subscribes to a service plan, wherein the switch is further operable to select the route based on the service plan subscribed to by the customer associated with the ingress trunk.

Abstract: An embodiment of a method includes generating one or more route plans, each route plan being associated with a service plan, and provisioning the one or more route plans on a core routing engine accessible by a softswitch for routing calls according to the one or more route plans. The one or more route plans may include an on-net route plan and an off-net route plan. An embodiment of a system includes a local route manager (LRM) configured to generate one or more route plans associated with one or more respective service levels that customers can subscribe to. The system may further include an inventory of trunk groups containing a plurality of trunk group identifiers (IDs), wherein trunk group IDs are marked as either on-net or off-net.

Abstract: An embodiment of a method includes generating one or more route plans, each route plan being associated with a service plan, and provisioning the one or more route plans on a core routing engine accessible by a softswitch for routing calls according to the one or more route plans. The one or more route plans may include an on-net route plan and an off-net route plan. An embodiment of a system includes a local route manager (LRM) configured to generate one or more route plans associated with one or more respective service levels that customers can subscribe to. The system may further include an inventory of trunk groups containing a plurality of trunk group identifiers (IDs), wherein trunk group IDs are marked as either on-net or off-net.

Abstract: An embodiment of a method includes determining a customer service plan identifier from information associated with a received call, determining a route plan associated with the identified customer service plan, and routing the call on a trunk group identified in the determined route plan. The method may further include determining a jurisdiction of the call based on a dialed number identified in the call, determining a local routing number (LRN) associated with the call, and using a portion of the LRN to determine the trunk group. An embodiment of a system includes a switch operable to select a route for routing a call received on an ingress trunk associated with a customer that subscribes to a service plan, wherein the switch is further operable to select the route based on the service plan subscribed to by the customer associated with the ingress trunk.

Abstract: An embodiment of a method includes generating one or more route plans, each route plan being associated with a service plan, and provisioning the one or more route plans on a core routing engine accessible by a softswitch for routing calls according to the one or more route plans. The one or more route plans may include an on-net route plan and an off-net route plan. An embodiment of a system includes a local route manager (LRM) configured to generate one or more route plans associated with one or more respective service levels that customers can subscribe to. The system may further include an inventory of trunk groups containing a plurality of trunk group identifiers (IDs), wherein trunk group IDs are marked as either on-net or off-net.