Guest

Preview Tool

Cisco Bug: CSCum90701 - LDAP import of msRTCSIP-PrimaryUserAddress does not strip sip:

Last Modified

Feb 25, 2019

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.0(1.10000.24)

Description (partial)

Symptom:
Microsoft's standard for msRTCSIP-PrimaryUserAddress in LDAP uses the following syntax: "SIP:user@domain.com".  msRTCSIP-PrimaryUserAddress can be used to sync with the end user Directory URI field when integrating with LDAP.  In CUCM 9.0, the Directory URI field in the End User configuration will place the URI in the Directory Partition by default. If the import has "SIP:" in the Directory URI, the system can not associate user@domain.com in the directory partition as SIP:user@domain.com is invalid.

Conditions:
Only applicable to CUCM 9.1(2) and 10.0(1). If we sync msRTCSIP-PrimaryUserAddress for Directory URI, there is no way to modify the Directory Partition to correct the error, so if LDAP sync is used, Directory URI should be turned off and entered manually.

The only work around is NOT to sync the Directory URI and import manually.  This is not operationally feasible for customers who have tens or hundreds of thousands of users and those that have multiple clusters.  This is operationally impossible.

Related Community Discussions

LDAP sync, Directory URI and SIP dialing
note: CUCM version 9.1.2 I have an issue when dialing people from a Telepresence endpoint. For phones, we have setup a specific phone service pointing to an external web server for Phone Directory. Telepresence endpoints cannot use that service and point automatically to the default corporate directory. Since we upgraded CUCM to version 9.1.2, the "Directory URI" parameter is now setup on end-users and their associated DN, as it is synced with LDAP. So when we want to dial a user using the directory ...
Latest activity: Jun 02, 2014
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.