<!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="reference"><meta name="DC.relation" scheme="URI" content="#task_hqq_3gp_gjb"><meta name="prodname" content="All PRI/BRI 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="reference_cny_3rq_2jb"><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/62825785/commonltr.css"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/62825785/custom.css"><title>ISDN User Guide</title></head><body><header role="banner"><div class="topicmeta title">ISDN User Guide</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">All PRI/BRI 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/62825785/ISDN%20User%20Guide.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#reference_cny_3rq_2jb">Important Information to Know Before Starting </a></li><li><a href="#reference_knk_fqp_gjb">Definitions </a></li><li><a href="#topic_title_Basic_Concepts_d1e17">Basic Concepts</a><ul><li><a href="#concept_alw_fcw_j1b">Integrated Services Digital Network (ISDN) </a></li><li><a href="#fileconcept">Auto configuration</a></li><li><a href="#concept_fnd_x42_sz">Preset Configuration</a></li></ul></li><li><a href="#topic_title_PRI__E1_T1__Configuration_d1e21">PRI (E1/T1) Configuration</a><ul><li><a href="#reference_swt_mlw_gjb">Important Information for North America</a></li><li><a href="#reference_rf1_yzy_p1b">Supported Signaling Protocols</a></li><li><a href="#reference_x14_bpw_gjb">Important PRI Settings</a></li><li><a href="#task_qsd_542_sz">Using a Preset Configuration File</a></li><li><a href="#task_p1v_ysc_ww">Associating a PRI Port to a Line Type and Protocol</a></li><li><a href="#task_pyd_xq4_ps">Configuring the E1T1 Interface (PRI)</a></li></ul></li><li><a href="#topic_title_BRI_Configuration_d1e28">BRI Configuration</a><ul><li><a href="#reference_ymn_lqp_j1b">Important BRI Settings </a></li><li><a href="#unique_8499844511472627066">Configuring the BRI Interface</a></li></ul></li><li><a href="#task_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a></li><li><a href="#task_hqq_3gp_gjb">Verifying the ISDN Status</a></li><li><a href="#topic_title_Advanced_Concepts_d1e33">Advanced Concepts</a><ul><li><a href="#reference_rmw_2py_bt">Definitions</a></li><li><a href="#unique_4786269231657449205">Inband Tones Generation</a></li><li><a href="#unique_3167006161857219992">Signal Handling</a></li><li><a href="#concept_qlj_3jw_j1b">Interop Parameters</a></li><li><a href="#unique_688785917287342651">Channel Allocation Strategy</a><ul><li><a href="#unique_1263302889938487199">Ascending</a></li><li><a href="#unique_18468365401286859782">Descending</a></li><li><a href="#unique_308325458983334360">Round-Robin Ascending</a></li><li><a href="#unique_16185674932086181749">Round-Robin Descending</a></li></ul></li><li><a href="#topic_title_Ressource_Management_d1e43">Ressource Management</a><ul><li><a href="#unique_15390876061803391911">Reservation of Channels for Incoming and Outgoing Calls</a></li></ul></li><li><a href="#topic_title_Supplementary_Services_d1e45">Supplementary Services</a><ul><li><a href="#concept_m5k_r5y_bt">Supplementary Services Support</a></li><li><a href="#concept_ogz_svy_bt">CLIP</a></li><li><a href="#concept_s4k_nwy_bt">CLIR</a></li><li><a href="#concept_qm1_hxy_bt">CLIR Override</a></li><li><a href="#concept_xj5_czy_bt">Interaction between CLIP, CLIR, and CLIR override</a><ul><li><a href="#reference_lyt_5zy_bt">ISDN Signaling Protocols (Except QSIG)</a></li><li><a href="#reference_bf1_lcz_bt">QSIG Signaling Protocol</a></li></ul></li><li><a href="#concept_ds5_kfz_bt">COLP</a></li><li><a href="#concept_xzd_qfz_bt">COLR</a></li><li><a href="#concept_h3q_wfz_bt">COLR Override</a></li><li><a href="#unique_605350562535959324">CONP</a></li><li><a href="#concept_wny_qgz_bt">Facility Message Waiting Delay</a></li><li><a href="#concept_dxp_vgz_bt">MSN (Multiple Subscriber Number)</a></li><li><a href="#concept_xfw_pmz_bt">Notify</a></li><li><a href="#concept_snl_sj2_ct">Advice of Charge</a></li><li><a href="#concept_lxn_wmz_bt">Calling Party Name</a></li><li><a href="#concept_z13_w4z_bt">Call Rerouting</a></li><li><a href="#unique_6054818391717471267">Default Values for Call Properties</a></li><li><a href="#concept_pnv_hj2_ct">InformationFollowing Operation</a></li><li><a href="#unique_11984515712070810886">Malicious Call Identification</a></li></ul></li><li><a href="#unique_2112192462817180658">Default Values for Call Properties</a></li></ul></li><li><a href="#topic_title_Advanced_Tasks_d1e68">Advanced Tasks</a><ul><li><a href="#task_c5m_gp4_j1b">Enabling ISDN Supplementary Services</a></li><li><a href="#task_rkq_fjw_j1b">Configuring Interop Parameters</a></li><li><a href="#task_tgq_22j_5s">Modifying Port Pinout</a></li><li><a href="#unique_1828743361312342957">Exporting a Preset Configuration File</a></li><li><a href="#reference_phj_xnw_j1b">Other Advanced ISDN Parameters </a></li></ul></li><li><a href="#topic_title_Cabling_Information_d1e75">Cabling Information</a><ul><li><a href="#concept_p4r_tcw_j1b">ISDN Reference Points</a></li><li><a href="#concept_m5t_l1w_yq">BRI S/T Connection (RJ-48)</a></li><li><a href="#unique_1959388957751274265">PRI Connection (RJ-48)</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="reference_cny_3rq_2jb">
<h1 class="title topictitle1" id="ariaid-title1">Important Information to Know Before Starting </h1>
<div class="body refbody">
<section class="section">Before you start, make sure your unit is properly installed. Refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Hardware+Installation+Guides" target="_blank">Hardware Installation Guide of your unit</a>. published on
the Media5 Documentation portal at https://documentation.media5corp.com and refer to the
Cabling Information section.<div class="note caution note_caution"><span class="note__title">Caution:</span> The Mediatrix unit ISDN BRI ports are
configurable to operate as network or terminal ports. The pin-out of the sockets is switched
according to this configuration. Wrong port configurations, wrong cabling or wrong
connections to neighbouring equipment can lead to short circuits in the BRI line
powering.</div><div class="note caution note_caution"><span class="note__title">Caution:</span> The Mediatrix unit BRI ports can be used as a S or T
reference point, but not as U reference points (2-wire). Never connect a U reference point
network equipment or telephony line into the Mediatrix unit BRI ports. If you are using an
S-BUS, you can simultaneously connect only one unit in NT mode and up to 7 units in TE mode.
</div></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title2" id="reference_knk_fqp_gjb">
<h1 class="title topictitle1" id="ariaid-title2">Definitions </h1>
<div class="body refbody">
<table class="table frame-all" id="reference_knk_fqp_gjb__table_r1q_sh2_kjb"><caption></caption><colgroup><col style="width:17.98561151079137%"><col style="width:82.01438848920863%"></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1">Term</th>
<th class="entry colsep-1 rowsep-1" id="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">BRI</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p">Basic Rate Interface </p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">E1</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p">European PRI digital signal carrier. 32 channels (30 voice channels +
synchronization and signaling)</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">ISDN</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p">Integrated Services Digital Network</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">NT</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p">Network Termination. The endpoint on the telephone switch side.</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">PRI</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p">Primary Rate Interface</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">T1</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p p-term-content"> North-American PRI digital signal carrier. 24
channels (23 voice + 1 signaling)</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__1"><dfn class="term">TE</dfn></td>
<td class="entry colsep-1 rowsep-1" headers="reference_knk_fqp_gjb__table_r1q_sh2_kjb__entry__2">
<p class="p"> Terminal Equipment, the endpoint on the customer side</p>
</td>
</tr>
</tbody></table>
</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_Basic_Concepts_d1e17">
<h1 class="title topictitle1" id="ariaid-title3">Basic Concepts</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title4" id="concept_alw_fcw_j1b">
<h2 class="title topictitle2" id="ariaid-title4">Integrated Services Digital Network (ISDN) </h2>
<div class="body conbody"><p class="shortdesc">ISDN is a set of digital transmission protocols defined by a few international standards
body for telecommunications, such as the ITU-T. One or the other of these protocols are accepted
as standards by virtually every telecommunications carrier all over the world.</p>
<div class="p">ISDN replaces the traditional telephone system so that one or two pairs of telephone wires can
carry voice and data simultaneously. It is a fully digital network where all devices and
applications present themselves in a digital form. ISDN is a User-Network Interface (UNI)
signalling protocol with a user and a network side. <ul class="ul" id="concept_alw_fcw_j1b__ul_rqw_v4r_r1b">
<li class="li">The user side is implemented in ISDN terminals (phones, terminal adapters, etc.)</li>
<li class="li">The network side is implemented in the exchange switches of the network operator.</li>
<li class="li">Both sides have different signaling states and messages.</li>
</ul> The Mediatrix unit ISDN interfaces can be configured to work as user (TE) or network (NT)
interfaces. Depending on your product, you can configure two types of ISDN interfaces: <ul class="ul" id="concept_alw_fcw_j1b__ul_d2x_4qx_k1b">
<li class="li">ISDN Basic Rate Interface (BRI)</li>
<li class="li">ISDN Primary Rate Interface (PRI)</li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title5" id="fileconcept">
<h2 class="title topictitle2" id="ariaid-title5">Auto configuration</h2>
<div class="body conbody">
<div class="p">The ISDN auto configuration is a process by which all ISDN interfaces try several configuration
combination in order to obtain a physical link up and then a signaling link up (PRI interfaces
only). The process is started using the <span class="keyword cmdname">Isdn.AutoConfigure</span> command and can be
stopped with the <span class="keyword cmdname">Isdn.CancelAutoConfigure</span> command. Starting the command will
abruptly terminate all ongoing calls on the ISDN interfaces. Once the auto configuration process
completes (successfully or not), a notification is sent reporting the result. If the operation is
successful, the following parameters will be set with the values that provided the link up
(overwriting the user configuration):<ul class="ul" id="fileconcept__ul_kfg_hjz_bt">
<li class="li">Endpoint Type</li>
<li class="li">Clock Mode</li>
<li class="li">Port Pinout (PRI interfaces only)</li>
<li class="li">Line Coding (PRI interfaces only)</li>
<li class="li">Line Framing (PRI interfaces only)</li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title6" id="concept_fnd_x42_sz">
<h2 class="title topictitle2" id="ariaid-title6">Preset Configuration</h2>
<div class="body conbody"><p class="shortdesc">The ISDN Preset Configuration contains a set of values for the configuration of the
parameters used by the ISDN connections. </p>
<p class="p">The preset configuration files are located in the file system persistent memory. Depending on
the Mediatrix unit you are using, the available ISDN Preset configuration files will differ or,
it may also be possible that no preset configuration files are available depending on the
Profile. Preset configuration files are provided by Media5 or can be user-defined, i.e. the
current ISDN configuration was exported from a unit. </p>
<div class="p">Using preset configuration files is especially useful for: <ul class="ul" id="concept_fnd_x42_sz__ul_vhs_fq2_sz">
<li class="li">units that do not use the default values provided by Media5 (for instance, using T1 instead
of E1)</li>
<li class="li">using the same configuration on several units</li>
</ul><div class="note important note_important"><span class="note__title">IMPORTANT:</span> user-defined presets are not kept in the event of a partial or
factory reset. Only script files can be used as preset ISDN configuration files. </div></div>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title7" id="topic_title_PRI__E1_T1__Configuration_d1e21">
<h1 class="title topictitle1" id="ariaid-title7">PRI (E1/T1) Configuration</h1>
<article class="topic reference nested1" aria-labelledby="ariaid-title8" id="reference_swt_mlw_gjb">
<h2 class="title topictitle2" id="ariaid-title8">Important Information for North America</h2>
<div class="body refbody"><p class="shortdesc">Mediatrix units are configured to default for E1, which is used in most countries in
Europe, Middle-East, Africa and Oceania. For the T1 interface used in North America, some
settings MUST be changed.</p>
<table class="table frame-all" id="reference_swt_mlw_gjb__table_dnw_wlw_gjb"><caption></caption><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Setting</th>
<th class="entry colsep-1 rowsep-1" id="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">T1 (North America)</th>
<th class="entry colsep-1 rowsep-1" id="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">E1 (Default)</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Line Coding</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">B8ZS</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">HDB3</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Line Framing</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">ESF (usually), or SF(D4)</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">CRC4 (usually), or NO-CRC4</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Signaling Protocol</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">NI2 (usually)</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">DSS1 (usually)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Preferred Encoding Scheme</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">u-Law</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">a-Law</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Fallback Encoding Scheme</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">a-Law</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">u-Law</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__1">Channel Range</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__2">1-23</td>
<td class="entry colsep-1 rowsep-1" headers="reference_swt_mlw_gjb__table_dnw_wlw_gjb__entry__3">1-30</td>
</tr>
</tbody></table>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title9" id="reference_rf1_yzy_p1b">
<h2 class="title topictitle2" id="ariaid-title9">Supported Signaling Protocols</h2>
<div class="body refbody">
<section class="section">
<table class="table frame-all" id="reference_rf1_yzy_p1b__table_dxr_zzy_p1b"><caption></caption><colgroup><col style="width:23.980815347721823%"><col style="width:76.01918465227818%"></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__1">Protocol </th>
<th class="entry colsep-1 rowsep-1" id="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__1">DSS1</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__2">Digital Subscriber Signaling System No.1</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__1">DMS100</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__2">Digital Multiplex System 100</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__1">NI2</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__2">National ISDN No.2</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__1">5ESS</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__2">5 Electronic Switching System</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__1">QSIG</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rf1_yzy_p1b__table_dxr_zzy_p1b__entry__2">ECMA's protocol for Private Integrated Services Networks</td>
</tr>
</tbody></table>
<div class="note important note_important"><span class="note__title">IMPORTANT:</span> In North America, the official standard is National ISDN2 (NI2).
Virtually all 5ESS, DMS100, and GTD-5 switches have been upgraded to use that standard since
the early 2000's.The "5ESS" and "DMS100" Signaling Properties settings are provided only for
backwards compatibility only with older switches and PBXes, and might not support some
functionalities such as Calling Name Delivery.</div>
</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title10" id="reference_x14_bpw_gjb">
<h2 class="title topictitle2" id="ariaid-title10">Important PRI Settings</h2>
<div class="body refbody">
<section class="section"><span class="keyword wintitle">Endpoint Type, Clock Mode, and Port Pinout</span><div class="p">These settings should
normally be auto-detected (Step 1)<ul class="ul" id="reference_x14_bpw_gjb__ul_kb2_cm2_kjb">
<li class="li"> In TE (Terminal Equipment) mode, the unit is normally in slave mode and will
automatically update its clock from the other (telco) side.</li>
<li class="li">In NT (Network Termination) mode, the unit is normally in master mode and will provide
the clock to the other side.</li>
<li class="li">For more information on clock reference when using multiple interfaces, refer to the
<a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Mediatrix+Gateways+and+ISDN+Clock+Synchronization" target="_blank">Mediatrix Gateways and ISDN Clock Synchronisation
</a> and <a class="xref" href="https://documentation.media5corp.com/pages/viewpage.action?pageId=45483805" target="_blank">Synchronising Unit Operation (TDM Sync)</a>
published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
</ul></div></section>
<section class="section"><span class="keyword wintitle">Signaling Protocol</span><p class="p">Refer to
the <a class="xref" href="#reference_rf1_yzy_p1b">Supported Signaling Protocols</a>
section.</p></section>
<section class="section"><span class="keyword wintitle">Fallback Encoding Scheme</span><p class="p">Only
valid when receiving a SETUP message. The user sending the SETUP message does not indicate
an alternative bearer capability.</p></section>
<section class="section"><span class="keyword wintitle">Channel Range</span><p class="p">This is
typically used for fractional T1 or E1 service.</p><ul class="ul" id="reference_x14_bpw_gjb__ul_xld_4m2_kjb">
<li class="li">Channels start at 1 and make abstraction of the synchronisation and signaling
timeslots.</li>
<li class="li">Channels outside of the range defined for this field are ignored. For example: <ul class="ul" id="reference_x14_bpw_gjb__ul_ymp_qm2_kjb">
<li class="li">Fractional T1 512K: Channel Range 1-8 (corresponds to B channels 1-8, D channel
24)</li>
<li class="li"> Fractional E1 on ramp 10: Channel Range 1-10 (corresponds to timeslot 0 + B
channels 1-10 + D channel 16)</li>
<li class="li">Fractional E1 on ramp 10: Channel Range 1-20 (corresponds to timeslot 0 + B channels
1-15 + D channel 16 + B channels 17-21)</li>
</ul></li>
</ul></section>
<section class="section">
<span class="keyword wintitle">Channels Reserved for Incoming
Calls</span> and
<span class="keyword wintitle">Channels Reserved for Outgoing
Calls</span>
<ul class="ul" id="reference_x14_bpw_gjb__ul_lbr_xm2_kjb">
<li class="li">Bearer channels are by default usable for both incoming and outgoing calls. Use this
range to reserve channels for incoming or outgoing calls.</li>
<li class="li">Channels outside of the range defined by <span class="keyword parmname">ChannelRange</span> parameter are
ignored.</li>
<li class="li">Channels reserved in both <span class="keyword parmname">IncomingChannelRange</span> and
<span class="keyword parmname">OutgoingChannelRange</span> parameters are considered usable for both
incoming and outgoing calls.</li>
<li class="li">The space character is ignored and duplication is not allowed.</li>
<li class="li">Channels must be specified in low to high order.</li>
</ul></section>
<section class="section"><span class="keyword wintitle">Calling Name Max Length</span><p class="p">The
value for calls from SIP to ISDN is set to 34 by default, but ranges from 0 to 82.Some
telephone companies do not allow customers to pass Calling Name and will drop calls if it is
not set to zero.</p></section>
<section class="section"><span class="keyword wintitle">Interface Configuration</span><p class="p">Call properties set in the Call Router have precedence over the default
values of the table. For more details on the Call Router, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Call+Router" target="_blank">Call Router user guide</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</p></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title11" id="task_qsd_542_sz">
<h2 class="title topictitle2" id="ariaid-title11">Using a Preset Configuration File</h2>
<div class="body taskbody">
<section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>If you are using a user-defined preset configuration file, do not forget to upload
it through the file management system, under <span class="keyword wintitle">Management</span>/<span class="keyword wintitle">File</span>. </section>
<section id="task_qsd_542_sz__steps_szb_hkf_sz"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_qsd_542_sz__steps_szb_hkf_sz"><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">ISDN Preset Configuration</span>
table from the <span class="keyword wintitle">Local Preset</span> list, choose the
preset configuration file you wish to import. </span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> In North America, the PRI_NorthAmerica-NI2.cfg contains the recommended
settings for a connexion with most of the telephone operators. </div>
</div>
</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>The preset configuration file will be uploaded to the unit and applied. <div class="note note note_note"><span class="note__title">Note:</span> In
most cases, the unit will be restarted. Please wait a few minutes for the operation
to complete, then log-in again into the Web interface of the unit.</div><br><img class="image" id="task_qsd_542_sz__image_ev2_qzx_k1b" src="https://documentation.media5corp.com/download/attachments/62825785/ISDNPresetConfiguration.png" width="500"><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_p1v_ysc_ww">Associating a PRI Port to a Line Type and Protocol</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_p1v_ysc_ww">
<h2 class="title topictitle2" id="ariaid-title12">Associating a PRI Port to a Line Type and Protocol</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">Hardware</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">PRI Ports Configuration</span> table,
from the <span class="keyword wintitle">Line Type</span>
selection list, select either E1 or T1.</span>
</li><li class="li step">
<span class="ph cmd">From the <span class="keyword wintitle">Signaling</span>
selection list, associate a type of signaling to the PRI port. </span>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
</li><li class="li step">
<span class="ph cmd">Restart the unit.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The selected line type will appear under <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Primary Rate Interface</span>. This is an
example of a PRI port association. <br><img class="image" id="task_p1v_ysc_ww__image_zs2_jcz_zw" src="https://documentation.media5corp.com/download/attachments/62825785/PriPortsConfiguration.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_pyd_xq4_ps">Configuring the E1T1 Interface (PRI)</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_pyd_xq4_ps">
<h2 class="title topictitle2" id="ariaid-title13">Configuring the E1T1 Interface (PRI)</h2>
<div class="body taskbody">
<section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>Endpoint Type, Clock Mode, and Port Pinout: These settings should normally be
auto-detected , therefore, always use <a class="xref" href="#task_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a>
procedure first to automatically detect and to automatically configure your PRI
interface. The manual configuration of the PRI interface should be used for fine tuning
of the configuration. </section>
<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> Before you start, refer to the <a class="xref" href="#reference_swt_mlw_gjb" title="Mediatrix units are configured to default for E1, which is used in most countries in Europe, Middle-East, Africa and Oceania. For the T1 interface used in North America, some settings MUST be changed.">Important Information for North America</a>
section </div>
</section>
<section id="task_pyd_xq4_ps__steps_i5x_fwq_2jb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_pyd_xq4_ps__steps_i5x_fwq_2jb"><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> ISDN ports can be configured while they are active. However they are
internally disabled to modify the configuration and then re-enabled. All
active calls on the port are dropped during this process. Configuration
changes should only be performed during planned down times. Most of the ISDN
parameters change require a restart of the ISDN service to be
applied.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Select Interface</span> drop box,
select the E1/T1 interface you wish to modify.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> Depending on the Mediatrix model, there may be several interfaces.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Modify the parameters as required.</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>
</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_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a></li></ul></div></nav></article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title14" id="topic_title_BRI_Configuration_d1e28">
<h1 class="title topictitle1" id="ariaid-title14">BRI Configuration</h1>
<article class="topic reference nested1" aria-labelledby="ariaid-title15" id="reference_ymn_lqp_j1b">
<h2 class="title topictitle2" id="ariaid-title15">Important BRI Settings </h2>
<div class="body refbody">
<section class="section">
<div class="note caution note_caution"><span class="note__title">Caution:</span> The Mediatrix unit BRI ports can be used as a S or T reference point, but
not as U reference points (2-wire). Never connect a U SCN line or a U TE into the Mediatrix
unit BRI ports. If you are using an S-BUS, you can simultaneously connect only one unit in
NT mode and up to 7 units in TE mode. </div>
</section>
<section class="section"><span class="keyword wintitle">Endpoint Type</span><ul class="ul" id="reference_ymn_lqp_j1b__ul_nnl_3x2_kjb">
<li class="li">Values used for the Mediatrix unit must be opposite to the value used for the PBX. For
instance, if the PBX is set to TE, then the Mediatrix unit must be set to NT. </li>
<li class="li">When the BRI interface <span class="keyword wintitle">Signaling Protocol</span> is set to QSIG, the
endpoint type is only used in the second layer (LAPD) since it is a concept that does not
exist in QSIG.</li>
<li class="li">To use a specific interface as the clock reference, this parameter must be set to TE.
</li>
</ul></section>
<section class="section"><span class="keyword wintitle">Clock Mode</span><ul class="ul" id="reference_ymn_lqp_j1b__ul_wms_mx2_kjb">
<li class="li"><span class="keyword wintitle">Auto</span> should be the value to
use.</li>
<li class="li">In a BRI configuration, setting the clock mode to slave for a NT endpoint can be set for
interop usage, while setting the clock mode to master for a TE endpoint is invalid (slave
mode is automatically applied in this case). For more information on Clock
Synchronisation, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Technical+Bulletins+-+Attachements?preview=%2F45482024%2F45486857%2FMediatrix+Gateways+and+ISDN+Clock+Synchronization.pdf" target="_blank">Technical Bulletin -Mediatrix Gateways and ISDN
Synchronisation</a> and <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Technical+Bulletins+-+Attachements?preview=%2F45482024%2F45483804%2FSynchronising+Unit+Operation+%28TDM+Sync%29.pdf" target="_blank">Technical Bulletin - Synchronising Unit Operation (TDM
Sync)</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
</ul></section>
<section class="section"><span class="keyword wintitle">Monitor Link State Parameter</span><p class="p">When enabled with the <span class="keyword wintitle">Ignore OPTONS on no usable endpoints</span> also
enabled under the <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Interop</span> page, this will influence how the
SIP options are answered.</p></section>
<section class="section"><span class="keyword wintitle">Connection Type</span><p class="p">Depends on
the equipment to which the Mediatrix unit port is connected to and it must be the same for
all interconnected pieces of equipment.</p></section>
<section class="section"><span class="keyword wintitle">Signaling Protocol</span>
<p class="p">Must match the connected ISDN equipment or network.</p></section>
<section class="section"><span class="keyword wintitle">Preferred Encoding Scheme</span><p class="p">Only G.711 u-Law and G.711 a-Law codecs are allowed. G.711 u-Law may not be supported
by DSS1 NT and TE endpoints. It is recommended to use G.711 a-Law as preferred encoding
protocol.</p></section>
<section class="section"><span class="keyword wintitle">Fallback Encoding Scheme</span><p class="p">
Only valid when receiving a SETUP message. The user sending the SETUP message does not
indicate alternative bearer capability.</p></section>
<section class="section"><span class="keyword wintitle">Calling Name Max Length</span><p class="p">The
value for calls from SIP to ISDN ranges from 0 to 82.</p></section>
<section class="section"><span class="keyword wintitle">Exclusive B-Channel
Selection</span><p class="p">When the parameter is enabled only the requested B channel is accepted when a call is
initiated ; if the requested B channel is not available, the call is cleared.</p></section>
<section class="section"><span class="keyword wintitle">Hook-Flash Keypad</span><ul class="ul" id="reference_ymn_lqp_j1b__ul_wpy_yhf_kjb">
<li class="li">Set the actual keypad string that is to be considered as a hook-flash in the Hook-Flash
Keypad field. </li>
<li class="li">An ISDN telephone may send INFORMATION messages that contain a “Keypad Facility”. You
can thus trigger a supplementary service (Hold, Conference, etc.) by sending a keypad
facility. </li>
<li class="li">Since the keypads can be received via several INFORMATION messages, they are accumulated
until they match or reset if the keypad reception timeout (second) has elapsed since the
last keypad has been received. The keypad reception timeout can only be modified via SNMP.
If the keypad reception timeout is set to 0, it disables the timeout, thus assuming that
all keypads will be received in a single INFORMATION message.</li>
<li class="li">Setting this parameter to an empty string disables the hook-flash detection.</li>
<li class="li">The permitted keypad must be made up of IA5 characters. See ITU-T Recommendation
T.50.</li>
</ul></section>
<section class="section"><span class="keyword wintitle">Accepted Progress Causes</span> and
<span class="keyword wintitle">Accepted Status Causes</span><ul class="ul" id="reference_ymn_lqp_j1b__ul_m2v_l3f_kjb">
<li class="li">The space character is not allowed.</li>
<li class="li">Causes must be specified in low to high order.</li>
<li class="li">Cause duplication is not allowed.</li>
</ul></section>
<section class="section"><span class="keyword wintitle">TEI Negotiation </span><p class="p">Only applies
on Point to Multipoint connections.</p></section>
<section class="section"><span class="keyword wintitle">Interface Configuration</span><p class="p">Call
properties set in the Call Router have precedence over the default values of the <span class="keyword wintitle">Interface Configuration</span> table. For more
details on the Call Router, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Call+Router" target="_blank">DGW Configuration Guide - Call Router user guide</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</p></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title16" id="unique_8499844511472627066">
<h2 class="title topictitle2" id="ariaid-title16">Configuring the BRI Interface</h2>
<div class="body taskbody">
<section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>Always use the Auto-sensing feature to automatically detect and to automatically
configure your PRI interface. Use the <a class="xref" href="#task_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a>
procedure first. The manual configuration of the BRI interface should be used for fine
tuning of the configuration. </section>
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>
<p class="p">It is important to take into consideration the following information: </p>
<ul class="ul" id="unique_8499844511472627066__ul_mcx_frp_j1b">
<li class="li"><span class="keyword wintitle">Endpoint Type</span>: Values
used for the Mediatrix unit must be opposite to the value used for the PBX. For
instance, if the PBX is set to TE, then the Mediatrix unit must be set to NT.
When the BRI interface <span class="keyword wintitle">Signaling Protocol</span> is set to
QSIG, the endpoint type is only used in the second layer (LAPD) since it is a
concept that does not exist in QSIG. NOTE: To use a specific interface as the
clock reference, this parameter must be set to TE. For more information on Clock
Synchronisation, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Technical+Bulletins+-+Attachements?preview=%2F45482024%2F45486857%2FMediatrix+Gateways+and+ISDN+Clock+Synchronization.pdf" target="_blank">Technical Bulletin - Mediatrix Gateways and
ISDN Synchronisation</a> and <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Technical+Bulletins+-+Attachements?preview=%2F45482024%2F45483804%2FSynchronising+Unit+Operation+%28TDM+Sync%29.pdf" target="_blank">Synchronising Unit Operation (TDM
Sync)</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
<li class="li"><span class="keyword wintitle">Preferred Encoding Scheme</span>: Only G.711 u-Law and G.711 a-Law codecs are allowed. G.711 u-Law may not be
supported by DSS1 NT and TE endpoints. It is recommended to use G.711 a-Law as
preferred encoding protocol.</li>
<li class="li"><span class="keyword wintitle">Fallback Encoding Scheme</span>: Only G.711 u-Law and G.711 a-Law codecs are supported. Only valid when
receiving a SETUP message. The user sending the SETUP message does not indicate
alternative bearer capability.</li>
<li class="li"><span class="keyword wintitle">Clock Mode</span>: "Auto"
should be the value to use. In a BRI configuration, setting the clock mode to
slave for a NT endpoint can be set for interop usage, while setting the clock
mode to master for a TE endpoint is invalid (slave mode is automatically applied
in this case). For more information on Clock Synchronisation, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Technical+Bulletins+-+Attachements?preview=%2F45482024%2F45486857%2FMediatrix+Gateways+and+ISDN+Clock+Synchronization.pdf" target="_blank">Technical Bulletin - Mediatrix Gateways and
ISDN Synchronisation</a> and <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Technical+Bulletins+-+Attachements?preview=%2F45482024%2F45483804%2FSynchronising+Unit+Operation+%28TDM+Sync%29.pdf" target="_blank">Technical Bulletin - Synchronising Unit
Operation (TDM Sync)</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
<li class="li"><span class="keyword wintitle">Calling Name Max Length</span>:
The value for calls from SIP to ISDN ranges from 0 to 82.</li>
<li class="li"><span class="keyword wintitle">Exclusive B-Channel
Selection</span>:
When the parameter is enabled only the requested B channel is accepted when a
call is initiated; if the requested B channel is not available, the call is
cleared.</li>
<li class="li"><span class="keyword wintitle">Monitor Link State Parameter</span>:
When enabled with the <span class="keyword wintitle">Ignore OPTONS on no usable endpoints</span> also enabled under the <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Interop</span> page, this will
influence how the SIP options are answered.</li>
<li class="li"><span class="keyword wintitle">Connection Type</span>:
depends on the equipment to which the Mediatrix unit port is connected to and it
must be the same for all interconnected pieces of equipment.</li>
<li class="li"><span class="keyword wintitle">Signaling Protocol</span>:
Must match the connected ISDN equipment or network.</li>
<li class="li"><span class="keyword wintitle">TEI Negotiation </span>: Only
applies on Point to Multipoint connections.</li>
<li class="li">Call properties set in the Call Router have precedence over the default values
of the <span class="keyword wintitle">Interface Configuration</span>
table. For more details on the Call Router, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Call+Router" target="_blank">DGW Configuration Guide - Call Router user
guide</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
<li class="li">In strings, the space character is ignored and duplicating causes is not
allowed.</li>
<li class="li">Some ISDN switches may require that the Sending Complete information element be
included in the outgoing SETUP message to indicate that the entire number is
included and there are no further destination digits to be sent.</li>
<li class="li">An ISDN telephone may send INFORMATION messages that contain a “Keypad
Facility”. You can thus trigger a supplementary service (Hold, Conference, etc.)
by sending a keypad facility. Since the keypads can be received via several
INFORMATION messages, they are accumulated until they match or reset if the
keypad reception timeout (second) has elapsed since the last keypad has been
received. The keypad reception timeout can only be modified via SNMP. If the
keypad reception timeout is set to 0, it disables the timeout, thus assuming
that all keypads will be received in a single INFORMATION message</li>
</ul>
</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">Use the <a class="xref" href="#task_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a> procedure first.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Basic Rate Interface</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Select Interface</span> drop-box,
select the BRI interface you wish to modify.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> Depending on the Mediatrix model, there may be several interfaces. To
configure more than one interface at a time, use the <span class="keyword wintitle">Apply To The Following
Interfaces</span> table.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Make all required changes to the displayed parameters.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</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_ol3_sv3_5s">Auto-Detecting and Auto-Configuring ISDN Interfaces</a></li></ul></div></nav></article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested0" aria-labelledby="ariaid-title17" id="task_ol3_sv3_5s">
<h1 class="title topictitle1" id="ariaid-title17">Auto-Detecting and Auto-Configuring ISDN Interfaces</h1>
<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/62825785/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/62825785/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_hqq_3gp_gjb">Verifying the ISDN Status</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested0" aria-labelledby="ariaid-title18" id="task_hqq_3gp_gjb">
<h1 class="title topictitle1" id="ariaid-title18">Verifying the ISDN Status</h1>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>
<p class="p">At any time, it is possible to check the status of the ISDN links.</p>
</section>
<section id="task_hqq_3gp_gjb__steps_nxb_ngp_gjb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_hqq_3gp_gjb__steps_nxb_ngp_gjb"><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">The <span class="keyword wintitle">Physical Link</span> and
<span class="keyword wintitle">Signaling</span> status
will be displayed for each interface.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
<p class="p">If the ISDN cables are properly connected and the basic interface settings are
correct, the Physical Link should be <span class="keyword wintitle">Up</span>.</p>
<div class="note note note_note"><span class="note__title">Note:</span> <span class="keyword wintitle">Signaling</span> will also
usually be "<span class="keyword wintitle">Up</span> on PRI
links. However, in some cases (BRI, On-demand links), it is normal to be in the
<span class="keyword wintitle">Down</span> state, except for
a brief period during call establishment.</div>
<br><img class="image" id="task_hqq_3gp_gjb__image_eyp_ljp_gjb" src="https://documentation.media5corp.com/download/attachments/62825785/Status.png" width="800"><br>
</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title19" id="topic_title_Advanced_Concepts_d1e33">
<h1 class="title topictitle1" id="ariaid-title19">Advanced Concepts</h1>
<article class="topic reference nested1" aria-labelledby="ariaid-title20" id="reference_rmw_2py_bt">
<h2 class="title topictitle2" id="ariaid-title20">Definitions</h2>
<div class="body refbody">
<section class="section">
<table class="table frame-all" id="reference_rmw_2py_bt__table_r5r_dzq_lt"><caption></caption><colgroup><col style="width:25%"><col style="width:75%"></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__1">Term</th>
<th class="entry colsep-1 rowsep-1" id="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__2">Definitions</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__1">Originating Side</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__2">Where the call is initiated on the ISDN network. At the originating side, the
USER (TE) uni-side initiates the call by sending a SETUP message towards the NETWORK
(NT). Then, the NT interface redirects the call to some other network, for example
SS7 or VoIP.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__1">Destination Side</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__2">Where the call reaches its ISDN destination. The NT interface at the
destination receives the call from another network, then sends a SETUP message over
the ISDN link to one or more TE interfaces.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__1">ISDN Interface</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__2">A physical ISDN port, either a BRI or PRI interface.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__1">IsdnInterface</td>
<td class="entry colsep-1 rowsep-1" headers="reference_rmw_2py_bt__table_r5r_dzq_lt__entry__2">This is the 4th layer of the ISDN stack, referred in <a class="xref" href="https://www.itu.int/rec/T-REC-Q.931" target="_blank">ITU-T
Q.931</a> (05/98) as the Resource Management and Call Control entities.</td>
</tr>
</tbody></table>
</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title21" id="unique_4786269231657449205">
<h2 class="title topictitle2" id="ariaid-title21">Inband Tones Generation</h2>
<div class="body conbody">
<p class="p">In an ISDN network, most of the call setup tones are played locally by the TE equipments (i.e.
telephone handset), although some require that the tones be played inband by the NT peer.</p>
<p class="p">When interworking with other networks occurs, such as in the IsdnInterface, the need for the tones to be played inband is more likely to arise.</p>
<p class="p">The IsdnInterface has configurability to enable inband tones to be played locally, on a per-interface basis. This option is present when the IsdnInterface is acting as both the NT and the TE UNI-side. However, in TE mode only, the ringback tone is played.</p>
<p class="p">The Call Setup tones (dial tone, ringback, etc.) are played in the direction where the call has been initiated. The call disconnection tones are played in both directions, but of course will not arrive to the peer who disconnected the call.</p>
<p class="p">When an inband tone is played, a Progress Indicator IE #8 "Inband information or appropriate
pattern available" is added to the ISDN message corresponding to the call state change, and in a
PROGRESS ISDN message if no state change is occurring.</p>
<p class="p">On TE interfaces, as soon as the NT peer advertises that it plays inband tones through a Progress
Indicator IE #8 or #1, the local inband tones generation is disabled for the rest of the call.
Refer to the <var class="keyword varname">UseImplicitInbandInfoEnable</var> interop parameter for special
handling of Progress Indicator #1.</p>
<p class="p">Whenever a tone is played inband locally or when the ISDN peer advertises that inband information is available, the CallManager is notified. The IP media path can then be opened earlier in the call, and can be closed with some delay after the call disconnection initiation. However, the configuration and associated behaviors of the higher-level entities are out of the scope of this document.</p>
<p class="p">The following tables summarize the inband tones generation behaviour for both NT and TE endpoint
types.</p>
<table class="table frame-all" id="unique_4786269231657449205__table_fpb_3ry_bt"><caption></caption><colgroup><col style="width:27.700831024930743%"><col style="width:39.05817174515235%"><col style="width:33.24099722991689%"></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_fpb_3ry_bt__entry__1">Signal IE Handling Enabled</th>
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_fpb_3ry_bt__entry__2">Inband Tones Generation Enabled</th>
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_fpb_3ry_bt__entry__3">Inband Tone Played</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__1">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__2">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__3">No</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__1">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__2">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__3">Yes</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__1">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__2">Don't Care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_fpb_3ry_bt__entry__3">No</td>
</tr>
</tbody></table>
<table class="table frame-all" id="unique_4786269231657449205__table_tct_lry_bt"><caption></caption><colgroup><col><col><col><col><col></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_tct_lry_bt__entry__1">Signal IE Handling Enabled</th>
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_tct_lry_bt__entry__2">Signal IE Received</th>
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_tct_lry_bt__entry__3">Inband Tones Generation Enabled</th>
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_tct_lry_bt__entry__4">NT Peer Advertised Inband Tones</th>
<th class="entry colsep-1 rowsep-1" id="unique_4786269231657449205__table_tct_lry_bt__entry__5">Inband Tone Played</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__1">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__2">Don't care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__3">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__4">Don't Care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__5">No</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__1">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__2">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__3">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__4">Don't Care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__5">Yes</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__1">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__2">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__3">Don't Care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__4">Don't Care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__5">No</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__1">No</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__2">Don't Care</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__3">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__4">Yes</td>
<td class="entry colsep-1 rowsep-1" headers="unique_4786269231657449205__table_tct_lry_bt__entry__5">No</td>
</tr>
</tbody></table>
<div class="note note note_note"><span class="note__title">Note:</span> When the signaling protocol is set to QSIG, the Signal IE does not exist so it has no effect
on the inband tones generation. These inband tones are played if the inband tones generation is
activated on the incoming side of the call.</div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title22" id="unique_3167006161857219992">
<h2 class="title topictitle2" id="ariaid-title22">Signal Handling</h2>
<div class="body conbody">
<p class="p">The Signal IE is used by the NT ISDN interface to tell its TE interfaces peers that they must
generate an inband tone locally. Thus, the Signal IEs are sent by the NT only.</p>
<p class="p">When the Signal IE handling is enabled on a given TE interface, the inband tones will be played
towards the IP gateway when a Signal IE is received. On a NT interface, a Signal IE will be
inserted in the ISDN messages sent to the TE peer when appropriate. </p>
<div class="note note note_note"><span class="note__title">Note:</span> If the signaling protocol is set to "NI-2" (National ISDN-2) on that interface, the Signal
IE handling is forced to be enabled for a NT interface.</div>
<div class="note note note_note"><span class="note__title">Note:</span> When the signaling protocol is set to QSIG, the Signal IE is not used.</div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title23" id="concept_qlj_3jw_j1b">
<h2 class="title topictitle2" id="ariaid-title23">Interop Parameters</h2>
<p class="shortdesc">Interop parameters allow the Mediatrix unit to properly work, communicate, or connect
with specific ISDN devices.</p>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title24" id="unique_688785917287342651">
<h2 class="title topictitle2" id="ariaid-title24">Channel Allocation Strategy</h2>
<div class="body conbody">
<div class="p">The ISDN interface supports 4 allocation strategy modes:<ul class="ul" id="unique_688785917287342651__ul_rwg_fnx_bt">
<li class="li">ascending;</li>
<li class="li">descending;</li>
<li class="li">round-robin ascending;</li>
<li class="li">round-robin descending.</li>
</ul>The Channel Allocation Strategy is configurable separately for each ISDN interface. </div>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title25" id="unique_1263302889938487199">
<h3 class="title topictitle3" id="ariaid-title25">Ascending</h3>
<div class="body conbody">
<p class="p">In this mode, the IsdnInterface always allocates the free channel that has the lowest number. </p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title26" id="unique_18468365401286859782">
<h3 class="title topictitle3" id="ariaid-title26">Descending</h3>
<div class="body conbody">
<p class="p">The highest-numbered free channel is allocated.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title27" id="unique_308325458983334360">
<h3 class="title topictitle3" id="ariaid-title27">Round-Robin Ascending</h3>
<div class="body conbody">
<p class="p">Starting from the enabled channel with the lowest number, the channels are selected increasingly
at each allocation. </p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title28" id="unique_16185674932086181749">
<h3 class="title topictitle3" id="ariaid-title28">Round-Robin Descending</h3>
<div class="body conbody">
<p class="p">Same as round-robin ascending, except that it is exactly the opposite!</p>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested1 nobody" aria-labelledby="ariaid-title29" id="topic_title_Ressource_Management_d1e43">
<h2 class="title topictitle2" id="ariaid-title29">Ressource Management</h2>
<article class="topic concept nested2" aria-labelledby="ariaid-title30" id="unique_15390876061803391911">
<h3 class="title topictitle3" id="ariaid-title30">Reservation of Channels for Incoming and Outgoing Calls</h3>
<div class="body conbody">
<p class="p">Channels can be reserved for incoming calls or for outgoing calls.</p>
<p class="p">The <span class="keyword parmname">IncomingChannelRange</span> and <span class="keyword parmname">OutgoingChannelRange</span>
parameters are defined for this purpose.</p>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested1 nobody" aria-labelledby="ariaid-title31" id="topic_title_Supplementary_Services_d1e45">
<h2 class="title topictitle2" id="ariaid-title31">Supplementary Services</h2>
<article class="topic concept nested2" aria-labelledby="ariaid-title32" id="concept_m5k_r5y_bt">
<h3 class="title topictitle3" id="ariaid-title32">Supplementary Services Support</h3>
<div class="body conbody">
<p class="p">Three generic protocols are defined for the control of supplementary services, two of which are
stimulus, the third being functional.</p>
<div class="p">These protocols are:<ul class="ul" id="concept_m5k_r5y_bt__ul_ixn_z5y_bt">
<li class="li">Keypad protocol;</li>
<li class="li">Feature key management protocol;</li>
<li class="li">Functional protocol.</li>
</ul>The Functional protocol consists of two categories of procedures. The first category, called
the separate message approach, uses separate message types to indicate a desired function. The
HOLD and RETRIEVE set of messages are identified for this category. </div>
<p class="p">The <span class="keyword parmname">FacilityServicesEnable</span> parameter is used to control the second
category, called the common information element procedure, which uses the FACILITY information
element.</p>
<p class="p">When the facility services are disabled and the interface receives a FACILITY message, it
answers it with a STATUS. When the facility services are enabled, the interface processes the
FACILITY messages.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title33" id="concept_ogz_svy_bt">
<h3 class="title topictitle3" id="ariaid-title33">CLIP</h3>
<div class="body conbody">
<p class="p">In ISDN, the Calling Line Information Presentation (CLIP) is an optional service offered to the
called party which provides the calling party’s ISDN number. When the service is enabled, a
Calling Party Number Information Element (CPN IE) containing the caller’s IA5 digits is sent in
the SETUP ISDN message.</p>
<p class="p">CLIP is supplemented by privacy rules defined by <a class="xref" href="#concept_s4k_nwy_bt">CLIR</a> and <a class="xref" href="#concept_qm1_hxy_bt">CLIR Override</a>. Refer to the diagrams in the <a class="xref" href="#concept_xj5_czy_bt">Interaction between CLIP, CLIR, and CLIR override</a> section for details.</p>
<p class="p">For all ISDN signaling protocols except QSIG, operation is as follows: on the originating side,
the TE interface always sends the Calling Party Number IE (unless CLIP is disabled). It is up to
the NT interface at the destination side to apply the appropriate privacy rules. If the originating side is
NT, the Calling Party number is sent only if the <span class="keyword parmname">Calling Number</span> parameter is not set
to 'Restricted' or if the <span class="keyword parmname">Override flag</span> parameter is set to 'Enabled'.</p>
<p class="p">CLIP is enabled through the <span class="keyword parmname">ClipEnable</span> parameter, which can take the
following values:</p>
<table class="table frame-all" id="concept_ogz_svy_bt__table_d5v_lwy_bt"><caption></caption><colgroup><col style="width:11.11111111111111%"><col style="width:88.88888888888889%"></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1">Disable</td>
<td class="entry colsep-1 rowsep-1">Calling Party Number IE is not sent.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Enable</td>
<td class="entry colsep-1 rowsep-1">Calling Party Number IE is sent in the SETUP message.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">UserOnly</td>
<td class="entry colsep-1 rowsep-1">Calling Party Number IE is sent in the SETUP message only if the ISDN interface is
configured as a TE.</td>
</tr>
</tbody></table>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title34" id="concept_s4k_nwy_bt">
<h3 class="title topictitle3" id="ariaid-title34">CLIR</h3>
<div class="body conbody">
<p class="p">The Calling Line Information Restriction (CLIR) is a supplementary service offered to the
calling party to restrict presentation of the calling party’s ISDN number to the called
party.</p>
<p class="p">CLIR uses the Calling Party Number (CPN) IE’s Presentation Indicator (PI) to disable
presentation of the calling number to the called party. CLIR can be disabled by the CLIR override
option, described later. Refer to the diagrams in the <a class="xref" href="#concept_xj5_czy_bt">Interaction between CLIP, CLIR, and CLIR override</a> section for details.</p>
<p class="p">For all ISDN signaling protocols except QSIG, operation is as follows: when the service is
enabled on a TE originating interface, the Calling Party Number IE’s Presentation Indicator field
is set to "Restricted" upon transmission of an ISDN SETUP message from TE to NT. However, the TE
must include the IA5 digits in the Calling Party Number.</p>
<p class="p">When the service is enabled on a NT interface that receives a call, the Calling Party number IE
Presentation Indicator is set to "Restricted" in the calling property returned to the call
managing system.</p>
<p class="p">For QSIG, when the service is enabled at the outgoing interface, the <span class="keyword parmname">Calling Party
number IE Presentation Indicator</span> parameter is set to 'Restricted'. At the incoming side, this
parameter has no effect. However, if the PI flag is set to "Restricted" in the received CPN IE,
the calling party number is removed. See <a class="xref" href="https://www.ecma-international.org/publications/standards/Ecma-148.htm" target="_blank">ECMA-148</a> section 8.</p>
<p class="p">CLIR is enabled through the <span class="keyword parmname">ClirEnable</span> parameter, which can take the
following values:</p>
<table class="table frame-all" id="concept_s4k_nwy_bt__table_zfy_ywy_bt"><caption></caption><colgroup><col style="width:8.333333333333332%"><col style="width:91.66666666666666%"></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1">Disable</td>
<td class="entry colsep-1 rowsep-1">There is no privacy restriction applied on the CLIP service.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Enable</td>
<td class="entry colsep-1 rowsep-1">
<div class="p"><u class="ph u">ISDN signaling protocols (except QSIG):</u>
<ul class="ul" id="concept_s4k_nwy_bt__ul_agy_ywy_bt">
<li class="li">TE interface that sends the SETUP message at the originating network side: The PI is set
to "Restricted" in the CPN IE inserted in the SETUP message sent to the ISDN. However, the
calling number is included in the CPN IE.</li>
<li class="li">NT interface that receives the SETUP message at the originating network side: When
receiving the SETUP message, the PI is forced to "Restricted" in the CPN IE received from
the TE. The calling number itself is forwarded.</li>
</ul></div>
<div class="p"><u class="ph u">QSIG signaling protocol:</u>
<ul class="ul" id="concept_s4k_nwy_bt__ul_bgy_ywy_bt">
<li class="li">Sending a SETUP message: The PI is set to "Restricted" in the CPN IE inserted in the
SETUP message sent to the ISDN, unless the CLIR override option is set. However, even if PI
is set to "Restricted", the calling number is included in the CPN IE.</li>
<li class="li">Receiving a SETUP message: If PI is set in the received message, the calling party
number is removed, unless the CLIR override option is set.</li>
</ul></div>
</td>
</tr>
</tbody></table>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title35" id="concept_qm1_hxy_bt">
<h3 class="title topictitle3" id="ariaid-title35">CLIR Override</h3>
<div class="body conbody">
<p class="p">CLIR override is an option that allows the calling party number to be presented to the
destination party even when the Calling Party Number (CPN) IE’s Presentation Indicator (PI) is
set to "Restricted". This option is typically used for police or emergency services.</p>
<p class="p">For all ISDN signaling protocols except QSIG, operation is as follows: if the CLIR Override is
enabled on the NT interface at the originating side, the Calling Party Number IA5 digits is included
in the Calling Party Number IEs even if the Presentation Indicator is set to "Restricted".</p>
<p class="p">For QSIG, the Calling Line Information Restriction Override is a service offered at the
destination interface. If the CLIR Override is not enabled and the Presentation Indicator is set
to "Restricted" then the Calling Number is not presented. See <a class="xref" href="https://www.ecma-international.org/publications/standards/Ecma-148.htm" target="_blank">ECMA-148</a> section 8.</p>
<p class="p">Refer to the diagrams in the <a class="xref" href="#concept_xj5_czy_bt">Interaction between CLIP, CLIR, and CLIR override</a>
section for details.</p>
<p class="p">CLIR override is enabled through the <span class="keyword parmname">ClirOverrideEnable</span> parameter, which
can take the following values:</p>
<table class="table frame-all" id="concept_qm1_hxy_bt__table_hb3_5yy_bt"><caption></caption><colgroup><col style="width:12.5%"><col style="width:87.5%"></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1">Disable</td>
<td class="entry colsep-1 rowsep-1">The parameter has no effect.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Enable</td>
<td class="entry colsep-1 rowsep-1">
<div class="p"><u class="ph u">ISDN signaling protocols (except QSIG):</u>
<ul class="ul" id="concept_qm1_hxy_bt__ul_ib3_5yy_bt">
<li class="li">The override option acts on the NT interface of the destination network side. It
prevents the number to be removed from the CPN IE inserted in the SETUP message sent to
the destination TE.</li>
</ul></div>
<div class="p"><u class="ph u">QSIG signaling protocol:</u>
<ul class="ul" id="concept_qm1_hxy_bt__ul_jb3_5yy_bt">
<li class="li">The override option prevents the calling name to be removed from the CPN IE in a
received SETUP message.</li>
</ul></div>
</td>
</tr>
</tbody></table>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title36" id="concept_xj5_czy_bt">
<h3 class="title topictitle3" id="ariaid-title36">Interaction between CLIP, CLIR, and CLIR override</h3>
<div class="body conbody">
<p class="p">The following diagrams show how <a class="xref" href="#concept_ogz_svy_bt">CLIP</a>, <a class="xref" href="#concept_s4k_nwy_bt">CLIR</a> and
<a class="xref" href="#concept_qm1_hxy_bt">CLIR Override</a> override work together to bring (or not) the calling
party number from the call originator to the call destination. Refer to the <a class="xref" href="#reference_lyt_5zy_bt">ISDN Signaling Protocols (Except QSIG)</a> and <a class="xref" href="#reference_bf1_lcz_bt">QSIG Signaling Protocol</a> sections for the corresponding diagrams. Call flow must
be read from the left (originating network side) to the right (destination network side).</p>
<p class="p">These diagrams also show on which interfaces the <span class="keyword parmname">ClipEnable</span>,
<span class="keyword parmname">ClirEnable</span> and <span class="keyword parmname">ClirOverrideEnable</span> parameters have
an effect. This is where they must be configured.</p>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested3" aria-labelledby="ariaid-title37" id="reference_lyt_5zy_bt">
<h4 class="title topictitle4" id="ariaid-title37">ISDN Signaling Protocols (Except QSIG)</h4>
<div class="body refbody">
<section class="section">
<div class="p">The Mediatrix unit can play four different roles: <ul class="ul" id="reference_lyt_5zy_bt__ul_ash_zzy_bt">
<li class="li">TE interface at the Originating Network Side;</li>
<li class="li">NT interface at the Originating Network Side;</li>
<li class="li">TE interface at the Destination Network Side;</li>
<li class="li">NT interface at the Destination Network Side.</li>
</ul></div>
<div class="p">The following diagram illustrates an end-to-end call where all four roles are played
by Mediatrix units: <br><div class="imagecenter"><img class="image imagecenter" id="reference_lyt_5zy_bt__image_aqf_jcp_wt" src="https://documentation.media5corp.com/download/attachments/62825785/MediatrixFourRoles.png" width="765"></div><br></div>
</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested3" aria-labelledby="ariaid-title38" id="reference_bf1_lcz_bt">
<h4 class="title topictitle4" id="ariaid-title38">QSIG Signaling Protocol</h4>
<div class="body refbody">
<section class="section">In QSIG, the ISDN interfaces have a peer-to-peer relationship.<p class="p">To describe how
CLIP/CLIR/CLIR override work together, we only need to identify the interface that sends the
SETUP message and the interface that receives it.</p>
<br><div class="imagecenter"><img class="image imagecenter" id="reference_bf1_lcz_bt__image_qcm_kcp_wt" src="https://documentation.media5corp.com/download/attachments/62825785/QSIG_SigProc.png" width="394"></div><br></section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title39" id="concept_ds5_kfz_bt">
<h3 class="title topictitle3" id="ariaid-title39">COLP</h3>
<div class="body conbody">
<p class="p">In ISDN, the Connected Line Identification Presentation is an optional service offered at the
originating interface by the NT peer. When the service is enabled, a Connected Line Identification
Presentation Element containing the connected number IA5 digits is sent under some conditions in
the CONNECT ISDN message.</p>
<p class="p">On the originating side, the TE interface always sends the Connected Party Number IE, it is up
to the NT interface at the destination side to apply the appropriate privacy rules. If the originating side
is NT, the Connected Party number is sent only if the Connected Number is not set to Restricted
or if the Override flag is enabled.</p>
<p class="p">For QSIG, the Connected Line Information Presentation is also an optional service offered at
the outgoing and incoming interface. If available, the Connected Party Number IE containing the
connected IA5 digits is included in the CONNECT ISDN message at the outgoing interface. However,
the Connected Party Number is not presented at the incoming interface if the Connected Number is
"Restricted" and the Override flag is not enabled see <a class="xref" href="https://www.ecma-international.org/publications/standards/Ecma-148.htm" target="_blank">ECMA-148</a>, section 6.</p>
<p class="p">The COLP can also be affected by the <span class="keyword parmname">uCP_ISDN_COLP_NUMBER</span> call property in
the same way that the <a class="xref" href="#unique_605350562535959324">CONP</a> is affected by
<span class="keyword parmname">uCP_ISDN_CONP_NAME</span> call property. See <a class="xref" href="#unique_605350562535959324">CONP</a> section
for more information.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title40" id="concept_xzd_qfz_bt">
<h3 class="title topictitle3" id="ariaid-title40">COLR</h3>
<div class="body conbody">
<p class="p">Generally, the Connected Line Identification Restriction is a service offered to the TE at the
originating interface. </p>
<p class="p">When the service is enabled on a TE originating interface, the Connected Party Number IE’s
Presentation Indicator field is set to "Restricted" upon transmission of an ISDN CONNECT message
from TE to NT interface. However, the TE interface must include the IA5 digits in the Connected Party Number.</p>
<p class="p">For QSIG, when the service is enabled at the outgoing interface, the <span class="keyword parmname">Connected Party
number IE Presentation Indicator</span> parameter is set to 'Restricted'. At the incoming side, this
parameter has no effect. See <a class="xref" href="https://www.ecma-international.org/publications/standards/Ecma-148.htm" target="_blank">ECMA-148</a> section 8.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title41" id="concept_h3q_wfz_bt">
<h3 class="title topictitle3" id="ariaid-title41">COLR Override</h3>
<div class="body conbody">
<p class="p">In ISDN, the Connected Line Identification Restriction Override is a service offered at the
originating interface by the NT peer. </p>
<p class="p">If the CLIR Override is enabled on the NT interface at the originating interface, the Connected Party
Number IA5 digits are included in the Connected Party Number IEs even if the Presentation
Indicator is set to "Restricted".</p>
<p class="p">For QSIG, this parameter has no effect. See <a class="xref" href="https://www.ecma-international.org/publications/standards/Ecma-148.htm" target="_blank">ECMA-148</a> section 8.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title42" id="unique_605350562535959324">
<h3 class="title topictitle3" id="ariaid-title42">CONP</h3>
<div class="body conbody">
<p class="p">The Connected Name identification Presentation (CONP) is a supplementary service
which provides the name of the answering or alerting user to the calling user.</p>
<p class="p">For ISDN-PBX to IP-PBX calls, if the <span class="keyword parmname">PrivacyHeadersInResponse</span> parameter is enabled, the
<span class="keyword parmname">uCP_ISDN_CONP_NAME</span> call property will be set from the 180 Ringing, 183 Session Progressing,
or 200 OK SIP message accordingly to the values of the P-Asserted-Identity SIP header. If the
<span class="keyword parmname">ConpEnable</span> is enabled, the ISDN CONP called name and connected name will be set accordingly
to the value of the <span class="keyword parmname">uCP_ISDN_CONP_NAME</span> call property respectively in the ISDN Alerting and Connect
message.</p>
<p class="p">The following diagram shows a detailed call from ISDN-PBX to IP-PBX with the parameters involved on both the IP
and ISDN sides.</p>
<p class="p"><img class="image" src="https://documentation.media5corp.com/download/attachments/62825785/ConpISDNtoSIP.png"></p>
<p class="p">For IP-PBX to ISDN-PBX calls, if the <span class="keyword parmname">ConpEnable</span> parameter is enabled, the
<span class="keyword parmname">uCP_ISDN_CONP_NAME</span> call property will be set from the ISDN Alerting, ISDN Progress,
or ISDN Connect from the value of the Called or Connected Name Facility
Information Element. If the <span class="keyword parmname">PrivacyHeadersInResponse</span> parameter is enabled,
the P-Asserted-Identity SIP header friendly name will be set to the
<span class="keyword parmname">uCP_ISDN_CONP_NAME</span> call property.</p>
<p class="p">The following diagram shows a detailed call from IP-PBX to ISDN-PBX with the parameters involved on both the IP
and ISDN sides.</p>
<p class="p"><img class="image" src="https://documentation.media5corp.com/download/attachments/62825785/ConpSIPtoISDN.png"></p>
<p class="p">If the number of characters in the connected/called party name exceeds 50, the gateway will truncate
the excess characters.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title43" id="concept_wny_qgz_bt">
<h3 class="title topictitle3" id="ariaid-title43">Facility Message Waiting Delay</h3>
<div class="body conbody">
<p class="p">Upon reception of a SETUP from the remote peer, the interface can optionally wait for a
configurable amount of time for a FACILITY message before processing the call. As soon as it
receives a FACILITY message or the delay expires, it goes on with normal call processing. The
delay is configured via the <span class="keyword parmname">MaximumFacilityWaitingDelay</span> parameter.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title44" id="concept_dxp_vgz_bt">
<h3 class="title topictitle3" id="ariaid-title44">MSN (Multiple Subscriber Number)</h3>
<div class="body conbody">
<p class="p">The Multiple Subscriber Number is a service allowing the TE to configure up to three numbers.
This service is available only for a BRI interface configured in TE Point To Multipoint. When
this service is enabled in the TE, the Called Party Number (Called E.164) received from IE is
matched with these numbers. If the Called Party Number is found, the call can be processed. In
the case where the E.164 is not matched, the call is silently discarded.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title45" id="concept_xfw_pmz_bt">
<h3 class="title topictitle3" id="ariaid-title45">Notify</h3>
<div class="body conbody">
<p class="p">The NOTIFY is an ISDN service independent of the HOLD and RETRIEVE. It serves only to notify an
ISDN endpoint when the remote peer, usually a SIP endpoint, holds or resumes a call. So a NOTIFY
REMOTE HOLD message is sent to the ISDN endpoint when the remote peer puts the call on hold, and
a NOTIFY REMOTE RETRIEVAL message is sent when the remote peer resumes the call. </p>
<p class="p">If the ISDN <span class="keyword parmname">SignalingChannelOutgoingNotifyEnable</span> paramater is disabled, no
NOTIFY message is sent.</p>
<p class="p">The BRI phone can use this message to inform the user of the new call state, by displaying the
remote hold or retrieval message on its LCD screen for example. Note that the BRI phone keeps the
voice path opened, so the hold tone or MOH can be heard.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title46" id="concept_snl_sj2_ct">
<h3 class="title topictitle3" id="ariaid-title46">Advice of Charge</h3>
<div class="body conbody">
<p class="p">To enable the Advice of Charge (AOC) support on the ISDN interface you must enable the FACILITY
services and at least one of the following AOC support: AOC-E (End of Call) or AOC-D (During the
Call).</p>
<div class="note note note_note"><span class="note__title">Note:</span> Since the AOC from ISDN interface to SIP is currently not supported, enabling the AOC on an
ISDN interface configured as TE (user side) is only meaningful when using hairpinning.</div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title47" id="concept_lxn_wmz_bt">
<h3 class="title topictitle3" id="ariaid-title47">Calling Party Name</h3>
<div class="body conbody">
<div class="p">Calling Party Name can be received and sent through three different methods: <ul class="ul" id="concept_lxn_wmz_bt__ul_vgn_knz_bt">
<li class="li">Facility information element;</li>
<li class="li">Display information element;</li>
<li class="li">User-User information element.</li>
</ul></div>
<div class="p">When receiving an incoming call, the Calling Party Name value comes from the provided IE, in
this order:<ul class="ul" id="concept_lxn_wmz_bt__ol_enw_mnz_bt">
<li class="li">Display</li>
<li class="li">Facility</li>
<li class="li">User-User</li>
</ul></div>
<p class="p">Calling Party Name is accepted in a Display Information Element only when explicitly identified
as a Calling Party Name (i.e. only when "Display Type" = "Calling Party Name" in the information
element).</p>
<div class="p">When initiating a call, Calling Party Name is sent according to the method selected in the
<span class="keyword parmname">CallingNameDelivery</span> parameter. If the method selected in the
<span class="keyword parmname">CallingNameDelivery</span> parameter is not supported for the protocol in use, the default
method for this protocol is used. The following table shows which method is used vs configuration
of <span class="keyword parmname">CallingNameDelivery</span>:
<table class="table frame-all" id="concept_lxn_wmz_bt__table_eb5_tnz_bt"><caption></caption><colgroup><col><col><col><col><col></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__1">Protocol</th>
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2" colspan="4">CallingNameDelivery</th>
</tr>
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__3"></th>
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__4">eFacility</th>
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__5">eDisplay</th>
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__6">eUserUser</th>
<th class="entry colsep-1 rowsep-1" id="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__7">eSignalingProtocol</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__1 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__3"><strong class="ph b">DSS1</strong></td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__4">IE User-User</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__5">IE User-User</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__6">IE User-User</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__7">IE User-User</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__1 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__3"><strong class="ph b">Dms100</strong></td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__4">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__5">IE Display</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__6">IE Display</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__7">IE Display</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__1 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__3"><strong class="ph b">NI-2</strong></td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__4">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__5">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__6">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__7">IE Facility</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__1 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__3"><strong class="ph b">5ESS</strong></td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__4">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__5">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__6">IE User-User </td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__7">IE Facility</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__1 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__3"><strong class="ph b">QSIG</strong></td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__4">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__5">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__6">IE Facility</td>
<td class="entry colsep-1 rowsep-1" headers="concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__2 concept_lxn_wmz_bt__table_eb5_tnz_bt__entry__7">IE Facility</td>
</tr>
</tbody></table>
</div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title48" id="concept_z13_w4z_bt">
<h3 class="title topictitle3" id="ariaid-title48">Call Rerouting</h3>
<div class="body conbody">
<p class="p">The Call Rerouting supplementary service allows to reroute an incoming public ISDN call
(originated from PSTN) within or beyond the private ISDN network (such a PBX) as specified in the
ETS30020701, section 10.5. The Rerouting data are received and relayed through a FACILITY message
containing a Facility Information Element. The Rerouting data are encoded in a CallRerouteing
invoke component as specified in the ETS30020701, section 7.</p>
<p class="p">In a Mediatrix typical CallRerouting scenario, when the CallRerouting supplementary service is
enabled (the <span class="keyword parmname">Isdn.SignalingChannelFacilityServicesEnable</span> parameter is
enabled and the <span class="keyword parmname">Isdn.SignalingChannelCallReroutingBehavior</span> parameter is set
to "RelayReroute" or "ProcessLocally") and a Facility Information Element containing a
CallRerouteing invoke component is received via a FACILITY message on a TE endpoint (from the
private network), the ISDN service parses the CallRerouting data and forward it to the
CallManager via a specific CallMessage. </p>
<p class="p">To prevent infinite CallRerouting loops, the ISDN service inspects the rerouteingCounter value
and returns an error if a loop is detected or if the maximal rerouteingCounter value allowed by
the ETS300 207 01 is reached (>5). When the CallRerouting service is not supported
(<span class="keyword parmname">Isdn.SignalingChannelFacilityServicesEnable</span> parameter is disabled or
<span class="keyword parmname">Isdn.SignalingChannelCallReroutingBehavior</span> set to "Unsupported"), the
CallRerouting request is automatically rejected.</p>
<p class="p">Upon reception of a CallMessage specifying a Rerouting request, the ISDN service inspects the
CallRerouting properties set and according to the
<span class="keyword parmname">Isdn.SignalingChannelCallReroutingBehavior</span> parameter, the services takes an
action. If the parameter is set to "RelayReroute", a Facility Information Element containing a
CallRerouteing invoke component is transmitted to the ISDN peer (public network side) via a
FACILITY message. The ISDN service waits for an answer from the peer. </p>
<p class="p">If the parameter is set to "ProcessLocally" or a negative CallRerouting answer is received (a
negative answer received would mean that the public network side (PSTN) is unable to complete the
call Rerouting request), the Isdn service initiates a new call to process locally the call
Rerouting request. The new call is requested to the CallManager without specifying a destination
interface to force the CallRouter service to select the appropriate route. If the new call is
routed to an ISDN interface, the ISDN service sends a SETUP containing a DivertingLegInformation2
invoke component in the Facility IE as specified in the ETS 300 207 01, section 10.2 and section
10.4. The data related to the call diversion set in the DivertingLegInformation2 are transferred
from the CallRerouting properties.</p>
<div class="note note note_note"><span class="note__title">Note:</span> Upon reception of the CallMessage requesting a Rerouteing, the ISDN service
automatically releases the current call whatever if the
<span class="keyword parmname">Isdn.SignalingChannelCallReroutingBehavior</span> parameter is set to
"RelayReroute" or "ProcessLocally".</div>
<p class="p">An illustration of a typical ISDN Call Rerouting scenario (Call Forward Unconditionnal) in a
Mediatrix device would be as the following sequence diagram:</p>
<br><img class="image" id="concept_z13_w4z_bt__image_yfw_fj2_ct" src="https://documentation.media5corp.com/download/attachments/62825785/CallRerouting.png" width="800"><br>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title49" id="unique_6054818391717471267">
<h3 class="title topictitle3" id="ariaid-title49">Default Values for Call Properties</h3>
<div class="body conbody">
<p class="p">Each ISDN interface can be configured with default values for the following parameters in the Calling Party Number IE and the Called Party Number IE.</p>
<div class="p">These default values apply only to outgoing ISDN calls: <table class="table frame-all" id="unique_6054818391717471267__table_dfk_hlz_bt"><caption></caption><colgroup><col><col><col></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Information Element (IE)</th>
<th class="entry colsep-1 rowsep-1" id="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Parameter</th>
<th class="entry colsep-1 rowsep-1" id="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">Configuration Parameter</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Type of Number (TON)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">DefaultCallingTon</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Numbering Plan Indication (NPI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">DefaultCallingNpi</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Presentation Indicator (PI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">DefaultCallingPi</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Screening Indicator (SI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">DefaultCallingSi</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Called Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Type of Number (TON)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">DefaultCalledTon</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__1">Called Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__2">Numbering Plan Indication (NPI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_6054818391717471267__table_dfk_hlz_bt__entry__3">DefaultCalledNpi</td>
</tr>
</tbody></table></div>
<p class="p">These parameters provide default values that are inserted in the Calling Party Number IE and the
Called Party Number IE when these values are not already provided by the call properties.</p>
<p class="p">Another way to control these values is by using the "Properties Manipulation" feature of the Call
Router. This method has precedence over the parameters described here.</p>
<div class="p">The following paragraphs provide additional information on how these parameters work:<ul class="ul" id="unique_6054818391717471267__ul_u14_llz_bt">
<li class="li">TON and NPI: If the value is not available from the Call Properties, the corresponding value
from <span class="keyword parmname">DefaultCallingTon</span>, <span class="keyword parmname">DefaultCalledTon</span>.
<span class="keyword parmname">DefaultCallingNpi</span> or <span class="keyword parmname">DefaultCalledNpi</span> parameter is used
directly.</li>
<li class="li">PI: If PI is not available from the Call Properties, its value is determined by the
following two steps.<ul class="ul" id="unique_6054818391717471267__ol_y1v_plz_bt">
<li class="li">First, it is set to the default value defined by "DefaultCallingPi".</li>
<li class="li">Second, it can be overridden by the CLIP and CLIR services: the value can be set to
"Restricted" by the CLIR service and the value can be set to "NotAvailable" if there is no
number to forward.</li>
</ul></li>
<li class="li">SI: Like the other parameters, the <span class="keyword parmname">DefaultCallingSi</span> parameter is ignored if the SI
value is provided by the Call Properties. If SI is not provided by the call properties, it is
set to the value provided by <span class="keyword parmname">DefaultCallingSi</span> except for one special case:
when the <span class="keyword parmname">DefaultCallingSi</span> parameter is set to "Context Dependent", the unit applies
internal rules to set SI to the value that makes most sense according to context. These
internal rules are as follows:<ul class="ul" id="unique_6054818391717471267__ul_imy_vlz_bt">
<li class="li">For all signaling protocols except QSIG:<ul class="ul" id="unique_6054818391717471267__ul_ixn_wlz_bt">
<li class="li">If interface is configured as NT (network side), SI is set to "NetworkProvided"</li>
<li class="li">If interface is configured as TE (user side), SI is set to
"UserProvidedNotScreened"</li>
</ul></li>
<li class="li">For QSIG signaling protocol:<ul class="ul" id="unique_6054818391717471267__ul_e25_zlz_bt">
<li class="li">If the calling party number string is not empty, SI is set to
"UserProvidedVerifiedAndPassed"</li>
<li class="li">If the calling party number string is empty, SI is set to "NetworkProvided"</li>
</ul></li>
</ul></li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title50" id="concept_pnv_hj2_ct">
<h3 class="title topictitle3" id="ariaid-title50">InformationFollowing Operation</h3>
<div class="body conbody">
<p class="p">The "informationFollowing" operation is supported for NI2 signaling only.</p>
<p class="p">When a SETUP message is received containing an "informationFollowing" operation, the unit
immediately sends a PROCEEDING message. The unit then waits normally for a FACILITY message
containing the calling party name, for a maximum time configured with the
<span class="keyword parmname">MaximumFacilityWaitingDelay</span> parameter.</p>
<p class="p">The only difference between this behavior and the usual behavior (i.e. without the
"informationFollowing" operation), is the immediate sending of the PROCEEDING message before
waiting for the calling party name.</p>
<p class="p">Note that the "informationFollowing" operation is mutually exclusive with the configuration
parameter <span class="keyword parmname">CallProceedingDelay</span>, which configures a delay before sending the
PROCEEDING message. If the PROCEEDING message is sent due to the "informationFollowing"
operation, the <span class="keyword parmname">CallProceedingDelay</span> parameter is ignored.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title51" id="unique_11984515712070810886">
<h3 class="title topictitle3" id="ariaid-title51">Malicious Call Identification</h3>
<div class="body conbody">
<p class="p">Malicious Call Identification (MCID) is a supplementary service that enables the service provider
to identify the source of malicious calls. A user who receives a malicious call from another network
can notify the PSTN of the malicious nature of the call, allowing the offnet system to take action,
such as notifying legal authorities.</p>
<p class="p">To invoke the MCID supplementary service, the called user shall send a mCIDRequest invoke component
carried by a Facility information element in a FACILITY message.</p>
<div class="p">To indicate that the service has been accepted, the network shall send:<ul class="ul" id="unique_11984515712070810886__ul_ixn_z5y_bt">
<li class="li">if accepted, a mCIDRequest return result component, or</li>
<li class="li">if rejected, a mCIDRequest return error component carried by a Facility information element in a FACILITY message</li>
</ul></div>
<div class="note note note_note"><span class="note__title">Note:</span>
For customer needs, the mCIDRequest invoke can be sent from both Network and User sides.
This behavior does not follow the signaling flow in EN 300 130-1 Annex A which stipulates
that the mCIDRequest invoke is only sent from the User side to Network side.
</div>
<p class="p">To enable the MCID supplementary service, the
<span class="keyword parmname">Isdn.SignalingChannel.FacilityServicesEnable</span> and
<span class="keyword parmname">Isdn.SignalingChannel.McidEnable</span> parameters must both be set to Enable.
Further more, the MCID feature is only available for DSS1 signaling.</p>
<p class="p">An illustration of a typical ISDN MCID scenario in a Mediatrix device:
<img class="image" src="https://documentation.media5corp.com/download/attachments/62825785/McidFunc.png" width="400"></p>
<p class="p">On the reception of a SIP INFO message containing the <code class="ph codeph">P-Call-Info: malicious</code>
proprietary header, the associated ISDN call will send an ISDN FACILITY message indicating
that this call is tagged as malicious.</p>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title52" id="unique_2112192462817180658">
<h2 class="title topictitle2" id="ariaid-title52">Default Values for Call Properties</h2>
<div class="body conbody">
<p class="p">Each ISDN interface can be configured with default values for the following parameters in the Calling Party Number IE and the Called Party Number IE.</p>
<div class="p">These default values apply only to outgoing ISDN calls: <table class="table frame-all" id="unique_2112192462817180658__table_dfk_hlz_bt"><caption></caption><colgroup><col><col><col></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Information Element (IE)</th>
<th class="entry colsep-1 rowsep-1" id="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Parameter</th>
<th class="entry colsep-1 rowsep-1" id="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">Configuration Parameter</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Type of Number (TON)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">DefaultCallingTon</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Numbering Plan Indication (NPI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">DefaultCallingNpi</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Presentation Indicator (PI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">DefaultCallingPi</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Calling Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Screening Indicator (SI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">DefaultCallingSi</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Called Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Type of Number (TON)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">DefaultCalledTon</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__1">Called Party Number</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__2">Numbering Plan Indication (NPI)</td>
<td class="entry colsep-1 rowsep-1" headers="unique_2112192462817180658__table_dfk_hlz_bt__entry__3">DefaultCalledNpi</td>
</tr>
</tbody></table></div>
<p class="p">These parameters provide default values that are inserted in the Calling Party Number IE and the
Called Party Number IE when these values are not already provided by the call properties.</p>
<p class="p">Another way to control these values is by using the "Properties Manipulation" feature of the Call
Router. This method has precedence over the parameters described here.</p>
<div class="p">The following paragraphs provide additional information on how these parameters work:<ul class="ul" id="unique_2112192462817180658__ul_u14_llz_bt">
<li class="li">TON and NPI: If the value is not available from the Call Properties, the corresponding value
from <span class="keyword parmname">DefaultCallingTon</span>, <span class="keyword parmname">DefaultCalledTon</span>.
<span class="keyword parmname">DefaultCallingNpi</span> or <span class="keyword parmname">DefaultCalledNpi</span> parameter is used
directly.</li>
<li class="li">PI: If PI is not available from the Call Properties, its value is determined by the
following two steps.<ul class="ul" id="unique_2112192462817180658__ol_y1v_plz_bt">
<li class="li">First, it is set to the default value defined by "DefaultCallingPi".</li>
<li class="li">Second, it can be overridden by the CLIP and CLIR services: the value can be set to
"Restricted" by the CLIR service and the value can be set to "NotAvailable" if there is no
number to forward.</li>
</ul></li>
<li class="li">SI: Like the other parameters, the <span class="keyword parmname">DefaultCallingSi</span> parameter is ignored if the SI
value is provided by the Call Properties. If SI is not provided by the call properties, it is
set to the value provided by <span class="keyword parmname">DefaultCallingSi</span> except for one special case:
when the <span class="keyword parmname">DefaultCallingSi</span> parameter is set to "Context Dependent", the unit applies
internal rules to set SI to the value that makes most sense according to context. These
internal rules are as follows:<ul class="ul" id="unique_2112192462817180658__ul_imy_vlz_bt">
<li class="li">For all signaling protocols except QSIG:<ul class="ul" id="unique_2112192462817180658__ul_ixn_wlz_bt">
<li class="li">If interface is configured as NT (network side), SI is set to "NetworkProvided"</li>
<li class="li">If interface is configured as TE (user side), SI is set to
"UserProvidedNotScreened"</li>
</ul></li>
<li class="li">For QSIG signaling protocol:<ul class="ul" id="unique_2112192462817180658__ul_e25_zlz_bt">
<li class="li">If the calling party number string is not empty, SI is set to
"UserProvidedVerifiedAndPassed"</li>
<li class="li">If the calling party number string is empty, SI is set to "NetworkProvided"</li>
</ul></li>
</ul></li>
</ul></div>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title53" id="topic_title_Advanced_Tasks_d1e68">
<h1 class="title topictitle1" id="ariaid-title53">Advanced Tasks</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title54" id="task_c5m_gp4_j1b">
<h2 class="title topictitle2" id="ariaid-title54">Enabling ISDN Supplementary Services</h2>
<div class="body taskbody">
<section id="task_c5m_gp4_j1b__steps_t3b_bq4_j1b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_c5m_gp4_j1b__steps_t3b_bq4_j1b"><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,
select the interface for which you wish to enable ISDN optional services.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Services Configuration</span> table,
enable the required ISDN options.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> To activate the ISDN hold feature, the <span class="keyword wintitle">Default Hook Flash
Processing</span> must be set to <span class="keyword wintitle">Using Signaling Protocol</span>
(Under<span class="keyword wintitle">Telephony</span>/<span class="keyword wintitle">Services</span>).</div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> For the Date/Time IE to be sent, the SNTP server must be configured (Under
<span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Host</span>).</div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> The AOC features are not available in the NI2 and QSIG signaling
protocols. Refer to <a class="xref" href="#task_pyd_xq4_ps">Configuring the E1T1 Interface (PRI)</a>
to configure the signaling protocol.</div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> To enable AOC support on the ISDN interface, the <span class="keyword wintitle">Facility Services</span>
parameter and <span class="keyword wintitle">AOC-E (End-of-Call)</span> or
<span class="keyword wintitle">AOC-D (During the Call)</span>
parameter must be set to <span class="keyword wintitle">Enable</span>. Since the AOC
from ISDN interface to SIP is currently not supported, enabling the AOC on
an ISDN interface configured as TE (user side) is only meaningful when using
hair-pinning. </div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> The <span class="keyword wintitle">Call Rerouting Behavior</span>
parameter is not available in the NI2 and QSIG signaling protocols. Refer to
<a class="xref" href="#task_pyd_xq4_ps">Configuring the E1T1 Interface (PRI)</a>
to configure the signaling protocol.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
</li></ol></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title55" id="task_rkq_fjw_j1b">
<h2 class="title topictitle2" id="ariaid-title55">Configuring Interop Parameters</h2>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>Interop parameters can be configured for PRI and BRI interfaces.</section>
<section id="task_rkq_fjw_j1b__steps_hgn_zjw_j1b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_rkq_fjw_j1b__steps_hgn_zjw_j1b"><li class="li step stepexpand">
<span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Interop</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Select Interface</span> drop down,
choose the interface for which you wish to configure the interop
parameters.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> To select more than one interface at a time, if available on the unit, use
the <span class="keyword wintitle">Apply To The Following
Interfaces</span> table.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Interface Configuration</span>
table, complete the fields as required.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
</li></ol></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title56" id="task_tgq_22j_5s">
<h2 class="title topictitle2" id="ariaid-title56">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/62825785/InterfaceConfiguration_PortPinout.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-title57" id="unique_1828743361312342957">
<h2 class="title topictitle2" id="ariaid-title57">Exporting a Preset Configuration File</h2>
<div class="body taskbody">
<section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>If you are using a user-defined preset configuration file, do not forget to upload
it through the file management system. </section>
<section id="unique_1828743361312342957__steps_szb_hkf_sz"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_1828743361312342957__steps_szb_hkf_sz"><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">ISDN Preset Configuration</span>
table, in the <span class="keyword wintitle">Preset Name</span> field, enter the name for the exported preset configuration file.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> We strongly recommend indicating the type of unit and date of export as
the name of the preset configuration file. For example:
MTXC740_20230215.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Save</span>.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
<br><img class="image" id="unique_1828743361312342957__image_y3l_sby_k1b" src="https://documentation.media5corp.com/download/attachments/62825785/ISDNPresetConfiguration_export.png" width="500"><br>The preset configuration file will be displayed
under <span class="keyword wintitle">Management</span>/<span class="keyword wintitle">File</span>, in the <span class="keyword wintitle">Internal files</span> table.</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title58" id="reference_phj_xnw_j1b">
<h2 class="title topictitle2" id="ariaid-title58">Other Advanced ISDN Parameters </h2>
<div class="body refbody">
<section class="section">
<div class="p">Although the services can be configured in great part in the Web browser, some aspects of
the configuration can only be completed with the MIB parameters by:<ul class="ul" id="reference_phj_xnw_j1b__ul_gfn_14v_wr">
<li class="li">using a MIB browser</li>
<li class="li">using the CLI</li>
<li class="li">creating a configuration script containing the configuration parameters</li>
</ul></div>
</section>
<section class="section"><h3 class="title sectiontitle"><span class="keyword parmname">Interop Play Local Ringback When No
MediaStream</span></h3>Configure the
<span class="keyword wintitle">isdn.InteropPlayLocalRingbackWhenNoMediaStream</span> parameter to set how to
play the local ringback when there is no stream. For more details, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Reference+Guide" target="_blank">DGW Configuration Guide - Reference Guide</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title59" id="topic_title_Cabling_Information_d1e75">
<h1 class="title topictitle1" id="ariaid-title59">Cabling Information</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title60" id="concept_p4r_tcw_j1b">
<h2 class="title topictitle2" id="ariaid-title60">ISDN Reference Points</h2>
<div class="body conbody"><p class="shortdesc">ISDN specifies a number of reference points that define logical interfaces between the
various equipment types on an ISDN access line. </p>
<div class="p">The Mediatrix unit supports the following ISDN reference points: <ul class="ul" id="concept_p4r_tcw_j1b__ul_uz1_wcw_j1b">
<li class="li">S: The reference point between user terminals and the NT2. This is used in
point-to-multipoint BRI connections. </li>
<li class="li">T: The reference point between NT1 (Modem) and NT2 (PBX) devices. This is used in point-to-
point PRI/BRI connections.</li>
</ul> All other ISDN reference points are not supported.<br><img class="image" id="concept_p4r_tcw_j1b__image_oyw_zdw_j1b" src="https://documentation.media5corp.com/download/attachments/62825785/ISDNReferencePoints.png" width="500"><br></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title61" id="concept_m5t_l1w_yq">
<h2 class="title topictitle2" id="ariaid-title61">BRI S/T Connection (RJ-48)</h2>
<div class="body conbody">
<div class="p"><div class="note caution note_caution"><span class="note__title">Caution:</span> Always use standard telecommunication cables with a minimum of 26 AWG wire
gauge.</div>BRI S/T connections use two pairs of wires: one pair for transmission and the
second pair for reception. It is wired so that pins 3 and 6 are on one twisted pair and pins 4
and 5 are on a second pair according to common wiring standards which meet the TIA/EIA 568A and
568B requirements.</div>
<div class="note caution note_caution"><span class="note__title">Caution:</span> The Mediatrix unit ISDN BRI ports are configurable to operate as network or
terminal ports. The pin-out of the sockets is switched according to this configuration. Wrong
port configurations, wrong cabling or wrong connections to neighbouring equipment can lead to
short circuits in the BRI line powering. </div>
<div class="p">
<br><img class="image" id="concept_m5t_l1w_yq__image_bqj_dzj_2r" src="https://documentation.media5corp.com/download/attachments/62825785/RJ-45-solo.jpg"><br>
</div>
<table class="table frame-all" id="concept_m5t_l1w_yq__table_qxq_tgf_1r"><caption></caption><colgroup><col style="width:50"><col style="width:100"><col style="width:100"></colgroup><thead class="thead">
<tr class="row">
<th class="entry align-center colsep-1 rowsep-1" id="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">Pin#</th>
<th class="entry align-center colsep-1 rowsep-1" id="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">TE mode</th>
<th class="entry align-center colsep-1 rowsep-1" id="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">NT mode</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">1</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Not Connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Not Connected</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">2</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Not Connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Not Connected</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">3</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Tx +</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Rx + </td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">4</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Rx +</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Tx +</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">5</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Rx -</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Tx -</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">6</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Tx -</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Rx -</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">7</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Not connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Not Connected</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__1">8</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__2">Not connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="concept_m5t_l1w_yq__table_qxq_tgf_1r__entry__3">Not Connected</td>
</tr>
</tbody></table>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title62" id="unique_1959388957751274265">
<h2 class="title topictitle2" id="ariaid-title62">PRI Connection (RJ-48)</h2>
<div class="body conbody">
<div class="p"><div class="note caution note_caution"><span class="note__title">Caution:</span> Always use standard telecommunication cables with a minimum of 26 AWG wire
gauge.</div> PRI connections use two pairs of wires: one pair for transmission and the second
pair for reception. It is wired so that pins 1 and 2 are on one twisted pair and pins 4 and 5 are
on a second pair according to common wiring standards which meet the TIA/EIA 568A and 568B
requirements.</div>
<div class="p">
<div class="note note note_note"><span class="note__title">Note:</span> The Mediatrix unit PRI ports can be used as a T reference point, but not as U reference
points (2-wire). Never connect a U PSTN line or a U TE into the Mediatrix unit PRI
ports.</div><br><img class="image" id="unique_1959388957751274265__image_akl_tyj_2r" src="https://documentation.media5corp.com/download/attachments/62825785/RJ-45-solo.jpg"><br></div>
<table class="table frame-all" id="unique_1959388957751274265__table_qxq_tgf_1r"><caption></caption><colgroup><col style="width:50"><col style="width:100"><col style="width:100"></colgroup><thead class="thead">
<tr class="row">
<th class="entry align-center colsep-1 rowsep-1" id="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">Pin #</th>
<th class="entry align-center colsep-1 rowsep-1" id="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">NT Mode</th>
<th class="entry align-center colsep-1 rowsep-1" id="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">TE Mode</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">1</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Transmit #2 (+)</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Receive #2 (+)</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">2</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Transmit #1 (-)</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Receive #1 (-)</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">3</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Not connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Not connected</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">4</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Receive #2 (+)</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Transmit #2 (+)</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">5</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Receive #1 (-)</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Transmit #1 (-)</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">6</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Not connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Not connected</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">7</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Not connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Not connected</td>
</tr>
<tr class="row">
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__1">8</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__2">Not connected</td>
<td class="entry align-center colsep-1 rowsep-1" headers="unique_1959388957751274265__table_qxq_tgf_1r__entry__3">Not connected</td>
</tr>
</tbody></table>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title63" id="reference_j4g_nbv_gfb">
<h1 class="title topictitle1" id="ariaid-title63">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-title64" id="concept_v4k_q3h_1r">
<h1 class="title topictitle1" id="ariaid-title64">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-title65" id="concept_fqm_rv4_k4">
<h1 class="title topictitle1" id="ariaid-title65">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> |
