Reconfiguration and Upgrade Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
Changing the IP Address of a Cisco Unity 8.x or Voice-Recognition Server
Downloads: This chapterpdf (PDF - 163.0KB) The complete bookPDF (PDF - 7.03MB) | Feedback

Changing the IP Address of a Cisco Unity 8.x or Voice-Recognition Server

Table Of Contents

Changing the IP Address of a Cisco Unity 8.x or Voice-Recognition Server

Changing the IP Address of a Cisco Unity 8.x Server Without Failover

Changing the IP Address of a Primary Cisco Unity 8.x Server (With Failover Configured)

Changing the IP Address of a Secondary Cisco Unity 8.x Server (With Failover Configured)

Changing the IP Address of a Cisco Unity 8.x Site Gateway in a Cisco Voicemail Organization

Changing the IP Address of a Cisco Unity 8.x Voice-Recognition Server


Changing the IP Address of a Cisco Unity 8.x or Voice-Recognition Server


This chapter contains the following sections:

Changing the IP Address of a Cisco Unity 8.x Server Without Failover

Changing the IP Address of a Primary Cisco Unity 8.x Server (With Failover Configured)

Changing the IP Address of a Secondary Cisco Unity 8.x Server (With Failover Configured)

Changing the IP Address of a Cisco Unity 8.x Site Gateway in a Cisco Voicemail Organization

Changing the IP Address of a Cisco Unity 8.x Voice-Recognition Server

Changing the IP Address of a Cisco Unity 8.x Server Without Failover

When choosing an IP address for a Cisco Unity server, note the following considerations:

Do not choose an address accessible from the Internet. Doing so can expose the Cisco Unity server to unwanted intrusion from the Internet, even when the server is hardened.

Do not choose an address that separates the Cisco Unity server from the following servers by a firewall:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

A Cisco Unity voice-recognition server.

If the Cisco Unity server is separated from any of the following servers by a firewall, open the applicable TCP and UDP ports:

Any Exchange server that homes mailboxes for Cisco Unity subscribers.

DNS servers.

Workstations that are used to administer Cisco Unity.

Client workstations that are used to access Cisco Unity via the Cisco Personal Communications Assistant (Cisco PCA).

Cisco Unified CM servers.

SIP end points.

SCCP phones.

For details on the TCP/UDP ports that must be opened in a firewall to allow communication between Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter in the Security Guide for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Do the applicable procedures.

To Change the IP Address of a Cisco Unity Server Without Failover


Step 1 On the Cisco Unity server, on the Windows Start menu, click Settings > Control Panel > Network and Dial-Up Connections > Local Area Connection.

Step 2 Click Properties.

Step 3 In the Components Checked Are Used by This Connection list, select Internet Protocol (TCP/IP), but do not uncheck the check box.

Step 4 Click Properties.

Step 5 In the Internet Protocol (TCP/IP) Properties dialog box, change values as applicable. Refer to Windows Help for more information.

Step 6 Click OK to close the Internet Protocol TCP/IP Properties dialog box.

Step 7 Click OK to close the Local Area Connection Properties dialog box.

Step 8 Close the Local Area Connection Status window.

Step 9 If the IP address is in a different subnet, disconnect the network cable from the original subnet, and connect the cable from the target subnet to the Cisco Unity server.

Step 10 Confirm that the server name can be resolved to the new IP address.


Depending on your network, after changing the IP address of a Cisco Unity server that has Exchange on the server, you may need to update the Exchange SMTP virtual server settings to reflect the new IP address so that Bridge and/or VPIM messages are delivered correctly.

To Check and Update the SMTP Virtual Server Relay List


Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Microsoft Exchange > System Manager.

Step 2 In the tree on the left, expand Servers\<Server name>\Protocols\SMTP.

Step 3 Right-click Default SMTP Virtual Server and select Properties.

Step 4 Click the Access tab.

Step 5 Click Relay.

Step 6 If All Except the List Below is selected and the new server IP address does not appear in the list, skip to Step 11. If All Except the List Below is selected and the new server IP address appears in the list, click the IP address and click Remove, then skip to Step 10. If Only the List Below is selected, continue with Step 7.

Step 7 Click Add.

Step 8 Click Single Computer, and enter the new IP address of the Cisco Unity server.

Step 9 Click OK.

Step 10 Verify that the Allow All Computers Which Successfully Authenticate to Relay, Regardless of the List Above check box is checked.

Step 11 Click OK twice to close the Properties dialog box.

Step 12 Close the Exchange System Manager.


