Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I am upgrading a UCCX system from 12.5 SU3 to 15.
In the instructions, it says before you upgrade, ensure that the VM type is open-vm-tools, and to use the switch command if not.
But then post-upgrade, it says to go to the Guest VM tools and Install/...
Hello,
I am having an issue with reports in Finesse for Agents and Supervisors that all show View ID not found.
My CUIC has all of the reports listed, but when I look at a report to verify the View ID, the Permalinks selection is greyed out. So I ca...
Hello,
I inherited a lab system than contains a CUCM/UCCE solution.
The CUCM is composed of a publisher and two subscriber nodes, and the UCCE is a duplex installation. All VMs in the same subnet.
The UCCE Peripheral Gateways for both PG1A and PG1B a...
When trying to create a SIP Trunk Security Profile, I keep getting the following error:
Add failed. TLS and UDP/TCP ports cannot be shared.
I am only setting up non secure UDP port 5060. Very basic.
I can create the profile if I choose TLS and E...
Hello,I have an issue with a UCCE 12.6(2) system reverting back to old registration and authorization data.Using the Unified Contact Center Enterprise Management web portal running on the AW server, under Infrastructure>License Management, I can use ...
The reports I have loaded were Historical and Realtime. I downloaded the LiveData zip file and tried to import it, but it gave me errors.
Does Realtime also use LiveData.xml?
I can run the reports that are loaded in the CUIC with no issues.
Thanks @bill.king1
I was able to use the CUIC command line to see all the View IDs of the reports.
sql select Id, Name, ParentRptId from cuic_data:cuicgrid
I have an issue now that only the Historical.xml gadgets are working but not the LiveData.xml...
This has been resolved.
There was a SIP trunk that was using encryption but on port 5060 instead of 5061.
Once that was corrected to use 5061 I had no issues creating new profiles.
