Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Moving phones from 4.3(2) to 8.0.2 then back to 4.3(2)

I am in the military and we have three CUCM suites that we use on different networks that.  Recently we got two 8.0.2 suites, but we still have a 4.3(2) server that needs to stay for the next year or until it is approved to upgrade it to 8.0.2.  The problem we are having we have limited phones and once we move phones from the 4.3(2) CUCM to 8.0.2 it works fine.  But once we move them back to 4.3(2) they won’t register until we do the factory reset on the phones (hold #, wait for flash, press all number keys).  Is there an easier to move phones back and forth?  There has to be a setting that 8.0.2 is putting on the phone but we can’t figure out what.  Our phone models vary from 7911, 7940, 7941, 7960, 7961, 7945, 7965, and 7975.  Also each exercise varies in size so we can’t dedicate certain phones to be on 4.3 until we upgrade.

Thanks.

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Red

Moving phones from 4.3(2) to 8.0.2 then back to 4.3(2)

Hi Scott,

Have you tried using this procedure before removing the phones from your 8.x build;

Prepare Cluster for Rollback to pre-8.0

Rolling Back the Cluster to a Pre-8.0 Release

Before  you roll back a cluster to a pre-8.0 release of Cisco Unified  Communications Manager, you must prepare the cluster for rollback using  the Prepare Cluster for Rollback to pre-8.0 enterprise parameter.


Caution If  a cluster is downgraded to a pre-8.0 release of Cisco Unified  Communications Manager without preparing it for rollback, Cisco Unified  IP Phones that use Security by Default will be in a loop requesting the  CTL, ITL, and signed configuration files while they try to register with  Cisco Unified Communications Manager. Cisco Unified IP Phones in this  state will not recognize any changes you make to their configuration  files, and you may need to manually delete the ITL file on each Cisco  Unified IP Phone in the system.


To prepare the cluster for rollback, follow this procedure on each server in the cluster:

Procedure


Step 1 From Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

The Enterprise Parameters Configuration window displays.

Set the Prepare Cluster for Rollback to pre-8.0 enterprise parameter to True.


Note Enable  this parameter only if you are preparing to rollback your cluster to a  pre-8.0 release of Cisco Unified Communications Manager. Phone services  that use https (for example, extension mobility) will not work while  this parameter is enabled. However, users will be able to continue  making and receiving basic phone calls while this parameter is enabled.


Restart the Cisco Trust Verification Service on all Nodes


Note You must restart services in the order that is specified in this procedure.


Step 2 From Cisco Unified Serviceability, choose Tools > Control Center - Network Services.

The Control Center - Network Services window displays.

Step 3 To restart the Cisco Trust Verification Service, click the Restart button at the bottom of the window.

Step 4 Restart the Cisco Trust Verification Service on all nodes in the cluster.

Restart the Cisco TFTP Service on the TFTP Servers

Step 5 From Cisco Unified Serviceability, choose Tools > Control Center - Feature Services.

The Control Center - Feature Services window displays.

Step 6 Restart the Cisco Tftp service on each node on which it is active.

Step 7 Wait five minutes for TFTP to rebuild the files.

Reset all Cisco Unified IP Phones


Note You must reset all the Cisco Unified IP Phones in the cluster to ensure that the phones have the most current configuration.


Step 8 From Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

The Enterprise Parameters Configuration window displays.

Step 9 Click Reset.

Step 10 Wait ten minutes for the Cisco Unified IP Phones to register with Cisco Unified Communications Manager.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/security/8_0_1/secugd/secusbd.html#wp1092162

Cheers!

Rob

"Always movin' ahead and never lookin' back" - Springsteen

1 REPLY
Hall of Fame Super Red

Moving phones from 4.3(2) to 8.0.2 then back to 4.3(2)

Hi Scott,

Have you tried using this procedure before removing the phones from your 8.x build;

Prepare Cluster for Rollback to pre-8.0

Rolling Back the Cluster to a Pre-8.0 Release

Before  you roll back a cluster to a pre-8.0 release of Cisco Unified  Communications Manager, you must prepare the cluster for rollback using  the Prepare Cluster for Rollback to pre-8.0 enterprise parameter.


Caution If  a cluster is downgraded to a pre-8.0 release of Cisco Unified  Communications Manager without preparing it for rollback, Cisco Unified  IP Phones that use Security by Default will be in a loop requesting the  CTL, ITL, and signed configuration files while they try to register with  Cisco Unified Communications Manager. Cisco Unified IP Phones in this  state will not recognize any changes you make to their configuration  files, and you may need to manually delete the ITL file on each Cisco  Unified IP Phone in the system.


To prepare the cluster for rollback, follow this procedure on each server in the cluster:

Procedure


Step 1 From Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

The Enterprise Parameters Configuration window displays.

Set the Prepare Cluster for Rollback to pre-8.0 enterprise parameter to True.


Note Enable  this parameter only if you are preparing to rollback your cluster to a  pre-8.0 release of Cisco Unified Communications Manager. Phone services  that use https (for example, extension mobility) will not work while  this parameter is enabled. However, users will be able to continue  making and receiving basic phone calls while this parameter is enabled.


Restart the Cisco Trust Verification Service on all Nodes


Note You must restart services in the order that is specified in this procedure.


Step 2 From Cisco Unified Serviceability, choose Tools > Control Center - Network Services.

The Control Center - Network Services window displays.

Step 3 To restart the Cisco Trust Verification Service, click the Restart button at the bottom of the window.

Step 4 Restart the Cisco Trust Verification Service on all nodes in the cluster.

Restart the Cisco TFTP Service on the TFTP Servers

Step 5 From Cisco Unified Serviceability, choose Tools > Control Center - Feature Services.

The Control Center - Feature Services window displays.

Step 6 Restart the Cisco Tftp service on each node on which it is active.

Step 7 Wait five minutes for TFTP to rebuild the files.

Reset all Cisco Unified IP Phones


Note You must reset all the Cisco Unified IP Phones in the cluster to ensure that the phones have the most current configuration.


Step 8 From Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

The Enterprise Parameters Configuration window displays.

Step 9 Click Reset.

Step 10 Wait ten minutes for the Cisco Unified IP Phones to register with Cisco Unified Communications Manager.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/security/8_0_1/secugd/secusbd.html#wp1092162

Cheers!

Rob

"Always movin' ahead and never lookin' back" - Springsteen

393
Views
5
Helpful
1
Replies