Erlang -- Megaco mib

Megaco/H.248

User's Guide

Version 3.18.6

- User's Guide
- Reference Manual
- Release Notes
- PDF
- Top

- Expand All
- Contract All

### Chapters

- Introduction
  - Top of chapter
  - Scope and Purpose
  - Prerequisites
  - About This Manual
  - Where to Find More Information
- Architecture
  - Top of chapter
  - Network view
  - General
  - Single node config
  - Distributed config
  - Message round-trip call flow
- Running the stack
  - Top of chapter
  - Starting
  - MGC startup call flow
  - MG startup call flow
  - Configuring the Megaco stack
  - Initial configuration
  - Changing the configuration
  - The transaction sender
  - Segmentation of transaction replies
- Internal form and its encodings
  - Top of chapter
  - Internal form of messages
  - The different encodings
  - Configuration of Erlang distribution encoding module
  - Configuration of text encoding module(s)
  - Configuration of binary encoding module(s)
  - Handling megaco versions
  - Encoder callback functions
- Transport mechanisms
  - Top of chapter
  - Callback interface
  - Examples
- Implementation examples
  - Top of chapter
  - A simple Media Gateway Controller
  - A simple Media Gateway
- Megaco mib
  - Top of chapter
  - Intro
  - Statistics counters
  - Distribution
- Performance comparison
  - Top of chapter
  - Comparison of encoder/decoders
  - System performance characteristics
  - Description of encoders/decoders
  - Setup
  - Summary
- Testing and tools
  - Top of chapter
  - Tracing
  - Measurement and transformation

# 7 Megaco mib

### 7.1 Intro

The Megaco mib is as of yet not standardized and our implementation is based on draft-ietf-megaco-mib-04.txt. Almost all of the mib cannot easily be implemented by the megaco application. Instead these things should be implemented by a user (of the megaco application).

So what part of the mib is implemented? Basically the relevant statistic counters of the MedGwyGatewayStatsEntry.

### 7.2 Statistics counters

The implementation of the statistic counters is lightweight. I.e. the statistic counters are handled separately by different entities of the application. For instance our two transport module(s) (see megaco_tcp and megaco_udp) maintain their own counters and the application engine (see megaco) maintain its own counters.

This also means that if a user implement their own transport service then it has to maintain its own statistics.

### 7.3 Distribution

Each megaco application maintains its own set of counters. So in a large (distributed) MG/MGC it could be necessary to collect the statistics from several nodes (each) running the megaco application (only one of them with the transport).