Scheduling Videoconferences Scheduling Videoconferences On An MCU On An MCU

Presented at theSURA/ViDe Digital Video Workshop

Atlanta, GeorgiaMarch 24-26, 2003

ByLarry Amiot

Northwestern Universityamiot@Northwestern.edu

To schedule, or not to schedule an To schedule, or not to schedule an MCU. That is the question!MCU. That is the question!

Several Choices:– Run the MCU in the Ad Hoc mode– Run the MCU in the scheduled mode– Perhaps a partitioned mode with both ad hoc and

scheduled capabilities

MCU SchedulingMCU Scheduling

Advantages:– Good management practices– Control who can use the MCU and when– Make sure MCU resources are available when

needed– Provide usage statistics– Provide means to charge for usage– Can be combined with room scheduling– Provides notification and information to

conference chair– Better security- restrict number of users

MCU SchedulingMCU Scheduling

Disadvantages:– Need to create or buy MCU vender or third

party scheduling software- cost– Need to provide method to collect information

relative to request- user effort– Requires administrative effort if not fully

automated– Adds complexity to testing procedures– Adds administrative burden to conference chair

SchedulingScheduling the MCU the MCU

Two choices:– Buy commercial scheduling software– Write your own software

A

P

I

MCU

Commercial Scheduling Software

MCU Control Software

•Calendaring,

•Room Scheduling,

•MCU Scheduling,

•Resource management,

•User management

Administrators and/or Users

Email/ Web Interface

Using Commercial Software

Write Your Own SoftwareWrite Your Own Software

Advantages:– Tailored to your needs– Describes your resources not generalized

resources– Extends organization’s existing Web pages– Saves software and maintenance costs– Provides appropriate user interface– Provides appropriate user notification– Not tied to commercial scheduling software

changes

Write Your Own SoftwareWrite Your Own Software

Disadvantages:– Takes effort to develop– Takes effort to maintain– Need MCU vendor to provide API– Need MCU vendor to provide information on

API– Need to keep current with vendor changes to

MCU

NU Design GoalsNU Design Goals

Utilize and extend existing IT videoconferencing Web pages

Keep the Web form as simple as possibleSchedule the MCU- No ad hoc sessions

– Specified session size– Single or quad split screens– Date and start/end time– Conference number

Optionally, schedule NU public videoconferencing rooms

NU Design Goals (Continued)NU Design Goals (Continued)

Eliminate, where possible, AT involvement in the scheduling process (self service)

Provide Administrative Interface– Schedule sessions on-the-fly– Change session parameters– Terminate sessions– Get session/participant information– Session chair authentication

A

P

I

Radvision MCU

Existing NU Web Pages

•NU MCU Controller

•Calendaring,

•Room Scheduling,

•MCU Scheduling,

•Resource management,

•Plus more

Users

Admin Interface

Administrators

Northwestern Developed Scheduling System

NU MCU Controller DesignNU MCU Controller Design

Implemented in JavaCan support multiple MCUsModular to support other manufacturer

MCUs- requires new driverMCU definitions in configuration fileAccepts Cold Fusion Tags as input

NU MCU Controller DesignNU MCU Controller Design

Allows specified session to be terminatedUses Radvision API XML InterfaceUtilizes TCP/IP for sending commands to

APIAllows session to be created with specified

– MCU service (quad split, single screen, etc.)– Conference dial number, and– number of participants

NU MCU Controller DesignNU MCU Controller Design

Allows participant(s) information to be retrieved

Allows conference(s) information to be retrieved

Things We Didn’t Implement– Dial participants– Session management– Ability for conference chair to modify

schedule parameters

NU MCU Controller DesignNU MCU Controller Design

A Few Issues– Setup/break down time– Additions to conference– MCU session termination after idle time– Interaction between API and MCU Web

interface administrators

User ProcedureUser Procedure

User fills out form on IT Web siteUsers requests IT public room if required

after checking scheduleConference number dynamically assigned

on Web formUser can request help if needed

User Procedure (Continued)User Procedure (Continued)

Email notification automatically sent to NU videoconferencing administrators, NU conference chair, and remote users

MCU session automatically scheduled at appointed time and terminated at appropriate time

AT video staff can intervene if:– Help requested– Conflicts arise– If changes required (time, number of

participants, etc)

Northwestern University Northwestern University Videoconferencing Web PageVideoconferencing Web Page

http://www.at.northwestern.edu/ctg/http://www.at.northwestern.edu/ctg/videoconf/default.ssivideoconf/default.ssi

Credit To Other NU StaffCredit To Other NU Staff

Eric DvorakGretchen GuoChris Karr

Questions?Questions?