Understanding Trunk Reusability for SRX Series Integrated Convergence Services

This topic covers reuse of trunks across multiple trunk groups. Trunk groups, which are associated with the route patterns of a dial plan, contain trunk configurations, or trunks. These trunks are used to route calls that match the route pattern’s digit pattern.

Trunks are discrete, reusable entities, and they can be included in multiple trunk groups concurrently. However, when a shared trunk is busy routing a call for one route pattern, it cannot be used to route a call for another one.

Consider the following example. In this example, the following conditions exist:

• Trunk Group A is assigned to Route Pattern 1.
• Trunk Group B is assigned to Route Pattern 2.
• Both trunk groups include some of the same trunks: trunk1, trunk2, and trunk6.

							Route Pattern 1
						

trunk-group-a

trunk1

trunk2

trunk7

trunk5

trunk6

							Route Pattern 2
						

trunk1

trunk2

trunk4

trunk8

trunk6

If a shared trunk is busy with a call for Route Pattern 1, it is not available to route a call for Route Pattern 2, that is, until the call ends. For example, if trunk1 in trunk-group-a (of Route Pattern 1) is busy with a call, it cannot be used for to route a call for Route Pattern 2. If trunk2 in trunk-group-b is busy with a call, it cannot be used by Route Pattern 1 until the call ends.

Related Topics

• Understanding SRX Series Integrated Convergence Services Media Gateway Trunks
• Understanding Trunk Precedence and Trunk Group Preference for SRX Series Integrated Convergence Services
• Understanding Trunk Group Reusability for SRX Series Integrated Convergence Services