
Chapter 5: Managing Session Manager
routing
Overview of Session Manager routing
This section details the procedures that are required to set up Session Manager enterprise
routing. To complete the administrative procedures, you must use the Routing selection from
the System Manager Common Console navigation pane.
Once the initial setup is completed, administrators can use the same screens and procedures
for administering and modifying the various routing entities as well as Session Manager
instances.
The primary task of Session Manager is to route session creation requests from one server to
another based on the address specified in the session creation request.
The addresses which are specified to identify the ultimate destination of a session creation
request are in the form of a SIP Uniform Resource Identifier (URI). It consists mainly of a user
part and a domain part. Session Manager uses both parts in its routing decisions in the
following manner:
• The domain part is normally a DNS domain.
• The user part is an alphanumeric string (or handle). Session Manager has special rules
for efficiently routing and manipulating handles which consist entirely of digits (for
example, telephone numbers).
The servers which send their session creation requests to the Session Manager are called SIP
entities. Session Manager routes these requests to other SIP entities based on the routing
rules you have administered.
Session Manager associates SIP entities with specific locations and can make different routing
decisions based upon the location from which a session creation request arrives.
Administering Avaya Aura
®
Session Manager November 2010 235
Comentarios a estos manuales