This topic describes the requirements for video greetings in Cisco Unity Connection and the network topology.
The requirements for video greetings are as follows:
- Video endpoints with SIP; for example, Cisco Unified IP Phone 9971 or Cisco Jabber for Desktop
- Video-enabled endpoints with SCCP; for example, Cisco Unified IP Phone 8945
- Cisco Unity Connection version 10.0(1)
- Cisco MediaSense version 10.0(1)
- Cisco Unified Communications Manager version 8.5(1) and later
Cisco Unity Connection must be integrated via SIP.
SIP = Session Initiation Protocol; SCCP = Skinny Client Control Protocol.
Video greetings are available as of Cisco Unity Connection version 10.0(1). Before you can record or play video greetings, you need to integrate video endpoints, Cisco Unified Communications Manager, and Cisco MediaSense into one video-enabled voice-messaging solution. The figure shows an overview of the supported version combinations to configure the video greetings feature.
The supported version combinations are determined by testing. Although other combinations may provide acceptable results to customers, Cisco must test or approve these combinations before they are supported.
For more information go to the Video Greetings in Cisco Unity Connection 10.x document at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/design/guide/10xcucdgx/10xcucdg070.html#65685.
The overview shows the integration and protocols that are used for video greetings. Only user accounts can be enabled for video greetings.
The figure shows the integration requirements for Cisco Unity Connection video greetings.
If your voice-messaging solution is integrated with SCCP, you need to reconfigure the integration to use SIP. Cisco Unity Connection and Cisco MediaSense can both run as standalone or in a cluster.
Note that the Cisco Unity Connection video greeting feature needs a dedicated Cisco MediaSense server. The Cisco MediaSense server cannot be shared for any other Cisco MediaSense features.
Only user accounts can be enabled for video greetings, and all forms of call handlers remain audio-only. The only way to enable a video-enabled call handler is to use user accounts as call handlers. User accounts have many options that are similar to call handlers and can use input to route calls to other user greetings or to transfer outside of the Cisco Unity Connection system. Each branch in a user-based video-enabled call handler represents one user account. For example, if a root video greeting is built with three options and each of those three options have two suboptions, a total of 10 video-enabled user accounts would be required to facilitate that call handler structure.