This series of interactive documents uses a typical head office and branch
office in order to demonstrate some common voice network configurations. This
interactive diagram allows you to view network configurations:
This image is interactive!
Click a component to view configuration
and troubleshooting information.
The Line/Device approach uses unrestricted Calling Search Space at the Device
level and applies blocking at the line level by using translation patterns,
as depicted in this diagram:
Because this configuration uses two sites (San Jose and
RTP) and four classes of services (internal, local, national, and international),
you must create a total of six Calling Search Spaces: one for each site and
In addition, you must create these partitions:
Internal_DN (assigned to phone DNs)
Block_Local (assigned to translation pattern that
blocks all PSTN, except 911 calls)
Block_National (assigned to translation pattern that
blocks all national calls, but permits 911 and local PSTN calls)
Block_International (assigned to translation pattern
that blocks international calls, but permits 911, local, and national PSTN
No_Block (no restrictions)
This image shows the parititions that you must create:
This image shows the route patterns that are created for the San Jose and RTP
Note: The number nine (9) is used to indicate PSTN access that gets stripped
by the route group configuration.
For international calls, two route patterns exist for each site:
one pattern that ends with an exclamation point (!), which means wait for
T302 timer (15 seconds) to expire
one pattern that ends with a pound sign (#), which means dial immediately
after the user presses #
For each site, a route group that contains the MGCP gateway is created, as
well as a route list that contains the local route group. The route lists are
then used for the route patterns.
This image shows an example of the route group and route list that are created
for the San Jose site:
Note: In order to implement digit manipulation at the route group level,
this configuration discards PreDot, which is the digit 9 for PSTN access, as
shown in this image:
You can implement digit manipulation at the route pattern configuration; however,
you have more control over dialing destinations when digit manipulation is used
at the route group level. That is, you can use one route pattern that points
to a route list and contains two route groups: one route group implements digit
manipulation and the other route group uses different digit manipulation.
In order to create different classes of service, this configuration uses translation
patterns that block unwanted dialing patterns. These translation patterns are
included in the appropriate Calling Search Spaces that are applied at the line
level, directory number (DN).
This configuration uses a total of 4 translation patterns that are placed in
the appropriate partition:
Next, the different Calling Search Spaces are created for each site at the
This image shows the San Jose Calling Search Space that is applied at the device
Note: The Internal_DN partition is included at the device level instead
of at the line level on each Calling Search Space.
This image shows the RTP Calling Search Space that is applied at the device
Note: This configurations includes the Internal_DN partition at the
device level instead of at the line level on each Calling Search Space.
Finally, the four Calling Search Spaces that contain the blocked translation
patterns are created and then are applied at the line level as shown in this
Note: Although this configuration includes Internal_DN (all phone DNs),
it is redundant if the device already includes it in the device Calling Search
Space. This is relevant only if you apply this to a DN that does not have a
device CSS (for example, Voice Mail Pilot Calling Search Space).