I had this same issue with 11.5 UCCX partial service, I was able to resolve by resetting the CTI services on the UCM 12.0 nodes, resetting the UCCX services, and discovered that there were triggers in the UCCX that were not populating in UCM, removed the triggers and re-adding them resolved the issue - system now in full service.