14.1 Routing configuration
A routing is always assigned to a specific trunk group, so that it is effectively a property of this trunk group. Rules are created based on the dialed destination numbers, and placeholders can be used. The routing can be formulated positively (Use this Trunk Group for Calls to the following) or negatively (Do not use this Trunk Group for Calls to the following). The routing records can be prioritized. A sequence order can thus be defined within the routings, e.g. "Try first on trunk group A, then on trunk group B". The caller number of the calling SwyxWare user, the group membership or the user's location can be taken into account in the decision on which trunk group is selected.
For SwyxLink trunks with configured intersite settings a routing record is created automatically. This entry is not editable.
If the trunk group consists of several trunks, the trunk with this number is selected. (e.g. Public numbers of this trunk). If no trunk matching the caller number is found within the selected trunk group, the trunk signaling the most information about the caller is selected. The number signaled externally arises according to the valid setting on this trunk in the field "Outgoing calls if Calling Party Number / URI is not assigned".
Example:
You have two ISDN connections e.g. each with five MSNs. For each of these connections you set up a trunk group:
- User A has an internal number, for which there is a call number mapping to trunk group 1,
- User B has an internal number, for which there is a call number mapping to trunk group 2.
- There are routing records for both trunk groups with the same priority and the same destination number range.
If one of these users calls an external number, then a trunk group is selected using the dialed number and the priority. If these criteria do not lead to a preferred trunk group, the trunk group is randomly selected, i.e. also trunk group 1 can be selected for user 2. If e.g. Hide Number is configured on the trunk groups for unassigned caller numbers, then - without the user intending this - his number is displayed on one call and not on another. To prevent this, when the trunks are similar you can manage both in one trunk group, regardless of the fact that two different ISDN connections are represented.
Routing Records and selection prefix for trunk groups
If a user defines which trunk group should be used for the next call by using the assigned selection prefix, no further routing records are applied.
This is how you define a route
Last modified date: 01/24/2024