Skip to end of metadata
Go to start of metadata

Download PDF Document

2018-07-12

All Mediatrix Units

v. 42.3.986


1 PCM Traces

The PCM traces are two different RTP streams made specifically to record all analog or digital signals that are either sent or received by the telephony ports of the Mediatrix unit.

These RTP streams are sent to a configurable IP address, normally an IP address on your network where it can be recorded with a packet sniffer (such as Wireshark). Moreover, they are independent from the regular RTP streams of the VoIP call. On the analog devices, the streams are sent instantly at device start-up, with an average ptime of 5 ms. The resulting streams, depending on the model, are around 15 kB/s.

Only the configured port, port #1 and/or #2 send the PCM traces for a maximum of four simultaneous RTP streams.

All streams are sent instantly at start-up with an average ptime of 15 ms. This means that until the PCM traces are disabled, even an idle unit will continuously send up to 66.6 packets/s X 4 streams = 267 packets/s using approximately 174 bytes each, for a total of 46 Kbytes of upstream bandwidth.

On digital devices, the streams will be sent once a call is in process of being established (ISDN SETUP, SIP INVITE). This means no data will be sent if the gateway is idle with no calls in progress.

PCM Traces are usefull at identifying problems with:

  • Echo in the network
  • DTMF signals
  • Caller ID signals
  • Fax signals (or false Fax detection)
  • Message Waiting Indicator signals
  • Any other analog signal
  • Any voice quality issue


2 Requirements

  • RTP stream port 5001 is used for the PCM stream received from the peer.
  • RTP stream port 6001 for the PCM stream sent to the peer.
  • For 3000/4400/S7/G7/C7 Series and Sentinel 100 and 400 test calls must be done on the configured port.

Note

Because of the resulting RTP traffic, enabling Update List of Packets in Real Time has been known to wrongly report 40% packet loss in Wireshark, which may totally impair our analysis capabilities. This feature must be disabled in Wireshark.

Note

PCM traces are not recommended in real deployments, unless it is for a short period of time, but rather in a lab environment and is meant for troubleshooting purposes only

Port names are as follows:
Ports Names
4102S Phone-Fax1/Phone-Fax2
4108/16/24 Port01 to Port24
4400 Bri1 to Bri4
C7

FXS1 to FXS8

FXO1 to FXO8

G7/S7/Sentinel 100

PRI1, PRI2, ...

FXS1, FXS2, ...

FXO1, FXO2, ...

Sentinel 400

Slot1/E1T1, Slot2/E1T1...

Slot3/FXS1, Slot3/FXS2...

Slot3/FXO1, Slot3/FXO2...


3 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..

3.1 Logging on to the Mediatrix Unit Web Interface

Context

For better performances, it is recommended to use the latest available version of Microsoft Internet Explorer, Google Chrome, or Mozilla Firefox.

Note

You may not be able to log on to the Mediatrix unit Web interface if you are using older browser versions. The computer's network card must be on the same subnet as the Mediatrix unit.

Steps

  1. In your Web browser, enter the IP address used by your Mediatrix unit to communicate with the Web interface.
    • If your computer is connected to the Ethernet port, commonly used to be connected to the Local Area Network (LAN), i.e. ETH2 on most devices, use the 192.168.0.10 IP address.
    • If your Mediatrix unit is configured to use a DHCP server with IPv4, use the provided DHCP server IP address.
  2. Enter public as your username and leave the password field empty.

    Note

    The public username account has administrator rights.

    Note

    You can also use admin as a username and administrator as password.

  3. Click Login.

Result

The Information page of the Web interface is displayed.

3.2 Restarting a Service - MIPT

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/Services.
  2. In the User Service table, locate the service Media IP Transport (MIPT).
  3. From the Startup Type selection list next to Media IP Transport (MIPT), choose Auto if you wish the service to start automatically when the system starts, or Manual to start to the service manually when needed.
  4. In the User Service table, click .

Result

The tab from which you can access the Web pages are no longer greyed out.

3.3 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.


4 Available Documentation

For more details, refer to the Mediatrix Documentation .

5 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.