Guest

Preview Tool

Cisco Bug: CSCus73488 - CUBE doesn't send H245 CLC for outstanding OLC if TCS is received

Last Modified

Mar 09, 2018

Products (81)

  • Cisco IOS
  • Cisco 888W Integrated Services Router
  • Cisco 886VA-CUBE Integrated Services Router
  • Cisco VG204XM Analog Voice Gateway
  • Cisco C892FSP Integrated Services Router
  • Cisco C897VA Integrated Services Router
  • Cisco 819 Hardened Integrated Services Router
  • Cisco 892W Integrated Services Router
  • Cisco 2951 Integrated Services Router
  • Cisco 886VAG 3G Integrated Services Router
View all products in Bug Search Tool Login Required

Known Affected Releases

12.4(24)T8 15.3(3)M3

Description (partial)

Symptom:
If CUBE receives a TCS (like an empty-capability-set signal for a hold/resume transition) right after sending an OLC and without having received an OLCack or OLCrej from the other end; the CUBE will throw and error and wait until the timeout for the outstanding OLC shoots.

An error like the one below will get printed if running cch323 logs:

Jan 22 20:03:58.926: //79205/8010A5CB0400/H323/errHdlr: ERROR: Received Unexpected IWF_EV_CLC_IND in state IWF_OLC_AWAIT_EST_CFM

Conditions:
Running a CUBE environment interworking between H323-to-H323 call legs

Related Community Discussions

Incoming calls via H323 GW to CUCM not working
Here is some background. Our office currently runs off of a hosted CM. It's SIP from our GW to the service provider. And the CM uses SIP trunks for routing.   We are building out a new internal CM that we will eventually cutover to. We have setup an h323 GW in our CM utilizing the loopback address of the voice GW. When I try to make an incoming test call to my CIPC phone, I get fast busy. Debug voice ccapi inout shows the call hit the correct dial peer (a dial peer I built for the specific DID and ...
Latest activity: Nov 02, 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.