[cisco-voip] Webex Control Hub and Room Kit Mailboxes

[Matthew Loraditch]

We do it like Lelio.


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Lelio Fulgenzi
Sent: Friday, August 9, 2019 1:40 PM
To: Jonathan Charles <jonvoip at gmail.com>; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Webex Control Hub and Room Kit Mailboxes

I have been thinking about this. My thought is this:


  *   If the room kit is at all portable, like on a cart, make them separate
  *   If the room kit is part of the room, use the same email address



---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Jonathan Charles
Sent: Friday, August 9, 2019 1:03 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Webex Control Hub and Room Kit Mailboxes

Customer asked a question and I am curious what best practices are...

Customer has room resources in O365 and is adding video systems to those rooms...

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?

My concern is the two entities (room and room kit) responding to the invite and causing some conflict.

If we use two different room resource mailboxes, users would invite one and not the other...

What are the best practices here?



Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190809/7a080ccf/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190809/7a080ccf/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image175023.png
Type: image/png
Size: 9409 bytes
Desc: image175023.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190809/7a080ccf/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image160065.png
Type: image/png
Size: 431 bytes
Desc: image160065.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190809/7a080ccf/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image059955.png
Type: image/png
Size: 561 bytes
Desc: image059955.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190809/7a080ccf/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image668585.png
Type: image/png
Size: 444 bytes
Desc: image668585.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190809/7a080ccf/attachment-0004.png>