Amanda Lalli-Cafini Unified Communications LAB

Unified Communications LAB
Unified Communications LAB | [Type the company name]
Contents
Unified Communications LAB .................................................................................................................. 1 Contents ................................................................................................................................................... 2 Acknowledgments .................................................................................................................................... 3 Overview .................................................................................................................................................. 4 Cisco Unified Communications LAB ........................................................................................................ 5 Cisco Unified Communications Manager (CUCM)................................................................................... 6 Server Configuration ............................................................................................................................ 6 Communication Manager Features ................................................................................................... 22 Gateways ........................................................................................................................................... 27 Cisco Unity Connection Voicemail ..................................................................................................... 35 Cisco Presence ...................................................................................................................................... 38
Contents | [Type the company name]
Acknowledgments
I would like to formally acknowledge the cooperation of staff members of XYZ without whom, the preparation and submission of this document would not have been possible. These include:
Acknowledgments | [Type the company name]
Overview
XYZ has engaged Amanda Lalli-Cafini to implement and provision a Unified Communications (UC) solution. This section of the Low Level Design (LLD) will detail configuration and integration requirements to ensure that XYZ obtain the maximum functionality from these systems.
Overview | [Type the company name]
Cisco Unified Communications LAB

The following lab will provide call routing, voicemail, presence information, desktop sharing, and the ability to make and receive calls from software based, mobile phones, and IPAD devices. The lab is based on Cisco Unified Communications Manager, Cisco Unity Connection, and Cisco Presence. Cisco Unified Communications Manager 8.6.2 will handle the central call processing signalling for the IP Telephony solution. It provides configuration information, call routing, caller restrictions, and phone images to the other components of the Cisco IP Telephony solution. A subscriber server will be the primary point for phones to register to and direct calls to. Cisco Unity Connection 8.6.2 will provide a platform for users to receive voicemail to their software based phones, mobile devices, and email client using IMAP. Unity Connection will also allow users to customise their voicemail settings through a web GUI. Users for example can configure Unity Connection to provide message notification of new messages through devices such as SMTP, SMS, text pagers and phone destinations. Cisco Unified presence will provide user availability information and the ability for users to collaborate with each other by phone, voicemail, chat, and desktop sharing. Cisco Jabber will be installed on user PCs, iPhones, and IPAD devices. The software will allow user to make and receive office calls, view presence information, and listen to voicemail on deskphones and hand held devices. A voice gateway router with SRST (Survivable Remote Site Telephony) will be configured to provide XYZ with a redundancy component. In the event of a failure of the CUCM servers, the router can assume the role of call processing for up to 50 local IP phones. The SRST component of the lab is dependant upon procurement of a suitable voice gateway router.
Cisco Unified Communications LAB | [Type the company name]
Cisco Unified Communications Manager (CUCM)

The Unfied Communications Manager will be built and located within the Canning Vale office. The CUCM 8.6.2 server will be built on a VMWare environment and is based on a Linux operating system. The publisher server will keep a copy of the system configuration, provide a TFTP service, and provide a backup registration and call routing service for phones and unified communications applications. The Subscriber server will provide the primary registration and call routing services. The following sections detail the installation and configuration requirements for the XYZ CUCM 8.6.2 cluster. Figure 1: Cisco Unified Communications Solution
VMWare Environment
CUCM-PUB
CUCM-SUB
CUC
CUPS
Server Configuration
SOFTWARE INSTALLATION
The following software packages will be installed on the CUCM 8.6.2 server: Table 1 CUCM Server Software
SOFTWARE Cisco Unified Communications Manager CM Locale Installer Required Latest version available at time STATUS Required COMMENTS 8.6.2 (SU1)
Cisco Unified Communications Manager (CUCM) | [Type the company name]
SOFTWARE Australian Numbering Plan Device Pack
STATUS Required
COMMENTS Latest version available at time
Optional
Latest version available at time
During the installation of the appliance system software, the following network parameters will be specified: Table 2 CUCM Network Configuration (Internal clocking at the moment)
PARAMETER Hostname IP Address Subnet Mask Default Gateway NTP Server DNS PUBLISHER CUCM-PUB 192.168.1.111 255.255.255.0 192.168.1.111 203.0.178.191 Not set
PARAMETER Hostname IP Address Subnet Mask Default Gateway NTP Server DNS
PUBLISHER CUCM-SUB 192.168.1.112 255.255.255.0 192.168.1.111 203.0.178.191 Not set
After the installation of the CUCM 8.6.2 appliances is complete, the appropriate services need to be activated on the CUCM servers. The services will be activated as follows: Table 3 CUCM Services
SERVICE NAME Cisco CallManager Cisco TFTP PUBLISHER Activated Activated
SERVICE NAME Cisco Messaging Interface Cisco IP Voice Media Streaming App Cisco CTI Manager Cisco CallManager Attendant Console Server Cisco Extension Mobility Cisco Extended Functions Cisco Dialled Number Analyzer Cisco DHCP Monitor Service Cisco IP Manager Assistant Cisco WebDialer Web Service Cisco SOAP - CDRonDemand Service Cisco CAR Scheduler Cisco CAR Web Service Cisco AXL Web Service Cisco Bulk Provisioning Service Cisco TAPS Service Cisco Serviceability Reporter Cisco CallManager SNMP Service Cisco CTL Provider Cisco Certificate Authority Proxy Function Cisco DirSync-( dependant on obtaining an AD Server)
PUBLISHER Activated Activated Activated Deactivated Activated Activated Activated Deactivated Deactivated Activated Deactivated Activated Activated Activated Activated Deactivated Deactivated Deactivated Activated Deactivated Activated
SYSTEM
The system menu contains configuration options for the CUCM system. The following sections outline the configuration that will be applied.
SERVER
Table 4 Servers
IP ADDRESS 192.168.1.111 HOSTNAME CUCM-PUB DESCRIPTION CUCM Publisher
IP ADDRESS 192.168.1.112
HOSTNAME CUCM-SUB
DESCRIPTION CUCM Subscriber
The naming convention used for the implementation needs to recognize that additional subscriber servers may be added in the future.
CISCO UNIFIED CM
Table 5 Unified CM
NAME CM Group DESCRIPTION CM Group AUTOREGISTRATION Disabled
CISCO UNIFIED CM GROUP

