SIP vs H323 - Revision history

Gijs: /* Links */

2007-02-20T07:54:23Z

Links

Gijs at 15:28, 19 February 2007

2007-02-19T15:28:43Z

Gijs at 15:26, 19 February 2007

2007-02-19T15:26:23Z

Gijs at 15:22, 19 February 2007

2007-02-19T15:22:03Z

Gijs at 15:13, 19 February 2007

2007-02-19T15:13:20Z

Gijs at 14:57, 19 February 2007

2007-02-19T14:57:25Z

Gijs at 14:48, 19 February 2007

2007-02-19T14:48:26Z

Fabio at 13:31, 1 February 2007

2007-02-01T13:31:08Z

Rubzzzz at 12:52, 1 February 2007

2007-02-01T12:52:48Z

New page

[http://scholar.google.com/scholar?hl=en&lr=&q=cache:saYycJvXDZcJ:www.ss7.co.kr/reference/data/voip/Comparison%2520of%2520H.323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998),+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]

← Older revision		Revision as of 07:54, 20 February 2007
Line 167:		Line 167:
	*[http://scholar.google.com/scholar?hl=en&lr=&q=cache:saYycJvXDZcJ:www.ss7.co.kr/reference/data/voip/Comparison%2520of%2520H.323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998),+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]		*[http://scholar.google.com/scholar?hl=en&lr=&q=cache:saYycJvXDZcJ:www.ss7.co.kr/reference/data/voip/Comparison%2520of%2520H.323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998),+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]
	*[http://www.sipcenter.com/sip.nsf/html/H.323+Background Overview SIP vs H323]		*[http://www.sipcenter.com/sip.nsf/html/H.323+Background Overview SIP vs H323]
		+	* [http://www.vcon.com/pdfdoc/eng/wp/050214_SIP-H.323%20Convergence.pdf Discussion about Sip and H323] - Note: not entirely objective, because this vendor also sells H323 devices.

@@ Line 13: / Line 13: @@
 |-
 |rowspan="2"|Components
-|Terminal/Gateway
+|allign="center"|Terminal/Gateway
-|UA
+|allign="center"|UA
 |-
-|Gatekeeper
+|allign="center"|Gatekeeper
-|Servers
+|allign="center"|Servers
 |-
 |rowspan="2"|Protocols
-|RAS/Q.931
+|allign="center"|RAS/Q.931
-|SI
+|allign="center"|SI
 |-
-|H.245
+|allign="center"|H.245
-|SDP
+|allign="center"|SDP
 |-
 |colspan="3" style="color:#ff0000;"|<big>Call control Functionality</big>
 |-
 |Call Transfer
-|Yes
+|allign="center"|Yes
-|Yes
+|allign="center"|Yes
 |-
 |Call Forwarding
-|Yes
+|allign="center"|Yes
-|Yes
+|allign="center"|Yes
 |-
 |Call Holding

@@ Line 8: / Line 8: @@
 ! SIP
 |-
-|style="color:#ff0000;"|Architecture
+|style="color:#ff0000;"|<big>Architecture</big>
 |H.323 covers almost every service, such as capability exchange, conference control, basic signaling,QoS, registration, service discovery, and so on.
 | SIP is modular because it covers basic call signaling, user location, and registration.  Other features are in other separate orthogonal protocols
@@ Line 26: / Line 26: @@
 |SDP
 |-
-|colspan="3" style="color:#ff0000;"|Call control Functionality
+|colspan="3" style="color:#ff0000;"|<big>Call control Functionality</big>
 |-
 |Call Transfer
@@ Line 72: / Line 72: @@
+|
 |-
-|colspan="3" style="color:#ff0000;"|Advanced features
+|colspan="3" style="color:#ff0000;"|<big>Advanced features</big>
 |-
 |Multicast Yesgnaling
@@ Line 90: / Line 90: @@
 |Yes
 |-
-|colspan="3" style="color:#ff0000;"|Scalability
+|colspan="3" style="color:#ff0000;"|<big>Scalability</big>
 |-
 |Large Number of Domains
@@ Line 108: / Line 108: @@
 |Yes, SIP uses Unicode (ISO 10646-1), encoded as UTF-8, for all text strings, affording full character set neutrality for names, messages and parameters. SIP provides for the indication of languages and language preferences.
 |-
-|style="color:#ff0000;"|Security
+|style="color:#ff0000;"|'''Security'''
 |Defines security mechanisms and negotiation facilities via H.235 , can also use SSL for transport-layer security.
 |SIP supports caller and callee authentication via HTTP mechanisms. Cryptographically secure authentication and encryption is supported hop-by-hop via SSL/TSL, but SIP could use any transport-layer or HTTP-like security mechanism, such as SSH or S-HTTP. Keys for media encryption are conveyed using SDP. SSL supports symmetric and asymmetric authentication. SIP also defines end-to-end authentication and encryption using either PGP or S/MIME.
 |-
-|style="color:#ff0000;"|Interoperability among Versions
+|style="color:#ff0000;"|'''Interoperability among Versions '''
 |The fully backward compatibility in H.323 enables all implementations based on different H.323 versions to be seamlessly integrated.
 |In SIP, a newer version may discard some old features that are not expected to be implemented any more. This approach saves code size and reduces protocol complexity, but loses some compatibility between different versions.
 |-
-|style="color:#ff0000;"|Implementation Interoperability
+|style="color:#ff0000;"|'''Implementation Interoperability '''
 |H.323 provides an implementers' guide, which clarifies the standard and helps towards interoperability among different implementations.
 |SIP thus far has not provided an implementation agreement.
 |-
-|style="color:#ff0000;"|Billing
+|style="color:#ff0000;"|'''Billing '''
 |Even with H.323's direct call model, the ability to successfully bill for the call is not lost because the endpoint reports to the gatekeeper the beginning and end time of the call via the RAS protocol.
 |If the SIP proxy wants to collect billing information, it has no choice but to stay in the call signaling path for the entire duration of the call so that it can detect when the call completes. Even then, the statistics are skewed because the call signaling may have been delayed.
 |-
-|style="color:#ff0000;"|Codecs
+|style="color:#ff0000;"|'''Codecs '''
 |H.323 supports any codec, standardized or proprietary, not just ITU-T codecs. There have been codepoints for MPEG and GSM, which are not ITU-T codecs, in H.323 for a long time; many vendors support proprietary codecs through ASN.1 NonStandardParameters, which is equivalent to SIP's "privately-named codec by mutual agreement"; and any codec can be signaled via the GenericCapability feature that was added in H.323v3. Payload types can be specified statically or dynamically.
 |SIP supports any IANA-registered codec (as a legacy feature) or other codec whose name is mutually agreed upon. Payload types can be specified statically or dynamically
 |-
-|style="color:#ff0000;"|Call Forking
+|style="color:#ff0000;"|'''Call Forking'''
 |H.323 gatekeeper can control the call signaling and may fork the call to any number of devices simultaneously.
 |SIP proxies can control the call signaling and may fork the call to any number of devices simultaneously.
 |-
-|style="color:#ff0000;"|Transport Protocol
+|style="color:#ff0000;"|'''Transport Protocol'''
 |Reliable or unreliable , e.g., TCP or UDP. Most H.323 entities use a reliable transport for signaling.
 |Reliable or unreliable , e.g., TCP or UDP. Most SIP entities use an unreliable transport for signaling.
 |-
-|style="color:#ff0000;"|Message Encoding
+|style="color:#ff0000;"|'''Message Encoding'''
 |H.323 encodes messages in a compact binary format that is suitable for narrowband and broadband connections.
 |SIP messages are encoded in ASCII text format, suitable for humans to read.
 |-
-|style="color:#ff0000;"|Addressing
+|style="color:#ff0000;"|'''Addressing '''
 |Flexible addressing mechanisms, including URLs and E.164 numbers.
 |SIP only understands URL-style addresses.
 |-
-|style="color:#ff0000;"|PSTN Interworking
+|style="color:#ff0000;"|'''PSTN Interworking'''
 |H.323 borrows from traditional PSTN protocols, e.g., Q.931, and is therefore well suited for PSTN integration. However, H.323 does not employ the PSTN's circuit-switched technology--like SIP, H.323 is completely packet-switched. How Media Gateway Controllers fit into the overall H.323 architecture is well-defined within the standard.
 |SIP has no commonality with the PSTN and such signaling must be "shoe-horned" into SIP. SIP has no architecture that describes the decomposition of the gateway into the Media Gateway Controller and the Media Gateways.
 |-
-|style="color:#ff0000;"|Loop Detection
+|style="color:#ff0000;"|'''Loop Detection'''
 |Yes, routing gatekeepers can detect loops by looking at the CallIdentifier and destinationAddress fields in call-processing messages. If the combination of these matches an existing call, it is a loop.
 |Yes, the SIP message Via header facilitates this. However, there has been talk about deprecating Via as a means of loop detection due to its complexity. Instead, the Max-Forwards header seems to be the prefered method of limiting hops and therefore loops.
 |-
-|style="color:#ff0000;"|Minimum Ports for VoIP Call
+|style="color:#ff0000;"|'''Minimum Ports for VoIP Call'''
 |5 (Call signaling, 2 RTP, and 2 RTCP.)
 |5 (Call signaling, 2 RTP, and 2 RTCP.)
 |-
-|style="color:#ff0000;"|Video and Data Conferencing
+|style="color:#ff0000;"|'''Video and Data Conferencing'''
 |H.323 fully supports video and data conferencing. Procedures are in place to provide control for the conference as well as lip synchronization of audio and video streams.
 |SIP has limited support for video and no support for data conferencing protocols like T.120. SIP has no protocol to control the conference and there is no mechanism within SIP for lip synchronization.

@@ Line 107: / Line 107: @@
 |Yes, H.323 uses Unicode (BMPString within ASN.1) for some textual information (h323-id), but generally has few textual parameters.
 |Yes, SIP uses Unicode (ISO 10646-1), encoded as UTF-8, for all text strings, affording full character set neutrality for names, messages and parameters. SIP provides for the indication of languages and language preferences.
 |-
 |}

@@ Line 8: / Line 8: @@
 ! SIP
 |-
-|Architecture
+|style="color:#ff0000;"|Architecture
 |H.323 covers almost every service, such as capability exchange, conference control, basic signaling,QoS, registration, service discovery, and so on.
 | SIP is modular because it covers basic call signaling, user location, and registration.  Other features are in other separate orthogonal protocols
 |-
-|Components
+|rowspan="2"|Components
 |Terminal/Gateway
 |UA
 |-
 |Gatekeeper
 |Servers
 |-
-|Protocols
+|rowspan="2"|Protocols
 |RAS/Q.931
 |SI
 |-
 |H.245
 |SDP
 |-
-|Call control Functionality
+|colspan="3" style="color:#ff0000;"|Call control Functionality
 |-
 |Call Transfer
 |Yes
 |Yes
 |-
 |}

@@ Line 3: / Line 3: @@
 H.323 is the more mature of the two, but problems may arise due to lack of flexibility.  SIP is currently less defined, but has greater scalability which could ease internet application integration. Which protocol will win out in the end?  It is still too early to tell, but our unbiassed analysis will help you decide which protocol best suites your application.
-{| border="1" cellspacing="0"
+{| border="1" cellspacing="0" allign="center"
+!
 ! H.323
@@ Line 19: / Line 19: @@
 |Gatekeeper
 |Servers
 |-
 |}

← Older revision		Revision as of 14:48, 19 February 2007
Line 1:		Line 1:
−	[http://~~scholar~~.~~google.com/scholar?hl=~~en~~&lr=&q=cache:saYycJvXDZcJ:www~~.~~ss7~~.~~co.kr~~/~~reference/data/voip/Comparison%2520of%2520H~~.~~323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998~~)~~,+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]~~	+	([http://www.en.voipforo.com/H323vsSIP.php Source])

−	[http://www.sipcenter.com/sip.nsf/html/H.323+Background Overview SIP vs H323]	+	H.323 is the more mature of the two, but problems may arise due to lack of flexibility. SIP is currently less defined, but has greater scalability which could ease internet application integration. Which protocol will win out in the end? It is still too early to tell, but our unbiassed analysis will help you decide which protocol best suites your application.
		+
		+	{\| border="1" cellspacing="0"
		+	!
		+	! H.323
		+	! SIP
		+	\|-
		+	\|Architecture
		+	\|H.323 covers almost every service, such as capability exchange, conference control, basic signaling,QoS, registration, service discovery, and so on.
		+	\| SIP is modular because it covers basic call signaling, user location, and registration. Other features are in other separate orthogonal protocols
		+	\|-
		+	\|Components
		+	\|Terminal/Gateway
		+	\|UA
		+	\|-
		+	\|
		+	\|Gatekeeper
		+	\|Servers
		+	\|-
		+	\|}
		+
		+
		+	== Links ==
		+
		+	*[http://scholar.google.com/scholar?hl=en&lr=&q=cache:saYycJvXDZcJ:www.ss7.co.kr/reference/data/voip/Comparison%2520of%2520H.323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998),+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]
		+	*[http://www.sipcenter.com/sip.nsf/html/H.323+Background Overview SIP vs H323]

← Older revision		Revision as of 13:31, 1 February 2007
Line 1:		Line 1:
	[http://scholar.google.com/scholar?hl=en&lr=&q=cache:saYycJvXDZcJ:www.ss7.co.kr/reference/data/voip/Comparison%2520of%2520H.323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998),+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]		[http://scholar.google.com/scholar?hl=en&lr=&q=cache:saYycJvXDZcJ:www.ss7.co.kr/reference/data/voip/Comparison%2520of%2520H.323%2520and%2520SIP.pdf+ITU-T+Recommendation+H.245+(1998),+Control+protocol+for+multimedia+communication. Comparison of H323 and SIP]
		+
		+	[http://www.sipcenter.com/sip.nsf/html/H.323+Background Overview SIP vs H323]