Skip to end of metadata
Go to start of metadata

Download PDF Document

2018-08-16

For All Mediatrix Units

v. 43.0.1125


1 Required Information to Report a Problem

When reporting a problem and to make sure that all the relevant information is given to the Mediatrix support team at once, the following information is required.

Required information Checkmark
Mediatrix product name, release and build number.
Profile name
Serial number of the Mediatrix unit if a hardware problem is suspected.
Name/manufacturer/type of other VoIP devices along with their IP addresses.
Name/manufacturer/software version of the Proxy server (SIP).
Whenever possible, a diagram of the network or wiring setup.
Call flow/call scenario to reproduce the problem.
Please mention if the call goes through a NAT, Firewall, Bridge, VPN, Router, Soft switch, etc.
Please detail any changes made to the initial configuration or export your configuration script. Refer toExporting a Configuration Script to Your PC

2 Exporting a Configuration Script to Your PC

Context

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will be displayed.

Steps

  1. Go to Management/Configuration Scripts
  2. If you are not using HTTPS, click Activate unsecure file transfer through web browser located at the top of the page.
  3. In the Transfer Scripts Through Web Browser table, from the Content selection list, choose if you wish to export only what is different from the factory configuration script or the complete configuration.
  4. If you wish to use encryption for transfer operations, complete the Privacy Key field.

    Note

    Media5 corp strongly recommends to use encryption to protect certificates and passwords.

  5. Click Export and Download.

Result

The configuration script will be exported to your PC in the Downloads folder. The system generates a macAddress.cfg file name.

3 Enabling Syslogs in Debug Mode

Before You Start

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will be displayed.

Context

Although a Syslog server can be used, it is recommended to use Wireshark.

Steps

  1. Go to System/Event Log.
  2. In the Remote Host field, enter the static IP address or domain name and port number of the device that archives the log entries sent by syslog transport.

    Note

    Specifying no port, or port 0, sends notifications to port 514.

  3. From the Diagnostic Traces field, select Enable.
  4. Click Edit.
  5. In the Diagnostic Traces table, select the level of severity an event should have to be reported by the syslog.

    Important

    Enabling all the traces will reduce the performance of the Mediatrix unit and may cause it to no longer respond.

  6. Click Apply.
  7. Click Apply again.

Result

The traces generated by the Mediatrix unit with the selected severity level, will be sent to the specified address.

4 Packet Captures

Packet captures are data packets intercepted when passing through a specific computer network.

Captured packets can be sent to a specific location where they can be analysed. The content of the capture can therefore be used to diagnose and troubleshoot network problems and determine if network security policies are being followed.

There are two different ways to perform a packet capture:

  • With the pcapture CLI command (not a Cli service command) available only via the CLI. This method displays the captured packet directly in the CLI or allows streaming the captured packet to a SSH tunnel to a remote Wireshark client.
  • With the PCaptureStart Nlm service command. This is a muse command, it can be executed via SNMP, a script, and the CLI. This is also the command used when performing packet captures via the Web page. This method sends the captured file to the service FILE or to a HTTP server via a standard HTTP upload.


4.1 Starting a Packet Capture

Before You Start

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will be displayed.

Steps

  1. Go to System/Packet Capture.
  2. In the Packet Capture Configuration form, complete the fields as required.

    Note

    The URL format must follow this syntax:

     protocol://[user[:password]@]hostname[:port]/[path/]filename

    Note

    Available protocols are File, HTTP, and HTTPS but the File protocol is not available on Mediatrix 4102 units.

    Important

    The HTTP server must allow "slow HTTP requests" (mod_reqtimeout module for Apache HTTP Server) otherwise the pcapture feature may not work as expected. Depending on the nature of what is being captured, chunks can be sent very slowly and with long delays, causing the capture to be considered as an attack and therefore stopped.

  3. From the Link Name, select the link to perform the capture.
  4. Click Apply & Start Capture.

Result

If there are no problems with your configuration, the "Last Capture Result" status will be "Requested". The captured packets will be sent to the specified URL. If the selected URL started with file://, then the capture will be sent to the File service.

4.2 Stopping a Packet Capture

Before You Start

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will be displayed.

Steps

  1. Go to System/Packet Capture.
  2. Click Apply & Stop Capture.

Result

If there are no problems with your configuration, the status of the "Last Capture Result" will be "Completed". The captured packets will no longer be sent to the specified URL.

5 Remote Packet Capture

A remote capture allows a remote Mediatrix unit to capture the traffic on its network interfaces, and forward it through a SSH tunnel, in order to see the traffic live on a local PC running Wireshark.


5.1 Starting a Network Capture Remotely On Windows

Context

This method is performed using the pcapture command of the CLI.

Before You Start

  • You must know the IP address of the unit running the DGW software.
  • The Mediatrix unit must be running a DGW v2.0.39.689 firmware or higher.
  • You must have a PC running Wireshark.

Steps

  1. From the PC, download the plink utility: plink utility .
  2. Save the plink utility in the same folder as the Wireshark executable is located.
  3. Open a command line interface (e.g. cmd.exe).
  4. Go to the Wireshark folder where the utility was saved.
  5. Enter
    plink.exe -pw "PASSWORD" USERNAME@IP_ADDRESS "pcapture -raw -i any" | wireshark -k -i -
    and replace the password, username, and IP address according to your setup.

    Note

    any is to make a capture on all ETH ports, including VLans (for example ETH1.10 where ) . But it is possible to choose the port, either ETH1, ETH2, ETH5, ETH1-4, ETH2-5, WAN, or LAN depending on the type of unit.

    Note

Result

The pcapture command will be executed in the CLI and the result will be sent to a new Wireshark window on the PC running the Wireshark.

5.2 Starting a Network Capture Remotely On MacOS or Linux

Context

This method is performed using the pcapture command of the CLI.

Before You Start

  • The Mediatrix unit must be running a DGW v2.0.17.285 firmware or higher.
  • You must know the IP address of the unit running the DGW software.
  • You must have a PC running Wireshark.

Steps

  1. Open a command line interface.
  2. Enter: and replace the password, username, and IP address according to your setup.
    ssh USERNAME@IP_ADDRESS "pcapture -raw -i any" | wireshark -k -i -

    Note

    any is to make a capture on all ETH ports. But it is possible to choose the port, either ETH1, ETH2, ETH5, ETH1-4, ETH2-5, WAN, or LAN depending on the type of unit.

    Note

Result

The pcapture command will be executed in the CLI and the result will be sent to a new Wireshark window on the PC running the Wireshark.

6 Capturing a Trace Using Wireshark

Before You Start

You must have downloaded Wireshark at the following link https://www.wireshark.org/ (Wireshark is a network protocol analyzer. It is an Open Source software released under the GNU General Public Licence. It can decode most VoIP protocols: SIP, MGCP, H.323, RTP, etc.). Select the Windows version. Make sure to install winpcap and read the instructions.

If you are taking a trace on a switch, the port of the switch connected to the PC must be configured to mirror the port connected to the Mediatrix unit. Alternatively, you could use a hub, which should be connected to both the PC running Wireshark and the Mediatrix unit.

Otherwise you will not capture the packets from the unit.

Steps

  1. In the Capture menu, select Capture Options.
  2. In the Capture selection list, select the Ethernet network adapters to use.
  3. In the (Display) Options section, select the Update list of packet in real time check box.
  4. Select the Automatic scrolling in live capture check box.
  5. If troubleshooting a random problem happening weekly, select the Use multiple files check box.

    Note

    For the latest Wireshark release, this can be configured via Capture/Options/Ouput/Create a new file automatically after…

Result

In Wireshark release 2.2.0

In older Wireshark releases


7 Enabling the PCM Traces of a Port Using the CLI

Before You Start

The PCM traces destination must be set so it can be recorded in a Wireshark capture on your network, normally sent to the PC doing the capture.

Context

If a port is receiving several calls at a time, the capture will be performed on the first call until it is completed, and only then will a capture be performed on another call. Traces are taken as soon as the port is opened.

Steps

  1. Using the CLI, set the Mipt.PcmCaptureEnable parameter to Enable.

    Note

    For example Mipt.PcmCaptureEnable=Enable or Mipt.PcmCaptureEnable=1

  2. Set the Mipt.PcmCaptureEndpoint parameter to the unit’s endpoint on which the PCM capture will be taken from. For endpoint examples, refer to Endpoint Examples.

    Note

    To make sure that you are capturing the appropriate endpoint, please verify its naming by running the following command in CLI: Epadm.Endpoint. The output of the command displays a table with the unit's endpoints.

    Note

    For example Mipt.PcmCaptureEndpoint = FXO2

    Note

    Port names are case sensitive.

  3. Set the Mipt.PcmCaptureIpAddr MIB parameter to the IP address of the PC running Wireshark.

    Note

    For example Mipt.PcmCaptureIpAddr = 192.168.0.17

    Note

    This IP address does not have to be listening on UDP ports, as it is easy to filter out ICMP “port unreachable” messages afterwards.

  4. When the capture is done, make sure to disable the Mipt.PcmCaptureEnable MIB parameter.

    Note

    For example Mipt.PcmCaptureEnable = Disable or Mipt.PcmCaptureEnable = 0

Result

In the configuration script, the value of Mipt.PcmCaptureEnable, Mipt.PcmCaptureIpAddr and Mipt.PcmCaptureEndpoint should reflect the values configured.

8 Enabling PCM Traces of a Port Using the Configuration Script

Before You Start

