
Routing of a call using routing policy data
1. Session Manager tries to match the domain to one of the authoritative domains.
2. If Session Manager is authoritative for the domain, then the Session Manager tries
to match the digit pattern.
3. If a digit pattern match is not found, it tries to use the regular expression table.
4. If no regular expression match is found, it sends the request to a Session Manager-
provisioned outbound proxy.
5. If no outbound proxy has been administered for the Session Manager and it is not
authoritative for the domain then it routes the request to the destination in the
request-URI. If the request-URI does not contain an P address, then it uses DNS
or the Local Host Name Resolution table to determine where to route the request.
6. If the hostname cannot be resolved to an IP address then the call fails.
Administering initial setup of the Session Manager
About this task
Once you have completed the initial setup as a part of ongoing administration, you can modify
the created entities or delete them as required.
The recommended order for the initial set up of the Session Manager using the System
Manager Routing screens is as follows.
Procedure
1. Accept or change default settings.
2. Create domains.
3. Create locations.
4. Create adaptations.
5. Create SIP entities, some of which are routing destinations:
• Create other SIP entities.
• Assign locations and adaptations to the SIP entities.
6. Create entity links:
• Between Session Managers.
• Between Session Managers and other SIP entities.
7. Create time ranges.
Routing
Administering Avaya Aura
®
Session Manager November 2010 237
Komentáře k této Příručce