Procedure
1. On the System Manager console, under Elements, click Session Manager.
2. Click Session Manager Administration in the left navigation pane.
3. Select a Session Manager instance from the list and click Edit.
4. Under the General section, change the following information, if required:
• Add a comment in the Description field for the Session Manager SIP entity.
• Change the IP address of the host on which the Session Manager is installed
in the Management Access Point Host Name/IP field. This is the IP address
of the domain name of the server that hosts the Session Manager application.
Session Manager passes the address to the SM100 agent to allow the agent
to query the server for the required information. To be a part of the Session
Manager instances network of an enterprise, a Session Manager instance
must first be administered as a management access point.
• Select the Direct Routing to Endpoints from the drop-down list.
5. Under the Security Module section, change the following information, if required
• Modify the network mask in the Network Mask field. Session Manager passes
this network mask to the SM100 agent. The agent configures the network mask
to define the subnet that the SM100 card is to be associated with.
• Modify the IP address in the Default Gateway field.
• Modify the value for Call Control PHB. The Call Control PHB (per hop
behavior) specifies the type of service and priority SIP traffic from SM100 that
you may expect as it travels through the IP network. All packets containing SIP
signaling which leave the SM100 have the specified value in the DSCP
(differentiated service code point) field of the IP header. Intervening routers
may or may not treat packets with this value with a different level of
precedence--they must either support this by default or be specially configured
to do so.
Different DSCP values are specified in RFCs 2597 and 2598. To be consistent
with Communication Manager, Session Manager uses a default DSCP value
of 46 which indicates forwarding with the highest priority.
• Select the Speed & Duplex value to configure the security module interface
speed and duplex values.
• Modify the QOS Priority value. This is the value of 802.1q priority bit (Layer 2
QoS) configuration to be used by Session Manager for any SIP traffic. The
default is 6. Range of this value is 0-7. This value specifies the ability to provide
different priority to different applications, users, or data flows, or to guarantee
a certain level of performance for a call on a local area network. The higher
the priority, the lower the QOS priority number.
Session Manager Administration
Administering Avaya Aura
®
Session Manager November 2010 337
Comentários a estes Manuais