Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated @ 2022-11-10T12:24:08.170670
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 2022"><meta name="DC.rights.owner" content="(C) Copyright 2022"><meta name="DC.type" content="concept"><meta name="prodname" content="All Mediatrix Units with ISDN cards"><meta name="version" content="DGW 4849.50.27182809"><meta name="platform" content="All"><meta name="DC.date.modified" content="2022-0511-0410"><meta name="DC.date.issued" content="2022-0511-0410"><meta name="DC.date.available" content="2022-0511-0410"><meta name="ChapterNumbering" content="no"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="concept_ijw_h33_5s"><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>ISDN Troubleshooting</title></head><body><header role="banner"><div class="topicmeta title">ISDN Troubleshooting</div><div class="topicmeta date">2022-0511-04<10</div><div class="topicmeta product">All Mediatrix Units with ISDN cards</div><div class="topicmeta version">DGW 4849.50.2718<2809</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/45482024/ISDN%20Troubleshooting.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#concept_ijw_h33_5s">ISDN Troubleshooting</a></li><li><a href="#reference_mtz_n33_5s">Protocols and Connection</a></li><li><a href="#topic_title_Troubleshooting_Tools_d1e17">Troubleshooting Tools</a><ul><li><a href="#concept_ix4_xgm_1r">Troubleshooting</a></li><li><a href="#task_wwl_sm3_5s"> Capturing a Trace Using Wireshark</a></li><li><a href="#task_k5b_kn3_5s">Enabling Syslog Menu</a></li><li><a href="#task_vcb_fr3_5s">Enabling Syslog Filters</a></li></ul></li><li><a href="#topic_title_Physical_Link_Down_d1e22">Physical Link Down</a><ul><li><a href="#task_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a></li><li><a href="#task_j2z_hy3_5s">Configuring ISDN Preset</a></li><li><a href="#task_fhq_31j_5s">Verifying BRI Connection</a></li><li><a href="#task_fjx_pdj_5s">Verifying PRI Connection</a></li><li><a href="#task_tgq_22j_5s">Modifying Port Pinout</a></li></ul></li><li><a href="#reference_djh_kfj_5s">Signalling Down Troubleshooting</a></li><li><a href="#topic_title_Troubleshooting_Failed_Calls_when_Physical_and_Signalling_Status_is_up_d1e29">Troubleshooting Failed Calls when Physical and Signalling Status is up</a><ul><li><a href="#task_mq4_ckj_5s">Troubleshooting SIP to ISDN Calls</a></li><li><a href="#reference_bcf_mnj_5s">Party Number Parameters Default Value</a></li><li><a href="#task_mss_yrj_5s">Troubleshooting Generic Non-Working Calls</a></li><li><a href="#task_l4t_sqj_5s">Troubleshooting ISDN to SIP Calls</a></li></ul></li><li><a href="#task_jlk_r5j_5s">Enabling Calling Line Information Presentation</a></li><li><a href="#task_e4c_yxj_5s">Disabling Double DTMF</a></li><li><a href="#reference_k2g_bwj_5s">Country/Provider Specific Configuration - France</a></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_ijw_h33_5s">
 <h1 class="title topictitle1" id="ariaid-title1">ISDN Troubleshooting</h1>
 <div class="body conbody">
  <p class="p">This document is destined to customers wanting to configure and troubleshoot Mediatrix ISDN
   gateways connected to a PSTN or a PBX ISDN Interface.</p>
  <p class="p">This document provides general tips on how to troubleshoot ISDN issues.</p>
  <p class="p">Different scenarios are analysed and suggestion of possible solutions are proposed.</p>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title2" id="reference_mtz_n33_5s">
  <h1 class="title topictitle1" id="ariaid-title2">Protocols and Connection</h1>
  <div class="body refbody">
    <section class="section">
      <div class="p">The Mediatrix gateways support the following protocols:<ul class="ul" id="reference_mtz_n33_5s__ul_wfc_fl3_5s">
          <li class="li">QSIG<div class="note note note_note"><span class="note__title">Note:</span> The support of the QSIG protocol is restricted to basic calls.</div></li>
          <li class="li">DSS1</li>
          <li class="li">DMS100</li>
          <li class="li">NI2</li>
          <li class="li">R2</li>
          <li class="li">5ESS</li>
        </ul>In the Europe, the DSS1 protocol is mainly used for interconnection with public carrier
        and QSIG is mainly used for connections with PBXs.</div>
      <p class="p">The R2 protocol is more specific to Central America / Latin America countries.</p>
      <p class="p">In North America, the most common protocols are DMS100 and NI2.</p>
      <p class="p">Note that the PTSN configuration can be different from carrier to carrier. Sometimes even
        the same carrier may have a different PSTN configuration. Connecting an ISDN gateway to a
        PBX can be done in point-to-point or point-to-multipoint mode. Please refer to the PBX to
        see if it is configured as point-to-point or point-to-multipoint.</p>
      <div class="p">The Mediatrix unit can be set in TE or NT mode:<ul class="ul" id="reference_mtz_n33_5s__ul_alf_4l3_5s">
          <li class="li">User side (TE): implemented in ISDN terminals (phones, terminal adapters, etc.).<ul class="ul" id="reference_mtz_n33_5s__ul_j5c_pl3_5s">
              <li class="li">Generally, use TE when the Mediatrix unit is used to connect to the PSTN or is
                replacing ISDN phones.</li>
            </ul></li>
          <li class="li">Network side (NT): implemented in the exchange switches of the network operator.<ul class="ul" id="reference_mtz_n33_5s__ul_lxf_5l3_5s">
              <li class="li">Generally, use NT when phones are plugged into the Mediatrix unit or when the
                Mediatrix unit replaces the PSTN.</li>
            </ul></li>
        </ul>Again this configuration will depend on the configuration of the PBX. If the PBX is
        configured as NT, the Mediatrix unit must be configured as TE. If the PBX is configured as
        TE, the Mediatrix unit must be configured as NT.</div>
      <p class="p">PRI cards can be configured as E1 or T1 line. Generally, E1 are available in Europe and T1
        in America</p>
    </section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title3" id="topic_title_Troubleshooting_Tools_d1e17">
   <h1 class="title topictitle1" id="ariaid-title3">Troubleshooting Tools</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title4" id="concept_ix4_xgm_1r">
 <h2 class="title topictitle2" id="ariaid-title4">Troubleshooting</h2>
 
 <div class="body conbody"><p class="shortdesc">The Mediatrix CPE provides several troubleshooting features such as notification
  messages, diagnostic traces and SIP signalling logs. </p>
  <div class="p">The Syslog daemon is a general purpose utility for monitoring applications and network devices
   with the TCP/ IP protocol. With this software, you can monitor useful messages coming from the
   Mediatrix CPE.<ul class="ul" id="concept_ix4_xgm_1r__ul_eg3_dt5_1r">
    <li class="li"><span class="keyword wintitle">Diagnostic Traces</span> are sent using the Syslog to the Technical Assistance
     Centre to further assist in resolving some issues such as Interoperability.</li>
    <li class="li"><span class="keyword wintitle">PCM traces</span> are two different RTP streams made specifically to record
     all analog signals that are either sent or received on the analog or ISDN side of the Mediatrix
     device. PCM traces are an efficient tool to identify problems with: <ul class="ul" id="concept_ix4_xgm_1r__ul_hxy_rt5_1r">
      <li class="li">Echo in your 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 or digital signal</li>
     </ul></li>
    <li class="li"><span class="keyword wintitle">Statistics</span> are collected on each port of the PRI card, on Ping/Pingv6
     on the CLI or on Media. Statistics are collected on: <ul class="ul" id="concept_ix4_xgm_1r__ul_pqw_s4v_1r">
      <li class="li">Packet loss</li>
      <li class="li">Jitter</li>
      <li class="li">Latency</li>
      <li class="li">Packet count</li>
      <li class="li">Octet count</li>
     </ul></li>
    <li class="li"><span class="keyword wintitle">Live Network Captures</span> can be taken with the pcapture command and sent
     to Wireshark located on a separate terminal. The SBC can also capture the SIP/RTP traffic of a
     specific call, selected by rules. The Network Capture will gather information on: <ul class="ul" id="concept_ix4_xgm_1r__ul_ssl_v4v_1r">
      <li class="li">Interoperability</li>
      <li class="li">Timing issues</li>
     </ul>
    </li>
    <li class="li"><span class="keyword wintitle">Configuration scripts </span>can be generated from the configuration running
     on the Mediatrix CPE. This provides the content of your configuration that can be used by
     technical support to troubleshoot your faulty configuration. </li>
   </ul></div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title5" id="task_wwl_sm3_5s">
    <h2 class="title topictitle2" id="ariaid-title5"> Capturing a Trace Using Wireshark</h2>
    <div class="body taskbody">
        <section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>You must have downloaded Wireshark at the following link <a class="xref" href="https://www.wireshark.org/" target="_blank">https://www.wireshark.org/</a> (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. <p class="p">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.</p><p class="p"> Otherwise you will not capture the packets from the unit.
            </p></section>

        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Capture</span> menu,
                    select <span class="keyword wintitle">Capture Options</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Capture</span>
                    selection list, select the Ethernet network adapters to use.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd"> In the <span class="keyword wintitle">(Display) Options</span> section, select the <span class="keyword wintitle">Update list of packet in real time</span>
                    check box. </span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Select the <span class="keyword wintitle">Automatic scrolling in live
                capture</span> check box.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">If troubleshooting a random problem happening weekly, select the <span class="keyword wintitle">Use multiple files</span> check
                    box.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> For the latest Wireshark release, this can be configured via
                            <span class="keyword wintitle">Capture</span>/<span class="keyword wintitle">Options</span>/<span class="keyword wintitle">Ouput</span>/<span class="keyword wintitle">Create
                            a new file automatically after…</span></div>
                </div>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <p class="p">In Wireshark release 2.2.0</p>
            <br><img class="image" id="task_wwl_sm3_5s__image_vhy_w5v_hz" src="https://documentation.media5corp.com/download/attachments/45482024/create_new_file.jpg" width="800"><br>
            <p class="p">In older Wireshark releases</p>
            <br><img class="image" id="task_wwl_sm3_5s__image_hwn_4y1_ws" src="https://documentation.media5corp.com/download/attachments/45482024/Wireshark1.png" width="800"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title6" id="task_k5b_kn3_5s">
    <h2 class="title topictitle2" id="ariaid-title6">Enabling Syslog Menu</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Syslog</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Remote Host</span>
                    field, set the IP address of the PC running the syslog daemon or
                    Wireshark.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Syslog Configuration</span> table,
                    set <span class="keyword wintitle">Diagnostic Traces</span>
                    to <span class="keyword wintitle">Enable</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_k5b_kn3_5s__image_f5j_1r3_5s" src="https://documentation.media5corp.com/download/attachments/45482024/TechnicalAssistanceCentre_enable.png" width="800"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title7" id="task_vcb_fr3_5s">
    <h2 class="title topictitle2" id="ariaid-title7">Enabling Syslog Filters</h2>
    <div class="body taskbody">
        <section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>Must have completed the task <a class="xref" href="#task_k5b_kn3_5s">Enabling Syslog Menu</a></section>
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Syslog</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Syslog Configuration</span> table,
                    click <span class="keyword wintitle">Edit</span> next to
                        <span class="keyword wintitle">Filter</span></span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Module</span> table,
                    set each module's type of syslog traces you want to receive.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_vcb_fr3_5s__image_mdz_st3_5s" src="https://documentation.media5corp.com/download/attachments/45482024/Module.png" width="800"><br>
        </section>
    </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title8" id="topic_title_Physical_Link_Down_d1e22">
   <h1 class="title topictitle1" id="ariaid-title8">Physical Link Down</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title9" id="task_ol3_sv3_5s">
    <h2 class="title topictitle2" id="ariaid-title9">Auto-Detecting and Auto-Configuring ISDN Interfaces</h2>
    <div class="body taskbody">
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div><div class="note note note_note"><span class="note__title">Note:</span> Some parameters cannot be auto configured. For example, the clock mode is
                configured according to the endpoint type, master for NT and slave for TE.</div></section>
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Status</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Automatic Configuration</span>
                    table, from the selection list, choose the interface you wish to auto configure
                    or select all interfaces.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Start Sensing</span>.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Launching the Automatic Configuration may terminate abruptly all ongoing
                        ISDN calls. The auto-configuration may take some time to complete and some
                        of the current ISDN configuration settings might be replaced by new
                        values.</div>
                </div>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div> Under <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Status</span>, the <span class="keyword wintitle">Physical Link</span> and <span class="keyword wintitle">Signaling</span> fields of each interface
            should indicate <span class="keyword wintitle">Up</span>.<br><img class="image" id="task_ol3_sv3_5s__image_zl5_jq2_b2b" src="https://documentation.media5corp.com/download/attachments/45482024/AutomaticConfiguration.png" width="800"><br><br><img class="image" id="task_ol3_sv3_5s__image_bsz_yfk_qmb" src="https://documentation.media5corp.com/download/attachments/45482024/StatusBRIup.png" width="800"><br></section>
    </div>
