Cisco Unity Connection SRSV 9.1(1)

1. Cisco Unity Connection SRSV9.1(1) TOI for Cisco Unity Connection SRSV EDCS-1202103 Dec 7, 2012

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.

3. Agenda • Cisco Unity Connection SRSV • Introduction • Benefits with SRSV • Features • Limitations • Topology • Working with Cisco Unity Connection SRSV • Connection SRSV set up configuration • Central Connection setup configuration • Provisioning and Voicemail management • CUC SRSV : Auto Attendant • CUC SRSV : Licensing • CUC SRSV : DRS (Restore & Backup) • Future Plans • References

4. Introduction to Cisco Unity Connection SRSV

5. Introduction Cisco Unity connection Survivable Remote Site Voicemail (SRSV) provides a cost-effective solution for supporting redundant voicemail service for organization's remote sites such as branch offices or small sites Cisco Unity Connection SRSV

6. Headquarters CUCM A A Cisco Unity Connection Administrative nightmare Headquarters CUCM With Cisco Unity Connection SRSV SRSV Benefits Without Cisco Unity Connection SRSV Cisco Unity Connection Remote sites • No voicemail synchronization: Voicemails are distributed across Central and branches with Cisco Unity Express(CUE) solution. • Manual provisioning of branches Remote sites Fully-Featured Survivable Branch with Centralized & Automatic Provisioning as well as users voicemail management

7. Features SRSV is a licensed feature Supports Automatic Synchronization of User Profile Information, directory configuration with Central Cisco Unity Connection over secure channel (HTTPS) Supports Automatic Synchronization of Voicemail Messages from remote sites (branch) Supports Survivable Basic Automated-Attendant Service Cisco Unity Connection SRSV works seamlessly works with standalone as well as Active-Active Central Unity Connection cluster Supports up to 200 users per branch. Each Central Unity Connection cluster can support up to 10 branches Currently certified with SRE 900/910, UCS-E or with any Unity Connection certified Hardware

8. Limitations w.r.t. Unity Connection • Other voicemail interfaces supported on the Central Cisco Unity Connection such as IMAP, SIB, VUI and Web based voicemail are not supported • Compose, forward and reply to voice messages is not supported • No Message Waiting Indicator (MWI) in survivable mode • Interview handlers are not supported • IPv6 not supported • Distribution Lists: • Voice messages sent to Distribution lists in survivable mode get sent to the members only after the WAN recovers • Private distribution list is not supported

9. Topology

10. Topology : Cisco Unity Connection SRSV Solution Components • Central site • Cisco Unified Call Manager • Cisco Unity Connection • Branch site • Cisco Unified SRST [Cisco Unified Survivable Remote Site Telephony] • CUCME-SRST (Cisco Unified Call Manager Express with SRST) • Cisco Unity Connection SRSV

11. Topology 1: with SRST

12. Topology 2: CUCME-as-SRST

13. Topology 3: Load balancing at Branch

14. Configuring Cisco Unity Connection SRSV

15. Configuring Cisco Unity Connection SRSV 1 2 HTTPS 3 HTTPS

16. 1 CUC SRSV setup configuration (Contd..) Install a Standalone Cisco Unity Connection 9.1(1) or use an existing Cisco Unity Connection 9.1(1) Standalone setup Convert the above Unity Connection to branch using the following CLI on the admin interface : “utils cuc activate CUSRSV”

17. 1 CUCSRSV setup configuration (Contd..) • It will take approximately ~60 to 90 minutes to convert Unity Connection to Branch depending on the hardware used and previous data on Unity Connection • Once Unity Connection is successfully converted to Connection SRSV, it cannot be rollback to Unity Connection and all the previous data and configurations will be lost • Branch upgrade is supported from Cisco Unity Connection SRSV 9.1(1) onwards ** In case of failure of conversion please collect /var/log/active/cuce/ mode-switch.log

18. 1 Cisco Unity Connection SRSV Admin page

19. Cisco Unity Connection SRSV Services (Contd..) 1 Main service responsible for SRSV features

20. 1 Cisco Unity Connection SRSV Service At Central : Synchronization of Voicemails and Provisioning between Central and Branch Offices. At Branch Responsible for provisioning of branch, using data sent by the Central Unity Connection.

21. Configuration of Central CUC Server at Cisco Unity Connection SRSV (Step 1) 1 Open Branch Administrator Page Go to Networking -> Central Server Configuration Add the FQDN of the Central Cisco Unity Connection

