Cisco Bug: CSCul50539 - EventLog Warning Raised Due to Bridge Disconnect at Max Duration is Conf
Apr 03, 2017
- Cisco TelePresence Conductor
Known Affected Releases
Symptom: Issuing an API factory.conferencecreate with factoryMaxDurationMinutes included in the request, but no 'Limit the conference duration' time set on the conductor template, we find that conductor does not log the MaxDuration value. Consequently, from Conductor's perspective, the conference always ends on the MCU/TPS before it expects. This is what triggers the Warning log. Conditions: Will always see this when using the API factory.conferencecreate. May also see this occasionally when, due to a race condition, the MCU/TPS clears the conference marginally before Conductor expects it to expire; conductor polls the MCU/TPS to check the conference state and it no longer exists.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases