MVTS 3.1.4 Configuration Manual

MVTS Configuration Operator's manual

© MERA Systems Inc. 2008 1

Document №: 1 Document type: Operator’s Manual

Document status:

Date of issue: 01.04.2008

Responsible employee: Technical Writer

Copyr ight © 2008 Mera Systems Inc. Al l r ights reserved. Mera Systems Inc. reserves the r ight to change any informat ion contained in th is document wi thout pr ior not ice.

COPYRIGHT INFORMATION The informat ion contained in this document is the property of MERA. No part of th is publ icat ion may be reproduced or copied in any form or by any means - graphic, e lectronic or mechanical including photocopying, recording, taping, or any other informat ion storage and retr ieval system - wi thout wr i t ten consent of MERA Mera Systems Inc. No third party, organizat ion or individual, is author ized to grant such permission.

© MERA Systems Inc. 2008 2

Table of Contents

1 INTRODUCTION .......................................................................................................... 8 1.1 DOCUMENT PROFILE.................................................................................................... 8 1.2 AUDIENCE ................................................................................................................... 8 1.3 CONVENTIONS............................................................................................................. 8 1.4 DOCUMENT STRUCTURE .............................................................................................. 9

2 CONFIGURATION FILES......................................................................................... 10

3 MERAPROXY.CFG..................................................................................................... 11 3.1 SECTION [ADMINISTRATION]..................................................................................... 12 3.2 SECTION [BILLING] ................................................................................................... 13 3.3 SECTION [CONSOLE] ................................................................................................. 14 3.4 SECTION [DEBUG] ..................................................................................................... 14 3.5 SECTION [GATEKEEPER]............................................................................................ 15 3.6 SECTION [H.323]....................................................................................................... 15 3.7 SECTIONS [RADIUS] AND [BACKUPRADIUS].............................................................. 16 3.8 SECTION [REDUNDANCY].......................................................................................... 18 3.9 SECTION [LAR]......................................................................................................... 19 3.10 SECTION [MEDIA]...................................................................................................... 19 3.11 SECTION [PROXY] ..................................................................................................... 20 3.12 SECTION [SNMP]...................................................................................................... 20 3.13 SECTION [STATISTICS]............................................................................................... 21

4 GATEWAY.CFG.......................................................................................................... 24

5 USER.CFG .................................................................................................................... 31

6 GATEKEEPER.CFG ................................................................................................... 38

7 DIALPEER.CFG .......................................................................................................... 39

8 CONFIGURATION HOWTOS .................................................................................. 43 8.1 CONFIGURATION CASE 1: ADDING TWO STATIC GATEWAYS....................................... 43 8.2 CONFIGURATION CASE 2: CONFIGURING SEVERAL STATIC GATEWAYS AND

ADDING GROUPS ........................................................................................................ 45 8.3 CONFIGURATION CASE 3: ADDING A REGISTERING ENDPOINT (ATA ADAPTER)

SITTING BEHIND A NAT ROUTER ............................................................................... 47 8.4 CONFIGURATION CASE 4: IMPLEMENTING RADIUS AUTHORIZATION AND

ACCOUNTING ............................................................................................................. 49 8.5 CONFIGURATION CASE 5: CONNECTING A SOFTPHONE ............................................... 51 8.6 CONFIGURATION CASE 6: CONFIGURING MVTS FOR INTERACTION WITH

GATEKEEPERS............................................................................................................ 53 8.7 CONFIGURATION CASE 7: CONFIGURING THE PRIMARY AND STANDBY MVTS

FOR FAILOVER-FAILBACK .......................................................................................... 55 8.7.1 GK-RAS user scheme ........................................................................................ 55 8.7.2 Shared IP failover-failback scheme ................................................................... 56

8.8 CONFIGURATION CASE 8: CONFIGURING THE SYSTEM OPERATING WITH THE SIP-HIT CONVERTER ................................................................................................ 57

8.8.1 SIP–HIT deployment ......................................................................................... 57

p.3 of 218

8.8.2 Configuring the system for operation with SIP-HIT co-installed on the MVTS server...................................................................................................... 60

8.9 MINIMUM DOWNTIME TRANSITION FROM SINGLE-SERVER TO MVTS-BASED CLUSTER SOLUTION ................................................................................................... 62

APPENDIX 1: CONFIGURATION PARAMETERS ALPHABETIZED..................... 63

p.4 of 218

List of tables Table 1 Typographic conventions used in the document......................................................... 8

Table 2 The MVTS configuration files.................................................................................. 10

Table 3 Sections of the system configuration file meraproxy.cfg ......................................... 11

Table 4 meraproxy.cfg: configuration parameters of section [Administration] .................... 12

Table 5 meraproxy.cfg: configuration parameters of section [Billing] ................................. 13

Table 6 meraproxy.cfg: configuration parameters of section [Console] ............................... 14

Table 7 meraproxy.cfg: configuration parameters of section [Debug] .................................. 14

Table 8: meraproxy.cfg: configuration parameters of section [Gatekeeper] ......................... 15

Table 9 meraproxy.cfg: configuration parameters of section [H323].................................... 15

Table 10 meraproxy.cfg: configuration parameters of section [Radius] ............................... 16

Table 11 meraproxy.cfg: configuration parameters of section [Redundancy]....................... 18

Table 12 meraproxy.cfg: configuration parameters of section [LAR]................................... 19

Table 13 meraproxy.cfg: configuration parameters of section [Media] ................................ 19

Table 14 meraproxy.cfg: configuration parameters of section [Proxy] ................................. 20

Table 15 meraproxy.cfg: configuration parameters of section [SNMP]................................ 21

Table 16 meraproxy.cfg: configuration parameters of section [Statistics] ............................ 21

Table 17 gateway.cfg: configuration parameters of an individual GW record...................... 24

Table 18 user.cfg: configuration parameters of a RAS user .................................................. 32

Table 19 gatekeeper.cfg: configuration parameters of a gatekeeper record .......................... 38

Table 20 dialpeer.cfg: configuration parameters of a dialpeer record ................................... 39

Table 21 What you need to write in the MVTS configuration files to implement connectivity scenario 1 ....................................................................................................................... 44

Table 22 Using groups to facilitate configuration tasks ........................................................ 46

Table 23 Adding registering users and allowing NAT traversal ........................................... 48

Table 24 Configuring softphone and ATA registering users................................................. 52

Table 25 Configuring MVTS – gatekeeper interoperation .................................................... 53

Table 26 Configured [Redundancy] sections on the main and standby systems. .................. 56

Table 27 MVTS and SIP-HIT configuration files (two-server deployment)......................... 58

Table 28 Configuration files of the MVTS session controller and SIP-HIT converter ......... 61

p.5 of 218

List of figures

Fig. 1 Linking two static gateways through MVTS............................................................... 43

Fig. 2 Grouping static endpoints for facilitation of configuration tasks ................................ 45

Fig. 3 Configuring a RAS user and enabling NAT traversal ................................................. 47

Fig. 4 Configuring ATA 186 adapter..................................................................................... 48

Fig. 5 Allowing for RADIUS authorization and accounting ................................................. 49

Fig. 6 Working with a softphone ........................................................................................... 51

Fig. 7 NetMeeting configuration dialog box.......................................................................... 52

Fig. 8 Configuring gatekeeper interoperation ........................................................................ 53

Fig. 9 Primary MVTS and failover MVTS operating as a GK-RAS user pair ...................... 55

Fig. 10 Configuring the MVTS and the SIP-HIT converter installed on different servers.... 58

Fig. 11 Configuring the MVTS and SIP-HIT converter to operate co-installed on a single server.............................................................................................................................. 60

p.6 of 218

List of References

Reference Name of document [1] “MVTS 3.1.4 Operator’s Manual” [2] “MVTS Redundancy schemes” [3] “MVTS-based clusters”

p.7 of 218

1 INTRODUCTION

1.1 DOCUMENT PROFILE The present document is a guide on the MERA VoIP Transit Softswitch configuration parameters. The document provides a description and explanation of each MVTS configuration parameter, its objective, its valid and default values.

Additionally, the guide contains information (in form of the so-called “how to’s”) on configuring the MVTS for operation with various VoIP entities (gatekeepers, RAS users, gateways, etc.) as well as with RADIUS server, SIP-HIT translator, etc.

1.2 AUDIENCE This guide is intended for a system administrator or any person whose responsibility is to configure and operate the MVTS. Users of this document are presumed to have a working knowledge of UNIX-like operating systems (Free BSD, Red Hat Linux) and to have at least some acquaintance with the MVTS application [1].

1.3 CONVENTIONS The table below describes the document conventions:

Table 1 Typographic conventions used in the document

Example Convention

Note: text Important information requiring special attention

[N] Numbers in square brackets represent a reference to some other document

Void

Words in Times New Roman expanded by 1.5pt represent examples of source code, program output, as well as contents of logs, configuration files etc.

[user@localhost]# cat user.cfg White text against black background represents screenshots of the CLI

CallingStationId Setup

Arial Narrow 12 pt is utilized to highlight call parameters and names of call session stages

Ulimit Boldface is used to highlight names of programs, files and directories as well as the names of the system configuration files

call_radix= Courier New, 11 pt is used to highlight names of parameters found in the system configuration files.

p.8 of 218

1.4 DOCUMENT STRUCTURE

Here is a brief synopsis of the chapters of this document:

Chapter 1: Introduction describes the subject matter and the structure of this document, the target audience and typographic conventions.

Chapter 2: Configuration files lists all the files whose parameters are instrumental in configuration of the MVTS.

Chapter 3: Meraproxy.cfg is focused on the configuration parameters of the global system configuration file and its 14 sections.

Chapter 4: Gateway.cfg enumerates and explains the use of the configuration parameters indispensable for description of static VoIP entities registered with the MVTS.

Chapter 5: User.cfg describes the configuration parameters of RAS user datafile, that is – the file that contains information about RAS signaling clients registered with the MVTS.

Chapter 6: Gatekeeper.cfg lists all the parameters used to describe and configure the MVTS interaction with the gatekeepers the MVTS registers with as a client.

Chapter 7: Dialpeer.cfg provides a description of the configuration parameters contained in the MVTS calling plan datafile.

Chapter 8 contains specific instances of configuring the MVTS to operate with various VoIP entities.

Appendix 1 presents a full list of configuration parameters in the alphabetical order.

p.9 of 218

2 CONFIGURATION FILES When installing the MVTS by means of the setup.sh installation script the configuration files are by default saved to the cfg/ directory. The five configuration files used to control the MVTS operation include: meraproxy.cfg, gateway.cfg, user.cfg, gatekeeper.cfg and dialpeer.cfg. Table 2 below gives a brief description of the files purpose and use.

Table 2 The MVTS configuration files

Filename Description

meraproxy.cfg File of global settings that determine the MVTS features and operational behavior

gateway.cfg Configuration file that contains information about ‘statically’ configured endpoints, i.e. gateways that do not register and are authenticated by the IP address.

user.cfg Configuration file that serves to define the properties of registering VoIP entities (i.e. endpoints that register with the MVTS gatekeeper under the RAS protocol and hereinafter referred to as RAS users)

dialpeer.cfg File that provides description of available call routing options (dial peers) and allows determination of call path peculiarities.

gatekeeper.cfg File used to describe and configure the MVTS interaction with other gatekeepers (the MVTS gatekeeper is configured in the section [Gatekeeper] of meraproxy.cfg)

Individual configuration parameters in the files are grouped into sections. A section of configuration parameters in the file meraproxy.cfg represents a functional feature of the system while a section in the file gateway.cfg, user.cfg, gatekeeper.cfg and dialpeer.cfg is a set of attributes that describe properties and capabilities of the pertinent object (a gateway, a registering endpoint, call path or a gatekeeper).

In what follows you will find detailed coverage of the MVTS configuration parameters.

p.10 of 218

3 MERAPROXY.CFG The configuration file meraproxy.cfg is the file of MVTS global settings. Meraproxy.cfg consists of 14 sections of configuration parameters that serve to manage all of the MVTS operation aspects.

The names of the sections and description of their purpose are given in Table 3.

Table 3 Sections of the system configuration file meraproxy.cfg

Section Description

[Administration] Use this section to change the default names of the system configuration files, specify the administrator’s email address for email alerts, set maximum and minimum call duration limits, and configure some other system properties.

[Billing] The parameters of this section determine how the MVTS handles CDR-based billing data

[Console] This section serves to set the parameters of the MVTS administration console and define GIDs for the Administration, Billing and Support user groups

[Debug] The parameters of this section determine how the MVTS manages debug logs

[Gatekeeper] This section is useful for enabling or disabling the MVTS’s gatekeeper functionality and determining the GK properties

[H323] This section serves to configure H.323-related properties of the system and set the parameters of the H.323/SIP converter if any

[Radius] Use the parameters of this section to manage the MVTS interaction with RADIUS servers (in authorization, accounting and routing).

[BackupRadius] This section is necessary to configure the MVTS for interoperation with an alternate RADIUS server

[Redundancy] Use the parameters of this section to manage the system failover-failback behavior

[LAR] The configuration parameters of this section are used to configure the look-ahead routing function and related properties of the system

[Media] The parameters of this section serve to configure interaction with media MVTSs (media MVTS is an element of MVTS-based cluster solutions)

[Proxy] The section [Proxy] comprises a set of parameters that determine the MVTS proxy characteristics

[SNMP] Section for determining SNMP-related features of the system

[Statistics] The configuration parameters of this section are used to control the statistics collection mechanism of the MVTS

p.11 of 218

3.1 SECTION [ADMINISTRATION] The parameters of this section are used to change the default names of the system configuration files, specify the administrator's email address for system alerts, set maximum and minimum call duration limits and configure some other system properties. Table 4 gives the name of a configuration parameter and explains the purpose it is used for. The names of the configuration parameters are links. Click the parameter name to see a detailed description of the parameter and its valid values.

Table 4 meraproxy.cfg: configuration parameters of section [Administration]

Configuration parameter serves to…

gateway_cfg= specify the name of the configuration file containing information about static gateways

user_cfg= specify the name of the data file with information about RAS users (registering endpoints)

dialpeer_cfg= indicate the file with dial peer data, Specify the file path relative to the root directory or the configuration file merarpoxy.cfg

gatekeeper_cfg=

indicate the file with information about gatekeepers; specify the file path relative to the root directory or the configuration file merarpoxy.cfg

mail_alert= specify an email address for malfunctioning alerts that the MVTS may develop

local_address= specify the local IP address to be used in call setup when the necessary data is not available from the OS routing table

rtp_threads= set a number of threads allocated for media traffic

call_threads= set a number of threads allocated for signaling traffic

max_call_duration= set the maximum reasonable call duration in seconds

min_call_duration= set a rounding point for the fractional part of call duration time

public_access= enable/disable IP address-based authentication of gateways

load_balancer_address= specify the IP address of the load balancer in three-level MVTS-based clusters

signaling_proxy_address= specify the IP address of the signaling MVTS in MVTS-based clusters

local_route_server_address= set the local IP address for sending statistical data (priority, number of current calls, maximum number of calls for the Media MVTS) to the routing server

p.12 of 218

Configuration parameter serves to…

route_server_address= specify the IP address of the routing server

priority= the value of this field is sent to an external routing server and does not affect the MVTS operation

call_limit= set the maximum quota of simultaneous calls for a Media MVTS in MVTS-based clusters

max_dnis_call_dup= define the number of simultaneous call sessions with identical DNIS number

route_h245= always set the parameter to its default value (1)

route_h225= always set the parameter to its default value (1)

diff_orig_by_prefix= enable/disable differentiation of the originating gateways with identical IP addresses (subnet mask) by number prefixes

ports_range= define ranges of ports for signaling and media traffic

direct_call_allowed= configure the signaling MVTS in a two-layer MVTS cluster to directly receive incoming signaling by-passing the load balancer

3.2 SECTION [BILLING] The parameters of this section determine how the MVTS handles CDR-based billing data.

Table 5 provides information about the intent of the section configuration parameters.

Table 5 meraproxy.cfg: configuration parameters of section [Billing]

Configuration parameter serves to...

bil_file_attr= change/set file attributes for the final file with billing data

bil_tmpfile_attr= change/set file attributes for the temporary file with billing data

cdr_format= set/change the format of billing data written to files (CDRs)

file= change the filename prefix of (and/or path to) the file to which the MVTS writes CDRs

level= enable/disable writing CDRs to the billing file

no_empty= allow/disallow empty CDR files

offset_period= define an offset value for the write time specified in the fieldperiod=

period= set file rotation time for CDR files

p.13 of 218

3.3 SECTION [CONSOLE] This section serves to set the parameters of the MVTS administration console and define GIDs for the Administration, Billing and Support user groups.

Table 6 meraproxy.cfg: configuration parameters of section [Console]


admin_gid= change/set the group identifier for the MVTS Admin group

billing_gid=

change/set a group identifier for the MVTS Billing user group

console_port=

set other than the default port 1730 for the MVTS administration console

support_gid=

change/set a group identifier for the MVTS Support user group

3.4 SECTION [DEBUG] The section incorporates the parameters that serve to configure the MVTS logging mechanism.

Table 7 meraproxy.cfg: configuration parameters of section [Debug]


debug_file_attr= change/set file attributes for the final file with debug logs

debug_tmpfile_attr=

change/set file attributes for the temporary file with debug logs

file= change the filename prefix of (and/or path to) the file with the MVTS debug logs

level= set the appropriate detail level for the data written to debug logs

max_file_size= specify the maximum acceptable size (kilobytes) for an individual log file

max_lifetime= set maximum storage time in days for debug logs

max_size= define an aggregate size of saved files with debug logs in kilobytes

no_empty= allow/disallow empty log files

offset_period= define an offset for the file rotation time set in the field period=

period= set file rotation time for debug logs

trace_level= set the appropriate detail level for trace logs written to the file named mp.kernel.sh.<date>

p.14 of 218

3.5 SECTION [GATEKEEPER] The configuration parameters of the section [Gatekeeper] serve to enable/disable and configure the MVTS gatekeeper functionality. Refer to Table 8 for brief description of the parameters purpose.

Table 8: meraproxy.cfg: configuration parameters of section [Gatekeeper]


debug_level= set the information detail level of the packet logging that reflect the MVTS gatekeeper operation

endpoint_ttl= set a registration update interval for RAS users registered with the MVTS gatekeeper

non_direct_reply_network=

enter a list of network IPs in the CIDR notation

gatekeeper_enable= enable/disable the MVTS gatekeeper functionality

gatekeeper_id= define the MVTS gatekeeper an ID

min_call_bandwidth= set the minimum bandwidth of the MVTS gatekeeper

mult_group= specify the gatekeeper’s address for RAS multicasting

mult_port= set the gatekeeper’s port for RAS multicasting

ras_port= specify the gatekeeper’s port number for RAS registration

rrq_full_reg_interval= set a registration update period for all RAS users registered with the MVTS GK

ip_precedence= set the default precedence of IP packets arriving from gateways (RAS users) to be sent to the destination

3.6 SECTION [H.323] This section serves to configure the H.323-related properties of the system and set the parameters of the H.323/SIP converter.

Table 9 meraproxy.cfg: configuration parameters of section [H323]


alternate_port= define another (alternative) signaling port

converter= specify the parameters of the H.323-SIP converter SIP-HIT

p.15 of 218

ldc_q931_reason= set LDC-Q931 disconnect reason correspondence

port= set other than default port 1720 for H.323 signaling

dont_make_cdr_for_ldc= define a list of local disconnect codes that prevent the MVTS from writing CDRs for calls completing with the LDCs on the list. The global list defined in this section overrides similar lists configured for individual static-IP GWs and registering endpoints.

dont_make_stat_for_ldc= define a list of local disconnect codes that prevent the MVTS from keeping statistics for calls that complete with LDCs from the list. The global list defined in this section overrides similar lists configured for individual static-IP GWs and registering endpoints

