Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated @ 2023-08-09T11:10:19.712871
HTML
headtrue
encodingUTF-8
<!DOCTYPE html
  SYSTEM "about:legacy-compat">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2023"><meta name="DC.rights.owner" content="(C) Copyright 2023"><meta name="DC.type" content="topic"><meta name="prodname" content="For all Mediatrix units"><meta name="version" content="DGW 49.12.28842941"><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="topic_title_Basic_Concepts_d1e13"><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>SIP Registration</title></head><body class="nobody"><header role="banner"><div class="topicmeta title">SIP Registration</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">For all Mediatrix units</div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/62825785/SIP%20Registration.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_d1e13">Basic Concepts</a><ul><li><a href="#concept_gqz_k4x_zp">Registration </a></li><li><a href="#concept_rgs_1lk_kcb">Registering to all SIP Gateways vs to a specific SIP Gateway</a></li><li><a href="#concept_nfx_kfk_kcb">Number of Registrations</a><ul><li><a href="#reference_gg5_thk_kcb">Registration Number Example</a></li></ul></li></ul></li><li><a href="#reference_wkq_prz_d2b">SIP Registration Basic Tasks</a></li><li><a href="#topic_title_Adavanced_Parameters_d1e19">Adavanced Parameters</a><ul><li><a href="#reference_nyj_wqx_zp">Advanced SIP Registration Parameters</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="topic_title_Basic_Concepts_d1e13">
   <h1 class="title topictitle1" id="ariaid-title1">Basic Concepts</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title2" id="concept_gqz_k4x_zp">
 <h2 class="title topictitle2" id="ariaid-title2">Registration </h2>
 
 <div class="body conbody"><p class="shortdesc">The DGW firmware handles multiple registration modes, either per endpoint, per gateway,
  or for the whole unit. Simultaneous registrations are supported for each endpoint or to multiple
  SIP gateways (a maximum of 5 is supported).</p>
  <p class="p">Each endpoint may have its own registration information. You can set information for each
   endpoint such as its telephone number and friendly name. </p>
  <p class="p">Unit registration is used to register a contact not directly related to endpoints. This is
   generally used to indicate to a registrar the IP location of the Mediatrix unit when it is used
   as a gateway. In SIP, a registration is valid for a period of time defined by the registrar. Once
   a unit is registered, the SIP protocol requires the User Agent to refresh this registration
   before the registration expires. Typically, this re-registration must be completed before the
   ongoing registration expires, so that the User Agent's registration state does not change (i.e.,
   remains 'registered'). </p>
  <div class="p">
   <br><img class="image" id="concept_gqz_k4x_zp__image_c5c_rxk_kcb" src="https://documentation.media5corp.com/download/attachments/62825785/BasicSipEndpoinRegistration.png" width="800"><br>
  </div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title3" id="concept_rgs_1lk_kcb">
 <h2 class="title topictitle2" id="ariaid-title3">Registering to all SIP Gateways vs to a specific SIP Gateway</h2>
 
 <div class="body conbody"><p class="shortdesc">Each endpoint can register to a specific SIP Gateway or register to all configured SIP
  Gateways simultaneously. DGW handles each registration separately, allowing the registration of
  individual endpoints to different SIP Gateways. </p>
  <p class="p">You can define a specific gateway to register to each endpoint of the Mediatrix unit. For
   instance, you could set all endpoints of the Mediatrix unit to register to all SIP Gateways
   simultaneously and set a specific endpoint to register to just one of the SIP Gateways. Using one
   or more specific parameter usually requires to enable an override parameter and set the specific
   configuration to apply. Refer to <a class="xref" href="#reference_nyj_wqx_zp">Advanced SIP Registration Parameters</a> section.</p>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title4" id="concept_nfx_kfk_kcb">
 <h2 class="title topictitle2" id="ariaid-title4">Number of Registrations</h2>
 
 <div class="body conbody"><p class="shortdesc">The total number of registrations is the sum of all the endpoint and gateway pairs. </p>
  <p class="p">For most Mediatrix devices, the total number of registrations is limited to 64. However, for
   the Mediatrix G7 Series, the Mediatrix S7 Series, the Sentinel 400, and the Sentinel 100, the
   limit is 500. If a custom DGW profile is used, the limit can be different depending on what value
   was defined in the profile. For example, when using a Sentinel 400, up to 500 registrations are
   possible, but if the profile specifies 200, then the unit will only be able to manage up to 200
   registrations.</p>
  <p class="p">The Mediatrix unit supports a maximum of 10 gateways. An endpoint configured with <span class="keyword wintitle">All</span> gateways generates as many registrations as
   the number of gateways. In a setup with 3 gateways, one endpoint configured with <span class="keyword wintitle">All</span> as the gateway name counts for 3 in the
   total number of registrations. The registrations are enabled gateway by gateway until the limit
   is reached. Endpoint registrations are used first, then unit registrations. The remaining
   registrations are not registered and do not appear in the <span class="keyword wintitle">Status</span> table. If the number of registrations
   exceeds the defined limit, a warning is displayed on the Web interface (as well as in the CLI and
   SNMP interfaces) and a syslog notify (Level Error) is sent. Adding a gateway or an endpoint
   triggers a warning message if the total number of registrations configured reached the defined
   limit</p>
 </div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested2" aria-labelledby="ariaid-title5" id="reference_gg5_thk_kcb">
  <h3 class="title topictitle3" id="ariaid-title5">Registration Number Example</h3>
  
  <div class="body refbody"><p class="shortdesc">In this example, three gateways (Default, gw1, and gw2) are used with the Mediatrix
    unit, as displayed in the <span class="keyword wintitle">Gateway Configuration</span> table. </p>
    <section class="section">
      <p class="p">The default ports (0 = 5060 for plain SIP and 0 = 5061 for secure SIP) can be used for two
        gateways, as long as they are attached to different signaling networks (in the <span class="keyword wintitle">Gateway Configuration</span> table, default/Uplink
        and gw1/Lan1 use the same ports 0 and 0). If you wish to define another gateway for the same
        signaling network, a different port should be used than the default ones (<span class="keyword wintitle">Gateway Configuration</span> table, gw2 is
        attached to the Uplink signaling network, as is the default gateway. For this scope, gw2 is
        only functional if it uses different ports than the default gateway). When a <span class="keyword wintitle">Gateway Name</span> for a <span class="keyword wintitle">User Name</span> is set to <span class="keyword wintitle">All</span>, this means that 3 registrations are
        used.</p>
      <br><img class="image" id="reference_gg5_thk_kcb__image_u4g_f3k_kcb" src="https://documentation.media5corp.com/download/attachments/62825785/GatewayConfigurationforRegistrationExample.png" width="700"><br>
    </section>
    <section class="section">
      <br><img class="image" id="reference_gg5_thk_kcb__image_z3m_g3k_kcb" src="https://documentation.media5corp.com/download/attachments/62825785/UnitandEndpointRegistationExample.png" width="700"><br>
      <table class="table frame-all" id="reference_gg5_thk_kcb__table_gdp_hjk_kcb"><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_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">User Name</th>
              <th class="entry colsep-1 rowsep-1" id="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">Gateway Name</th>
              <th class="entry colsep-1 rowsep-1" id="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">Number of Registrations</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">ur1</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">All</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">3</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">ur2</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">gw2</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">1</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">te1</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">all</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">3</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">te2</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">all</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">3</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">te3</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">gw1</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">1</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1">te4</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2">default</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">1</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__1 reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__2" colspan="2">TOTAL NUMBER OF REGISTRATIONS</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_gg5_thk_kcb__table_gdp_hjk_kcb__entry__3">12</td>
            </tr>
          </tbody></table>
    </section>
  </div>