Cisco Unified CM Groups are configured to determine the registration behaviour of IP Phones and other UC devices when multiple servers are in the cluster as will be the case at XYZ. The Cisco Unified CM Group configuration allows for the configuration of load balancing and redundancy of the CUCM 7.1 call processing functionality. The Cisco Unified CM groups will be configured as follows: Table 6 Unified CM Groups
CM GROUP CM Group GROUP MEMBERS CUCM-SUB CUCM-PUB AUTOREGISTRATION Yes
DATE/TIME GROUP
A date time group will be configured for Western Australia. This time group will be used to display the time on the phones. Table 7 Date/Time
DATE/TIME GROUP NAME WA W.Australia Standard Time (GMT +8) TIME ZONE DATE FORMAT D/M/Y TIME FORMAT 12-hour
REGION
A region is configured to represent each site at XYZ that directly interfaces the WAN. A single region will be configured for the Canning Vale site with a G.711 codec for intra-region calls, a G.729 codec
9 Cisco Unified Communications Manager (CUCM) | [Type the company name]
for inter-region calls, and 384K of bandwidth for video calls between regions. configuration will be as detailed below: Table 8 Region Configuration
SITE REGION NAME LOCAL AUDIO CODEC Canning Vale CaninngVale Default (G.711) AUDIO CODEC
The region
VIDEO CALL BANDWIDTH 384K
BETWEEN REGIONS Default (G.729)
DEVICE POOLS
A device pool is used to centrally configure a number of settings without having to configure these settings individually on each device. A device pool will be configured for each site so that all devices at each site can be configured with the same standard settings for that site. Within each device pool specific configuration can be applied such as regions, resource groups and music on hold sources. IP Phones will obtain their configuration based on the settings in the device pool configuration. The following device pool will be created: Table 9 Device Pools
PARAMETER NAME VALUE
Device Pool Name CUCM Group Date/Time Group Region SRST Reference MRGL
UC_LAB CM Group WA CanningVale 192.168.1.254 MRGL_UC_LAB
DIAL PLAN
The dial plan is a fundamental component of any Unified Communications implementation which requires careful consideration of all number ranges and calling behaviour of each site. With these considerations, the design of the UC implementation for XYZ will consider the following when preparing to deploy the infrastructure across all sites:
o o o
Extension dialling number of digits to be dialled to reach other extensions Extension addressing number of digits used to identify extensions Dialling privileges ability to dial certain numbers
o o o o o
Path selection how calls are to be routed. E.g. calls to remote site XYZ extensions to be routed over the WAN and external calls to be routed out the local PSTN gateway Alternate call paths if there is network congestion, should calls be routed through the PSTN? Blocking of calls are there types of calls that need to be blocked e.g. premium numbers Transformation of the called number e.g. retaining only the last five digits of a call dialled as a ten digit number Transformation of calling number are there numbers that should be transformed to another number e.g. if a user dials the full PSTN number for an internal extension, should this be transformed to an extension?
To cater for the multi-site solution a review has been done, of the existing number ranges used at all sites. In order to avoid clashes with number ranges some sites may need to change numbers or, if this is not possible, use a prefix when dialling some sites. A summary of the number ranges both in use and proposed is shown in the table below:
EXISTING DIAL PLAN

The existing dial plan is detailed in the table below: Table 10: Dial Plan - Existing
LOCATION INDIAL RANGE DIRECTORY NUMBER RANGE Canning Vale 8945529XX 70XX
PROPOSED DIAL PLAN

The proposed dial plan is detailed in the table below: Table 11: Dial Plan - Proposed
LOCATION INDIAL RANGE DIRECTORY NUMBER RANGE Canning Vale 8945529XX 70XX
A number of system extensions or numbers will also need to be configured for the UC environment these include pilot numbers for Voicemail, Pickup Groups, Call Parks and CTI Ports. These numbers do not have to be Indial numbers therefore they can be outside of the current dial plan range. The breakdown of allocated system numbers will be as follows:
11
Table 12: System Numbers

FUNCTION User Extensions MWI Indicators Voicemail Pilot Call Park Numbers Call Pickup Groups Unity Connection Pilots/Ports MeetMe CTI Ports CTI Route Points Transfer to Voicemail Emergency Emergency Services PSTN 6999 60XX 61XX 62XX 63XX 64XX 65XX *7XXX 0.000, 000 0.106 0.@ DIRECTORY NUMBERS 7XXX
PARTITIONS AND CALLING SEARCH SPACES

