Cisco Unity Voice-Mail Port Changes

This section describes various voice-mail port configurations in Cisco CallManager. Use the scenarios and procedures that follow to ensure that migration from Cisco CallManager 3.3(x) to Cisco CallManager 4.0 or later releases properly migrates the voice-mail port settings. This section describes voice-mail port configurations in Cisco CallManager 3.3(x) as well as the expected configuration after migration to Cisco CallManager 4.0 or later releases. This section also describes the voice-messaging system changes that take place after you upgrade your system to Cisco CallManager 4.0 or later releases.

Changes After Upgrading to Cisco CallManager 4.0 or Later Releases

You will need to reconfigure a few items to maintain your original voice-mail port functionality, depending on what type of scenario you have set up. You must also change your setup as described in this section.

Things That May Affect Your Setup

If your last voice-mail port is forwarded to a route pattern (gateway or intercluster trunk [ICT]), this configuration will no longer exist after the upgrade. You will need to add the intercluster trunk or gateway to a route group, then add the route group to the corresponding route/hunt list of the route patterns that are attached to the voice-mail pilot number. The route group represents the last member of the route/hunt list.

Note Cisco does not recommend use of the Broadcast distribution algorithm in conjunction with the implementation of voice-mail ports for Cisco Unity.

Line Group Forwarding and Cisco Unity Failover

If you are using the recommended Cisco Unity failover voice-mail port setup, you need to configure the following values for the line groups that are used for the voice-mail ports:

•No Answer: Skip Remaining members and go directly to next group.

•Busy: Try Next member, but do not go to next group.

•Not Available: Skip Remaining members and go directly to next group.

The descriptions of the various scenarios throughout this document provide specific information about these values.

If your final voice-mail port is configured to go to an operator, and the operator is set up to Call Forward No Answer (CFNA) and Call Forward Busy (CFB) back to the voice-mail pilot, you will no longer be able to CFB or CFNA back to the same voice-messaging system. You can add an additional line group that contains the operator line to the voice-mail hunt list.

After an upgrade, the system places the line group where the failover voice-mail ports reside in the route/hunt list that is associated with the hunt list pilot number. You need to manually select the hunt options on the basis of your original configuration.

Changes That You Will Notice After the Upgrade

After the upgrade from previous versions of Cisco CallManager to Cisco CallManager 4.0 or later releases, you will notice the following changes:

•Voice-mail ports now use line groups, route/hunt lists, and hunt pilot numbers.The system creates these entities automatically after the upgrade if the database contained an existing voice-mail port setup. You need to select the hunt options on the basis of your original configurations.

•The pilot number now represents a route pattern with the same number as the first voice-mail port, but in a different partition. The partition that is used for the pilot number was originally the partition that associated with the first voice-mail port.

•The system places voice-mail ports in a newly created partition during the upgrade process.

•The system places voice-mail ports that are used for MWI and for outbound calls on their own separate line groups, route/hunt lists, and hunt list pilot numbers.

Before Upgrading to Cisco CallManager 4.0 or Later Releases

Perform the following step on the voice-mail ports to ensure proper migration:

1. Important: Remove any call forwarding that is set on voice-mail ports that are used only for outbound calls and message waiting indication.

This section provides example configurations in Cisco CallManager 3.3(x) and then outlines what each configuration should resemble after an upgrade to Cisco CallManager 4.0 or later releases occurs. Some manual configuration needs to take place after an upgrade to Cisco CallManager version 4.0 or later releases. This section also outlines these changes.

In this example, on each server, four ports handle incoming calls, and two ports handle outbound calls and MWI. PhoneCSS contains partition(s) that are assigned to subscriber phones, as well as VMPilotNumberPT. VMRestrictedCSS contains only VMRestrictedPT, which is assigned only to VM ports.

In this example, on each server, four ports handle incoming calls, and two ports handle outbound calls and MWI. PhoneCSS contains partition(s) that are assigned to subscriber phones, as well as VMPilotNumberPT. VMRestrictedCSS contains only VMRestrictedPT, which is assigned only to VM ports. The VMPilotPartition gets created automatically and gets assigned to the voice-mail ports.