Guest

Preview Tool

Cisco Bug: CSCvt54071 - CMS - Enhancement request to disable Disconnect inactive calls feature

Last Modified

Mar 26, 2020

Products (1)

  • Cisco Meeting Server

Known Affected Releases

2.8.1

Description (partial)

Symptom:
From CMS 2.1 disconnects inactive calls (no RTP traffic) after 60 seconds. This is described in the release notes:

https://www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Release_Notes/Version-2-1/Cisco-Meeting-Server-Release-Notes-2-1-12.pdf#page=25
 2.6.3 Disconnect inactive calls
SIP sessions between the Meeting Server and a call control device, for example Cisco Unified
Communications Manager, can remain in place even if there is no longer any activity in the call.
This situation can arise from a laptop battery dying while in the call, or from network problems.
From version 2.1, the Meeting Server will disconnect and end SIP calls when the Meeting Server
detects no media activity in the call over a period of 60 seconds. This includes Lync and Skype
for Business (S4B) calls with no media activity. For SIP, TIP, Lync and S4B calls that go on hold ,
if the call stops sending RTP/RTCP traffic, then after 60 minutes the call is disconnected, this is
to prevent calls hanging around indefinitely.

Conditions:
Calls with clients that don't need/want to send RTP traffic (recorders/on hold)
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.