Mar 06 2020 10:39 AM - edited Mar 06 2020 10:44 AM
Hello,
We have a Teams meeting that has existed for a few months. It has a call in number and Conference ID associated with it and neither has changed in all this time. The meeting organizer starts the meeting each morning from Teams on his Windows laptop. Some remote users connect via Teams and some via phone. Connections via Teams is fine, but when users call in with the correct call in number and Conference ID, there seems to be a disconnect between the meeting and those calling in. Callers are told to wait for the meeting to start even though it already has. This problem started this week and again, nothing has changed with the recurring meeting.
Thanks,
Brian
Mar 06 2020 03:26 PM
Mar 06 2020 03:30 PM
Mar 06 2020 03:42 PM
@Chris Webb Thanks for your reply. Audio conference (phone) number hasn't changed. For each new meeting created, a new Conference ID is created. I just tested that now. I'm not aware of Conference ID's expiring, but if there is a rule about how long a Conference ID can persist, that would explain it. This a recurring meeting that was set up early in the year and continues through the end of the year. We need to have a stable and dependable Conference ID.
Mar 06 2020 04:34 PM
Jul 27 2020 08:49 PM
Hi @nimblejoe - we have recently been investigating expired PSTN Conferencing ID's expiring after have some failed meetings. Microsoft post details of Teams meeting limits here:
https://docs.microsoft.com/en-us/microsoftteams/limits-specifications-teams#meeting-expiration
Unfortunately there does not appear to be a method of discovering expired meetings!
I hope this helps...
Rich
Aug 26 2020 06:54 AM