Guest

Preview Tool

Cisco Bug: CSCuv07460 - CTIGW always sends ForwardingEvent to Lync with forwardStatus of 'True'

Last Modified

Sep 07, 2016

Product

Cisco Unified Communications Manager IM & Presence Service

Known Affected Releases

10.0(1) 11.0(1) 8.6(1) 9.0(1)

Description (partial)

Symptom:
When a Lync user attempts to unset call forwarding a pop-up appears with the following error:
"Cannot apply your new call forwarding settings"

Conditions:
User is using Lync 2013 as their client, and is configured for Remote Call Control of a Cisco Unified Communications Manager (CUCM) device.

Each time a Lync client logins and connects via RCC to IM & Presence, it will try to cancel Call forwarding by sending a CSTA SetForward request to IM & Presence, with the 'activateForward' parameter set to False.

This is successful and is forwarded to CUCM via CTI by IM & Presence. However on receiving a successful response from CUCM, IM & Presence will then create a CSTA ForwardingEvent to send the Call Forwarding state back to the Lync client. The problem with the CSTA ForwardingEvent that is sent, is that the 'forwardStatus' parameter is always set to true even if Call Forwarding is not enabled. When the Lync client receives this CSTA ForwardingEvent request, with 'forwardStatus' set to True but with no forwarding telephone number, a pop up will appear on the Lync Client indicating that the attempt to disable Call Forwarding failed.

Also, intermittently when the Lync user sets and unsets Call Forwarding using the Lync client, the same behavior will be observed with the attempt to unset Call Forwarding.
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.