User's Manual

Bulk import for Domains

Please follow these rules when creating an XML bulk import file:

• The domain name must be unique, and is referred to by other elements.

• It is not possible to create a domain with <domainType> of type “sip” that have

<defaultDomain> containing the value “true”.

• The values in <domainType> 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"?>

<defaultDomain>false</defaultDomain>

<domainName>avaya.com</domainName>

<name>avaya.com</name>

</SipdomainFullTO>

<notes>this is another test</notes>

<defaultDomain>false</defaultDomain>

<domainName>avaya2.com</domainName>

<name>avaya2.com</name>

</SipdomainFullTO>

</sipdomainFullTOList>

Locations

About Locations

You can use the Locations screen to set up and configure gateway and user locations. The IP

address of the device determines the current physical location of the caller or the called user.

Session Manager matches the IP address against the patterns defined on location screens. If

a call is from a SIP Entity does not match the IP address pattern then Session Manager uses

the location administered for the SIP Entity.

Session Manager uses the originating location to determine which dial patterns to look at when

routing the call if there are dial patterns administered for specific locations. Locations are also

used to limit the number of calls coming out of or going to a physical location. This is useful for

those locations where the network bandwidth is limited. This is also known as Call Admission

Control (CAC). CAC provides a level of protection by limiting the impact of multimedia traffic

over the most critical network links between enterprise locations, such as the links from branch

Managing Session Manager routing

246 Administering Avaya Aura

Session Manager November 2010

Comments? infodev@avaya.com