Downgrading Software Code - Avaya 3641 Installation, Configuration And Administration

the given extension will be unregistered, and any activity on the currently-registered
telephone will be stopped. If that telephone is in a call, the call will be dropped.
If the user does not want to override the existing extension, either enter a different
extension and password, or simply END the Wireless IP Telephone.
If two Wireless IP Telephones are assigned to the same extension, the Avaya

Aura™ Communication Manager will not properly resolve the registration conflict
due to the presence of the Avaya Voice Priority Processor. Both Wireless IP
Telephones may fail to operate properly.
Retry / Restart
Some errors will result in the following display, once # is pressed to continue:
* to retry
# to restart
Press * to immediately retry registering with the Communication Manager. Press # to
restart the Wireless IP Telephone, which will take about 20 seconds.
6.1

Downgrading Software Code

When downgrading code to a software version below 117.052 (R3.0), certain conditions
apply. Please study the following bullets before downgrading code.
•
If you change R3.0 specific settings (such as new security types or WMM types), then
you *might* run into problems doing a downgrade. We recommend doing a Restore
Default in this case and reprogramming the phone using HAT. This will get rid of any
R3.0 settings that might confuse the pre- R3.0 code.
•
If you didn't change any settings when you upgraded, then you should be able to
downgrade without doing a Restore Defaults.
•
If the phone has never had pre-R3.0 code on it and is configured with R3.0 settings,
and then the user tries to downgrade to a pre-R3.0 release, the phone will default to
pre-R3.0 configuration settings (for example, security will be None).
• In general, if you upgrade to R3.0 and enable R3.0 features and then you downgrade
the phone, the phone will not be able to connect to the network without changing the
network (unless you are running multiple APs/ AP configurations with different
security/ WMM settings).
•
The issue of doing a Restore Defaults generally only applies when downgrading from
R3.0 to pre- R3.0 code. For example, downgrading from 117.053 to 117.052 should
not require a Restore Defaults.
Issue 6, January 2011
Avaya Communication Manager Integration Factors
81