Design Guide for Cisco Unity Connection Release 10.x
Video Greetings in Cisco Unity Connection
Downloads: This chapterpdf (PDF - 183.0KB) The complete bookPDF (PDF - 3.53MB) | Feedback

Video Greetings in Cisco Unity Connection

Table Of Contents

Video Greetings in Cisco Unity Connection

Video Greeting's platform as of the 10.0 release of Unity Connection

Blanking Files

Video Greetings Operation

Cisco VCS Interoperability

Video Greetings as Call Handlers


Video Greetings in Cisco Unity Connection


Cisco Unity Connection 10.0(1) and later releases have enhanced the current greeting experience by providing the video greetings to the caller. Unity Connection allows subscribers to record a Video Greeting for both identified users and outside callers. Presenting Video Greetings for outside callers is enabled through the subscribed user's Class of Service.

Unity Connection 10.0(1) supports the following video-enabled endpoints:

Cisco 99XX and 89XX Series Endpoints

Cisco 79XX and 69XX Series Endpoints with Cisco Unified Video Advantage

Cisco Jabber for Windows 9.2(3) or later

Cisco Jabber for Mac 9.2(1) or later

Cisco Jabber for iPad 9.3(21386) or later

See the following sections:

Video Greeting's platform as of the 10.0 release of Unity Connection

Blanking Files

Video Greetings Operation

Cisco VCS Interoperability

Video Greetings as Call Handlers

Video Greeting's platform as of the 10.0 release of Unity Connection

Unity Connection's Video Greeting's feature is currently only supported using the 7 vCPU OVA. Smaller OVAs will be tested and the Design Guide will be updated as the testing completes. Each server in Unity Connection HA pair can support up to 20 concurrent video calls for a total of 40 video calls within a Unity Connection HA pair. For single Connection server, 35 concurrent video calls are supported.

MediaSense must also be deployed using the larger 7vCPU OVA. Smaller OVAs will be tested and the Design Guide will be updated as the testing completes. This MediaSense instance must be a single server and cannot be part of a MediaSense cluster and MediaSense must be dedicated for Unity Connection's Video Greeting's feature. Only one Cisco Unity Connection HA pair or single server can be integrated per MediaSense server.

Video Greetings is supported in an Active-Active co-located HA deployment and also supported in an Active-Standby HA deployment over the WAN. Video Greetings is not supported in an Active-Active HA deployment over the WAN.

MediaSense must be co-located with Cisco Unity Connection with 1gbps connectivity between the servers and less than 10ms Round Trip Time (RTT) latency. The Unity Connection team will be profiling the bandwidth and higher latency links in later releases to allow for a wider range of deployment options

Blanking Files

Due to differing behavior between some video devices, the use of a `blanking' file is recommended for the Video Greetings feature. The blanking file fills in the video RTP stream when Unity Connection and MediaSense would otherwise not be sending video. Without the blanking file, users may either experience video window closing on the device or the last received video frame freezing on the screen.

There is a sample blanking file located at http://www.ciscounitytools.com/Applications/MediaSense/VideoBlankingFiles/

This file needs to be uploaded to the MediaSense that Unity Connection is integrated with the following information:

Title: CiscoUnityConnectionLogo.mp4

Description: <Enter a brief description>

Filename: CiscoUnityConnectionLogo.mp4

The blanking file must be an MP4 video file with a resolution 640x360 (360p) using H.264 codec at 30 frames per second. The blanking file needs to include an empty or null audio track. MediaSense requires an audio track; however silence is preferred for the blanking file so it does not distract the user during the use of the Video Greetings feature.

Due to the Cisco Unified Communications Manager Regions settings in the "Video Greetings Operation" section, the Video Greeting's blanking files should be recorded at an average or constant bit rate of 600kbps to allow the administrator to better calculate the bandwidth requirements of the Video Greetings deployment.

Video Greetings Operation

Video Greetings are only supported using SIP trunk integrations and in the 10.0 release, Unity Connection supports the use of 360p (640x360) Video Greetings. MediaSense and Unity Connection allows the recording of Video Greetings up to 1080p (1920x1080) , however this offers limited compatibility across the video-enabled phone portfolio and is not a supported configuration as MediaSense does not support transcoding video to reduce the resolution for non-1080p video devices. To restrict Video Greetings to 360p, Unity Connection leverages the use of Communications Manager's Region configurations. The Unity Connection SIP Trunks need to be put in a region that has the following relationship settings with all other regions containing video-enabled devices that might call Unity Connection and expect Video Greetings:

Audio Codec Preference List: (Default or Administrator's Preference)

Maximum Audio Bit Rate: 64 kbps

Maximum Session Bit Rate for Video Calls: 600kbps

Maximum Session Bit Rate for Immersive Video Calls: 600kbps

For an Active-Standby HA deployment over a WAN connection, use the following Region settings for the SIP trunk to the Unity Connection server that is NOT co-located with MediaSense. This will disable Video Greetings when using the secondary node. Audio-only greetings will continue to fuction.

Audio Codec Preference List: (Default or Administrator's Preference)

Maximum Audio Bit Rate: 64 kbps

Maximum Session Bit Rate for Video Calls: Select "None"

Maximum Session Bit Rate for Immersive Video Calls: Select "None"

These settings will ensure maximum compatibility across the Cisco video-enabled phone portfolio and provide the best possible experience for using Video .Greetings.

When recording a Video Greeting, the audio and video RTP streams are both sent directly to Unity Connection. Unity Connection saves the audio RTP stream locally as an audio-only version of the Video Greeting and forks the audio and video RTP streams to MediaSense for recording. For playback, if the device is video-enabled, Unity Connection will instruct MediaSense to stream the Video Greeting to Unity Connection to be forked to the device. If MediaSense is not available or unable to playback the Video Greetings or if the device calling Unity Connection is not video-enabled, then Unity Connection will play the audio-only portion of the Video Greeting that it recorded. The audio-only greeting is the audio track from the Video Greeting. It is possible to have different greetings for audio-only callers and video-enabled callers.

Cisco VCS Interoperability

The Unity Connection team has not tested calling through a VCS or calling from devices registered to a VCS and as such, these call flows are not supported. The Design Guide will be updated as this testing is completed and support is verified. At current, the Unity Connection team is aware of an issue with certain devices registered to a VCS where video is not negotiated and audio-only greetings will be played or recorded. While not currently supported, CUCM registered devices calling through a VCS are typically able to play and record new Video Greetings.

Video Greetings as Call Handlers

In the 10.0 release only user accounts can be Video Greetings enabled and all forms of call handlers remain audio-only. Using user accounts as call handlers is the only way to enable a video enabled call handler. User accounts have many similar options to call handlers and can user input to route calls to other user greetings or to transfer outside of the Unity Connection system. Each branch in a user-based video-enabled call handler represents one user account. a. For example, if a root video greeting is built with 3 options and each of those 3 options have 2 sub-options, a total of 10 video-enabled user accounts would be required to facilitate that call handler structure.