© 2013 Cisco System Inc. All rights reserved Cisco Confidential 1 © 2013 Cisco System Inc. All rights reserved. 1 EDCS-1279430 August 06, 2013 Unity Connection

© 2013 Cisco System Inc. All rights reserved Cisco Confidential 1Cisco Confidential© 2013 Cisco System Inc. All rights reserved. 1

EDCS-1279430

August 06, 2013

Unity Connection Video Greetings Feature TOI

10.0(1)

© 2013 Cisco System Inc. All rights reserved Cisco Confidential 2

Notice

The information in this presentation is provided under Non-Disclosure agreement and should be treated as Cisco

Confidential. Under no circumstances is this information to be shared further without the express consent of Cisco.

Any roadmap item is subject to change at the sole discretion of Cisco, and Cisco will have no liability for delay in the delivery or failure to deliver any of the products or features set forth in

this document.


Introduction

What’s new

How it works

Network Topology

Flow Diagram

System Requirements

Supported Endpoints

Configuration

Limitations

Troubleshooting Tips

© 2013 Cisco System Inc. All rights reserved Cisco Confidential 4Cisco Confidential. 4


Cisco Unity Connection 10.0(1) (Connection) is a feature-rich voice messaging platform which now provides the immersive experience of Video Greetings.

Users will now be able to record and playback Video Greetings via the Telephony User Interface(TUI).


• Users can record video greetings through the TUI (touchtone conversation)

• Users can configure, play and re-record a Video for every type of available greetings : Standard, Alternate, Internal, Busy, Holiday and Closed (*except Error greeting)

• Callers (Internal or External) can now see recorded Video greetings of the called users when calling from a CUCM integrated video enabled Cisco endpoint**.

• In a Video Call, an image will be streamed towards the end point whenever Connection is playing any Audio only content.

• During the recording of greetings, an Image will be streamed towards the endpoint and a PIP (Picture-in-Picture) window is displayed to the caller.


• Connection integrates with Cisco MediaSense(MS), a media recording platform, which records video greetings for the user(s).

• Connection nodes and MediaSense should reside within the specified limit of latency.*

• Connection supports Video greetings only over SIP Integration with CUCM. SCCP integration is not supported.

• Connection Supports following codecs in a Video call:

For Video: H.264 (Base Profile: 420014)

For Audio: G.711ulaw

• The default value of Differentiated Services Code Point (DSCP) for the RTP (Video) connection is 46. Restart the Connection Conversation Manager for the changes to take effect.


• For a Video call to be established, Video capabilities of the EndPoint should be enabled on Cisco Unified Communications Manager.

• For a Video call to be established, Connection performs a series of checks to confirm if the user(s) are capable and configured for Video capabilities or not.

• Connection communicates over http(s) (Control Protocol) with Cisco MediaSense to start and stop the record/playback of video greetings with http(s) timeout of 4 sec. In case of timeout or failure during mid call, Connection downgrades the call to audio.

• With Connection acting as RTP(Streaming Protocol) Proxy, Video/Audio packets of video file are streamed from End point to MS or vice versa.

• Audio of all greetings (either from Video Greeting or Audio only greeting) is always stored on and accessible from the Connection server.

• Video Greetings, the Audio and Video combined content, is only stored on MediaSense server.


• Connection keeps the audio copy of the Video Greeting in its file system to be played in audio-only calls .

• In a Video call, when connection plays an Audio-only stream to the end user, an image is streamed from MS to provide Video experience.

• The image to be streamed will be configurable at MS. Please refer MS TOI for details.

• When User records a Video Recording, both Audio and Video Greeting of the user gets modified i.e. the Video Recording is saved as the User’s Video Greeting and the Audio part of the Video Recording is saved as User’s Audio Greeting . "My Personal Recording" on both 'Callers See' and 'Callers Hear' section for this greeting on User's Greeting page of CUCA and CPCA will be checked.

• When User records an Audio Greeting, his current audio greeting will be replaced with the new Audio Recording. 'My Personal Recording' will be checked on 'Callers Hear' Section and 'My Personal Recording' will be unchecked on 'Callers See' Section of Greetings page on CUCA and CPCA.


• In an RNA call if user is configured to record a message then the call will be downgraded to Audio once Video Greeting is streamed completely. This is done to optimize resources .

• In order to delete the orphan Videos from MS, a SysAgent task “Clean Orphan Video Recordings” has been created in Connection. This task sends the delete request to MS for deletion of the Video files and removes the orphan Video Session IDs from Database.