max_callrate= set the maximum traffic growth rate CAPS (calls per second

determine the Q.931 cause code sent to the origination gateway upon completion of the call owing to setting the parameter “gateway=” (dialpeer.cfg) to “NULL” or setting the parameter “hunt_stop=” to “1”.

q931_cause_override= substitute Q.931 cause codes

3.7 SECTIONS [RADIUS] AND [BACKUPRADIUS] The configuration parameters of the section [Radius] allow you to manage the MVTS system interaction with the RADIUS server.

To ensure continuous RADIUS service, should the primary RADIUS server fail, configure your MVTS for interoperation with an alternate RADIUS server using the parameters of the section [BackupRadius].

The table below provides a full list of configuration parameters of the section [Radius]. The table cells highlighted by tan background represent the configuration parameters that are common for both the sections [Radius] and [BackupRadius].

Table 10 meraproxy.cfg: configuration parameters of section [Radius]


acct_address=

specify the IP address of the accounting RADIUS server

acct_backup=

enable/disable copying of the accounting packets to the back-up Radius server provided it is configured in the section [Backup Radius] of meraproxy.cfg

acct_boot_msg=

set/reset the flag that controls sending the «Accounting Request – AcctStatusType – Accounting-on» requests

acct_enable= enable/disable RADIUS accounting

p.16 of 218


acct_interim_update=

set an interval for periodic update account messages sent to the RADIUS server in between the start accounting and stop accounting message

acct_leg_type= specify the type of emulated RADIUS accounting records

acct_port= define a port for RADIUS accounting

acct_stop_only= enable/disable sending stop accounting messages only to the RADIUS server

acct_type= define the preferred format of accounting

auth_address= specify the IP address of the authorization RADIUS server

auth_enable= enable/disable RADIUS authentication

auth_password_type= specify the password type

auth_port= specify a port for RADIUS authentication

debug_level= set the information detail level for packet logs covering the RADIUS functionality

dst_user_orig_leg= enable/disable username substitution into the UserName field of originating leg accounting packets sent to the RADIUS server

local_acct_port= assign a port for accounting responses from the RADIUS server

local_address= specify a local IP address for the bind function

local_auth_port= specify the MVTS’s authentication port

local_route_port= specify the MVTS port for RADIUS-aided external routing

q931_h323_disconnect_cause= enable/disable substitution of the AccessReject value received from the RADIUS server in the field CISCO VSA(30) h323-disconnect-cause for the actual Q931 disconnect cause

repeat_quantity= specify the number of send attempts for packets destined for the RADIUS server

repeat_time= set the duration of the pause (in seconds) between two consecutive send attempts

route_address= specify the IP address of a RADIUS server used for call routing

route_enable= enable/disable external routing provided by the RADIUS server

route_port= specify a port for routing exchange in addition to the value of the route_address= field

secret= specify a coding key (according to the ‘shared secret’ standard) for communication with the

p.17 of 218


RADIUS server

session_id_type= select a sessionID type for packets forwarded to the RADIUS server

stop_acct_level= control the size of Accounting packets sent to RADIUS

suppress_Q931_cause= enable/disable substitution of code 16 as a Q931 call termination cause

use_h323_ivr_in=

enable/disable user name substitution in the UserName field of the accounting packets forwarded to the RADIUS server

send_route_request_only= allow/disallow sending call authorization requests to the external routing system used for call routing

dont_send_stop_acct_for_ldc= disable/enable sending the Accounting Stop packet to the RADIUS server for calls, the termination attempts of which end with one of the LDCs specified in the field dont_make_cdr_for_ldc=

route_backup= enable/disable sending spare ARQs to an external routing server

3.8 SECTION [REDUNDANCY] Use the parameters of this section to configure interaction between the primary and failover MVTS servers (see [2] for details about possible MVTS redundancy layouts).

Table 11 meraproxy.cfg: configuration parameters of section [Redundancy]


challenge_no= configure the number of unanswered RAS queries from the standby MVTS that triggers the failover process

check_address= enter the set of parameters describing the system IP addresses for ingress traffic

check_period= define a time interval (in seconds) between successive TCP connects from the failover to the primary system

connect_timeout= set a TCP-connect timeout (in seconds)

master_address= specify an IP address for remote SSH access from the failover system to get down traffic-handling IP addresses

max_failed_retries= set the maximum acceptable number of failed connect attempts to the primary server

redundancy_type= determine the type of the MVTS failover/failback mechanism employed in case of the main server failure

slave_address= specify the IP address of the failover MVTS used for remote SSH access from the primary system to get down

p.18 of 218

traffic-handling IP addresses

master_gatekeeper= define the name of the primary MVTS server (actually the name of a section in the gatekeeper.cfg configuration file of the failover MVTS). The section describes the properties of the primary MVTS acting as the gatekeeper with which the failover MVTS registers (see [2]).

alternate_gatekeeper= specify GK name(s) that the MVTS backup server includes in the GRJ (GatekeeperReject) response sent to a remote host as a list of GK options

max_failed_addresses= specify the maximum allowed number of inactive IP addresses for the main MVTS host

3.9 SECTION [LAR] The parameters of this section serve to configure the look-ahead routing function and related system properties.

Table 12 meraproxy.cfg: configuration parameters of section [LAR]


route_cause= define call termination reasons that invoke LAR function (attempts to reroute the call)

validation_gap= set a delay time for the packets destined for the origination gateway to improve chances of a successful call setup

3.10 SECTION [MEDIA] Skip the settings of this section if you have a single-server system, as the section [Media] serves to configure a signaling MVTS that is a part of the MVTS cluster facility [3].

The parameters of this section serve to configure interaction with the media MVTS (media MVTS is an element of MVTS-based cluster solutions). The meraproxy.cfg file of global settings of MVTS single-server versions does not include this section.

Table 13 meraproxy.cfg: configuration parameters of section [Media]


address= specify the IP address of the Media MVTS

call_radix= specify the number of calls to be used in the route performance assessment of the MVTS-based cluster

min_acd= set the lowest admissible ACD for the media server

min_asr= set the minimum ASR value for the media server

p.19 of 218

mode= define a call termination method

no_connect_suspend_time= set the media MVTS time-out in case there is no TCP connection with the server

suspend_time= specify suspension time (in minutes) for a low ASR route

3.11 SECTION [PROXY] A set of parameters used to determine the MVTS proxy characteristics.

Table 14 meraproxy.cfg: configuration parameters of section [Proxy]


alias_route_path= specify an alternate routing instruction if the OS kernel routing table reading is disabled

dscp_byte_media= define the value of the field DSCP in the IP headers of datagrams sent by MVTS

dscp_byte_signaling= define the value of the field DSCP in the IP headers of signaling packets sent by MVTS

local_ip_manager_mode=

determine the system’s behavior in situations when all IPs in the list specified in the local_address=

field are congested with traffic

local_ip_manager=

configure bandwidth allotments (maximum bandwidth for ingress and egress traffic) for local IP addresses

read_route_table= enable/disable routing table reading by the OS kernel

force_proxy= enable/disable the function of forced traffic proxying

internal_network_mask= specify the LAN mask to avoid traffic proxying on the local area network

local_address= define a local address to be used in media traffic proxying

local_address_redefine= substitute the local address involved in call setup for another address to be used for media traffic proxying

alias_route_path_file= specify the the name of and path to the file with routing alternatives

3.12 SECTION [SNMP] Section [SNMP] contains configuration parameters determining SNMP-related parameters of the system.

p.20 of 218

Table 15 meraproxy.cfg: configuration parameters of section [SNMP]


community= specify the community name for access environment

contact_info= enter contact information about the system owner/operator

index_valid_time=

represent the period of time since MVTS start

local_port= specify the MVTS port for SNMP

snmp_enable= enable/disable response to SNMP queries

system_location= specify the system location

system_name= give the system a unique name

trap_address= specify an address for trap messages

trap_community= specify the name of the trap receivers community

trap_email_cmd= specify the command, which triggers e-mail sending (can be the name of a script)

trap_email_from= define the content of the “From:” field in e-mail messages

trap_email_period= specify the time of periodic e-mails

trap_email_subject= specify the content of the ‘Subject’ line in e-mail messages

trap_email= specify an address for trap-message reports

trap_enable= enables/disables SNMP trap messages

trap_level= set significance level of SNMP trap messages

trap_port= define a port for SNMP trap messaging

trusted_address=

specify a list of source IP addresses whose SNMP queries will be accepted by the system

3.13 SECTION [STATISTICS] Use the parameters of the section [Statistics] to configure the system statistics management.

Table 16 meraproxy.cfg: configuration parameters of section [Statistics]


asr_alert_email= specify an e-mail address for ASR deterioration alerts to the system administrator

call_radix= specify an amount of calls to be used in route performance analysis

call_sampling_number= specify a number of attempted calls to be used in

p.21 of 218


the serviceability assessment of suspended routes

file= change the name prefix of (and/or path to) the file to which the MVTS saves statistics

max_scd= set the maximum acceptable SCD (SETUP-CONNECT delay) in seconds

min_acd= set the lowest ACD level that will trigger email alerts with a list of the gateways or RAS users whose ACD or ASR has dropped below the configured value

min_asr_mode= define an ASR assessment method (conventional or the MVTS intrinsic) to be used for generation of a list with low-ASR gateways (those whose ASR has dropped below the level specified in min_asr= field in the section [Statistics] of meraproxy.cfg).

min_asr= set the lowest ASR level that will trigger email alerts when reached

min_scd= define a global SCD (Setup-Connect delay) minimum in seconds

no_empty= allow/disallow empty statistics files

period= configure file rotation for statistical data files

reset_after_save= allow/disallow statistics data clearing after saving it to a file

route_statistics_enable= enable/disable collection of statistics for routes

set_route_acd= set the lowest ACD that will block routes the ACD of which drops below the set value

set_route_asr_mode= define the method of calculating ASR (Answer Seizure Ratio) when smart routing is enabled

set_route_asr= set the lowest acceptable ASR for routes

smart_routing= engage/disengage smart routing based on the statistics analysis

stat_email_cmd= enter a command for dispatch of an email with statistics (e.g. name of a script)

stat_email_from= specify the content of the “From:” field in e-mail messages

stat_email_subject= specify the content of the Subject line in e-mail messages

stat_email= specify a destination email address for call statistics reports

stat_file_attr= set attributes of the statistical data file

stat_renewal_time=

define a time interval for periodic obsolete data removals (e.g. data about about gateways that are not in the configuration any more)

p.22 of 218


statistics_enable= enable/disable statistics keeping mechanism

suspend_time= specify suspension time for low-ASR routes

time_span=

define the longest no-updates period, after which the current statistics (for a gateway and the dial peer) gets cleared

total_duration_saving= enable/disable saving the data about total duration of calls so that this information survives MVTS restarts

asr_mail_period= set a time interval for periodic email notifications caused by min_asr=, min_acd=, min_scd=, max_scd= threshold violations

call_rate_period= define a time interval (in seconds) for calculation of the average traffic growth rate value (for individual gateways/RAS users and globally)

reset_active_time_period= define the reset interval for quantity statistics about traffic processed by RAS users and gateways registered with the MVTS

p.23 of 218

4 GATEWAY.CFG The gateway.cfg configuration file contains information about ‘static’ endpoints (that is the gateways whose IP addresses are known and they do not need to register with the MVTS gatekeeper.)

The properties and capabilities of such static gateways are configured by creating individual sections of configuration parameters and setting pertinent values. A properly named section with configured gateway properties provides a gateway record. The MVTS uses section names as H.323 aliases, so make sure that section names are unique.

In operation modes other than public access (public_access=0 ) the MVTS can establish a call connection between the calling and the called party only when both the calling and the called gateway/RAS user are configured in the gateway/RAS user data file (gateway.cfg or user.cfg).

Table 17 gives a full listing of configuration parameters that may constitute an individual gateway record.

Table 17 gateway.cfg: configuration parameters of an individual GW record


acct_enable= enable/disable RADIUS accounting for the GW being configured

address= specify the IP address or DNS name of the gateway (you can also use the CIDR notation for addresses of origination gateways)

alert_prog_ind_orig=

set ProgressIndicator of Alert and Progress messages in the packets that the call terminator sends the call originator

alert_prog_ind_term=

set the ProgressIndicator value of Alert and Progress messages in call-terminator bound packets

allowed_prefix= enter a list of destination number prefixes that the MVTS will accept from the gateway originating a call

always_accessible= enable/disable blocking the gateway that fails call termination attempts returning LDC 101 or 112

ani_allow= specify a list of authorized source numbers for gateway being configured

arq_alive_time= specify a period of time for the MVTS to wait for the arrival of SETUP with the CallID, identical to the one, sent to the MVTS from this gateway in the LRQ packet

auth_enable= enable/disable RADIUS authorization for the GW

bearer_capability= control the value of the field ‘bearer

p.24 of 218


capability’ in the headers of Q931 messages

call_connect_delay= define a delay for CONNECT sending to the call originator

capacity= define the maximum number of concurrent calls that the MVTS may route to the gateway

check_h225_version= enable/disable the h.225 protocol version check

check_rtcp_address= enable/disable address correctness verification

check_rtp_source= check IP addresses of media sources

codec_allow= specify a list of codecs supported by the gateway

codec_deny= define a list of codecs not supported or misinterpreted by the gateway

compatibility= specify a 4-byte mask of the gateway capabilities for compatibility check

converter=

specify the name of the SIP/H.323 converter in the record of a termination gateway

cut_fast_connect_refused= enable/disable removal of the fastConnectRefused field from all signaling packets

cut_h323_id= enable/disable removal of the h323_id field from transmitted packets

cut_non_standard_control=

enable/disable removal of the non_standard_control field from transmitted packets

cut_non_standard_data= enable/disable removal of the field nonStandardData from Setup

cut_symmetric_operation_required=

enable/disable removal of the symmetric_operation_required field from transmitted packets

cut_tunnelled_signalling_message=

enable/disable removal of the tunnelled_signalling_message field from transmitted packets

datacap_deny= specify a list of data capabilities not supported by the gateway

debug_level=

use this parameter to set an individual level of information details contained in logs for call sessions involving the gateway

direct_call_allowed= configure the signaling MVTS in a two-layer MVTS cluster to directly receive incoming signaling by-passing the load balancer

disallowed_prefix= enter a list of destination number prefixes

p.25 of 218


that the MVTS will not accept from the origination gatewayl

dont_make_cdr_for_ldc= define a list of local disconnect codes that prevent the MVTS from writing CDRs for calls that complete with LDCs on the list

dont_make_stat_for_ldc= define a list of local disconnect codes that prevent the MVTS from keeping statistics for calls that complete with LDCs from the list.

dscp_byte= define the value of the DSCP byte of a datagram sent to the gateway, the configuration of which contains the set dscp_byte= parameter

dst_acct_enable= enable/disable accounting for destination gateways

dst_allowed_prefix= define allowed prefixes of destination numbers

dst_disallowed_prefix= define disallowed prefixes of destination numbers

dst_translate=

src_translate=

define a translation pattern for the source (src_translate=) and destination (dst_translate=) number

exchange_calling_redirect_number= allow/disallow exchange of the values of the CallingPartyNumber and RedirectingNumber fields of SETUP

expire_date= define the gateway operation term – the date after which the MVTS stops exchanging traffic with the gateway

fake_rtcp= enable/disable RTCP faking for gateways devoid of the RTCP capability

force_alerting=

set a time interval (milliseconds) after which the MVTS will send a neutral Alerting message to the originating GW

force_call_proceeding= set a delay (milliseconds) after which the MVTS forwards a CallProceeding message with neutral content to the originating GW

force_originate_telephony= together with the parameter “nas_port_name=” this parameter allows discrimination of vendors associated with the same termination gateway

gatekeeper= specify the name of the GK through which calls get to the destination gateway

gateway_mode= set the GW operating mode

gateway_type= specify the GW type

group= enter the name of the group the GW belongs to

p.26 of 218


h323_gw_id= specify the H.323 alias of the call source

hunt_mode= define a load-balancing technique for termination gateways with more than one IP address specified in the field address=

ignore_lar_fault= enable/disable further routing cessation caused by a failed termination attempt via the previous route

in_dst_translate= set a pattern for preliminary translation of the call destination number

in_src_translate= set a pattern for preliminary translation of the call source number

interdigit_timeout= configure the maximum time interval (in milliseconds) between two subsequent Q931 Information messages sent by the origination gateway after the SETUP message

ip_precedence= set precedence for IP packets arriving from the gateway

local_address= provide a list of local IP addresses used both for egress and ingress traffic

lrq_allowed_only= enable/disable authorization of a call by its CallID

mask= specify the mask for the gateway calling connections

max_call_duration_src=

max_call_duration_dst=

configure the maximum duration of call session for origination (max_call_duration_src=) and termination (max_call_duration_dst=) gateways

max_call_duration= set a maximum duration for calls routed to the gateway

max_callrate= set the maximum traffic growth rate CAPS (calls per second) for static gateways individually

max_incoming_time=

define the maximum amount of traffic minutes that the MVTS will accept from the gateway

max_outgoing_time= define the maximum amount of traffic minutes that the MVTS will forward to the gateway

max_scd= set an individual SCD (setup-connect delay) limit for gateways

max_total_time= set a limit for the gateway ingress and egress traffic (in minutes)

min_acd= set an acceptable minimum ACD for the gateway

min_asr= enter an ASR value that will trigger bad ASR

p.27 of 218


email alerts

min_scd= define an SCD minimum for the gateway in seconds

min_success_duration= set a successful call duration minimum (in milliseconds) for the gateway

nas_port_name= together with the parameter “force_originate_telephony= ” this parameter allows discrimination of vendors associated with the same termination gateway

nat_rtp= enable NAT traversal when the destination gateway is sitting behind a NAT router

no_faststart= allow/disallow removal of the fastStart field from SETUP

no_packet_q931_cause= enter a Q931 call disconnect reason value that will appear in CDRs when the call is aborted upon expiry of the configured no-packet-to-originator timeout

no_packet_timeout= define the length of the wait period within which the dispatch of a packet to the originator is expected.

no_port_clean= enable/disable port clearing

no_tunnelling= control the value of the H245Tunnelling field of SETUP

number= specify the gateway’s phone number

numbering_plan= configure the type:plan parameter for the gateway

pass_display_ie= allow/disallow removal of the ‘display’ Information Element from packets sent to the gateway

password= specify the user password. The password is used in the system together with the user name for authorization purposes

port= specify the gateway port for signaling traffic

presentation_screening_allowed=

enable/disable removal of the fields Presentation and Screening from transferred packets and control the use of theconfiguration parameterspresentation= and screening=

presentation= manipulate the field presentationIndicator in SETUP

proxy_type= define a type of proxy operation for the gateway

p.28 of 218



radius_gw_id= set the h323_gw_id= and h323-remote-id RADIUS VSA fields for the originating and termination gateways respectively

radius_remote_address= enable/disable IP address substitution

radius_uses_callid= enable/disable substitution of the call ID for the conference ID in messages h323-incoming-conf-id and h323-conf-id sent to the RADIUS server

rbt_timeout= set the maximum wait time for Alert and/or ProgressIndicator packets from the termination gateway (in seconds)

reset_can_overlap_send= set or reset the canOverlapSend field of Setup

route_cause= specify call termination reasons that invoke the LAR function (i.e. attempts to reroute the call)

screening= specify the value of the field screeningIndicator in SETUP

set_h225_version= configure an h323 protocol version value that should be substituted in the parameter protocolIdentifier of H.225.0 messages

siphit_dst_codec= specify a list of codecs sent by the MVTS to the SIPHIT module to enable a session with the call terminator

siphit_src_codec= specify a list of codecs that the MVTS sends the SIPHIT module to enable a session with the origination endpoint

smart_routing_enable=

enable/disable smart routing (i.e. ASR and ACD monitoring)

src_numbering_plan= dst_numbering_plan=

use these fields to configure the type:plan parameter for the calling (src-_numbering_plan=) and the called (dst_numbering_plan=) gateways independently

src_presentation_screening_allowed= control the use of the src_presentation= and src_screening= configuration parameters

src_presentation= specify the value of the presentationIndicator parameter upon receipt of the SETUP message from the call originator

src_screening= define a value of the screeningIndicator parameter upon receipt of the SETUP message from the call originator

stat_group= group gateways into a common statistics

p.29 of 218


group

tcp_connect_timeout= set tcp_connect wait time

tos_precedence= set the precedence of IP packets, sent to the gateways, the configuration of which contains the set tos_precedence= parameter

use_info_digits= allow/disallow the use of digits received in INFORMATION packets arriving from the origination gateway after SETUP

user= specify the endpoint name in the system

validation_gap= set a packet forwarding delay in milliseconds for the gateway during which call setup packets exchange with the origination gateway will be suspended

validation_msg= specify the message whose arrival will resume the suspended exchange with the call originator during a call setup

p.30 of 218

5 USER.CFG All information about RAS signaling clients of the gatekeeper is stored in the RAS user datafile. It is a plain text file with a name assigned to it by the System Administrator (user.cfg by default) in the user_cfg= field of the general configuration file meraproxy.cfg. It consists of sections each one representing a single user. The user's name (alias) is assigned by the System Administrator and is used by the MVTS for the purposes of user identification and correlation of the user datafile with the dial plan (dialpeer.cfg). The user parameters needed by the MVTS are stored in the fields of individual user records in the data file. Contrastingly to the 'static' VoIP entities whose data is readily available from the records configured in the gateway file gateway.cfg, the RAS users are referred to as 'dynamic', because their IP addresses can not be known. To provide the gatekeeper component of the MVTS with the information it needs to exchange traffic with a dynamic user, the latter periodically registers with the MVTS. Such 'dynamic' or RAS users communicate with the gatekeeper through exchange of RAS messages. To make your work with the RAS-user datafile meaningful make sure the gatekeeper functionality of the MVTS is enabled (the gatekeeper_enabled= flag in the section [Gatekeeper] of the configuration file meraproxy.cfg is set to 1). For adding data to the RAS-user datafile or modifying the existing entries insert new records or edit the available data and save the changes. Authorization of RAS users can be performed through RADIUS only. To this end, the special section [Default] is added to the RAS-user data file with the user= field set tо 'default'. In this case, the system registers all users through RADIUS authentication (provided this service is enabled - the auth_enable= flag in the section [Radius] of the system configuration file meraproxy.cfg is set to 1). Therefore, the settings of the [Default] section will apply to all dynamically registered entities whose records are not available in the user.cfg data file. During RADIUS authentication of RAS users in compliance with the user=default setting and the [Default] section of the user.cfg file, the RADIUS server can return the AccessAccept packet with the CISCO AV-Pair(1) field containing a list of numbers. This feature permits making calls to dynamically registered users (i.e. RAS entities) rather than only receiving calls from them. Simply stated, if the AccessAccept arriving in response to the AccessRequest during RAS user authentication contains a list of numbers in the xpgk-ep-number field (for example, xpgk-ep-number=78312778708;78312788865), then termination of the next outbound call, which has the destination number 78312778708 or 78312788865 and happens to be routed via a dialpeer with the gateway=ENDPOINTS setting, will be attempted through the RAS user.

Configuring a gateway both as a static VoIP endpoint represented by a record in the gateway.cfg file and a RAS user, represented by a record in the user.cfg file will result in an error (see paragraph 6.1 “Troubleshooting” of [1]).

p.31 of 218

Table 18 presents a listing of RAS user configuration parameters that make up an individual endpoint record in the user.cfg file.

Table 18 user.cfg: configuration parameters of a RAS user


acct_enable= enable/disable RADIUS accounting for the RAS user being configured

alert_prog_ind_orig= set the ProgressIndicator value in the Alert and Progress messages

alert_prog_ind_term= set the ProgressIndicator value of the Alert and Progress messages in the packets forwarded to the call terminator

allowed_prefix= define a list of prefixes to be allowed by the MVTS from the RAS user originating a call

always_accessible= enable/disable blocking the RAS user if a call termination attempt through this RAS user fails returning LDC 101 or 112

ani_allow= specify a list of authorized ANI-numbers for the calling RAS user

auth_enable= enable/disable RADIUS authentication of a given RAS user

call_connect_delay= define a delay time for Connect sent to the call originator

capacity= specify the maximum number of concurrent calls that the MVTS can route through the RAS-user

check_rtcp_address= enable/disable address correctness verification

check_rtp_source= check IP addresses of media sources

check_src_number= enable/disable additional checks of the calling party number for the RAS user

codec_allow= specify a list of codecs supported by the endpoint

codec_deny= specify a list of codecs not supported or misinterpreted by the endpoint

compatibility= specify a 4-byte mask of the gateway capabilities for compatibility checks

converter= specify the name of a SIP/H.323 converter in the record of a termination RAS user

cut_fast_connect_refused= disable/enable removal of the fastConnectRefused field from all signaling packets

cut_non_standard_data= enable/disable removal of the field

p.32 of 218


nonStandardData from Setup

datacap_deny= define a list of data capabilities not supported by the gateway

debug_level= set the desired information detail level of log writing for the RAS user

dialpeer= enter the name of the RAS registering gateway

disallowed_prefix= enter a list of destination number prefixes that the MVTS will not accept from the origination gateway

dst_acct_enable= enable/disable accounting in configuration of termination RAS users

dst_allowed_prefix= define allowed prefixes of destination numbers

dst_disallowed_prefix= define disallowed prefixes of destination numbers

dst_translate= define a translation pattern for the destination number

endpoint_ttl= set a registration update interval for the RAS user

expire_date= define the operation term for the gateway - the day after which the MVTS will stop exchanging traffic with the RAS user

fake_rtcp= enable/disable RTCP packet faking for gateways devoid of the RTCP capability

force_alerting= set a time interval (in milliseconds) after which a neutral Alerting message will be sent to the origination gateway

force_call_proceeding= set the delay time (milliseconds) after which the MVTS forwards a CallProceeding packet with neutral content to the origination RAS user

gateway_type= specify the gateway type

group= specify the group the RAS user belongs to

h323_gw_id= specify the Source H323 Alias Identifier which sometimes becomes necessary for a remote RAS user

ignore_lar_fault= enable/disable blocking of route search if the call termination attempt via the previous route was unsuccessful

in_converter= specify a converter for ingress calls originating from the RAS-user

in_dst_translate=

in_src_translate=

set patterns for preliminary translation of the call source (in_src_translate=) or destination (in_dst_translate=) number

p.33 of 218


in_local_address= differentiate originating gateways with the same signaling addresses (subnet masks)

ip_precedence= set precedence of IP-packets arriving from the RAS user

local_address= define a list of local IP-addresses for egress and ingress traffic

max_call_duration= set the maximum duration of a call routed to this termination RAS user

max_incoming_time= impose a traffic origination limit on the RAS user

max_outgoing_time= impose a traffic termination limit on the RAS user

max_scd= set an individual SCD (Setup-Connect Delay) threshold for RAS users

min_acd= set the minimum ACD level for an individual RAS user

min_asr= set the minimum ASR (Answer Seizure Ratio) level that triggers e-mail alerts when reached

min_scd= define a minimum SCD value for the RAS-user

min_success_duration= set the minimum call duration time for the RAS user

force_originate_telephony= together with the parameter “nas_port_name=” this parameter allows discrimination of vendors associated with the same termination gateway

nat_call_port_type= configure the MVTS to take the signaling port number from the RRQ packet header or from the field callSignalAddress

nat_call_port= define a port number where the MVTS will forward calls intended for the dynamically registered user located behind a NAT-router

nat_rtp= enable/disable NAT traversal for RTP packets

no_faststart= allow/disallow removal of the Faststart field from Setup

no_packet_q931_cause= configure a Q931 disconnect reason value that will appear in CDRs when the call is aborted upon expiry of the configured no-packet-to-originator timeout

no_packet_timeout= define the length of the wait period within which the dispatch of a packet to the originator is expected

no_port_clean= engage/disengage the port clearing process

no_tunnelling= allow/disallow changing the value of the Tunneling field in Setup

p.34 of 218


number= specify a gateway’s phone number

numbering_plan= define a plan parameter for communication with the RAS user

pass_display_ie= allow/disallow removal of the ‘display’ information element from packets sent to the RAS user

password= enter user’s password

presentation_screening_allowed= allow/disallow the use of the configuration parameters presentation= and screening=

presentation= specify the value of the presentationIndicator parameter

proxy_type= set proxy mode attribute for the gateway traffic


radius_gw_id= set the h323_gw_id and h323_remote_id RADIUS VSA fields for the originating and termination RAS users respectively

radius_remote_address= enable/disable IP address substitution

radius_uses_callid= enable/disable substitution of the call ID for the conference ID in messages h323-incoming-conf-id and h323-conf-id sent to the RADIUS server

rbt_timeout= set the maximum wait time for arrival of the Alert and/or ProgressIndicator packets from the termination gateway (in seconds)

reg_address= specify the ‘static’ IP-address of the RAS-user

reset_can_overlap_send= set/reset the canOverlapSend field of Setup

route_cause= specify call termination reasons to invoke the LAR function (attempts to reroute the call)

screening= define the value of the screeningIndicator parameter

set_h225_version= configure an h323 protocol version value that should be substituted in the parameter protocolIdentifier of H.225.0 messages

smart_routing_enable= enable/disable smart routing

src_numbering_plan= dst_numbering_plan=

configure a numbering plan for the calling (src_numbering_plan=) and the called (dst_numbering_plan=) numbers independently

src_presentation_screening_allowed= use this parameter to control the use of the src_presentation= and

p.35 of 218


src_screening= configuration parameters

src_presentation= define the value of the presentationIndicator parameter upon receipt of the SETUP message from the call originator

src_screening= define the value of the screeningIndicator parameter upon receipt of the SETUP message from the call originator

src_translate= set a number translation pattern for the source number

user= provide a user’s name

validation_gap= set the packet forwarding delay (in milliseconds) for the RAS-user, during which call setup packets exchange with the origination gateway will be suspended

validation_msg= specify the message whose arrival will resume the suspended exchange with the call originator during the call setup process

check_h225_version= enable/disable the h.225 protocol version check

siphit_src_codec= specify a list of codecs that the MVTS sends the SIPHIT module to enable a session with the origination endpoint

dont_make_cdr_for_ldc= define a list of local disconnect codes that prevent the MVTS from writing CDRs for calls completing with the LDCs on the list.

dont_make_stat_for_ldc= define a list of local disconnect codes that prevent the MVTS from keeping statistics for calls that complete with LDCs from the list.

exchange_calling_redirect_number= allow/disallow exchange of the values of the CallingPartyNumber and RedirectingNumber fields of SETUP

use_info_digits= allow/disallow the use of digits received in INFORMATION packets arriving from the origination gateway after SETUP

siphit_dst_codec= specify a list of codecs sent by the MVTS to the SIPHIT module to enable a session with the call terminator

stat_group= group gateways into a common statistics group

max_callrate= set the maximum traffic growth rate CAPS (calls per second) for RAS-users individually

nas_port_name= together with the parameter “force_originate_telephony= ” this parameter allows discrimination of vendors associated with the same termination gateway

dscp_byte= define the value of the DSCP byte of a datagram sent to the RAS user, the

p.36 of 218


configuration of which contains the set dscp_byte= parameter

tos_precedence= set the precedence of IP packets, sent to the RAS user, the configuration of which contains the set tos_precedence= parameter

bearer_capability= control the value of the field ‘bearer capability’ in the headers of Q931 messages

max_call_duration_src=

max_call_duration_dst=

configure the maximum duration of call session for origination (max_call_duration_src=) and termination (max_call_duration_dst=) RAS users

interdigit_timeout= configure the maximum time interval (in milliseconds) between two subsequent Q931 Information messages sent by the origination RAS user after the SETUP message

reg_h323_id= allow additional verification of a registration request arriving from the IP address specified in the parameter reg_address=

p.37 of 218

6 GATEKEEPER.CFG The gatekeeper data file gatekeeper.cfg contains information about the gatekeepers, with which the MVTS is supposed to register as a client.

To configure your MVTS application for interworking with remote gatekeepers, make the necessary additions and modifications in the gatekeeper data file.

Note: Modification in the gatekeeper data file may involve the necessity to modify the gateway data file gateway.cfg accordingly.

All data pertaining to an individual gatekeeper is stored in the file in form of sections. The table below explains the meaning and purpose of configuration parameters found in an individual gatekeeper section.

Table 19 gatekeeper.cfg: configuration parameters of a gatekeeper record

Configuration parameter

serves to...

address= specify the IP address or DNS name of the gatekeeper

id= set the gatekeeper’s identifier

keepalive_type= define the type of registration message to be sent to the remote gatekeeper during re-registration

keepalive= set the time interval (in seconds) of repeated registration with the gatekeeper

local_address= specify a local IP address for communication with the remote gatekeeper

options= enable/disable translation of the destination number in positive replies received from the registration gatekeeper

password= set the user’s authorization password

port= specify other than default port (1719) for receipt of RAS traffic

prefixes= define a list of the gateway prefixes transmitted to the gatekeeper (when the make-believe flag is reset, i.e. terminal=0) or the list of E.164 aliases (when terminal=1)

security= select the gatekeeper authorization method

terminal= determine the way the remote gatekeeper treats the MVTS

type= specify the type of interaction between the MVTS and the gatekeeper it registers with

user= specify a user’s name for gatekeeper authorization

master_gatekeeper= indicate the name of the primary gatekeeper (name of section in gatekeeper.cfg) in configuration of aternate (slave) gatekeepers

slave_gatekeeper= indicate alternate gatekeepers (names of sections in gatekeeper.cfg) in configuration of the primary gatekeeper

p.38 of 218

7 DIALPEER.CFG The configuration file dialpeer.cfg comprises a set of records that identify possible directions that calls originated by static endpoints (gateway.cfg) and RAS users (user.cfg) can follow.

An individual call direction characterized by the termination gateway name, operating time, number translation patterns for the call source and destination number and some other features provides a dial peer, and dialpeer.cfg being a collection of dial peers, i.e. call path options makes a kind of a calling or dial plan.

Selecting a dial peer essentially means precedence-dependent determination of the optimal call route for a pair of call parties. The selected dial peer provides the data necessary to establish a call.

Modifications in the dial plan may apply to one or several dial peers. Once changes have been made make sure the modified dial plan correlates with the gateway data file. Carry out the reload config command in the administration console for the newly made changes to take effect.

Refer to Table 20 for a listing of configuration parameters that constitute an individual dial peer record.

Table 20 dialpeer.cfg: configuration parameters of a dialpeer record


active_time= specify “business hours” for the dial peer. This setting affects call routing decision made by the system

bill_translate= set the number translation patterns for accounting purposes

call_connect_delay= define a delay time (in configuration of a given dialpeer) for CONNECT sent to the call originator

capacity= specify the maximum number of simultaneous calls that the MVTS can route through the given dialpeer

codec_allow= specify a list of codecs supported by the gateway

p.39 of 218


codec_deny= define a list of codecs not supported or misinterpreted by the gateway

display_ie_translate= define translation patterns for the content of the ‘display’ information element

dst_bill_translate= set the destination number translation patterns for billing purposes

dst_exclude=

src_exclude=

define a list of disallowed dial peers (phone numbers)

dst_pattern=

src_pattern=

define a pattern for the called (dst_pattern=) and/or the calling (src_pattern=) party number

dst_translate=

src_translate=

define a follow-up number translation pattern for the calling (src_translate=) and the called (dst_translate=) parties

gateway= specify the internal name of the gateway (i.e. the name of a section from user.cfg or gateway.cfg) to which the call will be forwarded when the dialpeer is selected

group_allow=

group_deny=

define a list of gateway groups for which outbound calls through the dialpeer are allowed or denied

group_translate= define a user group translation

hunt_mode= determine a load balancing technique for the gateways defined in the gateway= field of the dial peer record

hunt_stop= stop further route search when the dial peer is found but the associated gateway is inaccessible or overloaded

p.40 of 218


max_scd=

min_scd=

set maximum/minimum notification thresholds for the SCD value, respectively

min_acd= set notification threshold for the ACD value

min_asr= set notification threshold for the ASR value

only_first_gateway= enable/disable use of the first gateway only in the gateway= parameter of the dialpeer

override_proxy_mode= set individual proxy mode for the dial peer to override the global proxy mode setting

override_user= perform user name (the parameter gateway=) substitution when the necessity to do authorized call termination under some other user’s name arises

priority= define dial peer precedence value that permits selection of a dial peer from a set of appropriate ones

q931_cause= specify Q931 termination causes for the dial peers with the gateway=NULL setting in the record

random_value= specify numeric intervals for the MVTS to select random values from. The selected values are then inserted into number translation fields in place of the $rnd$ macros

set_route_asr= set the lowest acceptable ASR for individual dialpeers when the smart routing function is enabled

src_bill_translate= define a source number translation rule for convenience of billing

p.41 of 218


user_translate= derive the user name/password from dst_number=

hunt_sort_period= set a period of time for rotation of the gateways specified in the field gateway=

p.42 of 218

8 CONFIGURATION HOWTOS

8.1 CONFIGURATION CASE 1: ADDING TWO STATIC GATEWAYS

Fig. 1 Linking two static gateways through MVTS

In the simpliest operating scenario involving two static gateways (see Fig. 1) you have to add records describing the gateways to the gateway.cfg file and configure two dial peers – one for calls from Moscow to New York and one for calls from NY to Moscow.

Table 21 shows how configuration records for a Cisco AS5300 and a VocalTec gateway used in this situation would look like.

The column for meraproxy.cfg, the file of global settings, is left blank intentionally as it is irrelevant in this scenario.

Focus on the settings that describe the gateways and dialpeer – gateway bindings in the gateway.cfg and dialpeer.cfg files.

p.43 of 218

Table 21 What you need to write in the MVTS configuration files to implement connectivity scenario 1

meraproxy.cfg gateway.cfg dialpeer.cfg user.cfg gatekeeper.cfg

[Сisco_5300] [Call_to_NYC]

address=xx.xx.xx.xx dst_pattern=1212[0-9]*

gateway_mode=3 gateway=Cisco_5300

port=1720

capacity=30 [Call_2_Moscow]

proxy_type=1 dst_pattern=7095[0-9]*

gateway=VocalTec

[VocalTec]

address=yy.yy.yy.yy

port=1720

gateway_type=2

capacity=30

p.44 of 218

8.2 CONFIGURATION CASE 2: CONFIGURING SEVERAL STATIC GATEWAYS AND ADDING GROUPS

Fig. 2 Grouping static endpoints for facilitation of configuration tasks

The basic intent of this a bit complicated communication setup involving four gateways and complex routing rules is to illustrate the use of gateway groups for facilitation of configuration tasks.

Imagine a communication system with a large quantity of VoIP endpoints where only selected endpoints are allowed to make calls through some dial peer. To avoid the need to add the commensurate amount of dial peers, you can just group the eligible endpoints and use the parameter group_allow= in the dial peer record.

In the communication scenario presented in Fig. 2 only New York gateways are allowed calls to Argentina. The simplest solution is to group all New York endpoints under the group name NY and use the group_allow= parameter in the Argentina dial peer to accept calls only from the NY group members.

See in Table 22 how the New York gateways are grouped under the group name NY, and the NYC_to_Arg dial peer is configured to allow calls for the NY group members only.

p.45 of 218

Table 22 Using groups to facilitate configuration tasks

meraproxy.cfg gateway.cfg dialpeer.cfg user.cfg gatekeepr.cf

g

[NYC1] [NYC]

address=xx.xx.xx.xx dst_pattern=1212[0-9]*

group=NY gateway=NYC1; NYC2

gateway_mode=3 hunt_mode=2

port=1720

proxy_type=1 [Moscow]

dst_pattern=7095[0-9]*

[NYC2] gateway=Moscow

address=yy.yy.yy.yy

group=NY [NYC_to_Arg]

gateway_mode=3 dst_pattern=54[0-9]*

port=1720 group_allow=NY

proxy_type=1 gateway=Arg

[Moscow]

address=zz.zz.zz.zz

gateway_mode=3

port=1720

proxy_type=1

[Arg]

address=xz.xz.xz.xz

gateway_mode=3

port=1720

proxy_type=1

p.46 of 218

8.3 CONFIGURATION CASE 3: ADDING A REGISTERING ENDPOINT (ATA ADAPTER) SITTING BEHIND A NAT ROUTER

This connectivity scenario illustrates the situation when you need to configure registering users with access through an ATA 186 adapter located behind a NAT router.

The users User1 and User2 shall be configured with the ability to originate and terminate calls. The ATA_to_GW1 dial peer is configured to handle calls with leading prefix 416 in the number. To enable NAT traversal, the nat_rtp= flag in the ATA_user1 and ATA_user2 record is set.

Make sure that the parameter gateway= in the 2_ATA_ENDPOINTS destination has the ENDPOINTS macroname as its value to initiate a perfect match search for the telephone number of the called party.

Fig. 3 Configuring a RAS user and enabling NAT traversal

To enable the use of the ATA 186 both as a call originator and call terminator, you will need to configure it accordingly. The telephone numbers of User1 and User2 are entered in the UID0 and UID1 fields of the ATA-186 configuration dialog box (see Fig. 4). For successful registration with the MVTS gatekeeper, enter 1 in the UseLoginID field and fill in the LoginID1 and LoginID2 fields with the respective user|password parameters from the user.cfg file of the MVTS session controller (first_user|passwd1 and second_user|passwd2 as in the example).

p.47 of 218

Fig. 4 Configuring ATA 186 adapter

Table 23 Adding registering users and allowing NAT traversal

gateway.cfg dialpeer.cfg user.cfg

[Static_GW1] [DP_ATA_ENDPOINTS] [ATA_user1]

address=xx.xx.xx.xx dst_pattern=70954444[0-9]{3} user=first_user

gateway_mode=3 gateway=ENDPOINTS password=passwd1

port=1720 number=70954444333

proxy_type=1 [DP_ATA_to_GW1] group=ATA_users

dst_pattern=416[0-9]* proxy_type=1

group_allow=ATA_users nat_rtp=1

gateway=Static_GW1

[ATA_user2]

user=second_user

password=passwd2

number=70954444555

group=ATA_users

proxy_type=1

nat_rtp=1

p.48 of 218

8.4 CONFIGURATION CASE 4: IMPLEMENTING RADIUS AUTHORIZATION AND ACCOUNTING

Fig. 5 Allowing for RADIUS authorization and accounting

For authorization of all dynamically registered users through a RADIUS server, set the auth_enable flag (auth_enable=1) in the meraproxy.cfg file (section [Radius]). To enable RADIUS accounting, set the acct_enable flag (acct_enable=1) in the same section.

To disable RADIUS authorization for individual gateways, reset the auth_enable flag (auth_enable=0) for relevant gateways in the gateway.cfg or user.cfg files.

Note: If the auth_enable= flag is reset (auth_enable=0), any RAS user can access the MVTS server without authorization, provided the auth_enable= parameter in the section representing this RAS user is also set to 0.

To allow any registering endpoint that is not configured in the user.cfg file to register with the MVTS gatekeeper, add the section [Default] to the file user.cfg and set user=default:

user.cfg

p.49 of 218

[default]

user=default …

The settings of the section [Default] will apply to any dynamically registered gateway that is not explicitly specified in the user.cfg file. Authentication of such RAS users is possible through the RADIUS server only (for more detailed information consult paragraph 7.2.6 of [1] .

p.50 of 218

8.5 CONFIGURATION CASE 5: CONNECTING A SOFTPHONE

Fig. 6 Working with a softphone

You can configure the MVTS to interoperate with a softphone. We will explain how to do this using an MS NetMeeting for example, as the majority of customers prefer to use MS NetMeeting for evaluation of the MVTS free demo.

To configure NetMeeting for interworking with the MVTS server, proceed as explained below:

In the NetMeeting menu bar

1) Select Tools->Options->Advanced Calling and select the checkbox Use a gatekeeper to place calls.

2) Choose Tools->Options->Advanced Calling and select the box Log on using my account name.

