Avaya SM61 - Manual (Page 15)

MJH; Reviewed:
SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
15 of 47
Sagemcom_SM61
6. Configure Session Manager
This section provides the procedures for configuring Session Manager (version 6.1) as
provisioned at Site 2 in the reference configuration. Although not shown is this document, a
similar Session Manager configuration would be required at Site 1 (using the appropriate version
6.0 screens). All provisioning for Session Manager is performed via the System Manager web
interface.
The following sections assume that Session Manager and System Manager have been installed
and that network connectivity exists between the two platforms.
The Session Manager server provides the network interface for all inbound and outbound SIP
signaling and media transport to all provisioned SIP entities. During compliance testing, the IP
address assigned to the Security Module interface is 10.64.21.31 as specified in Figure 1. The
Session Manager server also has a separate network interface used for connectivity to System
Manager for provisioning Session Manager. The IP address assigned to the Session Manager
management interface is 10.64.21.30.
The procedures described in this section include configurations in the following areas:
 SIP Domains – SIP Domains are the domains for which Session Manager is authoritative in
routing SIP calls. In other words, for calls to such domains, Session Manager applies
Network Routing Policies to route those calls to SIP Entities. For calls to other domains,
Session Manager routes those calls to another SIP proxy (either a pre-defined default SIP
proxy or one discovered through DNS).
 Locations – Locations define the physical and/or logical locations in which SIP Entities
reside. Call Admission Control (CAC) / bandwidth management may be administered for
each location to limit the number of calls to and from a particular Location.
 Adaptations – Adaptations are used to apply any necessary protocol adaptations, e.g.,
modify SIP headers, and apply any necessary digit conversions for the purpose of inter-
working with specific SIP Entities.
 SIP Entities – SIP Entities represent SIP network elements such as Session Manager
instances, Communication Manager systems, Session Border Controllers, SIP gateways, SIP
trunks, and other SIP network devices.
 Entity Links – Entity Links define the SIP trunk/link parameters, e.g., ports, protocol
(UDP/TCP/TLS), and trust relationship, between Session Manager instances and other SIP
Entities.
 Time Ranges – Time Ranges specify customizable time periods, e.g., Monday through
Friday from 9AM to 5:59PM, Monday through Friday 6PM to 8:59AM, all day Saturday and
Sunday, etc. A Network Routing Policy may be associated with one or more Time Ranges
during which the Network Routing Policy is in effect.
 Routing Policies – Routing Policies are used in conjunction with a Dial Patterns to
specify a SIP Entity that a call should be routed to.
 Dial Patterns – A Dial Pattern specifies a set of criteria and a set of Network Routing
Policies for routing calls that match the criteria. The criteria include the called party number
and SIP domain in the Request-URI, and the Location from which the call originated. For