Mediatrix 1104 Quick start guide

C
CC
C
C
CC
Co
oo
o
o
oo
on
nn
n
n
nn
nf
ff
f
f
ff
fi
ii
i
i
ii
ig
gg
g
g
gg
gu
uu
u
u
uu
ur
rr
r
r
rr
ra
aa
a
a
aa
at
tt
t
t
tt
ti
ii
i
i
ii
io
oo
o
o
oo
on
nn
n
n
nn
n N
NN
N
N
NN
No
oo
o
o
oo
ot
tt
t
t
tt
te
ee
e
e
ee
es
ss
s
s
ss
s 2
22
2
2
22
23
33
3
3
33
30
00
0
0
00
0
PBX Remote Line Extension using Mediatrix 1104 and
1204
February 21, 2006
Proprietary
2006 Mediatrix Telecom, Inc.

Configuration Notes
0230
Page 2 of 23
Table of Contents
Introduction ........................................................................................................................................................................... 3
Application Scenario............................................................................................................................................................. 3
Running the Unit Manager Network Software....................................................................................................................... 4
Configuring the Mediatrix 1104............................................................................................................................................. 7
Configuring the Mediatrix 1204........................................................................................................................................... 12
Appendix A – Troubleshooting Tips.................................................................................................................................... 23

Configuration Notes
0230
Page 3 of 23
Introduction
These Configuration Notes are distributed to partners and technical support personnel as an aid to configure units in a PBX
Remote Line Extension scenario. They are specific to the SIP v5.0 firmware.
Application Scenario
With VoIP, the distance limitation of extending copper wire from a PBX to a remote location is no longer an issue.
Small remote branch offices (SOHOs) can now have existing analog phones installed at the remote site as analog
extensions of the PBX system at the Main Office.
Requirement for fax at remote branch office.
Requirement for analog phone at remote branch office.
Toll-Bypass for intra-office calls.
The following configuration notes are not a substitute for the Mediatrix Administration Documentation for Mediatrix analog
products. Please have the following manuals available for reference:
Mediatrix 1104 SIP Reference Manual (SIP v5.0 version).
Mediatrix 1204 SIP Reference Manual (SIP v5.0 version).
Mediatrix Unit Manager Network Administration Manual and Quick Start guide (UMN v3.2).

Configuration Notes
0230
Page 4 of 23
Running the Unit Manager Network Software
The Unit Manager Network (UMN) software is a configuration and management tool for Mediatrix devices. The UMN is
provided on the CD included with the unit. It has a default 3-units limit upon installation. This will suffice for most
configurations.
It is recommended that the administrator uses the UMN to configure the Mediatrix devices. Please refer to the UMN Quick
Start guide for the installation of the software. Once the UMN software has been installed on your PC
1
, proceed with the
following steps.
Step 1: Start the UMN
Select from the Start Menu > Programs > Unit Manager Network 3.2 > Unit Manager Network.
Step 2: Login to the UMN
In the Administrator login window (Connect to Unit Manager), a User Name and Password are not required. Click
OK to proceed.
Step 3: Perform an Autodetect
On the left pane, right-click the Unit Manager level, then select Autodetect.
Set the IP Address Range to minimize the time it takes to auto-detect the unit. Click Start to begin Mediatrix unit
detection. When the unit is detected, the Result section lists the unit.
Select the unit and click OK. If no DHCP server is used in your subnet, you must connect one unit at a time since
they will start by using the default IP address 192.168.0.1 after a recovery reset. You will have to set a different
static IP address for every unit. Please see the 1100 series and 1204 SIP Quick Start Guide for more details on
initial setup.
1
If you are having trouble opening the UMN application, verify that the status of the “Unit Manager Network 3.2” service is started. See Page
5 to access Windows Services.

Configuration Notes
0230
Page 5 of 23
Note: The UMN runs in the Windows background. Mediatrix highly recommends that the administrator stops and restarts the
UMN service whenever the IP address of the PC is changed. A restart may be needed depending on your Windows O/S.
Go to Start Menu > Settings > Control Panel > Administrative Tools > Services.
Stop and restart the Unit Manager Network 3.2 service.

Configuration Notes
0230
Page 6 of 23
Alternatively, you can configure multiple IP addresses on the same PC network interface card (only in static IP
mode – not DHCP) to avoid restarting the computer or stopping and restarting the UMN service whenever you
change the IP address and subnet of the Mediatrix unit. This is recommended for advanced IP network users, the
current configuration notes do not cover the step by step setting for this alternative.

Configuration Notes
0230
Page 7 of 23
Configuring the Mediatrix 1104
Step 1: Setting Basic Network Parameters
Once the Mediatrix 1104 has been auto-detected, it should appear under the Unit Manager level. Right-click the
Administration level of the Mediatrix 1104 and select the Edit menu.
Configure the IP addresses to reflect your network. Uncheck Use DHCP if you are using static IP addresses.
Restart the unit after the configuration of IP addresses for the unit to accept the new addresses.
When using DHCP: you can also reserve the IP address for the Mediatrix 1104 by assigning the MAC address of
the unit to a specific IP address in your DHCP server – it will be easier to auto-detect the unit for provisioning. An
example of a unit IP address fetched by DHCP is shown in the figure below.
Another alternative to determine the IP address of the unit fetched by DHCP is to connect a telephone into port #2
of the Mediatrix 1104 and dial *#*0”. An internal IVR will provide the IP address of the unit.

