Simple local routing comprises cases in which each site
needs to route offnet calls to its local gateways. Provisioning of route
patterns and route lists can get reduced from the need to configure N route
patterns and N route lists to a configuration where only one route pattern and
one route list are needed.
For this case further assume that all phones that home to a
particular site belong to a single calling search space (CSS) that is unique to
that site. For example, phones at the Boulder site belong to the CSS-Bldr
calling search space and so forth. The following figure illustrates a possible
provisioning of this system without using the Local Route Group feature, so
regardless of site, a phone always prefers its local gateway when making an
offnet call by dialing 9 followed by a seven-, ten-, or eleven-digit pattern.
As more sites get added, each of the columns must include new entries (rows).
If N sites exist, you need N different route lists, route patterns, partitions,
and calling search spaces.
Figure 2. Provisioning Local Offnet Access Without Local Route
In the same implementation, use of the Local Route Group
feature allows configuration of a single route list, partition, route pattern,
and CSS, regardless of the number of sites, as shown in the following figure.
Figure 3. Provisioning Local Offnet Access With Local Route Groups
In this case, the following configuration applies:
All phones belong to a single CSS-System calling search space and
to a single P-System partition.
All phones for a given site belong to a single device pool unique
to that site.
The Local Route Group field in each device pool identifies the
specific route group for that site. In this example, RG-Bldr for Boulder,
RG-Rch for Richardson, and so on.
Thus, the route lists, route patterns, partitions and
calling search spaces for this case each get reduced from N to 1. The number of
gateways, route groups, and device pools remain N for N sites.
A new partition, P_System, and a new calling search space,
CSS_System, get added for accessing the 9.@ pattern from all sites. The calling
search space, CSS_Boulder, can contain both P_Boulder and P_System as well, as
can the CSS of the other sites.