• Once the call gets established as Audio, the respective call can’t be upgraded to Video.

• Only Attempt Sign-In, Sub Sign-In , Attempt Forward conversations are Video capable.




HTTPS

RTPSIP/SCCP

Call manager Cisco Unity Connection (10.0)

Node A

Node B

Cisco MediaSense Primary

Control Path

Data PathVideo Phones

CUVAJabber Client

Video End Points

RTP

SIP


Successful Sign-In - JSESSIONID is populated on CUC and MS. All requests carry JSESSION ID and are entertained by

MS

signIn (username/password)

Connection checks if Video call should be established or not*

New Incoming Call from Endpoint via CUCM

2000 (capabilities, dialogGuid)

Start (capabilities,)

INVITE with Video in SDP (Early Offer)

180 Ringing

100 Trying

200 Ok with SDP [Video Send]

ACK

2000 (JSessionID)

Connection is ready to receive RTP

2000

Updatemediacapabilities(capabilities, requestid, dialoguid)

getMediaCapabilities (KeepAlive)

2000 (capabilities)

System level KeepAlive

Messages sent periodically

System level KeepAlive

Messages sent periodically

EndPoint/CUCM Connection MediaSense


Video Playback during the Video call

2000

startSessionPlayback,(sessionid, requestid, dialoguid)

RTP (Video Content)

Video Playback

Video Playback

During the playback of Audio Content, Connection requests MS to play Image.

Image Playback

Image Playback

2000

startMediaPlayback,(mediatitle,requestid, dialoguid)

RTP ( Image Content)

RTP (Audio Content)

2000

stopPlayback,(targetrequestid,requesttid, dialoguid)On Video Playback/End call

2000

KeepAlive( RequestId, dialoguid)

Call level KeepAlive sent

periodically during the call

Call level KeepAlive sent

periodically during the call

EndPoint/CUCM

Connection MediaSense

Playback_Stopped(sessionid,targetrequestid, dialoguid)

2000

Events received from MS.

Events received from MS.

On playback Completion, MS sends notification to

Connection*


User presses relevant key for Video Record

INVITE with Video in SDP (For Video SendRecv)

180 Ringing

100 Trying

200 Ok with SDP

ACK

2000 (SessionID)

startRecord,(requestid, dialoguid)

User presses relevant key to stop Record

INFO200 OK

2000 stopRecord,(targetrequestid, requestid, dialoguid)

RTP ( Image Content)

Video file Name shared by MS in

response .

Video file Name shared by MS in

response .

Multiple INFO msgs sent to

collect Iframe from EP.

Multiple INFO msgs sent to

collect Iframe from EP.

RTP ( Video Content)

[Re-Invite] is sent with Video as SendOnly.

Hang-Up

2000 end(requestid, dialoguid)

EndPoint/CUCM

Connection MediaSense

To enable PIP window on

Phone Screen

To enable PIP window on

Phone Screen

To disable PIP window on

Phone Screen

To disable PIP window on

Phone ScreenImage Playback is stopped.

BYE

200 OK


• Size – Cisco Unity Connection 20,000 users OVA

• vCPU – 7

• RAM – 8GB

• HD – 2 X 300 GB, 2 X 500 GB

• Ports – 250

• CPU (MHz) –

• For Xeon 5600 and 7500 processors - minimum of 2.53 GHz each (10.12 GHz reserved)

• For Xeon E7 processors - minimum of 2.4 GHz each (9.6 GHz reserved)

• x


Please refer to ‘Deployment: Primary/Secondary node 7 vCPU’ in the following link:

http://ccbu-wiki.cisco.com/display/ORA/VM+Templates

Supported Version of MediaSense: 10.0

Note:

Unity Connection Video Greeting feature needs a dedicated MediaSense server. The MS server cannot be shared for any other MS features like VoH, Call recording etc

Currently only Single MS Node is supported.


Connection will support Video over 69XX, 79XX series phones with CUVA, 89XX and 99XX series phones and Jabber.

Following is the list of EPs and their firmware on which Video has been tested so far:

•9951, 9971 beginning with firmware Sip9951.9-3-2-10

•8945 series beginning with firmware: SCCP 9.3.4.9

•7945 (version: SCCP4.5.9-3-1SR2-1S or higher )with CUVA (version 2.3.1.0 or higher)

•6921, 6941, 6945

•Jabber Client (version 9.2.1 or higher) on MAC

