Megaco/H.248 Call flow examples
draft-ietf-megaco-callflows-04
| Document | Type |
Expired Internet-Draft
(megaco WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | B Madhubabu , Prerepa Viswanadham , Krishna Gundamaraju | ||
| Last updated | 2015-10-14 (Latest revision 2004-11-15) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Jon Peterson | ||
| IESG note | |||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Megaco/H.248 call flow examples draft illustrates the usage of Megaco - Version 1 protocol [Ref:3] defined between the Media Gateway Controller and Media Gateway. In light of the vast features presently incorporated and continuously evolving features of the protocol, it serves the purpose of representing typical use case scenarios. There are a lot of possible scenarios for usage of MEGACO protocol. It is not the intent of the draft to represent the inter-working functionality among various protocols, however, an attempt is made to depict its usage in such a case for the purpose of completeness in the larger perspective. An attempt has been made to illustrate the supplementary call services using MEGACO. The call flows can be categorized in to two sub sections,
Authors
B Madhubabu
Prerepa Viswanadham
Krishna Gundamaraju
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)