
Bulk Import for Dial Patterns
Please follow these rules when creating an XML bulk import file:
• A dial pattern is identified by a combination of 5 elements below. This combination must
be unique for each dial pattern.
- <digitpattern>
- <maxdigits>
- <mindigits>
- <sipdomainName>
- <routingoriginationName>
• <sipdomainName> must refer to an existing domain 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 dial pattern.
• <routingpolicyNames> must refer to existing Routing Policies 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 Dial pattern.
• <routingpolicyNames> must exist if <deny> is false.
• <routingpolicyNames> must exist if <deny> is true.
Example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<digitmapFullTOList>
<DigitmapFullTO>
<notes>this is a test</notes>
<deny>true</deny>
<digitpattern>123</digitpattern>
<maxdigits>36</maxdigits>
<mindigits>3</mindigits>
<routingoriginationName>New York</routingoriginationName>
<routingpolicyNames>toBerlin</routingpolicyNames>
<sipdomainName>avaya.com</sipdomainName>
<treatasemergency>true</treatasemergency>
</DigitmapFullTO>
<DigitmapFullTO>
<notes>this is a test</notes>
<deny>false</deny>
<digitpattern>123</digitpattern>
<maxdigits>36</maxdigits>
<mindigits>3</mindigits>
<routingoriginationName>Berlin</routingoriginationName>
<routingpolicyNames>toBerlin</routingpolicyNames>
<sipdomainName>avaya.com</sipdomainName>
<treatasemergency>true</treatasemergency>
</DigitmapFullTO>
</digitmapFullTOList>
Managing Session Manager routing
316 Administering Avaya Aura
®
Session Manager November 2010
Comentarios a estos manuales