- Sentinel 100
- Sentinel 400
- Mediatrix S7 and S7 LP Series
- Mediatrix G7 Series
- Mediatrix C7 Series
- Mediatrix 4100 Series
- Mediatrix 3000 Series
- Mediatrix 4400 Series
- Mediatrix LP Series
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:
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.
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
|4108/16/24||Port01 to Port24|
|4400||Bri1 to Bri4|
FXS1 to FXS8
FXO1 to FXO8
PRI1, PRI2, ...
FXS1, FXS2, ...
FXO1, FXO2, ...
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.
This IP address does not have to be listening on UDP ports, as it is easy to filter out ICMP “port unreachable” messages afterwards.
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.
The public username account has administrator rights.
You can also use admin as a username and administrator as password.
|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.
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.