3) In the Account name edit field enter user_name|password of the users described in the MVTS user.cfg configuration file.

p.51 of 218

Fig. 7 NetMeeting configuration dialog box

To enable calls from an ATA 186 to NetMeeting, disable the Fax T.38 support for the NetMeeting user by entering datacap_deny=4096 in the user.cfg file.

Table 24 Configuring softphone and ATA registering users

meraproxy.cfg gateway.cfg dialpeer.cfg user.cfg gatekeepr.cfg

[DP_ATAuser_to_NMet] [NetMeeting_user]


user=NM1

gateway=ENDPOINTS password=NM1

number=78312444333

[DP_NMuser_to_ATA] datacap_deny=4096


gateway=ENDPOINTS [ATA_user]

user=first_user

password=pass1

number=70954444333

proxy_type=1

p.52 of 218

8.6 CONFIGURATION CASE 6: CONFIGURING MVTS FOR INTERACTION WITH GATEKEEPERS

Fig. 8 Configuring gatekeeper interoperation

In the above model, the client gatekeeper GK1 registers with the MVTS server, and therefore should be declared as a RAS user in the user.cfg file. At the same time the MVTS registers with the remote gatekeeper GK2 and from the standpoint of the GK2 gatekeeper poses a common registering endpoint (by virtue of this there can be an enormous population of gateways registered with the MVTS and hidden from the GK2 gatekeeper). GW1 is configured as the source gateway for calls forwarded to GW2.

Configuration records in the MVTS configuration files would look as shown in Table 25.

Table 25 Configuring MVTS – gatekeeper interoperation

p.53 of 218

meraproxy.cfg gateway.cfg dialpeer.cfg user.cfg gatekeepr.cfg

[GW1] [GK1_to_GK2] [GK1] [GK2]

address=aa.aa.aa.aa #destination - FRISCO user=testuser address=xx.xx.xx.xx

dst_pattern=415[0-9]{7}

password=kk98fcc5 port=1719

[TermGW_for_GK2] gateway= GWterm_for_GK2

type=1

gatekeeper=GK2 user=second_testuser

proxy_type=1 password=

capacity=60 security=2

terminal=0

keepalive=30

p.54 of 218

8.7 CONFIGURATION CASE 7: CONFIGURING THE PRIMARY AND STANDBY MVTS FOR FAILOVER-FAILBACK

8.7.1 GK-RAS USER SCHEME To implement the GK-RAS user failover scheme configure the primary MVTS server as a master gatekeeper and configure the standby server as a client that registers with the primary server (see Fig. 9).

Fig. 9 Primary MVTS and failover MVTS operating as a GK-RAS user

pair

Make sure that the configuration settings of the communicating gateways and registering endpoints on the failover server are an exact replica of those on the primary MVTS.

Refer to the table below for the settings that differentiate the configuration of the primary server from that of the failover MVTS.

Primary MVTS Failover MVTS

user.cfg meraproxy.cfg

[Backup_Server]

p.55 of 218

p.56 of 218

user=user_name [Administration]

8.7.2 SHARED IP FAILOVER-FAILBACK SCHEME

password=MyPass8 … … … … master_gatekeeper=Main_MERA … … … … … … … …

gatekeeper.cfg

[Main_MERA]

address=zzz.zzz.zzz.zzz //enter actual IP here

port=1719

type=1 user=user_name password=MyPass8

To implement the redundancy method involving common IPs for handling traffic use the configuration parameters of the section [Redundancy] of meraproxy.cfg on the primary and the standby server.

The table below provides a configuration example for the system where 192.168.132.115 is the IP of the primary MVTS,the IP address of the standby MVTS is 192.168.132.114, and 192.168.132.140 is a dedicated IP for production traffic.

Table 26 Configured [Redundancy] sections on the main and standby systems.

Primary MVTS file meraproxy.cfg Failover MVTS file meraproxy.cfg

[Redundancy] [Redundancy] redundancy_type=2 redundancy_type=2 check_period=10 check_period=10 max_failed_retries=3 max_failed_retries=3 connect_timeout=3 connect_timeout=3 master_address=192.168.132.115 master_address=192.168.132.115 slave_address=192.168.132.114 slave_address = 192.168.132.114 check_address=192.168.132.140|192.168.132.114|/sbin/ifconfig eth0:0 inet 192.168.132.140 up|/sbin/ifconfig eth0:0 down;

check_address=192.168.132.140|192.168.132.115|/sbin/ifconfig eth0:0 inet 192.168.132.140 up|/sbin/ifconfig eth0:0 down;

For full information on system redundancy and trust relationship between the redundancy pair please see [1].

p.57 of 218

8.8 CONFIGURATION CASE 8: CONFIGURING THE SYSTEM OPERATING WITH THE SIP-HIT CONVERTER

8.8.1 SIP–HIT DEPLOYMENT The SIP-HIT converter can be deployed on a separate platform or co-installed on the same server with the MVTS. Installation on a separate computer is preferable as operation of the SIP-HIT h.323/sip converter involves codec conversion, a very resource-intensive process in terms of the system computing power.

For example, running the SIP-HIT co-installed on the MVTS-300 server will bring down the maximum capacity of the MVTS session controller from 300 to 120 concurrent calls.

To make the MVTS interoperable with the SIP-HIT converter, add the following record in the [H323] section of the meraproxy.cfg file

[H323]

… … …

… … … converter=converter_name/converter_ip_address/port/mode/type

… … …

where:

converter_name is the internal name of SIP-HIT

converter_ip_address is the IP address of the SIP-HIT module

port is a port number

mode denotes the converter’s operating mode (similar to MVTS’s gateway_mode parameter)

type specifies the protocol supported by the addressed endpoint (1 – H323; 2 – SIP)

Several converter records in a list are delimited by a semicolon, for example:

[H323]

… … …

… … …

converter=SIPconv/198.98.12.50/1720/3/2;H323conv/198.98.12.12/1720/3/1

… … …

To ensure SIP-HIT – MVTS binding enter the MVTS’s IP in the gateway= parameter (section [NETWORK]) of the converter’s configuration file configure.cfg.

See Table 27 for an example how you can configure the MVTS and SIP-HIT installed on different platforms for joint operation.

p.58 of 218

Fig. 10 Configuring the MVTS and the SIP-HIT converter installed on different servers

Table 27 MVTS and SIP-HIT configuration files (two-server deployment)

MVTS config files SIP-HIT config file

meraproxy.cfg gateway.cfg config.cfg

[SIPgw_in_NY] [MAIN]

[H323] address=123.45.58.55 daemon=1

... ... ... ... converter=SIPconv pidfile=/var/run/convert.pid

converter= SIPconv/193.98.17.70/1720/3/2; H323conv/193.98.17.70/1720/3/1

port=5060 phoenix=1

… … … … [H323gw_in_NY] facility=local5

address=123.32.23.77 [NETWORK]

converter=H323conv gateway=193.98.17.122

port=1720 local=193.98.17.70

natmode=2

[MEDIA]

codecs= G729 G729A G723 G711U FAX DTMF

[TRACE]

file=/usr/local/logs/SIPHIT_log

level=2

[H323]

H245Tunneling=1

FastStart=yes

MultiFastStart=false

port=1720

p.59 of 218

8.8.2 CONFIGURING THE SYSTEM FOR OPERATION WITH SIP-HIT CO-INSTALLED ON THE MVTS SERVER

Please remember that you can run the SIP-HIT co-installed on the MVTS server only at the cost of a dramatically reduced MVTS’s capacity. We recommend that you use the shared-server solution only if the maximum throughput of your MVTS system is much in excess of your actual operation needs.

Fig. 11 Configuring the MVTS and SIP-HIT converter to operate co-installed on a single server

Note: Configuring the MVTS make sure the SIP-HIT converter is assigned a port other than the default MVTS port 1720.

In view of the above note while considering the configuration example below pay special attention to the port value set in the converter= parameter of section [H323] of the meraproxy.cfg global configuration file.

p.60 of 218

Table 28 Configuration files of the MVTS session controller and SIP-HIT converter

MVTS config files SIP-HIT config file

meraproxy.cfg gateway.cfg config.cfg

[MAIN]

[H323] [SIPgw_in_NY] daemon=1

... ... ... ... address=123.45.58.55 pidfile=/var/run/convert.pid

converter= H323/193.98.17.122/1748/3/1; SIPconv/193.98.17.122/1748/3/2

converter=SIPconv phoenix=1

port=5060 facility=local5

[H323gw_in_NY] [NETWORK]

address=123.32.23.77 gateway=193.98.17.122

converter=H323conv natmode=2

port=5060

[MEDIA]

codecs= G729 G729A G723 G711U FAX DTMF

[TRACE]

file=/usr/local/logs/SIPHIT_log

level=2

[H323]

H245Tunneling=1

FastStart=yes

MultiFastStart=false

port=1748

p.61 of 218

8.9 MINIMUM DOWNTIME TRANSITION FROM SINGLE-SERVER TO MVTS-BASED CLUSTER SOLUTION

To ensure a smooth single-server-to-cluster transition with the minimum downtime of the system it is advisable to proceed as follows:

1. Deploy and configure you new cluster facility

2. Add the MVTS-based cluster as a gateway and dialpeer to your single-server configuration

3. Make a routing rule to divert part of the traffic to the cluster facility and see how the new installation operates

4. When positive that the cluster is ready to fully take over remove the single-server facility from service by deactivating the networking IP address on the single-server MVTS and getting it up on the MVTS cluster.

For that purpose get down the traffic IP on the old MVTS server by typing at the command prompt:

># ifconfig eth0 down

get up the IP address on the cluster MVTS server by typing at the command prompt:

># ifconfig eth0 inet xxx.xxx.xxx.xxx netmask yyy.yyy.yyy.yyy

># ifconfig eth0 up

p.62 of 218

MVTS Configuration Parameters

Page 63 of 218

APPENDIX 1: CONFIGURATION PARAMETERS ALPHABETIZED

A Parameter acct_address= meraproxy.cfg, section [Radius],

[BackupRadius]

Data type IP address

Valid values IP address in the oct.oct.oct.oct notation

Default value

Example acct_address=195.88.97.20

Explanation: Use this parameter to specify the IP address of the accounting RADIUS server.

Parameter acct_backup= meraproxy.cfg, section [Radius], [BackupRadius]

Data type Boolean

Valid values 0 – disables copying

1 – enables copying

acct_backup=<number>

Default value 0

Example acct_backup=0

Explanation Use the parameter to enable/disable copying of the accounting packets to the back-up Radius server provided it is specified in the section [Backup Radius] of meraproxy.cfg


Page 64 of 218

Parameter acct_boot_msg= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 – disables request sending

1 – enable request sending

Default value 1

Example acct_boot_msg=0

Explanation Set/reset the flag that controls sending the ««AAccccoouunnttiinngg RReeqquueesstt –– AAccccttSSttaattuussTTyyppee –– AAccccoouunnttiinngg--oonn»» requests

Parameter acct_enable= meraproxy.cfg, section [Radius], [BackupRadius]; user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – RADIUS accounting disabled

1 – RADIUS accounting enabled

acct_enable=<number>

Default value 1

Example acct_enable=1

Explanation This parameter serves to enable/disable global RADIUS accounting (in the sections [Radius] and [Backup Radius] of meraproxy.cfg and RADIUS accounting for an individual gateway (RAS user) in gateway.cfg and user.cfg. The RADIUS accounting setting in user.cfg and gateway.cfg may differ from the system global settings.

Parameter acct_interim_update= meraproxy.cfg, section [Radius]

Data type Integer

Valid values

Default value 0

Example acct_interim_update=0

Explanation Set a time interval for periodic update account messages to the RADIUS server sent between the start accounting and stop accounting messages. All positive integers below 10 result in the minimum10 seconds interval.


Page 65 of 218

Parameter acct_leg_type= meraproxy.cfg, section [Radius]

Data type Integer

Valid values 1 – use the start/stop records pertaining to the answer telephony leg,

2 – use the start/stop records pertaining to the originate VoIP leg,

3 – use both 1 and 2

4 – changes the following fields of the accounting packets sent to RADIUS:

For the incoming leg:

h323-call-origin=answer

h323-call-type=VoIP

h323-remote-address=IP address of the origination gateway

h323-remote-id=origination gateway ID

h323-gw-id=termination gateway ID

h323-setup-time= the time when Setup was received from the gateway-originator

For the outgoing leg:

h323-call-origin=originate

h323-call-type=VoIP

h323-remote-address=IP address of the termination gateway or gatekeeper

h323-remote-id= ID of the termination gateway or gatekeeper

h323-gw-id= ID of the origination gateway

h323-setup-time= the time the SETUP message was sent to the termination gateway

5 – in comparison to 4 makes the MVTS send only one set of accounting packets for the ‘answer telephony’ leg. For example, if a call has been rerouted three times, the packets to RADIUS will be dispatched in the following order:

start answer leg record start originate leg record 1 stop originate leg record 1 start originate leg record 2 stop originate leg record 2


Page 66 of 218

Parameter acct_leg_type= meraproxy.cfg, section [Radius]

start originate leg record 3 stop originate leg record 3 stop answer leg record

Default value 2

Example acct_leg_type=3

Explanation Use this parameter to specify the type of emulated RADIUS accounting records.

Parameter acct_port= meraproxy.cfg, section [Radius], [BackupRadius]

Data type Integer

Valid values Port number

Default value 1813

Example acct_port=1813

Explanation Use this parameter to specify a port for RADIUS accounting. Leave the default value 1813 unchanged if you have no port conflicts.

Parameter acct_stop_only= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 – disable sending stop accounting messages to the RADIUS server

1 – enable sending stop accounting messages to the RADIUS server

Default value 0

Example acct_stop_only=1

Explanation Use this parameter to make the MVTS send stop accounting messages only to the RADIUS server.


Page 67 of 218

Parameter acct_type= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 – means old CISCO format (overloaded attribute 44)

1 – stands for the CISCO VSA compatible format

Default value 0

Example acct_type=1

Explanation Use this parameter to define the preferred type of accounting format.

Parameter active_time= dialpeer.cfg

Data type Character string

Valid values The “business hours” of the dialpeer in the following format: <WD>/HH:MM-<wd>/<hh:mm> <WD> is the starting weekday of the uptime period, where: 1 – Monday, 2 – Tuesday, …. …., 7 – Sunday <wd> is the ending weekday of the uptime period, where 1 – Monday, 2 – Tuesday, …. …., 7 – Sunday. <HH:MM> denotes the start of the operation time, <hh:mm> is the end of the operation period.

Default value

Example active_time=1/08:00-3/20:00; 5/8:00-7/20:00

Explanation Use this parameter to specify uptime or “business hours” for the dial peer. The setting affects call routing decision made by the system. Use ‘;’ or ‘,’ to divide the parameter values.


Page 68 of 218

Parameter address= gateway.cfg; gatekeeper.cfg

Data type Character string or IP address in common dot-separated format

Valid values IP address address=<address>

Default value

Example address= 196.88.57.12

address=computer.mera.ru address=196.88.57.12/18

Explanation Use this parameter to specify the gateway/gatekeeper’s IP address or DNS-name. It is a mandatory field. With inbound connections, when this field contains a list of IP-addresses the value of the parameter mask= will apply to all IP addresses on the list. Note: The parameter address= in the file gateway.cfg allows you to configure addresses of origination gateways in the CIDR notation, i.e. xxx.xxx.xxx.xxx/n where xxx.xxx.xxx.xxx is the IP address in the common dot-separated format and n represents the number of significant bits used for the network identification. For example, the address value 196.88.57.12/18 means that 18 bits of total 32 represent the network and the remaining 14 are used to identify hosts.

Parameter address= meraproxy.cfg, section [Media]


Valid values IP address in the common oct.oct.oct.oct format

address=<address>

Default value

Example address= 196.88.57.12

Explanation This field, present in configuration of the signaling MVTS is used to specify the IP address of the dependent Media MVTS.

Parameter admin_gid= meraproxy.cfg, section [Console]

Data type Integer

Valid values Three-digit integers admin_gid=<number>

Default value 0

Example admin_gid=101

Explanation Use this parameter to specify the identifier of the group of users belonging to the server Administration group.


Page 69 of 218

Parameter alert_prog_ind_orig= gateway.cfg, user.cfg

Data type Integer

Valid values

0, 1, 2, 3, 4, 5 or 8 alert_prog_ind_orig=<number>

Default value

0 – disables the feature

Example alert_prog_ind_orig=5

Explanation

Use this parameter to set the ProgressIndicator value of Alert and Progress messages in the packets that the call terminator sends the call originator. The MVTS will insert a missing ProgressIndicator field with the set value if it is not present in the packets delivered by the call terminator.

Parameter alert_prog_ind_term= gateway.cfg, user.cfg

Data type Integer

Valid values 0, 1, 2, 3, 4, 5 or 8

Default value 0 (disables the functionality)

Example alert_prog_ind_term=4

Explanation

Use this parameter to set the ProgressIndicator value of Alert and Progress messages in call terminator-bound packets. If the ProgressIndicator field is missing in the packets that the originator sends the terminator, the MVTS will insert the missing field with the configured value prior to forwarding the messages to the call terminator. The MVTS leaves the value unchanged if it is there.

Parameter alias_route_path= meraproxy.cfg, section [Proxy]


Valid values

oct.oct.oct.oct/ oct.oct.oct.oct/oct.oct.oct.oct alias_route_path=<network address>/<network mask>/<IP address>

Default value

Example alias_route_path=205.10.204.160/255.255.255.254/205.10.204.175

Explanation Use this parameter to specify an alternate routing instruction with the OS kernel routing table reading disabled.


Page 70 of 218

Parameter alias_route_path_file= meraproxy.cfg, section [Proxy]


Valid values

Filepath alias_route_path_file=

<string>

Default value

none

Example

Explanation The parameter specifies the name of and the path to the file with routing alternatives listed in the following format: <network address>/<network mask>/<local address>. Each entry in the list of the routing alternatives should occupy a separate line (never delimit the list elements in the file by semicolons like in the parameter alias_route_path=).

Parameter alternate_gatekeeper= meraproxy.cfg, section [Redundancy]


Valid values

Valid gatekeeper names from the gatekeeper.cfg configuration file of the failover MVTS host, delimited by a semicolon

alternate_gatekeeper=

<name;name>

Default value

Example alternate_gatekeeper=

Explanation Use this field to specify a GK name or names that the MVTS backup server includes in the GRJ (Gatekeeper Reject) response sent to a remote host as a list of GK options.

If a remote host by mistake tries to register to the MVTS failover server running in the standby mode, the value of this configuration parameter will be included in the GatekeeperReject (GRJ) message that the MVTS backup server sends the registering entity. In fact, the GRJ with the list of gatekeeper options is intended to make the remote host send RRQ or GRQ to the MVTS primary server.


Page 71 of 218

Parameter alternate_port= meraproxy.cfg, section [H323]

Data type Integer

Valid values Port number alternate_port= <number>

Default value 0

Example a l t e r n a t e _ p o r t = 1770

Explanation Use this parameter to specify another (alternative) signaling port.

Parameter allowed_prefix= gateway.cfg, user.cfg

Data type A string of characters

Valid values A string of characters representing a list of allowed prefixes

allowed_prefix=<string>

Default value Empty string

Example

Explanation Use the parameter to enter a list of destination number prefixes that the MVTS will accept from the origination gateway/RAS user. Use “;” to delimit the list elements. If the gateway originates a call with a destination number prefix other than specified in the parameter allowed_prefix= , the call will be rejected with LDC 129 (NotAllowedPrefix). You can use both plain text strings and regular expressions to list allowed number prefixes.


Page 72 of 218

Parameter always_accessible= gateway.cfg, user.cfg

Data type Boolean

Valid values

0 allows blocking the gateway failing call termination attempts with LDC 101 or 112 1 disallows blocking the gateway failing call termination attempts with LDC 101 or 112

always_accessible=<number>

Default value

0

Example always_accessible=1

Explanation Normally the MVTS for 30-40 seconds excludes the gateway that fails to complete a call returning LDC 101 or LDC 112 from the pool of available call termination endpoints.

This parameter allows you to control how the MVTS responds to failed call attempts accompanied by LDC 101 and 112 cause codes (“Failure to initiate an H.225 session with the call terminator within 3 seconds time” and “Failure to set up an H.225 session with the call terminator” respectively). With the setting always_accessible=1 the MVTS ignores LDC 101, LDC 112 call termination codes and the gateway remains among available routing options.

Parameter ani_allow= user.cfg; gateway.cfg


Valid values A regular expression defining the mask for phone numbers. If the parameter value is a list delimit the list elements with ;

ani_allow=<number mask>

Default value

Example a n i _ a l l o w = 7 8 3 1 2 [ 0 -9 ]* ;7812 [0 -9 ]*

Explanation Use this parameter to specify a list of authorized ANI-numbers for the gateway being configured. This means that a call arriving from the calling gateway will be admitted by the MVTS if its ANI number complies with the number mask set in the ani_allow= field. Ignore this field if any ANI-number is allowed. The check is performed against the call-source number presented by the gateway, without any prior translation of the ani_allow= value.


Page 73 of 218

Parameter asr_alert_email= meraproxy.cfg, section [Statistics]


Valid values

An e-mail address asr_alert_email=<string>

Default value

Example [email protected]

Explanation Use this parameter to specify an e-mail address for ASR deterioration alerts to the Administrator.

Parameter asr_mail_period= meraproxy.cfg, section [Statistics]


Valid values

A time interval in the [[HH:]MM:]SS format asr_mail_period= [[HH:]MM:]SS

Default value

asr_mail_period= [[00:]15:]00

Example asr_mail_period= [[01:]15:]20

Explanation Use the parameter to set a time interval for periodic email notifications caused by min_asr=, min_acd=, min_scd=, max_scd= threshold violations

Parameter auth_address= meraproxy.cfg, section [Radius]



auth_address=oct.oct.oct.oct

Default value

Example auth_address=195.88.97.20

Explanation Use this parameter to specify the IP address of the authorization RADIUS server.


Page 74 of 218

Parameter auth_enable= meraproxy.cfg, sections [Radius] and [BackupRadius], user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – disables authentication through RADIUS

1 – enables authentication through RADIUS

auth_enable=<number>

Default value 0

Example auth_enable=0

Explanation

Use this parameter to enables/disable authentication through RADIUS. In the user.cfg and gateway.cfg configuration files the parameter serves to enable/disable RADIUS authorization of a given gateway.

Final RADIUS authorization setting for the given RAS-user results from multiplication of this setting by the similar setting in the section [Radius ] of the system configuration file meraproxy.cfg. The field is mandatory.

Parameter auth_password_type= meraproxy.cfg, section [Radius]

Data type Integer

Valid values 0 - for MD5 hash password (RFC 2138).

1 - for passwords in plain ASCII format (for compatibility with MindCti)

auth_password_type=<number>

Default value 0

Example auth_password_type=1

Explanation Use this parameter to specify the password type.


Page 75 of 218

Parameter auth_port= meraproxy.cfg, section [Radius], [BackupRadius]

Data type Integer

Valid values A positive integer auth_port=<number>

Default value 1812

Example auth_port=1819

Explanation Use this parameter to specify a port for RADIUS authentication.


Page 76 of 218

B

Parameter bearer_capability= user.cfg, gateway.cfg

Data type Integer

Valid values 0 – the value of the field ‘bearer capability’, received from the call originator is not changed;

1 (default) – substitute value 0x8090a3 into the field ‘bearer capability’;

>1 – all the values greater than 1 will be inserted into the field just as they appear in the parameter bearer_capability=

The values shall be entered in the hexadecimal notation.

bearer_capability=<number>

Default value 1

Example bearer_capability=0

Explanation The parameter serves to control the value of the field ‘bearer capability’ in the headers of Q931 messages.

The value set in the configuration of a termination gateway/RAS user prevails over that in the configuration of an origination endpoint.

Example:

- if the configuration of a terminatoin gateway/RAS user includes the parameter bearer_capability=>1 the MVTS will insert the value of this parameter into Q931 messages regardless of the value of the bearer_capability= in the configuration of the originator

- if the configuration of a termination gateway/RAS user includes the parameter bearer_capability=1, while the configuration of the originating endpoint includes the parameter bearer_capability>1, the MVTS will substitude the originator’s value into the Q931 message

- if the configuration of a termination gateway/RAS user includes the parameter bearer_capability=1, while the configuration of the originating endpoint has bearer_capability=0 or bearer_capability=1, the MVTS will insert the default value (0x8090a3) into the Q931 message.

- if the configuration of a termination gateway/RAS user includes bearer_capability=0, the MVTS will proxy q931 messages without changing the bearer capability field, and the termination party will receive them exactly the way they were delivered by the message originator.


Page 77 of 218

Parameter bil_file_attr= meraproxy.cfg, section [Billing]

Data type Integer

Valid values A three-digit decimal number

bil_file_attr=<number>

Default value 0600

Example bil_file_attr=664

Explanation Use this field to set file attributes for the final file with billing data. The permissions (read, write and execute) are identical to those found in all UNIX-like operating systems. Each digit of the three-digit number is a value ranging from 0 to 7 (i.e. from 000 to 111 in binary notation). The first digit pertains to the access permissions of the file owner, the second represents access permissions of the file owner group, and the third one specifies the access permissions of all other users. The access permission is granted when the appropriate bit is set (i.e. equals 1).

Note: Number 664 (110 110 100 in binary notation) specifies:

• For the file owner: 110 – 1 permission to read the file; 1 permission to write to the file; 0 – file execution not permitted.

• For users of the file owner group: 110 – 1 permission to read the file; 1 permission to write to the file; 0 – file execution not permitted

• For other users of the system: 100 – 1 permission to read the file; 0 – writing to the file is not permitted; 0 – file execution is not permitted.

Note: Regardless of the access permission settings in the main configuration file, the file owner can at all times read and write to the temporary and final files.


Page 78 of 218

Parameter bil_tmpfile_attr= meraproxy.cfg, section [Billing]

Data type Integer

Valid values A three-digit decimal number bil_tmpfile_attr=<number>

Default value 0600

Example bil_tmpfile_attr=664

Explanation Use this field to set access permissions for the accounting system temporary file. The permissions (read, write and execute) are identical to those found in all UNIX-like operating systems. Each digit of the three-digit number is a value ranging from 0 to 7 (i.e. from 000 to 111 in binary notation). The first digit pertains to the access permissions of the file owner, the second represents access permissions of the file owner group, and the third one specifies the access permissions of all other users. The access permission is granted when the appropriate bit is set (i.e. equals 1).







Page 79 of 218

Parameter bill_translate= dialpeer.cfg


Valid values

Regular expressions in the regexp format bill_translate = regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&] dst_translate= regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&]

