This document outlines the configuration steps to set up Mediatrix 41xx series FXS gateways with the Asterisk open-source telephone system. It assumes that you have an Asterisk server properly installed with the necessary modules. If you need technical assistance to configure your Asterisk server, the Mediatrix technical team can provide appropriate support to help you realizing your VoIP projects.
The Mediatrix® 41xx Series products are high-quality and cost-efficient VoIP gateways connecting larger branch offices and multi-tenant buildings to an IP network, while preserving investment in analog telephones and faxes.
The Mediatrix® 41xx access devices allow Service Providers to deploy rapidly and economically their solutions in medium-size premises and they are the ideal solution for branch office connectivity to larger private networks. The following Mediatrix 41xx models are available:
Benefits of using the Mediatrix 41xx over other Asterisk FXS solutions:
This is a typical deployment scenario of Mediatrix 41xx units in a SIP-based MTU/MDU environment. The units provide connectivity to analog phones and fax machines and analog trunking to legacy PBX/KSU (for small business) in each building floor, whereas the Asterisk IP PBX provides call control and telephony services for all gateways.
The Asterisk IP PBX – provides:
The following features are supported by both Asterisk and Mediatrix 41xx:
This configuration note was written and validated using the following platforms and versions.
The following configuration notes are not a substitute for the Mediatrix Administration Documentation for Mediatrix 41xx products. Please have the following manuals available for reference:
The following sections describe special configuration you must perform in Asterisk in order to properly work with the Mediatrix 41xx. The configuration parameters are located in various configuration files.
Creating an Extension
In Asterisk, an extension is the equivalent of the SIP user in the Mediatrix 41xx. 1. In the /etc/asterisk/sip.conf file, scroll to the bottom of the file and add the following:
2. In the /etc/asterisk/extensions.conf file, add the following:
3. Execute the following command on the server to reload the configuration:
asterisk -rx "reload"
The following sections describe special configuration you must perform in the Mediatrix 41xx in order to properly work with Asterisk.
All models in the Mediatrix 41xx series feature an embedded Web server. Most of the commonly used parameters are accessible from the web interface. The Mediatrix Unit Manager Network (UMN) software is needed if access to full unit configuration is required. The UMN can be downloaded from Unit Manage Network
It has a default 3-units limit upon installation. This will suffice for most configurations. Additional unit license can be purchased. Please contact your Mediatrix reseller for more details.
Using the Web interface
The web interface may be used to:
Mediatrix recommends that you use the latest version of the Microsoft® Internet Explorer web browser to properly access the web interface. To use the web interface configuration:
1. In the web browser’s address field, type the IP address of the Mediatrix 41xx (if you have performed a recovery mode, this is 192.168.0.1). The unit’s IP address can be found by dialing *#*0 from a phone connected to port 2 or above.
Page 7 of 17 2. Enter the default login name admin and password 1234.
3. The system information screen then appears, giving information about the firmware version, hardware revision, system up-time and MAC address.
Network Parameters Configuration
Network parameters are located in the Management. / Network Settings page.
1. Click Management and Network Settings to go the Network Settings web page.
2. In the IP Address Source option, select DHCP or Static.
DHCP is the default selection.
3. If you are using a Static IP address, select Static and enter the IP address, subnet mask, default router and DNS server IP in the proper fields.
4. If SNTP is required, set the SNTP Enable option to Enable and enter the appropriate SNTP server IP address in the SNTP Host field.
5. Click Submit to apply the changes.
In Asterisk, an extension is the equivalent of the SIP user in the Mediatrix 41xx. You must match the extension you have created in Asterisk in section Creating an Extension on page 5.
1. Click SIP and Configuration to go the SIP Configuration web page.
2. Choose Static as the SIP Server Source
3. In the Registrar Host and Proxy Host fields, enter the address of the PC that hosts Asterisk.
4. In the User Name (equivalent to the phone number) column, enter a user name as defined in Asterisk.
5. You can also enter a Friendly Name for each port.
6. Click Submit to apply the changes.
The next step is to enter SIP authentication information for each port.
1. Click SIP and Authentication to go to the SIP Authentication web page.
You can enter up to 5 credentials for each port, but only one is needed in most cases.
2. Type asterisk in the Realm field.
3. Enter the Username 101 and Password num101 for port 1.
4. Click Submit to save the changes.
Codec and DTMF Configuration
1. Click Telephony and Codec to go to the Codec page.
Codec and DTMF settings are configured on a port-by-port basis.
2. Set the DTMF Transport drop-down menu according to the DTMF transport mode you have defined in Asterisk.
In this case, OutOfBandUsingRTP is used
3. Set the Payload Type field to 101.
4. G.711 PCMU is the default codec.
5. Disable G.711 VAD (aka Silence Suppression):
You must turn off the Silence Suppression feature in the Mediatrix 41xx according to this Asterisk website: http://www.voip-info.org/wiki/index.php?page=Asterisk+config+sip.conf ,
Asterisk uses the incoming RTP Stream as a timing source for sending its outgoing Stream.
If the incoming stream is interrupted due to silence suppression then musiconhold will be choppy. So
in conclusion, you cannot use silence suppression. Make sure ALL SIP phones have disabled
silence suppression. There is a solution for the silence suppression problem, see bug 5374 for details
6. Disable G711 Comfort Noise.
7. Enable (default) / Disable T.38 Fax if you are not using it in your VoIP setup.
8. Click Submit to apply the changes.
Reboot the gateway.
1. Click Advanced and Reboot to go to the Reboot page.
2. Click the Reboot button on the page that displays.
The changes you just made will become effective after the unit reboots.
After the unit comes back, observe that the Ready LED should now light up (or blink if not all the ports are configured and registered with the SIP server). You can then hook up a telephone and make some test calls with the Mediatrix 41xx.
* Star Code and # Key Dial Map
By default, the Mediatrix 41xx dial map does not allow * and # keys. To do that, you must add the following dial map:
Here the first dial map is (*xx|#xx). The second dial map is x.# with # removed before the number is sent to Asterisk.
Call Transfer SIP Interop Setting for Asterisk 1.4
The SIP behaviour of Asterisk in the Call transfer scenario in version 1.4 is different than in previous Asterisk versions. The following MIB on the Mediatrix 41xx must be changed. To access this MIB parameter, the Mediatrix Unit Manager Network (UMN) is required. UMN can be downloaded from the Mediatrix Download Portal:
The MIB parameter is: mediatrix.mediatrixExperimental.sipInteropMIB.sipInteropReplacesConfig. This MIB has to be set to useReplacesNoRequire. The default value is “useReplacesWithRequire”:
From version 1.4, Asterisk supports the negotiation and passthrough of T.38.
1. Modify the /etc/asterisk/udptl.conf configuration file so that it is as follow :
T38FaxUdpEC = t38UDPRedundancy
T38FaxRateManagement = transferredTCF
T38FaxMaxDatagram = 400
udptlfecentries = 3
udptlfecspan = 3
2. Add the t38_udptl=yes to the “general” section of the /etc/asterisk/sip.conf
You can also add it to the SIP users and trunks supporting T.38:
By default, Asterisk supports speeds up to 9600. Mediatrix units are able to achieve speeds of up to 14400. To enable higher speeds, Asterisk needs to be recompiled. The following web page explains the procedure to enable higher speeds:
Depending on the Asterisk version, re-INVITEs sent by the Mediatrix units to switch to T.38 might conflict with re- INVITEs sent by the server. This happens especially when the “canreinvite” parameter is set to yes on the SIP user. If you experience problems with re- INVITEs, it is recommended to disable the dataIfCngToneDetection variable using Unit Manager Network.
Syslog Server for Troubleshooting
For troubleshooting purpose, syslog of various levels can be enabled on the Mediatrix 41xx. In this example, Syslog messages are sent to the syslog server at 192.168.1.100, the syslog level is set to Debug.