•Jabber Client (version 9.2.2 or higher) on Windows

Testing with End-Points is still ongoing. The list will be updated .



• Create SIP Trunk at CUCM

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/integration/guide/cucm_sip/cucintcucmsip060.pdf

• Create a voice mail pilot and voice mail profile.

For Voice Mail Pilot: Go to Advance Features-> VoiceMail->Voice Mail Pilot. Enter the pilot number (Here, Please use the same extension as the route pattern added for the respective SIP trunk)

For Voice Mail Profile: Go to Advance Features->VoiceMail->Voice Mail Profile. Use the pilot number created above.

• For all the users for whom Video Greeting is to be enabled:

Enable the Video Capabilities on the phone: Device -> Phone -> Select your phone -> Enable “Cisco Camera” and “video capabilities”.

Enter the Voice Mail Profile on the phone: Device->Phone->Directory Settings-> Select the SIP Voicemail profile created above. Save and Restart the phone.

NOTE:- Supported Versions of CUCM: 8.5 onwards*


Bulk-Edit Tool and BAT tool can be used to configure users for video capabilities.

Step 1 Step 2 Step 3


Pre Requisites

•Certificate Management:

Add the MS certificates in the Connection tomcat-trust store. MS root certificate is mandatory certificate to be uploaded on Connection for establishing Video call.

If self-signed certs are not used then at least root certificate is needed for third party signed certificate.

Any one out of self-signed or third party certificate can be used at a time. This option is configurable on VideoServices page.

The Certificate can be uploaded on Connection OS Administration page under Security>Certificate Management tab.

•The login credentials of MS used on Connection CUCA page are same as the credentials of API User on MS. Please refer the MS TOI for more details on the same.


Video Service represents the details of the Video server with which Unity Connection will be integrated to perform Video related Operations. To Configure it:

Go to Video -> Video Services -> Add New

Note: Only one Video Service can be added in this release.


• Please fill all the mandatory fields on the ‘Video Service Page’.

• Click on Test Button and verify that everything is working fine.

• Save the page.

Connection cluster

independent limit.*

Connection cluster

independent limit.*


• Go to users -> Edit -> Video services Accounts -> Add New

• Add the Video Server and Check “Map Video Service” box. Save the page.


• Enable Video under COS and Save.

• Assign this COS to user.


Test buttons are added on CUCA in order to perform quick tests to check the video configuration.

Test buttons/Icons are available at:

- On Video Services Page

- On Video Services Accounts Page


When user hits the Test button on Video Services page, following set of events take place:

1. Checks whether Connection is able to ping the MediaSense Server.

2. If the MediaSense is UP and running, then “signIn” API is sent to authenticate username and password of MediaSense.

3. It also validates the Self-signed/Third-party certificates used with MediaSense Server.

4. After the authentication is successful, “getMediaCapibilities” API is sent to display the codecs supported in Video calls with MediaSense.

Note: In case a chain of Certificates is configured on MediaSense, the test button will show Success in case, any of the certificate from the chain is added in the tomcat-trust on Connection.



When user hits the Test Icon of Video Services Account Page :

Along with the checks executed in Test button on Video Services Page, following additional checks take place:

1. Checks whether Video Service is enabled on Cisco Unity Connection or not.

2. Checks whether “Allow Users to Playback and Record Video Greetings” or “Allow Outside Callers" option is enabled in the User's Class of Service page.



• Unity Connection Video Greeting feature needs a dedicated MediaSense server. The MS server cannot be shared for any other MS features like VoH, Call recording etc.

• Video feature is not supported for the calls on the SCCP trunk between Call Manager (CUCM) and CUC (Connection).

• Video greeting feature is not supported for IPv6 or dual mode. Hence, IPv6 feature and Video feature should not be configured on the CUC at the same time.

• Video Greetings can be recorded for Connection Users only. Greetings for Call Handlers are still Audio-only.

• Users can not record video greeting through Media Master(i.e. Computer, Telephony Record and Playback (TRaP))


• Max 25* concurrent calls are supported. All the other calls are established as Audio

• VUI is not supported in a Video call.

• Outgoing Calls from Connection are established as Audio.

• For SIP Phones: PIP window which appears on phone screen during recording will not be turned off after recording ends due to the limitation of end point.

• The Primary DNS response time should be high otherwise, the user experience may get detoriated since the connection resolves the FQDN of Media Sense when it signs in.


• While resuming a Hold video-call, following behavior can be experienced by the users:

