Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Timing to disapper from MCU

HI all,

When we connect codecs to Codian MCU, we see endpoints on call at "Home > Conferences > Conference "name" > Participants" on the MCU.

And if we unplug a LAN cable of an endpoint on call, the name of the codec will disappear from Participants list soon.

The time differs from SIP and H.323 though, does anybody know how to vary the time to let codecs disappear from participants list?

(In this case we do not use VCS control because our customer does not have it)

Best Regards,

Kotaro Hashimoto

Everyone's tags (2)
2 ACCEPTED SOLUTIONS

Accepted Solutions
New Member

Timing to disapper from MCU

As you mentioned if you have e.g. a VCS control then you have much more control over how long calls take to time out.

If you just use the MCU to make direct SIP/H323 calls without a gatekeeper/registrar then it is not possible to control this as the default behaviour is hard-coded and the mechanism by which the disconnection happens is different.

With H.323 the participant will be removed when the h.225 or h.245 TCP connections time out, and I beleive the timer is of the order of two minutes. With SIP the participant will be disconnected when the SIP session timer expires, this is negotiated in the SIP signalling when the call is set up but could be more like 5 minutes by default.

This doesn't mean that it will take either two or 5 minutes for the call to be dropped, but rather that it will happen at the end of the next timeout 'window', so the exact time will vary.

Cisco Employee

Re: Timing to disapper from MCU

As Luc already explained this detail level, the exact time will vary.

Please note that if there is any update message from MCU to Endpoint (i.e H.245 MC, SIP INFO, etc.) then disconnection timing may much quicker as MCU will detect connection lost between Endpoint that point.

2 REPLIES
New Member

Timing to disapper from MCU

As you mentioned if you have e.g. a VCS control then you have much more control over how long calls take to time out.

If you just use the MCU to make direct SIP/H323 calls without a gatekeeper/registrar then it is not possible to control this as the default behaviour is hard-coded and the mechanism by which the disconnection happens is different.

With H.323 the participant will be removed when the h.225 or h.245 TCP connections time out, and I beleive the timer is of the order of two minutes. With SIP the participant will be disconnected when the SIP session timer expires, this is negotiated in the SIP signalling when the call is set up but could be more like 5 minutes by default.

This doesn't mean that it will take either two or 5 minutes for the call to be dropped, but rather that it will happen at the end of the next timeout 'window', so the exact time will vary.

Cisco Employee

Re: Timing to disapper from MCU

As Luc already explained this detail level, the exact time will vary.

Please note that if there is any update message from MCU to Endpoint (i.e H.245 MC, SIP INFO, etc.) then disconnection timing may much quicker as MCU will detect connection lost between Endpoint that point.

500
Views
0
Helpful
2
Replies