</article></article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title6" id="reference_wkq_prz_d2b">
  <h1 class="title topictitle1" id="ariaid-title6">SIP Registration Basic Tasks</h1>
  
  <div class="body refbody"><p class="shortdesc">The following technical bulletins describe the basic tasks related to registration.
    Keep in mind that these documents are for units configured with the default values of the
    parameters.</p>
    <section class="section"> The following documents are published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>:<ul class="ul" id="reference_wkq_prz_d2b__ul_ngg_pxz_d2b">
        <li class="li"><a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Basic+SIP+Endpoint+Registration" target="_blank">Technical Bulletin - Basic SIP Endpoint
            Registration</a></li>
        <li class="li"><a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Basic+SIP+Gateway+Registration" target="_blank">Technical Bulletin - Basic SIP Gateway
            Registration</a></li>
        <li class="li"><a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Basic+SIP+Unit+Registration" target="_blank">Technical Bulletin - Basic SIP Unit
          Registration</a></li>
        <li class="li"><a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Basic+SIP+Username+Registration" target="_blank">Technical Bulletin - Basic SIP Username
            Registration</a></li>
      </ul></section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title7" id="topic_title_Adavanced_Parameters_d1e19">
   <h1 class="title topictitle1" id="ariaid-title7">Adavanced Parameters</h1>
