Summary
Enhance APM phone number validation during Add User Jobs to also check whether the selected phone number is already configured in a Call Manager End User Profile.
When running an Add User Job, selecting a free phone number triggers APM to check Unity to verify whether the number is already in use.
If Unity reports the number as in use, APM displays a red warning message, preventing potential conflicts. This validation works well for Unity-associated numbers.
Some Add User Jobs still fail because the selected phone number is already assigned within Call Manager under an End User Profile (User Management).
These numbers are not currently caught by the existing Unity validation, which leads to job failures after submission.
Specifically, the number may exist in the End User field:
enduser.keypadenteredalternateidentifierBecause this field is not currently checked, the conflict is only discovered when the job attempts provisioning.
Extend the phone number validation logic during Add User Jobs to also check whether the selected number exists in Call Manager End User Profiles.
APM should:
Query Call Manager for the selected phone number in the field:
enduser.keypadenteredalternateidentifierIf the number is found, display a warning message similar to the existing Unity conflict warning.
Prevent or warn before job submission to avoid provisioning failures.
When selecting a phone number during an Add User Job:
APM checks:
Unity (existing behavior)
Call Manager End User Profiles (new behavior)
If the number exists in either location, the UI displays a conflict warning, helping the user choose another number before submitting the job.
Shane Stamper
This is actually the self-service ID for the end user in CUCM. We will look to add a validation that checks the self-service ID, but need to review the cost of searching those records before implementation.
Customer: IRS