09-22-2023 12:16 PM
We were told the reason these errors occurred is because we apparently changed the name in CUCM and should have made the change in UCCX
I'm not aware that the "Location" field is stored in UCCX and that we can change it or assign it in UCCX
Any input would be appreciated!
Solved! Go to Solution.
09-22-2023 11:29 PM
It doesn’t in general know about configuration in CM, other than what is used on the trigger numbers that are defined. As location is one of the values on a trigger a change of name on a location used on these would need to be matched in CCX.
09-22-2023 11:29 PM
It doesn’t in general know about configuration in CM, other than what is used on the trigger numbers that are defined. As location is one of the values on a trigger a change of name on a location used on these would need to be matched in CCX.
09-23-2023 08:01 AM
This mismatch typically occurs when a CTI port or trigger number is changed on the CUCM side. As mentioned by @Roger Kallberg, the location value is one example of a field that can cause this issue.
To resolve the mismatch, delete the trigger from the UCCX side and recreate it.
09-23-2023 09:03 AM - edited 09-23-2023 09:09 AM
I would think that it’s not required to delete and recreate the trigger. It should be enough to update the trigger with the new value.
09-23-2023 11:59 AM
Yes, you are right
but sometime when you have many values that need to be change, the faster way to do that for me is to delete and created again
09-25-2023 01:28 PM
Thank you all for the input. I had never really paid attention to the Show More button.
I learned something!
Thanks
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