Mediatrix Sentinel and Mediatrix 3000 v. 43.3.1398 2018-12-13
Table of Contents Table of Contents Information to Know Before Starting 4 Remote Users - Mediatrix SBC Located on the Edge 5 Getting Started 5 Logging on to the Mediatrix Unit Web Interface 6 Configuring the Lan1 Network Interface 7 Associating the Lan1 Network Interface to the System Management Services 8 Adding Local Firewall Rules 9 Configuring the Uplink Network Interface 12 Configuring the Default Network Gateway to a Static IP Address 13 Configuring the Domain Name Server (DNS) 13 Configuring the SNTP Server 14 Configuring the uplink_s Signaling Interface 15 Configuring the lan1_s Signaling Interface 16 Configuring the uplink_m Media Interface 17 Configuring the lan1_m Media Interface 18 Configuring the remote_users_ca Call Agent 19 Configuring the lan_ip_pbx_ca Call Agent 20 Importing Rulesets 21 Associating Call Agent Rulesets to a Call Agent 22 Associating Routing Rulesets to Your Configuration 23 Configuring Your Mobile/Remote Phones 24 Configuring Your Main Office Phones 24 Available Documentation 26
Table of Contents Copyright Notice 27
4 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 the mouse pointer 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 Use this value 192.168.0.10 Mediatrix unit to communicate with the Management Interface. Logging on to the Mediatrix Unit Web Interface (p. 6) 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 If your Mediatrix unit is configured to use a DHCP server, use the DHCP serverprovided IP address. Logging on to the Mediatrix Unit Web Interface (p. 6) Wan IP address as defined in your network address range. Configuring the Uplink Network Interface (p. 12) LAN IP address as defined in your network address range Configuring the Lan1 Network Interface (p. 7) IP address of the IP PBX Configuring the lan_ip_pbx_ca Call Agent (p. 20) Public address or FQDN of the main office Configuring Your Mobile/Remote Phones (p. 24)
5 Remote Users - Mediatrix SBC Located on the Edge This use case describes the configuration of remote users when the Mediatrix unit is located on the Edge. When the Mediatrix unit is located on the Edge, it implies that: The remote users are using SIP endpoints on the public Internet or behind a NAT on the public Internet. The SIP endpoints register on a PBX located in the LAN of the office, using the Mediatrix unit as an outbound proxy. The Mediatrix unit generates enough traffic from the SIP endpoints to maintain the firewall open. The Mediatrix unit is located on the Edge of the internet with one interface in the LAN and one on the Internet. Getting Started 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.
6 Note: If you are using your Mediatrix unit for the first time, refer to its Mediatrix unit Quick Start guide. Logging on to the Mediatrix Unit Web Interface (p. 6) Logging on to the Mediatrix Unit Web Interface Information 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. 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.
7 The Information page of the Web interface is displayed. Configuring the Lan1 Network Interface (p. 7) Configuring the Lan1 Network Interface 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. 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. Associating the Lan1 Network Interface to the System Management Services (p. 8)
8 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 Associating the Lan1 Network Interface to the System Management Services Before you start Configuring the Lan1 Network Interface (p. 7) must be completed. 1) Go to Management/Misc. 2) From the Network Interface selection list, select Lan1. 3) Click Apply. The user will access the System Management through the Lan1 Network Interface.
Adding Local Firewall Rules (p. 9) Adding Local Firewall Rules Before you start You must have a Network Interface created. 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. 9
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 +. 10
11 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. 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)
12 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) Setting the Uplink Network Interface to a Static Address Configuring the Uplink Network Interface 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.
13 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. Configuring the Default Network Gateway to a Static IP Address 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. Configuring the Domain Name Server (DNS) (p. 13) Configuring the Domain Name Server (DNS) 1) 2) 3) 4) Go to Network/Host. In the DNS Configuration table, form the Configuration Source selection list, select Static. For each DNS used, enter the IP address of the DNS. Click Apply.
14 Configuring the SNTP Server (p. 14) Configuring the SNTP Server Before you start Make sure there is an SNTP server available. 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. The SNTP host name and port will be displayed in the Host Status table under Network/Status.
15 Configuring the uplink_s Signaling Interface (p. 15) Configuring the uplink_s Signaling Interface 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. The Signaling Interface will be available when configuring a Call Agent, in the Configure Call Agent page in the Signaling Interface selection list.
16 Configuring the lan1_s Signaling Interface (p. 16) 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. 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. The Signaling Interface will be available when configuring a Call Agent, in the Configure Call Agent page in the Signaling Interface selection list.
17 Configuring the uplink_m Media Interface (p. 17) Configuring the uplink_m Media Interface 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. The Media Interface will be available when configuring a call agent, in the Configure Call Agent page, in the Media Interface selection list.
18 Configuring the lan1_m Media Interface (p. 18) 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. 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. The Media Interface will be available when configuring a call agent, in the Configure Call Agent page in the Media Interface selection list.
19 Configuring the remote_users_ca Call Agent (p. 19) Configuring the remote_users_ca Call Agent 1) Go to SBC/Configuration. 2) In the Call Agent Configuration table, click located on the same row as remote_users_ca. 3) In the Configure Call Agent table, complete the following fields: a) Select the Enable check box. b) From the Signaling Interface selection list, select uplink_s. c) From the Media Interface selection list, select uplink_m. d) Set the Peer Network to 0.0.0.0/0. 4) Click Save. 5) In the Configuration page, click Save. 6) Click Apply to apply all changes to the configuration. 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 unit will use the selected Call Agent for a communication, the selected parameters will be applied.
20 Configuring the lan_ip_pbx_ca Call Agent (p. 20) Configuring the lan_ip_pbx_ca Call Agent 1) Go to SBC/Configuration. 2) In the Call Agent Configuration table, click located on the same row as lan_ip_pbx_ca. 3) In the Configure Call Agent table, complete the fields as follows: a) Select the Enable check box. b) From the Signaling Interface selection list, select lan1_s. c) From the Media Interface selection list, select lan1_m. d) Set the Peer Host to the IP address of the IP PBX. 4) Click Save. 5) In the Configuration page, click Save. 6) Click Apply to apply all changes to the configuration. 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 unit will use the selected Call Agent for a communication, the selected parameters will be applied.
21 Importing Rulesets (p. 21) 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). Information This procedure is valid for Call Agent and Routing Rulesets. 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. 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.
22 Associating Call Agent Rulesets to a Call Agent (p. 22) Associating Call Agent Rulesets to a Call Agent Before you start The Call Agents must be configured. Importing Rulesets (p. 21) must be completed. 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 to which you wish to associate a Ruleset. 3) In the Call Agent Rulesets table, click. located on the same row as the Call Agent 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. Associating Routing Rulesets to Your Configuration (p. 23)
23 Call Agent Rulesets remote_users_ca Call Agent Note: Make sure to associate the Rulesets in the order they are listed. 1. 2. 3. 4. 5. 6. 7. 8. drop_common_scanners_in registration_throttling_in reject_unregistered_users_in rate_limit_register_per_source_in rate_limit_invite_per_source_in remote_users_behind_nat automatic_media_relay topology_hiding_out Associating Routing Rulesets to Your Configuration Before you start Importing Rulesets (p. 21) must be completed for Routing Rulesets to be available. 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.
Configuring Your Mobile/Remote Phones (p. 24) Routing Rulesets Note: Make sure to associate the Rulesets in the order they are listed. 1. lan_pbx_to_remote_users 2. remote_users_to_lan_pbx Configuring Your Mobile/Remote Phones Information These phones are registered to the IP PBX using the Mediatrix unit as an outbound proxy. 1) Set the SIP server to the (private) IP address of the IP PBX in the main office. 2) Set the outbound proxy to the public IP address or FQDN of the main office. 3) Set the username and password according to the IP PBX configuration. Configuring Your Main Office Phones (p. 24) Configuring Your Main Office Phones 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. 24
25 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.
Available Documentation For more details, refer to the Mediatrix Documentation. 26
27 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.