22. Configuration of Central CUC Server at Cisco Unity Connection SRSV (Step 2) 1 • Install Central Unity Connection certificates • By default self signed certificates are not allowed • To enable self signed certificates following commands on both Central and CUCSRSV : admin: run cucdbqueryunitydirdb EXECUTE PROCEDURE csp_ConfigurationModify(pFullName='System.SRSV.AcceptSrsvSelfSignedCertificates', pValue='1');

23. 1 Connectivity test between Central and Branch (Step 3)

24. 1 CUCSRSV setup configuration (Step 4) Perform SRSV Telephony Integration similar to Cisco Unity Connection

25. 1 Troubleshooting issues at SRSV • Enable all Micro traces for CUCESync and VMRESTfor CUCSRSV (Branch) • Probable test connectivity failures: • Certificate failure/ Mismatch: • Certificate not present : Check if CUC certificate has been installed correctly, if not install the same • Hostname mismatch in certificate: Check if CN in certificate from CUC matches with SRSV Central Server CUC Address, if not fix the mismatch • FQDN not configured in DNS: Configure the hostname for both on DNS • 2. Connectivity Failure • Check network connectivity between Central and Branch (ping, firewall issues etc) • Tomcat service is running on both Central CUC and SRSV

26. Configuration of CUCSRSV at Central CUC 1 2 HTTPS 3 HTTPS

27. 2 Configuration of CUCSRSV at Central CUC Go to Branch Management -> Branches and select Add New to create a new Branch Give Branch details such as display name, Server address(FQDN), admin credentials, SMTP domain name, PAT port number, Partition

28. 2 Troubleshooting issues at Central CUC • Enable all Micro traces for CUCESync , VMREST and CUCAfor Central CUC • For certificate issues troubleshooting remains same as for SRSV • Test Connectivity Failure • “Authentication failed. Incorrect Username and Password.”: Make sure that the username and password of the branch entered on the Edit Branch page are correct. Tomcat service is running on both Central CUC and SRSV • “Branch is unreachable”: Make sure that the PAT port number specified on the Edit Branch page is correct and NAT/PAT translation is enabled on router • “Server Address is Invalid”: Make sure that the FQDN/Hostname address of the branch entered on the Edit Branch page is correct

29. Sync up between Central CUC and Cisco Unity Connection SRSV 1 2 HTTPS 3 HTTPS

30. Central Cisco Unity Connection – Automatic provisioning of Branch 3 Enable Branch Provisioning Synchronization task and configure schedule

31. Central Cisco Unity Connection – Manual provisioning of Branch 3 Go to Branch Management -> Branches and select any Branch and click Sync Provisioning button

32. Cisco Unity Connection SRSV: Provisioning Flow SRSV Headquarters CUCM A Branch 1 1. HTTPS REST request to branch 2. OK response from branch Sends file to branch in form of TAR file chunk 5. Provisioning started Branch confirms for receiving TAR filechunk Central Unity Connection 3. 4. 6. Provisioning Completion * SRSV Branch is created and user assigned to branch 7. Central acknowledges Central Unity Connection sends request for provisioning Branch is ready for provisioning Central Unity Connection sends the provisioning data in form of TAR Chunk. Branch confirms for receipt of provisioning data TAR chunk and verifies the Sanity on last chunk. Provisioning started at Branch Provisioning completion notification sent to Central unity connection Central Unity Connection acknowledges Branch provisioning

33. 3 Troubleshooting issues in Provisioning Provisioning status of branches can be checked from Branch Sync Results page under Branch Management

34. 3 Troubleshooting issues in Provisioning • Snapshot of failed provisioning cycle Snapshot of successful provisioning cycle

35. Possible error codes for failed provisioning 1. Unable to start provisioning. Provisioning start REST API towards branch does not return 200 OK. 2. Unable to update authentication token for the branch. Central is not able to update the token in its DB. 3. Maximum wait time for provisioning response is reached. Branch is not able to send the provisioning notification in the pre-defined time to central. 4. Maximum retries for branch provisioning are exhausted. Central has tried all the number of retries for provisioning and did not succeed. 5. Provisioning at the branch side encountered some problem. Branch returns provisoining error in the notification to the central. 6. Unable to reach the branch. Central is not able to connect to the branch. 7. Operation was abnormally ended. An operation (provisioning or voice mail upload) was abruptly ended (service stop, system crash etc.)

