Cisco Bug: CSCur41139 - Jabber Android doesn't query ipPhone AD field.
Jun 14, 2016
- Cisco Unified Mobile Communicator
Known Affected Releases
Symptom: Jabber Android have no photo id on display during incoming call (via MRA and inside network). When we do search - we can see photo, saved contacts have photo too, but no photo during incoming call. . LDAP requests from different clients are different. Jabber for Android didn't include ipPhone field when requesting photo but Jabber for windows include this field. Customer AD has only ipPhone field filled with number. Conditions: If we compare requests from Jabber Windows and Jabber Android during an incoming call to the Application then we see the following Jabber for Windows sends the following query to AD: 2014-10-13 16:28:41,046 DEBUG [0x00008580] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - Query::RunQuery - [LDAP-FILTER] Executing query with filter: (&(objectclass=user)(!(UserAccountControl:1.2.840.1135220.127.116.113:=2))(telephoneNumber=4830)) 2014-10-13 16:28:41,076 DEBUG [0x00008580] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - Query::RunQuery - [LDAP-FILTER] Executing query with filter: (&(objectclass=user)(!(UserAccountControl:1.2.840.113518.104.22.1683:=2))(|(|(|(mobile=4830))(homePhone=4830))(ipPhone=4830))) 2014-10-13 16:28:41,096 TRACE [0x00008580] [\main\person\PersonManagerImpl.cpp(1702)] [csf.person] [person::PersonManagerImpl::PersonResolutionHandler::onSearchComplete] - (009AFD00) Found record 036AD0A0 (ActiveDirectory:email@example.com) =============================== jabber for Android: -- 2014-10-13 16:31:44.173 DEBUG [a069000] - [csf.person.ldap][sendSearchQuery] filter = (&(objectCategory=person)(objectClass=user)(|(telephoneNumber=4830)(mobile=4830)(homePhone=4830))), baseDN=DC=corp,DC=cisco,DC=com
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases