DOCSEARCHbyAlgolia
Submit Docs

NEMO Documentation

website·Indexed 32 days ago

https://nemo.docs.netaxis.solutions

An all-in-one solution for VoIP services and networks featuring flexible reporting, trace analysis, and troubleshooting tools. Documentation covers installation, backup and restore procedures, and release notes for versions 4.1, 5.0, and 5.1, including details on network elements, collectors, and probe deployments.

Tokens
154.1K
Snippets
427
Records
969
Agent score
39%

What's inside NEMO

  1. Overview of Nemo platform capabilities

    Nemo is an All-In-One, vendor-agnostic reporting and monitoring platform designed to provide insights into voice service usage by gathering data via probes and Call Detail Records (CDRs). Its core functions include:

    • Reporting: Multi-tenant reporting for resellers and end-users via a web portal or automated PDF/DOCX reports.
    • Monitoring & Troubleshooting: End-to-end call flow analysis, SIP message details, and media stream analysis (requires network probes).
    • Alarming: Detection of traffic anomalies (e.g., sudden call rate drops, high error rates) using a traffic patterns analysis engine.
    • Fraud Detection: Integrated capabilities to identify fraudulent activity.
    • Call Analytics: Serves as the analytics engine for the Netaxis Broadworks self-care portal, providing KPIs and CDRs for tenants and groups.

  2. Overview of NEMO VoIP Monitoring Platform

    NEMO is a vendor-agnostic All-In-One product for VoIP Services and Networks. It gathers data via probes and Call Detail Records (CDRs) regardless of format to provide the following functions:

    • Monitoring and Reporting
    • Troubleshooting (including end-to-end call flows, SIP message details, and media stream analysis/replay)
    • Alarming and Debugging
    • Fraud detection

    NEMO supports flexible deployment modes: using portable probes, high-capacity Probe L, CDRs from network equipment, or a hybrid mode combining both probes and CDRs.

  3. NEMO Logical Architecture and Modules

    NEMO follows a modular three-layer architecture: Interface Layer, Data Storage Layer, and Application Layer. These layers can reside on a single instance or be distributed across multiple computing instances.

    The system is divided into the following functional modules:

    • Call Statistics Module: Tracks registrations, call durations, destinations/sources, and release causes.
    • Voice Quality Module: Monitors packet loss, jitter, latency, MOS, codecs, and media bandwidth.
    • Calls Module: Provides call searching, trace searching, and trace analysis.
    • Anomalies Module: Inspects traffic anomalies and SNMP traces.

  5. Detect network anomalies using Anomaly Profiles

    NEMO uses a pattern analysis system to detect network anomalies (e.g., sudden call rate drops or packet loss exceeding thresholds). These rules are defined in 'anomalies profiles'.

    To activate anomaly detection, assign these profiles to specific network elements: realms, endpoints, ranges, trunks, or labels. This allows administrators to set different thresholds based on the expected quality of different segments of a heterogeneous VoIP network.

  6. Understand NEMO Core Terminology

    NEMO uses specific terminology to describe network components and software architecture:

    • Network Elements: Primarily the sources of CDRs.
    • Entities: Physical or logical elements of the monitored network (e.g., a server or a logical object). In some UI areas, these are referred to as 'objects'.
    • Third-party Equipment: Equipment external to the monitored telecom network that accesses the NEMO Stats DB via a REST API to collect statistics.
    • Devices: Names assigned to physical entities in a deployment (e.g., 'Nemo Capture' for probes, 'Net-Net SD' for Oracle SBCs, or 'Broadworks' for Cisco elements).
    • Plugins: Software components that adapt NEMO's behavior to specific network elements, determining available functionality based on the data provided (e.g., SIP vs RTP).
    • Collectors: Software components that ingest CDR data from network equipment using various protocols (e.g., Radius, SFTP) and formats (e.g., CSV, XML) and insert them into the database.
    • Nodes: Hardware equipment (physical servers or virtual machines) within the monitored telecom network.

  7. NEMO Product Overview

    NEMO is a vendor-agnostic monitoring and reporting platform for VoIP services and networks. It gathers data via probes and Call Detail Records (CDRs) to provide the following functions: monitoring, reporting, troubleshooting, alarming, debugging, and fraud detection. It supports deployment via portable probes, high-capacity probes (Probe L), CDR-only mode, or a hybrid of both.

  8. Configure MOS simplified pie chart ranges

    Define the ranges for the MOS (Mean Opinion Score) overview chart using the format label1,limit1;label2,limit2;….

    If a value like 5.0 is used, it creates 4 ranges: "bad" (0.0-2.0), "medium" (2.0-3.0), "good" (3.0-4.25), and "very good" (4.25-5.00).

    bad,2.0;medium,3.0;good,4.25;very good

  11. NEMO Product Overview

    NEMO is a vendor-agnostic monitoring and reporting platform for VoIP services and networks. It gathers data via probes and Call Detail Records (CDRs) to provide functions including monitoring, reporting, troubleshooting, alarming, debugging, and fraud detection. It supports three deployment modes: probe-based (ranging from portable to high-capacity Probe L), CDR-based, or a hybrid of both.

  12. NEMO Logical Architecture and Modules

    NEMO utilizes a modular three-layer architecture: Interface Layer, Data Storage Layer, and Application Layer. These layers can reside on a single instance or be distributed across multiple computing instances. A single instance can support multiple CDR sources (SBC, Broadworks, Probes) via multi-plugin mode.

    The platform is divided into the following functional modules:

    • Call Statistics: Tracks registrations, call durations, destinations/sources, and release causes.
    • Voice Quality: Monitors packet loss, jitter, latency, MOS, codecs, and media bandwidth.
    • Calls: Provides call searching, trace searching, and trace analysis.
    • Anomalies: Inspects traffic anomalies and SNMP traces.