
Bulk import for Routing Policies
Please follow these rules when creating an XML bulk import file:
• The name of a routing policy <referred to as routing policy> is unique and is referred to
by other elements.
• <sipentityName> must refer to an existing SIP element with the exact same name. It must
either appear in the System Manager database or in an import file that exists in the same
import operation as the Routing Policy.
• Multiple time of day entries (<timeofdayNames>) can be configured for one Routing
Policy.
- <timerangeName> must refer to an existing Time Range with the exact same name. It
must either appear in the System Manager database or in an import file that exists in
the same import operation as the Routing Policy.
Example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<routingpolicyFullTOList>
<RoutingpolicyFullTO>
<notes>this is a test</notes>
<disabled>false</disabled>
<name>toBerlin</name>
<sipentityName>BerlinCM</sipentityName>
<timeofdayNames>
<rank>1</rank>
<timerangeName>regularweek</timerangeName>
</timeofdayNames>
<timeofdayNames>
<rank>0</rank>
<timerangeName>24/7</timerangeName>
</timeofdayNames>
</RoutingpolicyFullTO>
</routingpolicyFullTOList>
Dial Patterns
About Dial Patterns
A dial pattern specifies which routing policy or routing policies are used to route a call based
on the digits dialed by a user which match that pattern. Session Manager matches these dialed
digits after applying any administered ingress adaptation.
The originating location of the call, the domain in the request-URI and the Global Settings
option of Prefer Longer Matching Dial Patterns in Location ALL to Shorter Matches in
Originator's Location in the Session Manager Administration page also determine how the
Dial Patterns
Administering Avaya Aura
®
Session Manager November 2010 307
Comentarios a estos manuales