A conference gateway supporting interoperability between SIP and H.323

Authors:
Jiann-Min Ho;Jia-Cheng Hu;Peter Steenkiste
Affiliations:
Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA
Venue:
MULTIMEDIA '01 Proceedings of the ninth ACM international conference on Multimedia
Year:
2001

Citing 4
Cited 2

An application level video gateway

Proceedings of the third ACM international conference on Multimedia
vic: a flexible framework for packet video

Proceedings of the third ACM international conference on Multimedia
The conference control channel protocol (CCCP): a scalable base for building conference control applications

SIGCOMM '95 Proceedings of the conference on Applications, technologies, architectures, and protocols for computer communication
KHIP—a scalable protocol for secure multicast routing

Proceedings of the conference on Applications, technologies, architectures, and protocols for computer communication

Modelling and verification of interworking between SIP and H.323

Computer Networks: The International Journal of Computer and Telecommunications Networking
A Methodology for SIP and SOAP Integration Using Application-Specific Protocol Conversion

ACM Transactions on the Web (TWEB)

Quantified Score

Hi-index	0.00

Visualization

Abstract

Increased network bandwidth is making desktop video conferencing an attractive application for an increasing number of computer users. Unfortunately, two competing standards for video conferencing signaling are in use, H.323 and SIP. In this paper we look at the interoperability between these two standards by developing a conferencing gateway that supports conferences involving both SIP and H.323 clients. By appropriately translating between H.323 and SIP operations, our prototype gateway supports basic multi-party video conferencing between NetMeeting (an H.323 client) and VIC (a SIP client) without modifications to the clients. However, our experiments also show that seamless interoperation would require changes to the client implementations and the standards.