Top

Mediatrix Gateway with the PSTN

This document outlines how to set up one Mediatrix gateway to act as a gateway with the PSTN

The Mediatrix digital gateway is used to connect an existing VoIP network to the PSTN. In this configuration notes, the Mediatrix gateway is configured to either:

  • Receive calls from the PSTN and route them to the VoIP network (right to left):
  • Receive calls from the VoIP network and route them to the PSTN (left to right)

Top

Configuring the Mediatrix Digital Gateway

Information to Know Before Starting

Before starting to use these configuration notes, complete the following table to make sure you have the required information to complete the different steps.

Note: The ISDN ports of the Mediatrix Gateway, i.e the PRI and BRI ports must first be configured. For the complete ISDN configuration information, refer to the ISDN User Guide published on the Media5 Documentation Portal.
Note: 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.
Note: The Mediatrix unit must be reinitialised to its factory default settings to make sure the configuration can be successfully executed.
This document includes the basic configuration of an FXO, PRI and/or BRI gateway. If you wish to add registration and authentication, refer to the Technical Bulletin - Basic SIP Unit Registration and DGW Configuration Guide - SIP Authentication documentation published on the Media5 Documentation Portal.
Information Value Used in Step
IP address of unit Logging on to the Mediatrix Unit Web Interface
IP address or FQDN of Registrar host Configuring the Default SIP Servers
IP address or FQDN of Proxy host Configuring the Default SIP Servers
Type of endpoint used BRI, PRI and/or FXO Creating a Hunt Group - PSTN

Top

Logging on to the Mediatrix Unit Web Interface

Before you begin
The computer IP address must be in the same TCP/IP network as the Mediatrix unit.
About this task
For better performances, it is recommended to use the latest available version of Microsoft Internet Explorer, Google Chrome, or Mozilla Firefox.
Note: You may not be able to log on to the Mediatrix unit Web interface if you are using older browser versions.
Procedure
  1. In your Web browser, enter the IP address at which the Web interface of your Mediatrix unit can be reached.
    • If your network has an IPv4 DHCP server, connect the primary Ethernet port of the Mediatrix unit to the network (ETH1 port), use the provided DHCP server IP address.
    • You can also connect your computer to the secondary Ethernet port of the Mediatrix unit (ETH2), use the 192.168.0.10 IP address. However, the computer must also own an IP address in the 192.168.0.0/24 network.
  2. Enter admin as your username and administrator as the password.
    Note: You can also use public as a username and leave the password field empty; it has the full administration rights by default.
  3. Click Login.
Results
The Information page of the Web interface is displayed.

Top

Configuring the Default SIP Servers

Context
In some instances, the configuration of the default servers may already be completed.
Steps
  1. Go to SIP/Servers.
  2. In the Registrar Host field, indicate the server IP address or FQDN of the SIP Registrar server .
  3. In the Proxy Host field, indicate the server IP address or FQDN of the SIP Proxy server.
  4. In the Messaging Server Host field, indicate the server IP address or FQDN of the Messaging server, if needed.
  5. Leave the Outbound Proxy Host field empty, unless specifically instructed to set a value.
    Note: Setting the address to 0.0.0.0:0 or leaving the field empty disables the outbound proxy host.
  6. Click Apply.
  7. Located at the top of the page, click restart required services.
Result



Top

Creating a Hunt Group - PSTN

Steps
  1. Go to Call Router / Route Config.
  2. In the Hunt table, click .
  3. In the Configure New Hunt table, set the following:
    1. Set the Name field to hunt_PSTN.
    2. Using the Destinations dropbox, add the destination endpoints to use.
    3. Leave the other fields with their default value.
  4. Click Save.
Result



Top

Creating a Route from Sip-Default to hunt_PSTN

Steps
  1. Go to Call Router/ Route Config.
  2. In the Routes table, click .
  3. In the Configure Route table, set the following:
    1. Set the Sources field to sip-default.
    2. Set the Destination field to hunt-hunt_PSTN.
    3. Leave the other fields with their default value.
  4. Click Save.
Result



Top

Creating a Route From PRI/BRI/FXO ports to Sip-Default

Steps
  1. Go to Call Router/Route Config.
  2. In the Routes table, click .
  3. In the Configure Route table, set the following:
    1. Set the Sources field to one of the PRI, BRI and/or FXO endpoint of the gateway.
      Note: More than one endpoint can be added at a time.
    2. Set the Destination field to sip-default.
    3. Leave the other fields to their default value.
  4. Click Save.
Result



Top
Top

Configuring Automatic Call Activation on FXO Ports

Context
These steps are necessary for FXO ports, since analog lines do not provide the destination number. You must configure the FXO to point to an PBX or IVR extension, otherwise your callers will get a second dialtone after answering.
Steps
  1. Go to Telephony /Services.
  2. From the Select Endpoint selection list, select the FXO endpoint to configure.
  3. In the Automatic Call section, set theEndpoint Specific selection list to Yes.
  4. Set the Automatic Call Activation selection list to Enable.
  5. Set the Automatic Call Target selection list to the SIP server IVR or desired extension number.
  6. Repeat steps 2 to 5 for each FXO endpoint to configure.
  7. Click Apply.
Result
Calls from the selected endpoint lines will be sent to the configured destination number in the SIP server.

Top

Configuring the Country for all Endpoints

Steps
  1. Go to Telephony/Misc.
  2. Make sure the Select Endpoint drop-down list is set to Default.
  3. In the Country table, select your country from the drop-down list.
  4. 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
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 © 2021 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.