
Manager application. Branch Session Manager passes the address to the
security module to allow the agent to query the server for the required
information. To be a part of the Branch Session Manager instances network of
an enterprise, a Branch Session Manager instance must first be administered
as a management access point.
• Select the Main CM for LSP from the drop-down list. Click the View / Add CM
Entities link to add new CM applications.
• Select the Direct Routing to Endpoints from the drop-down list.
• Select the Adaptation for Trunk Gateway from the drop-down list. This
selected adaptation is used by the Branch Session Manager during routing
calls to or from the Communication Manager LSP trunk gateway.
Note:
In case of Communication Manager Feature Server (CM-FS) or
Communication Manager Trunk Gateway (CM-TG), the adaptation from the
core CM-TG is used by default. This field adaptation selection overrides the
default CM-TG adaptation and is applied to all calls routed on the trunk
gateway entity to the LSP. For Communication Manager Evolution Server
(CM-ES), the default adaptation is taken from the core Communication
Manager entity. The adaptation is applied either to calls that are routed
through the gateway to the LSP and also to calls that are application
sequenced.
5. Under the Security Module section, change the following information, if required
• Modify the network mask in the Network Mask field. Branch Session Manager
passes this network mask to the security module. The agent configures the
network mask to define the subnet that the security module 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 security
module that you may expect as it travels through the IP network. All packets
containing SIP signaling which leave the security module 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, Branch 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 Branch Session Manager for any SIP traffic.
Branch Session Manager Administration
Administering Avaya Aura
®
Session Manager November 2010 355
Comentários a estes Manuais