In case Audio content was getting played, then blank screen will be observed for the duration of that prompt.

In case Video content was getting played, then blank screen and no audio will be observed for the duration of that content.

• During Image Playback if image-playback requests towards MS fail then call will remain Video although user may experience blank screen for the duration of the Audio playbacks.

• When MS goes down and comes up after some time then there could be a duration of 15 sec in which calls established will be audio.


• RTP streams towards MS server don’t support sRTP which could pose Man in The Middle (MiTM) threat.

• Notifications received from MS server are plain HTTP. A Man In The Middle could disrupt ongoing media session with MS, by knowing session information captured towards this port.

• Unity Connection will raise an alarm (as mentioned in Video Alarms slide) in case too many notifications requests (HTTP) are received . Alert raised will have the IP and port of the source. Please check the authenticity of the requests.



• Video Trace Level Information

• Links to Annotated traces

• Tips for Issues found during Quick Tests

• Tips for issues in establishing a Video call.

• Tips for issues during Video Recording

• Tips for issues during Video Playback

• Tips for issues related to Video Quality

• Video Alerts

• Video Performance Counters


Micro Traces Description Level

CDE Conversation State Machine traces 0,10-17,20,21

ConvSub Conversation Call Progress traces 1-5

MiuIO Input/output traces from MIU 11-13, 25,27

Miu Sip/Miu Sip Stack SIP Protocol Messages ALL

MiuMethods/MiuCall Diags for the Call processing in media Module

ALL

Mixer Diags of Audio/Video Channels for data transmission

01-04

Video Video Processing and messages exchanged with VideoServer

10,11

Log files to be collected : diag_CuCsMgr* and diag_CuMixer* from RTMT

Enable following traces to troubleshoot Video related issues:


Annotated traces for Video Greetings can be found at the following link:

This link contains the important trace information to look for during a Video call

•http://wikicentral.cisco.com/display/UNITYTRANS/Annotated+Traces+for+Video+Messaging

MS APIs and their respective response codes are discussed in brief at the following link

•http://wikicentral.cisco.com/display/UNITYTRANS/MS+APIs+with+response+Codes


You may receive the following error messages on the Edit Video service page of Cisco Unity Connection Administration(CUCA) when you test the connectivity of Connection with Cisco MediaSense(MS) using test button:

•"Video Service cannot be contacted by pinging”. Make sure that the FQDN/IP address of the Cisco MS (Video Server) is correct . If yes then check for the network connectivity between problem between Connection and MS

•“Video server is not responding on the port <port number>." Make sure that the port number specified on the Edit Video Service page is correct.

•“Username or password is incorrect.” Make sure that the username and password of Cisco MS are correct

•“Failure in validating the video server certificates.” Make sure that the hostname of the Cisco MS mentioned in the certificate installed on the Cisco Unity Connection is correct.


Along with the error messages received on Video Services page, You may receive following error messages when you check the configuration of the Video Services Account page of a User through test button:

•“The Enable Video settings are disabled for this user in the Edit Class of Service page”. Make sure that you select the 'Enable Video settings' in the 'Edit Class of Service' page.

• “Video service is disabled.” Make sure that you have selected the 'Enabled' option in the 'Edit Video Service' page.


Please check if:

•Cisco Camera and Video Capabilities are enabled for the device in Cisco Unified Communications Manager.

•"Connection Conversation Manager” is restarted after updating Video Service page.

•Cisco MediaSense is up and running using test button on Edit Video Service page

•Video Service Account is created for the user(s) in question.

•“Map Video Service” is enabled in Video Service Account for the user

•In Case of Connection User, check whether “Allow Users to Playback and Record Video Greetings” is enabled in Class of Service for both the calling and called user.

•In case of Outside Caller, check whether “Allow Outside Caller “is enabled in Class of Service for the user.


• Maximum concurrent video calls are reached . Please look for the following trace in diag_CuCsMgr* logs: Video,10,Alert::Exceeded Maximum ConCurrent Calls Limit Active[25]:Max[25]

• Please check if MS root certificate is uploaded on Connection.

• Please check the video channels usage via ‘taccli’ command.


Issue: Output of Test button is successful but Video call is not getting established.

Steps to follow:

Please ensure that MS root certificate is uploaded on Connection.

Cause:

Test button works with any certificate in the chain (Root-Intermediate-Leaf) uploaded on Connection.

However to establish video calls, MS Root certificate is mandatory to be uploaded on Connection


