<div dir="ltr">My fear is that the room will show as occupied and deny the request.... (i.e. the physical room accepts it and the room kit sees it as now in use...)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 9, 2019 at 12:43 PM Brian Meade <<a href="mailto:bmeade90@vt.edu">bmeade90@vt.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Webex doesn't respond to the invites. All it does is monitor the Room Resource mailbox. So you can just use the same and it will look for any meetings on the calendar. O365/Exchange should be the side setup to auto-respond to the invites.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 9, 2019 at 1:03 PM Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Customer asked a question and I am curious what best practices are...<div><br></div><div>Customer has room resources in O365 and is adding video systems to those rooms...</div><div><br></div><div>Should the video units get a separate calendar room room resource, or should it share the same room resource email ID in Webex Control Hub?</div><div><br></div><div>My concern is the two entities (room and room kit) responding to the invite and causing some conflict.</div><div><br></div><div>If we use two different room resource mailboxes, users would invite one and not the other...</div><div><br></div><div>What are the best practices here?</div><div><br></div><div><br></div><div><br></div><div>Jonathan</div></div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
</blockquote></div>