Changing the IP Address of a Primary Cisco Unity 8.x Server (With Failover Configured)

Use this procedure to change the IP address of the primary Cisco Unity server both when Exchange is installed on a separate server and when Exchange is installed on the secondary server.

When choosing an IP address for the primary Cisco Unity server, note the following considerations:

Do not choose an address accessible from the Internet. Doing so can expose the Cisco Unity server to unwanted intrusion from the Internet, even when the server is hardened.

Do not choose an address that separates the primary server from the following servers by a firewall:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

A Cisco Unity voice-recognition server.

If the primary server is separated from any of the following servers by a firewall, open the applicable TCP and UDP ports:

The secondary server.

Any Exchange server that homes mailboxes for Cisco Unity subscribers.

DNS servers.

Workstations that are used to administer Cisco Unity.

Client workstations that are used to access Cisco Unity via the Cisco Personal Communications Assistant (Cisco PCA).

Cisco Unified CM servers.

SIP end points.

SCCP phones.

For details on the TCP/UDP ports that must be opened in a firewall to allow communication between Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter in the Security Guide for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Do the following nine procedures in the order listed.

To Disable Automatic Failover and Failback, and Stop File Replication


Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Failover.

Step 3 Click Yes to confirm that you want to fail over to the secondary server.

Step 4 Click Advanced.

Step 5 Check the Disable Automatic Failover and Failback check box.

Step 6 Confirm that the Enable File Replication check box is unchecked.

Step 7 Click OK.

Step 8 Click Configure.

Step 9 Uncheck the Force Failover If Call Arrives on Inactive Secondary check box.

Step 10 Click OK.

Step 11 Close the Failover Monitor.


To Stop the Node Manager Service on the Primary and Secondary Cisco Unity 8.x Servers


Step 1 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Services.

Step 2 In the Services window, right-click AvCsNodeMgr, and click Stop.

Step 3 Close the Services window on the primary server.

Step 4 On the secondary server, on the Windows Start menu, click Programs > Administrative Tools > Services.

Step 5 In the Services window, right-click AvCsNodeMgr, and click Stop.

Step 6 Close the Services window on the secondary server.


To Change the IP Address of the Primary Cisco Unity 8.x Server


Step 1 On the primary server, on the Windows Start menu, click Settings > Control Panel > Network Connections > Local Area Connection.

Step 2 Click Properties.

Step 3 In the Local Area Connection Properties dialog box, in the This Connection Uses the Following Items list, select Internet Protocol (TCP/IP), but do not uncheck the check box.

Step 4 Click Properties.

Step 5 In the Internet Protocol (TCP/IP) Properties dialog box, change values as applicable. Refer to Windows Help for more information.

Step 6 Click OK to close the Internet Protocol TCP/IP Properties dialog box.

Step 7 Click OK to close the Local Area Connection Properties dialog box.

Step 8 Close the Local Area Connection Status window.

Step 9 If the IP address is in a different subnet, disconnect the network cable from the original subnet, and connect the cable from the target subnet to the Cisco Unity server.

Step 10 Confirm that the server name can be resolved to the new IP address.


To Check the Consistency of the Cisco Unity Database


Step 1 On the primary server, install the latest version of the Cisco Unity Directory Walker (DbWalker) utility, available at http://www.ciscounitytools.com/Applications/Unity/dbWalker/dbWalker.html.

Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)


To Set the Registry of the Secondary Cisco Unity 8.x Server by Reconfiguring Failover


Step 1 On the Windows taskbar, double-click the system clock. The Date and Time Properties dialog box appears.

Step 2 Set the time to the same hour and minute as shown on the primary server, and click OK.

Step 3 In Windows Explorer, browse to the CommServer directory.

Step 4 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.

Step 5 When the prompt that lists the requirements for the wizard appears, confirm that the requirements have been met and click OK.

Step 6 On the Welcome page, click Next.

Step 7 On the Specify Server Role page, click Secondary Server, and click Next.

Step 8 On the Enter the Name of Your Server page, click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.

Step 9 Click Next.

Step 10 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.

The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.


Caution You must specify the same account on both the primary and secondary servers.

Step 11 In the Password field, enter the password for the account that the failover service will log on as, and click Next.

Step 12 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the secondary server.

If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and do this procedure again.

Step 13 On the Completing page, click Finish.


To Confirm That Both Cisco Unity 8.x Servers Can Be Pinged and That SQL Replication Has No Errors


Step 1 On the primary server, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 2 In the Command Prompt window, enter C:\Ping <IP address of secondary server>, and press Enter.

