megaco/h.248 protocol implementationljilja/ensc835/spring02/projects/mannan_riyadh...megaco / h.248...
Post on 04-Apr-2018
223 Views
Preview:
TRANSCRIPT
Megaco / H.248 Implementation18 - 1
Megaco/H.248 ProtocolImplementation
Riadul MannanMahmood Riyadh
Shufang Wu{vswu, mrmannan, mmriyadh}@cs.sfu.ca
Tuesday, April 2, 2002
Megaco / H.248 Implementation18 - 2
Agenda
• Introduction• Project Plan & Requirements• Call flows• Implementation in OPNET: Network Model & Node Model• Implementation in OPNET: Custom Real Time Protocol (RTP)• Implementation in OPNET: Media Gateway Control (MGC)• Implementation in OPNET: Media Gateway (MG)• Project Status & Expected Results• References• Q & A
Megaco / H.248 Implementation18 - 3
Introduction
• Problem in Reality• Solution: Media Gateway Control Protocol• Problem in Reality• Solution: Media Gateway Control Protocol• A brand NEW area
– IETF– ITU-T– TIA/EIA
• Who are involved in ?– Cisco, Nortel, Lucent– Motorola, Microsoft
IP
Media Gateway (MG)
Media Gateway Controller (MGC)
Media Gateway (MG)
Master/slave Architecture
Megaco / H.248 Implementation18 - 4
Project Plan & Requirements( http://www.sfu.ca/~vswu/courses/CMPT885/project.htm)
• Project Plan ( Project is Repeatable & Controlled )– Version 1.1 ( 5 of 8 commands in 3 simulation scenarios )– Three main components: MG (IP Phone), MGC, Custom RTP
• Project Requirements– System Requirements
• System Functional Specification (SFS), Version1.4• SFS of Custom RTP, Version 1.0• System Interface Control Document (SICD), Version 1.1
– Software Requirements• Software Functional Specification (SWFS) of MG, Version 1.0• SWFS of MGC, Version 1.0• SWFS of Custom RTP, Version 1.0
Megaco / H.248 Implementation18 - 5
Call flows
[8] Add
MG1 MG2MGC
[6] Add
[1] Notify
[2] Notify
[4] Modify [3] Modify
[7] Add
[9] Modify [10] Modify
[5] Add
[11] Notify [12] Notify
[14] Modify [13] Modify
[15] Modify [16] Modify
Call flows of three simulation scenariosSuccessful MG Registration ProcedureSuccessful Call Setup ProcedureSuccessful Call Release Procedure
Successful Call Setup ProcedureHello!Hello!
Ring
Ring
Dail
Megaco / H.248 Implementation18 - 6
Agenda
• Introduction• Project Plan & Requirements• Call flows• Implementation in OPNET: Network Model & Node Model• Implementation in OPNET: Custom RTP• Implementation in OPNET: Media Gateway Control (MGC)• Implementation in OPNET: Media Gateway (MG)• Project Status & Expected Results• References• Q & A
Megaco / H.248 Implementation18 - 7
Implementation in OPNET: Network Model
Megaco/H.248 Protocol
RTP Protocol
Media Gateway Controller (MGC)
Media Gateways (MG)
Megaco / H.248 Implementation18 - 8
Implementation in OPNET: Node Model
MGC/MG/RTP
Megaco / H.248 Implementation18 - 9
Implementation in OPNET:Custom Real Time Protocol (RTP)
• What is RTP ?– RTP provides transmission functions for applications
transmitting real time data e.g. Audio, video.
• RTP has two kinds of packet formats– RTP Packet– RTCP Packet
• RTP in our project:– transmits voice traffic between two MGs– collects statistics
Megaco / H.248 Implementation18 - 10
Media Gateway Controller (MGC)
• The architecture of MGC:
Media Gateway Controller (MGC)
Message Analyzer
Message ReceiverMessage Sender
Media Gateway (MG)
Megaco / H.248 Implementation18 - 11
Implementation in OPNET:Media Gateway Controller (MGC)
• Software Design Specification (SWDS) of MGC, Version 1.0• FSM of MGC
Megaco / H.248 Implementation18 - 12
Agenda
• Introduction• Project Plan & Requirements• Call flows• Implementation in OPNET: Network Model & Node Model• Implementation in OPNET: Custom Real Time Protocol (RTP)• Implementation in OPNET: Media Gateway Control (MGC)• Implementation in OPNET: Media Gateway (MG)• Project Status, Expected Results & Future Work• References• Q & A
Megaco / H.248 Implementation18 - 13
Media Gateway (MG)
Media Gateway Controller (MGC)
MG_Recv MG_Send
MG_Process
V_Sink V_Src
RTP
Media Gateway (MG)
MG Architecture
Media Gateway (MG)
Megaco / H.248 Implementation18 - 14
Process MEGACO PacketProcess RTP Packet
MG Process Model
• SWDS of MG, Version 1.0
Implementation in OPNET: Media Gateway
Megaco / H.248 Implementation18 - 15
Project Status
• Completed Tasks– MGC Process Model– MG Process Model– Custom RTP– Node Model– Network Model
• Remaining Tasks– Debugging– Collecting Statistics– Writing Final Report
• For details, visithttp://www.sfu.ca/~vswu/courses/CMPT885/project.htm
Megaco / H.248 Implementation18 - 16
Expected Results & Future Work
• Expected Results– Packets Received– Packets Sent– Packets Loss– Average Delay
• Future Work– Implementation of other three Megaco/H.248 commands– Implementation of full featured RTP– Multiple call scenarios
Megaco / H.248 Implementation18 - 17
References
1. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for Real-TimeApplications", RFC 1889, January 1996. http://www.ietf.org/rfc/rfc1889.txt
2. Schulzrinne, H., "RTP Profile for Audio and Video Audio and Video Conferences with Minimal Control", RFC1890, January 1996. http://www.ietf.org/rfc/rfc1890.txt
3. Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.http://www.ietf.org/rfc/rfc2327.txt
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
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
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
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
Megaco / H.248 Implementation18 - 18
top related