Skip to end of metadata
Go to start of metadata

Download PDF Document



2018-11-13
For Mediatrix Sentinel and Mediatrix 3000
v. 43.2.1343
Top

1 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.

Important

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 be displayed.

Note

These configuration notes can be successfully executed, provided your unit is using the Factory default settings.

Information Value Used in Step
IP address used by your Mediatrix unit to communicate with the Management Interface.
  • If your computer is connected to the Ethernet port meant to be connected to the Local Area Network (LAN), i.e. Eth2 on most devices
Use this value 192.168.0.10 Logging on to the Mediatrix Unit Web Interface
  • If your Mediatrix unit is configured to use a DHCP server, use the DHCP server- provided IP address.
Logging on to the Mediatrix Unit Web Interface
  • If your Mediatrix unit is configured to use the IPv6 Link Local
Locate the IP Link Local label underneath your Mediatrix unit. Logging on to the Mediatrix Unit Web Interface
Wan IP address as defined in your network address range. Configuring the Uplink Network Interface
LAN IP address as defined in your network address range Configuring the Uplink Network Interface
IP address of each DNS server Configuring the Domain Name Server (DNS)
IP address of each SNTP server Configuring the SNTP Server
Static Default Router IP address of the Uplink Network Interface Configuring the Default Network Gateway to a Static IP Address
IP address or FQDN of the service provider server Configuring the wan_ip_trunk_ca Call Agent
IP address of the IP PBX Configuring the lan_ip_pbx_ca Call Agent
Credentials to register against the service provider (username, password and registrar address) Configuring a Registration Agent
Top

2 SIP Trunking Back to Back User Agent Configuration

This scenario describes how to connect a local PBX to a SIP service provider through the corporate firewall using a Mediatrix SBC. The Mediatrix unit is located on the Edge.

  • The Mediatrix unit is set as a Demarcation point.
  • The Mediatrix unit may or may not register to the SIP service provider.
  • The Mediatrix unit is located on the edge of the Internet with one interface in the LAN and one on the Internet.

Top

2.1 Getting Started

Steps
  1. Make sure the WAN network interface (either WAN, ETH1, Ethernet, Network, or ETH5 depending on your model) of your Mediatrix unit is connected to the network.
  2. Make sure the second Ethernet connector (either LAN, ETH2, or Computer depending on your model) of your Mediatrix unit is connected to the computer.
  3. Log on to the Mediatrix unit Web interface.

    Note

    If you are using your Mediatrix unit for the first time, refer to its Mediatrix unit Quick Start guide.

Next Step

2.2 Logging on to the Mediatrix Unit Web Interface
Top

2.2 Logging on to the Mediatrix Unit Web Interface

Context
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. The computer's network card must be on the same subnet as the Mediatrix unit.

Steps
  1. In your Web browser, enter the IP address used by your Mediatrix unit to communicate with the Web interface.
    • If your computer is connected to the Ethernet port, commonly used to be connected to the Local Area Network (LAN), i.e. ETH2 on most devices, use the 192.168.0.10 IP address.
    • If your Mediatrix unit is configured to use a DHCP server with IPv4, use the provided DHCP server IP address.
  2. Enter public as your username and leave the password field empty.

    Note

    The public username account has administrator rights.

    Note

    You can also use admin as a username and administrator as password.

  3. Click Login.
Result
The Information page of the Web interface is displayed.

Next Step

2.3 Configuring the Lan1 Network Interface
Top

2.3 Configuring the Lan1 Network Interface

Steps
  1. Go to Network/Interfaces.
  2. From the Link list located next to Lan1, leave the default value.
  3. In the Static IP Address field, enter the LAN static IP address as defined in your network address range.
  4. Click Apply to apply all changes to the configuration.

    Note

    A Warning message is displayed, but this is normal.

  5. Click Apply.
Result
The Lan1 Network Interface will be available in all the lists of the Management Interface where a Network Interface needs to be selected. For example, in the Local Firewall, and Configuration pages.

Next Step

