Jamie Sunderland 24082006

1
Jamie Sunderland24/08/2006

• Desktop Videoconferencing service pilot.

2
Background

• Why desktop videoconference?
• Strong interest from
• DVC International
• PVC Campus Coordination
• Researchers, academics and research groups.
• Some senior management committees
• Some teaching academics
• Perceived benefits
• Greater interaction between Victorian campuses,
  with international campuses and Other
  University/research organisations
• Ability to attend international online
  conferences on an ad-hoc basis
• Reduced risks and costs associated with travel
• Enhances student/staff mobility by supporting
  communications with their home campus/country.
  (Perhaps IM is actually more important here?)

3
Why a separate Desktop-VC pilot now?

• WCR will establish integrated tools
• for both Synchronous and Asynchronous
  collaboration and communication.
• NIS will also establish infrastructure
• for enhanced IP communications (which will
  include infrastructure to support Voice-over-IP
  and Video-IP. This has already started with QoS
  and moving inter PABX trunks off the ATM network.
• Neither of them are likely to deliver end-user
  desktop videoconferencing in 2007 (as there is
  much groundwork to be done and higher priorities
  to attack first)

4
Desktop VC Service H.323 Gatekeeper/ proxy and
Address book
I-comms scoping
Now
WCR (Decision) WCR Licence Neg
I-comms project preparation
WCR Preparation
Dec06
Firewall project
I-comms infrastructure development (SIP and
H.323 based)
WCR Directory, Mail and Calendar
Jun07
Dec07
WCR Web collaboration enhanced tools
I-comms applications and user devices
Jun08
5
Desktop VC Pilot project

• Project Website
• http//www.its.monash.edu/staff/projects/desktop-v
  c/
• Key Deliverables
• Virtual exchange/proxy for standards based H.323
  videoconferencing (including NACP/QoS issues)
• Central Directory of videoconference
  users/end-points
• Directory linking to AARNet, Global Directory
  System and Global numbering schemes.
• Pre-configured Windows client and published
  instructions for leading clients such as
  Gnomemeeting/Ekiga (linux) and Xmeeting (OS-X).

6
Draft Project Plan / Timeline estimate

• Establish Sever, client and network
  infrastructure.
• Link into directory service
• Alpha-pilot with first group to test different
  network scenarios and general end-user
  acceptance.
• Survey before snapshot with proposed beta
  group.
• Beta-test business impact of staged pilot.
• Service review Recommend improvements or changed
  required to move into a production service
• Communications plan and move to production early
  2007.

August September October November December
7
Desktop VC

• Comments / Queries
• Jamie Sunderland
• Paul Hii

8
AARNet Multipoint Bridge

• Web booking system
• IVR welcome
• Direct dialling - 1number for each conference
• Multi-speed, Multi-protocol. VOIP/POTS
• Up to 16 users on a screen, multiple layouts
• End-user custom layouts
• Streaming via Quicktime/RealMedia
• http//www.aarnet.edu.au/services/video/

9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)