H.323 Transition Strategies

Download Report

Transcript H.323 Transition Strategies

Rolling Out A Statewide H.323 Network
Technology Timeline
Quick Facts
• First PC based system: Intel
TeamStation, Spring 1997
• OneNet first regularly scheduled H.323
class: two TeamStations, Aug 1997
• By Feb 1999, 400 TeamStations were in
service in Oklahoma with over 1000
class sessions each week on OneNet
• Today there are over 1500 Polycom
units that have been purchased on state
contracts.
Testing…and more testing
• Types of endpoints tested: Gentner,
Intel, Microsoft, PictureTel,
Polycom, Sony, Tandberg, VCon,
Vtel
• Types of MCU tested:
Accord, PictureTel, Radvision,
VideoServer/Ezenia, WhitePine,
MCU Selection
• OneNet had an existing group of
application services provided via Sun
servers distributed around the state.
• Selecting a software based MCU made
sense with this consideration and the
strong regional distance learning alliances
that were already established.
• Purchased 350 ports of WhitePine and
dynamically allocate them based on need
or bell-schedules.
MCU
• FVC Conference Server (formerly
known as CUSeeMe Conference
Server, formerly known as White Pine
MeetingPoint Conference Server.)
• Runs on Solaris
• Web Interface Control
• Located at 35 hubsites
• Currently restrict conferences to G.711
and H.261 for compatibility
Endpoint Selection
Established categories:
1) Add-on card or device to an
existing PC
2) Dedicated PC system
3) Closet codec
4) Set-top appliance
Interoperability Strategy
• Test basic functionality between
endpoints in point-to-point
configuration
• Test multipoint with CUSeeMe
MCU (MeetingPoint) (Set to H.261
and G.711)
Interoperability Testing
• Each endpoint is connected using four
different speeds.
• Protocols are noted.
• Protocol mismatch situations are noted
(even when legal).
• Objective and subjective quality notes
are recorded.
• Each endpoint is connected as
originator as well as receiver.
Gatekeeper
• We use the Cisco MCM gatekeeper
• Runs on Cisco 3620 router
• Endpoint must be registered to use
our MCUs
• Acts as a translator for aliases
• Member of ViDe
Gateway
• OneNet does not provide Gateway
service.
• Both growth and standardization
goals were served by this strategy.
• One of our universities, OSU,
provides gateway service when
needed.
Directory Services
OneNet offers four solutions:
• Web access to database with list of
registered H.323 units and contacts.
• ‘Looking glass’ access to gatekeeper
with list of all registered endpoints.
• ILS Server
• Polycom Global Address Book
• Reviewing Click to Meet
Dialing Plan
• OneNet H.323 endpoint aliases follow a
general form that is customized for the
type of institution.
– K-12 maude_ps_102
– CT kiamichi_mcalester_312
– UNI casc_nursing_221
• OneNet H.323 MCU aliases are
assigned when a conference room is
created. Integrates course information.
MCU Scheduling
• Using an online form users are able to
request a conference room with its own
alias that will last an entire semester.
• Each class is assigned its own
conference room to track MCU usage
and assure compliance with licensing.
• Setup impromptu conferences that an
institution may use for a single meeting
that falls outside of normal class
session conferences.
Ramping Up
 Established an interoperability lab and staffed
it with 1-1/2 FTEs during the roll out phase to
evaluate hardware, software and develop
operating processes and procedures.
 Built a 350 port distributed MCU and put
three FTEs in place to manage it and to
provide help desk services for classrooms.
 Negotiated contracts for purchase of H.323
codecs and classroom equipment.
Endpoint/MCU Distribution
Implementation Strategies
• We do not control the endpoints
and rooms.
• Our members can purchase, setup
and connect an endpoint without
our knowledge.
• For some members, we encourage
the use of internal MCUs when
available.
Shifting viewpoints
 Video and data networks have
traditionally been separate worlds.
 In a good H.323 world, networks must
work together and so must the
professionals.
 Distance learning departments must
learn to cooperate with IT departments.
IT departments must realize how good
quality video can benefit their
organizations.
Different needs
 K-12s have a great need for the technology to
be invisible. Simpler systems seem to be
preferred.
 Some users are under statutory requirements
for the instructor to be able to always see the
students in all remote rooms. Quad-split
screens or multiple screens help.
 Technical users are more likely to utilize
T.120.
 Legacy distance learning users just want to
plug in a new codec and have it work.
Infrastructure concerns
 Networks have long been designed to take
advantage of bursty nature of traffic, giving
the provider the ability to over subscribe the
network.
 H.323 (and P2P file transfer applications)
have all but eliminated this bursty
characteristic. Over subscriptions must now
be reduced to much smaller numbers. Much
larger circuits are now required throughout
the infrastructure.
H.323 Transition Strategies
• Members are not forced to leave the previous
technology.
• Most were using Grass Valley systems, a
proprietary system which used DS3 transport.
• H.323 can be provided by less expensive T1s
or make the DS3 available wholly for IP
• As H.323 has grown several times larger,
more locations are available for connection
using H.323.
• Possible applications grow with the number of
endpoints
Technical Support
• OneNet provides video technical
support for its members in a
generous, but limited fashion.
• Work largely with interest groups
responsible for large subsets of our
membership. They assist individual
institutions in resolving many
issues.
H.323 Troubleshooting
• Many problems exhibit similar
symptoms.
• When troubleshooting H.323, it is
helpful, and often necessary to
have the LAN network admin in the
room with the DL coordinator.
QoS Needs
• Video Conferencing
– H.323
– MPEG
• Video Streaming
• P2P File Sharing
– KaZaA
– Gnutella
– All the rest…
• Distributed-FTP
It All Adds Up Quickly
Examples
• We now have over 800 H.323 endpoints
officially registered as distance learning
classrooms.
• Every higher education institution is wiring
their dorms or building new dorms to be
wired.
• Local expertise in many of our members’
networks regarding traffic management is
somewhat limited, new hip applications can
quickly congest links.