Configuration Notes
0230
Page 8 of 23
Step 2: Set the SIP Server Redirection
Select the Sip page and set the following:
oUncheck Use DHCP.
oSet the SIP Registrar field to empty since registration will not be required.
oSet the SIP Proxy field to be the IP address of the destination2 device. In this scenario, the destination IP
address is that of the Mediatrix 1204.
oClick in the User Name field next to the port number and type the telephone, fax, or extension number of
the Mediatrix 1104 port. Each port on the 1104 requires a User Name.
2
Using this setup will route all calls from the Mediatrix 1104 to the assigned IP address, that is our Mediatrix 1204. Note that you cannot use
this configuration to route calls to more than one unit.

Configuration Notes
0230
Page 9 of 23
Step 3: Access the Edit SNMP Window
Right-click the unit and select Edit SNMP.
Step 4: Set the Port Behaviour
On the top menu bar, check the option Automatic GET.
Go to iso>org>dod>internet>private>enterprises>mediatrix > mediatrixExperimental > sipExperimentalMIB >
sipExperimentalMIBObjects > sipUnregisteredPortBehavior and set this parameter to enableport in the drop
down menu that appears upon double-clicking the value located in the upper-right pane.

Configuration Notes
0230
Page 10 of 23
Step 5: NAT Traversal Configuration
You must configure the following parameters for the Mediatrix unit to work behind a NAT/Firewall router:
oGo to mediatrix > mediatrixExperimental > sipExperimentalMIB > sipExperimentalMIBObjects >
sipNatCustom > sipNatCustomEnable and set this parameter to enable.
oGo to mediatrix > mediatrixExperimental > sipExperimentalMIB > sipExperimentalMIBObjects >
sipNatCustom > sipNatCustomPublicAddress and set the parameter to be the public IP address of the
NAT/Firewall router where the Mediatrix 1104 is located. In this scenario, the IP address would be
69.129.134.6 as shown in the following figure.

Configuration Notes
0230
Page 11 of 23
Step 6: Configure Traffic Routing to the Mediatrix Unit
To allow traffic from the NAT/Firewall router to be routed to the Mediatrix unit, there are two alternatives:
oOption1 – Configure the NAT/Firewall router’s DMZ (demilitarized zone) to include the Mediatrix unit.
Please refer to the documentation provided with your NAT/Firewall router for configuration details.
oOption 2 – Enable the port forwarding on the NAT/Firewall router. The following ports should be forwarded
to the IP address of the Mediatrix unit behind the NAT/Firewall:
UDP 5060 for SIP Signaling
UDP 5004 to 5010 for Voice RTP streams
UDP 161 (optional for management of unit via UMN-SNMP)
Step 7: Configure the Hook Flash Relay
If your PBX uses the Hook Flash feature, you must configure both the Mediatrix 1104 and Mediatrix 1204 so that they can
properly exchange the Hook Flash events. See also the Mediatrix 1204 configuration.
Go to mediatrix > mediatrixConfig > telephonyAttributesMIB > telephonyAttributesMIBObjects >
telephonyAttributesIfFeaturesTable > telephonyAttributesIfFeaturesEntry >
telephonyAttributesHookFlashProcessing and set this parameter to outOfBandUsingRtp.
The Mediatrix 1104 will relay hook-flash events to the Mediatrix 1204 as telephone-event 16 via an RFC 2833 RTP
packet.

Configuration Notes
0230
Page 12 of 23
Configuring the Mediatrix 1204
Step 1: Autodetect the Mediatrix 1204
Autodetect the Mediatrix 1204 after a recovery reset (in a recovery reset, the unit restarts with the address
192.168.0.1) and configure the IP addresses to reflect your network parameters.
Uncheck Use DHCP if you are using static IP addresses. An example is shown in the following figure.
Restart the unit after the configuration of IP addresses for the unit to accept the new addresses.
When using DHCP, you can reserve the IP address for the Mediatrix 1204 by assigning the MAC address of the
unit to a specific IP address in your DHCP server – it will be easier to auto-detect the unit for provisioning.

Configuration Notes
0230
Page 13 of 23
Step 2: Configure SIP Parameters
Select the Sip page of the 1204 and set the following:
oUncheck Use DHCP.
oSet the SIP Proxy field to be the IP address of the destination devices, the Mediatrix 1104 IP address in this
case.
oUse default values for the other entries.