<nav role="navigation" class="related-links"><div class="linklist relinfo reltasks"><div class="linklistlabel"><strong class="sectiontitle linklistlabel">Next Step</strong></div><ul class="linklist"><li class="linklist"><a class="link" href="#task_j2z_hy3_5s">Configuring ISDN Preset</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title10" id="task_j2z_hy3_5s">
    <h2 class="title topictitle2" id="ariaid-title10">Configuring ISDN Preset</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Status</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">ISDN Preset Configuration</span>
                    table, set the following parameters:</span>
                <ol type="a" class="ol substeps" id="task_j2z_hy3_5s__substeps_nly_3z3_5s">
                    <li class="li substep substepexpand">
                        <span class="ph cmd">Using the dropdown menu, select a <span class="keyword wintitle">Local Preset</span></span>
                        <div class="itemgroup info">
                            <div class="note note note_note"><span class="note__title">Note:</span> Depending on your unit's profile, it may be possible that no
                                preset file are available.</div>
                        </div>
                    </li>
                    <li class="li substep substepexpand">
                        <span class="ph cmd">Using the <span class="keyword wintitle">Preset Name</span> field,
                            give a name to the preset.</span>
                    </li>
                </ol>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_j2z_hy3_5s__image_aqf_g1j_5s" src="https://documentation.media5corp.com/download/attachments/45482024/ISDNPresetConfiguration.png" width="800"><br>
        </section>
    </div>
