New UCCX Application Trigger being rejected in CUCM

[BoBo1]

Hello,

I'm hoping there is a simple fix for my issue, but forgive me as I'm not that experienced with UCCX and creating the applications.

I'm having troubles getting a trigger to work for a new application that I built in UCCX. I've created a trigger before and they worked fine, but that was always on applications that already existed and were working.

To create this new application, I just copied an existing one and change the names in some required fields as the script that will be required when triggered in the same.

For the Trigger, I create it in UCCX and then it generates everything in CUCM automatically. The trigger for this "new" application is getting marked as "Rejected" under the CTI route points in CUCM.

Any ideas on what to check for?

Thank you!

[Elliot Dierksen]

I would double check the telephony config in CCX. Is there another device using the DN for the trigger? Also, does the CM group in the device pool you used for the CTI route point match the order of the JTAPI servers in you telephony config in CCX?

[BoBo1]

The telephony config in CCX looks okay to me - at least when compared to the other triggers.

"Also, does the CM group in the device pool you used for the CTI route point match the order of the JTAPI servers in you telephony config in CCX?"

Can you explain this one a bit more? I'm not exactly sure where to check this. 

[Elliot Dierksen]

Let's say you have 4 call managers (1-4). The telephony config of CCX explicitly specifies which call managers it will try to register. If you have HA, is it LAN or WAN? If it is LAN, both CCX nodes use the same list of CM's. If it is WAN, they can be different. If Your telephony config says use CM1 and CM2, but the device pool CM list specifies CM3 and CM4 then the registration could be rejected.

[BoBo1 · Accepted solution]

I got it sorted out.

I was checking out the services in CCX Serviceability, and the Cisco Unified CCX Engine service was in "Partial Service".

I restarted that service, and the line now works fine.

Thanks for the help!