Download ppt - Cisco Unity Connection SRSV 9.1(1)

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1Cisco Confidential© 2012 Cisco and/or its affiliates. All rights reserved. 1

Cisco Unity Connection SRSV9.1(1)

TOI for Cisco Unity Connection SRSV

EDCS-1202103

Dec 7, 2012


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.

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 3

• 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



Cisco Unity Connection SRSV

Cisco Unity Connection SRSV

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


Fully-Featured Survivable Branch with Centralized & Automatic Provisioning as well as users voicemail management

Without Cisco Unity Connection SRSV

A

CUCM

Headquarters

Administrativenightmare

A

CUCM

Cisco Unity Connection

Headquarters

• No voicemail synchronization: Voicemails are distributed across Central and branches with Cisco Unity Express(CUE) solution.

• Manual provisioning of branches

With Cisco Unity Connection SRSV

Cisco Unity Connection

Remote sites

Remote sites


• 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


• 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



• Central site1. Cisco Unified Call Manager

2. Cisco Unity Connection

• Branch site1. Cisco Unified SRST [Cisco Unified Survivable Remote Site

Telephony]

2. CUCME-SRST (Cisco Unified Call Manager Express with SRST)

3. Cisco Unity Connection SRSV






HTTPS

HTTPS

1

2

3


• 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”

1


• 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

1


1


Mai

n se

rvic

e re

spon

sibl

e fo

r S

RS

V f

eatu

res

Mai

n se

rvic

e re

spon

sibl

e fo

r S

RS

V f

eatu

res

1


• 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.

1


• Open Branch Administrator Page

• Go to Networking -> Central Server Configuration

• Add the FQDN of the Central Cisco Unity Connection

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 CUC SRSV :

admin: run cuc dbquery unitydirdb EXECUTE PROCEDURE csp_ConfigurationModify(pFullName='System.SRSV.AcceptSrsvSelfSignedCertificates', pValue='1');

1


1


• Perform SRSV Telephony Integration similar to Cisco Unity Connection

1


• Enable all Micro traces for CUCESync and VMREST for CUC SRSV (Branch)

• Probable test connectivity failures:

1. Certificate failure/ Mismatch:

a. Certificate not present : Check if CUC certificate has been installed correctly, if not install the same

b. Hostname mismatch in certificate: Check if CN in certificate from CUC matches with SRSV Central Server CUC Address, if not fix the mismatch

c. FQDN not configured in DNS: Configure the hostname for both on DNS

2. Connectivity Failure

a. Check network connectivity between Central and Branch (ping, firewall issues etc)

b. Tomcat service is running on both Central CUC and SRSV

1


HTTPS

HTTPS

1

2

3


• 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

2


• Enable all Micro traces for CUCESync , VMREST and CUCAfor Central CUC

1. For certificate issues troubleshooting remains same as for SRSV

2. Test Connectivity Failure

a. “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

b. “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

c. “Server Address is Invalid”: Make sure that the FQDN/Hostname address of the branch entered on the Edit Branch page is correct

2


HTTPS

HTTPS

1

2

3


• Enable Branch Provisioning Synchronization task and configure schedule

3


• Go to Branch Management -> Branches and select any Branch and click Sync Provisioning button

3


Central Unity Connection

A

CUCM

Headquarters

Branch 1

SRSVHTTPS REST request to branch

OK response from branch

Sends file to branch in form of TAR file chunk

Branch confirms for receiving TAR filechunk

1.

2.

3.

4.

5. Provisioning started

1. Central Unity Connection sends request for provisioning

2. Branch is ready for provisioning

3. Central Unity Connection sends the provisioning data in form of TAR Chunk.

4. Branch confirms for receipt of provisioning data TAR chunk and verifies the Sanity on last chunk.

5. Provisioning started at Branch

6. Provisioning completion notification sent to Central unity connection

7. Central Unity Connection acknowledges Branch provisioning

6. Provisioning Completion

7. Central acknowledges

* SRSV Branch is created and user assigned to branch


