Preview Tool

Cisco Bug: CSCul27745 - CUBE fails to invoke xcoder during mid-call with Survivability.tcl app

Last Modified

Jan 27, 2017

Products (17)

  • Cisco IOS
  • Cisco ASR 901-6CZ-F-D Router
  • Cisco ASR 901-4C-FT-D Router
  • Cisco ME 3600X-24TS-M Switch
  • Cisco ASR 901-6CZ-F-A Router
  • Cisco ASR 901-6CZ-FT-A Router
  • Cisco ASR 901-12C-FT-D Router
  • Cisco ASR 901-6CZ-FT-D Router
  • Cisco 7600 Series Route Switch Processor 720 with Multilayer Switch Feature Card
  • Cisco 7600 Series Route Switch Processor 720 with 10 Gigabit Ethernet Uplinks
View all products in Bug Search Tool Login Required

Known Affected Releases


Description (partial)

CUBE fails invoke xcoder during mid-call code changes when survivability.tcl application is involved in the call flow.
Incoming calls are terminated to IP-IVR and G711 media is flow through the CUBE.  When there is an unexpected failure and if CUBE received a unusual CV say 404 in the second leg of the sip call, survivability.tcl application triggers the call survivability and tries to connect the call to an available agent  which can only do G729.   From the sip signalling perspective CUBE negotiates G729 with the agent side GW, however because of the mid-call signalling block configured on the dial-peers, CUBE cannot negotiate G729 end to end.   At this state, the incoming sip leg is still G711 active, where as the new second leg is negotiated for G729 with the agent side G729.   Ideally CUBE should be invoking the Xcoder to convert G711 to G729 and vise versa.   Hence CUBE continue to send G711 media streams to the agent side GW which is causing oneway audio issues.

When survivability.tcl script application is configured, cube fails invoke the xcoder during mid-call codec changes.
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.