08-11-2022 09:17 AM
Solved! Go to Solution.
08-12-2022 05:08 AM
In our case, the root cause turned out to be that the work number imported from Azure AD did not match the DN configured in CUCM. We have a 6-digit internal dial plan, and until we changed the attribute mapping to get those 6-digit numbers populated as the work telephone numbers imported into Webex the problem persisted. Once the change was made and another sync cycle ran, calling from the phone icon used CUCM as desired.
08-11-2022 11:07 AM
08-11-2022 02:24 PM
We actually tried that approach, but it made no difference. Currently working with TAC. It appears that it could be something to do with how the users sync'ed from Azure AD into Control Hub. I will post more once we resolve.
08-11-2022 03:39 PM
Please do. We have tested the above successfully, but reverted as our environment simply needed more flexibility. Good luck!
08-12-2022 05:08 AM
In our case, the root cause turned out to be that the work number imported from Azure AD did not match the DN configured in CUCM. We have a 6-digit internal dial plan, and until we changed the attribute mapping to get those 6-digit numbers populated as the work telephone numbers imported into Webex the problem persisted. Once the change was made and another sync cycle ran, calling from the phone icon used CUCM as desired.
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