Top

Enabling Power Feeding

Context
Note:
Your unit must support Power Feeding.
Steps
  1. Go to System/Hardware.
  2. From the BRI Cards Configuration table, from the Power Feeding drop down list, select Enable.
  3. Click Apply.
Result
Unit will feed power to the selected BRI interface.

Top

Selecting the Source of the Clock Reference

Steps
  1. Go to System/Hardware.
  2. From the Clock Reference Configuration table, select from the Suggestion list, several clock reference sources.
  3. Click Apply.
Result
The selected Clock Reference sources for each available telephony card, according to the unit type, are displayed in the Value field of the Clock Reference Configuration table. The first selected source will be used as a the clock reference. The following one will be used as the fallback source, in the listed order, if the first one becomes unavailable. Only one source is used at a time for the Clock Reference.

Top

Configuring the Syslog Server

Steps
  1. Go to System/Event Log.
  2. In the Syslog Configuration table, in the Remote Host field, enter the IP address of the syslog server.
    Note:
    If you are gathering packets using Wireshark, you can also use the IP of the PC that takes the Wireshark capture.
  3. Click Apply.
Result


Top

Enabling Diagnostic Traces

Context
Note:
Enabling the Diagnostic Traces should only be done when debugging an issue, as it can reduce the overall performance of the unit.
Steps
  1. Go to System/Syslog.
  2. In the Technical Assistance Center section (bottom of page), from the selection list located next to Diagnostic Traces, select Enable.
Result


Top

Configuring the Default Network Gateway to a Static IP Address

Steps
  1. Go to Network/Host.
  2. In the Default Gateway Configuration table, from the IPv4/Configuration Source selection list, select Static.
  3. In the IPv4/Default Gateway field, enter the IP address used as the Static Default Router for the Uplink Network Interface.
  4. In the Default Gateway Configuration table, from the IPv6/Configuration Source selection list, select Static.
  5. In the IPv6/Default Gateway field, enter the IP address used as the Static Default Router for the Uplink Network Interface.
  6. Click Apply.
Result
The specified address is used as the current default router address.

Top

Configuring the SNTP Server to a Static IP Address