<nav role="navigation" class="related-links"><div class="linklist relinfo reltasks"><div class="linklistlabel"><strong class="sectiontitle linklistlabel">Next Step</strong></div><ul class="linklist"><li class="linklist"><a class="link" href="#task_fhq_31j_5s">Verifying BRI Connection</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title11" id="task_fhq_31j_5s">
    <h2 class="title topictitle2" id="ariaid-title11">Verifying BRI Connection</h2>
    <div class="body taskbody">
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Check the cable on your BRI interface.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> On a 4400, you can use a straight Ethernet cable. However on a 3400 in NT
                        mode, you will need to use a BRI cross-over cable</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Verify the cable length.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> 
                        <p class="p">The cable length between the Mediatrix gateway and the PBX must not
                            exceed 600 metres</p>
                        <p class="p">For short Bus application (all terminals / wall-plugs are put in parallel
                            at arbitrary positions of the bus): max 120 metres.</p>
                        <p class="p">For extended bus installation (all terminals / wall-plugs are hooked in
                            parallel on the bus on the last 30 to 50 metres of the bus): max 450
                            metres.</p>
                        <p class="p">Proper termination of the ISDN bus / ISDN line on both ends with 100 Ohms
                            is mandatory.</p>
                    </div>
                </div>
            </li></ol></section>
    </div>
