Implementation Document VCS-CUCM Integration

Embed Size (px)

Citation preview

  • Implementation Document VCS CUCM Integration for Voice Calls Version 1.0

    Cognizant Technology Solutions

  • Page 2 of 20

    Dimension Data | Implementation Document

    Document Control 1. Signoff

    Author(s) and client sign-off

    Company Name Signature

    Author(s): Dimension Data Rameez Rahim M

    Sriram P

    Quality Control Dimension Data Manu

    Client: Cognizant Technology

    Solutions Phanindra K

    2. Document Title

    Customer: Cognizant Technology Solutions, Chennai

    Title: Implementation Document

    Document Name: VCS CUCM Integration for Voice Calls

    3. Preparation

    Action

    Name Date

    Prepared by: Rameez Rahim M 07.04.2012

    Updated by:

    Updated by:

  • Page 3 of 20

    Dimension Data | Implementation Document

    4. Release

    Version

    Date Released Change Notice Pages Affected Remarks/Changes

    V 1.0 07.04.2012 NA NA First release

    5. Distribution List

    Name

    Organisation Title

    Phanindra K Cognizant NSS Team

    Spenser P Cognizant NSS Team

    Manu M Dimension Data Senior Consultant

    Pradeep KA Dimension Data Operations Manager

    Copyright and other intellectual property rights

    Copyright and other Intellectual property rights in any original programs, specifications, reports or other items

    arising in the course of, or resulting from the project shall remain the property of Dimension Data although

    Cognizant Technology Solutions shall have a non-exclusive and non-transferable license to all such items for its

    own purposes. Nothing in this agreement shall enable either party to make use of any intellectual property rights

    vested in the other party prior to the commencement of this assignment.

  • Page 4 of 20

    Dimension Data | Implementation Document

    TABLE OF CONTENTS Pg no

    1 INTRODUCTION ................................................................................................................................. 5

    2 ACTIVITY ............................................................................................................................................ 5

    3 DOWNTIME......................................................................................................................................... 5

    4 IMPACT ............................................................................................................................................... 5

    5 ASSUMPTION ..................................................................................................................................... 5

    6 REQUIREMENT .................................................................................................................................. 6

    ALL TRANSFORMATIONS WOULD BE DONE ONLY IN VCS. ....................................................................... 6

    7 DESIGN ............................................................................................................................................... 7

    7.1 VCS: .................................................................................................................................................... 7

    7.1.1 Call flow: ........................................................................................................................................... 7

    7.2 CUCM: ................................................................................................................................................. 8

    7.2.1 Call flow: ........................................................................................................................................... 8

    8 CONFIGURATION: ............................................................................................................................. 9

    8.1 VCS ..................................................................................................................................................... 9

    8.1.1 Creating Zones in VCS. ................................................................................................................... 9

    8.1.2 Configuring VCS Search Rules. ..................................................................................................... 11

    8.1.3 Configuring VCS Transformation: .................................................................................................. 13

    8.2 CUCM ................................................................................................................................................14

    8.2.1 Configure the SIP Profile................................................................................................................ 14

    8.2.2 Configure the SIP Trunk security profile ........................................................................................ 16

    8.2.3 Configure the SIP Trunk device ..................................................................................................... 17

    8.2.4 Allow numeric dialing from Cisco phones to Cisco VCS ................................................................ 19

    9 TEST PLAN .......................................................................................................................................20

    10 ROLL BACK ......................................................................................................................................20

  • Page 5 of 20

    Dimension Data | Implementation Document

    1 INTRODUCTION

    This document describes the Analysis on the proposed Configuration Change on Cisco VCS, which will enable the VCS to send and receive calls to and from CUCM. Note: This impact analysis applies for VCS Control India.

    2 ACTIVITY

    CTS want to integrate their Cisco Video Infrastructure with their existing CUCM IP Telephony Infrastructure to send and receive calls to and from CUCM.

    3 DOWNTIME

    As such no downtime is required for this change

    4 IMPACT

    No Impact on the current Video Infrastructure is expected.

    5 ASSUMPTION

    It is assumed, all the configurations on CUCM will be made as per the following Requirement and Design.

  • Page 6 of 20

    Dimension Data | Implementation Document

    6 REQUIREMENT

    The following requirement of CTS is identified.

    Calls from IP phones registered to CUCM should be allowed to call to Video Bridges.

    o The IP Phone users will add the prefix 883 to the Video bridge number while dialing. o The Calls from CUCM will be allowed to only reach numbers starting with 85 on VCS.

    This is our prefix for the Video bridges.

    Calls from VCS to IP Phones registered to CUCM.

    o Video Devices would dial 883 followed by IP Phone DN number to call IP Phones. o As of now, no restriction for calls to CUCM from VCS is required.

    All transformations would be done only in VCS.

  • Page 7 of 20

    Dimension Data | Implementation Document

    7 DESIGN

    The following Design would be implemented in CTS.

    DATA USB LAN 1 LAN 1 LAN 1 LAN 1 ALM HDD

    PWR

    Cisco TelePresenceVideo Communication Server

    Cisco VCS Control

    India

    MPLS CLOUDCUCM Cluster

    Primary

    SIP TRUNK

    CUCM MEPZ

    CUCM SRI

    Secondary/Redundant

    SIP TRUNK

    7.1 VCS:

    Two neighbour zones will be configured from VCS, with CTS-MEPZ CUCM as primary neighbour

    and CTS-SRI CUCM as Secondary neighbour.

    The search rule will be prioritized to use CUCM-MEPZ as primary.

    7.1.1 Call flow:

    Outgoing calls to CUCM

    Video Endpoints will dial 883XXXXXX to call IP phones.

    XXXXXX is the IP Phone DN.

    VCS will strip 883 in its search rule and forwards the call to CUCM.

    Incoming calls from CUCM

    VCS should receive the Call with prefix 883 and the Video Bridge Number. Prefix should be removed by VCS.

    VCS will route the calls with their existing Search rules.

  • Page 8 of 20

    Dimension Data | Implementation Document

    7.2 CUCM:

    CUCM will create two SIP trunks to VCS-India. This can be transferred to VCS-US in future if

    required.

    7.2.1 Call flow:

    Outgoing calls to VCS

    IP Phone users will dial 88385XXXXX to call Video Bridge.

    85XXXXX is the Video Bridge Number. The calls from IP phones will be restricted only to Video Bridges and not to endpoints directly.

    Incoming Calls from VCS

    Calls from VCS would reach CUCM with just the DN number dailed.

    The Prefix 883 will be stripped by VCS.

  • Page 9 of 20

    Dimension Data | Implementation Document

    8 CONFIGURATION:

    8.1 VCS

    Follow the below configuration to configure a Neighbour zone to CUCM from VCS.

    8.1.1 Creating Zones in VCS.

    1. Go to

    2. Click on New

    3. Enter the following Details Name : CUCM-SIP TRUNK - MEPZ

    Type : Neighbor

    H323 Mode : Off

    SIP Transport : TCP

    SIP Port : 5060

    Accept Proxied Registrations : Deny

    Peer 1 Address : IP address of CUCM-MEPZ

    Zone Profile : Cisco Unified Communications manager

  • Page 10 of 20

    Dimension Data | Implementation Document

    4. Click Create Zone

    5. Follow similar procedure for another Neighbor zone to CUCM-SIP TRUNK SRI.

    Name : CUCM-SIP TRUNK - SRI

    Type : Neighbor

    H323 Mode : Off

    SIP Transport : TCP

    SIP Port : 5060

    Accept Proxied Registrations : Deny

    Peer 1 Address : IP address of CUCM-SRI

    Zone Profile : Cisco Unified Communications manager

    Check the Zone status and it should be as below

  • Page 11 of 20

    Dimension Data | Implementation Document

    8.1.2 Configuring VCS Search Rules.

    The following search rule will also transform the destination alias to the format understood by CUCM, before placing the call on to the neighbour zone. For Example: 883441234 or [email protected] will be converted to [email protected].

    1. Go to

    2. Enter the following Details

    Rule Name : Calls to CUCM

    Priority : 105 [Need to freeze this referring the VCS]

    Source : Any

    Mode : Alias pattern match

    Pattern type : Regex

    Pattern string : (883)(\d*)(@video.cognizant.com)?

    Pattern behavior : Replace

    Replace string : \2@

    On Successful match : Continue

    Target : Select the Zone CUCM-SIP TRUNK - MEPZ

    3. Click Create Search Rule

  • Page 12 of 20

    Dimension Data | Implementation Document

    4. Create another search rule with following details.

    Rule Name : Calls to CUCM

    Priority : 106 [Need to freeze this referring the VCS]

    Source : Any

    Mode : Alias pattern match

    Pattern type : Regex

    Pattern string : (883)(\d*)(@video.cognizant.com)?

    Pattern behavior : Replace

    Replace string : \2@

    On Successful match : Continue

    Target : Select the Zone CUCM-SIP TRUNK - SRI

  • Page 13 of 20

    Dimension Data | Implementation Document

    8.1.3 Configuring VCS Transformation:

    The following Transform has to be created in VCS. This transform will truncate the @ from the received called number from CUCM. Transform: Priority : 1 Pattern Type : Regex Pattern String : (883)(85\d*)@10.40.40.63(.*)

    *85 in the above string is to restrict the calls only to Video Bridges *Replace \d* with \d{n}, if number of digits followed by 85 has to be limited. *IP address in the above string should be replaced with IP address of VCS

    Pattern Behavior : Replace Replace String : \2

  • Page 14 of 20

    Dimension Data | Implementation Document

    8.2 CUCM

    Follow the below Procedure to configure SIP Trunk in CUCM.

    8.2.1 Configure the SIP Profile

    1. On CUCM, go to Device > Device Settings > SIP Profile

    2. Click Copy the double sheets of paper icon in the table.

  • Page 15 of 20

    Dimension Data | Implementation Document

  • Page 16 of 20

    Dimension Data | Implementation Document

    8.2.2 Configure the SIP Trunk security profile

    1. On CUCM, go to System > Security > SIP Trunk Security profile.

    2. Click Add New.

    Configure the fields as follows:

    3. Click Save.

  • Page 17 of 20

    Dimension Data | Implementation Document

    8.2.3 Configure the SIP Trunk device

    1. On CUCM, go to Device > Trunk.

    2. Click Add New.

    Device Protocol displays SIP.

    If asked for a Trunk Service Type, select None(Default).

    3. Configure the Device Information fields as follows:

    4. Configure the Call Routing Information > Inbound Calls fields as follows:

    5. Configure the Call Routing Information > Outbound Calls fields as follows:

  • Page 18 of 20

    Dimension Data | Implementation Document

    Configure the SIP Information fields as follows:

    6. Click Save and Reset

  • Page 19 of 20

    Dimension Data | Implementation Document

    8.2.4 Allow numeric dialing from Cisco phones to Cisco VCS

    1. On CUCM, go to Call Routing > Route/Hunt > Route Pattern.

    2. Click Add New.

    3. Configure a Route Pattern, so that any calls with Prefix 883 should be routed to the SIP trunk

    to VCS.

  • Page 20 of 20

    Dimension Data | Implementation Document

    9 TEST PLAN

    Follow the below procedure to Check whether the Calls to CUCM & Vice-versa works properly. Test the below call scenarios and check the call status in VCS and CUCM.

    UAT VCS-CUCM CALLS

    TEST SCENARIO

    To From

    449555 461281 414049

    [email protected] 609160020

    [email protected] 609117132

    449555 N.A N.A N.A

    461281 N.A N.A N.A

    414049 N.A N.A N.A

    [email protected] N.A N.A

    [email protected] N.A N.A

    10 ROLL BACK

    Follow the below procedure to Roll back the change in case of any issues.

    1. Go to

    2. Select the 2 search rules created in step 8.1.2 and Disable it.