Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated @ 2023-08-09T12:26:47.628334
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="All Mediatrix Units"><meta name="version" content="DGW 49.12.28842941"><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="no"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="topic_title_Basic_Concepts_d1e14"><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 Misc Parameter Configuration</title></head><body class="nobody"><header role="banner"><div class="topicmeta title">SIP Misc Parameter Configuration</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">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%20Misc%20Parameter%20Configuration.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_d1e14">Basic Concepts</a><ul><li><a href="#concept_f2f_gsn_5fb">SIP Penalty Box</a><ul><li><a href="#concept_kfq_qsn_5fb">SIP Penalty Box vs Transport Types</a></li></ul></li><li><a href="#reference_zpb_dvn_5fb">Default Conversion of Standard SIP Error Codes To ISDN Q.850 Cause Codes</a></li><li><a href="#reference_njy_zvn_5fb">Default Conversion of Standard Q.850 ISDN Cause Codes to SIP Error Codes</a></li><li><a href="#concept_glr_y4t_5fb">PRACK</a></li><li><a href="#concept_ndb_b5t_5fb">Session Timer Extension</a><ul><li><a href="#concept_mpd_k5t_5fb">SDP in Session Timer reINVITEs or UPDATEs</a></li><li><a href="#concept_phf_r5t_5fb">Relation Between Minimum and Maximum Values </a></li><li><a href="#concept_nmf_x5t_5fb">Session Refresh</a></li></ul></li><li><a href="#concept_kzy_3d5_5fb">Event Handling</a></li></ul></li><li><a href="#topic_title_Basic_Tasks_d1e25">Basic Tasks</a><ul><li><a href="#task_xgs_stn_5fb">Configuring the SIP Penalty Box</a></li><li><a href="#task_vpc_rzn_5fb">Overriding the Default Mapping for SIP Error Code to ISDN Cause </a></li><li><a href="#unique_1042068691910885398">Overriding the Default Mapping for ISDN Cause to SIP Error Codes </a></li><li><a href="#task_gr1_nmt_5fb">Choosing to Use Additional Headers</a></li><li><a href="#task_nkr_q4t_5fb">Defining the Type of PRACK Support</a></li><li><a href="#task_mjp_rqt_5fb">Setting the Session Refresh Information</a></li><li><a href="#task_bhy_fvt_5fb">Overriding the SIP Domain Used</a></li><li><a href="#task_msh_cyt_5fb">Setting the Blind Transfer Method</a></li><li><a href="#task_czv_d15_5fb">Configuring Call Diversion</a></li><li><a href="#task_hhd_y15_5fb">Configuring Supported DNS Queries</a></li><li><a href="#task_chp_nd5_5fb">Configuring Event Handling</a></li><li><a href="#task_htc_m25_5fb">Enabling Messaging Subscription</a></li><li><a href="#task_h13_ff5_5fb">Configuring Advice of Charge (AOC)</a></li><li><a href="#task_amf_xf5_5fb">Enabling the Media Security Agreement Parameter</a></li></ul></li><li><a href="#reference_h3d_yvp_mcb">Advanced Misc SIP Parameters</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="topic_title_Basic_Concepts_d1e14">
   <h1 class="title topictitle1" id="ariaid-title1">Basic Concepts</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title2" id="concept_f2f_gsn_5fb">
 <h2 class="title topictitle2" id="ariaid-title2">SIP Penalty Box</h2>
 
 <div class="body conbody"><p class="shortdesc">The penalty box feature is useful when a given host FQDN resolves to a non-responding
  address. When the address times out, it is put into the penalty box for a given amount of time.
  During that time, this address is considered as “non-responding” for all requests</p>
  <p class="p">This feature is useful when DNS requests return multiple or varying addresses for a host FQDN.
   It makes sure that, when a host is down, no SIP request is sent to it for a minimal amount of
   time. When enabled, this feature takes effect immediately on the next call attempt. </p>
  <div class="p">The penalty box feature is applied only when using UDP or TCP connections established with a
   FQDN. A similar penalty box feature for the TLS persistent connections is available via the
    <span class="keyword parmname">TLS Persistent Retry Interval</span> parameter.<div class="note note note_note"><span class="note__title">Note:</span> The Penalty Box feature works
    only with Trunk Gateways, i.e. it is disabled when an Endpoint Gateway type is
    configured.</div></div>
 </div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title3" id="concept_kfq_qsn_5fb">
 <h3 class="title topictitle3" id="ariaid-title3">SIP Penalty Box vs Transport Types</h3>
 
 <div class="body conbody"><p class="shortdesc">Media5 recommends to use this feature with care when supporting multiple transports  or
  you may experience unwanted behaviours. When the Mediatrix unit must send a packet, it retrieves
  the destination from the packet. If the destination address does not specify a transport to use
  and does not have a DNS SRV entry that configures which transport to use, then the Mediatrix unit
  tries all transports it supports, starting with UDP. If this fails, it tries with TCP. The unit
  begins with UDP because all SIP implementations must support this transport, while the mandatory
  support of TCP was only introduced in RFC 3261.</p>
  <div class="note note note_note"><span class="note__title">Note:</span> It is not the destination itself that is placed in the penalty box, but rather targets,
   which are a combination of address, port, and transport. Targets put in penalty box are not used
   unless all the targets are in the penalty box. In that case, the highest priority target is used. </div>
  <p class="p">Let’s say for instance that the Mediatrix unit supports both the UDP and TCP transports. It
   tries to reach endpoint “B” for which the destination address does not specify a transport and
   there is no DNS SRV entry to specify which transports to use in which order. It turns out that
   this endpoint “B” is also down. In this case, the Mediatrix unit first tries to contact endpoint
   “B” via UDP. After a timeout period, the UDP target is placed in the penalty box and the unit
   then tries to contact endpoint “B” via TCP. This fails as well and the TCP target is also placed
   in the penalty box.</p>
  <p class="p">Now, let’s assume endpoint “B” comes back to life and the Mediatrix unit tries again to contact
   it before UDP and TCP targets are released from the penalty box. First, the unit tries UDP, but
   it is currently in the penalty box and there is another transport left to try. The Mediatrix unit
   skips over UDP and tries the next target, which is TCP. Again, TCP is still in the penalty box,
   but this time, it is the last target the Mediatrix unit can try, so penalty box or not, TCP is
   used all the same to try to contact endpoint “B”.</p>
  <p class="p">There is a problem if endpoint “B” only supports UDP (RFC 2543-based implementation). Endpoint
   “B” is up, but the Mediatrix unit still cannot contact it: with UDP and TCP in the penalty box,
   the unit only tries to contact endpoint “B” via its last choice, which is TCP.</p>
  <p class="p">The same scenario would not have any problem if the penalty box feature was disabled. Another
   option is to disable TCP in the Mediatrix unit, which makes UDP the only possible choice for the
   unit and forces to use UDP even if it is in the penalty box.</p>
  <p class="p">You must fully understand the above problem before configuring this feature. Mixing endpoints
   that do not support the same set of transports with this feature enabled can lead to the above
   problems, so it is suggested to either properly configure SRV records for the hosts that can be
   reached or be sure that all hosts on the network support the same transport set before enabling
   this feature.</p>
 </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title4" id="reference_zpb_dvn_5fb">
  <h2 class="title topictitle2" id="ariaid-title4">Default Conversion of Standard SIP Error Codes To ISDN Q.850 Cause Codes</h2>
  <div class="body refbody">
    <section class="section">Mediatrix devices internally use Q.850 ISDN cause codes as the common representation
      for call errors and call terminations. Mediatrix devices are gateways used between SIP and
      conventional (i.e. non-SIP) telephony technologies; therefore converting SIP error codes to
      Q.850 ISDN cause codes is required in both directions i.e. from SIP to ISDN and ISDN to SIP. </section>
    <section class="section">The following table presents the conversion of SIP Error Codes to Q.850 ISDN Cause
      Codes. It is possible to override these default conversions and to configure the conversions
      of any other SIP error code between 400 and 699. (Refer to the Basic tasks)</section>
    <table class="table frame-all" id="reference_zpb_dvn_5fb__table_axr_fvn_5fb"><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="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">SIP Error Codes</th>
            <th class="entry colsep-1 rowsep-1" id="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">Q.850 ISDN Cause Codes</th>
          </tr>
        </thead><tbody class="tbody">
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">400: Bad Request</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">41 Temporary Failure</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">401: Unauthorized</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">21 Call rejected</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">402: Payment required</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">21 Call rejected</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">403: Forbidden</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">21 Call rejected</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">404: Not found</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">1 Unallocated number</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">405: Method not allowed</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">63 Service or option unavailable</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">406: Not acceptable</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">79 Service/option not implemented</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">407: Proxy authentication required</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">21 Call rejected</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">408: Request timeout</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">102 Recovery on timer expiry</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">410: Gone</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">22 Number changed (w/o diagnostic)</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">413: Request Entity too long</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">414: Request-URI too long</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">415: Unsupported media type</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">79 Service/option not implemented</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">416: Unsupported URI Scheme</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">420: Bad extension</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">421: Extension Required</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">423: Interval Too Brief</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">480: Temporarily unavailable</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">18 No user responding</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">481: Call/Transaction Does not Exist</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">41 Temporary Failure</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">482: Loop Detected</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">25 Exchange - routing error</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">483: Too many hops</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">25 Exchange - routing error</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">484: Address incomplete</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">28 Invalid Number Format</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">485: Ambiguous</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">1 Unallocated number</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">486: Busy here</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">17 User busy</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">500: Server internal error</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">41 Temporary failure</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">501: Not implemented</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">79 Not implemented, unspecified</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">502: Bad gateway</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">38 Network out of order</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">503: Service unavailable</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">41 Temporary failure</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">504:Server time-out</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">102 Recovery on timer expiry</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">504: Version Not Supported</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">513: Message Too Large</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">127 Interworking</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">600: Busy everywhere</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">17 User busy</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">603: Decline</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">21 Call rejected</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__1">604: Does not exist anywhere</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_zpb_dvn_5fb__table_axr_fvn_5fb__entry__2">1 Unallocated number</td>
          </tr>
        </tbody></table>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title5" id="reference_njy_zvn_5fb">
  <h2 class="title topictitle2" id="ariaid-title5">Default Conversion of Standard Q.850 ISDN Cause Codes to SIP Error Codes</h2>
  <div class="body refbody">
    <section class="section">Mediatrix devices internally use Q.850 ISDN cause codes as the common representation
      for call errors and call terminations. Mediatrix devices are gateways used between SIP and
      conventional (i.e. non-SIP) telephony technologies; therefore, converting SIP error codes to
      Q.850 ISDN cause codes is required in both directions i.e. from SIP to ISDN and ISDN to SIP.
        <p class="p">The following table presents the conversion of Q.850 ISDN Cause Codes to SIP Error Codes.
        It is possible to override these default conversions and to configure the conversions of any
        other Q.850 ISDN Cause Codes between 1 and 127. (Refer to the Basic tasks.)</p></section>
    <section class="section"><h3 class="title sectiontitle">Normal Event</h3>
      
    </section>
    <table class="table frame-all" id="reference_njy_zvn_5fb__table_itz_fwn_5fb"><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="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">Q.850 ISDN Cause Codes</th>
            <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">SIP Error Codes</th>
          </tr>
        </thead><tbody class="tbody">
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">1: Unassigned (unallocated) number.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">404 Not Found</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">2: No route to specified transit network.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">404 Not Found</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">3: No route to destination.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">404 Not Found</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">6: Channel unacceptable.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">500 Internal Server Error</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">7: Call awarded and being delivered in an established channel.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">500 Internal Server Error</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">16 normal call clearing</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">--- BYE or CANCEL</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">17: User busy.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">486 Busy Here</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">18: No user responding.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">408 Request Timeout</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">19: User alerting, no answer.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">480 Temporarily unavailable</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">20: Subscriber absent.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">480 Temporarily unavailable</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">21: Call rejected.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">403 Forbidden</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">22: Number changed (w/o diagnostic).</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">410 Gone</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">22: Number changed (w diagnostic).</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">301 Moved Permanently</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">23: Redirection to new destination.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">410 Gone</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">26: Non-selected user clearing.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">404 Not Found</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">27: Destination out of order.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">502 Bad Gateway</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">28: Invalid number format (incomplete number)</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">484 Address incomplete</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">29: Facility rejected.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">501 Not implemented</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">30: Response to STATUS ENQUIRY.</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">500 Internal Server Error</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__1">31 normal unspecified</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_itz_fwn_5fb__entry__2">480 Temporarily unavailable</td>
          </tr>
        </tbody></table>
    <section class="section"><h3 class="title sectiontitle">Resource unavailable</h3>
      
      <table class="table frame-all" id="reference_njy_zvn_5fb__table_icm_1xn_5fb"><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="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">ISUP Cause Value</th>
              <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">SIP Response</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">34: No circuit/channel available. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">503 Service unavailable</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">38: Network out of order. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">503 Service unavailable</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">41: Temporary failure.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">503 Service unavailable</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1"> 42: Switching equipment congestion. .</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">503 Service unavailable</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">43: Access information discarded. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">44: Requested circuit/channel not available. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__1">47: Resource unavailable, unspecified</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_icm_1xn_5fb__entry__2">503 Service unavailable</td>
            </tr>
          </tbody></table>
    </section>
    <section class="section"><h3 class="title sectiontitle">Service or option not available</h3>
      
      <table class="table frame-all" id="reference_njy_zvn_5fb__table_r54_fxn_5fb"><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="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__1">ISUP Cause Value</th>
              <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__2">SIP Response</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__1">55: Incoming calls barred within CUG. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__2">403 Forbidden</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__1">57: Bearer capability not authorized. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__2">403 Forbidden</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__1">58: Bearer capability not presently available.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__2">503 Service unavailable</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__1">63: Service or option not available, unspecified.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_r54_fxn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
          </tbody></table>
    </section>
    <section class="section"><h3 class="title sectiontitle">Service or option not implemented</h3>
      
      <table class="table frame-all" id="reference_njy_zvn_5fb__table_mtc_kxn_5fb"><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="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__1">ISUP Cause Value</th>
              <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__2">SIP Response</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__1">65: Bearer capability not implemented.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__2">488 Not Acceptable Here</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__1"> 66: Channel type not implemented. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__1">69: Requested facility not implemented. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__1">70: Only restricted digital information bearer. .</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__2">488 Not Acceptable Here</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__1">79: Service or option not implemented, unspecified</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mtc_kxn_5fb__entry__2">501 Not Implemented</td>
            </tr>
          </tbody></table>
    </section>
    <section class="section"><h3 class="title sectiontitle">Invalid Message</h3>
      
      <table class="table frame-all" id="reference_njy_zvn_5fb__table_ksc_4xn_5fb"><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="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">ISUP Cause Value</th>
              <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">SIP Response</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">81: Invalid call reference value. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">82: Identified channel does not exist. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">83: A suspended call exists, but this call identity does not. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">84: Call identity in use. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">85: No call suspended. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">86: Call having the requested call identity has been cleared. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">87: user not member of CUG.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">403 Forbidden</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1"> 88: Incompatible destination..</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">503 Service unavailable</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1"> 91: Invalid transit network selection. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__1">95: Invalid message, unspecified</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_ksc_4xn_5fb__entry__2">500 Internal Server Error</td>
            </tr>
          </tbody></table>
    </section>
    <section class="section"><h3 class="title sectiontitle">Protocol error</h3>
      
      <table class="table frame-all" id="reference_njy_zvn_5fb__table_txy_txn_5fb"><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="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">ISUP Cause Value</th>
              <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">SIP Response</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">96: Mandatory information element is missing.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1"> 97: Message type non-existent or not implemented.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1"> 98: Message not compatible with call state or message type non-existent or not
                implemented. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">99: Information element non-existent or not implemented. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">100: Invalid information element contents. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">101: Message not compatible with call state. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500: Internal Server Error</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">102: Recovery on time expiry. </td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">504 Gateway timeout</td>
            </tr>
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__1">111: Protocol error, unspecified.</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_txy_txn_5fb__entry__2">500 Server internal error</td>
            </tr>
          </tbody></table>
    </section>
    <section class="section"><h3 class="title sectiontitle">Interworking</h3>
      
      <table class="table frame-all" id="reference_njy_zvn_5fb__table_mq1_zxn_5fb"><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="reference_njy_zvn_5fb__table_mq1_zxn_5fb__entry__1">ISUP Cause Value</th>
              <th class="entry colsep-1 rowsep-1" id="reference_njy_zvn_5fb__table_mq1_zxn_5fb__entry__2">SIP Response</th>
            </tr>
          </thead><tbody class="tbody">
            <tr class="row">
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mq1_zxn_5fb__entry__1">127: Interworking, unspecified</td>
              <td class="entry colsep-1 rowsep-1" headers="reference_njy_zvn_5fb__table_mq1_zxn_5fb__entry__2">500 Server internal error</td>
            </tr>
          </tbody></table>
    </section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title6" id="concept_glr_y4t_5fb">
 <h2 class="title topictitle2" id="ariaid-title6">PRACK</h2>
 
 <div class="body conbody"><p class="shortdesc">Reliable provisional responses (PRACK) is supported as per RFC 3262.</p>
  <div class="p">It is possible to define the type of PRACK support when acting as a:<ul class="ul" id="concept_glr_y4t_5fb__ul_gld_2pt_5fb">
        <li class="li">user agent client</li>
        <li class="li">user agent server</li>
      </ul></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_ndb_b5t_5fb">
 <h2 class="title topictitle2" id="ariaid-title7">Session Timer Extension</h2>
 
 <div class="body conbody"><p class="shortdesc">The session timer extension allows detecting the premature end of a call caused by a
    network problem or a peer’s failure by resending a refresh request periodically. </p>
  <p class="p">This refresh request sent by the Mediatrix unit is either a reINVITE or an UPDATE, according to
      the configuration of the <span class="keyword wintitle">Session Refresh Request Method</span> parameter.</p>
  <p class="p">A successful response (200 OK) to this refresh request indicates that the peer is still alive
   and reachable. A timeout to this refresh request may mean that there are problems in the
   signalling path or that the peer is no longer available. In that case, the call is shut down by
   using normal SIP means.</p>
 </div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title8" id="concept_mpd_k5t_5fb">
 <h3 class="title topictitle3" id="ariaid-title8">SDP in Session Timer reINVITEs or UPDATEs</h3>
 <p class="shortdesc">The reINVITE is sent with the last SDP that was negotiated. Receiving a session timer
  reINVITE should not modify the connection characteristics. If the reINVITE method is used, it is
  sent with the last SDP that was negotiated. Reception of a session timer reINVITE should not
  modify the connection characteristics. If the UPDATE method is used, it is sent without any SDP
  offer.</p>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title9" id="concept_phf_r5t_5fb">
 <h3 class="title topictitle3" id="ariaid-title9">Relation Between Minimum and Maximum Values </h3>
 
 <div class="body conbody"><p class="shortdesc">A user agent that receives a Session-Expires header whose value is smaller than the
  minimum it is willing to accept replies a “422 Timer too low” to the INVITE and terminates the
  call. The phone does not ring.</p>
  <p class="p"> It is up to the caller to decide what to do when it receives a 422 to its INVITE. The
   Mediatrix unit will automatically retry the INVITE, with a Session-Expires value equal to the
   minimum value that the user agent server was ready to accept (located in the Min-SE header). This
   means that the maximum value as set in the Mediatrix unit might not be followed. This has the
   advantage of establishing the call even if the two endpoints have conflicting values. The
   Mediatrix unit will also keep retrying as long as it gets 422 answers with different Min-SE
   values.</p>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested2" aria-labelledby="ariaid-title10" id="concept_nmf_x5t_5fb">
 <h3 class="title topictitle3" id="ariaid-title10">Session Refresh</h3>
 
 <div class="body conbody"><p class="shortdesc">Sending a session timer reINVITE or UPDATE is referred to as refreshing the
  session.</p>
  <p class="p"> Normally, the user agent server that receives the INVITE has the last word on who refreshes.
   The Mediatrix unit always lets the user agent client (caller) perform the refreshes if the caller
   supports session timers. In the case where the caller does not support session timers, the
   Mediatrix unit assumes the role of the refresher.</p>
 </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title11" id="concept_kzy_3d5_5fb">
 <h2 class="title topictitle2" id="ariaid-title11">Event Handling</h2>
 
 <div class="body conbody"><p class="shortdesc">The Mediatrix unit supports receiving event handling Notifications to start a remote
  reboot or a sync of configuration for specific endpoint(s).</p>
  <div class="p"> The event handling Notifications "reboot" or "check-sync" is not specified in an Allow-Events
   header. The Mediatrix unit supports the Notify without subscription. <div class="note note note_note"><span class="note__title">Note:</span> It is recommended to
    use these event handling notifications only when the SIP transport is secure (TLS) or when the
    firewall filters the requests sent to the unit.</div></div>
 </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title12" id="topic_title_Basic_Tasks_d1e25">
   <h1 class="title topictitle1" id="ariaid-title12">Basic Tasks</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title13" id="task_xgs_stn_5fb">
    <h2 class="title topictitle2" id="ariaid-title13">Configuring the SIP Penalty Box</h2>
    <div class="body taskbody">
        <section id="task_xgs_stn_5fb__steps_arx_ttn_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_xgs_stn_5fb__steps_arx_ttn_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Penalty Box</span>
                    table, from the <span class="keyword wintitle">Penalty Box Activation</span>list,
                    choose <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Penalty Box Times </span> field, enter the duration during which the SIP target will remain in the SIP
                    penalty box.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_xgs_stn_5fb__image_vyn_v5n_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/Penaltyboxenable.png" width="800"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title14" id="task_vpc_rzn_5fb">
    <h2 class="title topictitle2" id="ariaid-title14">Overriding the Default Mapping for SIP Error Code to ISDN Cause </h2>
    <div class="body taskbody">
        <section id="task_vpc_rzn_5fb__steps_tsj_5zn_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_vpc_rzn_5fb__steps_tsj_5zn_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">SIP to Cause Error Mapping</span>
                    table, click <img class="image" id="task_vpc_rzn_5fb__image_ssn_p14_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/Plusbleu.jpg" width="15">.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Configure New SIP to Cause
                Error Mapping</span> table, from the <span class="keyword wintitle">Suggestion</span> list, choose a
                    SIP code and cause.</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>For example:<br><img class="image" id="task_vpc_rzn_5fb__image_xyc_5g4_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/SIPtoCausemapping.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title15" id="unique_1042068691910885398">
    <h2 class="title topictitle2" id="ariaid-title15">Overriding the Default Mapping for ISDN Cause to SIP Error Codes </h2>
    <div class="body taskbody">
        <section id="unique_1042068691910885398__steps_tsj_5zn_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_1042068691910885398__steps_tsj_5zn_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Cause to SIP Error
              Mapping</span>
                    table, click <img class="image" id="unique_1042068691910885398__image_ssn_p14_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/Plusbleu.jpg" width="15">.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Configure New Cause to SIP
                Error Mapping</span> table, from the <span class="keyword wintitle">Suggestion</span> list, choose a
                    SIP code and cause.</span>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="unique_1042068691910885398__image_y23_kh4_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/CauseToSIPmapping.png" width="800"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title16" id="task_gr1_nmt_5fb">
    <h2 class="title topictitle2" id="ariaid-title16">Choosing to Use Additional Headers</h2>
    <div class="body taskbody">
        <section id="task_gr1_nmt_5fb__steps_l1b_5mt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_gr1_nmt_5fb__steps_l1b_5mt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Additional Headers</span> table, set
                    the <span class="keyword wintitle">Reason Support</span>,
                    the <span class="keyword wintitle">Referred-By Support</span>
                    and the <span class="keyword wintitle">Privacy Headers In Response</span>
                    fields as required. </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 Reason and the Referred-By SIP Headers will be handled as chosen.<br><img class="image" id="task_gr1_nmt_5fb__image_fcm_n4t_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/AdditionalHeaders.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title17" id="task_nkr_q4t_5fb">
    <h2 class="title topictitle2" id="ariaid-title17">Defining the Type of PRACK Support</h2>
    <div class="body taskbody">
        <section id="task_nkr_q4t_5fb__steps_hlm_qpt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_nkr_q4t_5fb__steps_hlm_qpt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Prack</span> table,
                    set the <span class="keyword wintitle">UAC PRACK Support (RFC 3262)</span> and
                        <span class="keyword wintitle">UAS PRACK Support (RFC 3262)</span>
                    fields as required. </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>When acting as a user agent server or client, the RFC 3262 (PRACK) will or not be
                supported.<br><img class="image" id="task_nkr_q4t_5fb__image_b2z_dqt_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/Prack.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title18" id="task_mjp_rqt_5fb">
    <h2 class="title topictitle2" id="ariaid-title18">Setting the Session Refresh Information</h2>
    <div class="body taskbody">
        <section id="task_mjp_rqt_5fb__steps_ynr_lst_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_mjp_rqt_5fb__steps_ynr_lst_5fb"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Session Refresh</span>, table, set the <span class="keyword wintitle">Session Refresh Timer Enable</span>
                    selection list  to <span class="keyword wintitle">Enable</span>. </span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Disabling this parameter is not recommended since it will make 'dead'
                        calls impossible to detect.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set the <span class="keyword wintitle">Minimum Expiration Delays</span>
                    field. </span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> The value of the  <span class="keyword wintitle">Minimum Expiration Delays</span>
                        must be equal or smaller than the <span class="keyword wintitle">Maximum Expiration Delays</span>
                        value.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set the <span class="keyword wintitle">Maximum Expiration Delays</span>
                    field.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> The value of the  <span class="keyword wintitle">Maximum Expiration Delays</span>
                        must be equal or higher than the <span class="keyword wintitle">Minimum Expiration Delays</span>
                        value.</div>
                </div>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> When the <span class="keyword wintitle">Maximum Expiration Delays</span>
                        value is lower than the <span class="keyword wintitle">Minimum Expiration Delays</span>
                        value, the minimum and maximum expiration delay values in INVITE packets are
                        the same as the value set in the Minimum Expiration Delay field.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Set the <span class="keyword wintitle">Session Refresh Request Method</span>
                    field. </span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Session Refresh Requests can be received via both methods, regardless of
                        how this parameter is configured.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>For example : <br><img class="image" id="task_mjp_rqt_5fb__image_xpx_m35_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/SessionRefresh.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title19" id="task_bhy_fvt_5fb">
    <h2 class="title topictitle2" id="ariaid-title19">Overriding the SIP Domain Used</h2>
    <div class="body taskbody">
        <section id="task_bhy_fvt_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_bhy_fvt_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Gateway Configuration</span> table,
                    in the <span class="keyword wintitle">SIP Domain Override</span> field, enter the SIP domain name that should be used instead of the home
                    domain proxy. </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 specified SIP domain name will be used instead of the home domain proxy
                (<span class="keyword wintitle">Proxy Host</span> field under
                <span class="keyword wintitle">SIP</span>/ <span class="keyword wintitle">Servers</span> ) in the address of record
            and the request-URI. When it overrides the home domain proxy in the request-URI, the
            request-URI also contains a maddr parameter with the resolved home domain proxy to make
            sure the requests are routable.<br><img class="image" id="task_bhy_fvt_5fb__image_plt_tvt_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/GatewayConfiguration_TrunkLines.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title20" id="task_msh_cyt_5fb">
    <h2 class="title topictitle2" id="ariaid-title20">Setting the Blind Transfer Method</h2>
    <div class="body taskbody">
        <section id="task_msh_cyt_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_msh_cyt_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">SIP Transfer</span>
                    table, from the <span class="keyword wintitle">Blind Transfer Method</span> choose
                    the required method. </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 blind transfer will be achieved as set when participating in a transfer as the
            transferor. For example: <br><img class="image" id="task_msh_cyt_5fb__image_tmc_zzt_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/SipTransfer.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title21" id="task_czv_d15_5fb">
    <h2 class="title topictitle2" id="ariaid-title21">Configuring Call Diversion</h2>
    <div class="body taskbody">
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>The Diversion feature is not available in the NI2 and QSIG signalling protocols.
            For more details on ISDN PRI interfaces, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/ISDN+User+Guide" target="_blank">DGW Configuration Guide - ISDN user guide</a>
            published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</section>
        <section id="task_czv_d15_5fb__steps_fts_k15_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_czv_d15_5fb__steps_fts_k15_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Diversion</span>
                    table, from the selection list, choose the required <span class="keyword wintitle">Method</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The Gateway will use the SIP method selected to receive/send call diversion
            information in an INVITE. For example: <br><img class="image" id="task_czv_d15_5fb__image_ppr_s15_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/Diversion.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title22" id="task_hhd_y15_5fb">
    <h2 class="title topictitle2" id="ariaid-title22">Configuring Supported DNS Queries</h2>
    <div class="body taskbody">
        <section id="task_hhd_y15_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_hhd_y15_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">DNS</span> table,
                    from the <span class="keyword wintitle">Supported DNS Queries</span>
                    selection , select the type of DNS queries that the SipEp service supports.
                </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 SipEp service will support and use the selected DNS queries. For example: <br><img class="image" id="task_hhd_y15_5fb__image_p3y_hb5_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/Dns.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title23" id="task_chp_nd5_5fb">
    <h2 class="title topictitle2" id="ariaid-title23">Configuring Event Handling</h2>
    <div class="body taskbody">
        <section id="task_chp_nd5_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_chp_nd5_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Event Handling</span>
                    table, for each gateway, from the <span class="keyword wintitle">Reboot</span> selection list,
                    choose how the gateway handles the reboot SIP NOTIFY messages.</span>
            </li><li class="li step">
                <span class="ph cmd">From the <span class="keyword wintitle">Check Sync</span>
                    selection list, choose how the gateway handles check-sync SIP NOTIFY
                    messages.</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 SIP Gateway will handle  reboot SIP NOTIFY messages and the check-sync SIP
            NOTIFY messages as configured.<br><img class="image" id="task_chp_nd5_5fb__image_hn1_325_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/EventHandling.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title24" id="task_htc_m25_5fb">
    <h2 class="title topictitle2" id="ariaid-title24">Enabling Messaging Subscription</h2>
    <div class="body taskbody">
        <section id="task_htc_m25_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_htc_m25_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Messaging Subscription</span> table,
                    from the selection list, choose <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The unit will add the username in the request URI of MWI SUBSCRIBE requests.<br><img class="image" id="task_htc_m25_5fb__image_owt_y25_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/MessagingSubscription.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title25" id="task_h13_ff5_5fb">
    <h2 class="title topictitle2" id="ariaid-title25">Configuring Advice of Charge (AOC)</h2>
    <div class="body taskbody">
        <section id="task_h13_ff5_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_h13_ff5_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">AOC</span> table, for
                    each gateway, choose from the <span class="keyword wintitle">AOC-D Support</span> and <span class="keyword wintitle">AOCE Support</span> fields how the
                    AOC-D and AOC-E messages are sent.</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 current charge will be sent either (D)uring the call in AOC-D messages or at the
            (E)nd of the call in AOC-E messages.<br><img class="image" id="task_h13_ff5_5fb__image_on5_sf5_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/AOC.png" width="800"><br></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title26" id="task_amf_xf5_5fb">
    <h2 class="title topictitle2" id="ariaid-title26">Enabling the Media Security Agreement Parameter</h2>
    <div class="body taskbody">
        <section id="task_amf_xf5_5fb__steps_txr_3vt_5fb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_amf_xf5_5fb__steps_txr_3vt_5fb"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">Security Mechanism Agreement</span>
                    table, from the <span class="keyword wintitle">Media Security Agreement</span>
                    selection list, choose <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>Once enabled, security headers are added to the SIP signalling to agree upon the
            security mechanism to be used for the media, i.e. SRTP with SDES.<br><img class="image" id="task_amf_xf5_5fb__image_nw5_hg5_5fb" src="https://documentation.media5corp.com/download/attachments/62825785/SEcurityMechanismAgreement.png" width="800"><br></section>
    </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title27" id="reference_h3d_yvp_mcb">
  <h1 class="title topictitle1" id="ariaid-title27">Advanced Misc SIP Parameters</h1>
  <div class="body refbody">
        <section class="section">Although most of the DGW parameters can be configured in the Web browser, some
            aspects of the configuration can only be completed with the configuration parameters
                by:<ul class="ul" id="reference_h3d_yvp_mcb__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>For more details on the following 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">
            <ul class="ul" id="reference_h3d_yvp_mcb__ul_t4w_tjv_gfb">
                <li class="li">To set the forked provisional responses behaviour::
                        <span class="keyword parmname">SipEp.interopForkedProvisionalResponsesBehavior</span></li>
                <li class="li">To set the DNS failure concealment parameter:
                        <span class="keyword parmname">Sip.DnsFailureConcealment</span>
                    <div class="note note note_note"><span class="note__title">Note:</span> This parameter applies only to Endpoint Gateway types; it has no effect on
                        Trunk Gateways. The behavior on Trunk Gateways always matches the "none"
                        value.</div></li>
            </ul>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title28" id="reference_j4g_nbv_gfb">
  <h1 class="title topictitle1" id="ariaid-title28">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-title29" id="concept_v4k_q3h_1r">
 <h1 class="title topictitle1" id="ariaid-title29">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-title30" id="concept_fqm_rv4_k4">
 <h1 class="title topictitle1" id="ariaid-title30">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>