Thursday 2 June 2016

Module 3 4 5 - CUCM VCS

This part of the lab shows you how to configure the Cisco Telepresence Video Communication Server (VCS) version X8.1 and Cisco Unified Communications Manager version 10.x to interwork via a SIP trunk.

Configuring CUCM to enable calls between devices registered on CUCM

The configuration of CUCM and phones registered to CUCM consists of the following steps:
  1. Configuring the SIP Profile for VCS (Already exists if using 9.x +)
  2. Configuring the Region with appropriate bitrates for Video calls
  3. Configuring a SIP profile for devices registered to CUCM
  4. Adding the device to the list of supported devices by CUCM
  5. Configuring the device directory number
  6. Configure the device to get its configuration from CUCM

Configuring the Region with an appropriate bit rate for Video
  1. Access CUCM: https://10.10.10.15/ccmadmin
Username: admin
Password: C1sc0123
  1. Go to System > Region Information > Region
  2. Click Find

  1. Select Default Region
  2. Set Maximum Session Bitrate for Video Calls to 6000kbps
  3. Click Save & Click OK at popup
  4. Click Apply Config & Click OK at popup
  5. Click Reset & Restart at  popup. Click close at popup


Adding EX60 to CUCM

Register EX60 on the left side of your pod to CUCM
To register EX60, you will need to enter the MAC address. To find EX60 MAC address
Press top left hand corner of Touch panel
Select Settings
Select System Information
Find IPv4 address of EX60: 10.10.10.x
Access EX60 web UI at http://10.10.10.x
Username: admin
Password: <none>
Copy MAC address from Home menu into notepad. Delete all colons “:” so MAC is only digits & numbers


  1. Access CUCM: https://10.10.10.15/ccmadmin
Username: admin
Password: C1sc0123

  1. On the top menu, select Device -> Phone

Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-01 at 1.19.31 AM.png

  1. Select Add New

Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-01 at 1.22.49 AM.png

  1. From the dropdown list, Select Phone Type -> Cisco TelePresence EX60, and press Next.

Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-01 at 1.23.59 AM.png

  1. Enter or select the following:

    MAC Address: MAC Address of your POD’s EX60
    Description: Bill Zeng EX60
    Device Pool: DP_Lab
Phone Button Template: Standard Cisco TelePresence EX60
Owner User ID: bzeng
Device Security Profile: Cisco TelePresence EX60 – Standard SIP Non-Secure Profile
SIP Profile: Standard SIP Profile for TelePresence Endpoint
Admin Username: admin
Admin Password:
Web Access: Enabled
Click Save and Apply Config

  1. Click Line [1] – Add a new DN

Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-01 at 5.35.33 AM.png
   
Enter or select the following:   

Directory Number: 1001
Route Partition: PT_Local
Line 1 on Device
Display (Caller ID): Bill Zeng
ASCII Display (Caller ID): Bill Zeng
Click Save and Apply Config
Click Reset -> Reset
Click Close

  1. On the EX60 Touch Control, press Settings -> Administrator
Username: admin
Password: <none>
  1. Goto Provisioning –> Provisioning Wizard -> Start

  1. Select Cisco UCM -> Register

If prompted, enter following:
External Manager: 10.10.10.15
Register
Click OK

Calls can now be made between devices registered to CUCM.
Remote Desktop into workstation 2 @10.10.10.102
Username:student2
Password: C1sc0123
Verify by calling from Jabber to EX60.

If your POD’s EX60 prompt to perform System Upgrade. Accept the Software Upgrade by pressing Upgrade Now on the Touch Control.


VCS Control configuration
Configuration of the VCS Control, to enable calls to be made with devices registered to the VCS Control, can be broken down into four steps.
  1. Setup NTP Server
  2. Setup DNS Server
  3. Setup SIP domain of the VCS Control
  4. Create a transform, to ensure the dialed number has a domain added to it.

Setup NTP Server
Configure the NTP Server setting on the VCS
  1. Login into VCS Control, Navigate to http://10.10.10.65  and login
    1. Username: admin
    2. Password: C1sc0123
  2. Go to System > Time
  3. Configure NTP Server 1: 10.10.10.5
  4. Authentication: Disabled
  5. Click Save
  6. Verify NTP synchronization

Setup DNS Server Setting on VCS Control
  1. Go to System > DNS
  2. Configure System Host Name: vcs
  3. Configure Domain Name: uclab.com
  4. Configure Address 1: 10.10.10.5
  5. Click Save


Setup the SIP domain of the VCS Control
  1. Go to Configuration >  Domains
  2. Click NEW
  3. Configure Domain Name: uclab.com
  4. Click Save

Create Transform to ensure the dialed string has the domain component added.
  1. Go to Configuration > Dial Plan > Transforms
  2. Click NEW
  1. Configure the following fields as follows
    1. Description: Add domain where none exists
    2. Pattern Type: Regex (Regular Expression)
    3. Pattern String: ([^@]*)
    4. Pattern Behavior: Replace
    5. Pattern String: \1@uclab.com
    6. State: Enabled
  2. Click Create Transform


Confirm/Create a search rule to search Local Zone
  1. Go to Configuration > Dial Plan > Search Rules
  2. Click New
  3. Configure the following fields as follows
    1. Rule Name: Local Zone Match
    2. Description: Local Zone Alias Match
    3. Priority: 50
    4. Protocol: Any
    5. Source: Any
    6. Mode: Any Alias
    7. On Successful Match: Continue
    8. Target: LocalZone
    9. State: Enabled
  4. Click Create search rule


Registering endpoints to the VCS Control
Register EX60 on right side of your pod as H323 endpoint
  1. Press the setup icon on the touch panel
  2. Press Administrator
