![]() ![]() |
#1
|
|||
|
|||
![]()
I have a client who is upgrading to CMS R17. We are using Avaya's ECH export service converting binary CMS contact records to ECH and exporting them via SFTP to customer provided server. What does the customer need to have in terms of the ECH server they need to provide? I know server sizing depends on # of ECH records/month X # of months they wish to keep data.
What type of O/S server and DBMS? VMware supported? RAM and typical hard drive requirements? Anything else? They currently use OA for cradle to grave reporting but want to replace OA and just query the ECH records themselves for ad hoc issues such as investigating customer service complaints. |
#2
|
|||
|
|||
![]()
Hi,
Please go through the doc: https://downloads.avaya.com/css/P8/documents/100170083 At page 69, you will see all changes in ECHI since R12. As such, I don't think you need to do anything on ECH server side. Changes will impact fields which take data from CMS. I hope it helps. |
![]() |
Tags |
cms r17, customer requirements, ech, echi |
Thread Tools | Search this Thread |
Display Modes | |
|
|