Cisco Bug: CSCuo73369 - Call history in Jabber Windows does not record calls with * dialing.
Nov 27, 2020
- Cisco Jabber for Windows
Known Affected Releases
Symptom: Call history in jabber windows does not create an entry when the calling number contains a *. Conditions: Configure CUCM with a Translation Pattern: 1. Go to CUCM Administration Page > Call Routing > Translation Pattern. 2. Create a Translation Pattern on CallManager, say *.3006 where 3006 is the DN of Jabber. 3. Under 'Calling Party Transformations' section in the same page,set * in 'Prefix Digits (Outgoing Calls)' section. 4. Click save. 5. Now make a call to Jabber Windows by dialing the Translation Pattern (dial *3006) from a physical phone which does not have any directory URI at the DN level. 6. If the call is either answered or not, there is no Missed/Received calls in Call History. So call back is not possible. Call is received on Jabber Windows from an IP Phone.
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