Preview Tool

Cisco Bug: CSCtd04124 - the order of signal "MXCapabilitiesIncoming" and "MXFarEndCapsIncoming "

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)


This is a    H323 (FastStart, MTP checked ) ----MTP - MTP -----H323 (FastStart, MTP checked call.)
In this call, I notice that both H245 IF has received MXCapabilitiesIncoming and MXFarEndCapsIncoming signal.
The problem is that both signals have assigned the video capability into mPeerVidDataCap. And as you can see  below, the capability can be MTP's cap or FarEnd 's cap.


The issue was found testing with CUCM 6.1.4 The issue does not happens with CUCM 6.1.1
Bug details contain sensitive information and therefore require a 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.