• Provisioning status of branches can be checked from Branch Sync Results page under Branch Management

3


• Snapshot of successful provisioning cycle

3

• Snapshot of failed provisioning cycle


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.)


• Enable all Micro traces for CUCESync , VMREST for 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 (CuLicMgrSvr diags) 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.

3


• Enable Branch Voicemail Polling task and configure schedule

3


• Go to Branch Management -> Branches and select any Branch and click Voicemail Upload button

3


A

CUCM

Headquarters

Branch 1

SRSV

Central Unity Connection

HTTPS REST request to branch

Branch confirms new message available

Central request to publish message information

Branch sends the message details

1.

2.

3.

4.5.

6. Branch sends WAV file

1. Central Unity Connection checks for new voice mails for Branch

2. Branch confirms new message available

3. Central Unity Connection requests branch to provide message information

4. Branch sends the message details

5. Central Unity Connection fetches the new message as WAV file

6. Branch responses with WAV file using CML interface

7. Central confirms for message delivery and asks branch to delete them

8. Branch deletes the messages

Central starts fetching messages

Central confirms receipt and to delete from branch

Branch acknowledges

7.

8.


• Voice mail sync. status of branches can be checked from Branch Sync Results page under Branch Management

3


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.)

3

• Snapshot of successful voice mail upload cycle


• Enable all Micro traces for CUCESync , VMREST for 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 NDR code

3


• From System Distribution Lists Select Distribution list and enable Replicate to SRSV Branches

3


• 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)


• 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 + SRSVAll Basic User Features + SRSV

Included in CUWL Standard and ProIncluded in CUWL Standard and Pro


• 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


• Backup & Restore are supported at Branch

• Supported tools are: COBRAS, DRS



• The following features implementation currently are in progress

• Localization (will be delivered subsequent SU's)

• Scalability up to 50 branches (backlog US)



Dev Wiki

http://wikicentral.cisco.com/display/UNITYTRANS/How+to+configure+CME-as-SRST+to+act+as+a+call+agent+during+WAN+outage+and+its+integration+with+Cisco+Unity+Connection+Express

http://wikicentral.cisco.com/display/UNITYTRANS/How+to+install+UMG+and+configure+it+for+E-SRST

http://wikicentral.cisco.com/display/UNITYTRANS/How+to+configure+SRST+on+router

SRE virtualization: http://www.cisco.com/en/US/prod/collateral/ps10265/ps11273/installation_guide_c07-640002.html#wp9000269

Troubleshooting Wiki:

http://zed.cisco.com/confluence/display/UCET/Cisco+Unity+Connection#CiscoUnityConnection-CUCSRSV

Cisco UC SRSV DOCEDCS-1150554- Cisco UC SRSV FFS Document

EDCS-1149984 –Cisco UC SRSV FDS Document




The following limited Admin interface available at Branch side

•Users

• Administrator- Used to create New Administrative users for accessing Branch Admin interface

• User- The User Provisioned from Central CUC to corresponding Branch will visible. No option to add new user at Branch

•Templates

• Call Handler Templates- This is used to add new Call Handler templates, which can be used for adding a System Call Handler

•Call Management

• System Call Handler - New System Call Handler Can be added and Greeting can be recorded at Branch

• Directory Handler- Default Directory handler only available, which can be editable at Branch. Undeletable. No option for adding new Directory handler


• Connectivity

• Central Server Configuration- Used to add Central Cisco Unity Connection Server

• System Settings

• Schedules

• Conversations (Configure Remote Port status Monitor).

• Enterprise Parameters

• Plugins( User can download RTMT )

• Telephony Integration

• Phone System(Only Default available and can be editable. No option to add New)

• Port Group

• Port(Only 8 ports can be added)


• Telephony Integration

• Phone System(Only Default available and can be editable. No option to add New)

• Port Group

• Port(Only 8 ports can be added)


• Tools-> Custom Keypad Mapping

• Keypad mapping for Branch users can be changed from tools > custom keypad mapping at Branch

• Changes in the default keys will be reflected for all the branch users


Thank you.