To build the required classes of service for the XYZ UC implementation, the line/device approach will be used. This will minimise the total number of partitions and calling search spaces required as opposed to using the traditional approach. Partitions and Calling Search Spaces (CSS) are the components of a CUCM implementation responsible for controlling dialling privileges. Cisco defines a partition as a group of directory numbers (DNs) with similar accessibility, and a CSS determining which partitions are accessible to a particular device. A device is only able to call those DNs located in the partitions that are part of its CSS. To provide the appropriate calling privileges and the ability to restrict certain devices from particular calling capabilities, the following partitions and calling search spaces will be created: Table 13: Partitions
PARTITION Internal System DESCRIPTION All directory numbers at XYZ All devices and numbers accessible by all devices
12
PARTITION VMPorts OffNet Local National IDD Unrestricted Emergency
DESCRIPTION Voicemail ports and DNs only accessible by VM Pilot Route patterns to external numbers via LAB gateway Allow patterns for local numbers Allow patterns for STD and mobile numbers Allow patterns for International calls Unrestricted calls Emergency Services
All user directory numbers at XYZ will be in the same partition, Internal. If it is a requirement for greater restrictions on the ability for every directory number to be accessible by all users, then additional partitions can be created. Once partitions have been created, the calling search spaces can be created with the list of partitions to be included under each calling search space. The XYZ UC implementation will utilise the line/device approach for implementing class of service which requires CSS to be applied at both the device and line level. Therefore two groups of CSS will need to be created. The first group will define reach ability of system devices i.e. other extensions at XYZ, voice mail ports, system numbers and voice gateways and will be applied at the device level. The second group of CSS will define the calling restrictions of the extension and will be applied at the line level. The combination of these two CSS defines an extensions calling capabilities. The table below defines the CSS to be applied at the device level: Table 14: Calling Search Spaces Device Level
CALLING SEARCH SPACE VM Restricted VMPorts System Internal System System Internal Device System Internal OffNet AAR OffNet PARTITION LIST
The table below defines the CSS to be applied at the line level:
Table 15: Calling Search Spaces - Line Level

CALLING SEARCH SPACE Internal Emergency Internal System Local Emergency Internal System OffNet Local National Emergency Internal System OffNet Local National IDD Emergency Internal System OffNet Local National IDD PARTITION LIST
The combination of the line and device level CSS will allow XYZ to determine how individual extensions will have calling extensions applied.
ROUTE GROUPS AND ROUTE LISTS

Route Groups define a collection of gateways. A route group will be created to represent each of the PSTN gateways located at XYZ. Route groups provide the flexibility to add secondary voice gateways if required.
The following table details the route groups that will be created to enable calls destined for the PSTN to be directed to the appropriate gateways. Table 16: Route Group Details
ROUTE GROUP NAME LAB_PSTN_RG 192.168.1.254 ROUTE GROUP MEMBERS
Once the route groups have been configured, they are associated with route lists. The route list allows the administrator to configure additional parameters such as digit manipulation. The following route lists will need to be configured: Table 17: Route List Details
ROUTE LIST NAME CUCM GROUP ROUTE LIST MEMBERS CALLING PARTY TRANSFORM MASK LAB_PSTN_RL XYZ CMG LAB_PSTN_RG 945529XX None DISCARD DIGITS
ENTERPRISE PARAMETERS
The following changes to the Enterprise parameters will be required for the Australian environment. Table 18 Enterprise Parameters
PARAMETER NAME BLF for Call Lists Advertise G.722 Codec Default Network Locale Default User Locale Enabled Disabled Australia English, United States VALUE
LOCATIONS
Locations are required to provide Call Admission Control (CAC) capabilities for calls between sites. CAC is an essential component in ensuring optimum call quality between sites. As with the Region configuration, Locations will be configured for sites that directly interface the WAN. Locations reference the region configuration to determine the codec used between the sites. In the case of XYZ, a call from one site to another will always use the G.729 codec. The locations bandwidth is configured as a multiple of the bandwidth required for a single call. For example, based on allowing 5 concurrent voice calls between each of the sites, the amount of locations bandwidth
15
that will be provisioned is 5 x 24kbps (the amount of bandwidth CUCM allocates for a single G.729 call). Where there is more than one site represented in the Locations configuration, the total number of calls and audio bandwidth will be calculated based on the combination of all sites under the location. The following table shows the Location configuration: Table 19 Locations
LOCATION NAME LAB NUMBER OF CALLS Unlimited AUDIO BANDWIDTH Unlimited VIDEO BANDWIDTH None
PHYSICAL LOCATIONS
Physical Locations are also configured to reflect each site in the XYZ CUCM cluster. This can be used to ensure correct resource allocation if using extension mobility. Table 20 Physical Locations
PHYSICAL LOCATION LAB DESCRIPTION Devices located at VDC
SRST REFERENCES
Survivable Remote Site Telephony (SRST) capabilities are used to support all IP Phone devices located at the particular site. The SRST functionality is used at a remote site where there is no CUCM servers to register to and in the event of a WAN outage , SRST will allow the sites to continue to receive inbound and make outbound calls via the PSTN as well as allow for calls between extensions on the site that is in SRST mode. To enable this functionality, SRST profiles will be created for each site with a voice gateway. As VDC is the location of the main infrastructure including the Telephony servers, there is no requirement to use SRST, however this can be added as a additional redundant method if required Table 21 SRST References
SRST REFERENCE NAME LAB-SRST IP ADDRESS 192.168.1.254
16
LDAP DIRECTORY INTEGRATION

CUCM allows for LDAP directory integration without the need for changes to the Microsoft Active Directory schema. XYZ will implement LDAP directory integration from the CUCM cluster to enable end users with single sign on capabilities for UC requirements. LDAP on TCP port 389/3268 is used to import end users for CUCM from Microsoft Active Directory. For the integration to occur, an account needs to be created in AD with the permission to read all user objects. That account needs to be specified within CUCM The Domain Content (DC) and Organisation Unit (OU) of the AD will be configured in CUCM to allow CUCM to look for the specified user database to synchronise with AD. The synchronisation can be scheduled in CUCM, with the minimum configurable interval being every 4 hours. Table 22 LDAP System
PARAMETER Enable Sync from LDAP LDAP Server Type LDAP Attribute for User ID Checked Microsoft Active Directory sAMAccountName VALUE
Table 23 LDAP Authentication