If the secondary server sends a reply, the IP address is valid.

If the secondary server does not send a reply, either the primary server has a problem obtaining an address from the DHCP server, or the assigned IP address conflicts with the IP address of another computer on the network. Verify the network settings. If needed, troubleshoot any problem as you would a network connectivity problem.

Step 3 In the Command Prompt window, enter C:\Ping <Primary server name>, and press Enter.

If the primary server sends a reply, the server name is valid.

Step 4 On the secondary server, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 5 In the Command Prompt window, enter C:\Ping <IP address of primary server>, and press Enter.

If the primary server sends a reply, the IP address is valid.

If the primary server does not send a reply, either the secondary server has a problem obtaining an address from the DHCP server, or the assigned IP address conflicts with the IP address of another computer on the network. Verify the network settings. If needed, troubleshoot any problem as you would a network connectivity problem.

Step 6 In the Command Prompt window, enter C:\Ping <Secondary server name>, and press Enter.

If the secondary server sends a reply, the server name is valid.

Step 7 On the Windows Start menu, click the applicable command:

For Microsoft SQL Server 2005, click Programs > Microsoft SQL Server 2005 > SQL Server Management Studio. The SQL Server Management Studio window appears.

For Microsoft SQL Server 2000, click Programs > Microsoft SQL Server > Enterprise Manager. The SQL Server Enterprise Manager window appears.

Step 8 Confirm that no errors appear for the SQL replication agents.

If errors appear for the jobs, right-click the SQL Server Agent node and click Start. The errors will clear in a few minutes after the network connection between the primary and secondary servers is restored.


To Restart the Primary Cisco Unity 8.x Server


Step 1 While the secondary server is active and answering calls, restart the primary server.

The primary server becomes active, and the secondary server becomes inactive.

Step 2 Confirm that the primary server starts and that there are no errors in the Application Event log.


To Confirm That the Primary Cisco Unity 8.x Server Is Active and, If Applicable, to Re-enable Automatic Failover and Failback


Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 If the secondary server is active, click Failback, and click Yes.

Step 3 Re-enable file replication (if standby redundancy is configured), or re-enable automatic failover and failback, if applicable:

a. Click Advanced.

b. Do one of the following:

Check the Enable File Replication check box.

Uncheck the Disable Automatic Failover and Failback check box.

c. Click OK.

The setting will replicate to the primary server.

Step 4 If standby redundancy is configured, disable failover initiation when calls are unanswered on the primary server:

a. Click Configure.

b. Uncheck the Force Failover If Call Arrives on Inactive Secondary check box.

c. Click OK.

Step 5 Close the Failover Monitor.


During testing in the following procedure, you may need to refer to the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

To Confirm That Failover and Failback Function Correctly


Step 1 While the primary server is active, create a test file (for example, Test.txt) in the CommServer\Stream Files directory on the primary server.

Step 2 Confirm that the file replicates to the secondary server within the time set in the File Replication Interval field in the Failover Monitor (the default is 10 minutes).

If the file does not replicate, you must configure failover on both the primary and secondary servers, then do this procedure again.

Step 3 On the primary server, modify the extension of a subscriber.

Step 4 Confirm that the change replicates to the secondary server immediately. When you open the Cisco Unity Administrator on the secondary server, ignore the warnings that the secondary server is inactive.

If the change does not replicate, you must configure failover on both the primary and secondary servers, then do this procedure again.

Step 5 If Microsoft SQL Server 2005 is installed, continue to Step 6. If Microsoft SQL Server 2000 is installed, skip to Step 12.

Step 6 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.

Step 7 In the Connect to Server dialog box, in the Server Name field, click the name of the SQL Server and click Connect. The Microsoft SQL Server Management Studio window appears.

Step 8 In the left pane, expand the Replication > Local Publications node.

If the Local Publications node does not have a node for the UnityDb database, failover has not been configured. You must configure failover on both the primary and secondary servers, then do this procedure again.

Step 9 In the left pane, expand the SQL Server Agent > Jobs.

Step 10 If the Jobs subnodes do not have red Xs on them in the left pane, UnityDb database replication for failover is functioning normally.

If the Jobs subnodes have red Xs on them, restore replication for failover:

a. On the primary server, exit Microsoft SQL Server Management Studio.

b. On the secondary server, run the failover configuration wizard.

Step 11 Continue to Step 16.

Step 12 If Microsoft SQL Server 2000 is installed, on the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager. The SQL Server Enterprise Manager window appears.

