Unified Communications Manager Session Management Edition System Test Configuration Release 8.5(1)
From DocWiki
(Created page with "Applicable to UC System Release 8.5(1) =Introduction= This topic provides reference configuration for Cisco Unified Communications Manager Session Management Edition within a Cis...") |
m (1 revision) |
Revision as of 21:39, 10 January 2011
Applicable to UC System Release 8.5(1)
Contents |
Introduction
This topic provides reference configuration for Cisco Unified Communications Manager Session Management Edition within a Cisco Unified Communications deployment. The information is based primarily on testing performed during Cisco Unified Communications Release 8.5(1) system testing. This topic does not contain detailed step-by-step procedures; for detailed information about installing, and configuring Unified Communications Manager Session Management Edition, refer to the Unified Communications Manager Session Management Edition documentation.
Design
Cisco Unified Communications Manager Session Management Edition provides centralized trunking, unified communications application integration, policy control, and centralized dial plan. It reduces communication tolls, cuts administrative overhead, and supports easier migration to a full IP telephony environment. Unified Communications Manager Session Management Edition provides internal dial plan aggregation through Service Advertisement Framework (SAF). Cisco Service Advertisement Framework Call Control Discovery (CCD) deployments distribute both internal dial plan and corresponding external "To PSTN" dial plan to participating SAF CCD Unified Communications systems.
Combining Unified Communications Manager Session Management Edition and SAF CCD enables Session Management Edition to act as the central Session Manager for all leaf Unified Communications systems, while also using SAF CCD to distribute both the internal and external "To PSTN" dial plans to all SAF CCD participating Unified Communications Manager leaf clusters.
In a typical Session Management deployment, Unified Communications Manager Session Management Edition is essentially a Unified Communications Manager cluster with trunk interfaces only and with no IP endpoints. Here Unified Communications Manager is deployed in a session management mode. Thereby Unified Communications Manager’s rich interoperability and protocol support can interface with third-party PBX and other Unified Communications Manager clusters within the system. It enables aggregation of multiple unified communications systems/clusters referred to as leaf systems.
Figure 1: Centralized Trunking, UC Application Integration, Control by Unified CM - Session Management Edition.
For more information on Multisite Deployment with Unified Communications Manager Session Management Edition, refer to the section Unified Communications Manager Session Management Edition in the Unified Communications Solution Reference Network Design for Unified CM Release 8.x.
Topologies
This section contains Unified Communications Manager Session Management Edition deployment scenario and call flows in system test environment.
Component Deployment
During Cisco Unified Communications 8.5(1) Release system testing, the Unified Communications Manager Session Management Edition deployment and testing scenarios covered inter-working with H.323 Annex M1 intercluster trunks, SIP and SAF intercluster trunks terminating on a Unified Communications Manager Session Management Edition cluster.
The Unified Communications Manager Session Management Edition deployment has two Unified Communications Manager Session Management Edition clusters, see Figure 2; CDG-SME cluster and GVA-SME cluster. CDG-SME cluster is co-located with CDG (Paris) site and aggregates trunks from the CDG-Leaf node and MAD-Leaf node. The GVA-SME cluster, which is co-located with GVA (Geneva) site aggregates trunks from GVA-Leaf node, RKV-Leaf node and BRU-Leaf node. CDG-SME cluster and its leaf nodes (CDG, CDG-remotes, MAD) are running in SAF Autonomous system 333 and GVA-SME cluster and its leaf nodes (GVA, RKV, BRU) are running in SAF Autonomous system 444. Calls flowing from MAD-Leaf and LGW-Leaf do not have direct trunk to reach GVA-Leaf; instead they have to reach GVA-Leaf via Paris (CDG-SME). Similarly, calls from BRU-Leaf and RKV do not have a direct trunk to CDG-Leaf, they have to be routed through GVA-Leaf.
The following deployments were supported and tested by Unified Communications Manager Session Management Edition:
- Unified CM—Unified CM-SME—Unified CM (Sites used: CDG-> CDG-SME->MAD)
- Unified CM—Unified CM-SME—Unified CME (Sites used: GVA-> GVA-SME-> RKV)
- Unified CM—Unified CM-SME—Unified CM-SME—Unified CM (Sites used: CDG->CDG-SME->GVA-SME->GVA)
- PBX-SIP GW-Unified CM—Unified CM-SME—Unified CM-MGCP-PBX (sites used: PBX ->SIP GW ->CDG ->CDG- SME ->MAD-MGCP GW ->PBX)
Figure 2: Unified CM Session Management Edition Deployment in System Test Environment.
To route calls between the two SME clusters and in turn its leaf nodes, a static SIP (QSIG) trunk running between CDG-SME cluster and GVA-SME cluster is configured. CDG-SME cluster has a SIP Gateway for PSTN breakout and centralized Cisco Unity Connection server for voice mail service. The focus of testing was on SAF enabled SIP (QSIG) trunks with E2E RSVP support and QSIG features over SAF enabled SIP (QSIG) trunks.
On CDG-SME cluster, the SAF-CCD service advertises its leaf node DN information and “To PSTN” prefix to the SAF network and have a static SIP (QSIG) trunk to each of its leaf clusters (CDG and MAD sites). For example, in figure 2, when a call is made from CDG-Leaf to MAD-Leaf via CDG-SME cluster, first leg from CDG-Leaf to CDG-SME cluster will be SAF trunk and second leg from CDG-SME cluster to MAD-Leaf will be static SIP (QSIG) trunk, covering both SAF trunks and static SIP (QSIG) trunks. H.323 Annex M1 intercluster trunks are set up between CDG-SME and LGW-Leaf.
Global dial plans (8-digit dial plan) were configured for each cluster so that the call flows from one cluster to another is either over a static SIP or SAF trunk or an AnnexM1 trunk based on the user preference.
The following features supported by Unified Communications Manager Session Management Edition were tested:
- SAF for TCO with Unified CM-SME
- SAF-SME with E2E RSVP
- SAF for Distributed PSTN Fall Back with SME
- Q.SIG over SAF enabled SIP Trunk features
- ASA support for Q.SIG over SAF enabled SIP Trunk
- Run SAF Trunks on all nodes
Different endpoints such as SIP phones, SCCP phones, Cisco Unified Communications Integration for Microsoft Office Communicator and video endpoints were tested on the leaf systems. Unified Communications Manager Session Management Edition interworking with RSVP/CAC, calls with different codecs, video conferencing with MCU, and QSIG PBXs were also tested.
Call Flow Diagram
Example call flows between GVA-Leaf cluster to LGW-Leaf Cluster via CDG.
Configuration Details
This section provides Unified Communications Manager Session Management Edition testbed setup and configuration.
Table 1: Unified CM Session Management Edition Configuration.
| Configuration Task | Purpose | System Test Specific Configuration | More information |
| Create a centralized dial plan | Rather than configuring each unified communications system with a separate dial plan and trunks to connect to all the other unified communications systems, Unified Communications Manager Session Manager Edition allows you to configure the leaf unified communications systems with a simplified dial plan and trunk(s) pointing to the Session Manager. Unified Communications Manager Session Manager Edition holds the centralized dial plan with information to reach all the other Unified communications systems. | See the Route Pattern and Dial Plan for MAD-Leaf and CDG Sites section. | [http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs Session Manager
Designs] |
| Providing centralized PSTN access | Unified Communications Manager Session Manager Edition can be used to aggregate PSTN access to one (or more) centralized IP PSTN trunks. Centralized PSTN access is commonly combined with the reduction, or elimination, of branch-based PSTN circuits. | [http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs Session Manager
Designs] | |
| Aggregate PBXs for migration to a Unified Communications system | Unified Communications Manager Session Manager Edition can provide an aggregation point for multiple PBXs as part of the migration from legacy PBXs to a Cisco Unified Communications System. | [http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs Session Manager
Designs] | |
| Centralize applications | The deployment of a Unified Communications Manager Session Management Edition enables commonly used applications such as conferencing or videoconferencing to connect directly to the Session Management cluster, thus reducing the overhead of managing multiple trunks to leaf systems. | [http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs Session Manager
Designs] |
Route Pattern and Dial Plan for MAD-Leaf and CDG Sites
This section provides dial plans for MAD-Leaf and CDG sites.
To access the Cisco Unified Communications Manager Administration web pages for adding and configuring route patterns and dial plans, choose Call Routing > Route/Hunt > Route Pattern from the Cisco Unified Communications Manager Administration application. Table 2 shows the route patterns and dial plans that were configured from MAD-Leaf and CDG to GVA-Leaf.
Table 2: Route Pattern and Dial Plan for MAD-Leaf and CDG Sites.
| Field | Route Pattern and Dial Plan for MAD-Leaf to CDG-Leaf | Route Pattern and Dial Plan on SME to CDG-Leaf |
| Route Pattern | SAF learnt: 83356XXX | Static route: 83356XXX |
| Partition | SAF-Partition | SME-CDG |
| Description | SIP (SAF trunk) | SIP (SAF) trunk to SIP trunk (Static) |
| Route Class | Default | Default |
| Gateway/Route List | SAF-Trunk | SME-CDG |
| Route Option | Route This Pattern | Route This Pattern |
| Call Classification | OffNet | OffNet |
| Provide Outside Dial Tone | Yes (checked) | Yes (checked) |
| Calling Line ID Presentation | Default | Default |
| Calling Name Presentation | Restricted | Restricted |
| Calling Party Number Type | Cisco CallManager | Cisco CallManager |
| Calling Party Numbering Plan | Cisco CallManager | Cisco CallManager |
| Connected Line ID Presentation | Restricted | Restricted |
| Connected Name Presentation | Restricted | Restricted |
| Discard Digits | PreDot | PreDot |
| Called Party Number Type | Cisco CallManager | Cisco CallManager |
| Called Party Numbering Plan | Cisco CallManager | Cisco CallManager |
Related Information
For related information about Unified CM Session Management Edition, see the documents listed at: http://www.cisco.com/en/US/products/ps10661/index.html
http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition
