• 11. Riadul Mannan (mrmannan@sfu.ca), Mahmood Riyadh(mmriyadh@sfu.ca), and Shufang Wu(vswu@sfu.ca)

    Implementation and Analysis of Megaco/H.248 Protocol Using OPNET

    [Description] Megaco/H.248 Protocol is a media gateway control protocol. Media gateway control protocols were established for the need of IP networks to interwork with traditional telephony systems and provide support for large-scale phone-to-phone deployments. Media gateway control protocols specify a master/slave architecture for decomposed gateways, in which Media Gateway Control (MGC) is the master server, and one or more Media Gateways (MGs) are the slave clients that behave like simple switches. One MGC can serve many MGs. While some other multimedia over IP protocols like Session Initiation Protocol (SIP) and H.323 are based on a peer-to-peer architecture.

    Currently the best-known media gateway control protocols are Media Gateway Control Protocol (MGCP) and Megaco/H.248. MGCP was published as informational RFC2705 and has been widely deployed. As an evolution of MGCP conceptually, Megaco/H.248 is expected to win wide industry acceptance as the official standard because it is a collaborative effort of the Internet Engineering Task Force (IETF) and International Telecommunication Union (ITU), following an agreement by both bodies to cooperate on a single unified protocol.

    In our project, we will implement an environment using OPNET to simulate Megaco/H.248. One MGC and two MGs will be in it. Also, we will implement some Megaco/H.248 commands on top of User Datagram Protocol (UDP) between MG and MGC that are required for basic call flows to demonstrate the functions of Megaco/H.248. The voice traffic between two MGs will be simulated using Real-time Transport Protocol (RTP). Finally, we will give out some statistical analysis on various network performance parameters, such as call setup time and average delay per call experienced by media packets.

    [References]

  • 1. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", RFC 1889, January 1996. http://www.ietf.org/rfc/rfc1889.txt, accessed in Febrary 2002
  • 2. Schulzrinne, H., "RTP Profile for Audio and Video Audio and Video Conferences with Minimal Control", RFC 1890, January 1996. http://www.ietf.org/rfc/rfc1890.txt, accessed in Febrary 2002
  • 3. Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998. http://www.ietf.org/rfc/rfc2327.txt, accessed in Febrary 2002
  • 4. Greene, N., Ramalho, M. and B. Rosen, "Media Gateway control protocol architecture and requirements", RFC 2805, April 1999. http://www.ietf.org/rfc/rfc2805.txt, accessed in Febrary 2002
  • 5. Cuervo, F., Greene, N., Rayhan, A., Huitema, C., Rosen, B. and J. Segers, "Megaco Protocol Version 1.0", RFC 3015, November 2000. http://www.ietf.org/rfc/rfc3015.txt, accessed in Febrary 2002
  • 6. Blatherwick, P., Bell, R. and P. Holland, "Megaco IP Phone Media Gateway Application Profile", RFC 3054, January 2001. http://www.ietf.org/rfc/rfc3054.txt, accessed in Febrary 2002
  • 7. ITU-T SG16, H.248 Annex G: User Interface Elements and Actions Packages, Brown, M. & P. Blatherwick, November 2000. ftp://standards.nortelnetworks.com/megaco/docs/Approved/H248_G_PDF.zip, accessed in Febrary 2002