Default value

Empty string

Example [DIALPEER_TEST]

dst_pattern=[0-9]*

src_pattern=[0-9]*

dst_translate=..../1234#8812788&

bill_translate=..../7812788&

dialed number – 3264

result:

dst_number=1234#88127883264bill_number=7127883264

Explanation This field sets the number translation patterns for accounting purposes. The accounting system often requires that phone numbers appear in a readily readable form, for example, E.164 format. In the beginning of the dial peer search the bill_number= value is identical to the dst_number= value, though when the search is under way the accounting-oriented number translation is done in compliance with the pattern defined in the field bill_translate= rather than the pattern set by dst_translate=.

As a result, the number may be furnished in any form convenient for accounting.

Translation syntax is the same as in dst_translate=

Note: bill_translate is no longer used in MVTS configuration. It has been replaced by dst_bill_translate= and src_bill_translate= and is now present in configuration file dialpeer.cfg as a means to ensure compatibility with older versions of the MVTS application.

Parameter billing_gid= meraproxy.cfg, section [Console]

Data type Integer

Valid values A positive integer billing_gid=<number>

Default value 0

Example billing_gid=101

Explanation Use this field to specify the identifier for the MVTS Billing user group.


Page 80 of 218

C Parameter call_connect_delay= user.cfg, gateway.cfg

Data type Integer

Valid values Positive integers representing the delay time in milliseconds

call_connect_delay=<number>

Default value 0 – disable delay

Example call_connect_delay=500

Explanation Define a delay time that will precede sending Connect to the call originator.

Note: the parameter is valid only in configuration of termination endpoints (gateways and RAS users) and dialpeers.

Parameter call_connect_delay= dialpeer.cfg

Data type Integer

Valid values Positive integers representing the delay time in milliseconds

call_connect_delay=<number>

Default value 0 – disable delay

Example call_connect_delay=500

Explanation Define a delay time (for the dialpeer) for CONNECT sent to the call originator.

Note: the parameter is valid only in configuration of termination endpoints (gateways and RAS users) and dialpeers.

Parameter call_limit= meraproxy.cfg, section [Administion]

Data type Integer

Valid values Positive numbers call_limit=<number>

Default value

Example call_limit=10

Explanation This is a configuration parameter of Media MVTS, which is a part of the MVTS cluster system. Use the parameter to define the maximum quota of simiutaneous calls for an MMVTS.


Page 81 of 218

Parameter call_radix= meraproxy.cfg, section [Statistics], section [Media]

Data type Integer

Valid values 0 and integers in the 10 – 5000 range

call_radix=<number>

Default value 5000

Example call_radix=500

Explanation Use this parameter to specify a number of calls to be used for calculation of the average ASR, SCD, ACD values of the objects of statistics of the MVTS (section [Statistics]) or the MVTS-based cluster (section [Media]).

If call_radix= 0, the ASR, ACD and SCD estimates for the object are done for all the calls that the object handled since the latest restart of the MVTS.

Note: in case when the amount of calls that the object handled is less than the call_radix= setting, ASR, ACD and SCD estimates are done taking into account all calls actually handled by the object.

Parameter call_rate_period= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values 10 – 3600 call_rate_period=<number>

Default value 60

Example call_rate_period=60

Explanation The parameter serves to define a time interval (in seconds) for calculation of the average traffic growth rate value (for individual gateways/RAS users and globally).

Parameter call_sampling_number= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values

A positive integer ranging from 1 to the value specified in the call_radix= field.

call_sampling_number=<number>

Default value

500

Example call_sampling_number=70

Explanation Specify the number attempted calls to be used in the serviceability assessment of suspended routes.


Page 82 of 218

Parameter call_threads= meraproxy.cfg, section [Administration]

Data type Integer

Valid values A positive integer that stands for the number of threads

call_threads=<integer>

Default value 3

Example call_threads=2

Explanation This field defines threads allocation for signaling traffic. The recommended value is 3. It is advisable you use call_threads=3 in combination with rtp_threads=5 .

Parameter capacity= user.cfg; gateway.cfg

Data type Integer

Valid values Positive numbers capacity=<number>

Default value 65535

Example capacity=30

Explanation Use this parameter to specify the maximum number of concurrent calls that the MVTS can route through the gateway (RAS user).

Parameter capacity= dialpeer.cfg

Data type Integer

Valid values A positive integer in the decimal notation in the 0 – 65535 range

capacity=<number>

Default value 65535

Example capacity=200

Explanation Use this parameter to specify the maximum number of concurrent calls that the MVTS can route through the given dial peer.


Page 83 of 218

Parameter cdr_format= meraproxy.cfg, section [Billing]

Data type Format

Valid values 0 – MVTS intrinsic format 1 – MIND CTI format 2 – MVTS format unabridged without field names (fit for insertion in a spreadsheet) 3 – MVTS format with time stamps expressed as the number of seconds lapsed since 01.01.1970

cdr_format=<number>

Default value 0

Example cdr_format=1

Explanation Use this field to set the format of the billing data written to files (CDRs).

Parameter challenge_no= meraproxy.cfg, section [Redundancy]

Data type Integer

Valid values Positive integers from 1 up representing the number of unanswered RAS queries

challenge_no=<number>

Default value 1

Example challenge_no=3

Explanation Use the parameter in the configuration of the standby MVTS to define the number of unanswered RAS queries from the standby server to the primary MVTS that will cause the failover server to take over from the primary machine.


Page 84 of 218

Parameter check_address= meraproxy.cfg, section [Redundancy]


Valid values

Default value

Example check_address=64.1.45.1:1720|64.1.45.2|ifconfig eth0:0 inet 64.1.45.1 up|ifconfig eth0:0 down

Explanation Use the field to enter the parameters describing the system IP addresses for ingress traffic.

This field has the following format:

testIP:port|localIP|up command|down command,

where

‘testIP:port’ is an incoming traffic IP address and port tested by the TCP connect attempts.

‘localIP’ is the local address of the failover server. Serves to establish a TCP connect with the specified incoming traffic IP address of the main MVTS host.

‘up command’ is a command used to get up the IP address for incoming traffic on the network interface.

‘down command’ is the command used to get down the incoming traffic IP adderss on a network interface.

You can use several incoming addresses in the check_address= field using a semicolon (“;”) to delimit them.


Page 85 of 218

Parameter check_h225_version= gateway.cfg, user.cfg

Data type Boolean

Valid values

0 – disables H225 version check

1 – enables H225 version check

check_h225_version=<number>

Default value

1

Example check_h225_version=0

Explanation Use the parameter to enable or disable H225 signaling protocol version checking for termination gateways and RAS endpoints.

If the check_h225_version= flag is set for the termination gateway/RAS user (check enabled), and the version used by the origination gateway is 3 and earlier, the MVTS will remove the presentationIndicator and/or screeningIndicator from SETUP before passing it to the termination gateway.

If the check_h225_version= flag of the termination gateway is reset (check disabled), the MVTS leaves the presentationIndicator and/or screeningIndicator fields included in SETUP sent to the termination gateway.

Note: the parameter was introduced to ensure compatibility of gateways that operate under different versions of the H.225 protocol. Some gateways may incorrectly interpret the presentationIndicator and screeningIndicator fields in SETUP with H.225 protocol versions earlier than 4.

Parameter check_period= meraproxy.cfg, section [Redundancy]

Data type Integer

Valid values Positive numbers representing time in seconds

check_period=<number>

Default value 10

Example check_period=15

Explanation Use the parameter to define a time interval (in seconds) between successive TCP connects from the failover to the primary system.


Page 86 of 218

Parameter check_rtcp_address= gateway.cfg, user.cfg

Data type Boolean

Valid values 0, 1

0 – RTCP address verification disabled

1 – RTCP address verification enabled

Default value 0

Example check_rtcp_address=1

Explanation This parameter allows you to enable verification of RTCP addresses received from endpoints in Faststarts.

Parameter check_rtp_source= gateway.cfg, user.cfg

Data type Boolean

Valid values 0, 1

0 – the function is disabled

1 – the function is enabled

check_rtp_source=<number>

Default value 0

Example check_rtp_source=1

Explanation With this parameter enabled MVTS checks IP addresses of media sources.

This feature is instrumental when the following problem with media proxying occurs:

RTP traffic arrives at media ports of MVTS from an unknown IP address (i.e. this IP address has not yet been received within the H.245 session). If later the source of RTP traffic changes and within the H.245 session it sends actual IP addresses of its logical media channels, MVTS will be able to update IP addresses of media channels and proxy traffic to received IP addresses.


Page 87 of 218

Parameter check_src_number= user.cfg

Data type Boolean

Valid values 0 disables the function

1 enables the function

check_src_number=<number>

Default value 0

Example check_src_number=1

Explanation

With check_src_number=1, the feature functions in the following way. In case of RADIUS registration if the received RRQ contains a calling number which neither matches that specified in the field number= nor that available from the field xpgk-ep-number, the RRQ will be rejected with the reason invalidAliases. Further, if registration is successful, SETUPs from such a RAS user will be accepted only with CallingPartyNumbers matching those available in the RRQ or similar to those defined in the parameter ani_allow=, otherwise the call will be terminated with the cause SourceGatewayAniReject (205).


Page 88 of 218

Parameter codec_allow= user.cfg, gateway.cfg, dialpeer.cfg


Valid values Codec mnemonics:

g711A64k

g711A56k

g711U64k

g711U56k

g722_64k

g722_56k

g722_48k

g7231

g728

g729

g729A

is11172

is13818

g729B

g729AwB

g7231C

gsmFR

gsmHR

gsmEFR

NS:<irregular codec>

codec_allow=<codec1>;<codec2>;<codec3>

Default value Empty set

Example codec_allow=g729;g7231;g711U56k

Explanation Use this parameter to specify a list of codecs supported by the gateway. The list entries must be delimited with a semicolon or a comma. The list elements are case sensitive.

Note: The default value implies that all codecs are supported except those listed in the codec_deny= field.


Page 89 of 218

Parameter codec_deny= user.cfg, gateway.cfg, dialpeer.cfg


Valid values Codec mnemonics (see the list above)

codec_deny=<codec1>;<codec 2>;<codec3>

Default value Empty set

Example codec_deny=g729; g7231; g711U56k

Explanation Use this parameter to specify the list of codecs that are not supported or misinterpreted by the gateway. The list entries must be delimited by a semicolon or a comma. Spaces are ignored. The list entries are case sensitive.

Parameter community= meraproxy.cfg, section [SNMP]


Valid values Arbitrary string of characters

community=<string>

Default value public

Example community=transCity

Explanation Use this parameter to specify a community name for access environment. This community name is included in the SNMP queries. The devices that are “not aware” of the community name are precluded from SNMP operations.


Page 90 of 218

Parameter compatibility= user.cfg, gateway.cfg

Data type Integer

Valid values Unsigned integers in the hexadecimal notation representing the gateway capability bit pattern

compatibility=<number>

Default value 0xFFFFFFFF

Example Example 1: [originator_GW]

… … …

compatibility=0x0105 (G711 A-law, G729, T120)

… … … …

[terminating_GW]

… … …

compatibility=0x30C (G723, G729, T120, T38)

… … … …

0x0105 AND 0x30C=0x0104

The non-zero result of ANDing means that the termination GW has passed the compatibility check and the route may be selected for call termination Example 2: [originator_GW]

… … …

compatibility=0x0105 (G711 A-law, G729, T120)

… … … …

[terminating_GW]

… … …

compatibility=0x208 (G711 A-law, T38)

… … … …


Page 91 of 218

Parameter compatibility= user.cfg, gateway.cfg

0x0105 AND 0x208=0x0000

The zero result of the conjunction operation means that the gateway compatibility check failed and the route will not be selected for the call termination.

Explanation Use this parameter to specify a 4-byte mask of the gateway capabilities for compatibility check. Byte-oriented comparison of the mask allows selection of a termination gateway and therefore a route. The 4-byte capability masks of an originating and a would-be termination gateway are subject to logical ANDing. A route is selected for call termination if logical ANDing of at least one pair of bytes yields a non-zero value. By setting a parameter value the system Administrator selects arbitrary bit designations for codecs, protocols (e.g. T120, T38), and other relevant gateway compatibility features.

For example, the Administrator may designate the following values in the least significant byte: 0х01 – G711 A-law, 0x02 – G711 U-law, 0x04 – G729, 0x08 – G723 and set the following bit pattern in the byte next to it:

0x01 – T120

0x02 – T38

0x40 – other protocol compatibility features

Parameter connect_timeout= meraproxy.cfg, section [Redundancy]

Data type Integer

Valid values Positive numbers representing time in seconds

connect_timeout=<number>

Default value 3

Example connect_timeout=5

Explanation Use the field to set a TCP-connect timeout (in seconds).

Parameter console_port= meraproxy.cfg, section [Console]

Data type Integer

Valid values A port number console_port=<number>

Default value

Example console_port=1750

Explanation

Specify other than the default port for the MVTS administration console.


Page 92 of 218

Parameter contact_info= meraproxy.cfg, section [SNMP]


Valid values Arbitrary string contact_info=< string>

Default value root@localhost

Example [email protected] +78213995875

Explanation Use this parameter to present contact information about the system owner or operator.

Parameter converter= meraproxy.cfg, section [H323]


Valid values

A string in the converter_name/converter_ip_address/port/mode/type format,

where

converter_name defines the converter’s internal name

converter_ip_address is the IP address of the converter module

port defines a port number

mode denotes the converter’s operating mode (similar to the gateway_mode= parameter)

type specifies the protocol supported by the addressed gateway (1 – H323; 2 – SIP)

converter=<string>;<string>

Default value

Empty string

Example converter= SIPconv/198.98.12.50/1720/3/2;

H323conv/198.98.12.12/1720/3/1

Explanation Use this field to specify the parameters of the H.323-SIP Interprotocol translator.


Page 93 of 218

Parameter converter= gateway.cfg, user.cfg


Valid values The name of the signaling protocol converter as configured in the section [H323] of the meraproxy.cfg configuration file

converter=<string>


Example converter=SIPconv

Explanation Specify the name of a SIP/H.323 converter in the record of a termination gateway or RAS user. It is possible to enter several converter names delimiting them with semicolons. Upon arrival of a call the least traffic-laden converter is selected.

Parameter cut_h323_id= gateway.cfg

Data type Boolean

Valid values 0 – disables field removal

1 – enables field removal

cut_h323_id=<number>

Default value 1

Example cut_h323_id=0

Explanation Normally, the MVTS removes the h323_id field from transmitted packets. The cut_h323_id= flag serves to disable this functionality. Use this parameter in description of origination gateways.

Note: the parameter is valid in configuration of origination gateways only.

Parameter cut_fast_connect_refused= gateway.cfg, user.cfg

Data type Boolean



Default value 0

Example cut_fast_connect_refused=0

Explanation

Disable/enable removal of the fastConnectRefused field from all signaling packets.


Page 94 of 218

Parameter cut_non_standard_data= gateway.cfg, user.cfg

Data type Boolean

Valid values

0 – disables field removal


cut_non_standard_data=<number>

Default value

1

Example cut_non_standard_data=0

Explanation Enable/disable removal of the field nonStandardData from Setup.

Parameter cut_symmetric_operation_required= gateway.cfg

Data type Boolean



Default value

1

Example cut_symmetric_operation_required=0

Explanation Normally, the MVTS session controller removes the symmetric_operation_required field from transmitted packets. The cut_symmetric_operation_required= flag serves to disable the field removal.

Note: the parameter is valid in configuration of the origination gateways only.


Page 95 of 218

Parameter cut_non_standard_control= gateway.cfg

Data type Boolean



Default value 1

Example cut_non_standard_control=0

Explanation Normally, the MVTS session controller removes the non_standard_control= field from transmitted packets. Use the cut_non_standard_control= flag to disable the field removal. Use this parameter in description of origination gateways.


Parameter cut_tunnelled_signaling_message= gateway.cfg

Data type Boolean



Default value

1

Example cut_tunnelled_signaling_message=0

Explanation By default the MVTS session controller removes the tunnelled_signaling_message= field from transmitted packets. Use the cut_tunnelled_signaling_message= flag to disable the field clipping.



Page 96 of 218

D Parameter datacap_deny= user.cfg; gateway.cfg

Data type Integer

Valid values An integer in decimal notation representing the binary value of the gateway data capability bit pattern.

datacap_deny=<number>

Default value 0

Example datacap_deny=4096

Explanation This parameter contains the list of data capabilities not supported by the gateway. Failure to define the list may result in failed call setup.

The field data structure is as follows:

enum DataCapability { e_nonStandard=1, e_t120=2, e_dsm_cc=4, e_userData=8, e_t84=16, e_t434=32, e_h224=64, e_nlpid=128, e_dsvdControl=256, e_h222DataPartitioning=512, e_t30fax=1024, e_t140=2048, e_t38fax=4096, e_genericDataCapability=8192 };

Exapmle: Suppose that t30fax and t38fax capabilities are not supported. In this case, the parameter datacap_deny should be set to 5120, as 1024 (t30fax) and 4096 (t38fax) form sum of 5120.


Page 97 of 218

Parameter debug_file_attr= meraproxy.cfg, section [Debug]

Data type Integer

Valid values A three-digit decimal number representing access permissions for the final file with billing data.

debug_file_attr=<number>

Default value 600

Example debug_file_attr=664

Explanation Use this field to set access permissions for the final debug log file. The file attributes (read, write and execute) are identical to those found in all UNIX-like operating systems. Each digit of the three-digit number is a value ranging from 0 to 7 (i.e. from 000 to 111 in binary notation). The first digit pertains to the access permissions of the file owner, the second represents access permissions of the file owner group, and the third one specifies the access permissions of all other users. The access permission is granted when the appropriate bit is set (i.e. equals 1).






Parameter debug_level= meraproxy.cfg, section [Gatekeeper], sections [Radius] and [BackupRadius]

Data type Integer

Valid values 0 - logging disabled

1 – minimum information detail level

3 – maximum information detail level

debug_level=<number>

Default value 0

Example debug_level=2

Explanation Set the information detail level of packet logging covering the MVTS gatekeeper, RADIUS and BackupRadius functionalities (sections [Gatekeeper], [Radius], [BackupRadius] respectively). The value of this parameter will be valid even if general logging in the section [Debug] of meraproxy.cfg is disabled. The greater is the parameter value the more detailed information is saved to the log file and the bigger the log is. Whenever possible, keep the system at its default logging level.


Page 98 of 218

Parameter debug_level= gateway.cfg, user.cfg

Data type Integer

Valid values 0 - packet logging disabled

1 – minimum log files detail level

3 – maximum log files detail level

debug_level=<number>

Default value 0

Example debug_level=3

Explanation Use this parameter to set an individual level of information details contained in logs for call sessions involving the gateway/RAS user.

For example, if the system general setting iof log writing is 0, (the parameter level= in the section [Debug] of meraproxy.cfg is set to 0), you can set the debug_level= parameter in the configuration of the gateway/RAS user to the desired value (e.g. 3) thus enabling log writing with the highest level of information details for call sessions involving the gateway/RAS user being configured.

Parameter debug_tmpfile_attr= meraproxy.cfg; section [Debug]

Data type Integer

Valid values

Three-digit decimal numbers representing access permissions for the temporary file with billing data.

debug_tmpfile_attr=<number>

Default value

600

Example debug_tmpfile_attr=664

Explanation Use this field to set the access permissions for the temporary debug file. The permissions (the read permission, write and execute permissions) are identical to those found in all UNIX-like operating systems. Each digit of the three-digit number is a value ranging from 0 to 7 (i.e. from 000 to 111 in binary notation). The first digit pertains to the access permissions of the file owner, the second represents access permissions of the file owner group, and the third one specifies the access permissions of all other users. The access permission is grante when the appropriate bit is set (i.e. equals 1).



• For users of the file owner group: 110 – 1 permission to read the file; 1 permission to write to the file; 0 – file execution not permitted.



Page 99 of 218

Parameter dialpeer= user.cfg


Valid values Arbitrary string dialpeer=<string>

Default value

Example dialpeer=TORONTO

Explanation Use this parameter to enter the internal name of the dialpeer (i.e. the name of an appropriate section in dialpeer.cfg). Upon registration of this RAS user with the MVTS gatekeeper, the RAS user is automatically added to the list of termination options of this dialpeer.

It allows the operator to assign a dialpeer(s) to each RAS user registered with the MVTS as is the case with the endpoints specified in the field gateway= of dialpeer.cfg.

This RAS user will be included into the dialpeer search together with the endpoints of the field gateway=of dialpeer.cfg.

Note that unregistration of the RAS user with the MVTS will cause its exclusion from the dialpeer call termination options.

Parameter dialpeer_cfg= meraproxy.cfg, section [Administration]


Valid values File name dialpeer_cfg=file_name

Default value dialpeer.cfg

Example dialpeer_cfg=my_dialpeer.cfg

Explanation Use this parameter to indicate the file with dial peer data. Specify the file path relative to the root directory or the configuration file merarpoxy.cfg.


Page 100 of 218

Parameter diff_orig_by_prefix= meraproxy.cfg, section [Administration]

Data type Boolean

Valid values

0 – the MVTS does not differentiate gateways with the same ID address or mask

1 – the MVTS differentiates gateways with the same ID address or mask

diff_orig_by_prefix=<1/0>

Default value

0

Example diff_orig_by_prefix=0

Explanation Use this field to enable/disable the MVTS to differentiate origination gateways with identical IP addresses (subnet mask) by destination number prefixes,

With the differentiation function enabled the MVTS distinguishes between origination gateways with identical IP addresses (or subnet mask) by the destination number prefixes specified in the fields allowed_prefix=/disallowed_prefix= in the description of this gateway.

Note: the parameter is meaningless unless the gateway configuration includes configured parameters allowed_prefix=/disallowed_prefix=.

Parameter direct_call_allowed= meraproxy.cfg, section [Administration]; gateway.cfg

Data type Boolean

Valid values

0 – disables the parameter

1 – enables the parameter

direct_call_allowed=<number>

Default value

0

Example direct_call_allowed=1

Explanation This parameter serves to configure the signaling MVTS in a two-layer MVTS cluster to directly receive incoming signaling by-passing the load balancer.

To enable load balancer by-passing, enable the direct_call_allowed= parameter in the file meraproxy.cfg, section [Administration], then set the same parameter to ‘1’ in the configuration file gateway.cfg in the sections of gateways allowed to send direct calls.


Page 101 of 218

Parameter non_direct_reply_network=

meraproxy.cfg, section [Gatekeeper]

Data type IP in dot-separated format

non_direct_reply_network=<string>

Valid values Network address in the CIDR notation


Example non_direct_reply_network=192.168.1.1/24

Explanation

Parameter

Use this field to enter a list of network IPs in the CIDR notation. For the networks included in the list responses to query RAS packets that the networks originate will be sent to the IP address specified in the rasAddress field of the query rather than to the address of the query origin.

disallowed_prefix= gateway.cfg, user.cfg

Data type A string of characters

Valid values A string of characters representing a list of allowed prefixes

allowed_prefix=<string>


Example

Explanation Use the parameter to enter a list of destination number prefixes that the MVTS will not accept from the origination gateway/RAS user. Use “;” to delimit the list elements. You can use both plain text and regular expressions to enter unacceptable number prefixes.

Parameter dont_make_cdr_for_ldc= gateway.cfg, user.cfg, meraproxy.cfg, section [H.323]


Valid values MVTS Local Disconect Codes

Default value

Example dont_make_cdr_for_ldc=132;131

Explanation Use the parameter to define a list of local disconnect codes that prevent the MVTS from writing CDRs for calls completing with the LDCs on the list. The global list configured in section [H.323] of meraproxy.cfg overrides similar lists defined in configurations of static-IP GWs (gateway.cfg) and registering endpoints (user.cfg).

Note: See also the description of the dont_send_stop_acct_for_ldc= parameter.

Note: This parameter’s value cannot exceed 2000.

http://www.internetworktraining.com/kbase/layer_3_routing/cidr_notation.html




Page 102 of 218

Parameter dont_send_stop_acct_for_ldc= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 enables sending the Accounting Stop packet to the RADIUS server

1 disables sending the Accounting Stop packet to the RADIUS server

Default value 0

Example dont_send_stop_acct_for_ldc=

Explanation The parameter serves to disable/enable sending the Accounting Stop packet to the RADIUS server for calls, the termination attempts of which end with one of the LDCs specified in the field dont_make_cdr_for_ldc=.

Disabling the dispatch of the Accounting Start packet to the RADIUS server is unreasonable, as at the time of the message dispatch, the LDC of the call termination attempt is not known.


Page 103 of 218

display_ie_translate= Parameter dialpeer.cfg


Valid values Search string in the regexp/string format display_ie_translate= regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&]


display_ie_translate= regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&] or

display_ie_translate= empty/[str][\1][str][\2][str][\3][str][&]

Example

