Hi
okay without actually looking at it live I cannot see what is going on. Sorry scripts seem fine from what i can read out of it .
if you open the console screen on CMS and do ( after logged on as either superuser or root) use tail ACSERR.cvsLog . this will give you a running screen of...
okay run the reports manually , first in CMS client see if that gives a result if that works the report works ( as the script is only a mechanism to fire off the same report ,
now there was a option to monitor what the CMS aplication is doing ( forgot what it was) kick that report off via the...
Hi
you could but you would need to look very carefully on the build of each report , eg declaration etc . you can glue them into one script , the alternative is to run the reports sequential, give it a couple of minutes in between . PS to this, in my past working in a callcenter I had a very...
Hi
on the media resource board in the gateway you are terminating the analgue or digital extension , you would still need a session manager to manage the SIP element , SIP is a protocol not a transport mechanism.
Hi
There is an export process to store the historical data "external" from the old CMS on a shared or physical ( USB stick / drive) , you can then safeguard the information and import it back on ACD 1. ( check support.avaya.com , CMS , upgrade documentation ). Its states you can only do this...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.