2.4 Associating the Lan1 Network Interface to the System Management Services
Top

2.3.1 Link Default Values for the Lan1 Network Interface

Unit Type Link Default Value
Sentinel 400 eth2-5
Sentinel 100 eth2-5
Mediatrix G7 eth2-5
Mediatrix S7 eht2-5
Mediatrix C7 series eth2
Mediatrix 3000 eth1-4
Mediatrix 4104 eth2
Mediatrix 4108/16/24 eth2
Mediatrix 4102 lan
Mediatrix 4400 series eth2
Mediatrix LP series eth2
Mediatrix 4108 IPPBX eth2
Top

2.4 Associating the Lan1 Network Interface to the System Management Services

Before You Start
Configuring the Lan1 Network Interface must be completed.
Steps
  1. Go to Management/Misc.
  2. From the Network Interface selection list, select Lan1.
  3. Click Apply.
Result
The user will access the System Management through the Lan1 Network Interface.

Next Step

2.5 Adding Local Firewall Rules
Top

2.5 Adding Local Firewall Rules

Before You Start
You must have a Network Interface created.
Steps
  1. Go to Network/Local Firewall.
  2. In the Local Firewall Rules table, click +.
  3. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Uplink.

      Note

      Uplink is case sensitive.

    • From the Protocol selection list, select UDP.
    • In the Destination Port, enter 20000-20999.
    • From the Action selection list, select Accept.
  4. Click +.
  5. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Lan1.

      Note

      Lan1 is case sensitive.

    • From the Protocol selection list, select UDP.
    • In the Destination Port, enter 20000-20999.
    • From the Action selection list, select Accept.
  6. Click +.
  7. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Lan1.

      Note

      Lan1 is case sensitive.

    • From the Protocol selection list, select TCP.
    • In the Destination Port, enter 80.
    • From the Action selection list, select Accept.
  8. Click +.
  9. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Uplink.

      Note

      Uplink is case sensitive.

    • From the Protocol selection list, select UDP.
    • In the Destination Port, enter 5060.
    • From the Action selection list, select Rate Limit Source.
    • In the Rate Limit Value field, enter 10.
    • In the Rate Limit Time Unit field, enter 60.
  10. Click +.
  11. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Lan1.

      Note

      Lan1 is case sensitive.

    • From the Protocol selection list, select UDP.
    • In the Destination Port, enter 5060.
    • From the Action selection list, select Rate Limit Source.
    • In the Rate Limit Value field, enter 10.
    • In the Rate Limit Time Unit field, enter 60.
  12. Click +.
  13. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Uplink.

      Note

      Uplink is case sensitive.

    • From the Protocol selection list, select TCP.
    • In the Destination Port, enter 5060.
    • From the Action selection list, select Rate Limit Source.
    • In the Rate Limit Value field, enter 10.
    • In the Rate Limit Time Unit field, enter 60.
  14. Click +.
  15. In the Local Firewall Rules table, complete the fields.

    Note

    Not all fields are mandatory. You may leave some fields empty.

    • From the Activation selection list, select Enable.
    • In the Destination Address, enter Lan1.

      Note

      Lan1 is case sensitive.

    • From the Protocol selection list, select TCP.
    • In the Destination Port, enter 5060.
    • From the Action selection list, select Rate Limit Source.
    • In the Rate Limit Value field, enter 10.
    • In the Rate Limit Time Unit field, enter 60.
  16. In the Local Firewall Configuration table, from the Default Policy selection list, select Drop.

    Note

    Before setting the Default Policy to Drop, review your rules to make sure that at least one rule accepts incoming packets, otherwise the communication with the Mediatrix unit will be lost.

  17. Click Save and Apply to apply all changes to the configuration.
Result
External calls will only reach the Mediatrix unit if they are using SIP (port 5060) protocol or RTP (port 20000-20999).The Local Firewall rules will open the ports intended for:
  • RTP on the WAN side (Step 3)
  • RTP on the LAN side (Step 5)
  • Web access (Step 7)
  • UDP for SIP signaling on the WAN side (Step 9)
  • UDP for SIP signaling on the LAN side (Step 11)
  • TCP for SIP signaling on the WAN side (Step 13)
  • TCP for SIP signaling on the LAN side (Step 15)