Explanation Define translation patterns for the content of the ‘display’ information element (IE). The translation syntax is the same as in case of dst_translate=.

If the received SETUP does not contain the ‘display’ information element, and you need to insert it before the MVTS forwards SETUP to the termination gateway, use the keyword empty as in the example below:

Example:

display_ie_translate=empty/”MERA support”

Parameter

In this case the MVTS will forward the call terminator the SETUP message, which will contain IE ‘display’ with the value ”MERA support”.

dscp_byte= gateway.cfg, user.cfg

Data type Integer

Valid values 0 – 255 (in the hexadecimal notation) dscp_byte=<number>

Default value

Empty string (parameter is not used)

Example dscp_byte=ff

Explanation The parameter serves to define the value of the DSCP byte of a datagram sent to the gateway/RAS users, the configuration of which contains the set dscp_byte= parameter.

For instance, if the settings of a termination gateway (GW) include the configured parameter dscp_byte= , the value of the DSCP byte of all the RTP-packets intended for the gateway will be set in accordance with the value of the parameter.


Page 104 of 218

Parameter dscp_byte_media= meraproxy.cfg, section [Proxy]

Data type Integer

Valid values

0 – 255 (in the hexadecimal notation) dscp_byte_media=<number>

Default value

-1 (parameter is not used)

Example dscp_byte_media=a6

Explanation This parameter serves to define the value of the field DSCP in the IP headers of datagrams sent by MVTS.

Note: The parameter “dscp_byte” in the configuration of a gateway or RAS user overrides the global parameter “dscp_byte_media”.

Parameter dscp_byte_signaling= meraproxy.cfg, section [Proxy]

Data type Integer

Valid values

0 – 255 (in the hexadecimal notation) dscp_byte_signaling=<number>

Default value

-1 (parameter is not used)

Example dscp_byte_signaling=85

Explanation This parameter serves to define the value of the field DSCP in the IP headers of signaling packets sent by MVTS.

Parameter dst_allowed_prefix= gateway.cfg, user.cfg


Valid values Regular expressions dst_allowed_prefix=<number>

Default value

Empty string

Example

Explanation The parameters serve to define allowed and disallowed prefixes of destination numbers.

First MVTS checks the parameter dst_disallowed_prefix= (if configured) and then dst_allowed_prefix= (if configured). In case the received destination number does not satisfy the defined prefix pattern(s) the call is rejected with LDC 145 ‘NotAllowedDstPrefix’ and Q.931 disconnect reason 34 ‘No circuit/channel available’.


Page 105 of 218

Parameter dst_disallowed_prefix= gateway.cfg, user.cfg


Valid values

Regular expressions dst_disallowed_prefix=<number>

Default value

Empty string

Example

Explanation The parameters serve to define allowed and disallowed prefixes of destination numbers.

First MVTS checks the parameter dst_disallowed_prefix= (if configured) and then dst_allowed_prefix= (if configured). In case the received destination number does not satisfy the defined prefix pattern(s) the call is rejected with LDC 145 ‘NotAllowedDstPrefix’ and Q.931 disconnect reason 34 ‘No circuit/channel available’.

Parameter dst_bill_translate= dialpeer.cfg


Valid values

Regular expression dst_bill_translate=regexp1[|regexp2[|regexp3]]

Default value

Empty string

Example dst_bill_translate=77|.|.|32/774\332

Explanation Use this field to set the dst_number translation patterns for billing purposes.

Translation syntax is the same as in case of dst_translate=

Use the keyword empty when you need to denote an empty number in a translation pattern.

The list of the macronames that can be employed in all the translation fields (except the group_translate= field) of the dialpeer.cfg file is as follows:

$ani$ - ANI number of the caller

$dnis$ - number of the called party

$bill_ani$ - ANI number for billing

$bill_dnis$ - number of the called party for the purposes of billing

$user$ - user name

$id$ – unique call identifier (extracted form a CDR record) in the following notation <MVTS start time stamp>#<call ordinal number>#

Note: When the dial peer record contains both the bill_translate= and dst_bill_translate= patterns the dst_number= will be translated in accordance with the translation pattern of the dst_bill_translate= field.


Page 106 of 218

Parameter dont_make_stat_for_ldc= gateway.cfg, user.cfg, meraproxy.cfg, section [H.323]


Valid values MVTS LDCs

Default value

Example dont_make_stat_for_ldc=134;135

Explanation Use the parameter to define a list of local disconnect codes that prevent the MVTS from gathering statistics for calls completing with the LDCs on the list. The global list configured in section [H.323] of meraproxy.cfg overrides similar lists defined in configurations of static-IP GWs (gateway.cfg) and registering endpoints (user.cfg).

Note: This parameter’s value cannot exceed 2000.


Page 107 of 218

dst_acct_enable= Parameter gateway.cfg, user.cfg

Data type Boolean

Valid values 0 – disables accounting

1 – enables accounting

dst_acct_enable=<number>

Default value 1

dst_acct_enable=1 Example

Explanation Use the parameter in configuration of termination gateways/RAS users to enable or disable accounting at the destination. With dst_acct_enable=0 the originator gateway’s value of the field user= will appear in the username field in both the incoming and outgoing leg packets. With dst_acct_enable=1 the username field in the incoming leg packets will contain the value of the field user= of the origination gateway, while the username field in the outgoing leg packets will display the value of the field user= of the termination gateway.

Parameter dst_exclude=, src_exclude=

dialpeer.cfg


Note: the parameter dst_acct_enable= functions as above with acct_leg_type=4 and 5 only

Valid values Regular expression src_exclude=<regexp>; <regexp>; …

dst_exclude=<regexp>; <regexp>; …


dst_exclude= 78312.... ; 7095[0-9]*

Example

src_exclude= 78414....

Explanation Use these parameters to specify a list of dial peers (phone numbers) that are unfit for call setup.


Page 108 of 218

Parameter dst_pattern=, src_pattern=

dialpeer.cfg


Valid values Regular expression src_pattern = <string>; <string>; …

dst_pattern = <string>; <string>; …

Default value dst_pattern=empty string

src_pattern=all numbers

Example dst_pattern = 78312.... ; 7095[0-9]* src_pattern = 78414....

Explanation

Use these fields to specify number patterns for the called (dst_pattern= ) or calling (src_pattern= ) party. The applicable translation rules are set in form of regular expressions.

Parameter dst_numbering_plan= gateway.cfg, user.cfg

Data type Integer

Valid values

Decimal representation of the type:plan parameter

dst_numbering_plan=<number>

Default value

0

Example dst_numbering_plan=33

Explanation Use this field to configure the type:plan parameter for the called number.

Example: Suppose your intention is to configure the type:plan information elements for the gateway as type=International number and plan=ISDN/telephony numbering plan.

According to ITU-T Recommendation Q931 (called party number Information Element) the type element 'International number' (bits 7 6 5) is 0 0 1 and the plan element 'ISDN/telephony numbering plan' (bits 4 3 2 1) is 0 0 0 1. Therefore, set numbering_plan=33 (33 is decimal representation of the binary number 0 0 1 0 0 0 1). Note: The src_numbering_plan= and dst_numbering_plan= fields override the settings of the numbering_plan= parameter, which is effective only if src_numbering_plan=0 and dst_numbering_plan=0.

Note: the parameter is valid in configuration of termination endpoints only.

Note: If set to -1, the corresponding fields received from the call originator will be sent to the call terminator unchanged.


Page 109 of 218

Parameter dst_translate=, src_translate=

dialpeer.cfg


Valid values Regular expression src_translate= regexp1[|regexp2[|regexp3]]


Example A local number evolving into a full international number

dst_translate=....../78312&

778899 -> 78312778899

Changing some digits in the number

src_translate=77|.|.|32/774\332 778832 -> 774832

Explanation Use this parameter to specify follow-up number translation patterns for the calling (src_translate= ) and called (dst_translate= ) parties. This value normally comprises two parts: a regular expression for the search string, and a replacement string delimited with the “/” character. Using the delimiter “|”, you may divide the search string sections for convenience. The replacement string may contain a substring matching the section with the section number placed after the “\” character. “&” is used in the replacement string for a substring satisfying conditions of all sections simultaneously. These fields are optional.


Page 110 of 218

Parameter dst_translate=

src_translate= gateway.cfg, user.cfg


Valid values

Regular expression

The value is normally comprised of two parts:

o Regular expression for the search string

o Replacement string delimited by the “/” character.

The search string may be divided for convenience into sections by delimiter “|”. The replacement string may contain a substring satisfying the condition of the section with the section number placed after character ”\”. Character “&” is used in the replacement string for a substring satisfying conditions of all sections simultaneously

src_translate= regexp1[|regexp2[|regexp3]] dst_translate= regexp1[|regexp2[|regexp3]]

Default value

Empty string

Example A local number evolving into a full international number

dst_translate = ....../78312&

778899 -> 78312778899

Changing some digits in the number

src_translate = 77|.|.|32/774\332

778832 -> 774832

Explanation Define a translation pattern for the destination (dst_translate=) or source (src_number=) number.


Page 111 of 218

Parameter dst_user_orig_leg= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 – disables username substitution

1 - enables username substitution

If the parameter user= in the description of the termination gateway is not defined, the field UserName in the accounting packets sent to RADIUS for the outgoing call leg will contain the IP address of the termination gateway.

dst_user_orig_leg=<number>

Default value 0

Example dst_user_orig_leg=1

Explanation Use this flag to control the user name substitution into the UserName field of originating leg accounting packets sent to the RADIUS server.

Note: This parameter is functional only with the acct_leg_type= values 4 and 5.


Page 112 of 218

E Parameter endpoint_ttl= meraproxy.cfg, section [Gatekeeper], user.cfg

Data type Integer

Valid values Time in the notation [[hh:]mm:]ss

endpoint_ttl=<number>

Default value 00:00

Example endpoint_ttl=15:00

Explanation Sets a registration update interval for RAS users (and registering users registered with the MVTS gatekeeper). The parameter value is included into the RegistrationConfirm packet. Failure to re-register in time causes forcible unregistration of the user.

Note: If set to less than 10 seconds, the default value is used.

Parameter exchange_calling_redirect_number= gateway.cfg, user.cfg

Data type Boolean

Valid values 0 – disallows exchange

1 – allows exchange

Default value 0

Example exchange_calling_redirect_number=1

Explanation Use this field to allow or disallow the MVTS to exchange the values of the CallingPartyNumber and RedirectingNumber fields of SETUP, received from the call originator (gateway or RAS user).

If SETUP arrives with one of the two fields only (e.g. CallingPartyNumber), the MVTS will remove the present field from SETUP and substitute its value into the RedirectingNumber field. Thus, the SETUP message sent by the MVTS to the call termination point will have the RedirectingNumber field with the CallingPartyNumber value, received in SETUP from the originator.


Page 113 of 218

Parameter expire_date= user.cfg, gateway.cfg

Data type Integer

Valid values A date in the

dd-mm-yy:HH:MM notation

dd=01-31

mm=01-12

yy=1970-2038

HH=00-23 MM=00-59

expire_date=<dd-mm-yy:HH:MM>


Example expire_date=24-12-2004:00:00

Explanation Use this parameter to define the gateway operating term - that is the date which the MVTS will stop exchanging traffic with the gateway (RAS user).


Page 114 of 218

F Parameter fake_rtcp= user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – disables RTCP faking

1 – makes the MVTS send RTCP packets in lieu of the gateway

fake_rtcp=<number>

Default value 0

Example fake_rtcp=1

Explanation Use this flag to enable/disable RTCP faking for gateways devoid of the RTCP capability. Use this parameter to enable interoperation with VocalTec gateways.

Note: Employment of this function may hamper fax transmission.

Parameter file= meraproxy.cfg, section [Billing]; section [Debug], section [Statistics]


Valid values Characters from ‘A’…‘Z’(‘a’…’z’), numbers from 0 to 9 and the underscore character

Default value bill – for section [Billing]

log – for section [Debug]

empty string – for [Statistics]

Example file=../billing/bill

Explanation Use this parameter to specify the name prefix of and/or path to the file, where the MVTS saves billing [Billing], runtime [Debug] and statistical [Statistics] data (without the time stamp and the current file flag).


Page 115 of 218

Parameter force_alerting= user.cfg, gateway.cfg

Data type Integer

Valid values A positive number representing time interval in milliseconds

force_alerting=<number>

Default value 0 (disables the function)

Example force_alerting=0

Explanation

Use this parameter to set a time interval (in milliseconds), after which the system will send a neutral Alerting message to the origination gateway.

Note: this function becomes useful if a gateway requires an Alerting message for normal operation. For example, the VocalTec 2000 gateway (as well as some CISCO models) operate with one-way audio only or may not pass voice at all, if they fail to receive the Alerting message.

Note: the parameter is valid in configuration of origination endpoints only.

Parameter force_call_proceeding= user.cfg; gateway.cfg

Data type Integer

Valid values

A positive integer representing a delay time (in ms).

force_call_proceeding=<number>

Default value

0 (disables the function)

Example force_call_proceeding=4000

Explanation

Use this field to set a delay (in milliseconds), after which the MVTS forwards a CallProceeding message with neutral content to the origination gateway (RAS user).

Note: This feature becomes useful when the actual CallProceeding message delay on the call-termination side does not coincide with the H.323 standard (4 seconds). If such a discrepancy does occur, it may result in abortion of the call which otherwise might be successful. For example, this happens to the SMG gateways communicating with Westerm Europe operators, since the SMG gateways do not tolerate delays in receiving the CallProceeding m essage.



Page 116 of 218

Parameter force_originate_telephony= user.cfg; gateway.cfg

Data type Boolean

Valid values

0 – disable the function

1 - with this parameter set to “1” accounting packets on the egress call leg will include fields “h323-call-type=Telephony” and “h323-call-origin=originate”.

force_call_proceeding=<number>

Default value

0

Example force_originate_telephony=1

Explanation Together with the parameter “nas_port_name=” this parameter allows discrimination of vendors associated with the same termination gateway.

Parameter force_proxy= meraproxy.cfg, section [Proxy]

Data type Boolean

Valid values 0 – forced proxy mode disabled

1 – forced proxy mode enabled

force_proxy=<number>

Default value 0

Example force_proxy=0

Explanation Use the parameter to enable/disable function of forced traffic proxying. The parameter overrides the settings of the proxy_type= field in the configuration of gateways.


Page 117 of 218

G Parameter gatekeeper= gateway.cfg


Valid values Name of the gatekeeper gatekeeper=<string>


Example gatekeeper=main_ gatekeeper

Explanation Use this parameter to specify the name of the gatekeeper through which calls get to the destination gateway. Note: the use of the parameter gatekeeper= in a gateway record requires that you comment or remove the parameter address= and the parameter port= from the record.

Parameter gatekeeper_cfg= meraproxy.cfg, section [Administration]


Valid values File name gatekeeper_cfg=<filename>

Default value gatekeeper.cfg

Example gatekeeper_cfg=my_gk.cfg

Explanation Use this parameter to indicate the file with information about gatekeepers. Specify the file path relative to the root directory or the configuration file merarpoxy.cfg.

Parameter gatekeeper_enable= meraproxy.cfg, section [Gatekeeper]

Data type Boolean

Valid values 0 – disable the MVTS gatekeeper functionality

1 – enable gatekeeper

gatekeeper_enable=<number>

Default value 0

Example gatekeeper_enable=1

Explanation

Use this flag to enable or disable the MVTS gatekeeper functionality. With gatekeeper_enable=0 no RAS registrations will be possible.


Page 118 of 218

Parameter gatekeeper_id= meraproxy.cfg, section [Gatekeeper]


Valid values Arbitrary set of characters gatekeeper_id=< character string>

Default value XPGK_<host_name>

Example gatekeeper_id=OwnMVTS

Explanation Use this parameter to assign the MVTS gatekeeper an ID.


Page 119 of 218

Parameter gateway= dialpeer.cfg

Data type Name

Valid values An internal name of the gateway assigned to it in the gateway data file or one of the following macro names:

AGAIN - invokes number translation and the search for the dial-peer corresponding to the translated number starts anew.

ENDPOINTS – initiates a search for a gateway with a perfect match for the call number.

NULL – stops further dialpeer search and terminates the call.

NEXT – initiates number translation and transition to the next dialpeer.

EXTERNAL – enables use of external routing information from the RADIUS server.

GOTO – rerouts the call to another dial peer.

1 – unconditional rerouting. Example [DP1]

....

gateway=GOTO:DP2

....

Explanation: reroute the call to the diaplpeer “DP2”

2 – conditional rerouting. Example: [DP1]

....

gateway=GW;GOTO:Q931=17:DP2

...

Explanation: If the routing attempt to the gateway “GW” fails, MVTS will reroute call to the dial peer “DP2” only when the Q.931 disconnect cause code received from the gateway is 17.

gateway=<string >


Example gateway=Moscow

Explanation Use this mandatory field to specify the internal name of the gateway the call is to be forwarded to when the given dial peer is selected. The field may have section names from the gateway.cfg and user.cfg files as its parameter. This imposes an additional limitation on the section names, which have to be unique in both the


Page 120 of 218

Parameter gateway= dialpeer.cfg

files.

Parameter gateway_cfg= meraproxy.cfg, section [Administration]


Valid values File name gateway_cfg=<file_name>

Default value gateway.cfg

Example gateway_cfg=my_gateway.cfg

Explanation Use this parameter to specify the name of the file containing data about static gateways. Specify the file path relative to the root directory or the system configuration file merarpoxy.cfg.

Parameter gateway_mode= gateway.cfg

Data type Integer

Valid values 0 – the GW can neither send nor receive calls

1 – the GW can only send calls

2 – the GW can only receive calls

3 – the gateway can send and receive calls

gateway_mode = <number>

Default value 3

Example gateway_mode=2

Explanation Use this field to specify the gateway operating mode.


Page 121 of 218

Parameter gateway_type= user.cfg; gateway.cfg

Data type Integer

Valid values 0 – gateway type unknown

1 – CISCO gateway

2 – VocalTec gateway

3 – Samsung gateway

4 – MediaRing gateway

8 – VocalTec gateway, but without swapping over CALL ID and CONF ID in RADIUS packets. 9 – UkrTelecom gateway

gateway_type = <number>

Default value 0

Example gateway_type=1

Explanation Use this field to specify a gateway type.

Parameter group= user.cfg; gateway.cfg



group = <string>

Default value RASREG

Example group = GROUP1

Explanation Use this field to specify the name of the group the gateway (RAS user) belongs to. If you wish to specify several groups for one endpoint, be sure to delimit the group names with a semicolon.

Note: Grouping gateways with common features facilitates configuration tasks.


Page 122 of 218

Parameter group_allow=

group_deny=

dialpeer.cfg


Valid values A list of gateway groups group_allow=<string1>;<string2>;…

group_deny=<string3>;<string4>;…


Example group_allow=GROUP1

group_deny = GROUP3

Explanation Use these parameters to specify lists of the gateway groups for whom the outbound calls through the dial peer are allowed (group_allow=) or denied (group_deny=). The lists are used in the dial peer search.

Parameter group_translate= dialpeer.cfg


Valid values Arbitrary string of characters group_translate=<string1>/<string2>;


Example group_translate=OLDGROUP/NEWGROUP

Explanation Use this field to rename configured groups.


Page 123 of 218

H Parameter H323_gw_id= user.cfg; gateway.cfg

Data type String of characters

Valid values Arbitrary character string h323_gw_id=<string>


Example H323_gw_id=MainGW

Explanation Use this field to specify the Source H323 Alias identifier, which sometimes becomes necessary for a remote gateway (RAS user). The parameter applies to configuration of originators only.

Parameter hunt_mode= dialpeer.cfg

Data type Integer

Valid values 0 disables the functionality

1 rotates the gateways on the list every 10 seconds (the first gateway becoming the last one)

2 sorts the gateways on the list every 10 seconds by their absolute load (ascending sort)

3 sorts the gateways on the list every 10 seconds by their load/capacity ratio (ascending sort)

hunt_mode = <number>

Default value 0

Example hunt_mode=1

Explanation

Use this parameter to set the load balancing technique for the gateways defined in the gateway= field of the dial peer record. This field is optional.


Page 124 of 218

Parameter hunt_mode= gateway.cfg

Data type Integer

Valid values 0 (default) disables the functionality (MVTS forwards traffic only to the first IP on the list specified in the address= field)

1 - the MVTS rotates the IPs on the list in a round-robin fashion every 10 seconds (the first IP on the list becomes the last; the second IP becomes the first and so on)

2 - the IPs on the list change their eligibility every 10 seconds depending on current traffic load (the MVTS sends traffic to the least loaded IP)

hunt_mode = <number>

Default value 0

Example hunt_mode = 1

Explanation The parameter serves to define a load-balancing technique for termination gateways with more than one IP address specified in the field address=.

Parameter hunt_sort_period= dialpeer.cfg

Data type Integer

Valid values Positive integers hunt_sort_period= <number>

Default value 10

Example hunt_sort_period=22

Explanation

The parameter serves to set a period of time for rotation of the gateways specified in the field gateway=.

For example, if hunt_sort_period=20, the rotation will be performed every 20 seconds.

Rotation of the gateways is carried out in accordance with the setting of the hunt_mode= parameter of the same configuration file (dialpeer.cfg).


Page 125 of 218

Parameter hunt_stop= dialpeer.cfg

Data type Boolean

Valid values 0 – continues search

1 – stops further search

hunt_stop = <number>

Default value 0

Example hunt_stop = 1

Explanation Use this flag to control further dial peer search in situations when the gateway in the selected call path is inaccessible or busy. Optional field.


Page 126 of 218

I Parameter id= gatekeeper.cfg


Valid values Arbitrary string id=<type> (number, name, etc.)

Default value

Example id=5623

Explanation Use this field to specify the gatekeeper identifier.

Parameter ignore_lar_fault= gatekeeper.cfg, user.cfg

Data type Boolean

Valid values 0 – enable routing cessation (follow LAR-FAULT-REASON)

1 – override LAR-FAULT-REASON routing stoppage (continue route search regardless of LAR-FAULT-REASON)

ignore_lar_fault=<number>

Default value 0

Example ignore_lar_fault=1

Explanation Enable/disable cessation of further route search if the call termination attempt via the previous route failed.

If the value of the parameter is 1, the MVTS will look for another termination gateway (RAS-user) to complete the call termination.

Note: the parameter is valid only in configuration of the origination gateways and RAS users.


Page 127 of 218

Parameter in_converter= user.cfg


Valid values Converter name defined in the section [H.323] of meraproxy.cfg

in_converter=<string>

Default value

Example in_converter=SIPconv

Explanation Use this field to specify a converter for ingress calls that originate from the RAS user.

Parameter in_local_address= user.cfg


Valid values

The list of local addresses divided by ‘;’ in_local_

address=

<string>

Default value

Example in_local_address=212.92.148.115;192.168.131.69

Explanation This parameter makes it possible to differentiate originating gateways with the same signaling addresses (subnet masks). The values should be divided by ‘;’.

Parameter index_valid_time= meraproxy.cfg, section [SNMP]

Data type A positive integer

Valid values A time interval in days index_valid_time=<number>

Default value 0

Example index_valid_time=11

Explanation Represents the period of time since MVTS start. After the expiration of that period, dynamic SNMP index of an inactive object is purged from the System memory.


Page 128 of 218

Parameter interdigit_timeout=

user.cfg, gateway.cfg

Data type Integer

Valid values

Integers representing a time interval in milliseconds

interdigit_timeout=<integer>

Default value

0 disables parameter

Example interdigit_timeout=38

Explanation Use this field to configure the maximum time interval (in milliseconds) between two subsequent Q931 Information messages sent by the call originator after the SETUP message. The messages Information contain digits additionally dialed by the caller.

If the Information message arrives within the configured time, or if the received message contains the field SendingComplete, the MVTS processes the call with account for the additionally dialed digits.

Note: this parameter is meaningful only if the field use_info_digits= in the configuration of origination gateways/RAS-users is set to 1.


Page 129 of 218

Parameter in_dst_translate= in_src_translate=

user.cfg; gateway.cfg


Valid values

The value comprises two parts delimited by the “/” character:

• regular expression for the search string

• replacement string The search string may be divided for convenience into sections by the delimiter “|”. The replacement string may contain a substring satisfying the condition of the section with the section number placed after the backslash symbol ”\”. The ampersand character “&” is used in the replacement string for a substring satisfying the conditions of all sections simultaneously.

in_src_translate=

regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&] in_dst_translate=

regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&]

Default value

Empty string

Example i n _ d s t _ t r a n s l a t e =....../78312&

778899 -> 78312778899 (a local number evolving into a full international number)

i n _ s r c _ t r a n s l a t e =77|.|.|32/774\332 778832 -> 774832 (Changing some digits in the number)

Explanation

Use this parameter to set a pattern for preliminary translation of the call source (in_src_translare= ) or destination (in_dst_translate= ) number.

Preliminary number translationis carried out upon arrival of a call from this gateway (RAS user) and prior to a dial peer search. This parameter is useful when the gateway (RAS-user) provides numbers in a format other than the E.164 format.

Number translation rules are identical to those described for the fields src_translate=, dst_translate=.


Page 130 of 218

Parameter internal_network_mask= meraproxy.cfg, section [Proxy]


Valid values

Net mask in the common oct.oct.oct.oct format

Default value

255.255.255.255

Example internal_network_mask=255.255.255.0

Explanation Define a LAN mask to avoid traffic proxying on the local area network. The MVTS disables traffic proxying when a call passes across the LAN.

Parameter ip_precedence= merproxy.cfg, section [Gatekeeper]

Data type Integer

Valid values A number in the 0-7 range. ip_precedence=<number>

Default value 3

Example ip_precedence=2

Explanation Use this parameter to set the default precedence of IP packets arriving from gateways (RAS users) to be sent to the destination. The higher the value, the higher is the precedence. You can also use the parameters i p _ p r e c e d e n c e o f t h e c o n f i g u r a t i o n f i l e s user.cfg and gateway.cfg to set the precedence of IP packets for individual gateways (RAS users). See also the configuration parameter tos_precedence.


Page 131 of 218

Parameter ip_precedence= user.cfg; gateway.cfg

Data type Integer

Valid values A number in the 0-7 range. ip_precedence=<number>

Default value 3

Example ip_precedence=2

Explanation Use this parameter to set the precedence of IP packets arriving from individual gateways (RAS users), the configuration of which contains the set ip_precedence= parameter. For example, there are two gateways involved in a call session, namely GW1 and GW2. If the settings of GW1 include the configured parameter (ip_precedence=2), the MVTS will set the priority of all the IP packets sent to GW2 to 2. It is advisable to set ip_precedence= in excess of 3 for the least possible number of gateways (RAS users), since a large amount of high-precedence calls may cause instability of the OS kernel. The field is optional. See also the configuration parameter tos_precedence.


Page 132 of 218

K Parameter keepalive= gatekeeper.cfg

Data type Integer

Valid values A positive integer, representing a time interval

keepalive= <number>

Default value 300

Example keepalive=10

Explanation Use this parameter to specify the time interval (in seconds) of repeated registration with the gatekeeper.

Parameter keepalive_type= gatekeeper.cfg

Data type Boolean

Valid values 0 sends a “light-weight” message with a request to prolong registration

1 sends a full-scale re-registration request to the gatekeeper

keepalive_type=<number>

Default value 0

Example keepalive_type=1

Explanation Use this parameter to specify the type of the registration message to be sent to the remote gatekeeper during re-registration.


Page 133 of 218

L Parameter ldc_q931_reason= meraproxy.cfg, section [H.323]

Data type Integer

Valid values For LDC – all local disconnect codes.

For Q931 – integer values in the 0 – 127 range.

If at least one value of the <LDC>-<Q931 reason> pair fails to correspond to the above conditions, the whole pair is ignored.

ldc_q931_reason=<LDC>-<Q931 reason>;<LDC>-<Q931 reason>...

Default value

Example ldc_q931_reason=102-21;103-21

Explanation Set LDC-Q931 disconnect reason correspondence. The purpose of this configuration parameter is to configure Q931 disconnect code matches for MVTS LDSs other than 1 and 2.

Note: The parameter’s value cannot exceed 2000.

Parameter level= meraproxy.cfg, section [Billing]

Data type Boolean

Valid values 0 – disable CDR writing

1 – enable CDR writing

level=<number>

Default value 1

Example level=1

Explanation Use this parameter to enable/disable writing CDRs to the billing file. All values greater than 1 are treated by the system as 1.


Page 134 of 218

Parameter level= meraproxy.cfg, section [Debug]

Data type Integer

Valid values 0 disables log writing

1 keeps logged data at minimum

2 sets intermediate data detail level

3 turns on most detailed call session logging

level=<number>

Default value 0

Example level=1

Explanation The parameter sets a detail level for runtime data written to the debug log. The greater is the value the more detailed information is saved in the log file and the bigger the log is. Whenever possible, keep the system at its default logging level.

