I'm trying to install the QM 8.5 software in a virtual server with W2003 Server R2 + SQL Server 2008 SP3.
When the Monitoring & Configuration Setup it's opened and The Monitoring and Recording CTI Service window appears I fill de gaps with the IP of the UCCX nodes and click next button but appear this error and I can't finish the installation process.
"JTAPI Installation Error
The following installation errors occurred:
Cannot find SQM CTI Server profile for ip X.X.X.X> or hostname."
Checked on the website mention below:
Text:Cannot find SQM CTI Server profile for ip <localIp> or hostname <hostname>.
Add’l Info:The application could not find information in Directory Services for the local QM CTI Server.
Action:Verify that a QM CTI Server was defined for this server in Site Configuration.
From memory, this was caused by Firewall for SQL Database.
Set a FW rule for SQL Instance TCPIP port. I normally set the port Static (1433). Then Add a rule to allow connection to this port.
By default, SQL DB TCPIP port is dynamic port in 49xxx range. I normally change it to static 1433 add a firewall rule on QM server to allow this port.
Change SQL TCP Port:
From SQL server, start SQL Server Configuration Manager
Double TCP/IP to open TCP/IP Properties Window.
Go to IP Address Tab and you can see dynamic port allocated
I normally remove port from TCP Dynamic Ports field and set a static port 1433 to TCP Port field.
Add this port to Inbound firewall rule (SQL Server)
Windows Firewall with Advanced Security > Inbound Rules
Add new Rule
Rule Type Port
Protocol and Port TCP, Specific Local Ports > 1433
Action Allow the connection
Profile Domain, Private, Public
Name SQL01 for QM
I was having this same issue.
I had the CUCM IP address in the "CTI Services" instead of the QM server IP.
This is located in postinstall> telephony group>
Once i changed that, JTAPI and CTI testing worked.
anyone got it resolved? i am having the same issue. its 10.5version. fresh install. sql lives on locally. although i created the fw rule like mentioned here. still no go.
any suggestion is appriciated.