• Journal of Internet Computing and Services
    ISSN 2287 - 1136(Online) / ISSN 1598 - 0170 (Print)
    http://jics.or.kr/

Design Call Control of Mechanism for Multiparty Conference in SIP and Case Study


Jeong Dong-Youl, Min Jun-Sik, Cheon Suh-Hyun, Journal of Internet Computing and Services, Vol. 4, No. 5, pp. 77-86, Oct. 2003
Full Text:
Keywords: SIP, H.323, Video Conferencing

Abstract

This paper introduces the extension of SIP protocol for Multiparty Conference and the implementation of IP-based Multi-Conference. SIP protocol is a signaling protocol for initiating, modifying and terminating interactive sessions (voice, video, text, application). Multiparty conference system is implemented by RTP protocol for real time transmission and by H.323 for call setup. As H.323 fits into PSTN, it has some problems (call setup delay, hard implementation) for IP applications. IETF developed SIP protocol used for signaling in IP networks. However this SIP protocol doesn't explain signal protocol about multimedia conference, which is different from the existing H.323. So this paper describes the extension of SIP according to SIP Specification and case study for the multimedia conference.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from November 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[APA Style]
Jeong Dong-Youl, Min Jun-Sik, & Cheon Suh-Hyun (2003). Design Call Control of Mechanism for Multiparty Conference in SIP and Case Study. Journal of Internet Computing and Services, 4(5), 77-86.

[IEEE Style]
J. Dong-Youl, M. Jun-Sik and C. Suh-Hyun, "Design Call Control of Mechanism for Multiparty Conference in SIP and Case Study," Journal of Internet Computing and Services, vol. 4, no. 5, pp. 77-86, 2003.

[ACM Style]
Jeong Dong-Youl, Min Jun-Sik, and Cheon Suh-Hyun. 2003. Design Call Control of Mechanism for Multiparty Conference in SIP and Case Study. Journal of Internet Computing and Services, 4, 5, (2003), 77-86.