The PCM traces destination must be set so it can be recorded in a Wireshark capture on your network, normally sent to the PC doing the capture.

Context

If a port is receiving several calls at a time, the capture will be performed on the first call until it is completed, and only then will a capture be performed on another call. Traces are taken as soon as the port is opened.

Steps

  1. Create a txt file, and save it as a *.cfg.
  2. Enter Mipt.PcmCaptureEnable = Enable or Mipt.PcmCaptureEnable=1
  3. Enter Mipt.PcmCaptureEndpoint = Value , where Value is the unit’s endpoint on which the PCM capture will be taken from. For more information, refer to Endpoint Examples.

    Note

    To make sure that you are capturing the appropriate endpoint, please verify its naming by running the following command in CLI: Epadm.Endpoint. The output of the command displays a table with the unit's endpoints.

    Note

    The port names are case sensitive.

  4. Enter Mipt.PcmCaptureIpAddr = Value , where Value is the IP address of the PC running Wireshark.

    Note

    The IP address does not have to be listening on UDP ports, as it is easy to filter out ICMP “port unreachable” messages afterwards.

  5. Import the *.cfg file into the system. Refer to Configuration Scripts Import and Export .
  6. When the capture is done, make sure to disable the Mipt.PcmCaptureEnable MIB parameter.

    Note

    For example Mipt.PcmCaptureEnable = Disable or Mipt.PcmCaptureEnable = 0

Result

In the configuration script, the value of Mipt.PcmCaptureEnable, Mipt.PcmCaptureIpAddr and Mipt.PcmCaptureEndpoint parameters should reflect the values configured..

9 Enabling the PCM Traces of a Port Using UMN

Before You Start

The PCM traces destination must be set so it can be recorded in a Wireshark capture on your network, normally sent to the PC doing the capture.

Context

If a port is receiving several calls at a time, the capture will be performed on the first call until it is completed, and only then will a capture be performed on another call. Traces are taken as soon as the port is opened.

Steps

  1. Using UMN, right click the name of the unit and select Edit SNMP...
  2. Browse to: mediatrixSystem/gen5/mediatrixCommon/mediatrixServices/miptMIB/miptMIBObjects/debugGroup/ pcmCaptureGroup.
  3. Set the pcmCaptureEnable MIB parameter to Enable.
  4. Set the pcmCaptureEndpoint MIB parameter to the unit’s endpoint on which the PCM capture will be taken from. For endpoint examples, refer to Endpoint Examples.

    Note

    To make sure that you are capturing the appropriate endpoint, please verify its naming by running the following command in CLI: Epadm.Endpoint. The output of the command displays a table with the unit's endpoints.

  5. Set the pcmCaptureIpAddr MIB parameter to the IP address of the PC running Wireshark.

    Note

    This IP address does not have to be listening on UDP ports, as it is easy to filter out ICMP “port unreachable” messages afterwards.

  6. When the capture is done, make sure to set the pcmCaptureEnable MIB parameter to Disable.

Result


10 Enabling the Automatic Diagnostic Log Dump

Context

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will be displayed.

Steps

  1. Go to System/Diagnostic.
  2. In the Diagnostic Log Configuration table, select Enable.
  3. Click Apply.

Result

If the unit unexpectedly closes, the diagnostic logs will be automatically generated in an *.tgz file, available under Management/File in the Internal files table.

10.1 Manually Starting a Diagnostic Log Dump

Context

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will be displayed.

Steps

  1. Go to System/Diagnostic.
  2. In the Diagnostic Log Configuration table, select Dump Now.

Result

The diagnostic logs will be generated in an *.tgz file, available under the Management/File, in the Internal files table.

11 Endpoint Examples

Endpoint Name Description
Bri1-2 BRI port 1, channel 2
Slot2/E1T1-3 Channel 3 of the E1 port located in slot 2
Port09 Port 09 of a Mediatrix 4108-16-24 unit
Phone-Fax1 Port 1 of a Mediatrix 4102 unit
FXS1 Port 1 of the FXS card of a Mediatrix C7 unit
FXO1 Port 1 of the FXO card of a Mediatrix C7 unit

All possible endpoint names are listed in the Endpoint table displayed in the DGW Web interface (System/Endpoints). You may also access this table via the CLI by using the EpAdm.Endpoint command or directly via UMN.


12 Available Documentation

For more details, refer to the Mediatrix Documentation .

13 Copyright Notice

Copyright © 2018 Media5 Corporation.

This document contains information that is proprietary to Media5 Corporation.

Media5 Corporation reserves all rights to this document as well as to the Intellectual Property of the document and the technology and know-how that it includes and represents.

This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever, without written prior approval by Media5 Corporation.

Media5 Corporation reserves the right to revise this publication and make changes at any time and without the obligation to notify any person and/or entity of such revisions and/or changes.