PARAMETER LDAP Manager Distinguished Name Password LDAP User Search Base LDAP Server(s) xxxx DC=ad,DC= XYZ,DC=com,DC=au users.ad.XYZ.com.au VALUE CN=ciscocallmanquery,CN=users,DC=ad,DC= XYZ,DC=com,DC=au
Table 24 LDAP Directories

CONFIGURATION NAME LDAP Manager Distinguished Name USER SEARCH BASE DC=ad,DC= XYZ,DC=com,DC=au
The LDAP synchronization is enabled in the LDAP system and then the corresponding attributes as mentioned above are configured in the CUCM under LDAP system and LDAP authentication.
AAR GROUPS
Automated Alternate Routing groups are used to ensure that in the event of bandwidth oversubscription between sites, calls will be re-routed via the PSTN by prefixing digits to AAR Number Mask of the Dialled extension. As XYZ will have a standardised external access code of 0 across all
sites, only one AAR Group will be required. The following table details the AAR group settings required for the XYZ voice network: Table 25 AAR Groups
AAR GROUP NAME XYZ 0 PREFIX DIGITS
In addition to this configuration, the AAR Number Mask will have to be configured for every XYZ IP Phone. This field is defined on the line and will reflect the full eight digit PSTN number. The AAR configuration for XYZ devices will be as shown below:
Table 26 Line/Device Settings on IP phone to support AAR

AAR CSS (DEVICE) AAR GROUP (LINE) AAR CSS VDC XYZ AAR NUMBER MASK (LINE) 834099XX
APPLICATION DIAL RULES

Application dial rules are configured to manipulate number patterns so that numbers in the corporate directory, which are sourced from AD, can still be dialled even though the formatting of the number may not be acceptable for Cisco Unified Call Manager. The following table details the ADRs that are configured for the XYZ voice network listed in order of priority: Table 27 Application Dial Rules
NAME DESCRIPTION BEGINS WITH DIGITS DIGITS TO REMOVE WA-SANT NSWACT VIC-TAS Prepend zero for WA-SA-NT Prepend zero for NSW-ACT Prepend zero for VIC-TAS QLD Prepend zero for QLD Mobile Prepend zero for mobile
PREFIX WITH
08
10
02
10
03
10
07
10
04
10
NAME
DESCRIPTION
BEGINS WITH
DIGITS
DIGITS TO REMOVE
PREFIX WITH
Free1800
Add Zero for 1800
1800
10
Toll1300
Add Zero to 1300
1300
10
ROUTE PATTERNS
Route patterns are configured to allow calls to external (OffNet) numbers. Separate route patterns will be configured to route all calls to the PSTN via the Route Lists that have been configured for each site. The route patterns to be configured will be as follows: Table 28 Route Patterns
ROUTE PATTERN Route Patterns 0.@ Australian Numbering Plan Catchall 0.000 Emergency Calls VDC OffNet <None> VDC_PSTN_RL Route (with Priority) VDC OffNet <None> VDC_PSTN_RL Route DESCRIPTION PARTITION ROUTE FILTER ROUTE LIST ROUTE/BLOCK THIS PATTERN
TRANSLATION PATTERN
Translation patterns can be used to translate a dialled number to another number, whether this is for system wide abbreviated dialling functionality or to ensure that the most efficient path is taken for a dialled number.
19
Table 29: Translation Patterns

NUMBER 945529XX 94552999 TRANSLATION 70XX 6999 DESCRIPTION Translation for PSTN INDial Range Allow Access to the Voicemail Pilot from the PSTN
MEDIA RESOURCES
A Cisco UC implementation provides functionality for audio conferencing, transcoding and music on hold (MOH). Whilst audio conferencing and MOH is self explanatory, the transcoding functionality requires some explanation. In a multi site UC implementation where there is a mix of G.711 and G.729 voice codecs in use, there is the requirement to transcode between the two codecs when there are applications that utilise functionality such as Arc Console. This application in particular utilises components that can only be configured to use one codec, generally G.711. When a user at a remote site, in the case of XYZ this would be any site outside of VDC, attempts to contact VDC reception, they will be dialling a voice CTi Port at XYZ which will be configured to use the G.711 codec. However the call from the remote site to XYZ is configured to use G.729. When the regional sites are deployed DSP resources on the routers will be configured to transcode between the G.711 and G.729 codec to allow the remote user to contact the ARC Console operator at VDC. Media resources allow the configuration of conference bridge, transcoding and MOH functionality. The media resources will be configured on the CUCM servers initials. The transcoding and conference bridge functionality could be configured on the Cisco voice gateways using the Digitial Signal Processor (DSP) resources for each remote site for XYZ. Table 30 Conference Bridge/ Media Termination Point
TYPE CFB MTP XCODE CFB _2 MTP_2 NAME
MOH will be configured on the two servers, which will allow XYZ to add their own specific music sources. MOH is configured to be streamed using multi-cast sources from the CUCM servers. Multiple MOH Source files can be created and assigned to common device profiles that define resources to be used by sites or business units. The following tables detail the configuration requirements for the MOH Audio Source and the MOH Server:
Table 31 Music on Hold Audio Sources

STREAM NO 1 2 SampleAudioSource XYZ_MOH_Source SampleAudioSource XYZ_MOH_Source Yes Yes SOURCE FILE SOURCE NAME CONTINUO US Yes Yes M/CAST
Table 32 Music on Hold Servers

