Cisco Bug: CSCul19978 - Jabber for Windows CFA issues in call history
Mar 13, 2014
- Cisco Jabber for Windows
Known Affected Releases
Symptom: Customers have two CUCM clusters connected via a standard SIP trunk. When calling a client through this SIP trunk there are issues with the call history / caller ID showing the wrong number after a Call Forward All was previously used. Conditions: Cluster A has the following Phones: Client1 CSF Cluster B has the following Phones: DeskPhone1 DeskPhone2 If Client1 calls DeskPhone1 it is forwarded to DeskPhone2. The caller ID on Client1 displays correctly for DeskPhone2, and after the call is completed the call history also shows DeskPhone2. The issue is when the user calls DeskPhone1 when the Call Forward All to DeskPhone2 is removed. If the user Calls DeskPhone1 again, the Caller ID on Client1 shows Deskphone1 correctly and the call history also shows DeskPhone1. Unfortunately, the first call (that was CFA) is also updated to DeskPhone1.
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