04-18-2017 08:39 AM - edited 03-18-2019 01:00 PM
In TMS, we schedule a meeting, then click Externally Hosted, enter our URI (which is an internal CMS bridge number so our H323 units can dial it) then save the meeting to schedule it.
TMS dials the endpoints, connects them, then when we end the meeting, nothing happens and everyone is still in the meeting. Any ideas if this is expected behavior or a bug?
Solved! Go to Solution.
04-18-2017 09:30 AM
The behavior you're describing is by design. Unless there is another conference scheduled for those endpoints within TMS after the Externally Hosted Conference, the endpoints will remain connected even after the conference has been finished.
From the TMS 15.4 Admin Guide, bottom of pg 157 where it describes Externally Hosted Conferences:
... At end time, these participants will not be disconnected and in Cisco TMS the Externally Hosted Conference will be listed as finished. Cisco TMS cannot extend the Externally Hosted Conference itself.
Cisco TMS disconnects an ongoing extended Externally Hosted Conference, based on the following Meeting Types:
* OBTP: Cisco TMS sends an OBTP to the endpoint. If the participants of the ongoing meeting accept it, then the ongoing conference gets disconnected. Based on the importance of the existing conference, a participant can also decline it.
* Automatic Connect: The new meeting scheduled by Cisco TMS automatically gets connected and the existing meeting gets disconnected.
* Manual Connect: The user of the master endpoint has to click OK to get connected to the new meeting.
04-18-2017 09:30 AM
The behavior you're describing is by design. Unless there is another conference scheduled for those endpoints within TMS after the Externally Hosted Conference, the endpoints will remain connected even after the conference has been finished.
From the TMS 15.4 Admin Guide, bottom of pg 157 where it describes Externally Hosted Conferences:
... At end time, these participants will not be disconnected and in Cisco TMS the Externally Hosted Conference will be listed as finished. Cisco TMS cannot extend the Externally Hosted Conference itself.
Cisco TMS disconnects an ongoing extended Externally Hosted Conference, based on the following Meeting Types:
* OBTP: Cisco TMS sends an OBTP to the endpoint. If the participants of the ongoing meeting accept it, then the ongoing conference gets disconnected. Based on the importance of the existing conference, a participant can also decline it.
* Automatic Connect: The new meeting scheduled by Cisco TMS automatically gets connected and the existing meeting gets disconnected.
* Manual Connect: The user of the master endpoint has to click OK to get connected to the new meeting.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide