Radvision Video Conferencing Policies and Procedures10/25/2012 2:02:00 PM

Transcription

1 Radvision Video Conferencing Policies and Procedures10/25/2012 2:02:00 PM User Permissions The intent of this policy and procedures document is to utilize pre-defined UTAD groups to assign users to the appropriate level of rights within the Radvision environment. The UTAD groups to be used, in order of increasing rights, are: Apps.Scopia.MeetingOrganizer Apps.Scopia.MeetingOperator Apps.Scopia.OrganizationalAdmin Regular User The Radvision system includes a basic user level, Regular User. Our policy is that all UTAD users, verified by LDAP queries from the Radvision Server, have the rights of a Regular User. This means that no separate UTAD group is necessary. These rights are: o Create and manage own meetings o View scheduled meetings o Receive and respond to meeting notices o Attend meetings o Moderate meetings o Modify own profile Meeting Organizer All members of the IT_All group will be assigned into the UTAD group Apps.Scopia.MeetingOrganizer. This gives those users the rights of a Regular User and these additions: o Manage own virtual room o Manage personal address book o Create and manage meetings for others o Option to add Pro or Mobile license Meeting Operator No one is defined into this group by default. Individuals who need the following rights for support and training of other users can be moved into the UTAD group Apps.Scopia.MeetingOperator.

2 o View and manage all meetings within the organization Organizational Administrator No one is defined into this group by default. Individuals who need to manage all associated hardware and system functionality will be moved into the UTAD group Apps.Scopia.OrganizationalAdmin. Summary This will allow for the dynamic maintenance of Radvision rights and privileges using the existing UTAD user management practices and tools. User s request to be elevated in rights will be forwarded to Collaborative Services after approval from an Organizational Admin.

3 Radvision Video Conferencing Policies and Procedures10/25/2012 2:02:00 PM End Point Setup The intent of this policy and procedures document is to standardize the configuration and application of video conferencing terminals, also known as end points, that are used as part of the Radvision system. Qualifications of end points Must be Ethernet IP based Must execute industry standardized H.323 functions Must send and receive H.263, H.264, or higher supported video Network Setup Set device to DHCP for network address information Set to synchronize date and time with ntp.utoledo.edu Set up on a minimum 100mb full duplex switched port H.323 Setup Register with vconf.utoledo.edu as its gatekeeper Set up E.164 name as EP- followed by the building and room# where the end point is located o E.g EP-UC1400C or EP-DOW025C Configure the E.164 ID as the 7 digit phone number associated with the room where the End Point is located. Set unit to use Shared Global Address book Unit Setup Set unit to auto-answer and auto mute Set camera default position For units up to 720p, set bandwidth to 2048k For units with 1080p capabilities, set bandwidth to 4096k Set and document a Username and/or Password on the unit iview setup An Organizational Admin will configure iview to link the end point with the UTAD defined resource for the room it s located in. Summary This will allow the end points to be directly dialed from other end points on the gatekeeper via the E.164 ID, e.g dial

4 This will allow the end points to be dialed from off-campus end points by using the E.164 ID and the gatekeeper IP. E.g dial or ## The units will also be able to be scheduled through either the iview gateway or the Outlook calendar system with the iview add-on.

5 Radvision Video Conferencing Policies and Procedures10/25/2012 2:02:00 PM Scopia Desktop and Scopia Mobile The intent of this policy and procedures document is to standardize the configuration and usage of the Desktop and Mobile clients that are a part of the Radvision system. Qualifications of client machines Desktop client must have Core 2 Duo processor or better Mobile client must be iphone 4 or newer (4s recommended) or ipad2 or newer Downloading and installing Scopia Desktop software Any user can go to and will be prompted to download the client software UTAD users may then proceed to Sign In and use the Update option to download additional software tools Client settings for bandwidth should be left at the defaults or at settings not to exceed 512k send and 2048k receive o These settings relate more to the CPU power of the machine than to network bandwidth available. 384k send 1536k receive is the most that a Core 2 Duo can encode. 512k send and 2048k receive should be used only with an i5 processor or better. Downloading and installing Scopia Mobile software Any user can go to the App Store to download and install the Scopia Mobile App In Settings, set up to use In Settings, UTAD users should enter their credentials Client Licensing

6 All UTAD users must enter their credentials when using the Desktop client since there is a limit on the number of Guests that can use the system. Regular users of the Mobile application should apply through a Help Desk ticket for a license to be issued to their account. All other users of the Mobile application are considered to be part of the limited Guest accesses.

7 End Point Rollout 10/25/ :06:00 AM End Point Rollout Identifier user(s) that will be scheduling meetings Move users into the Apps.Scopia.MeetingOrganizer UTAD group Install iview / Outlook plugin on user s account/machine Train.

8 iview Outlook Scheduling 10/25/ :06:00 AM