References

For additional information refer to these resources:

Troubleshooting Issues in Provisioning

This topic describes how to resolve SRSV deployment issues.

  • Status of provisioning remains in progress or is not working:
    1. Check the network connectivity of the central Cisco Unity Connection and the branch.
    2. Ensure that the branch username and password are not expired by logging in to the branch administration page.
    3. Check whether the VMREST and Connection Branch Sync Service are active on both the headquarters and branch.
    4. Check the license and certificate status.
    5. If automatic provisioning is not working at the scheduled time, then check whether the branch provisioning synchronization task is enabled.
  • If the previous steps do not resolve the issue, enable all micro traces for CUCESync and VMREST services for the central Cisco Unity Connection. Check for any exceptions or failures in the traces for the CuCESync service.

Follow this list to resolve issues that are related to SRSV setup. If these steps do not resolve the issue, enable traces for SRSV.

The VMREST micro traces provide diagnostic information on the use of the API. The VMREST micro traces are written to the Tomcat diagnostic files. Collect logs for CUCESync service and Cisco Tomcat services from Cisco Unity Connection at both the headquarters and branches. If automatic provisioning is not working at the scheduled time, then provisioning is scheduled at the next cycle.

Replicate the System Distribution List

This topic describes how to enable replication of System Distribution Lists.

  • Distribution list replication is enabled on a per-list basis:
    1. Verify the synchronization of the distribution list.

Check the Replicate to SRSV Branches check box to synchronize the distribution lists from the headquarters Cisco Unity Connection server to the branch. Verify the synchronization in the Branch Sync Results page.

Monitor the Provisioning and Polling Status

This topic shows how to check the provisioning status of branches.

Choose Networking > Branch Management and monitor the results of the synchronization.

At the Branch Sync Results page under Networking > Branch Management, you can see the result of synchronization. The result can be any of the following:

  • In Progress: This result signifies that the synchronization activity is in progress.
  • Success: This result signifies that the synchronization activity is completed successfully.
  • Partial Success: This result signifies that the synchronization activity is partially completed. For example, if you initiated synchronization of four users from the headquarters Cisco Unity Connection server to the branch, two of the four users could have synchronized successfully and two did not. In such scenarios, you must check the error logs to determine the reason for the failure and take the appropriate action to resolve the problem.
  • Failed: This result signifies that the synchronization activity has failed. To check the reason for the failure, refer to the associated logs.

Automatic Provisioning and Voicemail Polling

This topic describes how to configure automatic provisioning and voicemail polling of the branch locations.

Choose Tools > Task Management and enable automatic branch provisioning and voicemail polling.

Enable automatic synchronization between the headquarters and the branch Cisco Unity Connection servers. You can run the synchronization after system startup, regularly after 10 or more minutes, or specify a certain day per week or month.

The provisioning flow is as follows:

  1. The headquarters Cisco Unity Connection sends a request for provisioning.
  2. The branch is ready for provisioning.
  3. The headquarters Cisco Unity Connection sends the provisioning data in the form of a zipped chunk.
  4. The branch confirms receipt of the provisioning data zipped chunk and verifies the integrity on last chunk.
  5. Provisioning is started at the branch.
  6. A notification is sent to the headquarters Cisco Unity Connection when provisioning is complete.
  7. The headquarters Cisco Unity Connection acknowledges branch provisioning.

The branch voicemail polling task polls the branches that are defined in the headquarters Cisco Unity Connection and schedules those branches for voicemail upload if they have voicemails.

The voicemail upload flow is as follows:

  1. The headquarters Cisco Unity Connection checks for new voicemails for the branch.
  2. The branch confirms that a new message is available.
  3. The headquarters Cisco Unity Connection requests message information from the branch.
  4. The branch sends the message details.
  5. The headquarters Cisco Unity Connection fetches the new message as a WAV file.
  6. The branch responds with a WAV file.
  7. The headquarters Cisco Unity Connection confirms the message delivery and asks the branch to delete the messages.
  8. The branch deletes the messages.

Set Up Headquarters Cisco Unity Connection

This topic shows how to configure the headquarters Cisco Unity Connection site as a central site for the SRSV branch sites.

Add a new branch on HQ Cisco Unity Connection:

  • Specify the partition to synchronize.
  • Enable synchronization for voice names and greetings.
  • Test the setup.
  • Manually provision the branch site for the first time.
  • Voicemail polling can also be done manually.

HQ = headquarters.

To add a new branch, choose Networking > Branch Management > Branches.

When you set up the central site, point to the server IP address of the branch Cisco Unity Connection site and enter the user credentials.

Enter a PAT port number that the central Cisco Unity Connection server uses to communicate with the branch. This port number specifies the port on the public side of the NAT, which further maps to port 443 for communicating with the branch.

In this example, only users that are located in the partition branch router are synchronized to the SRSV server in the branch site. You can also choose to synchronize the recorded voice names and greetings of the end users.

SRSV Configuration Checklist for Headquarters Site

This topic describes the configuration of Cisco Unity Connection in the headquarters site to register the branch SRSV server.

Central Cisco Unity Connection configuration

  • Create an SRSV branch user partition and move users into that partition.
  • Activate the branch.
  • Set up provisioning and polling schedules.

In the headquarters site, create a partition for branch users and set up the synchronization based on schedules. Then activate the branch to offer voicemail functionality during a WAN failure.