1
<?xml version="1.0" encoding="latin1" ?>
2
<!DOCTYPE chapter SYSTEM "chapter.dtd">
7
<year>2002</year><year>2009</year>
8
<holder>Ericsson AB. All Rights Reserved.</holder>
11
The contents of this file are subject to the Erlang Public License,
12
Version 1.1, (the "License"); you may not use this file except in
13
compliance with the License. You should have received a copy of the
14
Erlang Public License along with this software. If not, it can be
15
retrieved online at http://www.erlang.org/.
17
Software distributed under the License is distributed on an "AS IS"
18
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
19
the License for the specific language governing rights and limitations
24
<title>Megaco mib</title>
25
<prepared>Micael Karlberg</prepared>
26
<responsible>Micael Karlberg</responsible>
28
<approved>Micael Karlberg</approved>
30
<date>2007-06-15</date>
32
<file>megaco_mib.xml</file>
37
<p>The Megaco mib is as of yet not standardized and our
38
implementation is based on
39
<em>draft-ietf-megaco-mib-04.txt</em>. Almost all of the mib
40
cannot easily be implemented by the megaco application. Instead
41
these things should be implemented by a user (of the megaco
43
<p>So what part of the mib is implemented? Basically the relevant
44
statistic counters of the <em>MedGwyGatewayStatsEntry</em>.</p>
48
<title>Statistics counters</title>
49
<p>The implementation of the statistic counters is
50
lightweight. I.e. the statistic counters are handled
51
separatelly by different entities of the application. For
52
instance our two transport module(s) (see <seealso marker="megaco_tcp#stats">megaco_tcp</seealso> and <seealso marker="megaco_udp#stats">megaco_udp</seealso>) maintain their
53
own counters and the application engine (see <seealso marker="megaco#stats">megaco</seealso>) maintain it's own
55
<p>This also means that if a user implement their own transport
56
service then it has to maintain it's own statistics.</p>
60
<title>Distribution</title>
61
<p>Each megaco application maintains it's own set of counters. So
62
in a large (distributed) MG/MGC it could be neccessary to
63
collect the statistics from several nodes (each) running the
64
megaco application (only one of them with the transport).</p>