I have recently migrated a Customer from CCM 3.3(4) & IPCCX 3.1(3) to CUCM6.1(2) & CUCCX 5.0(2).
As part of this project LDAP synchronisation and Authentication was configured on the CUCM and the AXL API Interface was created between CUCM & CUCCX. Everything is working fine to date.
However, the customer has come to me since migration and said that some Visual Basic (VB) Scripts they used to run on the IPCCX are now not working due to authentication errors.
Basically their Helpdesk used the VB Scripts to change the name of .wav files so that a different mesage could be played if people called the Helpdesk during a major IT related incident - e.g if a vital server crashed a load of calls would be received at the Helpdesk so theywould change the opening greeting of the queu to say they were aware of the outage and working on it. This would stop the helpdesk queue from becoming jammed.
The VB script originally used an OS Administrator/password credential to "log on" to the IPCCX and change the filename in the appropriate directory. The original IPCCX server was a member server in the Customers Active Directory.
What I would like to know is whether the new CUCCX Servers (they now have failover) can become member Servers in AD as well as having the synchronisation and authentication functionality via the AXL API ? It is my understanding that LDAP Integration is via CUCM OR via AD.
In this set-up do the OS credentials still get authenticated via AXL or locally to the CUCCX server ?
Can anyone recommend an easy but different way to solve this problem ?