<!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="topic"><meta name="prodname" content="Sentinel 100 and Sentinel 400"><meta name="version" content="DGW 49.12.28842941"><meta name="platform" content="sbc"><meta name="platform" content=""><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="yes"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="topic_title_Basic_Concepts_d1e17"><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/45481987/commonltr.css"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/45481987/custom.css"><title>Configuring the Sentinel for a LAN or Edge Scenario</title></head><body class="nobody"><header role="banner"><div class="topicmeta title">Configuring the Sentinel for a LAN or Edge Scenario</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">Sentinel 100 and Sentinel 400 </div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/45481987/Configuring%20the%20Sentinel%20for%20a%20LAN%20or%20Edge%20Scenario.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#topic_title_Basic_Concepts_d1e17">Basic Concepts</a><ul><li><a href="#concept_grp_ysc_qkb">Sentinel 100 and Sentinel 400</a></li><li><a href="#concept_qt5_3xc_qkb">Sentinel on the LAN</a></li><li><a href="#concept_s22_twc_qkb">Sentinel on the Edge</a></li><li><a href="#concept_xqq_sgx_kr">Signaling and Media Interfaces</a></li><li><a href="#concept_dt4_p3s_jq">Default Network Interfaces</a></li><li><a href="#concept_mb2_vfp_bq">Call Agents</a></li></ul></li><li><a href="#topic_title_Basic_Tasks_d1e24">Basic Tasks</a><ul><li><a href="#task_b5b_srr_2q">Configuring the Network Interfaces</a></li><li><a href="#topic_title_Network_Interface_Binding_for_LAN_Scenarios_d1e26">Network Interface Binding for LAN Scenarios</a><ul><li><a href="#task_pqt_ncq_zkb">Configuring Signaling and Media Interfaces for LAN Scenarios</a></li><li><a href="#task_hnl_dbm_hq">Configuring the lan_ip_pbx_ca Call Agent for LAN Scenarios</a></li></ul></li><li><a href="#topic_title_Network_Interface_Binding_for_Edge_Scenarios_d1e29">Network Interface Binding for Edge Scenarios</a><ul><li><a href="#unique_570188944139378067">Configuring Signaling and Media Interfaces for Edge Scenarios</a></li><li><a href="#unique_4177548961876517868">Configuring the lan_ip_pbx_ca Call Agent for Edge Scenarios</a></li></ul></li></ul></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="topic_title_Basic_Concepts_d1e17">
<h1 class="title topictitle1" id="ariaid-title1">Basic Concepts</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title2" id="concept_grp_ysc_qkb">
<h2 class="title topictitle2" id="ariaid-title2">Sentinel 100 and Sentinel 400</h2>
<div class="body conbody"><p class="shortdesc">This technical bulletin explains how the physical and logical network ports can be
configured to suit different needs whether the Sentinel needs to be in the Lan or on the Edge of
the network. </p>
<p class="p"><img class="image" id="concept_grp_ysc_qkb__image_pzk_hbd_qkb" height="114" src="https://documentation.media5corp.com/download/attachments/45481987/clip_image002_-1363399475.jpg" width="348"></p>
<p class="p">The Sentinel 100 or 400 includes: </p>
<ul class="ul" id="concept_grp_ysc_qkb__ul_qzk_hbd_qkb">
<li class="li">1x Gigabit Ethernet WAN</li>
<li class="li">4x Gigabit Ethernet LAN switch</li>
<li class="li">VLAN, PPPoE, 802.1X</li>
<li class="li">Multiple IP (different subnets) support per network interface</li>
<li class="li">Multiple VLANs per network interface</li>
<li class="li">Static IP Routing</li>
<li class="li">Stateful local and network Firewall</li>
<li class="li">NAT</li>
</ul>
<p class="p">For more details visit the Media5 Corporation official Web site.at <a class="xref" href="https://www.media5corp.com" target="_blank">https://www.media5corp.com</a> or the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title3" id="concept_qt5_3xc_qkb">
<h2 class="title topictitle2" id="ariaid-title3">Sentinel on the LAN</h2>
<div class="body conbody"><p class="shortdesc">The Sentinel 100 or 400 is designed to fit different network roles and topologies. It
can be deployed inside a LAN behind a NAT firewall. </p>
<div class="p">
<br><img class="image" id="concept_qt5_3xc_qkb__image_wln_qxc_qkb" src="https://documentation.media5corp.com/download/attachments/45481987/SentinelonontheLan.png" width="800"><br>
</div>
<p class="p">In this scenario, the Sentinel is usually configured as follows:</p>
<ul class="ul" id="concept_qt5_3xc_qkb__ul_c32_4xc_qkb">
<li class="li">Private (local) IP assigned to LAN port, Internal SIP clients (e.g. IP phones and IP PBX)
also on the same LAN network.</li>
<li class="li">The Uplink Network interface is associated with the Wan/Eth1 physical link.</li>
<li class="li">The Lan1 Network interface is associated with the LAN/Eth2-5 physical link.</li>
<li class="li">The LAN signaling and media interfaces are not used.</li>
<li class="li">A signaling and media interface (pbx_s and pbx_m) wil be created to avoid port conflicts when
configuring the Call agents. They will be assigned associated to the LAN/Eth2-5 network
interface</li>
<li class="li">Local firewall rules created to protect the SBC from outside attack (to complement the Edge
NAT firewall router, optional). For more details refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Configuring+Local+Firewalls" target="_blank">Configuring Local Firewalls</a> Configuration guide published
on the Media5 documentation portal at https://documentation.media5corp.com </li>
<li class="li">Port forwarding for SIP and RTP ports set up on the edge NAT firewall router</li>
<li class="li">SBC SIP near end NAT traversal is configured</li>
<li class="li">SBC rules to process VoIP calls</li>
</ul>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title4" id="concept_s22_twc_qkb">
<h2 class="title topictitle2" id="ariaid-title4">Sentinel on the Edge</h2>
<div class="body conbody"><p class="shortdesc">The Sentinel 100 or 400 is designed to fit different network roles and topologies. It
can be deployed on the network Edge, with a public IP address and firewall enabled.</p>
<div class="p">
<br><img class="image" id="concept_s22_twc_qkb__image_kcb_1xc_qkb" src="https://documentation.media5corp.com/download/attachments/45481987/SentinelonontheEdge.png" width="800"><br>
</div>
<p class="p">The Sentinel located on the Edge is usually configured as follows:</p>
<ul class="ul" id="concept_s22_twc_qkb__ul_cbw_gxc_qkb">
<li class="li">Public IP assigned to WAN/Eth1 port</li>
<li class="li">Uplink Network interface is associated with the WAN/Eth1</li>
<li class="li">Lan1 network interface is associated with the LAN/eth2-5</li>
<li class="li">Private (local) IP assigned to LAN port</li>
<li class="li">Local firewall rules created to protect the SBC from outside attack, for reference: <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Configuring+Local+Firewalls" target="_blank">https://documentation.media5corp.com/display/DGWLATEST/Configuring+Local+Firewalls</a>
</li>
<li class="li">NAT, IP forwarding and Network Firewall are enabled if Sentinel is used as a router (this
is optional, the Sentinel by default does not forward any IP packets between the WAN and
LAN) for local IP clients, for reference: <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Configuring+a+Mediatrix+unit+as+a+NAT-Firewall+between+the+LAN+and+the+Internet" target="_blank">https://documentation.media5corp.com/display/DGWLATEST/Configuring+a+Mediatrix+unit+as+a+NAT-Firewall+between+the+LAN+and+the+Internet</a>
, <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Configuring+the+Network+Firewall" target="_blank">https://documentation.media5corp.com/display/DGWLATEST/Configuring+the+Network+Firewall</a>
</li>
<li class="li">SBC rules to process VoIP calls</li>
</ul>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title5" id="concept_xqq_sgx_kr">
<h2 class="title topictitle2" id="ariaid-title5">Signaling and Media Interfaces</h2>
<div class="body conbody"><p class="shortdesc">The Signaling Interface is used for SIP signaling and the Media Interface is used for
media ( RTP, UDPTL ) processing. </p>
<p class="p">When configuring a Call Agent, you must select a Signaling Interface and a Media Interface.
These interfaces are used whenever SIP signaling or media packets are sent to or received by the
Call Agent.</p>
<p class="p">It is possible to create several Signaling and Media Interfaces on the same Network Interface
but for different purposes. For example, one set of Signaling and Media Interfaces for a WAN SIP
Trunk and another set of Signaling and Media Interfaces for remote user calls. This means, for
instance, that two Signaling Interfaces will be created on the same Network Interface, using the
same IP address, but with a port range that will differ according to their intended use and to
avoid conflicts. </p>
<p class="p">A Media or Signaling Interface can be used by more than one Call Agent, but a specific
Signaling or Media Interface can be created for a specific Call Agent. This provides the liberty
to define non conflicting range of contactable interfaces on any physical network interfaces of
the units for your network structure needs (such as Vlans, PPPoE interfaces, multiple Ethernet
ports or multiple addresses on a link).</p>
<div class="p">The following Signaling and Media Interfaces are supplied by default: <ul class="ul" id="concept_xqq_sgx_kr__ul_nyb_hg5_mr">
<li class="li"><span class="keyword wintitle">lan1_m</span></li>
<li class="li"><span class="keyword wintitle">lan1_s</span></li>
<li class="li"><span class="ph uicontrol">loop_m</span></li>
<li class="li"><span class="ph uicontrol">loop_s</span></li>
<li class="li"><span class="keyword wintitle">uplink_s</span></li>
<li class="li"><span class="keyword wintitle">uplink_m</span></li>
</ul>
</div>
<p class="p"><span class="ph uicontrol">loop_m</span> and <span class="ph uicontrol">loop_s</span> interfaces are used to communicate with
the internal services of the unit. For example, the loop interfaces can be used to communicate
with the SipEp service to access phone ports.</p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title6" id="concept_dt4_p3s_jq">
<h2 class="title topictitle2" id="ariaid-title6">Default Network Interfaces</h2>
<div class="body conbody"><p class="shortdesc">There are four Network Interfaces created by default on the Mediatrix unit: Uplink, Lan
1, UplinkV6, and Rescue.</p>
<div class="p">
<ul class="ul" id="concept_dt4_p3s_jq__ul_jz3_35g_mr">
<li class="li">The <span class="keyword wintitle">Uplink</span> network interface
defines the uplink information required by the Mediatrix unit to properly connect to the
WAN. (By default eth1 for all platforms, except for the 4102S which is WAN . By default,
this interface uses the <span class="keyword wintitle">IpDhcp (IPv4 DHCP)</span>
connection type. If you are using only one Network Interface, you must use <span class="keyword wintitle">Uplink</span>.</li>
<li class="li">The <span class="keyword wintitle">Lan1</span> network interface
defines the information required by the Mediatrix unit to properly connect to the LAN.(By
default eth2-5 for all platforms, except for the 4102 which is LAN) By default, the
<span class="keyword wintitle">Lan1</span> Network Interface uses
the <span class="keyword wintitle">IpStatic (IPv4 Static)</span> connection type.
The <span class="keyword wintitle">Lan1</span> network interface can
only be added on units with 2 network ports. </li>
<li class="li"> The <span class="keyword wintitle">Rescue</span> network interface,
is used to display the <span class="keyword wintitle">Rescue</span>
Management Interface when a partial reset of the unit is performed. By default, the
<span class="keyword wintitle">Rescue</span> network interface <ul class="ul" id="concept_dt4_p3s_jq__ul_xxc_g2q_mcb">
<li class="li">is disabled and automatically enabled when a partial reset is performed.</li>
<li class="li">uses the <span class="keyword wintitle">IpStatic (IPv4 Static)</span> or the
<span class="keyword wintitle">Ip6Static (IPv6 Static)</span> addresses.</li>
</ul>The <span class="keyword wintitle">Rescue</span> Network
Interface cannot be deleted. Refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Performing+a+Partial+Reset" target="_blank">Technical Bulletin - Performing a Partial Reset</a>
document published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
<li class="li">The <span class="keyword wintitle">UplinkV6 </span> network interface
defines the IPv6 uplink information required by the Mediatrix unit to properly connect to
the WAN. By default, this interface uses the <span class="keyword wintitle">IP6autoConf (IPv6 Auto-Conf)</span> configuration
mode.</li>
</ul>It is possible to create up to 48 Network Interfaces. </div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title7" id="concept_mb2_vfp_bq">
<h2 class="title topictitle2" id="ariaid-title7">Call Agents</h2>
<div class="body conbody"><p class="shortdesc">Call Agents represent logical end-points that connect the Mediatrix unit to
peers.</p>
<p class="p">For security reasons, the Mediatrix unit communicates by default only with well-known and
defined peers. When a request cannot be associated with a Call Agent, it is rejected. Each Call
Agent is tied to a specific peer, ensuring all inbound and outbound communications with that
peer. Routing rulesets are used to route SIP signaling between Call Agents, where inbound
requests from a Call Agent are sent to another (or the same) Call Agent that will send an
outbound request to it's related peer. Call Agents can be associated with one or several Rulesets
which can be applied to the inbound or the outbound requests.</p>
<p class="p">When there is an inbound request, to determine the Call Agent the inbound request will go
through, the Mediatrix unit uses the destination IP address to choose the Network interface. Then
the destination port of the inbound request will determine the Signaling or Media Interface used.
Finally, the source address and the source port, will allow the Mediatrix unit to direct the
request to the appropriate Call Agent. At this point any Rulesets associated with the Call Agent
will be applied in order of priority.</p>
<div class="p">
<br><div class="imagecenter"><img class="image imagecenter" id="concept_mb2_vfp_bq__image_hrs_b1t_2q" src="https://documentation.media5corp.com/download/attachments/45481987/inboundrequest.png" width="400"></div><br>
</div>
<p class="p">When a request is sent out, i.e. there is an outbound request, the Routing Rulesets will
determine which Call Agent will be used. Then the Call Agent Rulesets will be applied to the
outbound request, in reverse priority order. The outbound request will then be sent through the
Signaling and Media Interface associated with the Call Agent. If the public IP address is used,
then the SIP request will use this address as the source IP address. The outbound request will
then be sent to the peer address of the Call Agent or according to the routing Ruleset if the
peer is a Network. </p>
<div class="p">
<br><div class="imagecenter"><img class="image imagecenter" id="concept_mb2_vfp_bq__image_zq2_lpy_2q" src="https://documentation.media5corp.com/download/attachments/45481987/outboundrequest.png" width="400"></div><br>
</div>
<p class="p">In addition, a Call Agent tracks REGISTER requests or monitor the peer host using SIP options.
When these features are activated, the Call Agent registration state and monitoring state are
updated allowing a Routing Ruleset to select another Call Agent based on the state of a primary
Call Agent.</p>
<p class="p">Eight default types of Call Agents were created for Mediatrix unit. This should be enough to
cover all your needs. However, for advanced users, it is possible to create new Call Agents. </p>
<p class="p">Seven of the eight default Call Agents allow the Mediatrix unit to communicate with seven
different types of end-points.</p>
<div class="p">
<table class="table frame-all" id="concept_mb2_vfp_bq__table_nd5_d5x_sq"><caption></caption><colgroup><col style="width:50%"><col style="width:50%"></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1">Call Agent Name</th>
<th class="entry colsep-1 rowsep-1" id="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">SIP or Endpoint Peer</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">wan_ip_trunk_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">SIP server located on the WAN.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">trunk_lines_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">Public Switch Telephony Network (PSTN), through PRI, BRI or FXO ports.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">phone_lines_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">Telephones, through FXS ports.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">lan_ip_pbx_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">IP Private branch exchange (PBX) located on the LAN.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">local_users_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">Users via SIP telephony located on the LAN.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">remote_users_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">Users using SIP telephony located on the WAN.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">registration_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">Used to route the registrations issued by the Registration Agent.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__1"><span class="keyword wintitle">secondary_ip_trunk_ca</span></td>
<td class="entry colsep-1 rowsep-1" headers="concept_mb2_vfp_bq__table_nd5_d5x_sq__entry__2">SIP server if the <span class="keyword wintitle">wan_ip_trunk_ca</span> Call Agent is not available.</td>
</tr>
</tbody></table>
</div>
<p class="p"><img class="image" id="concept_mb2_vfp_bq__image_i2t_qdd_5r" src="https://documentation.media5corp.com/download/attachments/45481987/CallFlow.jpg" width="800"></p>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title8" id="topic_title_Basic_Tasks_d1e24">
<h1 class="title topictitle1" id="ariaid-title8">Basic Tasks</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title9" id="task_b5b_srr_2q">
<h2 class="title topictitle2" id="ariaid-title9">Configuring the Network Interfaces</h2>
<div class="body taskbody">
<section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>When configuring network interfaces, Media5 recommends to have a syslog client
properly configured and enabled in order to receive any message related to the network
interfaces behaviour. The interface used to access the syslog client must also be
properly enabled.</section>
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>In the Edge scenario both the <span class="keyword wintitle">Uplink</span> and <span class="keyword wintitle">Lan1</span> network interface will be
used.</section>
<section id="task_b5b_srr_2q__steps_hqr_vrr_2q"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_b5b_srr_2q__steps_hqr_vrr_2q"><li class="li step stepexpand">
<span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
<div class="itemgroup info">
<div class="note important note_important"><span class="note__title">IMPORTANT:</span> Use extreme care when configuring network interfaces,
especially when configuring the network interface used to contact the unit
for management. Be careful never to disable or delete the network interface
used to contact the unit. Also be careful to always set the unit’s
management interface to be an interface that you can contact.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Network Interface Configuration</span> table, make sure the <span class="keyword wintitle">Uplink</span> network interface is
configured as follows: </span>
<ol type="a" class="ol substeps" id="task_b5b_srr_2q__substeps_sdt_21q_zkb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Link</span>=
<span class="keyword wintitle">eth1</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Type</span>=
<span class="keyword wintitle">IpStatic (IPv4 Static)</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Static IP Address</span>= IP address and Network mask of Network Interface</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Activation</span>=<span class="keyword wintitle">Enable</span></span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Network Interface Configuration</span> table, make sure the <span class="keyword wintitle">Lan1</span> network interface is
configured as follows: </span>
<ol type="a" class="ol substeps" id="task_b5b_srr_2q__substeps_lym_n1q_zkb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Link</span>=
<span class="keyword wintitle">eth2-5</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Type</span>=
<span class="keyword wintitle">IpStatic (IPv4 Static)</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Static IP Address</span>= IP address and Network mask of Network Interface</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Static Default Router</span>=IP address of the default router of the network interface.</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Activation</span>=<span class="keyword wintitle">Enable</span></span>
</li>
</ol>
</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>
<br><img class="image" id="task_b5b_srr_2q__image_gkc_kzp_zkb" src="https://documentation.media5corp.com/download/attachments/45481987/EdgeNetworkInterfaces.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_pqt_ncq_zkb">Configuring Signaling and Media Interfaces for LAN Scenarios</a></li><li class="linklist"><a class="link" href="#unique_570188944139378067">Configuring Signaling and Media Interfaces for Edge Scenarios</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested1 nobody" aria-labelledby="ariaid-title10" id="topic_title_Network_Interface_Binding_for_LAN_Scenarios_d1e26">
<h2 class="title topictitle2" id="ariaid-title10">Network Interface Binding for LAN Scenarios</h2>
<article class="topic task nested2" aria-labelledby="ariaid-title11" id="task_pqt_ncq_zkb">
<h3 class="title topictitle3" id="ariaid-title11">Configuring Signaling and Media Interfaces for LAN Scenarios</h3>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>
<p class="p">For the LAN scenarios, the default uplink Signaling and Media interfaces are used as
well as a custom signaling and media interface that will bind to the LAN1 Network
interface.</p>
</section>
<section id="task_pqt_ncq_zkb__steps_k1t_hqg_blb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_pqt_ncq_zkb__steps_k1t_hqg_blb"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">SBC</span>/<span class="keyword wintitle">Configuration</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Signaling Interface Configuration</span>, click <img class="image" id="task_pqt_ncq_zkb__image_v5d_wsg_blb" src="https://documentation.media5corp.com/download/attachments/45481987/minus.jpg" width="15">
located on the same line as <span class="keyword wintitle">lan1_s</span> to delete it.</span>
</li><li class="li step">
<span class="ph cmd">On the <span class="keyword wintitle">uplink_s</span> line,
complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="task_pqt_ncq_zkb__substeps_atz_zsh_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=Uplink</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port</span> =
5064</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Secure Port</span>=0</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Allowed Transport</span>=All</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">TLS Mode</span>=Client</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=NAT/FW IP address</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">click <img class="image" id="task_pqt_ncq_zkb__image_nj3_kwg_blb" src="https://documentation.media5corp.com/download/attachments/45481987/Plusbleu.jpg" width="15"> at the bottom of the table to add a new signalling interface. Complete the
fields as follows: </span>
<ol type="a" class="ol substeps" id="task_pqt_ncq_zkb__substeps_onj_fth_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Name</span>=pbx_s</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=<span class="keyword wintitle">Lan1</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port</span>=5060</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Secure Port</span>=0</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Allowed Transport</span>=All</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">TLS Mode</span>=Client</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=leave empty</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Media Interface Configuration</span>
table, click <img class="image" id="task_pqt_ncq_zkb__image_crc_5wg_blb" src="https://documentation.media5corp.com/download/attachments/45481987/minus.jpg" width="15"> located on the same line as <span class="keyword wintitle">lan1_m</span> to delete it.</span>
</li><li class="li step">
<span class="ph cmd">On the <span class="keyword wintitle">uplink_m</span> line,
complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="task_pqt_ncq_zkb__substeps_phk_mth_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=<span class="keyword wintitle">Uplink</span>.</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port Range</span>=20000-20999</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=NAT/FW IP address</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">Click <img class="image" id="task_pqt_ncq_zkb__image_xjn_zwg_blb" src="https://documentation.media5corp.com/download/attachments/45481987/Plusbleu.jpg" width="15">
at the bottom of the table to add a new signalling interface. Complete the
fields as follows: </span>
<ol type="a" class="ol substeps" id="task_pqt_ncq_zkb__substeps_ogt_4th_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Name</span>=pbx_m</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=<span class="keyword wintitle">Lan1</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port Range</span>=21000-21999</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=leave empty</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span></span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
<br><img class="image" id="task_pqt_ncq_zkb__image_ljc_p2q_zkb" src="https://documentation.media5corp.com/download/attachments/45481987/signalingMediaInterfaceLAN.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_hnl_dbm_hq">Configuring the lan_ip_pbx_ca Call Agent for LAN Scenarios</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested2" aria-labelledby="ariaid-title12" id="task_hnl_dbm_hq">
<h3 class="title topictitle3" id="ariaid-title12">Configuring the <span class="keyword wintitle">lan_ip_pbx_ca</span>
Call Agent for LAN Scenarios</h3>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div><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></section>
<section id="task_hnl_dbm_hq__steps_a5v_ybx_gq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_hnl_dbm_hq__steps_a5v_ybx_gq"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">SBC</span>/<span class="keyword wintitle">Configuration</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Call Agent Configuration</span>
table, click <img class="image" id="task_hnl_dbm_hq__image_a5j_mwq_lq" src="https://documentation.media5corp.com/download/attachments/45481987/pencilbleu.jpg" width="15"> next to <span class="keyword wintitle">lan_ip_pbx_ca</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Configure Call Agent</span> table,
complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="task_hnl_dbm_hq__substeps_edk_pbv_dq">
<li class="li substep">
<span class="ph cmd">Select the <span class="keyword wintitle">Enable</span> check
box.</span>
</li>
<li class="li substep">
<span class="ph cmd">From the <span class="keyword wintitle">Signaling Interface</span>
selection list, select <span class="keyword wintitle">pbx_s</span>.</span>
</li>
<li class="li substep">
<span class="ph cmd">From the <span class="keyword wintitle">Media Interface</span>
selection list, select <span class="keyword wintitle">pbx_m</span> .</span>
</li>
<li class="li substep">
<span class="ph cmd">Set the <span class="keyword wintitle">Peer Host</span> to IP
address of the IP PBX.</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Save</span>.</span>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span> to apply
all changes to the configuration.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div><span class="keyword wintitle">No</span> will be displayed in
the <span class="keyword wintitle">Config.Modified</span> field,
indicating that the configuration that was modified is now applied to the system. When
the Mediatrix SBC will use the selected Call Agent for a communication, the selected
parameters will be applied.<br><img class="image" id="task_hnl_dbm_hq__image_ejh_2ry_1fb" src="https://documentation.media5corp.com/download/attachments/45481987/ConfigureCallAgent_lan_ip_pbx_ca_BacktoBAck_LAN.png" width="800"><br></section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested1 nobody" aria-labelledby="ariaid-title13" id="topic_title_Network_Interface_Binding_for_Edge_Scenarios_d1e29">
<h2 class="title topictitle2" id="ariaid-title13">Network Interface Binding for Edge Scenarios</h2>
<article class="topic task nested2" aria-labelledby="ariaid-title14" id="unique_570188944139378067">
<h3 class="title topictitle3" id="ariaid-title14">Configuring Signaling and Media Interfaces for Edge Scenarios</h3>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>
<p class="p">For the Edge scenarios, the default uplink and lan Signaling and Media interfaces are
used.</p>
</section>
<section id="unique_570188944139378067__steps_k1t_hqg_blb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_570188944139378067__steps_k1t_hqg_blb"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">SBC</span>/<span class="keyword wintitle">Configuration</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Signaling Interface Configuration</span>, on the <span class="keyword wintitle">uplink_s</span>
line, complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="unique_570188944139378067__substeps_y3b_vth_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=Uplink</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port</span>=5060</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Secure Port</span>=All</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Allowed Transport</span>=All</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">TLS Mode</span>=Client</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=leave empty</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">On the same line as <span class="keyword wintitle">lan1_s</span>, complete the fields
as follows: </span>
<ol type="a" class="ol substeps" id="unique_570188944139378067__substeps_mqp_dcw_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=<span class="keyword wintitle">Lan1</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port</span>=5060</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Secure Port</span>=0</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Allowed Transport</span>=All</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">TLS Mode</span>=Client</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=leave empty</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Media Interface Configuration</span>
table, on the <span class="keyword wintitle">uplink_m</span>
line, complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="unique_570188944139378067__substeps_wvr_kcw_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=Uplink</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port Range</span>=20000-20999</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=leave empty</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">On the <span class="keyword wintitle">lan1_m</span> line,
complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="unique_570188944139378067__substeps_rjn_p2w_blb">
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Name</span>=lan1_m</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Network</span>=<span class="keyword wintitle">Lan1</span></span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Port Range</span>=20000-20999</span>
</li>
<li class="li substep">
<span class="ph cmd"><span class="keyword wintitle">Public Address</span>=leave empty</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span></span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
<br><img class="image" id="unique_570188944139378067__image_n5m_2fq_zkb" src="https://documentation.media5corp.com/download/attachments/45481987/signalingMediaInterfaceEdge.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="#unique_4177548961876517868" title="This is an example on how to configure the lan_ip_pbx_ca Call Agent.">Configuring the lan_ip_pbx_ca Call Agent for Edge Scenarios</a></li></ul></div></nav></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested2" aria-labelledby="ariaid-title15" id="unique_4177548961876517868">
<h3 class="title topictitle3" id="ariaid-title15">Configuring the <span class="keyword wintitle">lan_ip_pbx_ca</span>
Call Agent for Edge Scenarios</h3>
<div class="body taskbody"><p class="shortdesc">This is an example on how to configure the <span class="keyword wintitle">lan_ip_pbx_ca</span> Call Agent.</p>
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div><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></section>
<section id="unique_4177548961876517868__steps_a5v_ybx_gq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_4177548961876517868__steps_a5v_ybx_gq"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">SBC</span>/<span class="keyword wintitle">Configuration</span>.</span>
</li><li class="li step">
<span class="ph cmd">Select the <span class="keyword wintitle">Enable</span>
check box located next to <span class="keyword wintitle">lan_ip_pbx_ca</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Call Agent Configuration</span>
table, click <img class="image" id="unique_4177548961876517868__image_a5j_mwq_lq" src="https://documentation.media5corp.com/download/attachments/45481987/pencilbleu.jpg" width="15"> next to <span class="keyword wintitle">lan_ip_pbx_ca</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Configure Call Agent</span> table,
complete the fields as follows: </span>
<ol type="a" class="ol substeps" id="unique_4177548961876517868__substeps_edk_pbv_dq">
<li class="li substep">
<span class="ph cmd">From the <span class="keyword wintitle">Signaling Interface</span>
selection list, select <span class="keyword wintitle">lan1_s</span>.</span>
</li>
<li class="li substep">
<span class="ph cmd">From the <span class="keyword wintitle">Media Interface</span>
selection list, select <span class="keyword wintitle">lan1_m</span>.</span>
</li>
<li class="li substep">
<span class="ph cmd">Set the <span class="keyword wintitle">Peer Host</span> to IP
address of the IP PBX.</span>
</li>
</ol>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Save</span>.</span>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span> to apply
all changes to the configuration.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div><span class="keyword wintitle">No</span> will be displayed in
the <span class="keyword wintitle">Config.Modified</span> field,
indicating that the configuration that was modified is now applied to the system. When
the Mediatrix SBC will use the selected Call Agent for a communication, the selected
parameters will be applied.<br><img class="image" id="unique_4177548961876517868__image_hhq_sfq_zkb" src="https://documentation.media5corp.com/download/attachments/45481987/ConfigureCallAgent_lan_ip_pbx_ca_DualTrunk_Edge.png" width="800"><br></section>
</div>
</article></article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title16" id="concept_v4k_q3h_1r">
<h1 class="title topictitle1" id="ariaid-title16">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-title17" id="concept_fqm_rv4_k4">
<h1 class="title topictitle1" id="ariaid-title17">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> |
