Guest

Preview Tool

Cisco Bug: CSCub10861 - CUCM 8.5(1) MLPP Documentation / Call Waiting with MLPP Preemption

Last Modified

Jul 03, 2017

Products (6)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Business Edition 6000 Version 8.5
  • Cisco Business Edition 5000 Version 8.5
  • Cisco Business Edition 6000 Version 8.6
  • Cisco Unity Connection Version 8.5
  • Cisco Unified Communications Manager Version 8.5

Known Affected Releases

8.5(1)

Description (partial)

Symptom:
When the busy trigger is set to 2 and a second higher precedence call is received by the destination user, normal call waiting behavior should be exhibited. When the busy trigger is set to 1, then the existing call should be preempted. This is reproducible in all phone models and across different CUCM versions.


Conditions:
Existing Cisco documentation (taken directly from Cisco Unified Communications Manager Features and Services Guide for Cisco Unified Communications Manager Release 8.5(1), Chapter 35 Multilevel Precedence and Preemption, Line Feature Interaction, Call Waiting page 35-31) states the following:

Call Waiting

MLPP interacts with the call-waiting feature as described in the following list:

•When conflicts arise between call-waiting status and MLPP precedence calls due to the lack of network resources, the call gets preempted.

•When a precedence call is offered to a destination station that is configured with call waiting, the following behaviors take place:

■If the requested precedence is higher than the existing call precedence, the existing call gets preempted. If the destination user is nonpreemptable, call processing invokes normal call-waiting behavior and alerting. If the precedence call is of Priority precedence level or higher, the destination user receives precedence call-waiting tones and cadences.

■If the requested precedence level is the same as the existing call precedence, call processing invokes normal call-waiting behavior. If the precedence call is of Routine precedence, call processing alerts the destination with standard call-waiting tones. If the precedence call is of Priority or higher precedence, call processing alerts the destination with precedence call-waiting tones.

■If the requested precedence level is lower than the existing call precedence, call processing invokes normal call-waiting behavior. If the precedence call is of Routine precedence, call processing alerts the destination with standard call-waiting tones. If the precedence call is of Priority or higher precedence, call processing alerts the destination with precedence call-waiting tones.

■When a device has more than one appearance, the destination user may place a lower precedence call on hold to acknowledge receipt of a higher precedence call. After the higher precedence call ends, the destination user may resume the held, lower precedence call.

This documentation is not fully correct and needs to be changed to avoid misleading customers.
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.