CMS ECH issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • szleg4
    Hot Shot
    • Apr 2014
    • 15

    CMS ECH issue

    Hi all,
    We have implemented by ourself ECH on a CMS R17.

    The CHR files are generated in the /cms/cmstables as well

    After that, the file should be transferred from /cms/cmstables to /echi/queues/bin ... but no, the transfer is not done. Can someone explain the way to do it ? Is there a specific function to use ?

    I have done the job manually for a file and once the file is in the /echi/queues/bin, the crontab is scheduled to apply uucp_copy function. It makes the job and put the csv files in the /export/home/CMS directory.

    Thanks for your help
    Last edited by szleg4; 03-11-2015, 02:34 AM.
  • shaikht
    Genius
    .
    • Feb 2010
    • 246

    #2
    Hi,

    I guess we discuss this on chat too.

    If I want to do what you are trying, I may be creating a script/function, to move the files to required destination. You can use mv command for the same.

    I will have a cronjob to execute above script in every 15 minutes.

    For above approach, lot of things need to be taken as there may be scenario like it can move just generated chr files.

    Other option to have properly is to engage APS which I informed on chat.

    I hope it helps.

    Comment

    • szleg4
      Hot Shot
      • Apr 2014
      • 15

      #3
      OK, I understand. But, when you know that it has been working properly before Avaya done the upgrade of the CMS (R16 to R17) ... we don't understand why we should have to pay to have Avaya APS help !!
      Last edited by szleg4; 03-16-2015, 07:53 AM.

      Comment

      • shaikht
        Genius
        .
        • Feb 2010
        • 246

        #4
        Hi,

        I understand your point on it.

        It will be good to have your Account manager to talk to Avaya APS project manager to have solutions for it. As you may be aware that APS work on project basis so if they are involved to upgrade CMS, upgrade will be in scope of project not integrating third party to CMS.

        I hope it helps.

        Comment

        Loading