Parameter load_balancer_address= meraproxy.cfg, section [Administration]


Valid values

load_balancer_address=<number>

Default value

Example load_balancer_address=1719

Explanation This parameter is used to define the IP address of the load balancer in three-level MVTS cluster systems.


Page 135 of 218

Parameter local_acct_port= meraproxy.cfg, section [Radius], section [BackupRadius]

Data type Integer

Valid values A port number local_acct_port=<number>

Default value 1813 2813 for [BackupRadius]

Example local_acct_port=1845

Explanation Use the parameter to specify the port for accounting responses from the RADIUS server. Make sure the local_acct_port= values of the sections [Radius] and [BackupRadius] differ.

Parameter local_address= meraproxy.cfg section [Radius], section [BackupRadius].


Valid values oct.oct.oct.oct or * (which initiates automatic IP address search)

local_adress = <address>

Default value The default gateway field from the system routing table

Example local_address = *

local_address=199.99.99.99

Explanation Use this parameter to specify the local IP address for the bind function.

Parameter local_address= meraproxy.cfg, section [Administration]


Valid values IP address in common dot-separated format or * (to enable automatic address determination)

local_address=<IP address>

Default value

Example local_address=* local_address=199.99.99.99

Explanation Use this parameter to specify the local IP address to be used in call setup when the necessary data is not available from the OS routing table.


Page 136 of 218

Parameter local_address= gatekeeper.cfg


Valid values oct.oct.oct.oct local_address=<IP address>

Default value 0.0.0.0

Example local_address=195.88.57.123

Explanation Use this parameter to specify a local IP address for communication with the remote gatekeeper.

Parameter local_address= gateway.cfg


Valid values IP address in the oct.oct.oct.oct. notation


Default value



Explanation Use this parameter to define a list of local IP addresses both for ingress and egress traffic. The system always selects the least busy IP address. In situations when all the configured addresses are congested, address selection is performed according to the selection policy determined in local_ip_manager_mode= in the section [Proxy] of meraproxy.cfg. When the local_address= parameter is not defined, the address selection is based on the local routing table and the system will utilize the target address of the incoming call for ingress traffic.


Page 137 of 218

Parameter local_address= user.cfg


Valid values IP address in the oct.oct.oct.oct. formation or * for automatic IP address determination


Default value The default gateway from the system routing table.



Explanation Use this parameter to define a list of local IP addresses both for ingress and egress traffic. The system always selects the least loaded IP address. In the situation when all the defined addresses are congested, address selection is performed according to the selection policy determined in the local_ip_manager_mode= field in the [Proxy] section of the meraproxy.cfg file. With the local_address= parameter not defined, the address selection is based on the local routing table and the system will utilize the target address of the incoming call for ingress traffic.

Parameter local_address= meraproxy.cfg, section [Proxy]



local_address=<address>

Default value

Example local_address=195.88.57.121

Explanation This parameter defines a local IP address to be used in media traffic proxying.


Page 138 of 218

Parameter local_address_redefine = meraproxy.cfg, section [Proxy]

Data type IP address local_address_redefine =

Valid values

IP address in common dot-separated format

local_address_redefine =<LocalIpAddr1/LocalIpAddr2>

Default value

Example ip_precedence=192.168.132.1/192.168.132.2

Explanation This parameter allows the MVTS to substitute the local address involved in call setup for another address to be used for media traffic proxying. For example, having received the Setup message at LocalIpAddr1 the MVTS substitutes LocalIpAddr1 for LocalIpAddr2 and uses it for media traffic proxying for the current call session (in the CDR record this local address is presented in the field SELECTED-INCOMING-LOCAL-ADDRESS).

Parameter local_auth_port= meraproxy.cfg, section [Radius], section [BackupRadius]

Data type Integer

Valid values Port number local_auth_port=<number>


Example local_auth_port=1844

Explanation Use this parameter to specify the MVTS authentication port. Make sure the values of local_auth_port= in the sections [Radius] and [BackupRadius] differ.


Page 139 of 218

Parameter local_ip_manager= meraproxy.cfg, section [Proxy]

Data type Alphanumeric string

Valid values local_ip_manager=

<ip_address>/<RxMax>/<TxMax>/

TcpPingAddress:Port

where <ip_address> is a local IP address <RxMax> is the maximum bandwidth for ingress traffic <TxMax> is the maximum bandwidth for egress traffic [TcpPingAddress:Port] is the IP and port used for periodic (30 seconds) TCP connect integrity checks. This element is optional and may be omitted.

Example local_ip_manager=

192.168.1.1/120/120;

192.168.1.2/64/64;192.168.1.3/512/256

Explanation Use this parameter to configure bandwidth allotments for local IP addresses. The system prepares per-address traffic estimates every 30 seconds on the basis of the data obtained from the proxy module. By default (and with 0 bandwidth settings) there are no bandwidth limitations for traffic. This filed allows you to list values, the elements being delimited with ‘;’ or ‘,’.

Parameter local_ip_manager_mode= meraproxy.cfg, section [Proxy]

Data type Integer

Valid values

0 – use the default address;

1 – abort the call;

2 – use the least loaded address;

3 – use the least busy address from the actual to max.load ratio standpoint

local_ip_manager_mode=<number>

Default value

0

Example local_ip_manager_mode=3

Explanation

Use the field to determine the system’s behavior in situations when all IPs on the list specified in the local_address= field are congested with traffic. The system always selects the least busy IP address. With the local_address= parameter not defined, the address selection is based on the local routing table and the system will utilize the destination address of the incoming call for ingress traffic.


Page 140 of 218

Parameter local_port= meraproxy.cfg, section [SNMP]

Data type Integer

Valid values Port number local_port=<number>

Default value 161

Example local_port=161

Explanation Use this parameter to specify the MVTS port for SNMP.

Parameter local_route_port= meraproxy.cfg, section [Radius], section [BackupRadius]

Data type Integer

Valid values Port number local_route_port=<number>


Example local_route_port=1856

Explanation

Use the parameter to set the MVTS port for RADIUS aided external routing. Make sure the local_route_port= values in the sections [Radius] and [BackupRadius] differ.

Parameter local_route_server_address= meraproxy.cfg, section [Administration]


Valid values

IP address in common dot-separated format

Default value

Example local_route_server_address=199.99.99.99

Explanation This is a configuration parameter of Media MVTS, which is a part of the MVTS cluster system. Use this parameter to define a local address for sending statistical data (priority, number of current calls, maximum number of calls for the Media MVTS) to the routing server.


Page 141 of 218

Parameter lrq_allowed_only= gateway.cfg, user.cfg

Data type Boolean

Valid values 1 enables function

0 disables function

lrq_allowed_only=<0/1>

Default value 0

Example lrq_allowed_only=0

Explanation Use this parameter to enable/disable authorization of a call by its CallID. When lrq_allowed_only=1 the MVTS upon the receipt of an LRQ packet from this gateway extracts CallId from the received packet, places it into the buffer and waits for a SETUP message with identical CallId arriving from an unknown IP address. The maximum wait time (in seconds) is set in the arq_alive_time= parameter in the gateway configuration.

Warning: calls originated by gateways with lrq_allowed_only=1 in the configuration will not be processed!

Note: to allow the MVTS to accept calls from unknown IP addresses set the value of the public_access= parameter (meraproxy.cfg, section [Administration]) to 1.

Параметр arq_alive_time= meraproxy.cfg, section [Gatekeeper]

Тип данных Integer

Значения Positive integer representing a period of time in seconds

0 – MVTS will not wait for a SETUP with a CallId

arq_alive_time=<integer>

Значение по умолчанию

6

Пример arq_alive_time=18

Объяснение Use this parameter to specify a period of time in seconds during which the MVTS waits for a SETUP with the CallId identical to the one, previously sent to the MVTS by this gateway in LRQ.


Page 142 of 218

M Parameter mail_alert= meraproxy.cfg, section

[Administration]


Valid values E-mail address mail_alert= <address>


Example mail_alert = [email protected]

Explanation Use this parameter to specify an e-mail address for malfunctioning alerts that the system may develop. This field is optional.

Parameter mask= gateway.cfg



mask=<oct.oct.oct.oct>


Example mask=197.85.344.0

Explanation Use this field to specify the mask for the gateway calling connections. The gateway settings will apply to all inbound calls that satisfy the address/mask condition.

Parameter master_address= meraproxy.cfg, section [Redundancy]


Valid values IP address in the common dot-separated format

master_address=< oct.oct.oct.oct >

Default value

Example master_address=192.168.1.1

Explanation Use this field to specify the IP address of the main MVTS used for remote ssh access from the failover system to get down traffic-handling IP addresses.

mailto:[email protected]


Page 143 of 218

Parameter master_gatekeeper= meraproxy.cfg, section [Redundancy]


Valid values Character string representing the name of a section in the gatekeeper.cfg file of the failover server

master_gatekeeper=<string>


Example master_gatekeeper=Major_GK

Explanation Provide a name of the primary MVTS server (actually the name of a section in the gatekeeper.cfg configuration file of the failover MVTS). The section describes the properties of the primary MVTS acting as the gatekeeper with which the failover MVTS registers.

Parameter master_gatekeeper= gatekeeper.cfg


Valid values The name of a section in the gatekeeper.cfg file

master_gatekeeper=<string>


Example master_gatekeeper=Master_GK

Explanation

This parameter when used together with slave_gatekeeper= serves to provide resilience in gatekeeper services rendered to the MVTS.

For example, the configuration file gatekeeper.cfg includes four sections: GK_1, GK_2, GK_3, and GK_4 with descriptions of gatekeepers. Suppose you wish to make the gatekeeper GK_1 the main GK the MVTS registers to, all the rest remaining alternate gatekeepers used in case the main one fails. To configure such master-slave GK relationship, add the parameter slave_gatekeeper= GK_2; GK_3; GK_4 to the section GK_1 of the file gatekeeper.cfg. At the same time add the master_gatekeeper=GK_1 entry to the sections GK_2, GK_3 and GK_4. With such configuration the MVTS, when started, will register only to the master gatekeeper and registration with the remaining three GKs will be suspended. If the MVTS loses its registration with the master GK for some reason, it will attempt to register with the first alternate GK on the slave_gatekeeper= list. When the last slave GK on the list fails, the MVTS will try to restore its registration with the master GK.


Page 144 of 218

Parameter max_call_duration= meraproxy.cfg, section [Administration]

Data type Integer

Valid values Positive integers in the 100 – 1.000.000 range

max_call_duration=<integer>

Default value 10000 (2hrs 46min 40sec)

Example max_call_duration=3000

Explanation Use this parameter to set a maximum reasonable call duration limit in seconds, beyond which a call is presumed dangling and subject to forceful interruption with MVTS local disconnect code 300 (dangling call).

Parameter max_call_duration= gateway.cfg, user.cfg

Data type Integer

Valid values max_call_duration=<number>

Default value 0 - parameters disabled

Example max_call_duration=1000

Explanation Set a maximum duration (in seconds) for calls routed to the gateway. If the parameter is not defined or its value is 0, the duration limit for calls through this gateway will be set by the value of the max_call_duration= field in the section [Administration] of meraproxy.cfg. If the latter is not defined either, the duration of calls through this gateway will be limited to 10, 000 seconds.


Page 145 of 218

Parameter max_call_duration_src=

max_call_duration_dst= gateway.cfg, user.cfg

Data type Integer

Valid values

max_call_duration_dst=<number>

max_call_duration_dst=<number>

Default value

0 (parameters disabled)

Example max_call_duration_src=1230

max_call_duration_src=2283

Explanation Use the parameters to set the maximum call duration for the origination (max_call_duration_src=) and termination (max_call_duration_dst=) gateways/RAS-users.

Of two configured values max_call_duration_src= and max_call_duration_dst= the value of the parameter max_call_duration_src= prevails, i.e. when two gateways are involved in a call the maximum call duration is determined by the value of the max_call_duration_src= parameter even if the value of the max_call_duration_dst= parameter in the configuration of the called gateway is different. If the parameter max_call_duration_src= is not defined then the maximum call duration is determined by the value of max_call_duration_dst=. When neither max_call_duration_dst= nor max_call_duration_src= is defined the maximum call duration allowed is determined by the value of the global parameter max_call_duration= (section [Administration] of meraproxy.cfg). With none of the above parameters defined, the default maximum call duration is 10’000 seconds.

Example:

Suppose, there is a static gateway, the configuration of which includes max_call_duration_src=1000 and max_call_duration_dst=2000. When this gateway is the originator the duration of calls it originates will never exceed 1000 seconds, and when the gateway is the terminator the duration of calls the gateway handles will be limited to 2000 seconds (provided the configuration of the call originator does not include a defined parameter max_call_duration_src=).


Page 146 of 218

Parameter max_callrate= meraproxy.cfg, section [H.323]

Data type Integer

Valid values 0 – 65535 max_callrate=<number>

Default value 0 – CAPS control disabled

Example max_callrate =30

Explanation Use the parameter to set the maximum traffic growth rate CAPS (calls per second). When the defined rate is reached, the MVTS rejects new calls with LDC 141 (eMaxCallRateExceeded).

Parameter max_callrate= gateway.cfg, user.cfg

Data type Integer

Valid values 0 – 65535 max_callrate=<number>

Default value 0 – CAPS control disabled

Example max_callrate =30

Explanation Use the parameter to set the maximum traffic growth rate CAPS (calls per second) for static gateways and RAS users individually. When the set rate is reached, the MVTS rejects new calls (with LDC 141 - eMaxCallRateExceeded) from the gateway/RAS user whose traffic growth rate exceeds the configured value.

Parameter max_dnis_call_dup= meraproxy.cfg, section [Administration]

Data type Integer max_dnis_call_dup=<number>

Valid values A positive integer

Default value

0 (disables checking for call sessions with identical DNIS number)

Example max_dnis_call_dup=5

Explanation Use this parameter to define the maximum admissible number of simultaneous call sessions with identical DNIS number. The parameter helps to avoid looping of VoIP calls via PSTN, which may be caused by a change of the call identifier (CALL ID).


Page 147 of 218

Parameter max_failed_addresses= meraproxy.cfg, section [Redundancy]

Data type Integer

Valid values

0 and positive numbers max_failed_addresses=<number>

Default value

0 – parameter disabled

Example max_failed_addresses=5

Explanation The parameter serves to configure the maximum allowed number of inactive IP addresses (if there are several of them specified in the check_address= field) for the main MVTS host.

When the number of inactive IP addresses on the main host is equal to the number specified as a value of max_failed_address= , the failover MVTS shuts down all the operating IP addresses of the primary MVTS and gets them up on its own network interface cards.

Note: the maximum value of this parameter must not exceed the number of IP addresses specified in check_address= .


Page 148 of 218

Parameter max_failed_retries= meraproxy.cfg, section [Redundancy]

Data type Integer

Valid values

Positive numbers max_failed_retries=<number>

Default value

3

Example max_failed_retries=5

Explanation This parameter defines the maximum acceptable number of failed connect attempts. Connect failures in excess of the configured value serve as an indication of the primary MVTS crash and cause a change in the failover system operating mode. The failover MVTS issues a command to get down the active IP addresse(s) on the main server, gets the same addresses up on its own network interface cards and starts handling traffic.

Parameter max_file_size= meraproxy.cfg, section [Debug]

Data type Integer

Valid values A positive integer in the 102400 (100 Mb) – 2097152 (2 Gb) range representing the file size in kilobytes.

max_file_size=<number>

Default value 1048576 (1 Gb)

Example max_file_size=102400

Explanation Specify the maximum acceptable filesize (kilobyte) for an individual log. When the size of a log file reaches the set maximum the system starts a new file adding the _1, _2, …_n index to the filename.

Parameter max_scd= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values 0 or positive numbers max_scd=<number>

Default value -1

Example max_scd=0

Explanation Use the field to set the maximum acceptable SCD in seconds. The system will send the list of gateways with alarmingly high SCD to the address specified in asr_email_alert=.


Page 149 of 218

Parameter max_scd= gateway.cfg, user.cfg

Data type Integer max_scd=<number>

Valid values Positive numbers

Default value -1

Example max_scd=10

Explanation Use this parameter to set an individual SCD (setup-connect delay) limit in seconds for gateways and RAS users. The SCD time is used to evaluate the route connectivity quality. SCDs above the set value cause inclusion of the gateway name and of the time of SCD growth in the email alert sent to the system administrator every 15 minutes.

Parameter max_scd= dialpeer.cfg

Data type Integer

Valid values 0 or positive numbers max_scd=<number>

Default value -1

Example max_scd=0

Explanation Use the field to set the maximum acceptable SCD in seconds. In case the SCD value of a dial peer exceeds the defined value the system will send an appropriate notification to the administrator.

Parameter max_size= meraproxy.cfg, section [Debug]

Data type Integer

Valid values A positive integer representing filesize in kilobytes

max_size=<number>

Default value 0 (file size control is disabled)

Example max_size=500

Explanation Use this parameter to set the aggregate size of the stored files with debug logs in kilobytes. When the aggregate size of the saved files reaches the set maximum the system deletes old logs.


Page 150 of 218

Parameter max_incoming_time= user.cfg; gateway.cfg

Data type Integer

Valid values A positive integer, specifying traffic volume in minutes

max_incoming_time=<number>

Default value 0 (disables the restriction)

Example max_incoming_time=600

Explanation Use the parameter to define the maximum amount of traffic in minutes that the MVTS will accept from the gateway (RAS user). The data about the amount of incoming and outgoing traffic (in seconds) is written to the text file <stat_file_name>_time, where <stat_file_name> is the value of the parameter ‘file’ of the section [Statistics], by default this value is empty.

Parameter max_outgoing_time= user.cfg; gateway.cfg

Data type Integer

Valid values A positive integer representing maximum traffic volume

max_outgoing_time=<number>


Example max_outgoing_time=600

Explanation Use this parameter to define the maximum amount of traffic minutes that the MVTS will forward to the gateway (RAS user). The data about the amount of incoming and outgoing traffic (in seconds) is written to the text file <stat_file_name>_time, where <stat_file_name> is the value of the parameter ‘file’ of the section [Statistics], by default this value is empty.

Parameter max_lifetime= meraproxy.cfg, section [Debug]

Data type Integer

Valid values A positive integer representing log keeping time in days.

max_lifetime=<number>

Default value 0 (disables date monitoring)

Example max_lifetime=30

Explanation Use this parameter to set the maximum storage time for debug logs in days. When this value is exceeded the system will delete old files.


Page 151 of 218

Parameter max_total_time= gateway.cfg

Data type Integer

Valid values A positive number representing the quantity of traffic minutes

max_total_time=<number>

Default value 0 - the functionality is disabled

Example max_total_time=60

Explanation Set a limit for the gateway ingress and egress traffic (in minutes). When the set limit is reached, the MVTS will stop sending and receiving traffic to/from the gateway. Information about the actually handled traffic stays relevant only until the system is restarted by the mp_kerneld.x command.

Parameter min_acd= meraproxy.cfg, section [Media]

Data type Integer min_acd=<number>

Valid values Positive numbers representing an average call duration (ACD) in seconds

Default value 0 (disengages ACD dependent blocking of the media server).

Example min_acd=50

Explanation Use this parameter to set the lowest ACD level. When the set level is reached, the media server will be blocked for the period of time specified in the s u s p e n d _ t i m e = field. The system checks ACD level when the number of calls, handled by the media server has exceeded the number, specified in the call_radix= field.

Parameter min_acd= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values An integer in the 1 - 10 000 range

min_acd=<number>

Default value

Example min_acd=1000

Explanation Set the lowest ACD level that will trigger email alerts containing a list of gateways or RAS-users whose ACD or ASR has dropped below the configured value.


Page 152 of 218

Parameter min_acd= user.cfg, gateway.cfg



Default value 0


Explanation Set the minimum ACD level for an individual RAS user or a static gateway. A drop in ACD below the set level will result in adding the gateway/RAS user into the list of low-ACD entities. The value of the min_acd= field applies only to a specific RAS user/static gateway, whose record includes the parameter.

Parameter min_acd= user.cfg, gateway.cfg



Default value 0


Explanation Set the minimum ACD level for an individual RAS user or a static gateway. A drop in ACD below the set level will result in adding the gateway/RAS user into the list of low-ACD entities. The value of the min_acd= field applies only to a specific RAS user/static gateway, whose record includes the parameter.

Parameter min_acd= dialpeer.cfg



Default value 0

Example min_acd=3

Explanation Set the minimum ACD level for a dial peer. In case the ACD value of a dial peer drops below the defined threshold the System will send an appropriate notification to the administrator.


Page 153 of 218

Parameter min_asr= user.cfg, gateway.cfg, meraproxy.cfg, section [Statistics]

Data type Integer

Valid values A positive integer within the 0 – 100 range

min_asr=<number>


Example min_asr=50

Explanation Use this field to enter an ASR value that will trigger bad ASR email alerts when reached.

The global ASR level is defined in the section [Statistics], the ASR level for individual RAS users and gateways is defined in user.cfg and gateway.cfg respectively. The emails will contain the name of the gateway or RAS user with a low ASR value.

Parameter min_asr= meraproxy.cfg, section [Media]

Data type Integer

Valid values An integer within the 0 – 100 range

min_asr=<number>

Default value 0 (disengages ASR dependent blocking of the media server)

Example min_asr=50

Explanation Set the minimum ASR level for the media server. When the configured value is reached, the media server will be blocked for the period of time specified in the suspend_time= field. The system checks ASR level when the number of calls, handled by the media server exceeds the number specified in the call_radix= field.

Note: The parameter is applicable in MVTS cluster versions only.

Parameter min_asr= dialpeer.cfg

Data type Integer

Valid values A positive integer within the 0 – 100 range

min_asr=<number>

Default value 0

Example min_asr=20

Explanation Set the minimum ASR level for a dial peer. In case the ASR value of a dial peer drops below the defined threshold the System will send an appropriate notification to the administrator.


Page 154 of 218

Parameter min_asr_mode= meraproxy.cfg, section [Statistics]

Data type Boolean

Valid values 0 – MERA’s proprietary ASR

1 – standard ASR

min_asr_mode=<number>

Default value 0

Example min_asr_mode=1

Explanation Use the parameter to define an ASR assessment method (conventional or the MVTS intrinsic) to be used for generation of the list of low-ASR gateways. (low-ASR gateways are the gateways with ASR below the value specified in the min_asr= field of the section [Statistics] of meraproxy.cfg).

Parameter min_call_bandwidth= meraproxy.cfg, section [Gatekeeper]

Data type Integer

Valid values Positive numbers min_call_bandwidth=<number>

Default value

Example

Explanation Set the minimum bandwidth of the MVTS gatekeeper. The parameter value is included into the RegistrationConfirm packet. Mandatory for several types of gateways.

Parameter min_call_duration= meraproxy.cfg, section [Administration]

Data type Integer

Valid values A positive integer in the 10 – 999 range representing the time rounding point

min_call_duration=<integer>

Default value 500

Example min_call_duration=300

Explanation This parameter serves to set a rounding point for the fractional part of call duration time. Setting the parameter to, say, 200 (min_call_duration=200) means that a call with the 45.19 seconds duration will be registered as the call that lasted exactly 45 seconds, while the duration of a 45.21 seconds call will be rounded off to 46 seconds.


Page 155 of 218

Parameter mode= meraproxy.cfg, section [Media]

Data type Boolean

Valid values 0 does not allow the MVTS to route the call to the terminator if no media server is available.

1 makes the MVTS route the call to the terminator specified in the system configuration.

mode=<number>

Default value 0

Example mode=1

Explanation Use this field to define a call termination method.

Parameter min_scd= meraproxy.cfg, section [Statistics], gateway.cfg, user.cfg

Data type Integer

Valid values Positive integers representing SCD minimum value (in seconds)

min_scd=<number>

Default value -1

Example min_scd=1

Explanation Use the field to define an SCD minimum (in seconds) for gateways (in gateway.cfg), RAS users (in user.cfg) and system-wide (in the section [Statistics], meraproxy.cfg). The system reports a list of low SCD endpoints (RAS users and gateways) to the address, specified in asr_email_alert=.


Page 156 of 218

Parameter min_scd= dialpeer.cfg

Data type Integer

Valid values Positive integers representing SCD minimum value (in seconds)

min_scd=<number>

Default value

Example min_scd=1

Explanation Use the field to set the minimum acceptable SCD in seconds. In case the SCD value of a dial peer drops below the defined value the system will send an appropriate notification to the administrator.

Parameter min_success_duration= gateway.cfg, user.cfg

Data type Integer

Valid values Positive numbers min_success_duration=<number>

Default value 0

Example min_success_duration=5000

Explanation Use the parameter to set the minimum call duration time (in milliseconds) for static and dynamic users. The number of milliseconds will always be rounded up.

Parameter mult_group= meraproxy.cfg, section [Gatekeeper]


Valid values IP address in the oct.oct.oct.oct format

mult_group=<address>


Example mult_group=224.0.135.17

Explanation Use this parameter to specify the gatekeeper’s address for RAS multicasting.


Page 157 of 218

Parameter mult_port= meraproxy.cfg, section [Gatekeeper]


Valid values Port number mult_port=<number>

Default value 1718

Example mult_port=1770

Explanation Use this parameter to specify a port for RAS multicasting.


Page 158 of 218

N Parameter nas_port_name= user.cfg, gateway.cfg


Valid values

Default value

Example nas-port_name=vendor1

Explanation The string defined in this parameter is inserted into the VSA field CISCO_NAS_PORT of the Stop-Accounting packets. The parameter is valid only when the parameter “f o r c e _ o r i g i n a t e _ t e l e p h o n y = ” is set to “1”.


Page 159 of 218

Parameter nat_call_port= user.cfg

Data type Integer

