02-04-2019 09:12 AM - edited 03-14-2019 06:46 PM
Creating a new Trigger for a new Application for a new script - done several times in past - always registered to the UCCX Publisher, but in latest attempt the Trigger shows it is registered to the UCCX subscriber.
I am struggling with my new script/ application - just wondering if the Trigger being registered to the Subscriber causes issues.
Rather it be the experience I am having or as general rule it can cause issues.
If known issues - can someone let me know what those might be.
Most importantly : What is corrective action to get the Triggers to start registering properly to the UCCX Publisher ?
02-04-2019 02:06 PM
02-04-2019 02:46 PM
Thanks Anthony. I decided to remove the Trigger then Restart the CRS Engine on the Subscriber. Once it was back in service, I added the Trigger back and viola it now shows the UCCX Publisher. Figured I should try that , wanted to rule out anything that "looked" different.
Thanks for your time.
02-04-2019 05:58 PM
02-14-2019 02:28 PM
Hi Anthony,
You were right the 'registration' in CUCM did not matter.
I actually had an issue with the way I named my CSQ , script was looking for something different. It was so minor and so similar to another queue, I kept glazing over it in my review .... 'it's always the little things that mess you up' :-)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide