User's Manual

call gets routed. The dial pattern look up method as per the Global Setting option is explained
below:
1. When the Global Settings option is not selected:
Session Manager compares the user-part of the Request-URI with all dial patterns
valid for the originating location where the domain matches the domain in the
Request-URI. A Dial Pattern is valid for a particular location if :
• the location in the dial pattern matches the originating location, or
• the dial pattern is for “ALL” locations
Dial patterns that match the originating location are considered before dial patterns
for “ALL” locations. If a dial pattern for the originating location matches the digits,
dial patterns for “ALL” locations are ignored.
If no matching dial patterns are found, then the domain in the Request-URI is
modified to remove one level of subdomain until only a top-level domain is left. For
example, if “dr.avaya.com” was tried, then “avaya.com” is tried. If “avaya.com” was
tried, then Session Manager tries “.com” which fails.
If more than one Dial Pattern matches, the one with the longest matching pattern
is selected.
2. When the Global Settings option is selected:
Session Manager compares the user-part of the Request-URI with all dial patterns
valid for the originating location where the domain matches the domain in the
Request-URI. Only dial patterns matching the location are considered. If no
matching dial patterns are found, then the domain in the Request-URI is modified
to remove one level of subdomain until only a top-level domain is left. For example,
if “dr.avaya.com” was tried, then “avaya.com” is tried. If “avaya.com” was tried, then
Session Manager tries “.com” which fails. If more than one dial pattern matches,
the one with the longest matching pattern is selected.
Similarly, dial patterns administered for “ALL” locations are also compared.
This may result in two matching dial patterns, one for “ALL” locations and one for
the specific location. The longest matching pattern is then chosen, thus a longer
pattern administered for “ALL” locations overrides a location-specific pattern. If both
matching patterns are of the same length, then both patterns are examined for
wildcard characters. If one contains a wildcard and the other does not, then the
pattern without a wildcard is selected. If both patterns contain a wildcard, then the
location-specific pattern is selected.
Examples — Global Settings option is selected:
Location Specific Pattern “ALL” Locations Pattern Chosen Pattern
1303538 1303538 Location-Specific
130353 1303538 ALL Locations
Managing Session Manager routing
308 Administering Avaya Aura
®
Session Manager November 2010
Comments? [e-mail]