From 84adefa331c4159d432d22840663c38f155cd4c1 Mon Sep 17 00:00:00 2001
From: Erlang/OTP <otp@erlang.org>
Date: Fri, 20 Nov 2009 14:54:40 +0000
Subject: The R13B03 release.

---
 lib/megaco/doc/src/megaco_mib.xml | 67 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 67 insertions(+)
 create mode 100644 lib/megaco/doc/src/megaco_mib.xml

(limited to 'lib/megaco/doc/src/megaco_mib.xml')

diff --git a/lib/megaco/doc/src/megaco_mib.xml b/lib/megaco/doc/src/megaco_mib.xml
new file mode 100644
index 0000000000..3c0a549590
--- /dev/null
+++ b/lib/megaco/doc/src/megaco_mib.xml
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="latin1" ?>
+<!DOCTYPE chapter SYSTEM "chapter.dtd">
+
+<chapter>
+  <header>
+    <copyright>
+      <year>2002</year><year>2009</year>
+      <holder>Ericsson AB. All Rights Reserved.</holder>
+    </copyright>
+    <legalnotice>
+      The contents of this file are subject to the Erlang Public License,
+      Version 1.1, (the "License"); you may not use this file except in
+      compliance with the License. You should have received a copy of the
+      Erlang Public License along with this software. If not, it can be
+      retrieved online at http://www.erlang.org/.
+    
+      Software distributed under the License is distributed on an "AS IS"
+      basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
+      the License for the specific language governing rights and limitations
+      under the License.
+    
+    </legalnotice>
+
+    <title>Megaco mib</title>
+    <prepared>Micael Karlberg</prepared>
+    <responsible>Micael Karlberg</responsible>
+    <docno></docno>
+    <approved>Micael Karlberg</approved>
+    <checked></checked>
+    <date>2007-06-15</date>
+    <rev>%VSN%</rev>
+    <file>megaco_mib.xml</file>
+  </header>
+
+  <section>
+    <title>Intro</title>
+    <p>The Megaco mib is as of yet not standardized and our
+      implementation is based on
+      <em>draft-ietf-megaco-mib-04.txt</em>.  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>
+    <p>So what part of the mib is implemented? Basically the relevant
+      statistic counters of the <em>MedGwyGatewayStatsEntry</em>.</p>
+  </section>
+
+  <section>
+    <title>Statistics counters</title>
+    <p>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 <seealso marker="megaco_tcp#stats">megaco_tcp</seealso> and <seealso marker="megaco_udp#stats">megaco_udp</seealso>) maintain their
+      own counters and the application engine (see <seealso marker="megaco#stats">megaco</seealso>) maintain it's own
+      counters.</p>
+    <p>This also means that if a user implement their own transport
+      service then it has to maintain it's own statistics.</p>
+  </section>
+
+  <section>
+    <title>Distribution</title>
+    <p>Each megaco application maintains it's 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).</p>
+  </section>
+</chapter>
+
-- 
cgit v1.2.3