PARAMETER NAME Server Name Device Pool Location Enable Mcast? VALUE MOH CM MOH Servers MOH Yes
Once the MOH functionality has been configured, the resources can then be allocated to Media Resource Groups (MRGs). The following MRGs will be created: Table 33 Media Resource Groups
MRG NAME RESOURCES USE MULTICAST FOR MOH MRG MOH CM MRG CFB CM MOH Server from Publisher CFB Server from Publisher Checked Checked
Once the MRGs have been created Media Resource Group Lists (MRGLs) will be created to ensure each location has access to required media resources. The MRGLs are applied to the device pool. The following MRGLs will be created: Table 34 Media Resource Group Lists
MRGL NAME MRGL_LAB MRG MOH MRG CFB MRG MTP MRG
SERVICE PARAMETERS
Some of the CUCM service parameters will be changed from their default settings to allow for additional functionality. In particular, the service parameter settings for Call Detail Records (CDR).
21
In addition, the Forward No Answer Timeout (sec) service parameter determines the number of seconds prior to a call being forwarded to voicemail and this is often customised. The table below details the settings that will need to be changed from their default. Table 35 Service Parameters
SERVICE PARAMETER NAME CDR Enabled Flag CDR Log Calls with Zero Duration Flag Call Diagnostics Enabled Forward No Answer Timer (sec) G722 Codec Enabled True True True 18 Disabled VALUE
Communication Manager Features

Call Park
Call Park numbers are allocated on a per server basis. Twenty call park numbers will be initially allocated for the XYZ UC implementation. Call Park numbers will be configured as follows: Table 36 Call Park Numbers
CALL PARK NUMBER 9701-9720 PARTITION System CM CALLMANAGER
Cisco IP Phones
XYZ will initially install Cisco 7962 and Cisco 6921 IP Phones in the deployment. Below are the details relating to the firmware version that will be used for these phones in the environment Table 37: Cisco IP Phone Firmware
CISCO IP PHONE CIPC Jabber for Windows Jabber for iPhone Jabber for IPAD 9.1.1 FIRMWARE
22
CISCO IP PHONE
FIRMWARE
The Cisco IP Phones should obtain their IP address from a DHCP server. An example of a DHCP scope plan to be used with Microsoft DHCP server is detailed below. Table 38: DHCP Scope for VDC Office
DHCP SERVER x.x.x.x IP ADDRESSING y.y.y.y OTHER OPTION 150 Selected DETAILS LAB phones
At each remote site the phones will obtain their IP Addresses from the Voice Gateway/Router, the following configuration will need to be applied to each remote site Cisco 29xx gateway. IP Excluded-Address 10.20.42.1 255.255.255.192 ! ip dhcp pool Site DHCP Network 10.20.42.0 255.255.255.0 Default Router 10.20.42.1 Option 150 IP 10.50.150.100
Phone Templates
XYZs phone templates will be based on the standard templates within CUCM. Table 39: Phone Template
TEMPLATE XYZ CIPC BUTTON 1 2 Line Line LABEL
23
TEMPLATE
BUTTON
LABEL
Phone Softkey Template

XYZ will utilise one phone Softkey template with the following details Table 40: Phone Softkey Template
TEMPLATE Standard User NAME XYZ Standard User
Table 41: Standard User SoftKey Template

CALL STATE Connected SELECTED SOFTKEYS Hold End Call Transfer Park Conference Select Join Direct Transfer Connected Conference End Call Conference Connected Transfer End Call Transfer Digits After First Backward End Call Off Hook End Call Pick Up Group Pickup Redial Forward All Off Hook With Feature Redial End Call
24
CALL STATE On Hold
SELECTED SOFTKEYS Resume New Call Direct Transfer Select Join
On Hook
Redial New Call Forward All
Remote In Use
BXYZe New Call
Ring In Ring Out
Answer End Call
Common Device Configuration

XYZ will use the following Common Device Configuration profiles. These profiles are used to allow a group of similar users access to the same resources from the CUCM servers Table 42: Common Device Configuration
PARAMETER NAME VDC Softkey Template User Hold MOH Audio Source Network Hold MOH Audio Source User Locale XYZ Standard User LAB Audio Source LAB Audio Source English United States VALUE
CISCO CALL DETAIL RECORDS (CDR)

Cisco Call Detail Records (CDR) stores information about call processing on the CUCM cluster. The following services are required to ensure CDR is enabled and functional Table 43: CDR Services
SERVICE NAME Cisco CAR Web Service VALUE Enabled
25
SERVICE NAME Cisco SOAP-CDRonDemand
VALUE Optional (Required Using 3 Party)

rd
The CDR Repository Manager controls where the CDR records are stored and maintains the environment; the following settings will be applied to the CDR Repository Manager. Table 44: CDR Repository Manager
NAME Disk Allocation High Water Mark % Low Water Mark % CDR/CMR File Preservation Duration Disable CDR/CMR Files Deletion based On HWM VALUE 3000 80 40 30 Unchecked
The following CDR Enterprise Parameters will need to be configured within the CUCM system Table 45: CDR Service Parameters
NAME System Parameters CDR Enabled Flag CDR Log Calls With Zero Duration Flag Cluster Wide Parameters Device General Call Diagnostics Enabled Display FAC in CDR Show Line Group Member DN in finalCalledPartyNumber CDR Field Cluster Wide Parameters Device Phone Add Incoming Number Prefix to CDR True Enabled True True Enabled (All Servers) Enabled (All Servers) VALUE
The following CDR Service Parameters will also be configured in the CUCM system Table 46: CDR Enterprise Parameters
NAME CDR Parameters CDR File Time Interval 1 VALUE
26
NAME Cluster ID Web Service Parameters Allowed CDRonDemand get_file Queries Per Minute Allowed CDRonDemand get_file_list Queries Per Minute
VALUE StandAloneCluster
10
20
The following users will have access to the CDR Analysis and Reporting information Table 47: CDR Analysis and Reporting Administrators
NAME ccmadministrator Amanda Lalli-Cafini DESCRIPTION CUCM Administrator Amanda Lalli-Cafini Administrator
Gateways
There will be one Cisco rrxx series router which will be deployed for this implementation. This gateways will act as the primary inbound and outbound connection for all PSTN calls for the LAB and will also be used to connect the WAN back to the head office. Voice gateways at the remote sites will be configured for SRST to allow calls in the event that the remote site phones can reach the CUCM servers located at the head office. The interface between CUCM and the head office Voice gateway routers will be SIP. The voice gateway routers at the remote sites will use a combination of H.323 and SRST to allow them to function independently of the CUCM. This will allow calls to/from the PSTN to continue in the event of a CUCM server failure at the head office. Table 48: VDC Voice Gateway
VOICE GATEWAY Name here SERVICE ISDN 20 DESCRIPTION Cisco model Voice Gateway
The following table details the CUCM configuration of the Cisco 2921 gateways. Table 49 Voice Gateway Configuration Template
PARAMETER rtr-rand-XYZ01
VALUE
PARAMETER Gateway Type Device Name Description Device Pool Location Significant Digits (Inbound) Calling Search Space (Inbound) Calling Party Selection Calling Party Presentation Called party IE number type unknown Calling party IE number type unknown Called Numbering Plan Calling Numbering Plan UnKnown UnKnown UnKnown Originator Restricted UnKnown All System SIP
VALUE
SRST Voice Gateway

