trunk-group (route-pattern, route-policy)

Syntax

trunk-group trunk-group-name; {preference preference-number;digit-transform digit-transform-name;}

Hierarchy Level

[edit services convergence-services dial-plan dial-plan-name route-pattern digit-pattern]

[edit services convergence-services dial-plan dial-plan-name route-policy route-policy-name term term-name from]

[edit services convergence-services dial-plan dial-plan-name route-policy route-policy-name term term-name then route next-hop]

Description

Trunk Groups for Route Patterns

For a route pattern, specify the name of the trunk group to be added to it. If the route pattern contains more than one trunk group, you can assign each trunk group a preference number. If no preference number is assigned, trunk groups are tried in the order in which you assigned them to the route pattern.

If the route pattern contains more than one trunk group, you can assign each trunk group a preference number. If no preference number is assigned, trunk groups are tried in the order in which you assigned them to the route policy. Optionally, specify a digit transform to be used to transform the called number before it is routed to the telephony service provider.

Trunk groups are reusable across route patterns of a dial plan.

Trunk Groups for Route Policies

For a route policy’sfrom action, specify the trunk group from which a call is routed.

For the route policy’s next-hop partner statement, specify another trunk group (or a peer call server) to which the call is routed. ,

Trunk groups are reusable across route policies of a dial plan.

Using Trunk Groups Within Dial Plans

A route pattern or route policy can have multiple trunk groups associated with it. Each trunk group included in a route pattern or route policy can specify a preference number (low-order number takes precedence) that indicates which trunk group is used first.

If you use preference numbers, trunks within the trunk group with the highest preference (lowest number) are tried first.
If no preference number is assigned to the trunk groups, they are used in the order in which you add them to the route pattern.

Integrated Convergence Services tries to route the call using the first trunk in the preferred trunk group. If that trunk is used for a call, the next trunk in that trunk group is tried, and so on until an available trunk is identified.

If no trunk is available in the first trunk group of the route pattern or the route policy, then the trunk group with the next highest preference is tried. Its first trunk is tried. If the first trunk is busy with a call, then the next trunk of that trunk group is tried until an available trunk is identified and the call is routed.

If all trunks of the trunk groups are unavailable to route the call, the following message is played:

“We are sorry. All circuits are busy now. Please try again later.”

Options

trunk-group-name—Name of the trunk group.

preference-number—Order in which the trunk group should be used. Lowest number indicates highest preference.

digit-transform-name—Name of a digit transform to be used for trunks in this trunk group.

Usage Guidelines

For configuration instructions and examples, see the Junos OS Integrated Convergence Services Configuration and Administration Guide.

Required Privilege Level

services—To view this statement in the configuration.

services–control—To add this statement to the configuration.