Call gets downgraded to audio with the prompt “Video Services are not available, using Audio for the duration of call”

Steps to follow:

•Please check if Cisco MS is UP and running using test button on Video Services page and Video Services Account Page.

•Call gets downgraded in case any error response* is received from MS in response to the startRecord() or stopRecord() request. Please look for the respective error response in logs.

•User can proceed with the Audio call or establish the call again to re-record the Video Greeting.

•In case the issue is persistent , please collect the appropriate Connection Conversation Manager (CuCsMgr) logs at the mentioned trace levels using RTMT.


Issue 1: Call gets downgraded to audio with the prompt “Video Services are not available, using Audio for the duration of call”

Steps to follow:

•Please check if Cisco MS is up and running using test button on Video Services page and on Video Service Accounts Page.

•Call gets downgraded in case any error response* is received from MS in response to the startSessionPlayback() or stopPlayback() request. Please check for the respective error response in the logs

•Please proceed with the audio call or establish a new call for complete Video experience.

•In case the issue is persistent , please collect the appropriate Connection Conversation Manager (CuCsMgr) logs at the mentioned trace levels.


Issue 2:Issue 2: Playback hangs in between

Steps to follow:

•Press # button on phone to end the playback and continue with the call.

•Playback could hang due to missing "Playback_Stopped" event from MS. Please check the conversation logs for this event.

•Please report in case the issue is persistent with the CuCsMgr diags at the requested trace levels.

Issue 3: Audio Greeting is getting played with the image

Steps:

• Please check "Callers See" section on Greetings page and ensure that 'My Personal Greeting' is checked.

•If following trace is present in logs, please re-record your video greeting: Video Greeting can't be played either b'coz VideoFileName isn't available.


Issue: During playback of Video Greeting, quality of video is poor.

Steps:

•Please check and reduce the value of attribute “Interval in Seconds for sending KeyFrame Requests to End Point during recording” under Advanced>Telephony.

•In case the issue still persists, please collect diag*CuCsMgr* and diag*CuMixer* at the mentioned trace level.

•Capture wireshark traces at Connection and CUCM during the call.


Existing ‘TACCLI’ Interface has been enhanced for Video channels and fork groups added.

To check the statistics of Video Channels and Video forkgroups, run command “taccli” from root account and provide the input as per the displayed menu.

Only Following menu items have been updated to display the statistics for Video channels and forkgroups :

1 Display statistics for all channels

2 Display statistics for a channel

3 Display statistics for all forkgroups

4 Display forkgroup statistics

5 Display mixer status


Following new Alerts are added on Connection:

•E_MIU_MS_AUTHENTICATION_FAILURE - This alert will be generated if the ‘signIn’ request towards MS fails (e.g. due to incorrect username/password)

•E_MIU_MS_CONNECTOR_KEEPALIVE_TIMEOUT – This alert will be generated when keepalive requests towards MS fail due to timeout. It will be generated when MS is down.

•EVT_MAXIMUM_NUM_OF_VIDEO_NOTIFICATION_THREADS_EXCEEDED- This alert will be generated if number of Video Notification threads exceed its maximum limit. Connection will ignore all the subsequent notifications in case the limit is reached.*

• An INFO message “Connection to media sense succeeded” is also generated once MediaSense Serve is active and connected.

These alerts can be checked on RTMT tool or ‘CiscoSyslog’ file at the path /var/log/active/syslog on Connection.


New Counters have been added for tracking video related performance data. These counters can be found under the title “CUC Video ” on RTMT tool.

Please see the following link for all the counters added:

http://wikicentral.cisco.com/display/UNITYTRANS/Video+Performance+Counters


• TODO


All the Video documents are available at the following location:

//sea-dmz/temp/Video

•System Administration Guide> 10xcucsag100

This document gives the administrator a quick start with video greeting feature discussing about the need, configuration and prechecks of Video Greetings.

•User Guide for Cisco Unity Connection Phone Interface> Managing Your Personal Greetings

This document explains the end user to record and play video greetings using telephone user Interface.

•Troubleshooting Guide> 10xcuctsg140

This document discusses the error messages and troubleshooting steps that the administrator can perform while configuring video greetings.

•System Administration Guide > 10xcucsag130

This document explains how to allow users to playback video greetings.


Thank you.

Documents

© 2013 Cisco System Inc. All rights reserved Cisco Confidential 1 © 2013 Cisco System Inc. All rights reserved. 1 EDCS-1279430 August 06, 2013 Unity Connection