I've been tasked with a job to complete our UCCX install in our virtualised playpen.
I'm assured the install steps so far have been:
create admin user and pass
create application user and pass
Install UCCX with CM
Now, the UCCX server looks good. I can log into the CLI and execute commands just fine. So the next steps i have tried, as per the deployment guide are to log on via a browser to configure the web interface.
So i have connected successfully using the url - http://SVRname/ and am presented with the ccx administration login screen.
After entering my credentials i'm presented with another screen asking if this is an upgrade or a fresh install.
As per the deployment guide, i select fresh install and hit next. We're cooking on gas now as i'm presented with the next screen asking for my credentials again and the CM server name.
Here's where i get an issue. I provide the above (assuming CM is bundled on the same server), hit enter and i get the error:
"Cisco Unified CM Authentication failed because AXL Service possiblydisabled/stopped. Please check the Cisco AXL service on Cisco Unified CM"
Now, i've assumed massively here, CM was installed as part of the installation. Please excuse how dumb this may sound to you non-newbies,
So the only place i can check for the AXL service is on the UCCX CLI. I listed all available services and the AXL one was not there.
I did attempt to start the service. I got no errors, but i have a sneaky feeling i'm trying it on the wrong component anyway.
Is CM not in fact installed and i must obtain this software seperately?
Indeed, +5 for Anand here, you need to install CUCM before you install UCCX, as CUCM is your call processor and hub for all unified communications (IP-PBX plus more). Without CUCM you cannot deploy phones, you cannot make any calls, nor can you deploy any other applications including UCCX.
Are you performing this just for lab purposes or is this an actual production system? If production, I strongly suggest you engage a professional firm to assist with the implementation as it will only get more complex after the initial installation in order to properly provision the system, especially writing contact center scripts.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.