Step 13 In the left pane, expand the Microsoft SQL Servers node.

Step 14 Expand the Replication Monitor node.

If the node does not exist, failover has not been configured. You must configure failover on both the primary and secondary servers, then do this procedure again.

Step 15 If the Replication Monitor subnodes do not have red Xs on them in the left pane, UnityDb database replication for failover is functioning normally.

If the Replication Monitor subnodes have red Xs on them, restore replication for failover:

a. On the primary server, exit SQL Server Enterprise Manager.

b. On the secondary server, run the failover configuration wizard.

Step 16 Restore the original extension of the subscriber.

Step 17 On the primary server, manually initiate failover.

Step 18 Confirm that the primary server becomes inactive and that the secondary server becomes active.

Step 19 Call in to Cisco Unity.

Step 20 Confirm that the secondary server answers the call.

If the secondary server does not answer the call, you must configure failover on both the primary and secondary servers, then do this procedure again.

Step 21 On the secondary server, delete the test file from the CommServer\Stream Files directory.

Step 22 Confirm that the file is deleted from the primary server within the time set in the File Replication Interval field in the Failover Monitor (the default is 10 minutes).

Step 23 On the secondary server, manually initiate failback.

Step 24 Confirm that the primary server becomes active and that the secondary server becomes inactive.

Step 25 Call in to Cisco Unity.

Step 26 Confirm that the primary server answers the call.


Changing the IP Address of a Secondary Cisco Unity 8.x Server (With Failover Configured)

Use this procedure to change the IP address of the secondary Cisco Unity server both when Exchange is installed on a separate server and when Exchange is installed on the secondary server.

When choosing an IP address for the secondary Cisco Unity server, note the following considerations:

Do not choose an address accessible from the Internet. Doing so can expose the Cisco Unity server to unwanted intrusion from the Internet, even when the server is hardened.

Do not choose an address that separates the secondary server from the following servers by a firewall:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

A Cisco Unity voice-recognition server.

If the secondary server is separated from any of the following servers by a firewall, open the applicable TCP and UDP ports:

The primary server.

Any Exchange server that homes mailboxes for Cisco Unity subscribers.

DNS servers.

Workstations that are used to administer Cisco Unity.

Client workstations that are used to access Cisco Unity via the Cisco Personal Communications Assistant (Cisco PCA).

Cisco Unified CM servers.

SIP end points.

SCCP phones.

For details on the TCP/UDP ports that must be opened in a firewall to allow communication between Cisco Unity and other servers, see the "IP Communications Required by Cisco Unity 8.x" chapter in the Security Guide for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/security/guide/8xcusecx.html.

Do the following nine procedures in the order listed.

To Disable Automatic Failover and Failback, and Stop File Replication


Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Advanced.

Step 3 Check the Disable Automatic Failover and Failback check box.

Step 4 Confirm that the Enable File Replication check box is unchecked.

Step 5 Click OK.

Step 6 Click Configure.

Step 7 Uncheck the Force Failover If Call Arrives on Inactive Secondary check box.

Step 8 Click OK.

Step 9 Close the Failover Monitor.


To Stop the Node Manager Service on the Primary and Secondary Cisco Unity 8.x Servers


Step 1 On the primary server, on the Windows Start menu, click Programs > Administrative Tools > Services.

Step 2 In the Services window, right-click AvCsNodeMgr, and click Stop.

Step 3 Close the Services window on the primary server.

Step 4 On the secondary server, on the Windows Start menu, click Programs > Administrative Tools > Services.

Step 5 In the Services window, right-click AvCsNodeMgr, and click Stop.

Step 6 Close the Services window on the secondary server.


To Change the IP Address of the Secondary Cisco Unity 8.x Server


Step 1 On the secondary server, on the Windows Start menu, click Settings > Control Panel > Network Connections > Local Area Connection.

Step 2 Click Properties.

Step 3 In the Local Area Connection Properties dialog box, in the This Connection Uses the Following Items list, select Internet Protocol (TCP/IP), but do not uncheck the check box.

Step 4 Click Properties.

Step 5 In the Internet Protocol (TCP/IP) Properties dialog box, change values as applicable. Refer to Windows Help for more information.

Step 6 Click OK to close the Internet Protocol TCP/IP Properties dialog box.

Step 7 Click OK to close the Local Area Connection Properties dialog box.

Step 8 Close the Local Area Connection Status window.

Step 9 If the IP address is in a different subnet, disconnect the network cable from the original subnet, and connect the cable from the target subnet to the Cisco Unity server.

