Click here to load reader

Cisco Unity Connection SRSV 9.1(1)

  • View
    60

  • Download
    4

Embed Size (px)

DESCRIPTION

Cisco Unity Connection SRSV 9.1(1). TOI for Cisco Unity Connection SRSV EDCS-1202103. Dec 7, 2012. Notice - PowerPoint PPT Presentation

Text of Cisco Unity Connection SRSV 9.1(1)

SRSVCisco Confidential
*
EDCS-1202103
Cisco Confidential
*
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.
*
*
Cisco Confidential
Connection SRSV set up configuration
Central Connection setup configuration
Provisioning and Voicemail management
CUC SRSV : Auto Attendant
Future Plans
Cisco Confidential
*
*
Cisco Confidential
*
Cisco Confidential
Without Cisco Unity Connection SRSV
No voicemail synchronization: Voicemails are distributed across Central and branches with Cisco Unity Express(CUE) solution.
Manual provisioning of branches
Cisco Unity Connection
Automates the synchronization of voice mail messages
In previous solution with Cisco Unity Express and SRST, Administrator has to manually configure Unity Express on all individual branches. During WAN outage, when all the phones move to Survival mode, all the Voicemails were getting stored at Unity Express locally. When WAN connectivity was restored, phones re-register with the Central
 
 
 
 
During WAN outage, the voicemails which are locally stored at CUC SRSV, gets synced automatically with Central Unity Connection , when the network connectivity is restored. Now all the voicemails of the user is now available at a central location.
© 2012 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
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.
*
Cisco Confidential
*
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
*
Cisco Confidential
*
*
Cisco Confidential
CUCME-SRST (Cisco Unified Call Manager Express with SRST)
Cisco Unity Connection SRSV
Cisco Confidential
*
*
Cisco Confidential
*
*
Cisco Confidential
*
*
Cisco Confidential
*
*
Cisco Confidential
Creation and configuring Branch
Configuring Central Unity Connection
*
Cisco Confidential
*
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”
Cisco Confidential
*
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
Cisco Confidential
1
*
Cisco Confidential
1
Connection Branch Sync service is new service implemented for all SRSV features that includes:
Provisioning of Branches
*
Cisco Confidential
At Branch
Responsible for provisioning of branch, using data sent by the Central Unity Connection.
1
CUCESYNC running at Branch will be responsible for the provisioning of the branch using data sent by the Central Unity Connection over REST over HTTPS interface
*
Cisco Confidential
Add the FQDN of the Central Cisco Unity Connection
1
*
Cisco Confidential
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');
Cisco Confidential
1
*
Cisco Confidential
1
Cisco Confidential
*
Enable all Micro traces for CUCESync and VMREST for CUC SRSV (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
1
20:38:52.256 |6495,,,CUCESync,12,Thread=Provisioning-5; class=CuBranchSyncX509TrustManager;checkServerTrusted() - Self-signed certificate found.
20:38:52.256 |6495,,,CUCESync,12,Thread=Provisioning-5; class=CuBranchSyncX509TrustManager;checkServerTrusted() - CERTIFICATE_SELF_SIGNED
Cisco Confidential
Creation and configuring Branch
Configuring Central Unity Connection
*
Cisco Confidential
*
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
PAT port Number-PAT port number is that the central connection server uses to communicate with the branch. This port number specifies the port on the public side of that NAT, which further maps to port 443 for communicating with the branch
After creation of branch, perform connectivity test and ensure that status is shown as Active
Once the connectivity is established, check if the CuCESync service has also become Active
Branch Certificate installation needs to be done on Central CUC
*
Cisco Confidential
*
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
2
Cisco Confidential
Creation and configuring Branch
Configuring Central Unity Connection
*
Cisco Confidential
3
*
Cisco Confidential
*
Go to Branch Management -> Branches and select any Branch and click Sync Provisioning button
3
*
Cisco Confidential
*
OK response from branch
Sends file to branch in form of TAR file chunk
Branch confirms for receiving TAR filechunk
1.
2.
3.
4.
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
Central Unity Connection acknowledges Branch provisioning
6. Provisioning Completion
7. Central acknowledges
A
CUCM
Headquarters
Cisco Confidential
*
Provisioning status of branches can be checked from Branch Sync Results page under Branch Management
3
Snapshot showing status of all the provisioning cycles for a particular branch.
Individual status of each cycle can be checked by clicking on End Date column.
Result of Provisioning :
Success: Provisioning is successfully completed
Failed: Failure in provisioning cycle
*
Cisco Confidential
3
Snapshot of failed provisioning cycle
Snapshot showing status of all the provisioning cycles for a particular branch.
*
Cisco Confidential
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.
*
Cisco Confidential
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
Collect logs for CUCESync service and tomcat from both Central and branch
If automatic provisioning is not working at scheduled time, then provisioning will be scheduled next cycle
Provisioning stuck for long time:
14:47:11.557 |28168,,,CUCESync,11,Thread=Thread-0; class=CuBranchSyncProvisioningMonitor;DID NOT GET A RESPONSE FROM BRANCH IN TIME, MARKING PROVISINOING AS FAILED.
14:47:11.557 |28168,,,-1,-1,Provisioning completion notification is not received for branch[name= Srev-vm4, address= srev-vm4.cisco.com] in 30 minutes.
14:47:11.557 |GenAlarm: AlarmName = EvtBranchProvisioningFailedMaxWait, subFac = UCEVNTKeyParam = , severity = 3, AlarmMsg = %1 : Srev-vm4
%2 : srev-vm4.cisco.com
%3 : 30
AppID : CUCESync
15:22:39.934 |12562,,,CuLicMgrSvr,2,Thread=Thread-1 Exit ViolatedLicSvrState::licEventExpired
20:55:04.724 |13562,,,CUCESync,12,Thread=Provisioning-5; class=CuBranchSyncX509TrustManager;hostname = 10.78.171.1; allowSelfSignedCertificate = true; allowCertificateErrors = false
20:55:04.732 |13562,,,CUCESync,10,Thread=Provisioning-5; class=CuBranchSyncRequestProcessor;error in processing for::0655f50e-7042-4271-a435-deda6d86d1df type::3000 error::Connection refused
20:55:04.734 |13562,,,CUCESync,10,Thread=Provisioning-5; class=CuBranchSyncRequestProcessor;error in processing for::0655f50e-7042-4271-a435-deda6d86d1df type::3000 error::Connection refused
20:55:04.737 |13562,,,CUCESync,10,Thread=Provisioning-5; class=CuBranchSyncRequestProcessor;error in processing for::0655f50e-7042-4271-a435-deda6d86d1df type::3000 error::Connection refused
20:55:04.737 |GenAlarm: AlarmName = EvtBranchNotReachable, subFac = UCEVNTKeyParam = , severity = 3, AlarmMsg = %1 : ucbu-aricent-vm53.cisco.com
%2 : 10.78.171.1
AppID : CUCESync
Cisco Confidential
3
*
Cisco Confidential
*
Go to Branch Management -> Branches and select any Branch and click Voicemail Upload button
3
*
Cisco Confidential
*
Central request to publish message information
Branch sends the message details
1.
2.
3.
4.
5.
6.
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
Central starts fetching messages
Branch acknowledges
Cisco Confidential
*
Voice mail sync. status of branches can be checked from Branch Sync Results page under Branch Management
3
Snapshot showing status of all the voice mail sync. cycles for a particular branch.
Individual status of each cycle can be checked by clicking on End Date column.
Result of Voice mail upload :
In Progress: Voice mail upload is still ongoing
Success: Voice mail upload is successfully completed
Failed: Failure in Voice mail upload cycle
*
Cisco Confidential
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
Snapshot showing status of all the voice mail upload cycles from a particular branch.
*
Cisco Confidential
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
Collect logs for CUCESync service and tomcat from both Central and branch
Check for any exceptions/failure present in traces for CuCESync service, if still the voicemail is not visible then please check whether the provisioning between central and branch is proper, if not then re-sync the branch using manual provisioning
If automatic Voicemail upload is not working at scheduled time, then voicemail upload will be scheduled next cycle
1. SSL handshake failed due to self signed certificate
20:38:52.256 |6495,,,CUCESync,12,Thread=Provisioning-5; class=CuBranchSyncX509TrustManager;checkServerTrusted() - Self-signed certificate found.
20:38:52.256 |6495,,,CUCESync,12,Thread=Provisioning-5; class=CuBranchSyncX509TrustManager;checkServerTrusted() - CERTIFICATE_SELF_SIGNED
20:50:51.082 |13540,,,CUCESync,10,Thread=VoicemailUpload-33; class=CuBranchSyncRequestProcessor;error in processing for::0655f50e-7042-4271-a435-deda6d86d1df type::1000 error::Connection refused
20:50:51.240 |GenAlarm: AlarmName = EvtBranchNotReachable, subFac = UCEVNTKeyParam = , severity = 3, AlarmMsg = %1 : ucbu-aricent-vm53.cisco.com
%2 : 10.78.171.1
AppID : CUCESync
Cisco Confidential
*
From System Distribution Lists Select Distribution list and enable Replicate to SRSV Branches
3
*
Cisco Confidential
*
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)
CUC SRSV will emulate Unity Connection auto attendant behavior, it will match default Unity Connection call routing rules and plays recorded auto attendant greetings
Branch User is Unable to Login through Telephony User Interface (TUI) in Survivable mode
If a branch user is unable to login through TUI, consider the following:
• Make sure that the PIN entered on the central Connection is synchronized with the branch through provisioning, if not then manual re-sync the Branch
• If the branch user is logging in for the first time through TUI, make sure that the user has set the PIN at the central Connection and provisioning is done successfully
CuCsMgr Diags:
*
Cisco Confidential
*
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
*
Cisco Confidential
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
*
Cisco Confidential
Supported tools are: COBRAS, DRS
*
Cisco Confidential
*
*
Cisco Confidential
Localization (will be delivered subsequent SU's)
Scalability up to 50 branches (backlog US)
*
Cisco Confidential
*
*
Cisco Confidential
*
Cisco Confidential
*
*
Cisco Confidential
Cisco Confidential
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
*
Cisco Confidential
Connectivity
Central Server Configuration- Used to add Central Cisco Unity Connection Server
System Settings
Enterprise Parameters
Telephony Integration
Phone System(Only Default available and can be editable. No option to add New)
Port Group
*
Cisco Confidential
Telephony Integration
Phone System(Only Default available and can be editable. No option to add New)
Port Group
*
Cisco Confidential
Tools-> Custom Keypad Mapping
*
Cisco Confidential