Guest

Preview Tool

Cisco Bug: CSCvt99490 - CM should gracefully exit call if h245 link fails while allocating resource

Last Modified

Sep 30, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(2.10000.5) 10.5(2.18156.2) 11.5(1.10000.6) 12.0(1.10000.10) 12.5(1.10000.22)

Description (partial)

Symptom:
When CM looses tcp connection for H245 signaling channel call still remains active and able to request and allocate features such as MOH. However, this will cause media to fail as the link has been broken and will not be able to provide any supplementary services.

Conditions:
When having an active call and there is a network issue between CM and H323. You will see the following on the trace:
56198631.001 |08:43:14.642 |AppInfo  |TranslateAndTransport(16082)::wait_SdlCloseInd - ERROR: H245 signaling connection aborted!!!, err=104

56198631.002 |08:43:14.642 |AppError |H245Log: Process=TranslateAndTransport LogicalChannelNumber=1011 -- TCP ERROR: TcpAwaitRespTimer times out, or received SdlCloseInd from H245Handler, Perform cleanup of H245 Session

56198632.000 |08:43:14.642 |SdlSig   |TtFailure                              |sessionEstablished             |H245SessionManager(2,100,29,16082) |TranslateAndTransport(2,100,22,16082) |2,100,14,143864.152^*^*                  |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] #### 
56198632.001 |08:43:14.642 |Stopping |                                       |                               |H245SessionManager(2,100,29,16082) |H245SessionManager(2,100,29,16082) |                                         |NumOfCurrentInstances: 90
56198633.000 |08:43:14.642 |SdlSig   |H245SessionEstablishedFailure          |sessionEstablished             |H245Interface(2,100,191,16089)   |H245SessionManager(2,100,29,16082) |2,100,14,143864.152^*^*                  |[R:N-H:0,N:7,L:1,V:0,Z:0,D:0]

Later on when we received, StopStreaming, H245IF sent back stoppedstreaming back to MX right away. As it knows that it can not send signal to H323 endpoint since transport link is broken. This broken tcp connection is for the media signaling. Hence, cucm did not drop the call. But it cannot provide any supplementary services on it.
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.