8.1.56 compatible with 8.1.67

[BullDog54]

Gents,
I am downgrading an IP500-V2 from 9.0 to 8.1
The 8.1 .config I will be uploading is 8.1.67
I have 8.1.65 that I am using to do the IPO downgrade with
Are there any issues with the an 8.1.67 config running on an 8.1.65 IPO.
They also have Voicemail Pro - would this create any issue with the Voicemail.
Thanks for your help!

 

[Okkie26]

I don't think so...

 

[intrigrant]

No, it is all 8.1.x so no problem.

 

[BullDog54]

Thanks- will there be any effect on the IP phones? will they now have to download the older file or will they just work as normal?
Thanks

 

[Okkie26]

As long as you do not change the 16xxupgrade file nothing will happen..

 

[IPGuru]

why are you noy using the final V8.1 maintnanence releasse?

Actually why are you downgradding (I assume some issue with V9.0).
If we knew the reason we might* be able to offer a better solution.

If you do donwgrade downgrade the VM as well, back everything up first but it should all be fine.

*Although we may not, somtimes the downgrade is the best option.


Do things on the cheap & it will cost you dear

 

[BullDog54]

The customer, at the main office, has old IP500 hardware running 8.1.67
They closed a remote office that had IP500V2 hardware running 9.0.
They want to move their system at the main office to the V2 hardware.
I got the licenses swapped to the SD card on the V2 Hardware-so that is good
Since The V2 was running 9.0 - I needed to downgrade the V2 to 8.1.67 so I can upload the config from the old system.
This system has about 140 phones on it so I wanted to disrupt things as little as possible.
I could not find 8.1.67, so I downgraded the V2 to 8.1.65 yesterday, uploaded the config and everything looks good- no errors , all licenses are Valid.
My plan is to unplug the old IPO hardware, move the PRI card to the new V2 and plug everything back in.
At that point I would hope everything will work- the PRI, the Voicemail Pro.
If the IP phones do not have to "downgrade" to 8.1.65- would be great- just not sure.
That's it in a nutshell - if anyone can see anything that would go wrong- I would appreciate your pointing it out.
Thanks again for everyone's help

 

[IPGuru]

Sounds reassonable
I would build the replacement IP500V2 before perfrming the hardwase swap.
I still also recomend upgrading to the lates main release of V8.1 whilst you are at it or take the opertunity to upgradde the cust to V9.0 (the current cfg will be fine) unless they are using somthing that is nolonger supported.
the V8.1 firmware is available on Avayass web site so you should not have any trouble obtaining it.


Do things on the cheap & it will cost you dear

 

[BullDog54]

I finished the upgrade and all went well- however this system has an IP400 Analog Expansion module. I cannot get it to recognize its connected. RED LIGHT on front panel- In "System Status" it says link down. Is this module compatible with V2 hardware?

Thanks

 

[budbyrd]

It should be compatable. Power down the expansion unit and unplug it from the IPO. Power it back up, disconnected. It should come up and blink green. If it stays red it probably has a firmware issue and would need to do a DTE reset of the module.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[BullDog54]

How do you do a Firmware reset of the module?

 

[budbyrd]

Power off the IP Office
Connect the not working expansion module to the IP Office
Connect the expansion module serial port to your PC
Start HyperTerminal - 38400,8,N,1
Power up the expansion module and repeatingly press ESC on the PC until you get the Loader message
Power up the IP Office
Open Avaya Manager and open the config
Make sure the TFTP server in Manager is active and that the working directory contains the necessery bin files for the expansion module
In HyperTerminal enter AT-X (must be in caps), the module replies with Multi-Sector Erase and will show a TFTP Poll message
If all is well you can see in the Manager tftp logs that the module is loading the software
After a while the LED on the expansion module flashes green.
Reboot the module
Close the config in Manager and open it again
Test the module, if only the software was a problem it is working again - if not you have a hardware problem

On a V2 it may not pull the file from manager, it will probably pull it from the SD card. If you watch it in Monitor with the TFTP option turned on you should see it pulling the file.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'