Step 10 Confirm that the server name can be resolved to the new IP address.


To Check the Consistency of the Cisco Unity Database


Step 1 On the primary server, install the latest version of the Cisco Unity Directory Walker (DbWalker) utility, available at http://www.ciscounitytools.com/Applications/Unity/dbWalker/dbWalker.html.

Step 2 Run DbWalker, and correct all errors that the utility finds. Refer to DbWalker Help for detailed instructions on running the utility and on correcting errors in the database. (The Help file, DbWalker.htm, is in the same directory as DbWalker.exe.)


To Set the Registry of the Primary Cisco Unity 8.x Server by Reconfiguring Failover


Step 1 In Windows Explorer, browse to the CommServer directory.

Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.

Step 3 When the prompt that lists the requirements for the wizard appears, confirm that the requirements have been met and click OK.

Step 4 On the Welcome page, click Next.

Step 5 On the Specify Server Role page, click Primary Server, and click Next.

Step 6 On the Enter the Name of Your Server page, click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.

Step 7 Click Next.

Step 8 On the Enter Failover Account Information page, click Browse, and double-click the name of the message store services account. This is the account that the failover service will log on as.

The account you select must have the right to act as part of the operating system and to log on as a service, and must be a member of the Local Administrators group.


Caution You must specify the same account on both the primary and secondary servers.

Step 9 In the Password field, enter the password for the account that the failover service will log on as, and click Next.

Step 10 On the Begin Configuring Your Server page, click Configure. The wizard verifies settings and configures failover on the primary server.

If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and do this procedure again.

Step 11 On the Completing page, click Finish.


To Confirm That Both Cisco Unity 8.x Servers Can Be Pinged and That SQL Replication Has No Errors


Step 1 On the primary server, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 2 In the Command Prompt window, enter C:\Ping <IP address of secondary server>, and press Enter.

If the secondary server sends a reply, the IP address is valid.

If the secondary server does not send a reply, either the primary server has a problem obtaining an address from the DHCP server, or the assigned IP address conflicts with the IP address of another computer on the network. Verify the network settings. If needed, troubleshoot any problem as you would a network connectivity problem.

Step 3 In the Command Prompt window, enter C:\Ping <Primary server name>, and press Enter.

If the primary server sends a reply, the server name is valid.

Step 4 On the secondary server, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 5 In the Command Prompt window, enter C:\Ping <IP address of primary server>, and press Enter.

If the primary server sends a reply, the IP address is valid.

If the primary server does not send a reply, either the secondary server has a problem obtaining an address from the DHCP server, or the assigned IP address conflicts with the IP address of another computer on the network. Verify the network settings. If needed, troubleshoot any problem as you would a network connectivity problem.

Step 6 In the Command Prompt window, enter C:\Ping <Secondary server name>, and press Enter.

If the secondary server sends a reply, the server name is valid.

Step 7 On the Windows Start menu, click the applicable command:

For Microsoft SQL Server 2005, click Programs > Microsoft SQL Server 2005 > SQL Server Management Studio. The SQL Server Management Studio window appears.

For Microsoft SQL Server 2000, click Programs > Microsoft SQL Server > Enterprise Manager. The SQL Server Enterprise Manager window appears.

Step 8 Confirm that no errors appear for the SQL replication agents.

If errors appear for the Distribution agent, right-click the agent, and click Start Synchronizing to resume SQL replication. The errors will clear in a few minutes after the network connection between the primary and secondary servers is restored.


To Restart the Secondary Cisco Unity 8.x Server


Step 1 While the primary server is active and answering calls, restart the secondary server.

Step 2 Confirm that the secondary server starts and that there are no errors in the Application Event log.


To Confirm That the Primary Cisco Unity 8.x Server Is Active and, If Applicable, to Re-enable Automatic Failover and Failback


Step 1 On the secondary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 If the secondary server is active, click Failback, and click Yes.

Step 3 Re-enable file replication (if standby redundancy is configured), or re-enable automatic failover and failback, if applicable:

a. Click Advanced.

b. Do one of the following:

Check the Enable File Replication check box.

Uncheck the Disable Automatic Failover and Failback check box.

c. Click OK.

The setting will replicate to the primary server.

Step 4 If standby redundancy is configured, disable failover initiation when calls are unanswered on the primary server:

a. Click Configure.

b. Uncheck the Force Failover If Call Arrives on Inactive Secondary check box.

c. Click OK.