The WAN router will also be configured as a H.323 voice gateway with Survivable Remote Site Telephony (SRST) so that it may continue to provide basic telephony services in the event that connectivity to the CUCM server is not available. In order to route calls to and from the PSTN dial peers and translation rules will need to be configured as well as the SRST configuration. The following section shows a template configuration for the SRST voice gateways: The remote sites routers will be configured with the following template configuration: card type e1 0 0 ! network-clock-participate wic 0 network-clock-select 1 E1 0/0/0 !
28
isdn switch-type primary-net5 ! IP Excluded-Address X.X.X.X 255.255.255.x ! ip dhcp pool Site DHCP Network X.X.X.X 255.255.255.x Default Router X.X.X.X Option 150 IP X.X.X.X ! ip multicast-routing ! voice services voip modem passthrough nse codec g711alaw ! voice-card 0 no dspfarm dsp services dspfarm ! voice translation-rule 1 rule 1 /XXXXXX/ /1/ ! voice translation-rule 2 rule 1 /^02/ /002/ rule 2 /^03/ /003/
29
rule 3 /^04/ /004/ rule 4 /^07/ /007/ rule 5 /^08/ /008/ rule 6 /^7/ /07/ rule 7 /^8/ /08/ ! voice translation-profile PSTNIncoming translate called 1 translate calling 2 ! voice class h323 1 h225 timeout tcp establish 3 ! voice class codec 1 codec preference 1 g711ulaw codec preference 2 g729r8 ! controller E1 0/0/0 pri-group timeslots 1-10,16 description *** PSTN SERVICE *** ! interface Loopback0 ip address X.X.X.X 255.255.255.255 h323-gateway voip bind srcaddr X.X.X.X
30
! ip multicast-routing ! ccm-manager music-on-hold ! interface GigabitEthernet0/1 description *** remote site voice *** ip address X.X.X.X 255.255.255.0 ip pim sparse-mode ! ip pim rp-address X.X.X.X ! interface Serial0/0/0:15 no ip address encapsulation hdlc isdn switch-type primary-net5 isdn incoming-voice voice no cdp enable ! voice-port 0/0/0:15 translation-profile incoming PSTNIncoming cptone AU ! sccp local GigabitEthernet 0/1
31
sccp ccm X.X.X.X identifier 1 version 7.0 sccp ccm X.X.X.X identifier 2 version 7.0 sccp ! sccp ccm group 1 description Conferencing Resources associate ccm 1 priority 1 associate ccm 2 priority 2 associate profile 1 register CFBxxxxxxxxxxx ! dspfarm profile 1 conference codec g711ulaw codec g711alaw codec g729ar8 codec g729abr8 codec g729r8 codec g729br8 maximum sessions 6 associate application SCCP ! dial-peer voice 1 pots destination-pattern 0T progress_ind setup enable 3 progress_ind progress enable 8
32
direct-inward-dial port 0/0/0:15 ! dial-peer voice 10 voip description CUCM Extensions destination-pattern xx.. preference 1 progress_ind setup enable 3 progress_ind progress enable 8 progress_ind connect enable 8 session tXYZet ipv4:10.10.0.10 dtmf-relay h245-alphanumeric voice-class codec 1 no vad ! dial-peer voice 11 voip description CCM Extensions destination-pattern xx.. preference 2 progress_ind setup enable 3 progress_ind progress enable 8 progress_ind connect enable 8 session tXYZet ipv4:10.10.0.11 dtmf-relay h245-alphanumeric
33
voice-class codec 1 no vad ! call-manager-fallback secondary-dialtone 0 max-conferences 8 gain -6 transfer-system full-consult timeouts interdigit 3 ip source-address 10.10.x.x port 2000 max-ephones 50 max-dn 100 dialplan-pattern 1 xxxxx... extension-length 4 system message primary Fallback Mode: SRST in operation moh XYZMOH.wav multicast moh 239.1.1.1 port 16384 route X.X.X.X X.X.X.X
34
Cisco Unity Connection Voicemail

The Integrated Messaging solution for XYZ consists of a CUC server housed in a VMWare environment and connecting to the CUCM via a SIP trunk. The Unity Connection installation will be configured to use its onboard message store which allows for messages to be stored away from an Exchange environment and does not require the full Active Directory integration that some other products require. Subscriber mailboxes will therefore use the onboard message store to store all of their voice messages. The Cisco Unity Connection Version 8.6.2 software is a Linux based application. During the installation, the following network parameters will be specified: Table 50 Unity Connection Network Configuration
PARAMETER Hostname IP Address Subnet Mask Default Gateway VALUE
UNITY CONNECTION SOFTWARE