Next Step

2.6 Configuring the Uplink Network Interface
Top

2.6 Configuring the Uplink Network Interface

Steps
  1. Go to Network/Interfaces.
  2. In the Network Interface Configuration table, from the Link selection list located next to Uplink, leave the default value.
  3. From the Type selection list, select IpStatic (IPv4 Static).

    Note

    The Uplink Network Interface must be set with a fixed public IP address for the NAT/router to be able to do port-forwarding to the unit. It will also be easier for the PBX to communicate with the unit if the address is static.

  4. In the Static IP Address field enter the WAN static IP address.
  5. From the Activation selection list, select Enable.
  6. Click Apply to apply all changes to the configuration.

    Note

    Once the changes are applied, the connection with the unit might be lost. You may need to reconnect to the web page using the new address.

Next Step

2.7 Configuring the Default Network Gateway to a Static IP Address
Top

2.6.1 Link Default Values for the Uplink Network Interface

Unit Type Link Default Value
Sentinel 400 eth1
Sentinel 100 eth1
Mediatrix G7 eth1
Mediatrix S7 eth1
Mediatrix C7 series eth1
Mediatrix 3000 eth5
Mediatrix 4104 eth1/eth
Mediatrix 4108/16/24 eth1
Mediatrix 4102 Wan
Mediatrix 4400 series eth1
Mediatrix LP series eth1
Mediatrix 4108 IPPBX eth1
Top

2.7 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. Click Apply.
Result

Next Step

2.8 Configuring the Domain Name Server (DNS)
Top

2.8 Configuring the Domain Name Server (DNS)

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

Next Step

2.9 Configuring the SNTP Server
Top

2.9 Configuring the SNTP Server

Before You Start
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.
  4. If necessary, change the displayed default value of the Synchronisation Period.
  5. If necessary, change the displayed default 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.

Next Step

2.10 Configuring the uplink_s Signaling Interface
Top
Steps
  1. Go to SBC/Configuration.
  2. In the Signaling Interface Configuration table, from the Network selection list located next to uplink_s, make sure Uplink is selected.

    Note

    The Network Interfaces displayed in the Network column, are created under the Network/Interfaces page.

  3. In the Port field, set the SIP listening port for the Sbc service, if a listening port other than 5060 is required, or leave it as it is.
  4. Click Save.
  5. Click Apply to apply all changes to the configuration.
  6. Click restart required services, located at the top of the page.
Result
The Signaling Interface will be available when configuring a Call Agent, in the Configure Call Agent page in the Signaling Interface selection list.

Next Step

2.11 Configuring the lan1_s Signaling Interface
Top

2.11 Configuring the lan1_s Signaling Interface

Before You Start

Note

The lan1_s signaling interface is preconfigured by default. This step will only be necessary if the lan1_s signaling interface was deleted or modified.

Steps
  1. Go to SBC/Configuration.
  2. In the Signaling Interface Configuration table, from the Network selection list located next to lan1_s, make sure Lan1 is selected.

    Note

    The Network Interfaces displayed in the Network column, are created under the Network/Interfaces page.

  3. In the Port field, set the SIP listening port for the Sbc service, if a listening port other than 5060 is required, or leave it as it is.
  4. Click Save.
  5. Click Apply to apply all changes to the configuration.
  6. Click restart required services, located at the top of the page.
Result
The Signaling Interface will be available when configuring a Call Agent, in the Configure Call Agent page in the Signaling Interface selection list.

Next Step

2.12 Configuring the uplink_m Media Interface
Top
Steps
  1. Go to SBC/Configuration.
  2. In the Media Interface Configuration table, from the Network selection list located next to uplink_m, make sure Uplink is selected.

    Note

    The Network Interfaces displayed in the Network column, are created under Network/Interfaces page.

  3. In the Port Range field, set the media (RTP) port range, if a port range other than 20000-20999 is required, or leave it as it is.
  4. Click Save.
  5. Click Apply to apply all changes to the configuration.
  6. Click restart required services, located at the top of the page.