Step 5 Close the Failover Monitor.


During testing in the following procedure, you may need to refer to the Failover Configuration and Administration Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/failover/guide/8xcufgx.html.

To Confirm That Failover and Failback Function Correctly


Step 1 While the primary server is active, create a test file (for example, Test.txt) in the CommServer\Stream Files directory on the primary server.

Step 2 Confirm that the file replicates to the secondary server within the time set in the File Replication Interval field in the Failover Monitor (the default is 10 minutes).

If the file does not replicate, you must configure failover on both the primary and secondary servers, then do this procedure again.

Step 3 On the primary server, modify the extension of a subscriber.

Step 4 Confirm that the change replicates to the secondary server immediately. When you open the Cisco Unity Administrator on the secondary server, ignore the warnings that the secondary server is inactive.

If the change does not replicate, you must configure failover on both the primary and secondary servers, then do this procedure again.

Step 5 If Microsoft SQL Server 2005 is installed, continue to Step 6. If Microsoft SQL Server 2000 is installed, skip to Step 12.

Step 6 On the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.

Step 7 In the Connect to Server dialog box, in the Server Name field, click the name of the SQL Server and click Connect. The Microsoft SQL Server Management Studio window appears.

Step 8 In the left pane, expand the Replication > Local Publications node.

If the Local Publications node does not have a node for the UnityDb database, failover has not been configured. You must configure failover on both the primary and secondary servers, then do this procedure again.

Step 9 In the left pane, expand the SQL Server Agent > Jobs.

Step 10 If the Jobs subnodes do not have red Xs on them in the left pane, UnityDb database replication for failover is functioning normally.

If the Jobs subnodes have red Xs on them, restore replication for failover:

a. On the primary server, exit Microsoft SQL Server Management Studio.

b. On the secondary server, run the failover configuration wizard.

Step 11 Continue to Step 16.

Step 12 If Microsoft SQL Server 2000 is installed, on the primary server, on the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager. The SQL Server Enterprise Manager window appears.

Step 13 In the left pane, expand the Microsoft SQL Servers node.

Step 14 Expand the Replication Monitor node.

If the node does not exist, failover has not been configured. You must configure failover on both the primary and secondary servers, then do this procedure again.

Step 15 If the Replication Monitor subnodes do not have red Xs on them in the left pane, UnityDb database replication for failover is functioning normally.

If the Replication Monitor subnodes have red Xs on them, restore replication for failover:

a. On the primary server, exit SQL Server Enterprise Manager.

b. On the secondary server, run the failover configuration wizard.

Step 16 Restore the original extension of the subscriber.

Step 17 On the primary server, manually initiate failover.

Step 18 Confirm that the primary server becomes inactive and that the secondary server becomes active.

Step 19 Call in to Cisco Unity.

Step 20 Confirm that the secondary server answers the call.

If the secondary server does not answer the call, you must configure failover on both the primary and secondary servers, then do this procedure again.

Step 21 On the secondary server, delete the test file from the CommServer\Stream Files directory.

Step 22 Confirm that the file is deleted from the primary server within the time set in the File Replication Interval field in the Failover Monitor (the default is 10 minutes).

Step 23 On the secondary server, manually initiate failback.

Step 24 Confirm that the primary server becomes active and that the secondary server becomes inactive.

Step 25 Call in to Cisco Unity.

Step 26 Confirm that the primary server answers the call.


Changing the IP Address of a Cisco Unity 8.x Site Gateway in a Cisco Voicemail Organization

For information on changing the IP address of a Cisco Unity site gateway when Connection Networking is configured, see the "Making Changes to a Cisco Unity Site Gateway" section in the "Making Changes to the Networking Configuration in Cisco Unity Connection 8.x" chapter of the Networking Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

Changing the IP Address of a Cisco Unity 8.x Voice-Recognition Server

When choosing an IP address for a Cisco Unity voice-recognition server, note the following considerations:

Do not choose an address accessible from the Internet. Doing so can expose the Cisco Unity server to unwanted intrusion from the Internet, even when the server is hardened.

Do not choose an IP address that separates the voice-recognition server from the Cisco Unity server by a firewall. If failover is configured, do not separate the voice-recognition server from either Cisco Unity server by a firewall.

Do the following procedure.

To Change the IP Address of a Cisco Unity Voice-Recognition Server


Reinstall all software on the voice-recognition server, and configure the voice-recognition software by following the task list in the "Installing and Configuring a Cisco Unity 8.x Voice-Recognition Server" appendix in the applicable Installation Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.