Media5 mediatrix 4104 Reference Manual
  1. Manuals
  2. Brands
  3. Media5 Manuals
  4. Adapter
  5. Mediatrix 4104
  6. Reference manual

Media5 mediatrix 4104 Reference Manual

Hide thumbs Also See for mediatrix 4104:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
Table of Contents

Advertisement

Quick Links

See also: Installation Manual
Discover the Power of
5
Reference Manual
®
Mediatrix
4104
SIP Version
Product Version 5.0
Document Revision 17
July 30, 2012
Pb
RoHS
COMPLIANT
2002/95/EC

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the mediatrix 4104 and is the answer not in the manual?

Questions and answers

Related Manuals for Media5 mediatrix 4104

Summary of Contents for Media5 mediatrix 4104

  • Page 1 Discover the Power of Reference Manual ® Mediatrix 4104 SIP Version Product Version 5.0 Document Revision 17 July 30, 2012 RoHS COMPLIANT 2002/95/EC...
  • Page 2 – without the express written permission of the publisher. 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.

  • Page 3: Table Of Contents

    Free Standing Unit ..............................9 Condensation ................................9 Cleaning ..................................9 Hardware Connection ..........................10 Reserving an IP Address............................10 Before Proceeding..............................10 Installing the Mediatrix 4104............................11 Starting the Mediatrix 4104 for the First Time.....................12 IP Address Discovery or Configuration ........................12 Mediatrix 4104...
  • Page 4 Chapter 2 Web Interface – Introduction.................... 23 Introduction ..............................23 Using the Web Interface ..........................23 Web Interface Access Limitation ..........................23 System Status of the Mediatrix 4104......................... 25 Menu Frame ................................25 Content Frame ................................26 Submitting Changes ...........................26 Syslog Monitoring ............................27 Configuring the Syslog Daemon Application ......................
  • Page 5 Fax Parameters ................................. 85 Call Forward ...............................89 On Busy..................................89 On No Answer ................................91 Unconditional................................92 Services ..............................94 Call Transfer................................94 Call Waiting ................................95 Conference................................98 Call Hold.................................. 100 Second Call ................................101 Automatic Call ................................. 101 Mediatrix 4104...
  • Page 6 Variables for Administrative Commands ......................... 137 SNMP Access Limitation ..........................138 SNMP Service Agent ..........................138 Current MIB Version ..........................138 Sending Configuration Data to the Mediatrix 4104 ...................139 Configuration File ..............................139 Management Information Base – MIB ........................139 Chapter 8 IP Address and Network Configuration ................ 141 IP Addresses ............................141...
  • Page 7 Configuration Source............................... 169 Chapter 10 DNS SRV Configuration....................171 What is a DNS SRV?..........................171 Priority vs Weight ..............................171 DNS SRV Call Flow..............................172 Enabling DNS SRV on the Mediatrix 4104 ....................172 DNS SRV Record Lock..........................173 DNS SRV-Oriented Settings........................173 Mediatrix 4104...
  • Page 8 DHCP Configuration..............................207 Static Configuration ..............................208 Download Procedure ..........................209 Extracting the Zip File.............................. 209 Setting up the Image Path............................209 Software Download Status ............................211 Download via TFTP..............................213 Download via HTTP/HTTPS............................ 214 Automatic Software Update............................. 215 viii Mediatrix 4104...
  • Page 9 DTMF Detection Configuration ..........................239 Adaptative Jitter Buffer ..........................241 About Changing Jitter Buffer Values ........................241 Voice Activity Detection ..........................242 G.711 and G.726 VAD ............................242 G.729 VAD ................................242 Echo Cancellation.............................243 Signal Limiter................................243 Comfort Noise............................244 User Gain..............................244 Mediatrix 4104...
  • Page 10 Line-Specific Authentication ............................ 260 Unit Authentication ..............................261 Authentication Request Protection .......................... 261 SIP Trusted Sources..........................262 NAT Traversal............................262 Mediatrix 4104 Configuration ..........................263 NAT System Configuration............................263 SIP Transport Type...........................263 Transport Parameter ............................... 264 UDP Source Port Behaviour............................ 264 SIP Penalty Box............................265 Penalty Box vs Transport Types ..........................
  • Page 11 UDP Checksum ............................284 Chapter 19 STUN Configuration ......................285 What is STUN? ............................285 SIP Outbound Proxy..............................285 Restrictions on the Media5 STUN Implementation ....................285 STUN Client Configuration ........................286 Chapter 20 SNTP Settings........................287 Enabling the SNTP Client .........................287 Configuration Source ..........................288 DHCP Configuration..............................
  • Page 12 Call Transfer .............................315 Blind Transfer ................................315 Attended Transfer..............................316 Conference Call ............................317 Requirements ................................317 Enabling the Conference Call Feature ........................318 Managing a Conference Call........................... 319 Chapter 24 Telephony Attributes ...................... 321 Automatic Call............................321 Call Direction Restriction ..........................322 Mediatrix 4104...
  • Page 13 MWI Method #2 ............................... 331 MWI Notify Service ...........................331 How does the Service Work? ..........................331 Configuring the IP Communication Server ......................332 Configuring the Mediatrix 4104 ..........................332 Chapter 26 Management Server Configuration................333 Using the Management Server .........................333 Configuration Source...............................
  • Page 14 Contents Statistics by Syslog ..............................346 Example .................................. 347 Chapter 30 Maximum Transmission Unit (MTU) ................349 What is MTU? ............................349 Mediatrix 4104 MTU ..........................349 Possible Hardware Problem ........................349 Chapter 31 Troubleshooting ......................351 General Operation Issues.........................351 Calling Issues ............................354 Fax Issues ...............................355...
  • Page 15 Austria 2 .................................. 389 Brazil.................................390 Chile................................391 Chile 1 ..................................391 Chile 2 ..................................392 China ................................393 Czech Republic............................394 Denmark ..............................395 France...............................396 Germany ..............................397 Germany 1................................397 Germany 2................................398 Germany 3................................398 Hong Kong..............................399 Indonesia ..............................400 Israel .................................401 Mediatrix 4104...
  • Page 16 North America 2 ..............................409 Russia...............................410 South Africa ..............................411 Spain.................................412 Sweden..............................413 Switzerland ...............................414 Thailand ..............................415 United Arab Emirates..........................416 UK................................416 Appendix E Glossary ........................... 417 Appendix F List of Acronyms ......................425 Appendix G List of MIB Parameters ....................427 Mediatrix 4104...

  • Page 17: Preface

    From the perspective of the LAN administrator, a Mediatrix 4104 presents itself like another device to add to the LAN. It requires the same kind of TCP/IP addressing. The Mediatrix 4104 can also use a DHCP server on the LAN to automatically receive its IP configuration assignment.

  • Page 18: Document Structure

     “Installation and Web Page Configuration” on page 1. This part describes various installation of the Mediatrix 4104 and how to configure the unit via its web interface.  “SNMP Configuration” on page 123. This part describes all SNMP-related parameters of the Mediatrix 4104.
  • Page 19 “Chapter 24 - Telephony Attributes” on page 321 Describes the telephony attributes available on the Mediatrix 4104. “Chapter 25 - Message Waiting Indicator” on Explains how to set the Mediatrix 4104 to use the page 329 Message Waiting Indicator service. “Chapter 26 - Management Server Describes how to configure the Mediatrix 4104 to Configuration”...

  • Page 20: Document Conventions

    Lists the various parameters specific to a country such page 383 as loss plan, tones and rings, etc. Document Conventions The following information provides an explanation of the symbols that appear on the Mediatrix 4104 and in the documentation for the product. Warning Definition Warning: Means danger.

  • Page 21: Scn Vs Pstn

    These sections explain how to obtain documentation from Media5. Media5 Web Site Media5 offers the latest version of its products’ documentation on its web site. You will thus be able to access and download the most current Media5 documentation. Follow this link: http://www.media5corp.com/en/...

  • Page 22: Unit Manager Network - Element Management System

    Supports SNMP requests: GET, GET NEXT, GET TABLE, GET WALK, SET, TRAP.  SNMP abstraction layer: configuration can be changed without SNMP MIB knowledge. The demo version of the Unit Manager Network is available on the Media5 Download Portal at: https:// support.mediatrix.com/DownloadPlus/Download.asp.

  • Page 23: Installation And Web

    Installation and Web Page Configuration...
  • Page 24 Page Left Intentionally Blank...

  • Page 25: Chapter 1 Installation

    The Mediatrix 4104 package contains the following items:  the Mediatrix 4104 unit  a power cord for the country in which you are using the Mediatrix 4104  a printed Flyer You may also need additional 10/100 BaseT Ethernet RJ-45 cables.

  • Page 26: Overview

    Offers an intuitive Web-based management interface to simplify operation and support. Placing a Call You can place a call from a telephone or fax connected to a Mediatrix 4104. The unit automatically detects if the call originates from a voice or fax transmission and acts accordingly.

  • Page 27: Management Choices

    Overview Reference Manual (SIP Version) Management Choices The Mediatrix 4104 offers various management options to configure the unit. Table 3: Management Options Management Choice Description Web Interface The Mediatrix 4104 web interface offers the following options: • Password-protected access via basic HTTP authentication, as described in RFC 2617 •...

  • Page 28: Panels

    ETH2 Provides the state of the network connected to the ETH2 connector. Ready When lit, the Mediatrix 4104 is ready to initiate or receive a call. The unit does not have to be registered to a server. In Use When lit, at least one of the FXS lines is in use.

  • Page 29: Rear Connectors

    Panels Reference Manual (SIP Version) Rear Connectors The Mediatrix 4104 has several connections that must be properly set. Figure 2 shows the back panel of the Mediatrix 4104. Figure 2: Back Panel Connectors RJ-45 connector for 10/ RJ-11 Bypass 100 BaseT Ethernet...

  • Page 30: Choosing A Suitable Installation Site

    Warning: To prevent fire or shock hazard do not expose the unit to rain or moisture. The Mediatrix 4104 is suited for use in an office environment where it can be wall-mounted or free standing. Location Install the Mediatrix 4104 in a well-ventilated location where it will not be exposed to high temperature or humidity.

  • Page 31: Wall-Mounting

    Free Standing Unit When installing the Mediatrix 4104 on a desk or table, it should be located at least 20 cm from your monitor, computer casing or other peripherals, including speakers. Never put books or paper on the Mediatrix 4104.

  • Page 32: Hardware Connection

    For example, a straight cable is required to connect the Mediatrix 4104 to a hub or a switch, while a crossover cable is required to connect the Mediatrix 4104 to a PC.

  • Page 33: Installing The Mediatrix 4104

    Connect a SCN line into the Bypass connector of the Mediatrix 4104 (optional). Use a standard telecommunication cord with a minimum of 26 AWG wire size. Connect the power cord to the Mediatrix 4104 and then connect the other end to an electrical outlet. Warning: The electrical outlet must be installed near the Mediatrix 4104 so that it is easily accessible.

  • Page 34: Starting The Mediatrix 4104 For The First Time

    DHCP server for the unit you are about to connect (“Reserving an IP Address” on page 10). If you have not reserved an IP address, you can discover which IP address has been assigned to the Mediatrix 4104 by either: ...

  • Page 35: Initial Provisioning Sequence

    IP address is the same on every unit. Initial Provisioning Sequence When starting the Mediatrix 4104 for the first time, it needs to be configured before it can support calls. This process is known as provisioning. This sequence assumes that you have installed the Mediatrix 4104 hardware as per “Hardware Connection”...

  • Page 36: Led Behaviour In Starting Mode

    LED Behaviour in Starting Mode When the Mediatrix 4104 starts and it is not configured to use a DHCP server, it uses static IP addresses. If the static information is not valid, the LAN LED blinks at 1 Hz with 75% duty cycle. This lets you know that you must perform a Factory reset or Recovery mode operation.

  • Page 37: Led Patterns

    Progress Image Triggered after a failure of an image download Blink Blink Blink Blink Download operation. After 4 seconds, the unit restarts. 2 Hz 2 Hz 2 Hz 2 Hz Error Mediatrix 4104...

  • Page 38: Booting Led Pattern Description

    See the corresponding LED pattern in “NormalMode LED Pattern Description” on page b. If Bypass is triggered because power is removed from the Mediatrix 4104, all LEDs are Off. Booting LED Pattern Description While in the Booting state, the LEDs of the Mediatrix 4104 behave independently; the following table indicates the behaviour for each LED.

  • Page 39: Normalmode Led Pattern Description

    LED Indicators Reference Manual (SIP Version) NormalMode LED Pattern Description While in the NormalMode state, the LEDs of the Mediatrix 4104 behave independently; the following table indicates the behaviour for each LED. Table 9: LED Patterns in Operation Mode Pattern...

  • Page 40: Reset / Default Switch

     Reconfigure a unit. At Run-Time The Reset / Default switch can be used at run-time – you can press the switch while the Mediatrix 4104 is running without powering the unit off. Table 11 describes the actions you can perform in this case.

  • Page 41: Recovery Mode

    Recovery Mode The recovery mode restarts the Mediatrix 4104 in a known, static, and minimal state. It is used to recover from a basic configuration error that prevents you to reach the unit through the network. It may serve as a last resort before the Factory reset command.

  • Page 42: Factory Reset

    The Factory reset creates a new configuration file with the default factory values. It should be performed with the Mediatrix 4104 connected to a network with access to a DHCP server. If the unit cannot find a DHCP server, it sends requests indefinitely.

  • Page 43: Software Restart

    You can disable the factory reset procedure, even if users depress the Reset / Default switch. Disabling the factory reset means that users will not be able to revert the Mediatrix 4104 back to its factory settings if there are configuration problems.

  • Page 44: Verifying The Installation

    Chapter 1 - Installation Verifying the Installation Verifying the Installation There are two ways to verify that the Mediatrix 4104 is properly connected to the IP network and is working:  By contacting it with a SNMP Browser  By pinging it These two procedures assume that you know the IP address of the Mediatrix 4104 you want to verify.

  • Page 45: Web Interface - Introduction

    Web Interface Access Limitation Access to the web interface can be limited to only one of the Mediatrix 4104’s interface or all its interfaces. Furthermore, you can grant access to one or both of the Administration and End User web pages available.
  • Page 46 Restart the Mediatrix 4104 so that the changes may take effect.  To use the web interface configuration: In your web browser’s address field, type the IP address of the Mediatrix 4104 (if you have performed a recovery mode, this is 192.168.0.1). The following opens: Figure 8: Login Window The Mediatrix 4104 uses Digest Authentication to grant access to the web-based interface.

  • Page 47: System Status Of The Mediatrix 4104

    Using the Web Interface Reference Manual (SIP Version) System Status of the Mediatrix 4104 The Device Info – Info page displays the current system status of the Mediatrix 4104. Table 13: Info Page IP Information Description System Up Time The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

  • Page 48: Content Frame

    Mediatrix 4104. Submitting Changes When you perform changes in the web interface and click the Submit button, the Mediatrix 4104 validates the changes. A message informs you that the Mediatrix 4104 must be restarted if one or more non-dynamic value was changed.

  • Page 49: Syslog Monitoring

    Syslog daemon address is provided by a DHCP server or specified by the administrator, no messages are sent. For instance, if you want to download a new software into the Mediatrix 4104, you can monitor each step of the software download phase. Furthermore, if the unit encounters an abnormal behaviour, you may see accurate messages that will help you troubleshoot the problem.

  • Page 50: Configuring The Syslog Daemon Application

    Error error and has not been completed Configuring the Syslog Daemon Application You shall configure the Syslog daemon to capture those messages. Refer to your Syslog daemon’s documentation to learn how to properly configure it to capture messages. Mediatrix 4104...

  • Page 51: Web Interface - Management

    RFC 2617 – HTTP Authentication: Basic and Digest Access Authentication The Change HTTP Server ADMINISTRATOR Username/Password section allows you to modify the default password to access the web interface. The Mediatrix 4104 supports basic HTTP authentication, as described in RFC 2617. ...
  • Page 52 The web password is reset to the default value specified by the httpServerDefaultPassword variable. Restart the Mediatrix 4104 so that the change may take effect. Issue: Factory Reset does not Reset the Default Password Value The following describes three cases in which the factory reset may not properly reset the HTTP server password.

  • Page 53: System Management

    • Disable: SNMP connections are forbidden. If you are exclusively using the web page to configure the Mediatrix 4104, you could disable the SNMP service agent and forbid any SNMP connection to the unit. If the SNMP agent is disabled and the unit enters into recovery mode, SNMP connections are allowed during that time.

  • Page 54: Group Port Management

    Click Submit if you do not need to set other parameters. Interface Management You can set the administrative state of a line that will be kept until the Mediatrix 4104 restarts.  To set the interface management parameters: In the Interface Management section of the Admin page, select the proper command to execute in the Command column.

  • Page 55: Network Settings

    Network Settings Reference Manual (SIP Version) This command temporary locks/unlocks the selected line of the Mediatrix 4104. This state is kept until the unit restarts. It offers the following settings: Table 22: Temporary Lock Settings Setting Description noOp No action is taken.

  • Page 56: Network Settings

    The Network Settings section allows you to set the IP information the Mediatrix 4104 needs to work properly. This section is vital to the proper operation of the Mediatrix 4104. If a field of this group is not properly set, the Mediatrix 4104 may not be able to restart and be contacted after it has restarted.

  • Page 57: Sntp Settings

    If the IP address source is Static, enter the following static IP information. Table 24: IP Addresses Parameters Parameter Definition IP Address Public IP address of the Mediatrix 4104. This address is used for incoming signalling, media and management traffic. Subnet Mask Subnet mask IP address used by the Mediatrix 4104. Note: Media5 recommends not to set a subnet mask of 255.255.255.254...
  • Page 58 Table 25: Network Settings Configuration Sources Source Description Static You manually enter the value and it remains the same every time the Mediatrix 4104 restarts. Use the static configuration if you are not using a DHCP server or if you want to bypass it. DHCP The value is obtained at start-time by querying a DHCP server and using standard DHCP fields or options.
  • Page 59 The following are some valid POSIX strings: Table 28: Valid POSIX Strings Time Zone POSIX String Pacific Time (Canada & US) PST8PDT7,M3.2.0/02:00:00,M11.1.0/02:00:00 Mountain Time (Canada & US) MST7MDT6,M3.2.0/02:00:00,M11.1.0/02:00:00 Central Time (Canada & US) CST6CDT5,M3.2.0/02:00:00,M11.1.0/02:00:00 Eastern Time Canada & US) EST5EDT4,M3.2.0/02:00:00,M11.1.0/02:00:00 Mediatrix 4104...

  • Page 60: Configuration File Download

    185. Configuration File Download Server The service allows to download a unique file for each Mediatrix 4104, and/or a file shared among many units. These configuration files may be encrypted or not. You have the choice to perform the configuration file download by using the TFTP protocol or the HTTP protocol.

  • Page 61: Configuration File Server Settings

    HTTP server’s documentation. Configuration File Server Settings The Mediatrix 4104 must know the IP address and port number of its configuration file server. This server contains the configuration file the Mediatrix 4104 will download. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself.

  • Page 62: Setting Up The Configuration File Download

    Table 30: Configuration File Information Sources Source Description Static You manually enter the value and it remains the same every time the Mediatrix 4104 restarts. Use the static configuration if you are not using a DHCP server or if you want to bypass it. DHCP The value is obtained at start-time by querying a DHCP server and using standard DHCP fields or options.
  • Page 63 • Cut and paste the path and/or name of the directory that contains the extracted files into the configuration file path of the Mediatrix 4104 (you may have to convert “\” into “/ ”) to eliminate typographical errors. Note that you can define the C:/Root/Download part as you want. The file names may also differ from the example shown above.
  • Page 64 If valid configuration files are successfully downloaded, then the Mediatrix 4104 automatically restarts to apply all the new settings. If the Mediatrix 4104 does not restart, this could mean the download failed or that the configuration in the file is the same as the configuration in the unit.

  • Page 65: Configuration Files Encryption

    Reference Manual (SIP Version) Configuration Files Encryption You can secure the exchange of configuration files between the server and the Mediatrix 4104. A privacy key allows the unit to decrypt a previously encrypted configuration file. To encrypt a configuration file (generic or specific), you must use the MxCryptFile application. MxCryptFile is a command line tool that encrypts files before sending them to the Mediatrix 4104 unit.

  • Page 66: Automatic Configuration Update

    31 for more details on the system commands. Click Submit. Automatic Configuration Update You can configure the Mediatrix 4104 to automatically update its configuration. This update can be done:  Every time the Mediatrix 4104 restarts.  At a specific time interval you can define.
  • Page 67 Click Submit if you do not need to set other parameters. Automatic Update at a Specific Time Interval You can configure the Mediatrix 4104 to download new configuration files at a specific day and/or time.  To set the automatic update at a specific time interval: Set the configuration file server host and port as defined in “Configuration File Server Settings”...
  • Page 68 “SNTP Settings” on page 35 for more details on how to configure the Mediatrix 4104 for a SNTP server. If a time range is specified, the unit will download the configuration files at a random time within the interval specified.

  • Page 69: Error Handling

    The fetched configuration file “XXX”, from server “XXX”, has a size “XXX bytes” that exceeds the maximum allowed size “XXX bytes”. Set sysAdminDownloadConfigFileStatus to fail. Mediatrix 4104...
  • Page 70 Received a 404 Not Found from Send a syslog warning message including the the HTTP server. file location/name with the HTTP server address: The configuration file “XXX” was not found on the HTTP server “XXX”. Set sysAdminDownloadConfigFileStatus to fail. Mediatrix 4104...

  • Page 71: Firmware Download

    TFTP server with proper root path  MIB browser (with the current Mediatrix 4104 MIB tree) You can use the MIB browser built in the Media5’s Unit Manager Network. See “Unit Manager Network – Element Management System” on page xxii for more details.

  • Page 72: Firmware Servers Configuration

    If you are to perform a firmware download by using the HTTP protocol, you must install a HTTP server running on the PC designated as the server host. This PC must not have a firewall running. Media5 also recommends to place the PC and the Mediatrix 4104 in the same subnet.

  • Page 73: Setting Up The Firmware Download

    Extract the contents of the zip file on the PC designated as the firmware download server. Be sure to use the defined folder name. This creates a directory that contains the files required for the Mediatrix 4104 to properly update its firmware.
  • Page 74 The Mediatrix 4104 first downloads a file called “setup.inf”. This file contains the list of all the other files to download, depending on the product. The “setup.inf” file and all the other files must be in the same directory.
  • Page 75 Save this file as “mediatrix4104targetimage.inf” under the server root path. Note: If you leave the file empty, the Mediatrix 4104 will look for the firmware download information in the root directory of the image server. Configure the path of the “mediatrix4104targetimage.inf” file in the Firmware Selection File Location field.
  • Page 76 You can validate the status of the firmware download in various ways. Syslog Messages If you are using a Syslog daemon, you will receive messages that inform you of the firmware update status. The following are the syslog messages the Mediatrix 4104 sends: Table 39: Firmware Update Syslog Messages Level...
  • Page 77 When receiving TFTP error “ACCESS” or HTTP xxx on host: xxx is unauthorized response #401. LED States When the Mediatrix 4104 initiates a firmware download, the LEDs located on the front panel indicate the status of the process. Table 40: LED States in Firmware Download Event...

  • Page 78: Firmware Download Procedure

    If Transparent Address Sharing is enabled during the firmware download, the PC connected to the Mediatrix 4104 may experience momentary loss of Internet connectivity. Automatic Firmware Update You can configure the Mediatrix 4104 to automatically update its firmware. This update can be done:  Every time the Mediatrix 4104 restarts.
  • Page 79 Click Submit if you do not need to set other parameters. Automatic Update at a Specific Time Interval You can configure the Mediatrix 4104 to download a new firmware at a specific day and/or time.  To set the automatic update at a specific time interval: If not already done, setup the Image server used to download the firmware (see “Before...
  • Page 80 “SNTP Settings” on page 35 for more details on how to configure the Mediatrix 4104 for a SNTP server. If a time range is specified, the unit will initiate the image software download at a random time within the interval specified.

  • Page 81: Spanning Tree Protocol (Stp)

    The secondary image server is up and running well. In this case, the Mediatrix 4104 tries to contact the primary image server. As it is not available, the Mediatrix 4104 retries for two minutes. It contacts the secondary server after that period and starts the firmware download.

  • Page 82: Emergency Firmware Procedure

    However, if these addresses cannot be reached from the unit’s subnet, the default gateway must provide appropriate routing to them. If the firmware download also fails with the two default servers, the Mediatrix 4104 idles for one minute.

  • Page 83: Web Interface – Sip Parameters

    H A P T E R Web Interface – SIP Parameters The SIP page allows you to configure the various SIP-related parameters of the Mediatrix 4104:  General SIP configuration parameters  SIP Interop parameters  Authentication parameters SIP Servers Configuration Standards Supported •...

  • Page 84: Sip Configuration

    SIP Configuration The Mediatrix 4104 must know the IP address and port number of the SIP servers. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself.

  • Page 85: Sip User Agent

    A user agent is a logical entity that can act as both client and server for the duration of a dialog. Each line (also known as endpoint) of the Mediatrix 4104 is a user agent. You can set information for each user agent such as its telephone number and friendly name. This information is used to dynamically create the To, From and Contact headers used in the request the user agent sends.

  • Page 86: Sip Registration

    In the SIP Registration section of the SIP page, set the registration command in the SIP Registration Command menu. Figure 29: SIP – SIP Registration section The following values are available: • noOp: No operation. • refresh: Refresh registrations. Mediatrix 4104...

  • Page 87: Sip Publication

    When a host is in the penalty box, it is never used to try to connect to a remote host unless it is the last choice for the Mediatrix 4104 and there are no more options to try after this host.
  • Page 88 The Mediatrix 4104 skips over UDP and tries the next target, which is TCP. Again, TCP is still in the penalty box, but this time, it is the last target the Mediatrix 4104 can try, so penalty box or not, TCP is used all the same to try to contact endpoint “B”.

  • Page 89: Sip Transport Type

    RFC 3261 – SIP: Session Initiation Protocol You can globally set the transport type for all the lines of the Mediatrix 4104 to either UDP (User Datagram Protocol) or TCP (Transmission Control Protocol). The Mediatrix 4104 will include its supported transports in its registrations.
  • Page 90 Table 47: Call Transfer Versions Supported Version Description Transfer 02 The Mediatrix 4104 executes transfers by using the methods described in the now expired draft-ietf-sip-cc-transfer-02.txt. Its use is deprecated and you should use this setting for backward compatibility issues only.

  • Page 91: Sip Authentication

    You can add two types of authentication information:  user agent specific authentication You can define up to five user names and five passwords for each user agent of the Mediatrix 4104. A user agent can thus register with five different realms. ...
  • Page 92 When authentication information is required from users, the realm identifies who requested it. Enter a string that uniquely identifies this user agent in the realm in the Username column. Enter a user password in the Password column. Click Submit if you do not need to set other parameters. Mediatrix 4104...

  • Page 93: Web Interface – Telephony

    Shortcut to local number at other corporate sites 91xxxxxxxxxx Long distance numbers 9011 + up to 15 digits International number The solution to this problem is to load the Mediatrix 4104 with a digit map that corresponds to the dial plan. Mediatrix 4104...

  • Page 94: Special Characters

    Chapter 5 - Web Interface – Telephony Digit Maps A Mediatrix 4104 that detects digits or timers applies the current dial string to the digit map, attempting a match to each regular expression in the digit map in lexical order.
  • Page 95 It indicates that if users have not dialed a digit for the time defined, it is likely that they have finished dialing and the Mediatrix 4104 can make the call. A digit map for this could be:...

  • Page 96: General Parameters

    The timer starts when the dial tone is played. When the timer expires, the receiver off-hook tone is played. This value is expressed in milliseconds (ms). Values range from 1000 ms to 180000 ms. Click Submit if you do not need to set other parameters. Mediatrix 4104...

  • Page 97: Allowed Digit Maps

    Reference Manual (SIP Version) Allowed Digit Maps You can create/edit ten digit maps for the Mediatrix 4104. Digit map rules are checked sequentially. If a telephone number potentially matches two of the rules, the first rule encountered is applied. ...

  • Page 98: Blocked Digit Maps

    Blocked Digit Maps A blocked digit map forbids to call specific numbers; for instance, you want to accept all 1-8xx numbers except 1-801. You can create/edit ten blocked digit maps for the Mediatrix 4104.  To set up blocked digit maps: In the Blocked Digit Map section –...

  • Page 99: Voice & Fax Codecs

    Click Submit if you do not need to set other parameters. Voice & Fax Codecs The four lines of the Mediatrix 4104 can simultaneously use the same codec (for instance, G.711 PCMA), or a mix of any of the supported codecs. Set and enable these codecs for each line.

  • Page 100: G.726

    “G.726 Codecs Parameters” on page 84 for more details. Analog Modem The Mediatrix 4104 can send modem transmissions in clear channel (G.726). If configured adequately, modems with higher rate capabilities (for instance, V.90) will automatically fall back in the transmission range supported.

  • Page 101: General Parameters

    Voice & Fax Codecs Reference Manual (SIP Version) The Mediatrix 4104 supports G.729A and G.729AB for encoding and G.729, G.729A and G.729AB for decoding. Table 56: G.729 Features Feature Description Packetization time Range of 10 ms to 100 ms with increment of 10 ms. See “G.729 Codec...
  • Page 102 The jitter buffer allows better protection against packet loss, but increases the voice delay. If the network to which the Mediatrix 4104 is connected suffers from a high level of congestion, the jitter buffer protection level should be higher. If the network to which the Mediatrix 4104 is connected suffers from a low level of congestion, the jitter buffer protection level should be lower.
  • Page 103 Set the RTP Base Port field with the port number you want to use as RTP/RTCP base port. The RTP/RTCP ports are allocated starting from the base port. The Mediatrix 4104 may use two or four RTP/RTCP ports for each FXS interface: •...

  • Page 104: G.711 Codec Parameters

    Enable the G.711 Voice Activity Detection (VAD) by selecting Enable in the G.711 VAD choice. VAD defines how the Mediatrix 4104 sends information pertaining to silence. This allows the unit to detect when the user talks, thus avoiding to send silent RTP packets. This saves on network resources.

  • Page 105: G.729 Codec Parameters

    Enable the G.729 Voice Activity Detection (VAD) by selecting Enable in the G.729 VAD choice. VAD defines how the Mediatrix 4104 sends information pertaining to silence. This allows the unit to detect when the user talks, thus avoiding to send silent RTP packets. This saves on network resources.

  • Page 106: G.726 Codecs Parameters

    If a value between 96 and 127 is refused, this means it is already used by another dynamic codec. Note: If you set the DTMF Transport field to outOfBandUsingSignalingProtocol (“General Parameters” on page 79), you cannot configure a dynamic payload type to 111 because it is already used by the DTMF out-of-band using signalling protocol. Mediatrix 4104...

  • Page 107: Fax Parameters

    Upon fax termination, if the call is not BYE, the previous voice codec is recovered with another re- INVITE. All lines of the Mediatrix 4104 can simultaneously use the same codec (for instance, T.38), or a mix of any of the supported codecs. Set and enable these codecs for each line.
  • Page 108 The Mediatrix 4104 can send faxes in T.38 mode over UDP or TCP. T.38 is used for fax if both units are T.38 capable; otherwise, transmission in clear channel over G.711 as defined is used (if G.711 µ-law and/or G.711 A-law are enabled).
  • Page 109 For additional reliability, define the number of times T.38 packets are retransmitted in the T.38 Final Frames Redundancy field. This only applies to the T.38 packets where the PrimaryUDPTL contains the following T.38 data type: • HDLC_SIG_END, • HDLC_FCS_OK_SIG_END, • HDLC_FCS_BAD_SIG_END and • T4_NON_ECM_SIG_END Mediatrix 4104...
  • Page 110 See “Data Codec Selection Procedure” on page 251 for more details. Click Submit if you do not need to set other parameters. Mediatrix 4104...

  • Page 111: Call Forward

    71). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to stop the service in the Digits to disable field.
  • Page 112 Chapter 5 - Web Interface – Telephony Call Forward The deactivating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Set the activation status of the service in the Service Status field to Inactive or Active.

  • Page 113: On No Answer

    71). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to stop the service in the Digits to disable field.

  • Page 114: Unconditional

    For instance, you could decide to put “*74” as the sequence to activate the service. This sequence must be unique and follow the syntax for digit maps (see “Digit Maps” on page 71). Dialing this digit map does not have any effect unless the service’s status is “enabled”. Mediatrix 4104...
  • Page 115 Call Forward Reference Manual (SIP Version) The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to stop the service in the Digits to disable field.

  • Page 116: Services

    The blind call transfer service is sometimes called Transfer without Consultation or Unattended Transfer. It allows a user to transfer a call on hold to a still ringing (unanswered) call. The individual at the other extension or telephone number does not need to answer to complete the transfer. Mediatrix 4104...

  • Page 117: Call Waiting

    The user that is about to send a fax can thus deactivate the call waiting tone to ensure that the fax transmission will not be disrupted by an unwanted second call. When the fax transmission is completed and the line is on-hook, the call waiting tone is automatically reactivated. Mediatrix 4104...
  • Page 118 71). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The deactivating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to enable the call waiting service permanently in the Permanent Activation Digit Map field.

  • Page 119: Using Call Waiting

    Take the receiver off-hook. Replace the receiver on-hook. The call waiting tone is re-enabled. Permanently Removing the Call Waiting Tone You can permanently activate/deactivate the call waiting service.  To activate the call waiting service: Take the receiver off-hook. Mediatrix 4104...

  • Page 120: Conference

    Figure 51: Conference Call Flow User User User INVITE (G.729) Agent Agent Agent Trying/Ringing/200 OK Flash Hook Invite (HOLD) Trying/200 OK INVITE (G.729) Trying/Ringing/200 OK Flash Hook INVITE (PCMU) Trying200 OK INVITE (UNHOLD-PCMU) Trying/200 OK 3-way Conference Call Established Mediatrix 4104...
  • Page 121 If this is not the case, then part of the conversation may be lost, resulting in a choppy voice. For better results, Media5 recommends to set the packetization period of all participants of a 3-way conference to 30 milliseconds. See “Voice &...

  • Page 122: Call Hold

    To enable the Call Hold service: Select to which port you want to apply the changes in the drop down menu at the top of the window. In the Hold section, enable the service by selecting Enable in the Activation choice. Mediatrix 4104...

  • Page 123: Second Call

    When this service is enabled, the second line service is disabled but the call waiting feature is still functional. The user can still accept incoming calls.  To set the automatic call feature: In the web interface, click the Telephony link, then the Services sub-link. This links to the Telephony – Advanced web page. Mediatrix 4104...

  • Page 124: Miscellaneous

    Custom Tone Configuration  Message Waiting Indicator Country Selection It is very important to set the country in which the Mediatrix 4104 is used because a number of parameter values are set according to this choice. These parameters are:  Tones ...

  • Page 125: Custom Tone Configuration

    Miscellaneous Reference Manual (SIP Version) Click Submit if you do not need to set other parameters. This parameter is set for all the lines of the Mediatrix 4104. You cannot have a different country for each line. Caller ID Selection In countries that support more than one caller ID standard, this standard can be selected with the Country Selection field.
  • Page 126 Value of the loop counter. The range is from 2 to 128. states-section Description of the tone state. You can define up to eight states (s1 to s8). You must enter at least one state if the is not empty. tone-pattern state-description Description of the tone state. Mediatrix 4104...
  • Page 127 The following table gives some examples of custom tones. Note that the quotation marks are not part of the syntax and must not be included when entering the tone pattern. Table 62: Pattern Examples Example Pattern "" No tone Mediatrix 4104...
  • Page 128 The general format of the pattern string now looks as follows: Pattern = [ f1=350:-17,f2=440:-17 [ "," loop-counter-section ] "," states- section ] Set the loop-counter-section category, which is defined as: loop-counter-section = "l=" loop-counter It defines the number of times to repeat the pattern. Mediatrix 4104...
  • Page 129 You can use from one to four frequencies. The North America stutter dial tone has two frequencies, thus: frequency-selection = [ ":f1" ] [ ":f2" ] on-state-description parameter is now: on-state-description = "on" [ ":f1" ] [ ":f2" ] ] [ time] [ loop-indicator ] [ next-state ] Mediatrix 4104...
  • Page 130 = ":l" It is used to stop looping between states. It indicates that the loop stops after three times. Once the loop is completed, the pattern goes to the next state (which is state 3). Mediatrix 4104...
  • Page 131 Since the third state is a continuous tone and does not use loops, this parameter is not required. on-state-description parameter is now: on-state-description = "on" [ ":f1" ] [ ":f2" ] [ next-state ] Mediatrix 4104...

  • Page 132: Message Waiting Indicator

    The caller can then leave a message. After the message is recorded, the server sends a message to the Mediatrix 4104 listing how many new and old messages are available. The Mediatrix 4104 alerts the user of the new message in two different ways: ...
  • Page 133 Refresh message waiting subscriptions. All enabled endpoints unsubscribe themselves from the service and re-subscribe by using the current provisioning. This parameter is set for all the lines of the Mediatrix 4104. You cannot have a different behaviour for each line.
  • Page 134 Define the duration, in seconds, of dynamic subscription to a messaging service in the MWI Expiration Time field. This parameter is set for all the lines of the Mediatrix 4104. You cannot have a different behaviour for each line. Enable the MWI by selecting Active in the MWI Activation field.
  • Page 135 For more information on how to configure the Route Manager, please refer to the IP Communication Server Administration Manual or the IP Communication Server contextual help. Configuring the Mediatrix 4104 There is no special unit configuration required. The Mediatrix unit behaves as if in a standard call until it receives one of the following parameters in the Contact field: ...
  • Page 136 Chapter 5 - Web Interface – Telephony Miscellaneous Mediatrix 4104...

  • Page 137: Web Interface – Advanced

    H A P T E R Web Interface – Advanced The Advanced page allows you to configure various system and network parameters of the Mediatrix 4104. Quality of Service (QoS) QoS (Quality of Service) features enable network managers to decide on packet priority queuing. The Mediatrix 4104 supports the Differentiated Services (DS) field and 802.1q taggings.
  • Page 138 Enable this option only on compatible LAN with equipment supporting the VLAN tagging. Otherwise, the Mediatrix 4104 may be unreachable. In this case, use the Reset / Default button to access and disable VLAN tagging – in the recovery mode, tagging is not permitted.

  • Page 139: Diffserv Configuration

    When the filter for signalling protocol is disabled and the VLAN option is enabled, the Mediatrix 4104 uses the default user priority defined in the VLAN Default Priority field. Otherwise, the user priority set for signalling has precedence over the VLAN default user priority.

  • Page 140: Emergency

    RFC 3168 now defines the state in which to set the two least significant bits in the TOS byte. On the other hand, this RFC only applies to TCP transmissions and the bits are thus set to “0” in the Mediatrix 4104.

  • Page 141: Stun Configuration

    For a unit to work properly behind a firewall, it must keep a pinhole opened by sending keepalive packets through the firewall. The Mediatrix 4104 only sends keepalive packets to the last destination for a specific socket. When a unit is not configured with an outbound proxy, it can send, through its SIP socket, messages to various destinations, such as a SIP redirect server, another SIP unit, or a MWI server.

  • Page 142: Restrictions On The Media5 Stun Implementation

    NAT/firewall to be able to communicate with each other. STUN Client Configuration The STUN sub-page of the Advanced page allows you to configure the STUN client of the Mediatrix 4104. You can also set these parameters via SNMP, as described in “Chapter 19 - STUN Configuration”...

  • Page 143: Sip Custom Nat Traversal

    SIP Custom NAT Traversal The Mediatrix 4104 may be used in a private domain that is not directly connected to the IP network. For instance, this may be the case for ITSP (Internet Telephony Service Provider) clients that have a small private network.
  • Page 144 Chapter 6 - Web Interface – Advanced STUN Configuration Mediatrix 4104...

  • Page 145: Snmp Configuration

    SNMP Configuration...
  • Page 146 Page Left Intentionally Blank...

  • Page 147: Mib Structure And Snmp

    H A P T E R MIB Structure and SNMP This chapter describes how the Mediatrix 4104 uses the SNMP protocol for its configuration. SNMP Overview The Mediatrix 4104 uses the Simple Network Management Protocol (SNMP) for initial software configuration provisioning and subsequent software configuration.

  • Page 148: Snmp Versions

    Chapter 7 - MIB Structure and SNMP SNMP Overview SNMP Versions The Mediatrix 4104 supports three versions of SNMP: SNMPv1, SNMPv2c and SNMPv3. SNMP defines a few types of messages that are exchanged between the manager and agent. SNMPv1 Messages The following messages are specific to SNMPv1.

  • Page 149: Snmp Behaviour

    Manager SNMP Behaviour When using SNMP, the following rules apply:  Media5 recommends to copy the SNMPv3 user attributes only twice.  The administrator may edit the SNMPv3 user attributes: • Authentication algorithm (none, MD5, or SHA) •...

  • Page 150: Snmpv3 Special Behaviour

    SNMPv3 works properly. The Mediatrix 4104 thus refuses any SNMPv1 or SNMPv2 request it receives. You can disable / enable SNMPv1 / SNMPv2 by using the MIB Browser included in the Media5 Unit Manager Network (or any other MIB Browser) to modify the permissions related to SNMPv1 / SNMPv2 (security model).

  • Page 151: Snmp Configuration Via A Configuration File

    The vacmContextTable is not saved under any condition. SNMP Configuration via a Configuration File You can modify the SNMP configuration of the Mediatrix 4104 by inserting an SNMP Agent section in a configuration file and then transferring this configuration file into the unit. This configuration replaces any configuration set in a profile.
  • Page 152 <vacmGroupName ValueType="OCTET_STRING" Value="AuthNoPrivGrp"/> <vacmSecurityToGroupStorageType ValueType="UINT32" Value="4"/> <vacmSecurityToGroupStatus ValueType="UINT32" Value="1"/> </g> <h> <vacmSecurityModel ValueType="UINT32" Value="3"/> <vacmSecurityName ValueType="OCTET_STRING" Value="NoAuthNoPrivUser"/> <vacmGroupName ValueType="OCTET_STRING" Value="NoAuthNoPrivGrp"/> <vacmSecurityToGroupStorageType ValueType="UINT32" Value="4"/> <vacmSecurityToGroupStatus ValueType="UINT32" Value="1"/> </h> </vacmSecurityToGroupTable> <vacmAccessTable> <a> <vacmAccessContextPrefix ValueType="OCTET_STRING" Value="AuthPrivGrp"/> <vacmAccessSecurityModel ValueType="UINT32" Value="3"/> <vacmAccessSecurityLevel ValueType="UINT32" Value="3"/> Mediatrix 4104...
  • Page 153 <vacmAccessContextPrefix ValueType="OCTET_STRING" Value="Snmpv2cRWPrivateGrp"/> <vacmAccessSecurityModel ValueType="UINT32" Value="2"/> <vacmAccessSecurityLevel ValueType="UINT32" Value="1"/> <vacmAccessContextMatch ValueType="UINT32" Value="1"/> <vacmAccessReadViewName ValueType="OCTET_STRING" Value="PublicView"/> Enable/Disable SNMPv2 <vacmAccessWriteViewName ValueType="OCTET_STRING" Value="PublicView"/> Enable/Disable SNMPv2 <vacmAccessNotifyViewName ValueType="OCTET_STRING" Value="PrivateView"/> <vacmAccessStorageType ValueType="UINT32" Value="4"/> <vacmAccessStatus ValueType="UINT32" Value="1"/> </g> </vacmAccessTable> </vacmMIBObjects> </snmpVacmMIB> </snmpModules> </snmpV2> </SnmpAgentConfig> Mediatrix 4104...
  • Page 154 Figure 66 on page 129 with the following icon: Enable/Disable SNMPv3 Changing SNMPv3 Credentials The SNMP Agent section provides default Media5 credentials for SNMPv3. You can change these credentials.  To change SNMPv3 credentials: Change the password in the following fields: •...

  • Page 155: Mib Structure

    Please note that Media5’ configuration tool – the Unit Manager Network – does not support MIBs that are located under the mediatrixExperimental branch of the MIB structure.

  • Page 156: Textual Conventions

    Event An event is sent to tell what type of data will be received, but not the data itself. This is used to “warn” in advance what is coming. Mediatrix 4104...

  • Page 157: Ip Addresses

     By using a SNMP browser to contact the MIBs of the Mediatrix 4104. It is assumed that you have basic knowledge of TCP/IP network administration. You can use the MIB browser built in the Media5’ Unit Manager Network. See “Unit Manager...

  • Page 158: Tables

    Voice FXS Voice FXS Voice FXS Voice FXS (24) Figure 67 shows a table built in the Unit Manager Network from the voiceifTable parameters. Figure 67: voiceIftable Example You can perform GET and SET operations on these parameters. Mediatrix 4104...

  • Page 159: Variables For Administrative Commands

    The usage state of the current interface. It indicates the running state of a voice component. Available states are idle, active, busy, and idle-unusable. ifAdminParentType The parents type of this interface. ifAdminParent The index of the parent of this interface. Mediatrix 4104...

  • Page 160: Snmp Access Limitation

    Chapter 7 - MIB Structure and SNMP SNMP Access Limitation SNMP Access Limitation The SNMP access to the Mediatrix 4104 can be limited to only one of its interface or all interfaces.  To limit the access to the SNMP interface: In the snmpAgentMIB, select the interface where the Mediatrix 4104 can be accessed via SNMP in the snmpAgentAccess variable.

  • Page 161: Sending Configuration Data To The Mediatrix 4104

    The configuration file is mostly used for the initial provisioning sequence (see “Initial Provisioning Sequence” on page 13 for more details). For more information on how to use a configuration file for updating the Mediatrix 4104, see “Chapter 12 - Configuration File Download” on page 185.
  • Page 162 Chapter 7 - MIB Structure and SNMP Sending Configuration Data to the Mediatrix 4104 Mediatrix 4104...

  • Page 163: Ip Addresses

    The Mediatrix 4104 must be provisioned with various IP addresses and network parameters to be fully functional. This occurs each time the Mediatrix 4104 is started or when an IP address value is changed in the MIB. The Mediatrix 4104 can use static network parameters as well as parameters provided by a DHCP server or even a DNS.

  • Page 164: Ip Address And Network Configuration

    The value is not provisioned. The application provides an acceptable default. Services This section describes the services the Mediatrix 4104 uses and their settings. Most of these services require that you define their IP address and, if required, port number. See “DHCP Server Configuration” on page 153 for more details.

  • Page 165: Local Host

    Static Configuration Using static IP addresses allows you to bypass the DHCP server or still be able to use the Mediatrix 4104 if you are not running a DHCP server. In this case, having one or more configuration source variable set to DHCP slows down the restart process. If...
  • Page 166 Restart the Mediatrix 4104 so that the changes may take effect. WAN Address Configuration Source The Wide Area Network (WAN) address is the public IP address attributed to the Mediatrix 4104. This address is used for incoming signalling, media and management traffic.
  • Page 167 In the Unit Manager Network Administration Manual, refer to chapter Working with SNMP, section Setting Unit SNMP Preferences. The Mediatrix 4104 uses the SNMP protocol for software configuration. Set the following SNMP-related variable to properly use the protocol. Table 81: SNMP Configuration Variables...

  • Page 168: Static Dns

    Chapter 8 - IP Address and Network Configuration Services Static DNS By default, the Mediatrix 4104 receives DNS IP addresses according to the configuration source you have defined in the localHostSelectConfigSource variable. In general, these addresses are provided by an ISP (Internet Service Provider) via DHCP.

  • Page 169: Management Server

    This is the well-known TFTP port number as per RFC 1340. Management Server The ipAddressConfigMs group provides the configuration necessary for contacting a SNMP management server such as the Media5 Unit Manager Network. In the Unit Manager Network Administration Manual, refer to chapter Administration Parameters, section Unit Manager Server.

  • Page 170: Configuration File Fetching

    StaticHost configFileFetching Static Port Restart the Mediatrix 4104 so that the changes may take effect. Syslog The ipAddressConfigSyslog group provides the configuration necessary for contacting a Syslog server. In the Unit Manager Network Administration Manual, refer to chapter Administration Parameters, section Syslog Daemon.

  • Page 171: Sip Servers

    If not specified (0), use option 43, sub-option 203, bytes 0-3. sipRegistrarPort Use option specified in variable sipRegistrarDhcpSiteSpecificCode, bytes 4-5. If not specified (0), use option 43, sub-option 203, bytes 4-5. If bytes 4-5 are not present, use the default static value. Mediatrix 4104...

  • Page 172: Sntp

    DHCP server already has options that can be set to provide time server addresses, and the order in which clients use them to attempt to discover servers. The Mediatrix 4104 uses Option 42 to specify the IP address corresponding to the server that provides NTP/ SNTP (RFC 1769).

  • Page 173: Eth2 Connector Static Ip Address

    Reference Manual (SIP Version) ETH2 Connector Static IP Address You can use the ETH2 connector of the Mediatrix 4104 with the network card of a computer. You could then use this computer to directly access the unit via its LAN interface.

  • Page 174: Dhcp Configuration

    Many network switches use the Spanning Tree Protocol (STP) to manage Ethernet ports activity. If the Mediatrix 4104 is connected to such a switch, the switch may shut down the matching Ethernet port for at least one minute. This shutdown on the switch side can prevent proper communication. It may thus take up to three minutes before the unit receives an answer to its request for DHCP options.

  • Page 175: Changing The Size Of Dhcp Requests

    8 seconds delay  etc. The Mediatrix 4104 stops broadcasting as soon as it receives at least one reply. If the offer is valid, the Mediatrix 4104 takes it and continues its initialization procedure. Note: If the localHostSelectConfigSource variable is set to static and any other xxSelectConfigSource variable is set to dhcp, the Mediatrix 4104 makes its DHCP request that will be released immediately.

  • Page 176: Network Configuration

    The data is organized as a series of sub-options, each of them laid-out like a regular option (code, length, data). The codes can be anything between 1 and 254, and the vendor, Media5, chooses these codes. See Table 94 on page 156 for actual codes.

  • Page 177: Site Specific Options

    Vendor Class ID When using the vendor specific option, first define a Vendor Class ID for the Mediatrix 4104 (not supported in Windows NT servers). A Vendor Class ID can be used by DHCP clients to identify their vendor type and configuration.

  • Page 178: Option Codes

    The vendor specific options must be encapsulated because more than one information can be stored in this option: [code][length][4-6 bytes address][another code][another length][another address]... The site specific options can have only one information per option: [4-6 bytes address] Mediatrix 4104...

  • Page 179: Entering Fqdns

    Entering FQDNs The FQDN address layout is a Media5 proprietary extension to the IP address layout. This format allows the configuration of an IP address in binary format (with or without port) or a FQDN in string format (with or without port) in the same option.
  • Page 180 Site specific code definition option mx-syslog-ip code 129 = ip-address; option mx-syslog-str code 129 = string; option mx-primary-image-ip code 130 = ip-address; option mx-primary-image-str code 130 = string; option mx-secondary-image-ip code 131 = ip-address; option mx-secondary-image-str code 131 = string; Mediatrix 4104...

  • Page 181: Settings Example

    200 (management server) size of 4 bytes 0xA0x30x20xC9 IP address 10.3.2.201  Option 250 (site specific option) contains the hexadecimal sequence 0xA0x30x20xC80x400. Table 97: Hexadecimal Sequence - Option 250 Hexadecimal Part Corresponding Information 0xA0x30x20xC8 IP address 10.3.2.200 0x400 port 1024 Mediatrix 4104...

  • Page 182: Error Handling

    This assumes that the Mediatrix 4104 is set to get its IP information via a DHCP server. If the Mediatrix 4104 is configured to request some DHCP options but does not require an IP address from the server, the amount of time it will wait for an answer before proceeding further is configurable as defined in “Appendix - DHCP Options Waiting Time”...

  • Page 183: Ethernet Connection Speed

    This protocol can only detect the connection speed; the duplex mode cannot be detected. In this case, the connection may not be established. The Mediatrix 4104 has the possibility to force the desired Ethernet link speed and duplex mode by disabling the auto-negotiation and selecting the proper setting (sysConfigNetworkEthernetSpeed or sysConfigComputerEthernetSpeed variable).
  • Page 184 Chapter 8 - IP Address and Network Configuration Ethernet Connection Speed Mediatrix 4104...

  • Page 185: Sip Servers

    SIP Configuration Window. Configuration Source The Mediatrix 4104 must know the IP address and port number of the Registrar server. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself with the static variables.
  • Page 186 To use static information: In the ipAddressConfig folder, locate the sipServerSelectConfigSource variable (under the ipAddressConfigSipServer group). This variable defines whether or not the Mediatrix 4104 must get its registrar server configuration through a DHCP server. Set the sipServerSelectConfigSource variable to static.

  • Page 187: Proxy Server

    SIP Configuration Window. Configuration Source The Mediatrix 4104 must know the IP address and port number of the proxy server. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself with the static variables.

  • Page 188: Outbound Proxy Server

    To use static information: In the ipAddressConfig folder, locate the sipServerSelectConfigSource variable (under the ipAddressConfigSipServer group). This variable defines whether or not the Mediatrix 4104 must get its proxy server configuration through a DHCP server. Set the sipServerSelectConfigSource variable to static.

  • Page 189: Configuration Source

    Reference Manual (SIP Version) Configuration Source The Mediatrix 4104 must know the IP address and port number of the outbound proxy. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself with the static variables.

  • Page 190: Loose Router Configuration

    (section 6) for processing of the Route header field. These procedures separate the destination of the request (present in the Request-URI) from the set of proxies that need to be visited along the way (present in the Route header field). A proxy compliant to these mechanisms is also known as a loose router. Mediatrix 4104...

  • Page 191: Presence Compositor Server

    MIB is 0.0.0.0. Configuration Source The Mediatrix 4104 must know the IP address and port number of the Presence Compositor server. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself with the static variables.
  • Page 192 To use static information: In the ipAddressConfig folder, locate the sipServerSelectConfigSource variable (under the ipAddressConfigSipServer group). This variable defines whether or not the Mediatrix 4104 must get its Presence Compositor server configuration through a DHCP server. Set the sipServerSelectConfigSource variable to static.

  • Page 193: Dns Srv Configuration

    H A P T E R DNS SRV Configuration This chapter describes the configuration required for the Mediatrix 4104 to work with a DNS SRV. What is a DNS SRV? Standards Supported • RFC 2782 – A DNS RR for specifying the location of services (DNS SRV) •...

  • Page 194: Dns Srv Call Flow

    To enable DNS SRV: In the ipAddressConfig folder, locate the sipServerSelectConfigSource variable (under the ipAddressConfigSipServer group). This variable defines whether the Mediatrix 4104 must get its proxy server configuration through a DHCP server or not. Set the sipServerSelectConfigSource variable to static.

  • Page 195: Dns Srv Record Lock

    DNS SRV Record Lock You can configure the Mediatrix 4104 to always use the same DNS SRV record for a SIP call ID. As a result, a call or registration always uses the same destination until the destination is unreachable or the unit receives a different DNS SRV result.
  • Page 196 Chapter 10 - DNS SRV Configuration DNS SRV-Oriented Settings Mediatrix 4104...

  • Page 197: Country-Specific Configuration

    Both methods can be used on different lines at the same time. DTMF Signalling The data transmission using DTMF signalling is performed during or before ringing depending on the country settings or line configuration. The Mediatrix 4104 provides the calling line identity according to the following standards: ...

  • Page 198: Adsi

    Currently, very few ADSI-capable devices support these additional information. Setting the Location (Country) It is very important to set variables according to the country in which the Mediatrix 4104 is used because a number of parameter values are set according to this choice. These parameters are: ...

  • Page 199: Caller Id Selection

    To set a country location: In the telephonyMIB, locate the telephonyCountrySelection variable. This variable indicates the current country used by the Mediatrix 4104. It can also be used to select a caller ID standard in countries that support more than one caller ID standard.

  • Page 200: Custom Tone Configuration

    = [ ":f1" ] [ ":f2" ] [":f3" ] [ ":f4" ] time = ":" 2*5DIGIT loop-indicator = ":l" next-state = ":" ( "s1" / "s2" / "s3" / "s4" / "s5" / "s6" / "s7" ) Mediatrix 4104...

  • Page 201: Customizing The Tones

    Enter the override pattern in the corresponding countryCustomizationToneTone variable. You must follow the syntax as described in “Pattern Definition” on page 178. “Custom Tone Example” on page 180 for a detailed example on how to create a proper pattern. Mediatrix 4104...

  • Page 202: Custom Tone Example

    The general format of the pattern string now looks as follows: Pattern = [ f1=350:-17,f2=440:-17 [ "," loop-counter-section ] "," states- section ] Set the loop-counter-section category, which is defined as: loop-counter-section = "l=" loop-counter It defines the number of times to repeat the pattern. Mediatrix 4104...
  • Page 203 You can use from one to four frequencies. The North America stutter dial tone has two frequencies, thus: frequency-selection = [ ":f1" ] [ ":f2" ] on-state-description parameter is now: on-state-description = "on" [ ":f1" ] [ ":f2" ] ] [ time] [ loop-indicator ] [ next-state ] Mediatrix 4104...
  • Page 204 = ":l" It is used to stop looping between states. It indicates that the loop stops after three times. Once the loop is completed, the pattern goes to the next state (which is state 3). Mediatrix 4104...
  • Page 205 Since the third state is a continuous tone and does not use loops, this parameter is not required. on-state-description parameter is now: on-state-description = "on" [ ":f1" ] [ ":f2" ] [ next-state ] Mediatrix 4104...
  • Page 206 [ ",s3=" "on" [ ":f1" ] [ ":f2" ] ] ] ] If you remove all the brackets and quotation marks, which are not to be included, the pattern is: Pattern = f1=350:-17,f2=440:- 17,l=3,s1=on:f1:f2:100:s2,s2=off:100:1:s1,s3=on:f1:f2 Ther pattern could also be defined as follows: Pattern = f1=350:-17,f2=440:- 17,s1=on:f1:f2:100:s2,s2=off:100:s3,s3=on:f1:f2:100:s4,s4=off:100:s5,s5=on:f 1:f2:100:s6,s6=off:100:s7,s7=on:f1:f2 Mediatrix 4104...

  • Page 207: Configuration File Download

    Configuration File Download Server The service allows to download a unique file for each Mediatrix 4104, and/or a file shared among many units. These configuration files may be encrypted or not. You have the choice to perform the configuration file download by using the TFTP protocol, the HTTPS protocol or the HTTP protocol.

  • Page 208: Configuring The Https Server

    Certificates The Mediatrix 4104 contains embedded security certificates formatted as per ITU x.509 and RFC 3280. The certificates are factory-installed. The name of X.509 certificates currently installed in the Mediatrix 4104 are listed in the securityCertificatesMIB under the certificateName variable (under the certificateTable group). You must have at least one matching certificate on your HTTPS server.

  • Page 209: Configuration File Server Settings

     checking the server certificates validity (dates) The Mediatrix 4104 then checks the server’s identity by validating the host name used to contact it against the information found in the server’s certificate, as described in RFC 2818, section 3.1. If any of the above does not succeed, the Mediatrix 4104 refuses the secure connection. To help detect such errors, you can increase the syslog messages level.

  • Page 210: Setting Up The Configuration File Download

     To use static information: In the ipAddressConfig folder, locate the configFileFetchingSelectConfigSource variable. This variable defines whether the Mediatrix 4104 must ask for its configuration file server settings through a DHCP server or not. Set the configFileFetchingSelectConfigSource variable to static.
  • Page 211 • Cut and paste the path and/or name of the directory that contains the extracted files into the configuration file path of the Mediatrix 4104 (you may have to convert “\” into “/ ”) to eliminate typographical errors. Note that you can define the C:/Root/Download part as you want. The file names may also differ from the example shown above.

  • Page 212: Configuration Update Status

    If valid configuration files are successfully downloaded, then the Mediatrix 4104 automatically restarts to apply all the new settings. If the Mediatrix 4104 does not restart, this could mean the download failed or that the configuration in the file is the same as the configuration in the unit.

  • Page 213: Configuration Files Encryption

    Configuration Files Encryption You can secure the exchange of configuration files between the server and the Mediatrix 4104. A privacy key allows the unit to decrypt a previously encrypted configuration file. This applies to files downloaded via TFTP, HTTPS, or HTTP.

  • Page 214: Configuration Download Via Tftp

    Set the configFilePrivacyEnable variable to enable. The Mediatrix 4104 will be able to decrypt the next encrypted generic or specific configuration file. If this variable is set to disable, the configuration file is not decrypted by the unit and the configuration update fails.

  • Page 215: Configuration Download Via Http/Https

    The password in the configFileTransferPassword variable. In the groupAdminMIB, set the groupSetAdmin variable to ForceLock. All activities in progress on the Mediatrix 4104 are terminated immediately and the unit enters the maintenance mode (the value of the groupAdminState variable is “locked”). The configuration file download may take place.

  • Page 216: Automatic Configuration Update

    %%: A '%' sign. Restart the Mediatrix 4104 so that the changes may take effect. Automatic Configuration Update You can configure the Mediatrix 4104 to automatically update its configuration. This update can be done:  Every time the Mediatrix 4104 restarts.
  • Page 217 Configuration File Download Server Reference Manual (SIP Version) Automatic Update at a Specific Time Interval You can configure the Mediatrix 4104 to download new configuration files at a specific day and/or time.  To set the automatic update at a specific time interval: Set the configuration file server host and port as defined in “Configuration File Server Settings”...

  • Page 218: Error Handling

    The unit configuration is only updated if at least one parameter value defined in the downloaded configuration files is different from the actual unit configuration. If one of the telephones/faxes is off-hook, the Mediatrix 4104 will perform the update 5 minutes after both ports are detected on-hook.
  • Page 219 Send a syslog warning message including the violation) from the TFTP server. file name and location with the TFTP server address: The configuration file “XXX” was not fetched. There was a TFTP access violation with server “XXX”. Set sysAdminDownloadConfigFileStatus to fail. Mediatrix 4104...
  • Page 220 The HTTP server closed the Send a syslog warning message including the peer session. file location/name with the HTTP server address: The configuration file “XXX” HTTP transfer session was closed by peer: host “XXX”. Set sysAdminDownloadConfigFileStatus to fail. Mediatrix 4104...

  • Page 221: Management Server

    Set sysAdminDownloadConfigFileStatus to fail. Management Server You can set the Mediatrix 4104 so that it asks the management server to send it a configuration file. Note: Downloading a configuration file from the management server can only be performed through the TFTP protocol.

  • Page 222: Error Handling

    ASCII codes 10 invalid character (ASCII code): (LF), 13(CR), and 32 to 126. The configuration file “XXX” pushed to the unit by the TFTP client “XXX” has an invalid character “ASCII code XXX”. No recorded settings applied. Mediatrix 4104...

  • Page 223: Syslog Messages

    The notification “XXX” could not A SNMP trap could not be sent to the be sent to msHost “XXX” and management server. The syslog warning msTrapPort XXX. message includes the SNMP trap number, the management server address and port. Mediatrix 4104...

  • Page 224: Configuration File Example

    <MX_Config_File FileId="MX_MIBFILE" MIBVersionNumber="1.0" VersionNumber="1.0"> <Object Prefix="1.3.6.1.4.1.4935.15.1.8.1" Suffix="0" Value="0"/> <Object Prefix="1.3.6.1.4.1.4935.15.1.10.1" Suffix="0" Value="0"/> <Object Prefix="1.3.6.1.4.1.4935.15.1.10.10.1" Suffix="0" Value="192.168.0.10"/> <Object Prefix="1.3.6.1.4.1.4935.15.1.20.1" Suffix="0" Value="0"/> <Object Prefix="1.3.6.1.4.1.4935.15.3.1.30.1" Suffix="0" Value="0"/> <Object Prefix="1.3.6.1.4.1.4935.15.3.1.30.3" Suffix="0" Value="ConfigFile.xml"/> <Object Prefix="1.3.6.1.4.1.4935.15.15.1.5" Suffix="0" Value="0"/> <Object Prefix="1.3.6.1.4.1.4935.15.35.1.20.1.1" Suffix="3" Value="0"/> <Object Prefix="1.3.6.1.4.1.4935.15.35.1.20.1.1" Suffix="4" Value="0"/> </MX_Config_File> Mediatrix 4104...

  • Page 225: Supported Characters

    123 {, open curly bracket <, less than \, backslash 124 |, vertical bar =, equals ], close square bracket 125 }, close curly bracket 126 ~, tilde All other ASCII codes will result in an invalid configuration file. Mediatrix 4104...
  • Page 226 Chapter 12 - Configuration File Download Configuration File Example Mediatrix 4104...

  • Page 227: Software Download

    If you are to perform a software download by using the HTTP protocol, you must install a HTTP server running on the PC designated as the server host. This PC must not have a firewall running. Media5 also recommends to place the PC and the Mediatrix 4104 in the same subnet.

  • Page 228: Configuring The Https Server

    Certificates The Mediatrix 4104 contains embedded security certificates formatted as per ITU x.509 and RFC 3280. The certificates are factory-installed. The name of X.509 certificates currently installed in the Mediatrix 4104 are listed in the securityCertificatesMIB under the certificateName variable (under the certificateTable group). You must have at least one matching certificate on your HTTPS server.

  • Page 229: Software Servers Configuration

     checking the server certificates validity (dates) The Mediatrix 4104 then checks the server’s identity by validating the host name used to contact it against the information found in the server’s certificate, as described in RFC 2818, section 3.1. If any of the above does not succeed, the Mediatrix 4104 refuses the secure connection. To help detect such errors, you can increase the syslog messages level.

  • Page 230: Static Configuration

     To use static information: In the ipAddressConfig folder, locate the imageSelectConfigSource variable. This variable defines whether the Mediatrix 4104 must ask for its Image server settings through a DHCP server or not. Set the imageSelectConfigSource variable to static. Set the following variables:...

  • Page 231: Download Procedure

    The Mediatrix 4104 first downloads a file called “setup.inf”. This file contains the list of all the other files to download, depending on the product. The “setup.inf” file and all the other files must be in the same directory.
  • Page 232 This is the location of the “setup.inf” file that contains the list of the files to download into the Mediatrix 4104. The “setup.inf” file and all the other files must be in the same directory. In other words, this is the path from the root TFTP/HTTP/HTTPS folder down to the files extracted from the zip file.

  • Page 233: Software Download Status

    You can validate the status of the software download in various ways. Syslog Messages If you are using a Syslog daemon, you will receive messages that inform you of the software update status. The following are the syslog messages the Mediatrix 4104 sends: Table 132: Software Update Syslog Messages Level...
  • Page 234 When receiving TFTP error “ACCESS” or HTTP xxx on host: xxx is unauthorized response #401. LED States When the Mediatrix 4104 initiates a software download, the LEDs located on the front panel indicate the status of the process. Table 133: LED States in Software Download Event...

  • Page 235: Download Via Tftp

    Set the imageTransferProtocol variable to tftp. Set the groupSetAdmin variable (in the groupAdminMIB) to ForceLock. All activities in progress on the Mediatrix 4104 are terminated immediately and the unit enters the maintenance mode (the value of the groupAdminState variable is “locked”). The software upgrade may take place.

  • Page 236: Download Via Http/Https

    Download via HTTP/HTTPS The following steps explain how to download a software by using the HTTP protocol.  or HTTPS If you are using HTTPS, the Mediatrix 4104 must contain the proper certificate. See “Configuring the HTTPS Server” on page 206 for more details.To download a software via HTTP or HTTPS:...

  • Page 237: Automatic Software Update

    %%: A '%' sign. Restart the Mediatrix 4104 so that the changes may take effect. Automatic Software Update You can configure the Mediatrix 4104 to automatically update its software version. This update can be done:  Every time the Mediatrix 4104 restarts.
  • Page 238 Chapter 13 - Software Download Download Procedure Automatic Update at a Specific Time Interval You can configure the Mediatrix 4104 to download a software version at a specific day and/or time.  To set the automatic update at a specific time interval: If not already done, setup the Image server used to download the software (see “Before...

  • Page 239: Spanning Tree Protocol (Stp)

    The secondary image server is up and running well. In this case, the Mediatrix 4104 tries to contact the primary image server. As it is not available, the Mediatrix 4104 retries for two minutes. It contacts the secondary server after that period and starts the software download.

  • Page 240: Software Downgrade

    Chapter 13 - Software Download Software Downgrade Software Downgrade It is possible to downgrade a Mediatrix 4104 from the current version (for instance, v5.0rx.x) to an older version (for instance, v4.4rx.x). Note: If you perform a default reset on the Mediatrix 4104, you must download the current version into the unit before performing the software downgrade procedure.
  • Page 241 Emergency Software Procedure Reference Manual (SIP Version) If the emergency software download still fails, the Mediatrix 4104 tries to initiate the software download again by doubling the delay between each attempt up to a maximum of 16 minutes: • first attempt: 1 minute delay •...
  • Page 242 Chapter 13 - Software Download Emergency Software Procedure Mediatrix 4104...

  • Page 243: Line Configuration

    Temporary Administrative State You can set the administrative state of a line that will be kept until the Mediatrix 4104 restarts. Once the unit restarts, it uses the permanent state defined for each line. See “Permanent Administrative State”...

  • Page 244: Permanent Administrative State

    Using the “flash” button that is present on many standard telephone handsets can also trigger a flash hook. The Mediatrix 4104 allows you to set the minimum and maximum time within which pressing and releasing the plunger is actually considered a flash hook.

  • Page 245: Source Line Selection

    You can map an FXS line to a specific FXO line of a gateway such as the Mediatrix 1204. In this case, a call made from this FXS line will always use the same FXO line. To achieve that, the Mediatrix 4104 and Mediatrix 1204 configurations would be something similar to the following: Mediatrix 4104: IP address 192.168.0.1...

  • Page 246: Loop Current

    = 6662222 With such a configuration, a call made from line #2 of a Mediatrix 4104 is processed on line #2 of the Mediatrix 1204. On the other hand, if a caller from the SCN calls line #3 of the Mediatrix 1204, the call is automatically redirected to line #3 of the Mediatrix 4104.

  • Page 247: Callee Hang-Up Supervision

    Enable the callee hang-up supervision feature by setting the fxsCalleeHangupSupervision variable to enable. When the user is the first to hang up on a received call, the Mediatrix 4104 waits for the amount of time set in the fxsCalleeHangupDelay variable before signalling the end of the call.

  • Page 248: Line Reversal

    They are used because of an inability by some customer's CPE to react to busy tone. When one of the options is activated, it replaces the default behaviour of the Mediatrix 4104, which is to briefly remove power from the line to signal that the remote party has hung up.

  • Page 249: Calling Number Transformation

    ® Technology---Portable Operating System Interface (POSIX A regular expression is a string used to find and replace strings in other large strings. The Mediatrix 4104 uses regular expressions to enter a value in the fxsCallingNumberCriteria variable, often by using wildcard characters.
  • Page 250 (defined by “\1” to “\9”) and matching is not case sensitive. “\0” represents the whole string. Lets say for instance you have the following string: 9(123(45)6) The following describes how the groups are replaced: Table 141: Groups Replacement Example Replacement Result 9123456 123456 Mediatrix 4104...

  • Page 251: Voice Transmissions

    Codec Descriptions The four lines of the Mediatrix 4104 can simultaneously use the same codec (for instance, G.711 PCMA), or a mix of any of the supported codecs. Set and enable these codecs for each line. Table 142: Codecs Comparison...

  • Page 252: G.726

    244 for more details. Analog Modem The Mediatrix 4104 can send modem transmissions in clear channel (G.726). If configured adequately, modems with higher rate capabilities (for instance, V.90) will automatically fall back in the transmission range supported Quality of modem transmissions is dependent upon the system configuration, quality of the analog lines, as well as the number of analog-to-digital and digital-to-analog conversions.

  • Page 253: Preferred Codec

    Preferred Codec Reference Manual (SIP Version) The Mediatrix 4104 supports G.729A and G.729AB for encoding and G.729, G.729A and G.729AB for decoding. Table 146: G.729 Features Feature Description Packetization time Range of 10 ms to 100 ms with increment of 10 ms. See “Packetization...

  • Page 254: Packetization Time

    235), you cannot configure a dynamic payload type to 111 because it is already used by the DTMF out-of-band using signalling protocol. Restart the Mediatrix 4104 so that the changes may take effect. Packetization Time The packetization time (also called packetization period or ptime) is the duration, in ms, of the voice packet.
  • Page 255 Longest packetization period allowed for the 10-100, with increments PTime G.726-16kbps codec. Authorized values go up of 10 to 100 ms, in discrete steps of 10 ms, and start at the one specified by the voiceIfCodecG72616kbpsMinPTime variable. Default Value: 100 Mediatrix 4104...
  • Page 256 Longest packetization period allowed for the 10-100, with increments G.729 codec. Authorized values go up to of 10 100 ms, in discrete steps of 10 ms, and start at the one specified by the voiceIfCodecG729MinPTime vartiable. Default Value: 100 Mediatrix 4104...

  • Page 257: Dtmf Transport Type

    DTMF sequence back by re- generating the true tones. Such a mechanism is known as out-of-band DTMF. The Mediatrix 4104 receives and sends out-of-band DTMFs as per ITU Q.24. DTMFs supported are 0-9, A-D, *, #.

  • Page 258: Dtmf Transport Using Sip Info

    When the feature is enabled:  The Mediatrix 4104 sends a separate SIP INFO method every time a digit is entered during the call.  The Mediatrix 4104 plays each DTMF sent in a separate message upon receiving a valid SIP INFO message.

  • Page 259: Dtmf – Rfc 2833 Events

    235), or the variable telephonyAttributesHookFlashProcessing to outOfBandUsingRtp (“Hook Flash Processing” on page 322), the Mediatrix 4104 will advertise the support for events 0-15; it will assume support for events 0-15 when support for RFC 2833 is received in an announcement. disable This creates a deliberate deviance to RFC 2833 as support of basic events is not automatic.

  • Page 260: Dtmf Detection

    Restart the Mediatrix 4104 so that the changes may take effect. DTMF Detection The default DTMF detection parameters of the Mediatrix 4104 may sometimes not be enough to properly detect the DTMFs. This section describes how to set additional DTMF detection parameters.

  • Page 261: Dtmf Detection Configuration

    Figure 79: DTMF Detection Example To detect this DTMF, the DSP relies on several parameters. The following table lists the default values that the Mediatrix 4104 uses. You can override any one of these values. Table 154: DTMF Detection Default Parameters...
  • Page 262 Disabling the Step Rise criteria may result in deteriorated talk-off performance, but increases the detection of malformed DTMF. The Confirm DTMF SNR criteria is an additional Signal-to-noise ratio test performed before a confirmed DTMF report is sent to finally validate the DTMF. Mediatrix 4104...

  • Page 263: Adaptative Jitter Buffer

    Mediatrix 4104 is connected suffers from a high level of congestion, the jitter buffer protection level should be higher. If the network to which the Mediatrix 4104 is connected suffers from a low level of congestion, the jitter buffer protection level should be lower.

  • Page 264: Voice Activity Detection

    Voice Activity Detection Voice Activity Detection The Voice Activity Detection (VAD) defines how the Mediatrix 4104 sends information pertaining to silence. This allows the unit to detect when the user talks, thus avoiding to send silent RTP packets. This saves on network resources.

  • Page 265: Echo Cancellation

    You can disable the echo cancellation feature of the Mediatrix 4104, which may be useful to ensure the success of some modem transmissions.

  • Page 266: Comfort Noise

    You can compensate with the user gain if there is no available configuration for the country in which the Mediatrix 4104 is located. Because the user gain is in dB, you can easily adjust the loss plan (e.g., if you need an additional 1 dB for analog to digital, simply put 1 for user gain input).
  • Page 267 Values range from -30 dB to +20 dB. However, going above +6 dB may introduce clipping/distortion depending on the country selected. Under -24 dB, you will not have much signal either. Restart the Mediatrix 4104 so that the changes may take effect. Mediatrix 4104...
  • Page 268 Chapter 15 - Voice Transmissions User Gain Mediatrix 4104...

  • Page 269: Fax Transmission

    Upon fax termination, if the call is not BYE, the previous voice codec is recovered with another re- INVITE. All lines of the Mediatrix 4104 can simultaneously use the same codec (for instance, T.38), or a mix of any of the supported codecs. Set and enable these codecs for each line.

  • Page 270: Ced Fax Tone Detection

    This configuration has no effect if the dataIfCngToneDetectionEnable variable is set to enable. Analog CED Detection Behaviour You can define the behaviour of the Mediatrix 4104 upon reception of a CED fax tone from the analog port.  To define the analog CED detection behaviour: In the dataIfMIB, set the dataIfAnalogCedDetectionBehavior variable with the proper value.

  • Page 271: Clear Channel Fax

    Clear Channel Fax Reference Manual (SIP Version) Clear Channel Fax The Mediatrix 4104 can send faxes in clear channel. The following is a clear channel fax call flow: Figure 80: Clear Channel Fax Call Flow INVITE […] […] m=audio 5006 RTP/AVP 18 0 13...
  • Page 272 “Data Codec Selection Procedure” on page 251 for more details. Media5 suggests to use pcma if you are located in Europe and pcmu anywhere else. However, you should check first which codec is supported in your telephone network. Mediatrix 4104...

  • Page 273: Data Codec Selection Procedure

    Data Codec Selection Procedure The Mediatrix 4104 follows a procedure when selecting data codec. This procedure is the default behaviour of the Mediatrix 4104. Some interop variables may modify this procedure. Tones are detected on the analog ports only. Figure 81: Data Codec Selection Procedure...

  • Page 274: T.38 Fax

    The Mediatrix 4104 can send faxes in T.38 mode over UDP or TCP. T.38 is used for fax if both units are T.38 capable; otherwise, transmission in clear channel over G.711 as defined is used (if G.711 µ-law and/or G.711 A-law are enabled).

  • Page 275: T.38 No-Signal

    Restart the Mediatrix 4104 so that the changes may take effect. T.38 No-Signal You can set the Mediatrix 4104 to send no-signal packets during a T.38 fax transmission. The Mediatrix 4104 sends no-signal packets if no meaningful data have been sent for a user-specified period of time.

  • Page 276: T.38 Invite Rejected With 606

    Chapter 16 - Fax Transmission T.38 Fax T.38 INVITE Rejected with 606 You can define the behavior of the Mediatrix 4104 when receiving a 606 SIP error response to an INVITE for T.38 fax.  To define the behavior In the sipInteropMIB, set the sipInteropBehaviorOnT38InviteRejectedWith606 variable to the proper value.

  • Page 277: Bypass Configuration

    H A P T E R Bypass Configuration The Mediatrix 4104 may have an optional RJ-11 connector used to connect to a standard SCN line, called Bypass. It allows its users to maintain telephone services in the event of a power outage or network failure.
  • Page 278 Chapter 17 - Bypass Configuration Bypass Connector Settings Mediatrix 4104...

  • Page 279: Sip Protocol Features

    A user agent is a logical entity that can act as both client and server for the duration of a dialog. Each line (also known as endpoint) of the Mediatrix 4104 is a user agent. You can set information for each user agent such as its telephone number and friendly name. This information is used to dynamically create the To, From and Contact headers used in the request the user agent sends.

  • Page 280: Home Domain Override

    The User-Agent header field contains information about the user agent client originating the request. For instance, the information of the User-Agent header could be something like the following: User-Agent: Softphone Beta1.5 You can specify whether or not the Mediatrix 4104 sends this information when establishing a communication and customize the header value. ...

  • Page 281: Session Timers

    • draft-ietf-sip-session-timer-04.txt (expired) You can select the version of the session timer draft that the Mediatrix 4104 uses. Session timer versions other than those provisioned may not work because of backward compatibility issues between the versions. This feature is currently located under the mediatrixExperimental branch of the MIB structure. See “MIB...

  • Page 282: Background Information

    You can also set these parameters via the web interface, as described in “SIP Authentication” on page Line-Specific Authentication You can define up to five user names and five passwords for each line of the Mediatrix 4104. A line can thus register with five different realms. Keep in mind that: ...

  • Page 283: Unit Authentication

    Unit Authentication You can define up to five user names and five passwords for the Mediatrix 4104. These user names and passwords apply to all lines of the unit. In the Unit Manager Network Administration Manual, refer to chapter Signalling Protocols Parameters, section SIP Authentication.

  • Page 284: Sip Trusted Sources

    SIP Trusted Sources You can configure the Mediatrix 4104 so that it only accepts SIP messages coming from one of six trusted IP addresses. All other SIP messages are ignored. This source address validation takes place at the IP level and does not depend on the SIP header or body.

  • Page 285: Mediatrix 4104 Configuration

    RFC 3261 – SIP: Session Initiation Protocol You can globally set the transport type for all the lines of the Mediatrix 4104 to either UDP (User Datagram Protocol) or TCP (Transmission Control Protocol). The Mediatrix 4104 will include its supported transports in its registrations.

  • Page 286: Transport Parameter

    UDP Source Port Behaviour You can configure if the Mediatrix 4104 always uses the same local port (the port on which it is listening for incoming packets) when sending SIP traffic over UDP. This is called symmetric UDP source port. Symmetric UDP ports are sometimes needed to traverse NAT/Firewall devices.

  • Page 287: Sip Penalty Box

    The Mediatrix 4104 skips over UDP and tries the next target, which is TCP. Again, TCP is still in the penalty box, but this time, it is the last target the Mediatrix 4104 can try, so penalty box or not, TCP is used all the same to try to contact endpoint “B”.

  • Page 288: Registration Parameters

    (43 seconds before the unit becomes unregistered). Note: Normally, the Mediatrix 4104 cannot make or receive calls until the REGISTER has completed successfully. Because the timeout for a SIP transaction in UDP is 32 seconds, it is possible to have an ongoing re-REGISTER transaction at the same moment that the registration itself expires.

  • Page 289: Default Registration Expiration

    “Refreshing Registration” on page 266 for more details. The recommended value in RFC 3261 (section 10.2) is 3600 seconds. Restart the Mediatrix 4104 so that the change may take effect. Publication Parameters Standards Supported • RFC 3863 – Presence Information Data Format (PIDF) •...

  • Page 290: Publications Expiration

    The delay before a re-PUBLISH is the value set in the sipInteropDefaultPublicationExpiration variable minus the value set in the sipPublicationRefreshTime variable. See “Refreshing Publications” on page 267 for more details. Restart the Mediatrix 4104 so that the change may take effect. Mediatrix 4104...

  • Page 291: Interop Parameters

    RFC 3515 - The Session Initiation Protocol (SIP) (Refer Method) You can select the version of the transfer draft that the Mediatrix 4104 uses. The provisioned version is used for initiating transfers and receiving them. Transfer versions other than those provisioned do not work.
  • Page 292 This allows you to control how the Mediatrix 4104 interoperates with other vendor’s products and older Mediatrix units.

  • Page 293: Transmission Timeout

    RFC 3261 – SIP: Session Initiation Protocol If a DNS SRV answer contains more than one entry, the Mediatrix 4104 will try these entries if the entry initially selected does not work. You can configure the maximum time, in seconds, to spend waiting for answers to messages, from a single source.

  • Page 294: Referred-By Field

    Protocol (SDP) You can define:  if the SDP direction attribute is present in the initial INVITE sent by the Mediatrix 4104  whether or not the direction attribute present in the SDP received from the peer is ignored ...
  • Page 295 RFC 3264 – An Offer/Answer Model with Session Description Protocol (SDP) The Mediatrix 4104 can provide the direction attribute and the meaning of the connection address “0.0.0.0” sent in the SDP when putting an endpoint on hold. This configuration has no effect if the sipInteropSdpDirectionAttributeEnable variable is set to Disable (see “Direction Attribute”...

  • Page 296: Allowing Multiple Active Media In Answer

    Other media are set to inactive Local Ring Behaviour on Provisional Response You can set the Mediatrix 4104 so that it starts or not the local ring upon receiving a “18x Provisional” response without SDP. This setting does not affect the behaviour when the “18x Provisional” response contains SDP, which allows to establish an early media session before the call is answered.

  • Page 297: Sip Credential

    The local ring is started on any “18x Provisional” response without SDP. SIP Credential You can configure how the Mediatrix 4104 reuses the credential in different transactions of the same call or registration. For instance, it may be required that a new SIP request does not reuse the credential negotiated in the previous transaction of the same call or registration.

  • Page 298: Ringing Response Code

    URI-Parameters You can specify whether or not the Mediatrix 4104 copies the uri-parameters from the Request-URI header to the level of proxy authentication. Not copying the uri-parameters allows to reduce the SIP packet size but it does not follow the recommendations of RFC 3261.

  • Page 299: Unsupported Info Request

    In the sipInteropMIB, set the sipInteropProxyAuthenticationUriParametersEnable variable to enable. Unsupported INFO Request You can define the Mediatrix 4104’s behaviour upon reception of an unknown type of INFO request.  To define the unsupported INFO request behaviour: In the sipInteropMIB, set the sipInteropAckUnsupportedInfoRequests variable with the proper behaviour.

  • Page 300: T.38 Negotiation Syntax

    In the sipInteropMIB, set the sipInteropUseSipDomainInRequestURI variable with the proper behaviour. Table 182: SIP Domain in Request URI Behaviour Parameter Description disable The request URI is built using the home domain proxy host as defined in “Proxy Server” on page 165. Mediatrix 4104...

  • Page 301: Sip From: Uri Content

    The default behaviour when sending an initial offer that contains an RFC 2833 payload type is to keep using that payload type even if the response comes back with a different one. You can set the Mediatrix 4104 to rather use the payload type found in the answer.

  • Page 302: Controlling The Call Waiting Tone Via Sip Info

    The default behaviour when receiving an answer to an offer that contained an RFC 2833 payload type is to use that payload type symmetrically (to send and receive DTMF). You can set the Mediatrix 4104 to rather use the payload type that was placed in the initial offer to receive DTMF but still use the one in the response to send them.

  • Page 303: Ignore Username Parameter

    The default behaviour in the interpretation of the username parameter of an incoming request for the routing purpose is to compare the entire username. You can configure the Mediatrix 4104 so that it ignores the username parameter in the comparison.

  • Page 304: Offer/Answer Model

    RFC 3264 – An Offer/Answer Model with the Session Description Protocol (SDP) You can define whether or not the Mediatrix 4104 requires strict adherence to RFC 3264 from the peer when negotiating capabilities for the establishment of a media session.

  • Page 305: Allow Audio And Image Negotiation

    Offer/Answer model. Allow Audio and Image Negotiation You can define the behaviour of the Mediatrix 4104 when offering media or answering to a media offer with audio and image negotiation.

  • Page 306: Udp Checksum

     To enable UDP checkum: In the sipExperimentalMIB, set the sipRtpUdpChecksumEnable variable to enable. The UDP checksum is calculated for each RTP packet. Note that this may affect performance. The parameter takes effect on the next connection. Mediatrix 4104...

  • Page 307: Stun Configuration

    For a unit to work properly behind a firewall, it must keep a pinhole opened by sending keepalive packets through the firewall. The Mediatrix 4104 only sends keepalive packets to the last destination for a specific socket. When a unit is not configured with an outbound proxy, it can send, through its SIP socket, messages to various destinations, such as a SIP redirect server, another SIP unit, or a MWI server.

  • Page 308: Stun Client Configuration

    Chapter 19 - STUN Configuration STUN Client Configuration STUN Client Configuration The following describes how to configure the Mediatrix 4104 STUN client via SNMP. You can also use the web interface to configure the STUN parameters. See “STUN Configuration” on page 119 for more details.

  • Page 309: Sntp Settings

    Enabling the SNTP Client Standards Supported RFC 1769 – Simple Network Time Protocol (SNTP) You must enable the SNTP client of the Mediatrix 4104 to properly connect to a a SNTP or NTP server.  To enable the SNTP feature: In the sntpMIB, set the sntpEnable variable to enable.

  • Page 310: Configuration Source

    Configuration Source Configuration Source The Mediatrix 4104 must know the IP address and port number of the SNTP server. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself with the static variables.

  • Page 311: Defining A Custom Time Zone

    Greenwich Mean Time (GMT) format (also known as Universal Time Coordinated - UTC), so it needs to convert this GMT time into the proper time zone. To do this, the Mediatrix 4104 offers time zone configuration with daylight saving settings.

  • Page 312: Example

    Eastern Time Canada & US) EST5EDT4,M3.2.0/02:00:00,M11.1.0/02:00:00 Atlantic Time (Canada) AST4ADT3,M3.2.0/02:00:00,M11.1.0/02:00:00 GMT Standard Time GMT0DMT-1,M3.5.0/01:00:00,M10.5.0/02:00:00 W. Europe Standard Time WEST-1DWEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 China Standard Time CST-8 Tokyo Standard Time TST-9 Central Australia Standard Time CAUST-9:30DCAUST-10:30,M10.5.0/02:00:00,M3.5.0/02:00:00 Australia Eastern Standard Time AUSEST-10AUSDST-11,M10.5.0/02:00:00,M3.5.0/02:00:00 UTC (Coordinated Universal Time) UTC0 Mediatrix 4104...

  • Page 313: Digit Maps

    Because the Mediatrix 4104 cannot predict how many digits it needs to accumulate before transmission, you could use the digit map, for instance, to determine exactly when there are enough digits entered from the user to place a call.

  • Page 314: Special Characters

    Special Characters The solution to this problem is to load the Mediatrix 4104 with a digit map that corresponds to the dial plan. A Mediatrix 4104 that detects digits or timers applies the current dial string to the digit map, attempting a match to each regular expression in the digit map in lexical order.

  • Page 315: Using The # And * Characters

    It indicates that if users have not dialed a digit for the time defined, it is likely that they have finished dialing and the Mediatrix 4104 can make the call. A digit map for this could be:...

  • Page 316: Processing Digits When Pressed

    The variables related to the digit maps are located in tables. You can create/edit ten digit maps for each Mediatrix 4104. Before changing a parameter value, build its corresponding table with your MIB browser’s table functionality. Depending on the MIB browser you are using, the tables may not appear the same way.

  • Page 317: Refused Digit Maps

    Refused Digit Maps A refused digit map forbids your users to call specific numbers; for instance, you want to accept all 1-8xx numbers except 1-801. You can create/edit ten refused digit maps for each Mediatrix 4104.  To set up refused digit maps: In the digitMapMIB, define the digit map string that is considered invalid when dialed in the digitMapRefusedDigitMap variable.

  • Page 318: Digit Maps Timeouts

    This digit map rule checks for calls outside the country. Table 201: Digit Map Rules #1 Settings Variable Setting digitMapAllowedEnable Enable digitMapAllowedDigitMap (011x.#|001x.T) digitMapPrefixedDigitRemovalCount A valid telephone number must contain a country code, an area code, and a number – the “011” part is not required. Mediatrix 4104...
  • Page 319 ([235-9]xxxxxx|45[1-9]xxxx|4[0-469]xxxxx) digitMapPrependedString 1206 (country code and area code) A valid telephone number must contain a country code, an area code, and a number. The country code and area code are missing in this number and must be added. Mediatrix 4104...

  • Page 320: Digit Map Example 2 – Pbx Emulation

    (in North America). The two digits must be removed because they do not need to be expressed to the SIP Server. The SIP Server needs only to know the complete number of the called party (CC+AC+directory number). Mediatrix 4104...
  • Page 321 1819 (country code and area code) A valid telephone number must contain a country code, an area code, and a number. The country code and area code are missing in this number and must be added. Mediatrix 4104...
  • Page 322 Chapter 21 - Digit Maps Digit Map Examples Mediatrix 4104...

  • Page 323: Telephony Features

    H A P T E R Telephony Features This chapter explains how to set the telephony variables of the Mediatrix 4104 to define the way the unit handles calls. Making Calls Users with telephones or faxes connected to a Mediatrix 4104 dial as if they were on a standard telephony system.

  • Page 324: Emergency Call

    291). Dialing this digit map does not have any effect unless the service's status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have different sequences for each line. Set the number to reach for an urgent call in the emergencyCallUrgentGatewayTargetAddress variable.

  • Page 325: Subscriber Services

    H A P T E R Subscriber Services The Mediatrix 4104 offers subscriber services users can directly access on their telephone. However, you must set these services before they can be used. Most of the variables related to the subscriber services are located in tables. These tables display the information for all lines.

  • Page 326: Call Hold

    The user can resume the call in the same way. You must enable this service for the following services to work properly:  Call Waiting  Second Call  Blind Transfer  Attended Transfer  Conference Mediatrix 4104...

  • Page 327: Enabling Call Hold

    To use the second call service: Perform a Flash-Hook by pressing the “Flash” button on your analog telephone. This puts the call on hold and the second line is automatically connected to your line. Initiate the second call. Mediatrix 4104...

  • Page 328: Call Forward

    291). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to stop the service in the subscriberServicesCallForwardUnconditionalDisableDigitMap variable (under the subscriberServicesActivationDigitmaps group).
  • Page 329 Dial the sequence the system administrator has implemented to deactivate the call forward – unconditional service. This sequence could be something like *71. Wait for three “beeps” followed by a silent pause. The call forward is cancelled. Hang up your telephone. Mediatrix 4104...
  • Page 330 291). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to stop the service in the subscriberServicesCallForwardOnBusyDisableDigitMap variable (under the subscriberServicesActivationDigitmaps group).
  • Page 331 Dial the sequence the system administrator has implemented to deactivate the call forward on busy service. This sequence could be something like *73. Wait for three “beeps” followed by a silent pause. The call forward is cancelled. Hang up your telephone. Mediatrix 4104...

  • Page 332: On No Answer

    291). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to stop the service in the subscriberServicesCallForwardOnNoAnswerDisableDigitMap variable (under the subscriberServicesActivationDigitmaps group).
  • Page 333 Dial the sequence the system administrator has implemented to deactivate the call forward on no answer service. This sequence could be something like *75. Wait for three “beeps” followed by a silent pause. The call forward is cancelled. Hang up your telephone. Mediatrix 4104...

  • Page 334: Call Waiting

    291). Dialing this digit map does not have any effect unless the service’s status is “enabled”. The deactivating sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. Define the digits that users must dial to enable the call waiting service permanently in the subscriberServicesCallWaitingPermanentDigitMapEnable variable.

  • Page 335: Using Call Waiting

    “Chapter 21 - Digit Maps” on page 291). The sequence is set for all the lines of the Mediatrix 4104. You cannot have a different sequence for each line. When dialing this digit map, this sets the subscriberServicesCallWaitingEnable variable for the line the user is currently using to disable.

  • Page 336: Permanently Removing The Call Waiting Tone

    Dial the sequence the system administrator has implemented to deactivate the call waiting tone service. This sequence could be something like *85. Wait for the transfer tone (three “beeps”) followed by the dial tone. The call waiting is cancelled. Hang up your telephone. Mediatrix 4104...

  • Page 337: Call Transfer

    You are back with the first call and the third party is released.  To transfer a call on hold with the flash hook and digit method: Perform a Flash-Hook by pressing the “Flash” button on your analog telephone. Dial the digit 4. Mediatrix 4104...

  • Page 338: Attended Transfer

    Flash-Hook. The busy tone or ring tone is cancelled and you are back with the first call.  To transfer a call on hold with the flash hook and digit method: Perform a Flash-Hook by pressing the “Flash” button on your analog telephone. Dial the digit 4. Mediatrix 4104...

  • Page 339: Conference Call

    If this is not the case, then part of the conversation may be lost, resulting in a choppy voice. For better results, Media5 recommends to set the packetization period of all participants of a 3-way conference to 30 milliseconds. See “Packetization Time”...

  • Page 340: Enabling The Conference Call Feature

    RFC 4579. The participants are connected to the conference server by sending the REFERs sequentially. The REFER is not sent to the second participant and the call stays in the same state if the first participant fails to complete the REFER. This is the default value. Mediatrix 4104...

  • Page 341: Managing A Conference Call

    “A” wants to add a fourth member to the conference: This is available only in the converenceServer conference type. “A” performs a Flash-Hook. This puts “B” and “C” on hold and the second line is automatically connected. “A” hears a dial tone. Mediatrix 4104...
  • Page 342 Chapter 23 - Subscriber Services Conference Call “A” dials “D’s” number. “A” and “D” are now connected. “A” performs another Flash-Hook. The call on hold (“B” and “C”) is reactivated. “A” is now conferencing with “B”, “C”, and “D”. Mediatrix 4104...

  • Page 343: Telephony Attributes

    This string is used literally, so cosmetic symbols (such as the dash in “555-xxxx”) should not be present. Because this variable is located in a table, you can define a different number for each line of the Mediatrix 4104. Enable the automatic call feature by setting the telephonyAttributesAutomaticCallEnable variable to enable.

  • Page 344: Call Direction Restriction

    The Mediatrix 4104 allows to make calls but cannot receive calls. ipToScnOnly The Mediatrix 4104 allows to receive calls but does not allow to make calls. Because this variable is located in a table, you can define a different call direction for each line of the Mediatrix 4104.

  • Page 345: Ip Address Call Service

    Dial the telephone number of the specific line you want to reach. For example, let’s say you want to reach the telephone connected to Line 2 of the Mediatrix 4104 with the IP address 192.168.0.23. The phone number assigned to Line 2 of this Mediatrix 4104 is 1234.

  • Page 346: Pin Dialing

    This feature could be used in the case where a user makes an automatic call to an IVR system, and after a pre-defined delay, the Mediatrix 4104 sends the DTMF tones (PIN) to indicate where the call is coming from.

  • Page 347: Remote Line Extension

    Description disable The Mediatrix 4104 picks up the SCN line and opens the audio channel with the peer. This way, the user of a dedicated FXS/FXO combinaison will feel “closer” to the SCN: as soon as the user takes the receiver off-hook, he/she interacts with the SCN because the actions are not relayed via IP to the FXO unit.

  • Page 348: Delayed Hot Line

    Enable the delayed hot line feature by setting the telephonyAttributesDelayedHotLineEnable variable to enable. When the feature is disabled, a user picking up the phone but not pressing any telephone keys hears the Receiver Off-Hook tone after the amount of time specified in the digitMapTimeoutFirstDigit variable. Mediatrix 4104...

  • Page 349: Call Rejection

    504: Server time-out 415: Unsupported media type 504: Version Not Supported 416: Unsupported URI Scheme 513: Message Too Large 420: Bad extension 600: Busy everywhere 421: Extension Required 603: Decline 423: Interval Too Brief 604: Does not exist anywhere Mediatrix 4104...
  • Page 350 Chapter 24 - Telephony Attributes Call Rejection Mediatrix 4104...

  • Page 351: Message Waiting Indicator

    The caller can then leave a message. After the message is recorded, the server sends a message to the Mediatrix 4104 listing how many new and old messages are available. The Mediatrix 4104 alerts the user of the new message in two different ways: ...
  • Page 352 291). Dialing this digit map does not have any effect unless the service's status is “enabled”. The activating sequence is set for all the lines of the Mediatrix 4104. You cannot have different sequences for each line. Set the destination to call to retrieve messages in the mwiConfigFetchAddress variable.

  • Page 353: Mwi Method #2

    This method does not require any special settings or configuration. MWI Notify Service The Mediatrix 4104 offers the possibility to extend some key features to remote extensions located in Branch or Home Offices across the SCN. This service is available only when using the IP Communication Server v3.1 product as a SIP Redirect server.

  • Page 354: Configuring The Ip Communication Server

    For more information on how to configure the Route Manager, please refer to the IP Communication Server Administration Manual or the IP Communication Server contextual help. Configuring the Mediatrix 4104 There is no special unit configuration required. The Mediatrix unit behaves as if in a standard call until it receives one of the following parameters in the Contact field: ...

  • Page 355: Management Server Configuration

    Using the Management Server You have the choice of setting up Mediatrix 4104 units directly with a SNMP browser or with the Management Server. If you want to use the Management Server to setup the units, you shall tell these units how to reach the Management Server.
  • Page 356  To use static information: In the ipAddressConfig folder, locate the msSelectConfig Source variable. This variable defines whether the Mediatrix 4104 shall get its Management Server configuration through a DHCP server or not. Set the msSelectConfigSource variable to static. Set the following variables:...

  • Page 357: Quality Of Service (Qos)

    – one variable for signalling (SIP) and one variable for each of voice and T.38 media. The Mediatrix 4104 supports the Real Time Control Protocol (RTCP), which is used to send packets to convey feedback on quality of data delivery.

  • Page 358: Ieee 802.1Q

    RFC 3168 now defines the state in which to set the two least significant bits in the TOS byte. On the other hand, this RFC only applies to TCP transmissions and the bits are thus set to “0” in the Mediatrix 4104.

  • Page 359: Voice Qos Vs Rtcp Packets

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0x8100 | Pri |T| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ For both signalling and media packets, the VLAN priority section is configurable independently. Mediatrix 4104...

  • Page 360: Vlan Substitution

    For more information, please refer to the MIB Reference manual. VLAN Substitution The Mediatrix 4104 can tag the packets relayed from the ETH2 (LAN) port to the ETH1 (WAN) port with a VLAN ID different from the standard value defined in “VLAN”...

  • Page 361: Lan And Wan With Vlan Substitution

    Mediatrix 4104 could then use this address to contact the Mediatrix 4104. For more information on how to set the ETH2 (LAN side) connector IP address of the Mediatrix 4104, refer to “ETH2 Connector Static IP Address” on page 151.
  • Page 362 Chapter 27 - Quality of Service (QoS) VLAN Mediatrix 4104...

  • Page 363: Syslog Daemon

    Syslog daemon address is provided by a DHCP server or specified by the administrator, no messages are sent. For instance, if you want to download a new software into the Mediatrix 4104, you can monitor each step of the software download phase. Furthermore, if the unit encounters an abnormal behaviour, you may see accurate messages that will help you troubleshoot the problem.

  • Page 364: Configuration Source

    Syslog Daemon Configuration Configuration Source The Mediatrix 4104 must know the IP address and port number of the Syslog server. You can assign these information to the Mediatrix 4104 through a DHCP server or manually enter them yourself with the static variables.

  • Page 365: Customizing Syslog Messages

    Syslog server static IP port number. Default Value: 514 Customizing Syslog Messages You can display additional information in the prefix of syslog messages the Mediatrix 4104 sends. This allows you to later filter the messages. The following is the additional information you can enable: ...
  • Page 366 Chapter 28 - Syslog Daemon Syslog Daemon Configuration Mediatrix 4104...

  • Page 367: Statistics

    H A P T E R Statistics The Mediatrix 4104 collects meaningful statistics that can be read via the RTP MIB. RTP Statistics RTP statistics are related to the transmission of information and include, but are not limited to: ...

  • Page 368: Statistics By Syslog

    In the sysAdminMIB, set the sysAdminCommand variable to resetStats. This resets all cumulated call statistics. Statistics by Syslog You can configure the Mediatrix 4104 to send the RTP and T.38 statistics by syslog message. You will thus be able to see them by using your syslog daemon. ...

  • Page 369: Example

    130. 50 total octets transmitted in the sixth 5-minutes period. The previous statistics are transferred to the corresponding cumulated statistics variable. The statistics for the second 5-minutes period are dropped, for a cumulated total octets transmitted of 200. Mediatrix 4104...
  • Page 370 Chapter 29 - Statistics RTP Statistics Mediatrix 4104...

  • Page 371: Maximum Transmission Unit (Mtu)

    The Mediatrix 4104 MTU is 1500 bytes, which is the Ethernet typical value. Possible Hardware Problem The implementation of the IEEE Standard 802.1q in the Mediatrix 4104 may have a minor problem because of hardware limitations. 802.1q increases the Ethernet frame header by 4 bytes, adding a Virtual LAN ID and a user_priority. This is useful to limit broadcasts that cross bridges, and it may also prioritize frames in the queuing algorithm of switches.
  • Page 372 MTU. Values smaller than 68 will result in the transport using an MTU of 68. To validate that the changes are correct, try to ping the Mediatrix 4104 with large packets once restarted: ping -l 2000 This will cause IP fragmentation, the first fragment being as large as the interface allows it.

  • Page 373: Troubleshooting

    DHCP server cannot be reached, even if most other settings are set to “static”. This delay is caused by the Mediatrix 4104 that cannot function as configured if part of its configuration (the DHCP information) is unavailable.
  • Page 374 • DHCP Server IP address: 192.168.0.20 If you happen to change the Mediatrix 4104 IP address to 192.169.0.1, for instance, the subnet mask is still valid, but cannot reach your DHCP server anymore. Refer to subnet mask documentation for more details.
  • Page 375 ], close square bracket 125 }, close curly bracket 126 ~, tilde : Media5 Technical Support personnel asked me to enable the PCM traces. How do I do it? ESCRIPTION  : PCM traces are an efficient tool to identify problems with:...

  • Page 376: Calling Issues

    OSSIBLE AUSE between the refresh and the SIP timeouts. Normally, the Mediatrix 4104 cannot make or receive calls until the REGISTER request has completed successfully. Because the timeout for a SIP transaction in UDP is 32 seconds, it is possible to have an ongoing re-REGISTER transaction at the same moment that the registration itself expires.

  • Page 377: Fax Issues

    Mediatrix 4104. : Unable to establish a call from the Mediatrix 4104 to a user agent such as an IP phone, a ESCRIPTION gateway or another access device.

  • Page 378: Tested Fax Models

    : There is no solution. OLUTION Tested Fax Models The following table lists the fax models tested with the Mediatrix 4104 for the T.38 protocol. Each of these fax ® models has been emulated and tested with each other by using the FaxLab fax/telephony testing tool.

  • Page 379: Issues Arising From Specific Combinations/Scenarios

    LaserJet 3200 • OfficeJet 570 Issues Arising from Specific Combinations/Scenarios The following are very specific issues the Mediatrix 4104 may experience with certain types of faxes. : Fax in T.38 fails with particular fax machines and fax test sheet. ESCRIPTION ...

  • Page 380: Configuration Issues

    : If none of the xxxConfigSource variables (in the ipAddressStatus folder) are set to OSSIBLE AUSE dhcp, then the Mediatrix 4104 does not send a DHCP REQUEST message. This is the case if: • you set all xxxSelectConfigSource variables to something other than dhcp and you...

  • Page 381: Software Upgrade Issues

    OLUTION Software Upgrade Issues The following are issues you may encounter when performing a software upgrade operation. : An error occurs when the Mediatrix 4104 attempts to communicate with the image server. ESCRIPTION  : The directory specified in the upgrade command does not exist or does not contain...

  • Page 382: Snmp Management Software Issues

    This delay is caused by the Mediatrix 4104 that cannot function as configured if part of its configuration (the DHCP information) is unavailable. Furthermore, there is an issue with switches that use the Spanning Tree Protocol.
  • Page 383 SNMP Management Software Issues Reference Manual (SIP Version) Try to locate the Mediatrix 4104 IP address. If impossible, perform a recovery reset as indicated in section “Reset / Default Switch” on page : There is no response when trying to access the Mediatrix 4104.
  • Page 384 Chapter 31 - Troubleshooting SNMP Management Software Issues : Is it possible for a hacker to change the content of SNMPv3 variables once the Mediatrix 4104 ESCRIPTION is in secure mode management?  : In secure management mode, the Mediatrix 4104 works in SNMPv1 read-only,...

  • Page 385: Appendices

    Appendices...
  • Page 386 Page Left Intentionally Blank...

  • Page 387: Standards Supported

    EN61000-4-11 (1995), Voltage Dips and Interruptions Telecom • FCC Part 68:Subpart D • Industry Canada CS-03, issue 9, Part I, November 15, 2004 Note: The standards compliance of the Mediatrix 4104 are printed on a sticker located on the bottom of the unit. Mediatrix 4104...

  • Page 388: Disclaimers

    If they do, you will be notified in advance to give you an opportunity to maintain uninterrupted telephone service. If you experience trouble with this telephone equipment, please contact Media5 for information on how to obtain service or repairs. The telephone company may ask that you disconnect this equipment from the network until the problem has been corrected or until you are sure that the equipment is not malfunctioning.

  • Page 389: Industry Canada

    DIRECTIVE 1999/5/EC OF THE EUROPEAN PARLIAMENT (RTTE DIRECTIVE) is given. Any unauthorized modification of the product voids this declaration. For a copy of the original signed Declaration Of Conformity please contact Media5 at the above address. Mediatrix 4104...

  • Page 390: Rohs China

    Appendix A - Standards Compliance and Safety Information Disclaimers RoHS China Mediatrix 4104...

  • Page 391: Translated Warning Definition

    Translated Warning Definition Reference Manual (SIP Version) Translated Warning Definition The following information provides an explanation of the symbols which appear on the Mediatrix 4104 and in the documentation for the product. Warning: Means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, you must be aware of the hazards involved with electrical circuitry and familiar with standard practices for preventing accidents.

  • Page 392: Safety Warnings

    Socket Outlet Warning Warning: The socket outlet, if used, shall be located near the equipment and shall be easily accessible by the user. The AC adaptor inlet is considered as disconnection device. The device must be readily operational. Mediatrix 4104...

  • Page 393: Safety Recommendations

    Avoid using a telephone (other than a cordless type) during an electrical storm. There may be a remote risk of electric shock from lightning. • Do not use the telephone to report a gas leak in the vicinity of the leak. Mediatrix 4104...
  • Page 394 Appendix A - Standards Compliance and Safety Information Safety Recommendations Mediatrix 4104...

  • Page 395: Standard Hardware Information

    Media5 sales representative to obtain the latest version of the technical specifications. Industry Standard Protocols The Mediatrix 4104 has been designed to support all major industry standards used today, as well as those that will eventually be implemented at a later date. Because of this specific design characteristic, the Mediatrix 4104 can be integrated with existing telephone, fax and data equipment such as PCs and routers.

  • Page 396: Interfaces

    Seamless switch over period if the client UPS detects a power loss and activates within 8 ms. Casing / Installation  Casing: Desktop (Plastic ABS UL94 V0).  Installation: The Mediatrix 4104 is designed for the desktop or can be wall-mountable. Product Architecture Details  Supports four concurrent communications using any vocoders. ...

  • Page 397: Analog Line Interface (Fxs)

    Dynamic Range -25 dBm to 0 dBm per tone Frequency Accept ± 1.5% of nominal frequencies Minimum Tone Duration 40 ms, can be increased with software configuration Interdigit Timing Detects like digits with a 40 ms interdigit delay Mediatrix 4104...

  • Page 398: Dtmf Tone Generation

    Within 1.5% of nominal values MTBF Value The Mean Time Before Failure (MTBF) value of the Mediatrix 4104 is 250,000 hours at 25 degrees Celsius ambient temperature. It has been defined using RelCalc v5.0, Bellcore method (LimitedStress - Method I, Case 3), Desktop unit.

  • Page 399: Dimensions And Weight

    22 cm x 17.6 cm x 4.9 cm - 8.7 in. x 6.9 in. x 1.9 in. (approx.) Weight 468 g (1.03 lb) Warranty All Media5 products carry Media5's standard three-year hardware and software warranty. An extended warranty is available. Mediatrix 4104...
  • Page 400 Appendix B - Standard Hardware Information Warranty Mediatrix 4104...

  • Page 401: Cabling Considerations

    P P E N D I X Cabling Considerations This Appendix describes the pin-to-pin connections for cables used with the Mediatrix 4104. Warning: To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. RJ-45 Cable The RJ-45 connector is commonly used for network cabling and for telephony applications.

  • Page 402: Crossover Cable

    A crossover cable is sometimes called a null modem. The coloured wires at either end are put into different pin numbers, or crossed over. Figure 93: Crossover Connectivity 1- TX+ TX+ -1 2- TX- TX- -2 3- RC+ RC+ -3 6- RC- RC- -6 Mediatrix 4104...

  • Page 403: Rj-11 (Telephone) Cable

    The RJ-11 pair of wires is wired so that pins 3 and 4 are connected to the Ring and Tip, which meets the following requirements:  EIA/TIA-IS 968  CS-03 Issue 8, Part III requirements. Warning: The RJ-11 cable should comply with UL 1863 and CSA C22.2 No 233 standards. Mediatrix 4104...
  • Page 404 Appendix C - Cabling Considerations RJ-11 (Telephone) Cable Mediatrix 4104...

  • Page 405: Country-Specific Parameters

    Impedance is the apparent resistance, in an electric circuit, to the flow of an alternating current, analogous to the actual electrical resistance to a direct current, being the ratio of electromotive force to the current. When representing an impedance, the following applies:  Symbol “//” means parallel.  Symbol “+” means serial. Mediatrix 4104...
  • Page 406 Terminal Balance Return Loss (TBRL) Impedance Input Impedance Impedance of the Mediatrix 4104 at the Tip and Ring wires. Terminal Balance Return Loss (TBRL) Impedance Balance return loss attributable to transmission loss between two points. It is used to characterize an impedance balancing property of the 2-wire analog equipment port.

  • Page 407: Distinctive Ring

    <http://127.0.0.1/Bellcore-dr4> or <Bellcore-dr4> Bellcore-dr4 0.3 – 0.2, 1.0 – 0.2, 0.3 – 4.0 The Mediatrix 4104 plays the default ring of the country selected if the Alert-Info value is not present or the value is not supported. Note: Since the first pause of the distinctive ring is lower that 1 second, a splash ring followed by an Off of 1 second precedes the distinctive ring pattern.

  • Page 408: Australia

    0.375 – 0.375 -18 dBm Ring AC: 45 VRMS, 25 Hz 0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -6 dBr Mediatrix 4104...

  • Page 409: Australia 2

    0.375 – 0.375 -18 dBm Ring AC: 45 VRMS, 25 Hz 0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -6 dBr Mediatrix 4104...

  • Page 410: Australia 3

    AC: 45 VRMS, 25 Hz 0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 220 Ω + 820 Ω // 115 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 411: Austria

    Ring AC: 45 VRMS, 50 Hz 1.0 – 5.0 DC: 15 Vdc 270 Ω + 750 Ω // 150 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -10 dBr Mediatrix 4104...

  • Page 412: Brazil

    425 Hz 0.2 – 0.2 -10 dBm Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 900 Ω Input Impedance Default Caller ID TELEBRAS_DTMF FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 413: Chile

    0.2 – 0.2 -10 dBm Ring AC: 45 VRMS, 20 Hz 1.0 – 3.0 DC: 15 Vdc 600 Ω Input Impedance 600 Ω Tbrl-Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 414: Chile

    0.2 – 0.2 -10 dBm Ring AC: 45 VRMS, 20 Hz 1.0 – 3.0 DC: 15 Vdc 900 Ω Input Impedance 900 Ω Tbrl-Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 415: China

    450 Hz 0.7 – 0.7 -10 dBm Ring AC: 45 VRMS, 20 Hz 1.0 – 4.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 416: Czech Republic

    AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 220 Ω + 820 Ω // 115 nF Input Impedance Default Caller ID ETSI FSK FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 417: Denmark

    Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 300 Ω + 1000 Ω // 220 nF Input Impedance Default Caller ID TDK_DTMF FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -6 dBr Mediatrix 4104...

  • Page 418: France

    AC: 45 VRMS, 50 Hz 1.5 – 3.5 DC: 15 Vdc 215 Ω + 1000 Ω // 137 nF Input Impedance Default Caller ID FRANCE: BELLCORE FRANCE_ETSI_FSK: ETSI_FSK FRANCE_ETSI_DTMF:ETSI_DTM FXS Line Attenuation (Input) +1.9 dBr FXS Line Attenuation (Output) -8.9 dBr Mediatrix 4104...

  • Page 419: Germany

    Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 220 Ω + 820 Ω // 115 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -10 dBr Mediatrix 4104...

  • Page 420: Germany 2

    Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 220 Ω + 820 Ω // 115 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -10 dBr Mediatrix 4104...

  • Page 421: Hong Kong

    0.25 – 0.25 -13 dBm Ring AC: 45 VRMS, 20 Hz 0.4 – 0.2, 0.4 –3.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -6 dBr Mediatrix 4104...

  • Page 422: Indonesia

    425 Hz 0.25 – 0.25 -9 dBm Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -3 dBr Mediatrix 4104...

  • Page 423: Israel

    400 Hz 0.25 – 0.25 -15 dBm Ring AC: 45 VRMS, 25 Hz 1.0 – 3.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 424: Italy

    Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 180 Ω + 630 Ω // 60 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 425: Japan

    400 Hz 0.5 – 0.5 -13 dBm Ring AC: 45 VRMS, 20 Hz 1.0 – 2.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 426: Malaysia

    0. – 0.25 -18 dBm Ring AC: 45 VRMS, 20 Hz 0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 427: Mexico

    425 Hz 0.25 – 0.25 -18 dBm Ring AC: 45 VRMS, 20 Hz 1.0 – 4.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -3 dBr Mediatrix 4104...

  • Page 428: Netherlands

    Ring AC: 45 VRMS, 20 Hz 1.0 – 4.0 DC: 15 Vdc 270 Ω + 750 Ω // 150 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 429: New Zealand

    AC: 45 VRMS, 25 Hz 0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 300 Ω + 1000 Ω // 220 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 430: North America

    AC: 45 VRMS, 20 Hz 2.0 – 4.0 DC: 15 Vdc 600 Ω Input Impedance 600 Ω Tbrl-Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -3 dBr a. TBRL-Impedance for “on-premise" or short loop ports. Mediatrix 4104...

  • Page 431: North America 2

    350 Ω + 1000 Ω // 210 nF Tbrl-Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) 0 dBr a. TBRL-Impedance for “off-premise" or long loop ports (wire length longer than 2.5 km). Mediatrix 4104...

  • Page 432: Russia

    425 Hz 0.2 – 0.2 -10 dBm Ring AC: 45 VRMS, 25 Hz 0.8 – 3.2 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) +2 dBr FXS Line Attenuation (Output) -2 dBr Mediatrix 4104...

  • Page 433: South Africa

    AC: 45 VRMS, 25 Hz 0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 300 Ω + 1000 Ω // 220 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 434: Spain

    Ring AC: 45 VRMS, 25 Hz 1.5 – 3.0 DC: 15 Vdc 220 Ω + 820 Ω // 120 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -7 dBr Mediatrix 4104...

  • Page 435: Sweden

    Ring AC: 45 VRMS, 25 Hz 1.0 – 5.0 DC: 15 Vdc 200 Ω + 1000 Ω // 100 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -5 dBr Mediatrix 4104...

  • Page 436: Switzerland

    Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 220 Ω + 820 Ω // 115 nF Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) 0 dBr FXS Line Attenuation (Output) -6.5 dBr Mediatrix 4104...

  • Page 437: Thailand

    400 Hz 0.3 – 0.3 -10 dBm Ring AC: 45 VRMS, 25 Hz 1.0 – 4.0 DC: 15 Vdc 600 Ω Input Impedance Default Caller ID BELLCORE FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -3 dBr Mediatrix 4104...

  • Page 438: United Arab Emirates

    0.4 – 0.2, 0.4 – 2.0 DC: 15 Vdc 300 Ω + 1000 Ω // 220 nF Input Impedance Default Caller ID UK: BRITISH_TELECOM UK_BELLCORE: BELLCORE UK_CCA: CCA UK_ETSI_FSK: ETSI_FSK FXS Line Attenuation (Input) -3 dBr FXS Line Attenuation (Output) -9 dBr Mediatrix 4104...

  • Page 439: Glossary

    Geographical (regional) zone of the number (in France, there are five zones). It has two digits. ABPQ First four digits corresponding to a local zone defined by central offices. 12 34 Unique number to reach a specific destination. Mediatrix 4104...
  • Page 440 “foreign”, exchange, rather than the local exchange area’s central office. This is the station (telephone) end of an FX circuit. An FXS port will provide dial tone and ring voltage. Mediatrix 4104...
  • Page 441 Systems Interconnection (OSI). The Network Layer is concerned with knowing the address of the neighbouring nodes in the network, selecting routes and quality of service, and recognizing and forwarding to the transport layer incoming messages for local host domains. Mediatrix 4104...
  • Page 442 Private Branch Exchange (PBX) A small to medium sized telephone system and switch that provides communications between onsite telephones and exterior communications networks. Mediatrix 4104...
  • Page 443 A communication network, such as the public switched telephone network (PSTN), in which any user may be connected to any other user through the use of message, circuit, or packet switching and control devices. Server A computer or device on a network that works in conjunction with a client to perform some operation. Mediatrix 4104...
  • Page 444 UDP is an OSI layer 4 protocol. Voice Over IP (VoIP) The technology used to transmit voice conversations over a data network using the Internet Protocol. Such data network may be the Internet or a corporate Intranet. Mediatrix 4104...
  • Page 445 Wide Area Network (WAN) Reference Manual (SIP Version) Wide Area Network (WAN) A large (geographically dispersed) network, usually constructed with serial lines, that covers a large geographic area. A WAN connects LANs using transmission lines provided by a common carrier. Mediatrix 4104...
  • Page 446 Appendix E - Glossary Wide Area Network (WAN) Mediatrix 4104...

  • Page 447: List Of Acronyms

    Open Systems Interconnection Private Branch eXchange Pulse Code Modulation Personal Identification Number PSTN Public Switched Telephone Network Quality of Service Ringer Equivalence Number Request For Comment RTCP Real Time Control Protocol Switched Circuit Network Session Description Protocol Session Initiation Protocol Mediatrix 4104...
  • Page 448 Transmission Control Protocol/Internet Protocol Transport Layer Security Twisted-Pair Ethernet User Datagram Protocol Underwriters Laboratories Incorporated Universal Time Coordinated Unshielded Twisted pair Voice Activity Detection VLAN Virtual Local Area Network VoIP Voice over Internet Protocol Wide Area Network eXtensible Markup Language Mediatrix 4104...

  • Page 449: List Of Mib Parameters

    ..........................248 dataIfClearChannelCodecPreferred......................249 dataIfCngToneDetectionEnable........................247 dataIfCodecT38Enable ..........................252 dataIfCodecT38ProtectionLevel........................253 dataIfT38FinalFramesRedundancy......................253 dataIfT38NoSignalEnable ..........................253 dataIfT38NoSignalTimeout .......................... 253 digitMapAllowedDigitMap..........................294 digitMapAllowedEnable..........................295 digitMapAllowedLineToApply ........................295 digitMapPrefixedDigitRemovalCount ......................294 digitMapPrependedString ..........................295 digitMapProcessDigitsWhenPressed ......................294 digitMapRefusedDigitMap ..........................295 Mediatrix 4104...
  • Page 450 IfAdminInitialAdminState ..........................222 ifAdminSetAdmin ............................221 imageAutoUpdateEnable ........................215 imageAutoUpdateOnRestartEnable......................215 imageAutoUpdatePeriod ..........................217 imageAutoUpdateTimeRange........................217 imageAutoUpdateTimeUnit .......................... 216 imageConfigSource ............................20 imageDhcpPrimarySiteSpecificCode ....................146 imageDhcpSecondarySiteSpecificCode ....................147 imageLocation............................209 imageLocationProvisionSource ........................209 imagePrimaryHost ..........................19 imagePrimaryPort ...........................19 imageSecondaryHost........................19 imageSecondaryPort ........................19 Mediatrix 4104...
  • Page 451 .............................19 msTrapRetransmissionPeriod........................333 msTrapRetransmissionRetryCount ......................333 mwiConfigActivation............................. 330 mwiConfigFetchAddress ..........................330 mwiConfigUserSubscriptionAddress......................329 mwiExpirationTime............................330 mwiFetchDigitMap ............................330 mwiSubscriptionCmdRefresh........................330 mxDebugPcmCaptureEnable ........................353 mxDebugPcmCaptureEndpointNumber....................... 353 mxDebugPcmCaptureIpAddress ......................... 353 mxInteropHttpUAHeaderConfig ......................193 pinDialingDelay ............................324 pinDialingEnable ............................324 Mediatrix 4104...
  • Page 452 238 sipInteropDtmfTransportMethod ........................237 sipInteropEscapePoundInSipUriUsername ....................281 sipInteropIgnoreUsernameParam ........................ 281 sipInteropIgnoreViaBranchIdInCancelEnable ....................276 sipInteropInternationalCodeMappingEnable ....................277 sipInteropInternationalCodeMappingString....................277 sipInteropLocalRingOnProvisionalResponse....................275 sipInteropLockDnsSrvRecordPerCallEnable ....................173 sipInteropMaxForwardsValue ........................271 sipInteropMwiMessageSummaryValidation ....................330 sipInteropOnHoldAnswerSdpStreamDirection ..................... 274 sipInteropOnHoldSdpStreamDirection ......................273 sipInteropProxyAuthenticationUriParametersEnable ................... 277 Mediatrix 4104...
  • Page 453 266 sipRtpUdpChecksumEnable ........................284 sipServerSelectConfigSource ..................149 sipTransportContactEnable ......................... 264 sipTransportEnable ............................263 sipTransportQValue ............................. 263 sipTransportRegistrationEnable........................263 sipTrustedSourcesEnable..........................262 sipTrustedSourcesIpAddress........................262 sipUAAuthPassword ............................ 261 sipUAAuthRealm............................261 sipUAAuthUsername ........................... 261 sipUAAuthValidateRealm..........................261 sipUADisplayName ............................258 sipUAMainUsername ........................... 257 Mediatrix 4104...
  • Page 454 ................... 312 subscriberServicesCallWaitingEnable ......................312 subscriberServicesCallWaitingPermanentDigitMapDisable................. 313 subscriberServicesCallWaitingPermanentDigitMapEnable................312 subscriberServicesCallWaitingStatus ......................312 subscriberServicesConferenceEnable ......................318 subscriberServicesConferenceStatus ......................318 subscriberServicesHoldEnable ........................305 subscriberServicesHoldStatus ........................305 subscriberServicesProcessingTrigger ......................303 subscriberServicesSecondCallEnable ......................305 subscriberServicesSecondCallStatus ......................305 sysAdminCommand........................143 sysAdminDefaultSettingsEnable ........................21 Mediatrix 4104...
  • Page 455 ........................233 voiceIfCodecG723MinPTime ........................233 voiceIfCodecG72616kbpsEnable......................... 232 voiceIfCodecG72616kbpsMaxPTime......................233 voiceIfCodecG72616kbpsMinPTime......................233 voiceIfCodecG72616kbpsPayloadType ....................... 232 voiceIfCodecG72624kbpsEnable......................... 232 voiceIfCodecG72624kbpsMaxPTime......................234 voiceIfCodecG72624kbpsMinPTime......................234 voiceIfCodecG72624kbpsPayloadType ....................... 232 voiceIfCodecG72632kbpsEnable......................... 232 voiceIfCodecG72632kbpsMaxPTime......................234 voiceIfCodecG72632kbpsMinPTime......................234 voiceIfCodecG72632kbpsPayloadType ....................... 232 voiceIfCodecG72640kbpsEnable......................... 232 voiceIfCodecG72640kbpsMaxPTime......................234 voiceIfCodecG72640kbpsMinPTime......................234 Mediatrix 4104...
  • Page 456 ....................... 240 voiceIfDtmfDetectionUnitPositiveTwist ......................240 voiceIfDtmfEnforceDefaultEvents ........................ 237 voiceIfDtmfPayloadType ..........................236 voiceIfDtmfTransport......................232 voiceIfEchoCancellationEnable ........................243 voiceIfG711ComfortNoiseGenerationEnable ....................244 voiceIfG711VoiceActivityDetectionEnable ....................242 voiceIfG729VoiceActivityDetectionEnable ....................242 voiceIfMaxJitterBufferLength ....................... 241 voiceIfSignalLimiterLevel ..........................243 voiceIfTargetJitterBufferLength......................241 voiceIfUserInputGainOffset .......................... 244 voiceIfUserOutputGainOffset ........................245 Mediatrix 4104...
  • Page 457 10 BaseT data see also 100 BaseT clear channel fax call enabling automatic preferred dialing sequence enabling emergency T.38 bypass voice enabling defined forced SCN DTMF detection forward DTMF transport type on busy Mediatrix 4104...
  • Page 458 # and * characters connecting the unit combining two expressions connectors definition ETH1 examples ETH2 PBX emulation Phones/Faxes standard calls port numbering convention, FXS processing digits behaviour PSTN refused Reset/Default rules universal power supply unit special characters Mediatrix 4104...
  • Page 459 CED tone detection, enabling record lock, in SIP clear channel documentation T.38 Media5 download portal INVITE rejected with 606 Mediatrix download portal no-signal downgrading software, procedure user gain vs communication quality downloading software firmware download. see software...
  • Page 460 DNS, secondary data codecs static analog CED detection behaviour download server CED fax tone detection entering clear channel fax ETH2 connector, static clear channel, enabling Image server clear channel, preferred locating enabling Management Server Mediatrix 4104...
  • Page 461 Route header Max-Forwards header, in SIP out-of-band DTMF MDI/MDIX, auto overview of the product Media5 download portal Mediatrix download portal message waiting indicator defined package contents notifications packetization time, setting for voice codecs...
  • Page 462 Replaces header, in SIP session expiration delay configuration maximum version minimum requirements version supported, setting restart signal limiter behaviour in case of broadcast storm signalling protocol, SIP. see SIP, setting software-initiated SIP INFO, controlling call waiting tone via unit Mediatrix 4104...
  • Page 463 HTTPS server, configuring registration refresh HTTPS, via web interface, configuring via Image path replaces LED states configuration SNTP server, configuring version Spanning Tree Protocol ringing response code syslog messages session timer TFTP server, configuring session expiration delay, maximum TFTP, via Mediatrix 4104...
  • Page 464 RFC 2246 blind transfer RFC 2347 web interface, configuring via RFC 2348 call waiting RFC 2349 web interface, configuring via RFC 2459 conference call RFC 2475 web interface, configuring via RFC 2543 hold RFC 2543bis direction attributes Mediatrix 4104...
  • Page 465 DHCP setting TPE. see cabling verifying the installation transfer, version supported, setting viewing statistics and performances transferring a call VLAN, in QoS attended transfer substitution values blind Mediatrix 4104...
  • Page 466 SIP custom NAT traversal SIP outbound proxy server SIP penalty box SIP proxy server SIP publications refresh SIP registrar server SIP registration refresh SIP transport type SIP user agents SNTP status, system STUN subnet mask system management user name, modify Mediatrix 4104...

Table of Contents