Attendant Console Directory Field Mappings for BLF
I have LDAP integration with AD for CUCM 9.1. The extensions in AD are the full E164 numbers but my internal extensions are 4-digit. In-order for Attendant Console BLF’s to work they need to reflect the 4-digit extensions exactly. I have populated the ipPhone field in AD with 4-digits. In LDAP Directory in CUCM, I have added a “Custom User Field Name” called ipPhone to match the “LDAP Attribute” in AD to ipPhone and did a manual synch. I cannot see the new ipPhone attribute in End User in CUCM, I suppose it is there but in the database. Am I correct? On CUEAC under “Directory Field Mappings” I selected the source field “telephonenumber” and default value “ipPhone”. The “destination field” is greyed out and set to Extension. However, the CUEAC is still displaying the E164 number instead of the 4-digit extensions and therefore the BLF’s do not work. What have I missed?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.