Guest

Preview Tool

Cisco Bug: CSCul36221 - Transfer does not work if MLPP max Bandwidth Enforcement set to 'STRICT'

Last Modified

Mar 01, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.0(1.10000.8)

Description (partial)

Symptom:
Some supplementary services (like transfer etc) may not work if both of the following service parameters are set
1. Location based MLPP Enabled  = True
2. Location based Maximum Bandwidth Enforcement Level for MLPP Calls = STRICT

Note: By default - Location based MLPP is not enabled. Also; the default level of Maximum Bandwidth Enforcement Level for MLPP calls = LENIENT.
So; this issue will not be hit in default case.

Conditions:
Irrespective of the available bandwidth, when the Enforcement Level is Strict with MLPP Enabled, a call transfer (consult or blind) would result in call getting dropped.

Related Community Discussions

CUCM - Transfer stopped working
Hi there. We're running CUCM 9.1.1 with SCCP phones, and transfer has stopped working. We've tried this from several phones, and get the same result. A user can hit the transfer key to put the caller on hold, dial and connect to the number to be transferred to, and hit the transfer key again. To the user, it seems like the transfer went fine, but the caller just hears a fast busy and isn't connected. Users are able to put callers on hold without issue, and the conference function works fine, so this ...
Latest activity: Jun 23, 2015
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.