Result
The Media Interface will be available when configuring a call agent, in the Configure Call Agent page, in the Media Interface selection list.

Next Step

2.13 Configuring the lan1_m Media Interface
Top

2.13 Configuring the lan1_m Media Interface

Before You Start

Note

The lan1_m media interface is preconfigured by default. This step will only be necessary if the lan1_m media interface was deleted or modified.

Steps
  1. Go to SBC/Configuration.
  2. In the Media Interface Configuration table, from the Network selection list next to lan1_m, make sure Lan1 is selected.

    Note

    The Network Interfaces displayed in the Network column, are created under the Network/Interfaces page.

  3. In the Port Range field, set the media (RTP) port range, if a port range other than 20000-20999 is required, or leave it as it is.
  4. Click Save.
  5. Click Apply to apply all changes to the configuration.
  6. Click restart required services, located at the top of the page.
Result
The Media Interface will be available when configuring a call agent, in the Configure Call Agent page in the Media Interface selection list.

Next Step

2.14 Configuring the wan_ip_trunk_ca Call Agent
Top

2.14 Configuring the wan_ip_trunk_ca Call Agent

Steps
  1. Go to SBC/Configuration.
  2. Select the Enable check box, located next to wan_ip_trunk_ca.
  3. In the Call Agent Configuration table, click next to wan_ip_trunk_ca.
  4. In the Configure Call Agent table, complete the following fields:
    1. From the Signaling Interface selection list, select uplink_s.
    2. From the Media Interface selection list, select uplink_m.
    3. Set the Peer Host to the IP address of the service provider server or FQDN.
  5. Click Save.
  6. Click Apply to apply all changes to the configuration.
Result
No will be displayed in the Config. Modified field, indicating that the configuration that was modified is now applied to the system. When the Mediatrix SBC will use the selected Call Agent for a communication, the selected parameters will be applied.

Next Step

4.0.0.1 Configuring the secondary_ip_trunk_ca Call Agent
Top

2.15 Configuring the lan_ip_pbx_ca Call Agent

Steps
  1. Go to SBC/Configuration.
  2. Select the Enable check box located next to lan_ip_pbx_ca.
  3. In the Call Agent Configuration table, click next to lan_ip_pbx_ca.
  4. In the Configure Call Agent table, complete the fields as follows:
    1. From the Signaling Interface selection list, select lan1_s.
    2. From the Media Interface selection list, select lan1_m.
    3. Set the Peer Host to IP address of the IP PBX.
  5. Click Save.
  6. Click Apply to apply all changes to the configuration.
Result
No will be displayed in the Config. Modified field, indicating that the configuration that was modified is now applied to the system. When the Mediatrix SBC will use the selected Call Agent for a communication, the selected parameters will be applied.

Next Step

2.16 Configuring a Registration Agent
Top

2.16 Configuring a Registration Agent

Context

Note

This procedure is only necessary if your Mediatrix unit registers to the service provider.

Steps
  1. Go to SBC/Registration.
  2. In the Registration Agent Configuration table, click .

    Note

    A new line of fields is added.

  3. Complete the User Name, Friendly Name, and Domain parameters fields according to the service provider's requirements.
  4. In the Contact field, enter credentials to register against the service provider. Format must be sip:user@public_IP Address or sip:public_IP Address or sips:user@public_IP_Address:sip listening port;uri-parameters of the unit.
  5. If necessary, repeat step 2 to step 4 if you are using more than one service provider.
  6. Click Apply.
Result

Next Step

2.17 Configuring the Call Agent Penalty Box
Top

2.17 Configuring the Call Agent Penalty Box

Steps
  1. Go to SBC/Configuration.
  2. Click next to the Call Agent you wish to configure.
  3. In the Configure Call Agent table, set the Keep-Alive field to 30.
  4. Set the Blacklisting Duration to 60.
  5. Click Save.
