Multimedia Networking

7.4.4 H.323

Home
Introduction
7.1 Multimedia Networking Applications
7.1.1 Examples of Multimedia Applications
7.1.2 Hurdles for Multimedia in Today's Internet
7.1.3 How Should the Internet Evolve to Support Multimedia Better?
7.1.4 Audio and Video Compression
7.2 Streamimg Stored Audio and Video
7.2.1 Accessing Audio and Video Through a Web Server
7.2.2 Sending Multimedia from a Streaming Server to a Helper Application
7.2.3 Real-Time Streaming Protocol (RTSP)
7.3 Making the Best of the Best-Effort Service: An Internet Phone Example
7.3.1 The Limitations of a Best-Effort Service
7.3.2 Removing Jitter at the Receiver for Audio
7.3.3 Recovering from Packet Loss
7.4 Protocols for Real-Time Interactive Applications
7.4.1 RTP
7.4.2 RTP Control Protocol (RTCP)
7.4.3 SIP
7.4.4 H.323
7.5 Distributing Multimedia: Content Distribution Networks
7.6 Beyond Best Effort
7.6.1 Scenario 1: A 1 Mbps Audio Application and an FTP
7.6.2 Scenario 2: A 1 Mbps Audio Application and a High-Priority FTP Transfer
7.6.3 Scenario 3: A Misbehaving Audio Application and an FTP Transfer
7.6.4 Scenario 4: Two 1 Mbps Audio Applications over an Overload 1.5 Mbps Link
7.7 Scheduling and Policing Mechanisms
7.7.1 Scheduling Mechanisms
7.7.2 Policing: The Leaky Bucket
7.8 Intergrated Services and Differentiated Services
7.8.1 Intserv
7.8.2 Diffserv
7.9 RSVP
7.9.1 The Essence of RSVP
7.9.2 A Few Simple Examples
H.323

kurose_320719_c07f15.gif

As an alternative to SIP, H.323 is a popular standard for real-time audio and video conferencing among end systems on the Internet.  The H.323 gatekeeper is a device similar to an SIP register.
 
The H.323 standard is an umbrella specification that includes the following specifications:
  • A specification for how endpoints negotiate common aufio/video encodings.
  • A specification for how audio and video chunks are encapsulated and sent over the network.
  • A specification for how endpoints communicate with their respective gatekeepers.
  • A specification for how Internet phones communicate through a gateway with ordinary phones in the public circuit-switched telephone network.
 
Each H.323 endpoint must support the G.711 speech compression standard.  G.711 uses PCM to generate digitized speech at either 56 kbps or 64 kbps.  Although H.323 requires every endpoint to be vioce capable, video capabilities are optional.
 
H.323 is a comprehensive umbrella standard, which, in addition to the standards and protocolsmandates a H.245 control protocol, a Q.931 signaling channel, and anRAS protocol for registration with the gatekeeper.
 
Some of the most important differences between H.323 and SIP:
  • H.323 is a complete, vertically integrated suite of protocols for multimedia conferencing: signaling, registration, admission control, transport, and codes.
  • SIP addresses only session initiation and management and is a single component.
  • H.323 comes from the ITU, whereas SIP comes from the IETF and borrows many comcepts from the Web, DNS, and Internet e-mail.
  • H.323 is large and complex.  Sip uses the KISS principle: keep it simple, stupid.