
Bulk import for Entity Links
Please follow these rules when creating an XML bulk import file:
• The name of an Entity Link must be unique.
• <entityName1> , <entityName2> must refer to an existing SIP Entity 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 Entity Link.
• The values in <transportProtocol> must appear exactly same (being case sensitive) as
they appear in the System Manager user interface.
Example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<entitylinkFullTOList>
<EntitylinkFullTO>
<notes></notes>
<listenPortEntity1>5061</listenPortEntity1>
<listenPortEntity2>5061</listenPortEntity2>
<name>SessionManager1_BerlinCM_5061_TLS</name>
<transportProtocol>TLS</transportProtocol>
<trusted>true</trusted>
<entityName1>SessionManager1</entityName1>
<entityName2>BerlinCM</entityName2>
</EntitylinkFullTO>
<EntitylinkFullTO>
<notes></notes>
<listenPortEntity1>5061</listenPortEntity1>
<listenPortEntity2>5061</listenPortEntity2>
<name>NewYorkCM-SessionManager1-TLS</name>
<transportProtocol>TLS</transportProtocol>
<trusted>true</trusted>
<entityName1>SessionManager1</entityName1>
<entityName2>NewYorkCM</entityName2>
</EntitylinkFullTO>
</entitylinkFullTOList>
Time Ranges
About the Time Ranges
Time ranges indicate when a particular rank or cost of a routing policy is to be used when
determining the least-cost route. They do not indicate when routing policies are available to
be considered for routing.
You must specify as many time ranges as necessary to cover all hours and days in a week for
each administered routing policy.
Managing Session Manager routing
294 Administering Avaya Aura
®
Session Manager November 2010
Comentarios a estos manuales