Is there an upgrade path from IP office V8 windows Contactstore to V9 Contact Recorder?

[VikeshR]

Does anyone know if Avaya has an upgrade path for someone using IP office v8 contact store on windows to V9 Contact recorder on Linux.
Is there a way to do this

 

[tlpeter]

There isn't as I think they use a different database.
On windows it is a windows database which isn't an option on Linux

BAZINGA!

I'm not insane, my mother had me tested!

 

[VikeshR]

Thanks, I thought as much, I read the manual sometime back and it stated that there isn't a migration path. I see Avaya has taken that note out subsequently.... I guess the customer moving to version 9 will have to keep contact store on windows, no ACR

 

[soflaphoneguy]

I actually did this for one site. The Windows version of CS was 7.8.1.16, so it was using the PostgreSQL database. I just did a database backup on the windows machine, then copied it to the Linux machine. Then the longest part - copying the recording files from the Windows to Linux machine. After the files finished copying, I set the correct permissions on the recording data folder, then restored the backup, restarted the machine and everything worked. It's been running for 8 months now with no issue.

WinSCP and putty were indispensable.

 

[tlpeter]

Funny as Avaya states that it isn't possible

BAZINGA!

I'm not insane, my mother had me tested!

 

[derfloh]

Seems to be not very difficult if it is documented. Or to ensure users without Linux knowledge can do it too Avaya could create a small wizard.

 

[amriddle01]

That's not their style, they still haven't created a wizard/tool (publically available) to convert/transition greetings and prompts etc from Embedded to VM Pro

 

[VikeshR]

Okay then if IPOSS is purchased and the we do it the soflaphoneguy explained. Avaya wont support any issues that may arise. :-(

 

[IPGuru]

Don't tell them ;-)

as both the windows & Linux variants use postgesql for the DB I cant see any reason for problems (postgesql is open source after all so it almost certainly originated on Linux)
The most likely explanation is nobody at Avaya can be bothered to try, much the same way that most clothing that says dry clean only is only labelled like that because the manufacturer cant be bothered to test it (& don't want any possible come back).

It doesn't surprise me considering the poor implementation of their in house Linux apps. (VM Pro running as root WTF)

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[soflaphoneguy]

The site I did this for does not have support from Avaya, so it did not matter to them. I did a pg_dump from the old and new versions of the eware database. There were a few functions from the old version that are no longer in the new version, but other than that everything (table structure, keys, other functions) seemed to be the same. I guess that's why it works.

 

[soflaphoneguy]

I forgot to mention that some calls were not showing in user searches after the upgrade. I finally found that it was because the "owner" extension of the recording was the text extension name and not the numerical extension number. I think that the removed functions might have taken care of this in the old version.

The only workaround I found is that the field "allow calls owned by" has to be populated with both the extension number and name. That is a nightmare to maintain where there are many allowed extensions.