Valid values A positive integer denoting a port number (if not specified the MVTS sends Setup to the address specified in the RegistrationRequest.

nat_call_port=<number>

Default value 0

Example nat_call_port=10721

Explanation This parameter is a solution to the one-way calls problem for registering endpoints (RAS users) sitting behind a NAT router with fixed port mapping. Suppose there are 10 registering endpoints located downstream of a NAT router with external address 1.1.1.1. The local IPs of the endpoints user1, user2 … user10 listening to signaling traffic at port 1720 are 192.168.1.1, 192.168.1.2 … … 192.168.1.10 respectively. The NAT router port mapping table is as follows:

External port Local IP:port

10720 192.168.1.1:1720 10721 192.168.1.2:1720 ... ... ... ... ... ... 10729 192.168.1.10:1720

Since TCP connect forwarding is carried out in accordance with the port mapping table, ONLY outward calls will be possible from behind the NAT router unless you specify the external port number in the nat_call_port= parameter of a RAS user to enable termination of incoming calls too. For example:

[user1] # internal address 192.168.1.1 user= password= nat_call_port=10720 [user2] # internal address 192.168.1.2 user= password= nat_call_port=10721 ... ... [user10] # internal address 192.168.1.10 user= password= nat_call_port=10729


Page 160 of 218

Parameter nat_call_port_type= user.cfg

Data type Boolean

Valid values 0 – the MVTS extracts the number of the signaling port from the Registration Request packet header.

1 - the MVTS extracts the number of the signaling port from the callSignalAddress field of the Registration Request.

Default value 0

Example nat_call_port_type=0

Explanation Use this parameter to configure the MVTS to take the signaling port number of an endpoint sitting behind a NAT router from the Registration Request packet header or from the callSignalAddress field of the RRQ.

Parameter nat_rtp= usr.cfg; gateway.cfg

Data type Boolean

Valid values 0 disables NAT traversal

1 enables NAT traversal (the MVTS sends RTP packets to the address from which the packets actually arrive rather than to the address advised by the gateway during the H.245 session).

nat_rtp=<number>

Default value 0

Example nat_rtp=1

Explanation This is an RTP-packet forwarding flag. Use this parameter to enable NAT traversal when the destination gateway is behind a NAT router. This field is optional.


Page 161 of 218

Parameter no_connect_suspend_time= meraproxy.cfg, section [Media]

Data type Integer

Valid values

A positive integer representing the time-out period

no_connect_suspend_time=<number>

Default value

Example no_connect_suspend_time=5

Explanation Set the media MVTS time-out period in case there is no TCP connection with the server.

Parameter no_empty= meraproxy.cfg, section [Billing]; section [Debug], section [Statistics]

Data type Boolean

Valid values 0 – allow empty files

1 – disallow empty files

no_empty=<number>

Default value 1

Example no_empty=1

Explanation This is a “no-empty-files” flag. When you set the flag (no_empty=1) the proxy-server leaves no empty billing files [Billing], statistic records [Statistics] or debug logs [Debug].

Parameter no_faststart= user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – removal disallowed

1 – removal allowed

no_faststart=<number>

Default value 0

Example no_faststart=1

Explanation Allow/disallow removal of the fastStart field from Setup.



Page 162 of 218

Parameter no_packet_q931_cause= user.cfg; gateway.cfg

Data type Integer

Valid values

Q931 disconnect cause code no_packet_q931_cause=<number>

Default value

0

Example no_packet_q931_cause=

Explanation Use this parameter to enter a Q931 call disconnect reason value that will appear in CDRs when the call is aborted upon expiry of the configured no-packet-to-originator timeout (see no_packet_timeout=)

Parameter no_packet_timeout= user.cfg; gateway.cfg

Data type Integer

Valid values Positive integers representing the timeout in milliseconds

no_packet_timeout=<number>

Default value 0

Example no_packet_timeout=

Explanation Use this parameter to configure the length of the wait period within which the dispatch of a packet to the originator is expected. If the configured timeout expires and no packet went to the originator the call is aborted with LDC 131 (eNoPacketTimeout) and Q931 cause 34 or the Q931 cause value configured in no_packet_q931_cause=

Parameter no_port_clean= user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – allows port release

1 – prevents port release

no_port_clean=<number>

Default value 0

Example no_port_clean=1

Explanation Use this flag to control the port clearing process. The parameter may come in handy when the gateway despite a change in the operating mode (switching to fax, for example) persists in sending RTP-packets to the old ports which according to the H.323 standard should be released (such operating peculiarity was observed in MediaRing gateways, for instance).


Page 163 of 218

Parameter no_tunnelling= user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – leave the value of the H245Tunnelling field in SETUP unchanged

1 – change the value of the H245Tunnelling field in SETUP to “false”

no_tunnelling=<number>

Default value 0

Example no_tunnelling=1

Explanation Control the value of the H245Tunnelling field of Setup.


Parameter number= user.cfg; gateway.cfg

Data type Integer

Valid values Digital characters number=<string>


Example number=78312775825

Explanation Use this parameter to specify the gateway’s phone number. You must not use regular expressions in this instance as the parameter provides an argument for the exact match search in the dialpeer.cfg file for a dial peer pointing to the ENDPOINTS macroname.

Example:

[DIRECTNUMBERS] dst_pattern=[0-9]*

priority=1000

gateway=ENDPOINTS


Page 164 of 218

Parameter numbering_plan= user.cfg; gateway.cfg

Data type Integer

Valid values Decimal representation of the type:plan parameter

numbering_plan=<number>

Default value 0

Example numbering_plan=33

Explanation Use this field to configure the type:plan parameter for the gateway. The numbering_plan= setting is optional


According to ITU-T Recommendation Q931 (called party number Information Element) the type element 'International number' (bits 7 6 5) is 0 0 1 and the plan element 'ISDN/telephony numbering plan' (bits 4 3 2 1) is 0 0 0 1. Therefore, set numbering_plan=33 (33 is decimal representation of the binary number 0 0 1 0 0 0 1).




Page 165 of 218

O Parameter offset_period= meraproxy.cfg, section [Billing], section

[Debug]

Data type Integer

Valid values Time in the [[<hours>:] minutes:] notation

offset_period=<time>

Default value 02:00

Example offset_period=02:00

Explanation Use this parameter to specify an offset for the the file rotation time set in the period= field. The offset value should not exceed the setting in the period= field, otherwise the system will ignore the offset parameter altogether.

Note: with period=24:00 and offset_period=02:00 the log file rotation time will shift from midnight to 2 a.m.

Parameter only_first_gateway= dialpeer.cfg

Data type Boolean

Valid values 0 – the MVTS will try to terminate the call through all the gateways (in the order in which they appear on the list) present in the gateway= field of the dialpeer

1 – the MVTS will use only the first gateway on the list for call termination

only_first_gateway=<number>

Default value

Example only_first_gateway=0

Explanation

This parameter allows you to control how many gateways of those specified in the field gateway= of the dial peer record will be used for call termination. With only_first_gateway=0 the MVTS tries all the gateways specified in the field gateway= successively (the order in which the MVTS selects gateways for call termination is not necessarily the order in which they appear in the gateway= field. For example, the order may be different if the dial peer record includes a configured parameter hunt_mode=.) With only_first_gateway=1 the MVTS uses only the first gateway in the list.


Page 166 of 218

Parameter options= gatekeeper.cfg

Data type Boolean

Valid values 0 – disable translation

1 – enable translation

options=<number>

Default value 0

Example options=1

Explanation With options=1, for example, if an ARQ contains a destination number other than the number returned by the gatekeeper in the ACF (Admission Confirm), the MVTS will send the terminator a SETUP containing the destination number received from the gatekeeper.

Parameter override_proxy_mode= dialpeer.cfg

Data type Integer

Valid values

0 – signaling traffic proxying only

1 – signaling and media traffic proxying (full proxy mode)

2 – the proxy mode of the calling party

3 – the proxy mode of the called party

override_proxy_mode=<number>

Default value

-1

Example override_proxy_mode=2

Explanation Use this parameter to override the global proxy mode settings. The mode setting will apply only to the dial peer whose record contains this parameter. This parameter is optional.


Page 167 of 218

Parameter override_user= dialpeer.cfg


Valid values Arbitrary character string override_user=<string>

Default value

Example override_user=OtherUser

Explanation

Use this parameter to perform a user name (parameter gateway=) substitution when the need to do an authorized call termination under some other user’s name arises.


Page 168 of 218

P Parameter password= user.cfg; gateway.cfg; gatekeeper.cfg



password=<character string>


Example password=Key0598E

Explanation Use this parameter to specify the user password. The password is used in the system together with the user name for authorization purposes. The password= field found in a RAS user record (file user.cfg) may also contain the metasymbol ‘*’ as its parameter. With the password=* setting, the user password will be extracted from the registration query and forwarded to the RADIUS server unchanged. Use of the ‘*’ metasymbol frees you from the need to specify the passwords of RAS users in the user.cfg file. This mode of operation is possible with the logins of the <user|password> type, though. This field is mandatory.

Parameter pass_display_ie= user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – allow removal of the Display information element 1 – disallow removal of the Display information element

pass_display_ie=<number>

Default value 0

Example pass_display_ie=1

Explanation

Allow/disallow removal of the ‘display’ Information Element from packets sent to the static gateway/RAS user.


Page 169 of 218

Parameter period= meraproxy.cfg, section [Billing]; section [Debug], section [Statistics]

Data type Integer

Valid values A period of time in the [[<hours>:] minutes:] seconds notation.

period=[[<hours>:] minutes:] seconds

Default value 120:00

Example period=120:40

Explanation Use the parameter to set file rotation time for CDR files [Billing]; debug logs [Debug] and statistical data files [Statistics].

Note: If you plan to express the file rotation period in hours, the appropriate value is an exact divisor of 24 or an exact divisor of 60 if your file rotation frequency estimate is in minutes. Configuring a file rotation period in seconds is unadvisable as creation of a large quantity of files may result in the file system overflow.

Note: If this parameter is set to less than 60 seconds, it is automatically reset to 60 seconds.

Parameter port= meraproxy.cfg, section [H323]

Data type Integer

Valid values Port number port=<number>

Default value 1720

Example port=1770

Explanation Set other than default port 1720 for H.323 signaling. Leave default port 1720 unchanged if you have no port assignment conflicts.

Parameter port= gateway.cfg

Data type Integer


Default value

Example port=1770

Explanation Specify the gateway port for signaling traffic.


Page 170 of 218

Parameter port= gatekeeper.cfg



Default value 1719

Example port=1770

Explanation Set other than default port (1719) for receipt of RAS traffic.

Parameter ports_range= meraproxy.cfg, section [Administration]


Valid values Port number ports_range=<number>

Default value

Example ports_range=20000-30000;40000-50000

Explanation The parameter serves to define ranges of ports for signaling and media traffic. List entries are delimited by semicolons.

If the range of ports is defined and all ports within the range are busy MVTS rejects calls with LDC 402 ‘NoAvailablePorts’.

Parameter prefixes= gatekeeper.cfg


Valid values Gateway prefixes or E.164 aliases

prefixes = <list>

Default value

Example prefixes=789#;889#;775#

Explanation Use this parameter to specify a list of the gateway prefixes, transmitted to the gatekeeper (when the make-believe flag is reset, i.e. terminal=0) or the list of E.164 aliases (when terminal=1). The list elements must be delimited by a semicolon ‘;’ or a comma ‘,’.


Page 171 of 218

Parameter presentation_screening_allowed= user.cfg; gateway.cfg

Data type Boolean

Valid values

0 –disallows the use of the parameters

1 – allows the use of the parameters

presentation_screening_allowed=

<number>

Default value

0

Example presentation_screening_allowed=1

Explanation Normally the MVTS removes the fields Presentation and Screening from transferred packets. To prevent removal of these fields and enable the use of the presentation= and screening= configuration parameters set this flag (i.e. presentation_screening_allowed=1).


Parameter presentation= user.cfg; gateway.cfg

Data type Integer

Valid values -1 means ‘do not change the received value’

0 means ‘presentation allowed’

1 means ‘presentation restricted’

2 means ‘number not available due to interworking’

3 is reserved

presentation=<number>

Default value -1

Example presentation=1

Explanation Use this parameter to specify the value of the field presentationIndicator in SETUP.

Note: this parameter is valid in configuration of termination endpoints only.


Page 172 of 218

Parameter priority= meraproxy.cfg, section [Administration]

Data type Integer

Valid values priority=<integer>

Default value

Example priority=2

Explanation The value of this field is sent to an external routing server and does not affect the MVTS operation. The field is optional.

Parameter priority= dialpeer.cfg

Data type Integer

Valid values An integer in the 0 – 65535 range

priority=<number>

Default value 1

Example priority=4

Explanation Use this parameter to specify the dial peer precedence. The precedence value permits selection of a dial peer from a set of appropriate ones. A greater value means bigger precedence. This field is optional.


Page 173 of 218

proxy_type= Parameter user.cfg; gateway.cfg

Data type Boolean

Valid values 0 – signaling traffic proxying only

1 – full traffic proxying

proxy_type=<attribute>

Default value 1

Example proxy_type=0

Explanation Use this parameter to define the proxy mode attribute for the gateway traffic.

Signaling traffic proxying is used for gateways that belong to the same net, while full proxy operation (i.e. signaling and media) is for gateways residing on different networks. If two communicating gateways have different proxy modes the strictest one is used, i.e. full proxying.

Parameter public_access= meraproxy.cfg, section [Administration]

Data type Boolean

Valid values 0 , 1 public_access=<number>

Default value 0

Example public_access=0

Explanation Use this parameter to disable/enable IP address-based authorization of gateways. Setting the flag to 1 means that the MVTS will accept calls from any IP address but will process only those coming from the gateways present in the MVTS configuration or with the CallId identical to the one received by the MVTS in an LRQ packet.

Note: the customers who operate the MVTS with the setting public_access=1 are advised to add to the MVTS configuration a dummy, that is an imaginary gateway with any IP address in the field address= and mask= 0.0.0.0. This will allow the MVTS to accept calls from any IP address.

Warning: setting the parameter lrq_allowed_only= to 1 and public_access= to 1 increases the chances of a successful DoS attack against the MVTS signaling port.


Page 174 of 218

Q Parameter q931_cause= dialpeer.cfg

Data type Integer

Valid values A positive integer within the 0-127 range

q931_cause=<number>

Default value -1

Example q931_cause=0

Explanation Use this parameter to specify the Q931 call termination causes for the dial peers with the gateway=NULL setting in the record. For example, you may wish to specify call termination cause = 1 for the calls that match none of the existing dial peers due to a wrong number.

Note: the parameter will function even if the dialpeer search stopped with hunt_stop=1 .

Parameter q931_cause_mode= meraproxy.cfg, section [H323]

Data type Boolean

Valid values 0 – the origination gateway is sent the disconnect cause code as defined in the parameter “q931_cause=” (dialpeer.cfg) of the dial peer with “gateway=NULL” or “hunt_stop=1”

1 – the origination device is sent the disconnect cause code received during the last but one routing attempt, i.e. the attempt preceding the effect of the parameter “gateway=NULL” or “hunt_stop=1”.

q931_cause_mode=<number>

Default value 0

Example q931_cause_mode=1

Explanation The parameter serves to determine the Q.931 cause code sent to the origination gateway upon completion of the call owing to setting the parameter “gateway=” (dialpeer.cfg) to “NULL” or setting the parameter “hunt_stop=” to “1”.


Page 175 of 218

Parameter q931_cause_override= meraproxy.cfg, section [H323]; gateway.cfg; user.cfg

Data type Integer

Valid values

Pair of integers delimited with a dash q931_cause_override=<code1-code2>;<code3-code4>

Default value

Example q931_cause_override=31-16

Explanation The parameter allows substitution of Q.931 cause codes.

Parameter q931_h323_disconnect_cause= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values

0 disables Q931 cause substitution

1 enables Q931 cause substitution

q931_h323_disconnect_cause=

<number>

Default value

0

Example q931_h323_disconnect_cause=1

Explanation Use this parameter to enable/disable substitution of the AccessReject value received from the Radius server in the field CISCO VSA(30) h323-disconnect-cause for the actual Q931 disconnect cause, since in case of a rejection from the RADIUS server the Q931 cause is always set to 3 (destination unreachable).

WARNING! Use of this substitution function should be judicious; since the Q931 cause value is also present in the Release-Complete packet and according to the developer’s experience, some gateways cannot digest uncommon Release-Complete values and hang.


Page 176 of 218

R Parameter radius_gw_id= user.cfg; gateway.cfg


Valid values An arbitrary string of characters radius_gw_id=<string>


Example radius_gw_id=DistantGate

Explanation

Use this parameter to set the h323_gw_id= and h323-remote-id RADIUS VSA fields for the originating and termination gateways respectively. When the radius_gw_id= is not determined then the h323_gw_id= and h323_remote_id= parameters assume the IP-addresses of respective gateways.

Parameter radius_remote_address= user.cfg; gateway.cfg

Data type Boolean

Valid values

0 – disables substitution of the gatekeeper IP address for the address of the remote gateway in the h323_remote_address and

h323_remote _id messages.

1 – enables substitution of the gatekeeper IP address for the remote gateway IP in the h323-remote-address and h323-remote-id messages

radius_remote_address=<number>

Default value

0

Example radius_remote_address=1

Explanation Use this parameter to enable IP-address substitution. When the flag is set (1) the IP-address of the gatekeeper is substituted for the remote gateway IP-address in the h323-remote-address and h323-remote-id messages sent to the RADIUS server, otherwise (the flag is reset to 0) the messages contain the IP-address of the remote gateway.

Note: the parameter is used in configuration of termination endpoints only.


Page 177 of 218

Parameter radius_uses_callid= user.cfg; gateway.cfg

Data type Boolean

Valid values 0 disables call ID substitution.

(conference identifier is used in messages h323_incoming_conf_id and h323_conf_id sent to the RADIUS server)

1 enables call ID substitution, provided the call_id parameter is not void.

radius_uses_callid=<number>

Default value 0

Example radius_uses_callid=1

Explanation Accounting and billing systems may use conference ID for call identification purposes. This can cause problems with certain gateways (for example, VocalTec gateways may generate identical conference IDs for a number of individual calls). The radius_uses_callid= flag was introduced as a solution to such problems. When the flag is reset (0) the conference identifier is used in messages h323-incoming-conf-id and h323-conf-id sent to the RADIUS server. Setting the flag (1) causes substitution of the call ID for the conference ID in the said messages, provided the call_ID= parameter is not void.



Page 178 of 218

Parameter random_value= dialpeer.cfg


Valid values Random value intervals

random_value=<min1>-<max1>;<min2>-<max2>...

Default value

Example random_value=1-2999;7100-7299

Explanation The value of this parameter is an interval or a set of intervals. Each of these intervals is limited by the minimum and the maximum value. If an interval has only one value, or its minimum value equals or is greater than its maximum value, then it is considered that the interval consists of one value only.

The value randomly selected from the random_value= field can be inserted into any number translation parameter with the aid of the $rnd$ macros.

Example:

[test_dp]

random_value=1-2999;7100-7299 src_translate=7095123|[0-9]{4}/\1$rnd$ ...

The MVTS replaces the $rnd$ macros in the dial string with the values randomly selected from the random_value= field in the following way:

First the MVTS randomly selects one of the intervals (if there are two or more of them), defined in random_value= and then it selects a random value from the chosen interval. If the digit capacity of the maximum value of the interval is different from that of the minimum value of the same interval, the MVTS adds zeros to the left side of the inserted value till it reaches the digit capacity of the maximum value. Thus, if interval 0 – 999 is defined, the numbers in the 000 – 999 range will be inserted into the number translation parameter in place of the $rnd$ macros.

According to the above-cited example, after the number translation we get the ANI number ranging from 70951230001 to 70951232999 and from 70951237100 to 70951237299.

Note: the minimum and maximum values limiting the interval must never exceed 999999999.


Page 179 of 218

Parameter ras_port= meraproxy.cfg, section [Gatekeeper]


Valid values Port number ras_port=<number>

Default value 1719

Example ras_port=1721

Explanation Use this parameter to specify the gatekeeper port number for RAS registration. Leave the default value 1719 unchanged if you have no port allocation conflicts.

Parameter rbt_timeout= gateway.cfg, user.cfg

Data type Integer

Valid values A positive integer representing wait time

rbt_timeout=<number>

Default value 0 (the function is disabled)

Example rbt_timeout=10

Explanation Use this parameter to set the maximum wait time for Alert and/or ProgressIndicator packets from the termination gateway (in seconds). The parameter is intended for fine tuning of the system operation.

We recommend that you use this parameter very carefully paying special attention to how it correlates with the values of the validation_gap= and validation_msg= fields!

For example, with the settings validation_gap=10000 , validation_msg=7 (i.e. suspended exchange between the gateways will be resumed in 10 seconds or upon arrival of the Connect message, whichever occurs first) and the rbt_timeout set to 9 sec. (rbt_timeout=9) , in absence of the Connect within the 9 seconds time after sending Setup the call will be terminated with the eRBTTimeout cause.



Page 180 of 218

Parameter read_route_table= meraproxy.cfg, section [Proxy]

Data type Boolean

Valid values 0 disables table reading. The routing path in this case needs to be entered manually in the alias_route_path=

field

1 enables table reading by the OS kernel.

read_route_table=<number>

Default value 1

Example read_route_table=0

Explanation Use this flag to control the routing table reading by the OS kernel. When set (1) the kernel reads the routing table.


Page 181 of 218

Parameter redundancy_type= meraproxy.cfg, section [Redundancy]

Data type Integer

Valid values 0 – redundancy disabled

1 – gatekeeper – RAS user redundancy scheme

2 – shared IP redundancy scheme

3 – single-license load sharing redundancy scheme

4 – regular redundancy scheme

redundancy_type=<number>

Default value 0 – failover/failback mechanism disabled

Example redundancy_type=1

Explanation Use the field to determine the type of the MVTS failover/failback mechanism employed in case of the main server failure.

If you choose to implement the ‘Gatekeeper – RAS-user’ redundancy scenario, please remember that this failover method requires configuration of the section [Redundancy] on the MVTS backup host only. Example of the configured section [Redundancy] follows: meraproxy.cfg

....

[Redundancy]

redundancy_type=1

master_gatekeeper=<master mvts>

where <master mvts> is the name of the gatekeeper section configured in gatekeeper.cfg of the failover server.

The remaining three redundadcy layouts need to be configured both on the primary and backup hosts.

Note: changing the redundancy type requires restart of both the instances of the MVTS application – running on the primary and standby computer.

Parameter reg_address= user.cfg


Valid values A positive integer in the oct.oct.oct.oct. format

reg_address=oct.oct.oct.oct.

Default value

Example reg_address=195.128.97.20

Explanation Use this parameter to specify the IP address of the RAS user.


Page 182 of 218

Parameter reg_h323_id= user.cfg

Data type String

Valid values Character string representing a RAS user identifier

reg_h323_id=<string>

Default value

Example reg_h323_id=

Explanation The parameter allows additional verification of a registration request arriving from the IP address specified in the parameter reg_address=. The registration is verified by the content of the field H323_ID in the RegistrationRequest message sent to the MVTS by the registering entity. Verification is successful when the content of the H323_ID field coincides with the value of the parameter reg_h323_id=.

By this means if the configuration of a registering entity includes both the parameter reg_address= and the parameter reg_h323_id= the MVTS will allow registration of the endpoint only when the IP address and H323 ID of the registering point match the values of the respective parameters.

Note: the parameter reg_h323_id= can be used only when reg_address= is defined.

Parameter reset_active_time_period= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values Time interval in the following format: [[[hh:]mm:]ss], where hh is hours, mm – minutes and ss – seconds.

Default value 00:00:00

Example reset_active_time_period=12:00:00

(quantity statistics for the traffic processed by RAS users and gateways registered with the MVTS will be reset every 12 hours)

Explanation The parameter defines the reset interval for quantity statistics about traffic processed by RAS users and gateways registered with the MVTS.


Page 183 of 218

Parameter reset_after_save= meraproxy.cfg, section [Statistics]

Data type Boolean

Valid values 0 – disables data clearing after saving (preserves the statistics even after writing it to the file).

1 – enables data clearing after saving

reset_after_save=<number>

Default value 0

Example reset_after_save=1

Explanation Allow/disallow statistics data clearing after saving it to a file.

Parameter reset_can_overlap_send= gateway.cfg, user.cfg

Data type Boolean

Valid values 0 - serves to disable the function and leave canOverlapSend unchanged

1 – makes the MVTS forcefully set canOverlapSend to “false”

reset_can_overlap_send=<number>

Default value 0

Example reset_can_overlap_send=1

Explanation Use this parameter to let the canOverlapSend field of SETUP stay set or have the MVTS reset it (some H.323 gateways may malfunction when the canOverlapSend field value is true).


Parameter route_address= meraproxy.cfg, section [Radius] and [BackupRadius]


Valid values IP address in the oct.oct.oct.oct notation.

route_address=oct.oct.oct.oct

Default value

Example route_address=195.88.97.20

Explanation Use this parameter to specify an IP address of a RADIUS server used for call routing.


Page 184 of 218

Parameter route_backup= meraproxy.cfg, sections [Radius]

Data type Boolean

Valid values 0 – the AccessRequest with a routing request is sent to the primary RADIUS server only

1 – the AccessRequest with a routing request is sent both to the primary and backup RADIUS server

route_backup=<1/0>

Default value 0

Example route_backup=1

Explanation The parameter serves to enable/disable sending spare ARQs to an external routing server.

Parameter route_enable= meraproxy.cfg, sections [Radius], [BackupRadius]

Data type Boolean

Valid values 0 – disable RADIUS-aided routing

1 – enable RADIUS-aided routing

route_enable=<number>

Default value 0

Example route_enable=1

Explanation Use this parameter to enable/disable external routing provided by the RADIUS server.

Parameter route_port= meraproxy.cfg, sections [Radius], [BackupRadius]

Data type Integer

Valid values Port number route_port=<number>

Default value The port number specified in the auth_port= field

Example route_port=1798

Explanation Use this parameter to specify a port number for routing exchange in addition to the value of route_address=.


Page 185 of 218

Parameter repeat_quantity= meraproxy.cfg, sections [Radius] and [BackupRadius]

Data type Integer

Valid values A positive integer within the 1 – 9 range representing the number of attempts

repeat_quantity=<number>

Default value 5

Example repeat_quantity=7

Explanation Use this parameter to specify the number of send attempts for the packets destined for the RADIUS server.

Parameter repeat_time= meraproxy.cfg, sections [Radius] and [BackupRadius]

Data type Integer

Valid values A positive integer within the 1 - 9 range representing a time interval

repeat_time=<number>

Default value 3

Example repeat_time=8

Explanation Use this parameter to set the duration of the pause (in seconds) between two consecutive send attempts.

Parameter route_cause= meraproxy.cfg section [LAR], user.cfg; gateway.cfg

Data type Integer

Valid values A decimal number representing the call rejection cause invoking the look-ahead routing function.

route_cause = <number>

Default value 0 (call rerouting disabled)

Example route_cause=0-16;18-127

Explanation Use this parameter to specify call termination reasons that invoke LAR function (i.e. attempts to reroute the call). The elements of a list must be delimited with a semicolon ‘;’. route_cause=0-127 means that any reason causes further routing attempts.

Note: In this particular case when the termination gateway responds with the ReleaseComplete code 17 (“line busy”) there will be no further rerouting attempts.



Page 186 of 218

Parameter route_server_address= meraproxy.cfg, section [Administration]


Valid values IP address in common dot-separated format

Default value

Example route_server_address=

Explanation This is a configuration parameter of Media MVTS, which is a part of the MVTS cluster system. Use this parameter to define the IP address of a routing server.

Parameter route_statistics_enable= m e r a p r o x y . c f g , section [Statistics]

Data type Boolean

Valid values

0 – statistics keeping disabled

1 – statistics keeping enabled

route_statistics_enable= <integer>

Default value

0

Example route_statistics_enable=1

Explanation Use this parameter to enable/disable collection of statistics for routes.

Parameter rtp_threads= meraproxy.cfg, section [Administration]

Data type Integer

Valid values A positive integer, representing the number of threads

rtp_threads=<number>

Default value 5

Example rtp_threads=3

Explanation This parameter defines the number of threads allocated for media traffic. The parameter default setting is the recommended value.


Page 187 of 218

Parameter rrq_full_reg_interval= meraproxy.cfg, section [Gatekeeper]

Data type Integer

Valid values Time in the HH:MM:SS format rrq_full_reg_interval=<time>

Default value

0 (function disabled)

Example rrq_full_reg_interval=24:00:00

Explanation Use this parameter to specify a registration update period for all RAS entities registered with the MVTS GK.


Page 188 of 218

S

Parameter screening= gateway.cfg, user.cfg

Data type Integer

Valid values -1 means ‘leave provided value unchanged’

0 means ‘user provided, not changed’

1 means ‘user provided, verified and passed’

2 means ‘user provided, verified and failed’

3 means ‘network provided’

screening=<number>

Default value -1

Example screening=2

Explanation

Use this parameter to specify the value of the screeningIndicator= parameter.

This parameter is used to ensure compatibility with PSTN gateways.

Note: the parameter is used in configuration of termination endpoints only.

Parameter secret= meraproxy.cfg, sections [Radius] and [BackupRadius]


Valid values Arbitrary string of characters representing the coding key

secret=<string>

Default value

Example secret=strongsecret

Explanation Use this parameter to specify the coding key (according to the 'shared secret' standard) for communications with the RADIUS server. The field is mandatory.


Page 189 of 218

Parameter security= gatekeeper.cfg

Data type Integer

Valid values 0 - the source_alias=user|password" method of generating the registration parameter

1 – VocalTec

2 – CISCO

3 – CHAP

security= <number>

Default value 0

Example security=3

Explanation Use this parameter to select the gatekeeper authorization method.

Parameter send_route_request_only= meraproxy.cfg, sections [Radius] and [BackupRadius]

Data type Boolean

Valid values

0 (default) allows sending call authorization requests

1 disallows sending call authorization requests

send_route_request_only=<boolean>

Default value

0

Example send_route_request_only=0

Explanation The parameter serves to allow/disallow sending call authorization requests to the external routing system used for call routing.


Page 190 of 218

Parameter session_id_type= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 assigns the same sessionID to all packets forwarded to RADIUS within one call session

1 enables random assignment of the sessionID to the packets forwarded to RADIUS within one call session

session_id_type=<number>

Default value 0

Example session_id_type=1

Explanation Use the parameter to select the type of sessionID field in the packets sent to RADIUS. The value of the sessionID field varies within the 0 – 256 range.

If session_id_type=1 each packet sent to the RADIUS server during one call session is subject to random allocation of sessionID, in which case for example Accounting Stop Request may arrive before the corresponding Accounting Start Request.

If session_id_type=0 all the packets sent to RADIUS during one specific call session have identical sessionID, which allows to avoid confusion when the packets are being delivered.

Parameter set_H225_version= gateway.cfg, user.cfg

Data type Integer

Valid values 0, 1, 2, 3, 4 set_H225_version=<number>

Default value 0 (no version substitution)

Example set_H225_version=4

Explanation Use this parameter to configure what H323 protocol version should be substituted in the protocolIdentifier parameter of H.225.0 messages


Page 191 of 218

Parameter set_route_acd= dialpeer.cfg

Data type Integer

Valid values 1 – 10 000 set_route_acd=<number>

Default value 0

Example set_route_acd=100

Explanation Set the lowest ACD level that will block routes the ACD of which drops below the set value. The smart routing function has to be enabled (the smart_routing= field in the section [Statistics] of meraproxy.cfg is set to 1).

Parameter set_route_asr= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values A positive integer in the 1 – 100 range representing the lowest acceptable ASR level

set_route_asr=<number>

Default value -1 – (ASR is not used for smart routing)

Example set_route_asr=15

Explanation Use this parameter to set a minimum acceptable ASR for routes. If the value of this field comes into contradiction with the set_route_asr= value in the configuration of an individual dialpeer, the dialpeer ASR will prevail.

Parameter set_route_asr= dialpeer.cfg

Data type Integer

Valid values An integer in the -1 – 100 range representing the minimum ASR level

set_route_asr=<number>

Default value -1 (ASR value is not used for smart routing)

Example set_route_asr=15

Explanation Use this parameter to set a minimum ASR value for individual dialpeers. The value of this field overrides the setting of the identical global parameter found in the section [Statistics] of meraproxy.cfg. The smart routing function must be enabled.


Page 192 of 218

Parameter set_route_asr_mode= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values 0 enables use of MERA’s proprietary ASR assessment method (successful calls/attempted calls*100%)

1 enables use of the standard ASR calculating method

set_route_asr_mode=<number>

Default value 0

Example set_route_asr_mode=1

Explanation Define the method of calculating ASR (Answer Seizure Ratio) when smart routing is enabled.

Parameter siphit_dst_codec= gateway.cfg, user.cfg


Valid values Codec mnemonics siphit_dst_codec=<codec>;<codec>…


Example siphit_dst_codec= iLBC13k3;iLBC15k2;speex

Explanation Use this parameter to specify a list of codecs that the MVTS sends the SIPHIT module to enable a session with the termination endpoint. Delimit the list elements with semicolons. You can add codecs using codec names as established for the fields codec_allow= and codec_deny=. Additionally, you can use the iLBC13k3, iLBC15k2 and speex codec mnemonics in this field.

Parameter siphit_src_codec= gateway.cfg, user.cfg


Valid values Codec mnemonics siphit_src_codec=<string>;<string>…


Example siphit_src_codec= iLBC13k3;iLBC15k2;speex

Explanation Use this parameter to specify a list of codecs that the MVTS sends the SIPHIT module to enable a session with the origination endpoint. Delimit the list elements with semicolons. You can add codecs using codec names as established for the fields codec_allow= and codec_deny=. Additionally, you can use the iLBC13k3, iLBC15k2 and speex codec mnemonics in this field.


Page 193 of 218

Parameter smart_routing= meraproxy.cfg, section [Statistics]

Data type Boolean

Valid values 0 – smart routing disabled

1 – smart routing enabled

smart_routing=<number>

Default value 0

Example smart_routing=1

Explanation Use this parameter to enable/disable smart routing based on the statistics analysis. This function allows you to block low-ASR routes (routes with ASR value that has dropped below a threshold level) thus excluding them from the routing options for a certain period of time. Upon expiration of this period the route is temporarily unblocked and its current ASR level is evaluated. The evaluation of ASR is performed on the basis of a certain number of calls through this route. In case the ASR value is still below the threshold level, the route is blocked.

The period of time during which a low-ASR route is blocked is configured with the parameter suspend_time= the section [Statistics], the ASR threshold level is defined in set_route_asr= in the section [Statistics], the number of calls for evaluation of ASR of temporarily blocked routes is set in call_sampling_number= section [Statistics].

Parameter smart_routing_enable= user.cfg, gateway.cfg

Data type Boolean

Valid values 0 – disables smart routing

1 – enables smart routing

Default value 1

Example smart_routing_enable=0

Explanation Use the field to enable/disable smart routing for a given gateway (RAS user). The MVTS checks the state of the route (blocked/unblocked) only when smart_routing=1. That is why smart_routing_enable=1 is meaningless when smart_routing=0.


Page 194 of 218

Parameter signaling_proxy_address= meraproxy.cfg, section [Administration]


Valid values

signaling_proxy_address== < o c t . o ct . o c t . o c t >

Default value

Example signaling_proxy_address=199.99.99.99

Explanation This is a configuration parameter of Media MVTS, which is a part of the MVTS cluster system. Use the field to set the IP address of the signaling MVTS.

Parameter slave_address= meraproxy.cfg, section [Redundancy]


Valid values

slave_address=<oct.oct.oct.oct>

Default value

Example slave_address=192.168.1.2

Explanation Use the field to define an IP address to remotely disable the operating IP addresses on the standby MVTS from the principal MVTS over ssh


Page 195 of 218

Parameter slave_gatekeeper= gatekeeper.cfg


Valid values

Names of sections of the gatekeeper.cfg configuration file

slave_gatekeeper=<string>

Default value

Example slave_gatekeeper=GK_1;GK_2; GK_3

Explanation

This field, together with master_gatekeeper= serves to establish master-slave(s) relations between the gatekeepers the MVTS registers with.

Use this field in configuration of the master gatekeeper to specify a list of the names of the slave gatekeepers the MVTS will register with in case it loses registration with the master gatekeeper. The MVTS registers with the slave GKs one by one in the order as they appear on the list. Configuration example:

gatekeeper.cfg:

[master_gk]

address = 195.10.10.11

id = gk_11

type = 1

slave_gatekeeper=slave_gk

....

[slave_gk]

address = 195.10.10.12

id = gk_12

Explanation

This parameter when used together with master_gatekeeper= serves to provide resilience in gatekeeper services rendered to the MVTS.

Use this field in the configuration of primary gatekeeper to specify a list of alternate gatekeepers the MVTS will register to in case it loses registration with the master gatekeeper. The MVTS tries to register to alternate GKs exactly in the order they appear on the slave_gatekeeper= list. Configuration example:

gatekeeper.cfg:

[master_gk]

address = 195.10.10.11

id = gk_11

type = 1

slave_gatekeeper=GK_1; GK_2; GK_3

....

[GK_1]

address = 195.10.10.12

id = gk_12


Page 196 of 218

Parameter slave_gatekeeper= gatekeeper.cfg

type = 1

master_gatekeeper=master_gk

....

[GK_2]

address = 195.10.10.14

id = gk_13

type = 1


....

[GK_3]

address = 195.10.10.17

id = gk_14

type = 1


.... gateway.cfg:

[some_gw]

gatekeeper=master_gk

....

Parameter snmp_enable= meraproxy.cfg, section [SNMP]

Data type Boolean

Valid values 0 disables response

1 enables response snmp_enable= < n u mb e r >

Default value 0

Example snmp_enable=1

Explanation Use the parameter to enable/disable response to SNMP queries.


Page 197 of 218

Parameter src_bill_translate= dialpeer.cfg

Data type Character sting

Valid values

Regular expressions and data strings

dst_bill_translate = regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&] dst_translate = regexp1[|regexp2[|regexp3]]/[str][\1][str][\2][str][\3][str][&]

