<!DOCTYPE html
SYSTEM "about:legacy-compat">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2023"><meta name="DC.rights.owner" content="(C) Copyright 2023"><meta name="DC.type" content="concept"><meta name="prodname" content="Mediatrix Units with ISDN Interface (PRI/BRI)"><meta name="version" content="DGW 49.12.28842941"><meta name="platform" content="Sentinel"><meta name="DC.date.modified" content="2023-0308-2809"><meta name="DC.date.issued" content="2023-0308-2809"><meta name="DC.date.available" content="2023-0308-2809"><meta name="ChapterNumbering" content="no"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="concept_rkw_fvv_ts"><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>Mediatrix Gateways and ISDN Clock Synchronization</title></head><body><header role="banner"><div class="topicmeta title">Mediatrix Gateways and ISDN Clock Synchronization</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">Mediatrix Units with ISDN Interface (PRI/BRI)</div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/62825785/Mediatrix%20Gateways%20and%20ISDN%20Clock%20Synchronization.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#concept_rkw_fvv_ts">ISDN Clock Mode</a><ul><li><a href="#task_wyz_zcw_ts">Setting the Clock Mode</a></li></ul></li><li><a href="#concept_ils_szv_ts">ISDN Clock Reference</a><ul><li><a href="#task_g3n_jhb_ww">Selecting the Source of the Clock Reference</a></li></ul></li><li><a href="#concept_o2w_l2b_5s">Current Clock Reference</a></li><li><a href="#reference_sm4_fbw_ts">Mediatrix Unit Clock Synchronization</a></li><li><a href="#reference_kfq_wbw_ts">Direct ISDN Connection Between Endpoints</a></li><li><a href="#concept_b5r_bfw_ts">IP Connection Between ISDN Networks</a></li><li><a href="#reference_j4g_nbv_gfb">Online Help</a></li><li><a href="#concept_v4k_q3h_1r">DGW Documentation</a></li><li><a href="#concept_fqm_rv4_k4">Copyright Notice</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1"><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="nested0" aria-labelledby="ariaid-title1" id="concept_rkw_fvv_ts">
<h1 class="title topictitle1" id="ariaid-title1">ISDN Clock Mode</h1>
<div class="body conbody">
<p class="p">ISDN is a synchronous network, meaning that all endpoints on the network need to synchronize on
the same clock signal. Typically, one endpoint acts as the clock MASTER, generating the clock
signal, and the other endpoints act as clock SLAVE, synchronizing on the clock signal received
from the MASTER.</p>
<p class="p">By default, a NT type endpoint acts as clock MASTER, and a TE type endpoint acts as clock
SLAVE. This default behaviour can be changed by using the web interface of the Mediatrix units.
The clock mode of the ISDN endpoints can be set to either clock MASTER or clock SLAVE.</p>
<div class="p">The following is a description of the endpoints behaviour with regards to clock signal
synchronization:<ul class="ul" id="concept_rkw_fvv_ts__ul_wjs_mzv_ts">
<li class="li">In transmission, all endpoints, regardless of their type, send a clock signal along with the
data they send.</li>
<li class="li">In reception, all endpoints, regardless of endpoint type, use the clock they receive from
the other end to synchronize the received data.</li>
<li class="li">In transmission, a clock SLAVE adjusts the clock it sends, based on the clock received from
the other end in reception.</li>
<li class="li">In transmission, a clock MASTER sends an absolute clock signal that does not depend on the
clock received from the other end.</li>
</ul></div>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title2" id="task_wyz_zcw_ts">
<h2 class="title topictitle2" id="ariaid-title2">Setting the Clock Mode</h2>
<div class="body taskbody">
<section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">ISDN</span>/<span class="keyword wintitle">Basic Rate Interface</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Select Endpoint</span>
dropdown menu, select the endpoint you want to configure.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Interface Configuration</span>
table, set the <span class="keyword wintitle">Clock Mode</span>.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
<br><img class="image" id="task_wyz_zcw_ts__image_dmr_x2w_ts" src="https://documentation.media5corp.com/download/attachments/62825785/InterfaceConfiguration_ClockMode.png" width="800"><br>
</section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title3" id="concept_ils_szv_ts">
<h1 class="title topictitle1" id="ariaid-title3">ISDN Clock Reference</h1>
<div class="body conbody">
<p class="p">On Mediatrix units with multiple ISDN endpoints, it is possible to select which endpoint should
be used as the clock reference. When an endpoint is designated as clock reference, the other
endpoints on the Mediatrix unit use this endpoint s clock as a synchronization source for
generating their own clock.</p>
<p class="p">In the following example, the clock signal generated by the ISDN PBX is received on the
Mediatrix C740 #1 s TE Slave endpoint and taken as a reference for this unit. Therefore the clock
signal generated by this unit s NT Master endpoint is synchronized on this signal. The Mediatrix
C740 #2 s TE Slave endpoint receives this signal and uses it as a reference for this unit,
meaning that the clock signal generated by this unit s NT Master endpoint towards the ISDN phone
is synchronized on this signal, therefore on the PBX s signal.</p>
<br><img class="image" id="concept_ils_szv_ts__image_uxv_yzv_ts" src="https://documentation.media5corp.com/download/attachments/62825785/ISDNClockReference.png" width="800"><br>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title4" id="task_g3n_jhb_ww">
<h2 class="title topictitle2" id="ariaid-title4">Selecting the Source of the Clock Reference</h2>
<div class="body taskbody">
<section id="task_g3n_jhb_ww__steps_aqq_qhb_ww"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_g3n_jhb_ww__steps_aqq_qhb_ww"><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">From the <span class="keyword wintitle">Clock Reference
Configuration</span>
table, select from the <span class="keyword wintitle">Suggestion</span> list, several
clock reference sources.</span>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The selected <span class="keyword wintitle">Clock Reference</span> sources for each available telephony card, according to the unit type, are displayed
in the <span class="keyword wintitle">Value</span> field of the
<span class="keyword wintitle">Clock Reference Configuration</span> table. The first selected source
will be used as a the clock reference. The following one will be used as the fallback
source, in the listed order, if the first one becomes unavailable. Only one source is
used at a time for the <span class="keyword wintitle">Clock Reference</span>.<br><img class="image" id="task_g3n_jhb_ww__image_jml_jbz_zw" src="https://documentation.media5corp.com/download/attachments/62825785/ClockReferenceConfiguration_2.png" width="800"><br></section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title5" id="concept_o2w_l2b_5s">
<h1 class="title topictitle1" id="ariaid-title5">Current Clock Reference</h1>
<div class="body conbody">
<div class="p">The Mediatrix unit selects the interface that is effectively used as clock reference in the
following way:<ul class="ul" id="concept_o2w_l2b_5s__ul_kvs_p2b_5s">
<li class="li">Only a clock SLAVE interface can be used as clock reference.</li>
<li class="li">If there is a configured preferred clock reference interface, this interface becomes the
clock reference as soon as it is UP (and running in SLAVE mode).</li>
<li class="li">If the preferred clock reference interface is DOWN or if there is no configured preferred
clock reference interface, the first clock SLAVE interface to become UP becomes the clock
reference.</li>
<li class="li">If no clock SLAVE interface is UP, there is no clock reference and the unit uses its own
internally-generated clock signal.</li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title6" id="reference_sm4_fbw_ts">
<h1 class="title topictitle1" id="ariaid-title6">Mediatrix Unit Clock Synchronization</h1>
<div class="body refbody">
<section class="section">
<p class="p">An ISDN network will be reliable when all endpoint clocks are synchronized correctly. When
endpoints are not synchronized, they each run on their own internally-generated clock
signals (free-running). The following are acceptable clock signal deviations from the
reference specified clock frequency in ppm (parts-per-million).</p>
</section>
<section class="section">
<table class="table" id="reference_sm4_fbw_ts__table_bpc_mbw_ts"><caption></caption><colgroup><col><col><col></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry">Recommendation</td>
<td class="entry">Interface</td>
<td class="entry">Acceptable deviation</td>
</tr>
<tr class="row">
<td class="entry">ITU-T I.430</td>
<td class="entry">Basic Rate (BRI)</td>
<td class="entry"> 100 ppm</td>
</tr>
<tr class="row">
<td class="entry">ITU-T I.431</td>
<td class="entry">Primary Rate (PRI)</td>
<td class="entry"> 50 ppm</td>
</tr>
</tbody></table>
</section>
<section class="section">
<p class="p">Mediatrix units are tested and certified against these specifications, and are guaranteed
to follow the specified clock signal accuracy.</p>
<p class="p"> When endpoints are not synchronized, the clock signals are obviously not running at the
exact same frequency, because of normal hardware deviations. The clock signals therefore
gradually drift away from each other and a periodical frame slip happens</p>
</section>
<section class="section">
<div class="p">With respect to the specified accepted deviations, the worst case frame slip rates are
calculated as follows:<table class="table" id="reference_sm4_fbw_ts__table_e3v_nbw_ts"><caption></caption><colgroup><col><col><col><col></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry">Interface</td>
<td class="entry">Acceptable deviation</td>
<td class="entry">Worst case difference between endpoints</td>
<td class="entry">Frame slip rate</td>
</tr>
<tr class="row">
<td class="entry">Basic Rate (BRI)</td>
<td class="entry">
<p class="p"> 100 ppm</p>
<p class="p">for each endpoint on a link</p>
</td>
<td class="entry">200 ppm</td>
<td class="entry">2E-4 (one slip every 5000 frames)</td>
</tr>
<tr class="row">
<td class="entry">Primary Rate (PRI)</td>
<td class="entry">
<p class="p"> 50 ppm</p>
<p class="p">for each endpoint on a link</p>
</td>
<td class="entry">100 ppm</td>
<td class="entry">1E-4 (one slip every 10000 frames)</td>
</tr>
</tbody></table></div>
</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title7" id="reference_kfq_wbw_ts">
<h1 class="title topictitle1" id="ariaid-title7">Direct ISDN Connection Between Endpoints</h1>
<div class="body refbody">
<section class="section">
<p class="p">It is important to configure each endpoint appropriately so the clock signal is
synchronized correctly with the rest of the network. The following table shows the different
endpoint clock mode combinations and the associated behaviour.</p>
<table class="table frame-all" id="reference_kfq_wbw_ts__table_oyk_1cw_ts"><caption></caption><colgroup><col><col><col></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__1">Endpoint 1 \ Endpoint 2</th>
<th class="entry colsep-1 rowsep-1" id="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__2">Master</th>
<th class="entry colsep-1 rowsep-1" id="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__3">Slave</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__1">Master</td>
<td class="entry colsep-1 rowsep-1" headers="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__2">
<ul class="ul" id="reference_kfq_wbw_ts__ul_bhr_bcw_ts">
<li class="li">Endpoints are not synchronized.</li>
<li class="li">Connection experiences frame slips and potentially loses data.</li>
</ul>
</td>
<td class="entry colsep-1 rowsep-1" headers="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__3">
<ul class="ul" id="reference_kfq_wbw_ts__ul_egp_hcw_ts">
<li class="li">Endpoints are synchronized.</li>
</ul>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__1">Slave</td>
<td class="entry colsep-1 rowsep-1" headers="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__2">
<ul class="ul" id="reference_kfq_wbw_ts__ul_zgp_3cw_ts">
<li class="li">Endpoints are synchronised.</li>
</ul>
</td>
<td class="entry colsep-1 rowsep-1" headers="reference_kfq_wbw_ts__table_oyk_1cw_ts__entry__3">
<ul class="ul" id="reference_kfq_wbw_ts__ul_pzx_jcw_ts">
<li class="li">Connection MAY be established but is unreliable due to synchronization
loop.</li>
</ul>
</td>
</tr>
</tbody></table>
</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title8" id="concept_b5r_bfw_ts">
<h1 class="title topictitle1" id="ariaid-title8">IP Connection Between ISDN Networks</h1>
<div class="body conbody">
<p class="p">When using Mediatrix units to connect different ISDN networks through IP, each ISDN network
runs on its own clock because there is no way to share the clock signal between the networks.
Therefore, VoIP calls between different ISDN networks always experience periodical frame slips,
which result in periodical packet losses, or measured bit error rates.</p>
<br><img class="image" id="concept_b5r_bfw_ts__image_gt5_lfw_ts" src="https://documentation.media5corp.com/download/attachments/62825785/IPConnectionBetweenISDNNetworks.png" width="800"><br>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title9" id="reference_j4g_nbv_gfb">
<h1 class="title topictitle1" id="ariaid-title9">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-title10" id="concept_v4k_q3h_1r">
<h1 class="title topictitle1" id="ariaid-title10">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-title11" id="concept_fqm_rv4_k4">
<h1 class="title topictitle1" id="ariaid-title11">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> |