Table 51: Software Details
SOFTWARE Cisco Unity Connection UC Locale Installer STATUS Required Required Comments
VOICEMAIL PORTS
The Unity Connection system demo license allows for for 2 Voicemail Ports. The ports will be configured to cover all voicemail functions. The Ports will be configured in Unity Connection as follows: Table 52 Voicemail Ports Unity configuration
35
VM PORT# 1-2
SERVER
DIRECTORY NUMBER
ANSWER CALLS
MESSAGE NOTIFICATION Yes
DIALOUT MWI Yes
TRAP
HUNT LIST
CUC
n/a SIP integration
Yes
Yes
n/a
MWI NUMBERS
Message Wait Indicator numbers will need to be configured for the Unity Connection system to Dial to set MWI On/Off. Table 53 MWI Numbers
DIRECTORY NUMBER 6998 6999 MWI Off MWI On System System PARTITION DESCRIPTION CSS
VOICEMAIL PILOT & VOICEMAIL PROFILE

The VM Pilot & VM Profile should be configured according to the following tables Table 54 Voicemail Pilot
PILOT NUMBER 6999 Unity VM Pilot VM Restricted DESCRIPTION CSS SYSTEM DEFAULT Yes
Table 55 Voicemail Profile

NAME DESCRIPTION PILOT NUMBER SYSTEM DEFAULT Unity VM Unity Voicemail 6999 / VM Restricted Yes
CUCM INTEGRATION
In the Unity Administration a Phone System will be configured to handle the integration with CUCM. The Phone System parameters required for the integration are as follows: Table 56 Phone System configuration
PARAMETER Port Group Name Device Name Prefix MWI On CUC PortGroup CiscoUM1-VI 9898 VALUE
36
PARAMETER MWI Off Number of Ports IP Address Server Type 9899 2 X.X.X.X
VALUE
Cisco Unity Connection
An AXL connection is required in order to import CUCM users into the Unity server. The AXL server parameters required for the integration are as follows: Table 57 AXL Server configuration
PARAMETER IP Address Port Username Password CUCM Version X.X.X.X 8443 Cucaxl XXXX 5.0 or Greater (SSL) VALUE
Table 58 Enterprise Parameters The following changes to the Unity Connection Enterprise parameters will be required for the Australian environment.
PARAMETER BLF for Call Lists Advertise G.722 Codec Default Network Locale Default User Locale Enabled Disabled Australian English United States VALUE
37
Cisco Presence
This section provides integration details for Cisco Unified Presence Server with CUCM. integration of CUCM with the Cisco Presence server. Cisco Unified Presence collects information about a user's availability status such as busy, idle, away or available. The information regarding user capabilities (such as the capability to support voice, video, instant messaging and Web collaboration) is also collected and the data is complied in a repository for each presence user. Cisco Unified Personal Communicator (CUPC) is a Cisco desktop client which is used to perform numerous functions such as click to dial, phone control and voice, video, and Web collaboration. The Cisco Presence will be based on a VMWare server. Figure 2: Cisco Presence Cluster In this section Amanda Lalli-Cafini has described the integration steps essential for configuration and
LAB
CUPS Cisco Presence
CUCM CONFIGURATION
This section provides configuration information required on the Unified Communications Manager to integrate Cisco Unified Presence. Table 59: Application Server Details
PARAMETER Hostname IP Address Subnet Mask VALUE CUPS 192.168.1.114 255.255.255.0
38
Cisco Presence | [Type the company name]
PARAMETER Default Gateway
VALUE 192.168.1.1
CISCO PRESENCE SOFTWARE

Table 60: Software Details
SOFTWARE Cisco Unified Presence CUPS Locale Installer STATUS Required Required COMMENTS
SERVICE PARAMETERS
This configuration will apply to the two Unified Communications Manager Servers Service Parameters. The Cisco Unified Communications Manager Cluster wide settings, Default Inter-Presence Group Subscription will be set to Allow Subscription. Table 61: Security Profile for SIP Trunk
SIP TRUNK TYPE Non Secure INCOMING TRANSPORT TYPE TCP + UDP OUTGOING TRANSPORT TYPE TCP Accept Presence Subscription Accept Out-of-Dialog REFER Accept Unsolicited Notification Accept Replaces Header CHECK TO ENABLE
INSTALLATION USERNAME AND PASSWORD

The following table provides details for the Application User configured in Unified Communications Manager for Presence Integration. Table 62: Cisco Presence Access Configuration
TYPE OF LOGIN Operating System Administrator Application Administrator USERNAME administrator cupadministrator PASSWORD xxxx xxxx N/A Standard CUPS Super User AXL API user name cupsaxl xxxx Standard AXL API ROLES
39
SIP TRUNK CONFIGURATION

The following table provides SIP Trunk Configuration configured in Unified Communications Manager. Table 63: SIP Trunk Configuration
TRUNK NAME CUPS_Trunk DEVICE POOL System DESTINATION PORT 5060 DESTINATION ADDRESS 192.168.1.111 SECURITY PROFILE Non Secure SIP PROFILE Standard
PRESENCE SERVER CONFIGURATION

This section provides configuration required on the Cisco Unified Presence Server.
LICENSING
The relevant license file will be uploaded to the Presence server using the licensing File Upload option. Table 64: Presence Gateway
TYPE CUCM DESCRIPTION CUCM-PUB PRESENCE GATEWAY 192.168.1.111
Table 65: Proxy Server Settings

MODE On PREFERRED PROXY SERVER SETTINGS Default SIP Proxy TCP Listener
Table 66: Service Activation (List the other services)

SERVICE Cisco Enterprise SIP Proxy Cisco Enterprise Presence Engine Yes Yes ENABLE
40
SERVICE
ENABLE
PRESENCE CALENDAR INTEGRATION

