Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated @ 2023-08-09T10:09:26.479416
HTML
headtrue
encodingUTF-8
<!DOCTYPE html
  SYSTEM "about:legacy-compat">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2023"><meta name="DC.rights.owner" content="(C) Copyright 2023"><meta name="DC.type" content="concept"><meta name="description" content="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."><meta name="prodname" content="All Mediatrix Units"><meta name="version" content="DGW 49.12.28842941"><meta name="platform" content="All"><meta name="DC.date.modified" content="2023-0308-2809"><meta name="DC.date.issued" content="2023-0308-2809"><meta name="DC.date.available" content="2023-0308-2809"><meta name="ChapterNumbering" content="no"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="concept_png_yfm_1r"><link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/45482024/commonltr.css"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/45482024/custom.css"><title>Enabling the PCM Traces of a Port Using UMN</title></head><body><header role="banner"><div class="topicmeta title">Enabling the PCM Traces of a Port Using UMN</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">All Mediatrix Units </div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/45482024/Enabling%20the%20PCM%20Traces%20of%20a%20Port%20Using%20UMN.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#concept_png_yfm_1r">PCM Traces</a></li><li><a href="#reference_cvc_ljf_ts">Requirements</a></li><li><a href="#task_iww_qpc_zp">Enabling the PCM Traces of a Port Using UMN</a><ul><li><a href="#task_ifw_qpc_zp">Logging on to the Mediatrix Unit Web Interface</a></li><li><a href="#task_r3h_tyc_gr">Restarting a Service - MIPT</a></li><li><a href="#reference_gwm_mdh_x1b">Endpoint Examples</a></li></ul></li><li><a href="#reference_j4g_nbv_gfb">Online Help</a></li><li><a href="#concept_v4k_q3h_1r">DGW Documentation</a></li><li><a href="#concept_fqm_rv4_k4">Copyright Notice</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1"><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="nested0" aria-labelledby="ariaid-title1" id="concept_png_yfm_1r">
 <h1 class="title topictitle1" id="ariaid-title1">PCM Traces</h1>
 
 <div class="body conbody"><p class="shortdesc">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. </p>
  <p class="p">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.</p>
  <p class="p">Only the configured port, port #1 and/or #2 send the PCM traces for a maximum of four
   simultaneous RTP streams.</p>
  <p class="p">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.</p>
  <p class="p">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.</p>
  <div class="p">PCM Traces are usefull at identifying problems with:<ul class="ul" id="concept_png_yfm_1r__ul_bdr_r3f_ts">
    <li class="li">Echo in the network</li>
    <li class="li">DTMF signals</li>
    <li class="li">Caller ID signals</li>
    <li class="li">Fax signals (or false Fax detection)</li>
    <li class="li">Message Waiting Indicator signals</li>
    <li class="li">Any other analog signal</li>
    <li class="li">Any voice quality issue</li>
   </ul></div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title2" id="reference_cvc_ljf_ts">
  <h1 class="title topictitle1" id="ariaid-title2">Requirements</h1>
  <div class="body refbody">
    <section class="section">
      <ul class="ul" id="reference_cvc_ljf_ts__ul_mhc_jbx_1cb">
        <li class="li">UMN v3.2r24.51 or later </li>
        <li class="li">RTP stream port 5001 is used for the PCM stream received from the peer.</li>
        <li class="li">RTP stream port 6001 for the PCM stream sent to the peer.</li>
        <li class="li">For S7/G7/C7 Series and Sentinel 100 and 400 test calls must be done on the
          configured port.</li>
      </ul>
    </section>
    <section class="section">
      <div class="note note note_note"><span class="note__title">Note:</span> Because of the resulting RTP traffic, enabling <span class="keyword parmname">Update List of Packets in Real
          Time</span> 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.
      </div>
    </section>
    <section class="section">
      <div class="note note note_note"><span class="note__title">Note:</span> 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</div>
    </section>
    <section class="section">The port names are as follows: <table class="table frame-all" id="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts"><caption></caption><colgroup><col style="width:50%"><col style="width:50%"></colgroup><thead class="thead">
            <tr class="row">
              <th class="entry colsep-1 rowsep-1" id="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__1">Ports</th>
              <th class="entry colsep-1 rowsep-1" id="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__2">Names</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__1">4102S</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__2">Phone-Fax1/Phone-Fax2</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__1">C7 </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__2">
                <p class="p">FXS1 to FXS8</p>
                <p class="p">FXO1 to FXO8</p>
              </td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__1">G7/S7/Sentinel 100</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__2">
                <p class="p">PRI1, PRI2, ...</p>
                <p class="p">FXS1, FXS2, ...</p>
                <p class="p">FXO1, FXO2, ...</p>
              </td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__1">Sentinel 400</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_cvc_ljf_ts__simpletable_sq3_5pf_ts__entry__2">
                <p class="p">Slot1/E1T1, Slot2/E1T1...</p>
                <p class="p">Slot3/FXS1, Slot3/FXS2...</p>
                <p class="p">Slot3/FXO1, Slot3/FXO2...</p>
              </td>
            </tr>
          </tbody></table>
    </section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested0" aria-labelledby="ariaid-title3" lang="en-US" id="task_iww_qpc_zp">
    <h1 class="title topictitle1" id="ariaid-title3">Enabling the PCM Traces of a Port Using UMN</h1>
    <div class="body taskbody">
        <section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>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.</section>
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">About this task</strong></div> 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. </section>
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Procedure</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Using UMN, right click the name of the unit and select <strong class="ph b">Edit
                    SNMP...</strong></span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Browse to:
                    mediatrixSystem/gen5/mediatrixCommon/mediatrixServices/miptMIB/miptMIBObjects/debugGroup/
                    pcmCaptureGroup.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set the <span class="keyword parmname">pcmCaptureEnable</span> MIB parameter to <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set the <span class="keyword parmname">pcmCaptureEndpoint</span> MIB parameter to the unit’s
                    endpoint on which the PCM capture will be taken from.  For endpoint examples,
                    refer to <a class="xref" href="#reference_gwm_mdh_x1b">Endpoint Examples</a>.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> To make sure that you are capturing the appropriate endpoint, please
                        verify its naming by running the following command in CLI:
                            <span class="keyword parmname">Epadm.Endpoint.</span> The output of the command displays
                        a table with the unit's endpoints.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set the <span class="keyword parmname">pcmCaptureIpAddr</span> MIB parameter to the IP address
                    of the PC running Wireshark.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> This IP address does not have to be listening on UDP ports, as it is easy
                        to filter out ICMP “port unreachable” messages afterwards.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">When the capture is done, make sure to set the
                        <span class="keyword parmname">pcmCaptureEnable</span> MIB parameter to <span class="keyword wintitle">Disable</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Results</strong></div>
            <br><img class="image" id="task_iww_qpc_zp__image_ynw_22g_ts" src="https://documentation.media5corp.com/download/attachments/45482024/PCMTraces_Dgw.png" width="400"><br>
        </section>
    </div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title4" lang="en-US" id="task_ifw_qpc_zp">
    <h2 class="title topictitle2" id="ariaid-title4">Logging on to the Mediatrix Unit Web Interface</h2>
    <div class="body taskbody">
        <section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>The computer IP address must be in the same TCP/IP network as the Mediatrix
            unit.</section>
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">About this task</strong></div>For better performances, it is recommended to use the latest available version of
            Microsoft Internet Explorer, Google Chrome, or Mozilla Firefox. <div class="note note note_note"><span class="note__title">Note:</span> You may not be
                able to log on to the Mediatrix unit Web interface if you are using older browser
                versions. </div></section>
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Procedure</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">In your Web browser, enter the IP address at which  the Web interface of your
                    Mediatrix unit can be reached.</span>
                <ul class="ul choices" id="task_ifw_qpc_zp__choices_kx1_wf3_bq">
                    <li class="li choice">If your network has an IPv4 DHCP server, connect the primary Ethernet
                        port of the Mediatrix unit to the network (ETH1 port), use the provided DHCP
                        server IP address.</li>
                    <li class="li choice">You can also connect your computer to the secondary Ethernet port of the
                        Mediatrix unit (ETH2), use the 192.168.0.10 IP address. However, the
                        computer must also own an IP address in the 192.168.0.0/24 network.</li>
                </ul>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Enter <span class="keyword wintitle">admin</span> as your
                    username and <span class="keyword wintitle">administrator</span> as the
                    password.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> You can also use <span class="keyword wintitle">public</span> as a username and
                        leave the password field empty; it has the full administration rights by
                        default. </div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="ph uicontrol">Login</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Results</strong></div>The <span class="ph uicontrol">Information</span> page of
            the Web interface is displayed.</section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title5" id="task_r3h_tyc_gr">
    <h2 class="title topictitle2" id="ariaid-title5">Restarting a Service - MIPT</h2>
    <div class="body taskbody">
        
        <section id="task_r3h_tyc_gr__steps_vbz_tyc_gr"><div class="tasklabel"><strong class="sectiontitle tasklabel">Procedure</strong></div><ol class="ol steps" id="task_r3h_tyc_gr__steps_vbz_tyc_gr"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Services</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">User Service</span>
                    table, locate the service <span class="keyword wintitle">Media IP Transport (MIPT)</span>. </span>
            </li><li class="li step">
                <span class="ph cmd">From the <span class="keyword wintitle">Startup Type</span>
                    selection list next to <span class="keyword wintitle">Media IP Transport (MIPT)</span>, choose
                        <span class="keyword wintitle">Auto</span> if you wish
                    the service to start automatically when the system starts, or <span class="keyword wintitle">Manual</span> to start to the
                    service manually when needed.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">User Service</span>
                    table, click <img class="image" id="task_r3h_tyc_gr__image_epn_f41_5jb" src="https://documentation.media5corp.com/download/attachments/45482024/Restart.png" width="15">.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Results</strong></div>The tab from which you can access the Web pages are no longer greyed out.</section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title6" id="reference_gwm_mdh_x1b">
  <h2 class="title topictitle2" id="ariaid-title6">Endpoint Examples</h2>
  <div class="body refbody">
    <table class="table frame-all" id="reference_gwm_mdh_x1b__table_lv1_tkm_x1b"><caption></caption><colgroup><col style="width:34.48275862068966%"><col style="width:65.51724137931035%"></colgroup><thead class="thead">
          <tr class="row">
            <th class="entry colsep-1 rowsep-1" id="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">Endpoint Name</th>
            <th class="entry colsep-1 rowsep-1" id="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">Description</th>
          </tr>
        </thead><tbody class="tbody">
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">Bri1-2</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">BRI port 1, channel 2</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">Slot2/E1T1-3</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">Channel 3 of the E1 port located in slot 2</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">Port09</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">Port 09 of a Mediatrix 4108-16-24 unit</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">Phone-Fax1</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">Port 1 of a Mediatrix 4102S unit</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">FXS1</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">Port 1 of the FXS card of a Mediatrix C7 unit</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__1">FXO1</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_gwm_mdh_x1b__table_lv1_tkm_x1b__entry__2">Port 1 of the FXO card of a Mediatrix C7 unit</td>
          </tr>
        </tbody></table>
    <section class="section">
      <p class="p">All possible endpoint names are listed in the Endpoint table displayed in the DGW Web
        interface (<span class="keyword wintitle">System</span>/<span class="keyword wintitle">Endpoints</span>). You may also access this table
        via the CLI by using the <span class="keyword parmname">EpAdm.Endpoint</span> command or directly via
        UMN.</p>
    </section>
  </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title7" id="reference_j4g_nbv_gfb">
  <h1 class="title topictitle1" id="ariaid-title7">Online Help</h1>
  <p class="shortdesc"><span class="ph">If you are not familiar with the meaning of the fields and
                buttons, click <span class="keyword wintitle">Show Help</span>, 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 bedisplayed.</span></p>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title8" id="concept_v4k_q3h_1r">
 <h1 class="title topictitle1" id="ariaid-title8">DGW Documentation</h1>
 
 <div class="body conbody"><p class="shortdesc">Mediatrix devices are supplied with an exhaustive set of documentation. </p>
  <p class="p">Mediatrix user documentation is available on the <a class="xref" href="http://documentation.media5corp.com" target="_blank">Media5 Documentation
    Portal</a>.</p>
  <div class="p">Several types of documents were created to clearly present the information you are looking for.
   Our documentation includes:<ul class="ul" id="concept_v4k_q3h_1r__ul_bqy_cjh_1r">
    <li class="li"><strong class="ph b">Release notes</strong>: Generated at each GA release, this document includes the known and
     solved issues of the software. It also outlines the changes and the new features the release
     includes.</li>
    <li class="li"><strong class="ph b">Configuration notes</strong>: These documents are created to facilitate the configuration of a
     specific use case. They address a configuration aspect we consider that most users will need to
     perform. However, in some cases, a configuration note is created after receiving a question
     from a customer. They provide standard step-by-step procedures detailing the values of the
     parameters to use. They provide a means of validation and present some conceptual information.
     The configuration notes are specifically created to guide the user through an aspect of the
     configuration. </li>
    <li class="li"><strong class="ph b">Technical bulletins</strong>: These documents are created to facilitate the configuration of a
     specific technical action, such as performing a firmware upgrade.</li>
    <li class="li"><strong class="ph b">Hardware installation guide</strong>: They provide the detailed procedure on how to safely and
     adequately install the unit. It provides information on card installation, cable connections,
     and how to access for the first time the Management interface.</li>
    <li class="li"><strong class="ph b">User guide</strong>: The user guide explains how to customise to your needs the configuration
     of the unit. Although this document is task oriented, it provides conceptual information to
     help the user understand the purpose and impact of each task. The User Guide will provide
     information such as where and how TR-069 can be configured in the Management Interface, how to
     set firewalls, or how to use the CLI to configure parameters that are not available in the
     Management Interface.</li>
    <li class="li"><strong class="ph b">Reference guide</strong>: This exhaustive document has been created for advanced users. It
     includes a description of all the parameters used by all the services of the Mediatrix units.
     You will find, for example, scripts to configure a specific parameter, notification messages
     sent by a service, or an action description used to create Rulesets. This document includes
     reference information such as a dictionary, and it does not include any step-by-step
     procedures. </li>
   </ul></div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title9" id="concept_fqm_rv4_k4">
 <h1 class="title topictitle1" id="ariaid-title9">Copyright Notice</h1>
 

 <div class="body conbody"><p class="shortdesc">Copyright © 2023 Media5 Corporation.</p>
  <p class="p">This document contains information that is proprietary to Media5 Corporation.</p>
  <p class="p">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.</p>
  <p class="p">This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever,
   without written prior approval by Media5 Corporation.</p>
  <p class="p">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.</p>
 </div>
</article></article></main></body></html>