<article class="topic reference nested1" aria-labelledby="ariaid-title8" id="reference_nyj_wqx_zp">
    <h2 class="title topictitle2" id="ariaid-title8">Advanced SIP Registration Parameters</h2>
    <div class="body refbody">
                <section class="section">Although the services can be configured in great part in the DGW Web
                        browser, some aspects of the configuration can only be completed with the
                        MIB parameters by :<ul class="ul" id="reference_nyj_wqx_zp__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></section>
        <section class="section">For more details on these advanced parameters, 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>
                <section class="section"><h3 class="title sectiontitle">Non specific registration parameters</h3>
                        
                        <ul class="ul" id="reference_nyj_wqx_zp__ul_s4g_tvk_kcb">
                                <li class="li">Registration Delay Value:
                                                <span class="keyword parmname">SipEp.InteropRegistrationDelayValue</span></li>
                                <li class="li">Behaviour on Initial-Registration Reception:
                                                <span class="keyword parmname">SipEp.BehaviorOnInitialRegistrationReception</span></li>
                                <li class="li">Unregistered Unit Behavior:
                                                <span class="keyword parmname">SipEp.DefaultUnitRegistrationUnregisteredBehavior</span></li>
                                <li class="li">Default Registration Retry Time Value:
                                                <span class="keyword parmname">SipEp.DefaultRegistrationRetryTime</span></li>
                                <li class="li">Default Unregistered Endpoint Behaviour:
                                                <span class="keyword parmname">SipEp.DefaultRegistrationUnregisteredBehavior</span></li>
                        </ul>
                </section>
                <section class="section"><h3 class="title sectiontitle">User Agent registration parameters </h3>
                        
                        <ul class="ul" id="reference_nyj_wqx_zp__ul_jhq_2vk_kcb">
                                <li class="li">Preferred Language:
                                                <span class="keyword parmname">SipEp.UserAgent.AcceptLanguage</span>
                                </li>
                                <li class="li">Contact Domain:
                                                <span class="keyword parmname">SipEp.UserAgent.ContactDomain</span></li>
                                <li class="li">SIP User Agent Header:
                                                <span class="keyword parmname">SipEp.InteropSendUaHeaderEnable</span></li>
                        </ul>
                </section>
                <section class="section"><h3 class="title sectiontitle">Endpoint specific registration parameters </h3>
                        
                        <ul class="ul" id="reference_nyj_wqx_zp__ul_bmj_24k_kcb">
                                <li class="li">Specific Unregistered Endpoint Behaviour:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistration.UnregisteredBehavior</span></li>
                        </ul>
                </section>
                <section class="section"><h3 class="title sectiontitle">Gateway specific registration parameters </h3>
                        
                        <ul class="ul" id="reference_nyj_wqx_zp__ul_bf4_l4k_kcb">
                                <li class="li">Specific Unregistered Endpoint Behaviour:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistration.UnregisteredBehavior</span></li>
                                <li class="li">Gateway Specific Registration Retry Time:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistrationRetryTime</span></li>
                                <li class="li">Expiration Value in Registration:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistration.ExpirationValue</span></li>
                                <li class="li">Registration Refresh:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistrationRefreshTime</span></li>
                                <li class="li">Registration Expiration:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistration.ProposedExpirationValue</span></li>
                                <li class="li">Enable Configuration:
                                                <span class="keyword parmname">SipEp.GwSpecificRegistration.EnableConfig</span></li>
                        </ul>
                </section>
    </div>
</article></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>