36. 3 Troubleshooting issues in Provisioning • Enable all Micro traces for CUCESync , VMRESTfor Central CUC • Status of Provisioning Remains In Progress or it is not working (traces info in notes) a. Check the network connectivity of the central Cisco Unity Connection with the branch. b. Ensure branch username and password is not expired by login into the branch admin page. c. Check whether the VMREST and Connection Branch Sync Service is active on both central Connection and branch. d. Check License (CuLicMgrSvrdiags) and Certificate status e. Check for any exceptions/failure present in traces for CuCESync service. f. If automatic provisioning is not working at scheduled time, then check whether the Branch Provisioning synchronization task is enabled or not.

37. 3 Central Cisco Unity Connection setup- Automatic VM upload from Branch Enable Branch Voicemail Polling task and configure schedule

38. Central Cisco Unity Connection setup- Manual VM upload from Branch 3 Go to Branch Management -> Branches and select any Branch and click Voicemail Upload button

39. Cisco Unity Connection SRSV : VM upload Flow SRSV Headquarters CUCM A Branch 1 1. HTTPS REST request to branch 2. Branch confirms new message available Central request to publish message information Branch sends the message details 3. 4. 5. Central starts fetching messages 6. Branch sends WAV file Central Unity Connection 7. Central confirms receipt and to delete from branch 8. Branch acknowledges Central Unity Connection checks for new voice mails for Branch Branch confirms new message available Central Unity Connection requests branch to provide message information Branch sends the message details Central Unity Connection fetches the new message as WAV file Branch responses with WAV file using CML interface Central confirms for message delivery and asks branch to delete them Branch deletes the messages

40. 3 Troubleshooting issues in Voicemail Upload Voice mail sync. status of branches can be checked from Branch Sync Results page under Branch Management

41. 3 Troubleshooting issues in Voice mail upload • Snapshot of successful voice mail upload cycle Possible error codes for failed Voice mail upload 1. Unable to fetch voice mail details from branch. Central is not able to fetch all voice mail summary from the branch. 2. There is no voice mail to upload at the branch. Branch responds with no data in voice mail summary request from central 3. Unable to reach the branch. Central is not able to connect to the branch. 4. Operation was abnormally ended. An operation (provisioning or voice mail upload) was abruptly ended (service stop, system crash etc.)

42. 3 Troubleshooting issues in Voicemail upload • Enable all Micro traces for CUCESync , VMRESTfor Central CUC • Status of voicemail upload Remains In Progress or it is not working a. Check the network connectivity of the central Cisco Unity Connection with the branch. b. Ensure branch username and password is not expired by login into the branch admin page. c. Check whether the VMREST and Connection Branch Sync Service is active on both central Connection and branch. d. Check Certificate status (notes section below) e. If automatic voicemail upload is not working at scheduled time, then check whether the VM upload synchronization task is enabled or not. f. If NDR is created on the central Connection but the same email is delivered on the branch, check the NDRcode

43. Central Cisco Unity Connection – Replicate Distribution List 3 From System Distribution Lists Select Distribution list and enable Replicate to SRSV Branches

44. CUCSRSV : Auto Attendant • During WAN outage, CUC-SRSV provides mechanism for recording a message when a user’s phone is busy or the user does not answer • It will also provide access to retrieve user’s voicemails by dialing voicemail pilot number • Directory look up of local SRSV user’s is supported **Traces of CuCsMgr logs needs to be collected for troubleshooting Auto attendant issues (Please refer notes section below)

45. CUCSRSV: Licensing • Only Central Cisco Unity Connection server needs to be added to the ELM server, • “Enhanced Messaging Users” is a new tag added at Central Cisco Unity Connection for the users of Branch All Basic User Features + SRSV Included in CUWL Standard and Pro

46. CUC SRSV : Licensing (Contd..) • Provisioning synchronization will not work if Central Cisco Unity Connection server is in expired state • Voice mail functionality at branch remains unaffected • In Demo and Violation mode Provisioning synchronization works as expected ** If the central Connection moves to the Violation state, make sure that the number of licenses for the Connection features, such as SpeechView and Connection SRSV, does not exceed its maximum limit

47. CUCSRSV: DRS (Restore & Backup) Backup & Restore are supported at Branch Supported tools are: COBRAS, DRS

48. Future Plans

49. Future Plans • The following features implementation currently are in progress • Localization (will be delivered subsequent SU's) • Scalability up to 50 branches (backlog US)

50. References