Result

Next Step

2.18 Importing Rulesets
Top

2.18 Importing Rulesets

Before You Start
Rulesets must be imported. The latest Ruleset package can be found on the Media5 Support Portal (you will be required to supply a user name and password).
Context
This procedure is valid for Call Agent and Routing Rulesets.
Steps
  1. Go to Management/File.

    Note

    Required Rulesets depend on the scenario being configured. Refer to the Call Agent and Routing Ruleset sections of the configuration notes for details on Rulesets needed to complete the configuration.

    Note

    Step 2 is only required when importing the first Ruleset and if you are not using a secure connexion to access the Management Interface (http://).

  2. Click Activate unsecure file transfer through web browser.
  3. From the Path field, select sbc/rulesets/.
  4. Click Browse, and navigate to the Ruleset you wish to import.

    Note

    Ruleset file extension must be *.crs for Call Agent Rulesets or *.rrs for Routing Rulesets.

  5. Click Import.
Result
The imported Ruleset will appear in the Internal files table, with the selected path in front of the name. The Ruleset will be available in the tables of the SBC/Rulesets page.

Next Step

2.19 Associating Call Agent Rulesets to a Call Agent
Top

2.19 Associating Call Agent Rulesets to a Call Agent

Before You Start
Steps
  1. Go to SBC/Configuration.

    Note

    Refer to the Call Agents section to identify which Rulesets are associated with the Call Agents used in this Use Case.

  2. From the Call Agent Configuration table, click located on the same row as the Call Agent to which you wish to associate a Ruleset.
  3. In the Call Agent Rulesets table, click .
  4. From the Name selection list, select a Ruleset.
  5. To add other Rulesets, click .
  6. Click Save.
  7. In the Configure Call Agent page, click Save.
  8. Click Apply to apply all changes to the configuration.
Result

Next Step

2.20 Associating Routing Rulesets to Your Configuration
Top

2.19.1 Call Agent Rulesets

wan_ip_trunk_ca Call Agent.
Top

2.20 Associating Routing Rulesets to Your Configuration

Before You Start
Importing Rulesets must be completed for Routing Rulesets to be available.
Steps
  1. Go to SBC/Configuration
  2. In the Routing Rulesets table, from the Name selection list, select the Routing Ruleset you wish to apply to the configuration.

    Note

    Refer to the Routing Rulesets section to identify the Rulesets that apply to this Use Case.

  3. If necessary, in the Parameters field enter the required parameters.
  4. Click .
  5. Repeat steps 2 and 3 for each Routing Ruleset you wish to associate to your configuration.
  6. Click Save.
  7. Click Apply to apply all changes to the configuration.
Result

Next Step

2.21 Configuring the IP PBX
Top

2.20.1 Routing Rulesets

  • wan_ip_trunk_to_lan_pbx
If the Mediatrix SBC Registers to the Service Provider
Select the Ruleset according to the service provider that requires registration.
  • registration_to_wan_ip_trunk
Top

2.21 Configuring the IP PBX

Context
The IP PBX server is configured with the IP address and port of the Mediatrix SBC lan1_s Signaling Interface. The Mediatrix unit must be configured in the PBX as a SIP Trunk.
Steps
  1. Configure the PSTN phone number(s) to be forwarded to the PBX's IVR.

Next Step

2.22 Configuring Your Main Office Phones
Top

2.22 Configuring Your Main Office Phones

Steps
  1. Set the SIP server, username and password according to the IP PBX configuration.

    Note

    These phones do not use the Mediatrix unit to communicate with the PBX.

  2. Make a call from the PSTN to the Lan.
  3. Make a call from the Lan to the PSTN.
Result
The call signal should be routed from the PSTN to the Lan, and vice-versa. At this point, the configuration of this use case is completed. Under SBC/Registration, in the Registration Cache table, a value should be displayed in the AoR field.
Top

3 Available Documentation

For more details, refer to the Mediatrix Documentation .
Top

4 Copyright Notice

Copyright © 2018 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.

Top