Guest

Preview Tool

Cisco Bug: CSCur38391 - MGCP MDCX fails during transfer when v.150 and t.38 are enabled

Last Modified

Feb 25, 2019

Products (12)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Business Edition 5000 Version 8.6
  • Cisco Intercompany Media Engine
  • Cisco Unity Connection Version 9.1
  • Cisco Business Edition 5000 Version 9.1
  • Cisco Business Edition 3000 Version 8.6
  • Cisco Unified Communications Manager Version 8.6
  • Cisco Business Edition 6000 Version 8.6
  • Cisco Unity Connection Version 8.6
  • Cisco Business Edition 6000 Version 9.1
View all products in Bug Search Tool Login Required

Known Affected Releases

10.0(0) 8.6(2) 9.1(2)

Description (partial)

Symptom:
Call failure when transferring

Conditions:
Any call flow requiring v.150 MDCX via MGCP after t.38 strict mode has already been locked by MGCP gateway will result in the gateway NACKing the MDCX from UCM.
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.