Before you begin
Make sure there is an SNTP server available.
Steps
  1. Go to Network/Host.
  2. In the SNTP Configuration table, from the Configuration Source selection list, select Static.
  3. Provide an IP address or domain name and port numbers for each SNTP server you are using.
    Note:
    The best practice is to use the servers supplied by your Internet Service Provider, then complement with servers from a different network close to your geographical area. For example: time.nist.gov (USA), ntp4.sptime.se (Sweden), time1.isu.net.sa (Saudi Arabia), ntp.nict.jp (Japan), time.google.com (Worldwide), pool.ntp.org or one of their regional server pools (see https://www.ntppool.org/ for more information).
  4. If necessary, change the value of the Synchronisation Period.
  5. If necessary, change the value of the Synchronisation Period on Error.
  6. Click Apply.
Result
The SNTP host name and port will be displayed in the Host Status table under Network/Status.

Top

Configuring the Domain Name Server (DNS)

Before you begin
Although it is possible to use public DNS servers you should always ask your internet service provider to provide at least the primary and secondary DNS servers.
Steps
  1. Go to Network/Host.
  2. In the DNS Configuration table, form the Configuration Source selection list, select Static.
  3. For each DNS used, enter the IP address of the DNS.
  4. Click Apply.
Result


Top

Configuring a Network Interface

Context
When configuring network interfaces, Media5 recommends to have a syslog client properly configured and enabled in order to receive any message related to the network interfaces behaviour. The interface used to access the syslog client must also be properly enabled.
Steps
  1. Go to Network/Interfaces.
    IMPORTANT:
    Use extreme care when configuring network interfaces, especially when configuring the network interface used to contact the unit for management. Be careful never to disable or delete the network interface used to contact the unit. Also be careful to always set the unit’s management interface to be an interface that you can contact.
  2. In the Network Interface Configuration table, complete the fields as required.
  3. From the Activation drop-down list, select Enable.
  4. Click Apply.
Top

Configuring the BRI Interface

Before you begin
You must be using a BRI phone.
Steps
  1. Go to ISDN/Basic Rate Interface.
  2. From the Select Interface dropbox, select Bri1
  3. In the Interface Configuration table, set Endpoint Type to NT.
  4. Set Connection Type to Point to Multipoint.
  5. Set Inband DTMF Dialing to Enable.
  6. Set Exclusive B-Channel Selection to Enable.
  7. Set the Send Restart On Startup.
  8. Leave all the other parameters to their default values.
  9. From the Apply To The Following Interfaces select the interfaces for which the configuration will be applied to.
  10. Click Apply.
Result


Top

Configuring Interoperability

Steps
  1. Go to ISDN/Interop.
  2. From the Select Interface selection list, choose an interface PRI2.
  3. In the Interop Configuration table, select Enable for all fields.
  4. In the Apply To The Following Endpoints table, select the interfaces you wish to apply the interoperability configuration.
  5. Click Apply.
    Note:
    When facing issues in call establishment, disable the parameters one by one.
Result




Top

Enabling Calling Line Information Presentation

Steps
  1. Go to ISDN/Services.
  2. From the Select Interface drop-down menu, select the interface you want to configure.
  3. In the Services Configuration table, set Facility Services to Enable.
  4. Set Calling Line Information Presentation to Enable.
  5. In the MSN field, enter the numbers that will be allowed when a call is incoming from the SIP side.
    Note:
    Please refer to Show Help to apply the appropriate syntax.
  6. From the Apply To The Following Interfaces section, select the interfaces for which the configuration will be applied to.
  7. Click Apply.
Result

Support of ISDN FACILITY messages will be enabled.



Top

Registering Endpoints to All Gateways

Steps
  1. Go to SIP/Registrations.
    Note:
    If two or more endpoints have the same user name, a single registration request and/or subscription request will be performed under that user name.
  2. For each endpoint requiring registration, repeat the following 2 steps.
  3. From the Register selection list, select Enable.
  4. From the Gateway Name selection list, select All for each endpoint.
  5. Click Apply and Refresh.
Result


Top

Configuring Default SIP Servers

Before you begin
Steps
  1. Go to SIP/Servers.
  2. In the Default Servers table, in the Registrar Host field, enter the IP Address or the FQDN and port of your Registrar host.
    Note:
    :0 represents the 5060 default port. If you use the FQDN, using :0 will make the Mediatrix unit issue DNS SRV requests.
  3. In the Proxy Host field, enter the FQDN and port of your Proxy host.
    Note:
    :0 represents the 5060 default port. If you use the FQDN, using :0 will make the Mediatrix unit issue DNS SRV requests.
  4. If you are using an Outbound proxy, enter its IP address and port in the Outbound Proxy Host field.
  5. Click Apply.
  6. Click restart required services located at the top of the page.
Result
All gateways will use the default SIP servers, unless specified otherwise.

Top

Configuring Endpoint Authentication

Steps
  1. Go to SIP/Authentication.
  2. Click Edit All Entries located at the bottom of the page.
  3. In the Authentication table, from the Criteria selection list, select Endpoint for all endpoints needing registration.
  4. From the Endpoint selection list, select the related FXS port for each entry.
  5. From the Realm field, enter the provided realm and from the Validate Realm selection list, select Enable. If no Realm was provided, leave the field empty and from the Validate Realm selection list, select Disable.
  6. In the User Name field, enter the SIP user name for each entry.
  7. In the Password field, enter the appropriate password for each entry.
  8. Click Apply and Refresh Registration.
Result
The endpoints will be registered.

Top

Configuring OPTIONS Method Support

Context
Note:
This step is required if your server is configured to only receive 200 OK by the Mediatrix unit, when it polls the Mediatrix with SIP OPTIONS.
Note:
This is not supported by all SIP servers, this feature is not mandatory in most use cases.
Steps
  1. Go to SIP/Interop.
  2. In the SIP Interop table, from the OPTIONS Method Support selection list, select Always 200 OK.
  3. Click Apply.
Result
The unit will always answer 200 OK to SIP OPTIONS messages received (Keep Alive).

Top

Enabling Default Codecs

Steps
  1. Go to Media/Codecs.
  2. From the Select Codec Bank, choose if you want the G.722 , the G.723.1, G.726 or G.729 codec.
    Note:
    All Codec Banks include the T.38, the Clear Mode, the Clear Channel, and the X-CCD codecs.
  3. In the Codec table, select the desired codecs and Enable / Disable them.
    Note:
    Codecs that appear in Red are not part of the selected codec Bank, thus they can be disabled without a problem.
  4. Click for Advanced codec settings.
    Note:
    When enabling two codecs or more, the priority order can be modified by selecting the advanced options.
  5. Click Apply.
Result




Top

Configuring DTMF Transport

Steps
  1. Go to Media/Misc.
  2. In the DTMF Transport table, set the Transport Method to the one set in the VoIP server.
    1. In-band
    2. Out-of-Band using RTP (RFC2833). This is usually the preferred method. Remember to set the payload type if different (e.g.: 96, 101 or 110 in some cases).
    3. Out-of-Band using SIP. For Cisco or Avaya systems, from the SIP Transport Method field, use Info DTMF Relay. For legacy Nortel and others, leave Draft Choudhuri SIP Info Digit 00.
    4. Signaling Protocol Dependent: choose this method if unsure. It will try to use the method negotiated by the VoIP server.
  3. Click Apply.
Result


Top

Enabling the Payload Type Found in the Answer

Context

You cannot access this parameter from the DGW Web page, you must use the Command Line Interface (CLI).

Steps
  1. In the CLI, enter sipEp.interopUseDtmfPayloadTypeFoundInAnswer=1
    Note:
    For more details on the sipEp.interopUseDtmfPayloadTypeFoundInAnswer parameter, refer to the DGW Configuration Guide - Reference Guide published on the Media5 Documentation Portal or type "help SipEp.interopUseDtmfPayloadTypeFoundInAnswer".
  2. Click Enter.
Result
The Payload Type found in the answer is used instead of the configured Payload Type (Media/Misc/DTMF Transport).
Top
Top

Adding the # Key Dial Map

Context
The Mediatrix unit dial map # key is deactivated by default.
Steps
  1. Go to Telephony/DTMF Maps.
  2. In the Allowed DTMF Map table, complete the fields as required.
    Note:
    x.# - for speed dialling, e.g. 267# , call will be dialled right away once the # key is hit.
Result
For more details on DTMF map configuration, refer to the the DGW Configuratio Guide -DTMF Map Configuration -Dial Plan published on the Media5 Documentation Portal.

Top

Creating a Hunt

Steps
  1. Go to Call Router/Route Config.
  2. In the Hunt table,
    • click located on the same row as an existing hunt to add a new hunt above or,
    • click located at the bottom of the table to add a hunt at the end of the table.
    Note:
    You can create up to 40 hunts.
  3. In the Configure Hunt table, enter a name in the Name field.
  4. From the Suggestion selection list next to the Destinations field, select 1 or several destinations.
  5. From the Suggestion selection list next to the Causes field, select the causes pertinent to your situation.
  6. To create another hunt group, repeat steps 2 to 5 .
    Note:
    Up to 40 hunt groups can be created.
  7. Click Save.
Result
The hunt is available to be used in a route.

Top

Creating a Route from a SIP Gateway to a Destination

Steps
  1. Go to Call Router/Route Config.
  2. In the Routes table, click .
    • click located on the same row as an existing route to add a new route above or,
    • click located at the bottom of the table to add a route at the end of the table.
    Note:
    A maximum of 40 routes can be created.
  3. In the Configure Route table, from the selection list of the Sources field, select a SIP gateway.
  4. If necessary, from the selection list of the Destination field, select an Interface or a hunt group.
    Note:
    Leave the Signaling Properties, the Transformations and Criteria Property fields empty.
  5. Click Save.
Result
A new route is created and will appear in the Routes table.

Top

Creating a Route from a Physical Interface to a SIP Destination

Steps
  1. Go to Call Router/Route Config.
  2. In the Routes table, click .
  3. In the Configure Route table, from the selection list of the Sources field, select an interface.
  4. From the selection list of the Destination field, select a SIP Gateway or a SIP hunt group.
    Note:
    Leave the Signaling Properties, the Transformations and Criteria Property fields empty.
    Note:
    A maximum of 40 routes can be created.
  5. Click Save.
Result


Top

Restarting Services

Steps
  1. Go to System/Services.
  2. In the restart required services table, click restart required services.
Top

Online Help

If you are not familiar with the meaning of the fields and buttons, click Show Help, 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.

Top

DGW Documentation

Mediatrix devices are supplied with an exhaustive set of documentation.

Mediatrix user documentation is available on the Media5 Documentation Portal.

Several types of documents were created to clearly present the information you are looking for. Our documentation includes:
  • Release notes: 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.
  • Configuration notes: 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.
  • Technical bulletins: These documents are created to facilitate the configuration of a specific technical action, such as performing a firmware upgrade.
  • Hardware installation guide: 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.
  • User guide: 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.
  • Reference guide: 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.
Top

Copyright Notice

Copyright © 2026 Media5 Corporation.

This document contains information that is proprietary to Media5 Corporation.

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.

This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever, without written prior approval by Media5 Corporation.

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.