Filter
Top Products
Managing URI Route Maps 127
The Route - EndPoints - OutDial Patterns page refreshes, verifying the out
dial pattern was unassigned.
Managing URI
Route Maps
This section provides information on how to add and delete URI route
maps. A URI route map maps destination URIs to route IDs using various
routing policies and source based input parameters.
Source based input parameters are used for two functional
components of the directory server, which are destination URI
translation and destination URI to route mapping. Destination URI
translation translates the URI, which can be a string URI or a E.164
phone number, into another URI. This translation can be a complete
replacement of the URI or a partial replacement. The destination URI
to route mapping associates the destination URI (URI/DNIS phone
number) to a specific route.
The source based input parameters allow the server to vary the
translation or route mapping based on the source. For example,
translation of the same URI would be different based on which
gatekeeper the request came from:
The same logic applies for destination URI to route mapping. For
example, if the request comes from gatekeeper 1 then the route
would be different than if the request comes from gatekeeper 2.
Adding URI Route
Maps
To add URI route maps:
1 From the directory provisioning page, see Figure 24, click URI Route Map.
The List Routes Mapped To URI Patterns page appears. See Figure 48.
Table 25 URI Translation
Direct Requestor Destination URI/DNIS Translation
Gatekeeper 1 312-555-1212 708-555-1212
Gatekeeper 2 312-555-1212 630-555-1212