Cisco TelePresence MCU 4200 Series

Cisco TelePresence MCU disconnects an IP session

Under what conditions will a Cisco TelePresence MCU disconnect an IP session?

This article applies to the following products:

  • Cisco TelePresence MCU 4200 Series
  • Cisco TelePresence MCU 4500 Series
  • Cisco TelePresence MCU 5300 Series
  • Cisco TelePresence MCU MSE Series

Other than when a participant chooses to disconnect, the MCU will only drop an endpoint from the conference when TCP communication between the two devices breaks down. This could be related to the network or the endpoint, for example, when an endpoint connected to a conference is suddenly powered down, its network cable is pulled out, or the network fails between the endpoint and the MCU.

The MCU describes dropping a call due to network problems as an H.245 network connection error.

The time between the start of the problem and the MCU removing the endpoint from the conference will be approximately 75 seconds.

The MCU will never terminate the IP connection in the case where there is no problem with the TCP connection between the endpoint and the MCU but for some reason the endpoint stops sending all UDP/RTP/RTCP packets etc. to the MCU.

Note: it is also possible for either the MCU or the endpoint to receive a disconnect command from a managing application. For example, if Cisco TelePresence Management Suite is managing the MCU, you can check the Conference Control Centre logs if you suspect a disconnection originated from TMS.

January 22nd, 2013 TAA_KB_133