Default value

Empty string

Example

Explanation

Use this parameter to set the dst_number translation patterns for convenience of accounting.

Use the keyword empty when you need to denote an empty number in a translation pattern.

The list of the macronames that can be employed in all the translation fields (except the group_translate field) of the dialpeer.cfg file is as follows:

$ani$ - ANI number of the caller

$dnis$ - number of the called party

$bill_ani$ - ANI number for billing

$bill_dnis$ - number of the called party for the purposes of billing

$user$ - user name

$id$ – unique call identifier (extracted form a CDR record) in the following notation <MVTS start time stamp>#<call ordinal number>#

In general the translation syntax is the same as in case of dst_translate=

Note: When a dial peer record contains both the bill_translate and dst_bill_translate patterns the dst_number will be translated in accordance with the translation pattern of the dst_bill_translate= field.


Page 198 of 218

Parameter src_numbering_plan= gateway.cfg, user.cfg

Data type Integer

Valid values Decimal representation of the type:plan parameter

src_numbering_plan=<number>

Default value 0

Example src_numbering_plan=33

Explanation Use the field to configure the type:plan parameter for the calling gateway.


According to ITU-T Recommendation Q.931 (called party number Information Element) the type element 'International number' (bits 7 6 5) is 0 0 1 and the plan element 'ISDN/telephony numbering plan' (bits 4 3 2 1) is 0 0 0 1. Therefore, set numbering_plan=33 (33 is decimal representation of the binary number 0 0 1 0 0 0 1).

Note: The src_numbering_plan= and dst_numbering_plan= fields override the settings of the numbering_plan= parameter, which is effective only if src_numbering_plan=0 and dst_numbering_plan=0.



Parameter src_presentation= gateway.cfg, user.cfg

Data type Integer

Valid values -1 means ‘do not change the received value’

0 means ‘presentationAllowed’

1 means ‘presentationRestricted’

2 set addressNotAvailable

3 is reserved

Default value -1

Example src_presentation=2

Explanation Specify a value of the presentationIndicator parameter upon receipt of the SETUP message from the call originator.

The parameter is used to ensure compatibility with PSTN gateways.



Page 199 of 218

Parameter src_presentation_screening_allowed=

gateway.cfg, user.cfg

Data type Boolean

Valid values 0 – disallows use of the parameters

1 – allows use of the parameters

src_presentation_screening_allowed=<number>

Default value

0

Example src_presentation_screening_allowed=1

Explanation

Use this parameter to control the use of the src_presentation= and src_screening= configuration parameters. Depending on the value of this parameter, the MVTS removes the corresponding fields from the packets or enables use of the src_presentation= and src_screening= configuration fields.


Parameter src_screening= gateway.cfg, user.cfg

Data type Integer

Valid values -1 means ‘leave provided value unchanged’

0 means ‘user provided, not changed’

1 means ‘user provided, verified and passed’

2 means ‘user provided, verified and failed’

3 means ‘network provided’

src_screening=<number>

Default value -1

Example src_screening=2

Explanation

Define the value of the screeningIndicator parameter upon receipt of the SETUP message from the call originator.



Page 200 of 218

Parameter stat_email= meraproxy.cfg, section [Statistics]


Valid values A regular e-mail address stored in the $EMAIL$ variable



Explanation Use this field to specify a sestination e-mail address for call statistics reports.

Parameter stat_email_cmd= meraproxy.cfg, section [Statistics]


Valid values Script or command name stat_email_cmd=<string>

Default value ((printf "From: mvts\nTo: $EMAIL$\nSubject: $SUBJECT$\n\n";cat $FILE$) | /usr/sbin/sendmail -B8BITMIME -f mvts -F$FROM$ $EMAIL$)

Example stat_email_cmd=((printf "From: mvts@\nTo: $EMAIL$\nSubject: $SUBJECT$\n\n";cat $FILE$) | /usr/sbin/sendmail -B8BITMIME -f mvts@ -F$FROM$ $EMAIL$)

Explanation Use this parameter to enter a command for dispatch of an e-mail with statistics (e.g. name of the script).

Parameter stat_email_from= meraproxy.cfg, section [Statistics]


Valid values An arbitrary string of characters including spaces that is stored in the $FROM$ variable

stat_email_from=<string>


Example stat_email_from=MVTS Server Statistics Manager

Explanation Use this parameter to specify the content of the “From:” field in e-mail messages.

mailto:[email protected]


Page 201 of 218

Parameter stat_email_subject= meraproxy.cfg, section [Statistics]


Valid values

An arbitrary character string including space characters that is stored in the $SUBJECT$ variable

stat_email_subject=<string>

Default value

mvts statistics

Example stat_email_subject=routine call statistics

Explanation Use this field to specify the content of the subject line in e-mail message.

Parameter stat_file_attr= meraproxy.cfg, section [Statistics]

Data type Integer stat_file_attr=

Valid values A three-digit decimal number, each digit may range from 0 to 7.

Default value 660

Example stat_file_attr=365

Explanation

Use this parameter to set attribute of the file where MVTS writes statistics. The permissions (read, write and execute) are identical to those found in all UNIX-like operating systems. Each digit of the three-digit number is a value ranging from 0 to 7 (i.e. from 000 to 111 in binary notation). The first digit pertains to the access permissions of the file owner, the second represents access permissions of the file owner group, and the third one specifies the access permissions of all other users. The access permission is granted when the appropriate bit is set (i.e. equals 1).

Note: Regardless of access permission settings in the main configuration file, the file owner can at all times read and write to the temporary and final files.


Page 202 of 218

Parameter stat_renewal_time= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values A positive integer in the 0 – 525599 (that is 1 year) representing a time interval in minutes

0 disables the functionality

stat_renewal_time=<number>

Default value 720 (12 hours)

Example stat_renewal_time=1440

Explanation Use this field to define a time interval (in minutes) for periodic obsolete data removals (e.g. data about gateways that are not in the configuration any more).

Parameter statistics_enable= meraproxy.cfg, section [Statistics]

Data type Boolean

Valid values 0 – disables statistics keeping

1 – enables statistics keeping

statistics_enable=<number>

Default value 1

Example statistics_enable=1

Explanation Use this parameter to enable or disable the statistics keeping mechanism.

Parameter stat_group= gateway.cfg, user.cfg


Valid values Arbitrary string of alphanumeric characters


Example stat_group=GROUP_1

Explanation The parameter is used to add gateways to groups of common statistics. The MVTS keeps an integral statistics record for all gateways/RAS users with identical values of the parameter stat_group=

Example:

Suppose you add the parameter stat_group=GROUP_1 to a gateway record configured in the gateway.cfg and a RAS-registering user described in user.cfg. By doing so you make the gateway and the RAS endpoint the members of the statistics group GROUP_1, and the MVTS from now on will keep common statistics for the gateway and the RAS user.


Page 203 of 218

Parameter stop_acct_level= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0, 1

0 – reduced size packets

1 – full size packets

stop_acct_level=<number>

Default value 1

Example stop_acct_level=0

Explanation The need to control the size of accounting packets originated by the MVTS arises from the fact that the OS divides UDP packets the size of which exceeds 1,500 bytes while not all network routers have the capability to correctly reassemble fragmented packets. At the same time a failure to receive a valid Accounting Stop packet may result in overcharging.

Resetting the stop_acct_level= flag (stop_acct_level=0) allows you to reduce the size of accounting packets limiting their contents to most essential VSA elements. The make-up of reduced accounting packets is presented in the table below.

VSA fields of Accounting packets with stop_acct_level=0

Accounting Start packet Accounting Stop packet

'h323-call-origin'

'h323-call-type',

'h323-conf-id',

'h323-call-id',

'h323-gw-id',

'h323-gw-address'

'h323-remote-id',

'h323-remote-address',

'h323-setup-time',

'xpgk-src-number-in',

'xpgk-src-number-out',

'xpgk-dst-number-in',

'xpgk-dst-number-out',

'h323-call-origin',

'h323-call-type',

'h323-conf-id',

'h323-call-id',

'h323-remote-address',

'h323-remote-id',

'h323-gw-id',

'h323-setup-time',

'h323-connect-time',

'h323-disconnect-time',

'h323-disconnect-cause',

'h323-voice-quality',

'xpgk-src-number-in',

'xpgk-src-number-out',

'xpgk-dst-number-in',

'xpgk-dst-number-out',

'xpgk-local-disconnect-cause',


Page 204 of 218

Parameter support_gid= meraproxy.cfg, section[Console]

Data type Integer

Valid values support_gid=<number>

Default value 0

Example support_gid=101

Explanation Use this parameter to specify the group identifiers for the MVTS Support user group.

Parameter suppress_Q931_cause= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values

0 – disables substitution

1 – substitutes 16 for the Q931 call termination cause

suppress_Q931_cause=<number>

Default value

0

Example suppress_Q931_cause=1

Explanation Enable/disable substitution of code 16 as Q931 call termination cause. This parameter comes useful when the employed billing system does not accept the Q931 call termination code other than 16 for calls of nonzero duration. When this is the case set the parameter to 1 and the MVTS will send 16 to the RADIUS server as the Q931 call termination cause code to indicate that the call duration was nonzero.

Parameter suspend_time= meraproxy.cfg, section [Statistics], section [Media]

Data type Integer

Valid values A positive integer ranging from 1 to 525599 (i.e. one year)

suspend_time=<number>

Default value 30

Example suspend_time=50

Explanation Use this parameter to specify suspension time (in minutes) for a route with low ASR.


Page 205 of 218

Parameter system_location= meraproxy.cfg, section [SNMP]


Valid values An arbitrary string of alphanumeric characters

Default value Server

Example system_location=SEATTLE OFFICE, 5-th ALLEY

Explanation Use this parameter to specify the location of the system.

Parameter system_name= meraproxy.cfg, section [SNMP]


Valid values An arbitrary string of alphanumeric characters representing the system name

system_name=<string>

Default value MVTS

Example system_name=MAIN SILONET GK/PROXY

Explanation Use this parameter to assign a unique name to the system.


Page 206 of 218

T Parameter terminal= gatekeeper.cfg

Data type Integer

Valid values 0 – MVTS poses as a gateway

1 – MVTS poses as a terminal

terminal=<number>

Default value 0

Example terminal=1

Explanation Use this parameter to determine the way the remote gatekeeper treats the MVTS. This field is optional.

Note that the value of this field does not affect the MVTS operation in any way. It is critical for the remote gatekeeper the MVTS registers with.

Parameter tcp_connect_timeout= gateway.cfg

Data type Integer

Valid values A positive integer denoting a time interval

tcp_connect_timeout=<number>

Default value 4500

Example tcp_connect_timeout=6000

Explanation Use this parameter to set tcp-connect wait time. By default the MVTS monitors the arrival of ACK at the signaling port for 4.5 sec. A failure to establish an H.225 session within the specified time results in call disconnection with local code 101. You may wish to extend the timeout to increase the chances of a successful call.

Parameter time_span= meraproxy.cfg, section [Statistics]

Data type Integer

Valid values A period of time in the following format: [[<hours>:] minutes:] seconds

time_span=[[<hours>:] minutes:] seconds

Default value 00:00:00

Example time_span=12:00:00

Explanation: Define maximum no-updates period, after which the current statistics (for a gateway and the dialpeer) will be cleared.

Note: If this parameter is set to the value of less than 60 seconds, it is automatically reset to 60.


Page 207 of 218

Parameter total_duration_saving= meraproxy.cfg, section [Statistics]

Data type Boolean

Valid values 0 – disables saving

1 – enables saving

total_duration_saving=<number>

Default value 1

Example total_duration_saving=1

Explanation: Use this parameter to enable/disable saving information about total duration of calls so that this information survives MVTS restarts.

Parameter tos_precedence= user.cfg, gateway.cfg

Data type Integer

Valid values 0 – 7 tos_precedence=<number>

Default value -1

Example tos_precedence=0

Explanation: The parameter serves to set the precedence of IP packets, sent to the gateways (RAS users), the configuration of which contains the set tos_precedence= parameter. For instance, if the settings of an origination gateway (GW1) include the configured parameter (tos_precedence=2), the MVTS will set the priority of all the RTP packets sent to GW1 to 2.

Note: it is advisable to set tos_precedence= in excess of 3 for the least possible number of gateways (RAS users), since a large amount of high-precedence packets may cause instability of the OS kernel.


Page 208 of 218

Parameter trace_level= meraproxy.cfg, section[Debug]

Data type Integer

Valid values 0 – disables log writing

1 – keeps the logged data at minimum

2 – sets intermediate data detail level

3 – turns on the most detailed logging

trace_level=<number>

Default value 0

Example trace_level=2

Explanation Use this parameter to define an information detail level for trace data written to the trace log contained in the file named mp . k e r n e l . s h . l o g - < d a t e > . The greater is the value the more detailed is the information written to the log.

Parameter trap_address= meraproxy.cfg, section [SNMP]


Valid values IP address in the common dot-separated format

trap_address=oct.oct.oct.oct

Default value

Example trap_address=194.23.122.14

Explanation Use this parameter to specify an IP address for sending trap messages.

Parameter trap_community= meraproxy.cfg, section [SNMP]


Valid values Arbitrary string of characters trap_community=<string>

Default value public

Example trap_community=municipal

Explanation Use this parameter to specify the name of the community of trap receivers.


Page 209 of 218

Parameter trap_email= meraproxy.cfg, section [SNMP]


Valid values A regular e-mail address stored in the $EMAIL$ variable



Explanation Use this field to specify an e-mail address for trap-message reports.

Parameter trap_email_cmd= meraproxy.cfg, section [SNMP]


Valid values Command or script name trap_email_cmd=<string>

Default value ((printf "From: mvts@\nTo: $EMAIL$\nSubject: $SUBJECT$\n\n";cat $FILE$) | /usr/sbin/sendmail -B8BITMIME -f mvts@ -F$FROM$ $EMAIL$)

Example trap_email_cmd=((printf "From: mvts@\nTo: $EMAIL$\nSubject: $SUBJECT$\n\n";cat $FILE$) | /usr/sbin/sendmail -B8BITMIME -f mvts@ -F$FROM$ $EMAIL$)

Explanation The field specifies the command triggering e-mail sending (e.g. name of the script).

Parameter trap_email_from= meraproxy.cfg, section [SNMP]


Valid values Arbitrary string of characters including spaces that is stored in the $FROM$ variable

trap_email_from=<string>

Default value MVTS Server Trap Manager

Example trap_email_from=MVTS server No.3

Explanation Use this parameter to specify the content of the “From:” field in e-mail message.


Page 210 of 218

Parameter trap_email_period= meraproxy.cfg, section [SNMP]

Data type Integer

Valid values

A time interval in the <[[<hours>:] minutes:] seconds> notation

trap_email_period=<[[<hours>:] minutes:] seconds>

Default value

1:00:00

Example trap_email_period=02:00:00

Explanation Use this parameter to specify the time of periodic e-mails.

Parameter trap_email_subject= meraproxy.cfg, section [SNMP]


Valid values An arbitrary character string including space characters that is stored in the $SUBJECT$ variable

Default value mvts trap list

Example trap_email_subject=Routine trap report

Explanation Use this field to specify the content of the ‘Subject’ line in the e-mail message.

Parameter trap_enable= meraproxy.cfg, section [SNMP]

Data type Boolean

Valid values 0 – disables trap sending

1 – enable trap sending

trap_enable=<number>

Default value 0

Example trap_enable=1

Explanation Use this parameter to enable/disable trap messages.


Page 211 of 218

Parameter trap_level= meraproxy.cfg, section [SNMP]

Data type Integer

Valid values 0 – no trap sending

1 – critical errors

2 – non-critical errors

3 – warnings

4 – information

5 – notification

trap_level=<number>

Default value 0

Example trap_level=1

Explanation Use this parameter to set significance level of trap messages.

Parameter trap_port= meraproxy.cfg, section [SNMP]

Data type Integer

Valid values Trap port number trap_port=<number>

Default value 0

Example trap_port=162

Explanation Use this parameter to define a port for SNMP trap messaging.

Parameter trusted_address= meraproxy.cfg, section [SNMP]


Valid values

32-bit IP addresses trusted_address=oct.oct.oct.oct

Default value

126.44.23.15

Example trusted_address=125.245.26.39

Explanation Use this parameter to specify a list of the source IP addresses whose SNMP queries will be accepted by the system. Use the delimiter ‘;’ to separate the list elements.


Page 212 of 218

Parameter type= gatekeeper.cfg

Data type Integer

Valid values 0 – MVTS sends the gatekeeper a request for the IP address used for call termination (LRQ – location request)

1 - MVTS registers with the gatekeeper as a RAS user and sends it an ARQ (admission request) for each outgoing call. The incoming calls enjoy pre-granted ACF (admission confirm) in this case the gatekeeper is not notified.

type=<number>

Default value 0

Example type=1

Explanation Use this parameter to specify the type of interaction between the MVTS and the remote gatekeeper it registers with.


Page 213 of 218

U Parameter user= gatekeeper.cfg


Valid values Arbitrary string user=<string>

Default value

Example user=anyone

Explanation Use this parameter to specify a user name for gatekeeper authorization.

Parameter user= user.cfg, gateway.cfg


Valid values An arbitrary string of characters

user=<string>


Example user=anyone

Explanation Use this parameter to specify the user name in the system. The name is used as the endpoint identity in RADIUS queries.

Parameter user_cfg= meraproxy.cfg,

section [Administration]

Data type String of characters

Valid values File name user_cfg=file_name

Default value user.cfg

Example user_cfg=my_user.cfg

Explanation Use this parameter to define the name of the data file with information about RAS users (registering endpoints). Specify the file path relative to the root directory or the system configuration file merarpoxy.cfg.


Page 214 of 218

Parameter use_h323_ivr_in= meraproxy.cfg, section [Radius]

Data type Boolean

Valid values 0 – disables username substitution

1 – enables username substitution

use_h323_ivr_in=<number>

Default value 0

Example use_h323_ivr_in=1

Explanation Use this flag to control user name substitution in the UserName field of the accounting packets forwarded to the RADIUS server. The substituted name is the user name present in the Cisco AV-pair (1) h323_ivr_in= field of the AccessAccept response (sent to the RADIUS server). The substituted name is used exclusively in the accounting packets and for the current route only.

Note: This parameter is functional only when the acct_leg_type value is within the 1 – 4 range.

Parameter use_info_digits= gateway.cfg, user.cfg

Data type Boolean

Valid values 0 – disallows the use of digits from INFORMATION packets

1 – allows the use of digits from INFORMATION packets

Default value use_info_digits=0

Example use_info_digits=1

Explanation This flag allows and disallows the use of digits from the Information packets received by the MVTS after SETUP. The INFORMATION packet digits concatenated to the number from SETUP appear in the CDR in the field INFO-NUMBER.

Use this parameter together with reset_can_overlap_send= .


Page 215 of 218

Parameter user_translate= dialpeer.cfg


Valid values Regular expressions/$ip$ macros user_translate=<string1>/[\n1]:[\n2];

Default value

Empty string

Example user_translate=[0-9]*|#|[0-9]*|#|1111[0-9]*/\1:\3

With the call’s d s t _ n u m b e r being 47765#13245#1111974553

the extracted user name is 47765

and the user’s password is 13245

Explanation

The parameter is used to extract the user name:password from the dst_number= pattern. The translation pattern is the regexp configured in dst_number=, and [\n1]:[\n2] are numbers of substitution sections.

Note: you can use the character ‘:’ in the translation pattern as follows:

Example:

Suppose the MVTS has a call with destination number 1234#5678#70951000000. Originally the user name is ‘client’, and password is ‘clientpass’. If user_translate=[0-9]{4}|#|[0-9]{6}|#[0-9]/\1:\3, the extracted user name and password will be username=1234, password=5678

If nothing follows the trailing colon in the regexp user_translate=[0-9]{4}|#|[0-9]{6}|#[0-9]/\1: the user password will be an empty string, i.e. username=1234, password= If the regular expression contains no colon - user_translate=[0-9]{4}|#|[0-9]{6}|#[0-9]/\1 , the user password remains unchanged, i.e. username=1234, password=clientpass

Note: you can use the $ip$ macros as a value of the user_translate field, in which case the MVTS sends the RADIUS server the user’s IP address.


Page 216 of 218

V Parameter validation_gap= meraproxy.cfg, section [LAR]

Data type Integer

Valid values Positive numbers representing a packet forwarding delay in milliseconds

validation_gap=<number>

Default value 0

Example validation_gap=1000

Explanation A delay time for the packets destined for the origination gateway to improve chances of a successful call setup.

Parameter validation_gap= user.cfg, gateway.cfg

Data type Integer

Valid values A packet forwarding delay in milliseconds

validation_gap=<number>

Default value 1000

Example validation_gap=3000

Explanation Set the packet forwarding delay in milliseconds for the gateway (RAS user) during which call setup packets exchange with the origination gateway (RAS user) will be suspended.

During call setup the packets arriving from the termination gateway (RAS user) are stored in the MVTS buffer, whose content will be forwarded further to the origination gateway only when the delay time specified in the validation_gap= field is over or when one of the messages defined in the validation_msg= (Progress, Facility, Alerting etc.) is received from the termination gateway (RAS user), whichever is first.

Such organization of the call setup and look-ahead routing procedure is needed for gateways (RAS users) that can handle one CallProceeding message only. Hence, if a CallProceeding message is occasionally followed by a Release_Complete message, further work (call setup and call rerouting) with such a gateway (RAS user) intolerable to repeated CallProceeding messages and failing to initialize may become impossible.



Page 217 of 218

Parameter validation_msg= user.cfg, gateway.cfg

Data type Integer

Valid values Codes of the message from the called party validation_msg=<number>

Default value

0 – parameter disabled

Example validation_msg=7

Explanation Use this parameter to specify the message whose arrival will resume the suspended exchange with the call originator during the call setup process.

The other condition of resuming the packet exchange with the call originator is expiration of the validation_gap= time. When the called party rejects the call prior to meeting both of the above conditions the call will be rerouted.

Note: Call rerouting will be impossible after establishing TCP connection for H.245 by the called party.

Note: the following settings Connect=7, Alerting=1, Progress=3, Facility=98 are effectuated by any non-zero validation_gap= values.


Page 218 of 218

Document history

04/01/08 tsamarin: The description of the following parameters has been added: dscp_byte_media=

dscp_byte_signaling=

ports_range=

check_rtp_source=

direct_call_allowed=

q931_cause_override=

dst_allowed_prefix=

dst_disallowed_prefix=

Documents

MVTS 3.1.4 Configuration Manual