Cisco Unified Presence will be configured to retrieve calendar state information and aggregate this into a presence status via the calendar module interface with Exchange 2003 mail environment. Microsoft Exchange makes the calendar data available from the server via Outlook Web Access (OWA), which is built upon WebDAV protocol extensions. The integration with Exchange will be completed via a separate presence gateway configuration for calendar applications, once this is configured users will have the ability to enable or disable information into their presence status. The communication between the presence server and Exchange is done using HTTP. Table 67: Aggregated Presence State Based on Calendar State
CALENDAR STATE Free/Tentative Busy Out Of Office CISCO UNIFIED PRESENCE STATE Available Idle/Busy Away
To ensure that the correct calendar information is synced from the Exchange calendar data the Presence Users ID will be used. This ID will be mapped as the users UserID in Communications Manager ensuring the information is being sent to the correct user store. Information is gathered via a subscription for calendar state from the Presence Server to the Microsoft Exchange server. The Presence server requires an Exchange account with special permissions to query end user calendar data which are detailed below Table 68: Exchange Account Details
NAME ciscopresence PASSWORD XXXX PERMISSIONS Exchange View-Only Administrator Group Receive-As permission on end user mailboxes
41
CISCO JABBER
The Cisco Jabber client will be used to provide real-time presence information to other users within the environment. The Cisco Jabber software will be installed on the Windows operating systems. The Jabber client will be used for presence information, instant messaging, voicemail, click to call and searching the corporate directory.
Table 69: Jabber Presence States

CISCO UNIFIED PRESENCE STATE Available DESCRIPTION The person is logged in to Cisco Unified Personal Communicator and has recently been using his or her computer or phone. Alternatively, the person has set the status to Available. Away Do Not Disturb The person has set the status to Away Setting your availability status to Do Not Disturb prevents people from initiating instant messaging with you. If you initiate an instant messaging session, the recipient can respond until you close the messaging window. When your availability status is set to Do Not Disturb, if the phone mode is set to soft phone and people call you, the calls generally go directly to voice mail without alerting you through your computer. However: Your desk phone may ring. Calls may be forwarded to numbers other than voice mail. Incoming calls may not be displayed in the Recent communications list
42
CISCO UNIFIED PRESENCE STATE Invisible (Appear Offline)
DESCRIPTION Setting your availability status to Invisible (Appear Offline) prevents people from seeing your presence information when you are logged in. Your screen name will appear offline to all people who have you in their Contact List. The Invisible status does not impact your ability to use outward bound Cisco Unified Personal Communicator features
Offline or Unknown
The person is not logged in to Cisco Unified Personal Communicator, the person has added you to his or her blocked list, or the system is unable to determine the status of the person.
None
The person is not set up to exchange availability status and instant messages with you through Cisco Unified Personal Communicator.
To ensure that users will be able to place calls from the Jabber client the following Application Dial rules will be applied to the Communications Manager server, in order to format the numbers from the directory or contacts, into a format that can be dialled by CUCM. Table 70: Application Dial Rules
NAME DESCRIPTION BEGINS WITH DIGITS DIGITS TO REMOVE ADE-PER-NT NSW-ACT VIC-TAS QLD Mobile Free1800 Toll1300 Prepend zero for ADE-PER-NT Prepend zero for NSW-ACT Prepend zero for VIC-TAS Prepend zero for QLD Prepend zero for mobile Add Zero for 1800 Add Zero to 1300 08 02 03 07 04 1800 1300 10 10 10 10 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 PREFIX WITH
43

Amanda Lalli-Cafini Unified Communications LAB

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Amanda Lalli-Cafini Unified Communications LAB

Hochgeladen von

Copyright:

Verfügbare Formate

Unified Communications LAB

Unified Communications LAB

Unified Communications LAB | [Type the company name]

Unified Communications LAB

Contents | [Type the company name]

Unified Communications LAB

Acknowledgments | [Type the company name]

Unified Communications LAB

Overview | [Type the company name]

Unified Communications LAB

Cisco Unified Communications LAB

Cisco Unified Communications LAB | [Type the company name]

Unified Communications LAB

Cisco Unified Communications Manager (CUCM)

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

SOFTWARE Australian Numbering Plan Device Pack

COMMENTS Latest version available at time

Latest version available at time

PUBLISHER CUCM-SUB 192.168.1.112 255.255.255.0 192.168.1.111 203.0.178.191 Not set

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

DESCRIPTION CUCM Subscriber

CISCO UNIFIED CM GROUP

Unified Communications LAB

VIDEO CALL BANDWIDTH 384K

BETWEEN REGIONS Default (G.729)

UC_LAB CM Group WA CanningVale 192.168.1.254 MRGL_UC_LAB

Unified Communications LAB

EXISTING DIAL PLAN

PROPOSED DIAL PLAN

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

Table 12: System Numbers

PARTITIONS AND CALLING SEARCH SPACES

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

PARTITION VMPorts OffNet Local National IDD Unrestricted Emergency

Unified Communications LAB

Table 15: Calling Search Spaces - Line Level

ROUTE GROUPS AND ROUTE LISTS

Unified Communications LAB

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

LDAP DIRECTORY INTEGRATION

Table 23 LDAP Authentication

Table 24 LDAP Directories

Unified Communications LAB

Table 26 Line/Device Settings on IP phone to support AAR

APPLICATION DIAL RULES

Unified Communications LAB

Add Zero for 1800

Add Zero to 1300

Cisco Unified Communications Manager (CUCM) | [Type the company name]

Unified Communications LAB

Table 29: Translation Patterns

Unified Communications LAB

Table 31 Music on Hold Audio Sources

Table 32 Music on Hold Servers