Username: admin
Password: <none>
  1. Select H323. Enter the following details
    1. H.323 Number: 2001
    2. H.323 Id: 2001@uclab.com
    3. Gatekeeper discovery: Manual
    4. Gatekeeper Address: 10.10.10.65
    5. Authentication Mode: Off
    6. Click Save
  2. Press Call Details
    1. Default Protocol: H323
    2. Click Save
  3. Access EX60 web UI at http://10.10.10.x
    1. Username: admin
    2. Password: <none>
  4. Go to Network Services
    1. Ensure H323 is Enabled

Confirming Endpoint Registration to VCS
  1. Access back to VCS
  2. Go to Status > Registrations >By device

You should see your device registered to VCS

Enabling Endpoints on VCS to call endpoints on CUCM. Configuring the trunk from VCS to CUCM

Configuring CUCM can be broken down into 3 steps:

  1. Configure the SIP trunk security profile
  2. Configure the SIP trunk device
  3. Configure the Cluster FQDN
Configure the SIP Trunk Security Profile

  1. Go to System > Security > SIP Trunk Security Profile
  2. Add New
  3. Name: Non Secure SIP Trunk Profile - VCS
  4. Device Security Mode: Non Secure
  5. Check box – Accept unsolicited notification
  6. Check box – Accept replaces header
  7. Click Save
  8. Click Reset – to reset the trunk

Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-02 at 5.19.46 AM.png

Creating SIP Trunk to VCS

Step 1    On the top menu, select Device -> Trunk

Step 2    Click Add New to create SIP Trunk to VCS, select the following:
    Trunk Type: SIP Trunk
Device Protocol: SIP
Trunk Service Type: None (Default)
Click Next

Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-01 at 5.46.47 AM.png
   
Step 3    Enter or select the following:
   
Device Information   
Device Name: VCS_Trunk
    Description: VCS_Trunk
    Device Pool: DP_Lab
    Call Classification: OnNet
Check SRTP Allowed
Check Run On All Active Unified CM Nodes

Inbound Calls
Calling Search Space: CSS_All_Access
Check Redirecting Diversion Header Deliver - Inbound

Outbound Calls
Calling and Connected Party Info Format: Deliver URI and DN in connected party, if available
   
SIP Information
    Destination Address: 10.10.10.65
    Destination Port: 5060
    SIP Trunk Security Profile: Non Secure SIP Trunk Profile - VCS
SIP Profile: Standard SIP Profile for Cisco VCS
DTMF Signaling Method: RFC 2833
Normalization Script: vcs-interop


Enabling calls to be placed from VCS to CUCM.
Configuring the VCS to setup the Trunk from VCS to CUCM

The configuration of the VCS has 3 steps.
  1. Create a neighbor zone that contains the details of  CUCM
  2. Create a search rule to route calls to that zone
  3. Create a transform, to convert <alias>@<IP address of CUCM> to number <number>@uclab.com

Creating a neighbor zone to CUCM
  1. On VCS, Go to Configuration > Zones > Zones
  2. Click New
  1. Configure the following fields:
    1. Name: CUCM Neighbor
    2. Type: Neighbor
    3. Hop Count: 15
    4. H.323 Mode: Off
    5. SIP Mode: On
    6. SIP Port: 5060
    7. Transport: TCP
    8. Accept Proxied Registrations: Deny
    9. Media Encryption Mode: Auto
    10. Peer 1 Address: cucm-pub-v10.uclab.com
    11. Zone Profile: Cisco Unified Communications Manager 8.6.1 or later
  2. Click Create Zone
  3. Confirm Zone is Reachable.

Create a search rule to route calls to the CUCM neighbor Zone
  1. Go to Configuration > Dial Plan > Search Rules
  2. Click New

  1. Configure the following fields as follows
    1. Rule Name: Route to CUCM
    2. Description: Route all calls not found to CUCM
    3. Priority: 100
    4. Protocol: Any
    5. Source: Any
    6. Mode: Any Alias
    7. On Successful Match: Stop
    8. Target: CUCM Neighbor
    9. State: Enabled

  1. Click Create Search Rule

Create a transform that converts number@<ipaddr of CUCM> to number@uclab.com

  1. Go to VCS Configuration > Dial Plan > Transforms
  2. Click NEW
  3. Configure the following fields as follows
    1. Prioirty: 3
    2. Description: VCS IP to domain
    3. Pattern Type: Regex (Regular Expression)
    4. Pattern String: (.*)@10.10.10.(15|65)((:|;).*)?
    5. Pattern Behavior: Replace
    6. Pattern String: \1@uclab.com\3
    7. State: Enabled
  1. Click Create Transform

Creating SIP Route Pattern on CUCM
   
  1. On the top menu, select Call Routing -> SIP Route Pattern


Description: MacSSD:Users:wihew:Desktop:Screen Shot 2014-03-01 at 3.08.50 AM.png

  1. Click Add New to add new SIP Route Pattern

  1. Enter or select the following:

    Pattern Usage: Domain Routing
    IPV4 Pattern: *.*
Description: Domain Routing to VCS
Route Partition: PT_Local
SIP Trunk/Route List: VCS_Trunk
Click Save

Description: C:\Users\wihew\AppData\Local\Temp\vmware-wihew\VMwareDnD\d3522cb4\Screen Shot 2014-03-01 at 2.43.07 PM.png

Creating Route Pattern on CUCM
  1. On the top menu, select Call Routing -> Route Hunt -> Route Pattern
  2. Add New
  3. Enter or select the following:
Route Pattern: 2XXX
Route Partition: PT_Local
Description: To VCS H323
Route List: VCS_Trunk
Call Classification: OnNet

Calls can now be placed between VCS and CUCM.
Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)