File: megaco_mib.html

package info (click to toggle)
erlang-doc-html 1%3A11.b.2-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 23,284 kB
  • ctags: 10,724
  • sloc: erlang: 505; ansic: 323; makefile: 62; perl: 61; sh: 45
file content (53 lines) | stat: -rw-r--r-- 2,047 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- This document was generated using DocBuilder 3.3.3 -->
<HTML>
<HEAD>
  <TITLE>Megaco mib</TITLE>
  <SCRIPT type="text/javascript" src="../../../../doc/erlresolvelinks.js">
</SCRIPT>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#FF00FF"
      ALINK="#FF0000">
<CENTER>
<A HREF="http://www.erlang.se"><IMG BORDER=0 ALT="[Ericsson AB]" SRC="min_head.gif"></A>
</CENTER>
<A NAME="7"><!-- Empty --></A>
<H2>7 Megaco mib</H2>
<A NAME="7.1"><!-- Empty --></A>
<H3>7.1 Intro</H3>

<P>The Megaco mib is as of yet not standardized and our
implementation is based on
<STRONG>draft-ietf-megaco-mib-04.txt</STRONG>. 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). 
<P>So what part of the mib is implemented? Basically the relevant
statistic counters of the <STRONG>MedGwyGatewayStatsEntry</STRONG>.<A NAME="7.2"><!-- Empty --></A>
<H3>7.2 Statistics counters</H3>

<P> The implementation of the statistic counters is
lightweight. I.e. the statistic counters are handled
separatelly by different entities of the application. For
instance our two transport module(s) (see <A HREF="megaco_tcp.html#stats">megaco_tcp</A> and <A HREF="megaco_udp.html#stats">megaco_udp</A>) maintain their
own counters and the application engine (see <A HREF="megaco.html#stats">megaco</A>) maintain it's own
counters.

<P> This also means that if a user implement their own transport
service then it has to maintain it's own statistics.
<A NAME="7.3"><!-- Empty --></A>
<H3>7.3 Distribution</H3>

<P> Each megaco application maintains it's own set of counters. So
in a large (distributed) MG/MGC it could be neccessary to
collect the statistics from several nodes (each) running the
megaco application (only one of them with the transport).
<CENTER>
<HR>
<SMALL>
Copyright &copy; 1991-2006
<A HREF="http://www.erlang.se">Ericsson AB</A><BR>
</SMALL>
</CENTER>
</BODY>
</HTML>