How can I create phone books based on provisioned endpoints that correlate to the Provisioning Directory subgroups? For example, I have sub-group OfficeA, I'd like to have a phone book source called OfficeA-Provisioned, and be able to have a phone book listed as "OfficeA" that then includes just those provisioned endpoints in the OfficeA sub-group.
I have TMS 13.1.2 and am able to successfully provision users from LDAP so that I don't need to manually create them. I can also create sub-groups by way of utilizing search filters (for example sorting by OU: ou=OfficeA or ou=OfficeB might result in sub-groups OfficeA and OfficeB).
I realize that I can try and create a phone book based on LDAP, the challenge there being that it overpopulates the directory with meaningless entries.
Jens is correct...this is doable in TMSPE but not in Legacy TMS Agent Which means since your running TMS 13.1.2, I assume your running Legacy TMS Agent. Therefore, you'll need to upgrade to TMS 13.2 or later so has to migrate to TMSPE. And I stronly encourage you do that
Cisco CUCM Connector for Work from Home/Field Executives Cisco CUCM telephony setup is deployed at enterprise networkAs per enterprise business requirement Sales Executive/Relationship Manger need to call their customers using the existing ente...
attached pdf is not final but sharing first version
will continue later hopefully with more hints and additions
note this is not an official guide, there is chance that I miss better alternatives
Hey All, Just thought I would share a good LDAP filter for CMS user import: (&(objectCategory=person)(objectClass=user)(telephoneNumber=*)person(sn=*)) This successfully imported 12500 users into CMS for me. Hope this helps.&...
All, when trying to create an end user I am getting the error message "KeypadEnteredAlternateIdentifier for ENd User Already exists" can someone give me a clue on what that means. I kinda figure it means the user with that nam...
Disclaimer: Yes, security fanatics may not approve of this (but, hey, they would probably never really approve of anything, anyway). However, for most pragmatists, this is a feasible solution with acceptable risk to an elevated credential...