cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3979
Views
31
Helpful
4
Replies

Is the 5 minute pre-meeting configurable for OBTP

ryan_oconnell
Level 3
Level 3

Hello, 

 

We have hybrid Cal setup for some video enabled boardrooms that are registered to a UCM cluster and these devices use Webex Edge for Devices. This is all working just fine. 

 

The users have requested that we modify the default pre-meeting admittance time from 5 Min to 15min so that people can join meeting earlier if they wanted to. We adjusted the scheduling templates and made it the default for the ORG under the Webex Site admin. This is working fine for users that join using the Webex Meetings Application however we are still seeing that the OBTP video endpoints seem to only allow a pre-meeting join time of 5 min's. Is this a function that we can modify to match the new scheduling template? 

1 Accepted Solution

ryan_oconnell
Level 3
Level 3

I ended up opening a TAC case. They confirmed this to be normal behavior and provided the following Technical explanation as to why.

 

If meetings are hosted in a user's Personal Room or in a single Space back-to-back, then the same Locus is used underneath. In order to send an OBTP Join notification, CalendarService sets the subject into the Locus meeting title, loads the roster list with the new users/rooms, and then sets the state from Inactive to Initializing. Initializing state then sends the OBTP Join notification. Also, the non-connected users/rooms are removed at the same time and the new attendee list is added to the roster. Those new people/rooms may attempt to join the existing meeting being hosted in the same Locus.

 

The longer the OBTP Join shows up, then the change activity is set on the Locus earlier which will negatively impact the current meeting. That is why it is set to 5 minutes due to the UX downsides.

 

 

 

View solution in original post

4 Replies 4

JNeubecker
Level 4
Level 4

I face the same issue. Users are complaining that the 5 minutes for OBTP is not early enough. Namely for larger meetings when multiple presenters want to discuss how they plan to conduct the meeting, but also for simple meetings. There has got to be a solution, especially if there is no prior meeting to finish first. If there are meetings in sequence, of course the 5 minute is ok.

A staged solution would be welcome, say a default 5 minutes if back-to-back meetings are happening and 15 minutes if no prior meeting in those 15 minutes and 30 minutes if no prior meeting in those 30 minutes. 

Cole Callahan
Cisco Employee
Cisco Employee

Hi Ryan,

 

I'm sorry you were having this issue. Thanks for sharing an update on your TAC case. Hopefully, this post and reply will act as a resource for anyone else that may be experiencing a similar issue.

 

Have a great day!



Response Signature


ryan_oconnell
Level 3
Level 3

I ended up opening a TAC case. They confirmed this to be normal behavior and provided the following Technical explanation as to why.

 

If meetings are hosted in a user's Personal Room or in a single Space back-to-back, then the same Locus is used underneath. In order to send an OBTP Join notification, CalendarService sets the subject into the Locus meeting title, loads the roster list with the new users/rooms, and then sets the state from Inactive to Initializing. Initializing state then sends the OBTP Join notification. Also, the non-connected users/rooms are removed at the same time and the new attendee list is added to the roster. Those new people/rooms may attempt to join the existing meeting being hosted in the same Locus.

 

The longer the OBTP Join shows up, then the change activity is set on the Locus earlier which will negatively impact the current meeting. That is why it is set to 5 minutes due to the UX downsides.