<nav role="navigation" class="related-links"><div class="linklist relinfo reltasks"><div class="linklistlabel"><strong class="sectiontitle linklistlabel">Next Step</strong></div><ul class="linklist"><li class="linklist"><a class="link" href="#task_fjx_pdj_5s">Verifying PRI Connection</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title12" id="task_fjx_pdj_5s">
    <h2 class="title topictitle2" id="ariaid-title12">Verifying PRI Connection</h2>
    <div class="body taskbody">
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Check the cable on your PRI interface.</span>
            </li><li class="li step">
                <span class="ph cmd">Straight cable versus PRI Cross-over.</span>
            </li></ol></section>
    </div>
<nav role="navigation" class="related-links"><div class="linklist relinfo reltasks"><div class="linklistlabel"><strong class="sectiontitle linklistlabel">Next Step</strong></div><ul class="linklist"><li class="linklist"><a class="link" href="#task_tgq_22j_5s">Modifying Port Pinout</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title13" id="task_tgq_22j_5s">
    <h2 class="title topictitle2" id="ariaid-title13">Modifying Port Pinout</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Primary Rate Interface</span>.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Not all PRI and/or BRI platforms support Port Pinout.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Interface Configuration</span>
                    table, set the <span class="keyword wintitle">Port Pinout</span> to reflect your
                    configuration.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_tgq_22j_5s__image_fjv_knj_5s" src="https://documentation.media5corp.com/download/attachments/45482024/InterfaceConfiguration_PortPinout.png" width="800"><br>
        </section>
    </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title14" id="reference_djh_kfj_5s">
  <h1 class="title topictitle1" id="ariaid-title14">Signalling Down Troubleshooting</h1>
  <div class="body refbody">
    <section class="section">Make sure you have correctly configured the following:<ul class="ul" id="reference_djh_kfj_5s__ul_xdz_nfj_5s">
        <li class="li">Endpoint Type</li>
        <li class="li">Signalling Protocol</li>
        <li class="li">Line Coding</li>
        <li class="li">Line Framing</li>
      </ul>On some BRI connections, the Signaling status can be <em class="ph i">Down</em> even when the link is
      functional. When the variable Link Establishment is at its default setting “On Demand”, the
      signaling link will be seen as up only when calls occur.</section>
    <section class="section">If the link is correctly configured, we suggest trying a call in both directions even
      if the Signaling Status is Down.</section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title15" id="topic_title_Troubleshooting_Failed_Calls_when_Physical_and_Signalling_Status_is_up_d1e29">
   <h1 class="title topictitle1" id="ariaid-title15">Troubleshooting Failed Calls when Physical and Signalling Status is up</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title16" id="task_mq4_ckj_5s">
    <h2 class="title topictitle2" id="ariaid-title16">Troubleshooting SIP to ISDN Calls</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Call Router</span>/<span class="keyword wintitle">Route Config</span> to
                    verify if a route from a SIP gateway to an ISDN interface is configured.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Primary Rate Interface</span>, and
                    set <span class="keyword wintitle">Calling Name Max Length</span> to 0. </span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Some providers do not accept User-to-user information (UUI) to be sent in
                        setup messages. Any setup containing a UUI Information Element (IE) will be
                        rejected by the provider, most likely with an ISDN Status message. One
                        reason for this is that this feature might not be provided for free.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Verify the setup sent to the ISDN interface by looking at the syslog
                    messages.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Primary Rate Interface</span> and set
                        <span class="keyword wintitle">Preferred Encoding Scheme</span> to
                        <span class="keyword wintitle">G.711 u-law</span></span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> By default, the Mediatrix units are configured to use the a-law codec as
                        encoding scheme in ISDN SETUP messages. A-law is usually used in Europe.
                        Some North-American providers and PBX reject the SETUP message unless it
                        uses the u-law codec</div>
                </div>
            </li></ol></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title17" id="reference_bcf_mnj_5s">
  <h2 class="title topictitle2" id="ariaid-title17">Party Number Parameters Default Value</h2>
  <div class="body refbody">
    <section class="section">DGW sets the following default values: <table class="table frame-all" id="reference_bcf_mnj_5s__table_fc5_k4j_5s"><caption></caption><colgroup><col><col></colgroup><thead class="thead">
            <tr class="row">
              <th class="entry colsep-1 rowsep-1" id="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__1">SIP to ISDN Calls</th>
              <th class="entry colsep-1 rowsep-1" id="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__2">Default value</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__1">TON (called and calling)</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__2">Unknown</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__1">NPI (calling and called)</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__2">Unknown</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__1">SI (calling)</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__2">User-side: not-screened Network-side: network</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__1">ITC (calling)</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__2">3.1 kHz audio</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__1">PI (calling)</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_bcf_mnj_5s__table_fc5_k4j_5s__entry__2"><ol class="ol" id="reference_bcf_mnj_5s__ol_wb2_m4j_5s">
                  <li class="li">When the Calling Party Number E.164 is missing: interworking. In this case,
                    this value overrides any value set by the call router.</li>
                  <li class="li">When CLIR is enabled (user-side only): restricted. In this case, this value
                    overrides any value set by the call router.</li>
                  <li class="li"></li>
                </ol>All other cases: allowed. This is the default value if the two cases above do
                not apply and no value has been set by the call router.</td>
            </tr>
          </tbody></table></section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title18" id="task_mss_yrj_5s">
    <h2 class="title topictitle2" id="ariaid-title18">Troubleshooting Generic Non-Working Calls</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Interop</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Interop Configuration</span> table,
                    set <span class="keyword wintitle">Progress Indicator In Call Proceeding</span> to <span class="keyword wintitle">Disable</span>
                </span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_mss_yrj_5s__image_w22_q5j_5s" src="https://documentation.media5corp.com/download/attachments/45482024/InteropConfiguration_ProgressIndicatorInCallProceeding_Disable.png" width="800"><br>
        </section>
        <section class="example"><div class="tasklabel"><strong class="sectiontitle tasklabel">Example</strong></div>
            <ul class="ul" id="task_mss_yrj_5s__ul_kdz_h5j_5s">
                <li class="li">Depending on the provider or the Pbx, the Mediatrix unit can receive an ISDN
                    STATUS message such as the following:</li>
            </ul>
            <p class="p">IsdnStackL3Msg [1C9F] 0 &lt; Call 22182-Inbound TEI 0 Unicast <strong class="ph b">RECV Status</strong>
                (125) </p>
            <p class="p">IsdnStackL3Msg [1CA0] 0 &lt; IE Cause [Coding: CCITT (0) Location: Public network
                serving local user (2) Cause: <strong class="ph b">Information element non-existent or not implemented
                    (99)</strong>] </p>
            <p class="p">IsdnStackL3Msg [1CA1] 0 &lt; IE Call State [Coding standard: CCITT (0) State value:
                9_INCOMING_CALL_PROCEEDING (9)]</p>
            <p class="p">The cause 99, Information element non-existent or not implemented, refers to the
                previous ISDN message sent. If the previous message contains an IE Progress
                Indicator like in this example:</p>
            <p class="p">IsdnStackL3Msg [1C48] 0 &gt; Call 22182-Inbound TEI 0 <strong class="ph b">SEND</strong><strong class="ph b">Call
                    Proceeding</strong> (2) </p>
            <p class="p">IsdnStackL3Msg [1C49] 0 &gt; IE Channel Id 1/2 [IntID: Implicit Primary (1) 0
                Preferred DChan: Is not D channel Pref: Exclusive] </p>
            <p class="p">IsdnStackL3Msg [1C4A] 0 &gt; IE Channel Id 2/2 [Chan Sel: 1] </p>
            <p class="p"> IsdnStackL3Msg [1C4B] 0 &gt; <strong class="ph b">IE Progress Indicator</strong> [Coding standard: CCITT
                (0) Location: User (0) Description: Destination address is non-ISDN (2)]</p>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title19" id="task_l4t_sqj_5s">
    <h2 class="title topictitle2" id="ariaid-title19">Troubleshooting ISDN to SIP Calls</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Call Router</span>/<span class="keyword wintitle">Route Config</span> to
                    verify if a route from an ISDN interface to a SIP gateway is configured.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Using syslog traces,verify if a SIP INVITE was generated by the gateway after
                    it received the ISDN Setup from the ISDN interface.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> SIP debug must be enabled.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Verify if the provider is sending a ISDN Setup message without the Called
                    Number, with an empty Called number or only part of the Called number (last 4
                    digits for example). If this is the case, it is possible, via the call router,
                    to manipulate the Called number before it is sent via SIP. </span>
            </li></ol></section>
    </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested0" aria-labelledby="ariaid-title20" id="task_jlk_r5j_5s">
    <h1 class="title topictitle1" id="ariaid-title20">Enabling Calling Line Information Presentation</h1>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Services</span>.</span>
            </li><li class="li step stepexpand">

                <span class="ph cmd">From the <span class="keyword wintitle">Select Interface</span> drop-down
                    menu, select the interface you want to configure.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Services Configuration</span> table,
                    set <span class="keyword wintitle">Facility Services</span>
                    to <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set <span class="keyword wintitle">Calling Line Information
                Presentation</span> to <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">MSN</span> field,
                    enter the numbers that will be allowed when a call is incoming from the SIP
                    side.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Please refer to <span class="keyword wintitle">Show Help</span> to apply the
                        appropriate syntax.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">From the <span class="keyword wintitle">Apply To The Following
                Interfaces</span> section, select the interfaces for which the configuration will be applied
                    to.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <p class="p">Support of ISDN FACILITY messages will be enabled. </p>
            <br><img class="image" id="task_jlk_r5j_5s__image_a1n_5d5_xy" src="https://documentation.media5corp.com/download/attachments/45482024/ServicesConfiguration_CallingLineInformationPresentation_Enable.png" width="800"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested0" aria-labelledby="ariaid-title21" id="task_e4c_yxj_5s">
    <h1 class="title topictitle1" id="ariaid-title21">Disabling Double DTMF</h1>
    
    <div class="body taskbody"><p class="shortdesc">By default, Mediatrix units listen for out-of-band and inband DTMF. Some ISDN links
        provide, for the same DTMF, an out-of-band and inband signal, resulting in two DTMFs being
        sent to the SIP proxy.</p>
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Primary Rate Interface</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">Using <span class="keyword wintitle">Select Interface</span>
                    drop down menu, select the interface you want to configure.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Interface Configuration</span>
                    table, set <span class="keyword wintitle">Inband DTMF Dialing</span> to
                        <span class="keyword wintitle">Disable</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_e4c_yxj_5s__image_q4q_syj_5s" src="https://documentation.media5corp.com/download/attachments/45482024/InterfaceConfiguration_InbandDTMFDialing_Disable.png" width="800"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title22" id="reference_k2g_bwj_5s">
  <h1 class="title topictitle1" id="ariaid-title22">Country/Provider Specific Configuration - France</h1>
  <div class="body refbody">
    <section class="section">
      <ul class="ul" id="reference_k2g_bwj_5s__ul_f41_3wj_5s">
        <li class="li">Connection to France Telecom<p class="p">In France, the prevalent protocol is VN6 (a variant of
            ISDN protocol)</p><p class="p">If you are having issues with the ISDN connection, verify with your
            ISDN provider if it is possible to set the ISDN link to Euro ISDN.</p></li>
      </ul>
    </section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title23" id="reference_j4g_nbv_gfb">
  <h1 class="title topictitle1" id="ariaid-title23">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-title24" id="concept_v4k_q3h_1r">
 <h1 class="title topictitle1" id="ariaid-title24">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-title25" id="concept_fqm_rv4_k4">
 <h1 class="title topictitle1" id="ariaid-title25">Copyright Notice</h1>
 

 <div class="body conbody"><p class="shortdesc">Copyright © 2022 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>