VOIP Call History Report

Introduction

It is essential to network administrators today to track each VOIP call as they are interested in creating a *true* and *functional* VOIP Call ‘Service Accounting Levels’ through accounting for each of the calls using each prospective call’s details.

Solution Overview

This VOIP Call accounting could be done by collecting the values of the MIB Objects representing the details per actual Call registered in a production environment. The MIB Objects to reflect Call identification details are cvVoIPCallHistoryRemoteIPAddress, cvVoIPCallHistoryRemoteUDPPort, cCallHistoryPeerAddress, cCallHistoryConnectTime, cCallHistoryDisconnectTime among other objects representing the Call’s Session protocol and Session target respectively.

SOSL based Management Process script configuration

MODULE  cCallHistoryData();

BEGIN

          ALL-DEV (ZONE "entL3") BY DEV                  

          {                 

                   SET-INDEX cCallHistoryTable

                           (cvVoIPCallHistoryConnectionId [cCallHistoryIndex, INT]);

                   WITH-INDEX cCallHistoryTable

                   {

                             POLL (cvVoIPCallHistoryRemoteIPAddress;

                                    cvVoIPCallHistoryRemoteUDPPort;

                                    cvVoIPCallHistorySessionProtocol;

                                    cvVoIPCallHistorySessionTarget;

                                    cCallHistoryPeerAddress;

                                    cCallHistoryDisconnectText;

                                    cCallHistoryConnectTime;

                                    cCallHistoryDisconnectTime;

                                    cCallHistoryCallOrigin     );

                   };

           };

END

[SOSL Case Studies], [Management Concepts], [NMS Technology R&D]

[Home], [About], [Solutions Center], [NMS Market], [Products & Services],
[Management Technology], [Technical Support], [Contact us], [Site Map]