The data model for 2.x logically consists of Members, Rooms, Gateways, and legacy devices as illustrated in this figure:
Members—Members are users who have authorized accounts to use the portal. Members always use their login name and password for authentication. Members can originate/receive direct calls (also known as two party calls), join meeting rooms and they can be “invited” to meeting rooms. Members may have a display name and other parameters. Each Member belongs to a Group.
Rooms—Rooms are named conferences that members (or guests) may join, depending on the status, PIN, availability, etc. Rooms are of three types:
Each room has an owner. The owner can modify the room’s properties; control the conference when in session, etc. Each member has one personal room. When a member or a legacy device (via gateway) tries to reach a member with a personal room, they will have an option of either joining the personal room or placing a direct call to the member. Like members, Rooms may also have more descriptive display names. Rooms may also have multiple aliases for addressing purposes. For example, the unique names “alice meeting” and “2001” could both refer to the same meeting room, which has the display name “Alice Jones’ Meeting.”
Group—A group has a set of properties. All the members belonging to a group share these properties.
Gateways—Gateways are used to make and receive calls to external legacy devices that are not part of Vidyo Conferencing system. Calls to these legacy devices are identified by prefixes followed by the devices address. Based on the prefix, the request is routed to the appropriate gateway to bring a legacy device to the conference.
Guests—Guests do not belong to the system; however, they are allowed to join the room without any authentication. Guest can be invited to a meeting room by using Guest WS API.