View source for SIP vs H323

([http://www.en.voipforo.com/H323vsSIP.php Source])

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]