Configuration Notes
0230
Page 14 of 23
Step 3: Configure Incoming Calls from PSTN Behaviour
The Mediatrix 1204 exhibits two possible behaviours when an incoming call from the PSTN is received:
oThe Mediatrix 1204 goes off-hook and produces a second dial tone from which the PSTN user can dial a
number in IP.
oThe Mediatrix 1204 redirects the call to a specific SIP endpoint upon off-hook. For the purpose of this
application, the second behaviour is required. The goal is to tie the PBX analog extension to a specific FXS
point located remotely in the IP network.
Select the Telephony Attributes page and set the following:
oEnable Automatic call on all ports.
oSet an Automatic call address for each port.

Configuration Notes
0230
Page 15 of 23
Step 4: NAT Traversal Configuration
You must configure the following parameters for the Mediatrix unit to work behind a NAT/Firewall router:
oGo to mediatrix > mediatrixExperimental > sipExperimentalMIB > sipExperimentalMIBObjects >
sipNatCustom > sipNatCustomEnable and set this parameter to enable.
oGo to mediatrix > mediatrixExperimental > sipExperimentalMIB > sipExperimentalMIBObjects >
sipNatCustom > sipNatCustomPublicAddress and set the parameter to be the public IP address of the
NAT/Firewall router where the 1204 is located.

Configuration Notes
0230
Page 16 of 23
Step 5: Configure Traffic Routing to the Mediatrix Unit
To allow traffic from the NAT/Firewall router to be routed to the Mediatrix unit, there are two alternatives:
oOption1 – Configure the NAT/Firewall router’s DMZ (demilitarized zone) to include the Mediatrix unit.
Please refer to the documentation provided with your NAT/Firewall router for configuration details.
oOption 2 – Enable the port forwarding on the NAT/Firewall router. The following ports should be forwarded
to the IP address of the Mediatrix unit behind the NAT/Firewall:
UDP 5060 for SIP Signaling
UDP 5004 to 5010 for Voice RTP streams
UDP 161 (optional for management of unit via UMN-SNMP)
Step 6: Configure Dial Tone Detection
The FXO dial tone detection mechanim allows the Mediatrix 1204 to wait for a dial tone on the PSTN side before initiating
the dialing sequence. If no dial tone is detected, the line is considered busy with an incoming PSTN call. This mechanism
helps to avoid collisions between incoming and outgoing calls.
Under Edit SNMP, go to mediatrix > mediatrixConfig > fxoMIB > fxoMIBObjects > fxoLinePropertiesCustomization
>fxoDialtoneDetectionMode and set this parameter to countryTone.
Note: Certain PBX manufacturers do not produce the country dial tone on the extension line. If this is the case, make sure
that the dial tone detection is disabled, otherwise the Mediatrix 1204 will not output dialed digits.

Configuration Notes
0230
Page 17 of 23
Step 7: Configure the Answering Delay
Under Edit SNMP, go to mediatrix > mediatrixConfig > fxoMIB > fxoMIBObjects > fxoIfAnsweringDelayTable.
The parameter fxoAnsweronCallerIdDetection allows the Mediatrix 1204 to go off-hook upon caller ID detection
during the ringing of the PBX extension.
Note: If the PBX does not pass the caller ID to the Mediatrix 1204, you can reduce the <fxoPreAnswerDelay = 1000> to
reduce the time before the Mediatrix 1204 goes off-hook upon ring detection.

Configuration Notes
0230
Page 18 of 23
Step 8: Configure the Line Selection Parameters (Port-to-Port Mapping)
Under Edit SNMP, go to mediatrix > mediatrixConfig > lineSelectionMIB > lineSelectionMIBObjects >
lineSelectionIfCustomizationTable:
oSet the lineSelectionEnable variable to enable.
oSet the lineSelectionDigitMap variable to the number corresponding to the Mediatrix 1104 FXS user name.
This feature enables the port-to-port mapping between the Mediatrix 1104 and Mediatrix 1204. Each port of the
Mediatrix 1204 corresponds to a specific port of the Mediatrix 1104.

Configuration Notes
0230
Page 19 of 23
Step 9: Configure the Far End Disconnect Parameters
Far end disconnect refers to methods for detecting that a remote party has hung up. The far end disconnect signal is not
mandatory in Loop Start and this could create problems. The lack of a far end disconnect signal in Loop Start lines is one of
the main reasons why the Ground Start lines were created.
If the far end disconnect signal is not sent to or properly detected by the Mediatrix 1204, the connection will not be released
by the unit, thus freezing the FXO port in the off hook state.
Under Edit SNMP, go to mediatrix > mediatrixConfig > fxoMIB > fxoMIBObjects >
fxoForcedEndOfCallCustomization.
Set the fxoFeocOnToneDetectionMode variable to customTone.

Configuration Notes
0230
Page 20 of 23
Set the frequency that the Mediatrix 1204 needs to detect for far end disconnect. This frequency is typically the
dial tone frequency (350 Hz for North America) but will vary from one PBX to another. Please verify with your
PBX vendor to determine what tone (exact frequency and cadence) the PBX produces on the extension
when the far end is disconnected.
Set the fxoEndOfCallToneCustomFrequency variable to 350 Hz.
Set the cadence and repetition required with the fxoEndOfCallToneCustomCadence and
fxoEndOfCallToneCustomRepetition variables.