Comparing H.323 Vs. SIP: What's The Difference? - TechTarget

H.323 vs. SIP comparison

As H.323 and SIP were developed by different standards-setting bodies, they have evolved in different ways. While they aim to achieve the same goal of transmitting rich media over IP networks, they have different capabilities.

ArchitectureH.323 has a very well-defined architecture, which includes rules for implementing features and requirements for specific components of an H.323-based service. These components include the following:

• Terminals that are the endpoints in an H.323 service.
• Gateways that allow interconnection between H.323- and non-H.323-based endpoints. For example, a gateway could allow a public switched telephone network (PSTN)- or SIP-based phone to connect to an H.323 conference.
• Gatekeepers that control sessions and manage bandwidth by limiting the number of participating endpoints. Gatekeepers are optional, but most endpoints must use them if they are present.
• Multipoint control units, which serve as the hub for interconnecting three or more terminals. MCUs receive voice and video from terminals and distribute media out to other terminals participating in a conference.

SIP loosely defines the way endpoints connect to each other. It includes the ability for developers to define options for video and video codecs and security. The protocol also offers flexibility for developers to create additional features. Key SIP components include the following:

• user agents, which are endpoints like phones and video conferencing apps or platforms; and
• intermediaries that allow scaling of conferencing, administration and security, and gateway functions. SIP intermediaries include the following:
• proxy servers to support features like discovery of endpoints, policy enforcement, multipoint control and endpoint registration;
• redirect servers to route SIP session requests to alternative endpoints based on policy, such as routing an incoming call to a backup phone or contact center; and
• back-to-back user agents to enable insertion of devices into a SIP session for security, policy or gateway functionality.

Session Description Protocol (SDP) is core to SIP as it defines the characteristics of a session. SDP enables the use of encryption, transport protocol, the selection of voice and video codecs, and compression.

ReliabilityBoth protocols offer reliable means to establish sessions, as they support the use of TCP to ensure delivery of session setup and control messages between endpoints and intermediaries.

SIP reliability, however, is dependent on the design of the application, and the potential use of intermediaries to prevent introducing new sessions or endpoints onto a congested network.

SecurityMost H.323 implementations support H.325 for encryption of signaling and media streams, like voice and video. SIP supports the use of HTTPS to encrypt all session management messages, typically on IP Port 5161. SIP implementations may also define encryption of media streams.

ScalabilityBoth H.323 and SIP are extremely scalable. H.323, however, has strict server requirements, which can make a large H.323 implementation more costly and complex. H.323's inherent traffic management capabilities, such as load balancing across gatekeepers and strict call admission control, mean that it will prevent session creation when the network is unable to support the desired session.

SIP lacks inherent control functions, but it provides the flexibility for application developers to implement their own approaches for call admission control and scalability. SIP session setup, management, and teardown typically require less network traffic than H.323.

In addition, SIP messages incorporate the IP addresses of the sender and receiver of a session request into the SIP header, creating difficulties in establishing sessions across network address translation boundaries. Its lack of tightly-defined service implementations -- unlike H.323 -- means not all instances of SIP are interoperable and supporting SIP across firewalls is problematic. For that reason, many enterprises deploy session border controllers, which are SIP-optimized devices, to manage security, protocol translation and policy enforcement between SIP instances.

Call SetupH.323 call setup is handled by gatekeepers that receive session setup requests and join appropriate endpoints.

SIP setup is either direct between endpoints, if one endpoint knows the IP address and can directly reach another, or through gatekeepers. A SIP terminal sends a session initiation request to the gatekeeper, which forwards the request to the destination terminal. The destination terminal responds to the request, and both terminals use SDP to negotiate the characteristics of the session.