[ccpccxml]

default_uri

Default CCXML Application

Specifies the URI for the default CCXML application

Default value

file://$InstallationRoot$/config/default.ccxml

Takes effect immediately

defaultmaxage

Default Maxage

Default Maxage for fetching an initial CCXML page

Valid values

From 30 to 180 inclusive (in seconds)

Default value

60

Takes effect immediately

defaultmaxstale

Default Maxstale

Default Maxstale for fetching an initial CCXML page

Valid values

From 0 to 180 inclusive (in seconds)

Default value

0

Takes effect immediately

fips_enabled

FIPS Mode Enabled

Specifies whether to enable FIPS mode in CCP. When FIPS mode is enabled, only FIPS 140-2 approved ciphers and algorithms can be used in SSL connections.

Valid values

  • true
  • false

Default value

false

Takes effect At start/restart

shutdown_grace_period

Shutdown Grace Period

The amount of time (in seconds) sessions are given to terminate after Graceful Stop is selected. Once this grace period is exceeded, sessions are killed by ccxml.kill.unconditional events.

Valid values

From 0 to 65535 inclusive (in seconds)

Default value

7200

Takes effect immediately

sip.send_progressing

Send SIP Progressing

Determines whether 180 SIP response is sent on tag for all incoming calls.
0 - 180 response is sent when <send> is called
1 - 180 response is sent immediately after sending 100 Trying

Valid values

  • 1
  • 0

Default value

0

Takes effect immediately

[ccxmli]

basichttp.recv.accessuri

Preferred IP version to be used in basichttp access uri

Preferred IP version to be used in basichttp access uri "session.ioprocessors["basichttp"]". Valid values are "ipv4" and "ipv6".

Valid values

  • ipv4
  • ipv6

Default value

ipv4

Takes effect immediately

basichttp.recv.host

BasicHTTP Receive - Host for IPv4 network

The IPv4 address or hostname on which the Basic HTTP Event I/O Processor will be listening for HTTP requests on IPv4 network interface. If the value is an empty string, the system listen on all available IPv4 network interface. If hostname is specified, the first IPv4 address in the resolved list will be used.

Default value

(blank)

Takes effect immediately

basichttp.recv.host.ipv6

BasicHTTP Receive - Host for IPv6 network

The IPv6 address or hostname on which the Basic HTTP Event I/O Processor will be listening for HTTP requests on IPv6 network interface. If the value is an empty string, the system listen on all available IPv6 network interface. If hostname is specified, the first IPv6 address in the resolved list will be used.

Default value

(blank)

Takes effect immediately

basichttp.recv.path

BasicHTTP Receive - Path

The access path for the Basic HTTP Event I/O Processor.

Default value

/ccxml/basichttp

Takes effect immediately

basichttp.recv.port

BasicHTTP Receive - Port

The port on which the Basic HTTP Event I/O Processor will be listening for HTTP requests.

Default value

4892

Takes effect immediately

basichttp.recv.show_error_body

BasicHTTP Receive - Show Error Body

When set to TRUE, a descriptive text will be returned in the response body when an HTTP failure response is given for a request to the Basic HTTP Event I/O Processor.

Valid values

  • true
  • false

Default value

false

Takes effect immediately

basichttp.send.timeout

BasicHTTP Send Timeout

The HTTP response timeout (in milliseconds) value for an event sent to another platform via HTTP.

Default value

15000

Takes effect immediately

createsession.recv.accessuri

Preferred IP version to be used in createsession access uri

Preferred IP version to be used in createsession access uri "session.ioprocessors["createsession"]". Valid values are "ipv4" and "ipv6".

Valid values

  • ipv4
  • ipv6

Default value

ipv4

Takes effect immediately

createsession.recv.host

CreateSession Receive Host for IPv4 network

The IPv4 address or hostname on which the Session Creation Event I/O Processor will be listening for HTTP requests on IPv4 network interface. If the value is an empty string, the system listen on all available IPv4 network interface. If hostname is specified, the first IPv4 address in the resolved list will be used.

Default value

(blank)

Takes effect immediately

createsession.recv.host.ipv6

CreateSession Receive Host for IPv6 network

The IPv6 address or hostname on which the Session Creation Event I/O Processor will be listening for HTTP requests on IPv6 network interface. If the value is an empty string, the system listen on all available IPv6 network interface. If hostname is specified, the first IPv6 address in the resolved list will be used.

Default value

(blank)

Takes effect immediately

createsession.recv.path

CreateSessoin Receive - Path

The access path for the Session Creation Event I/O Processor.

Default value

/ccxml/createsession

Takes effect immediately

createsession.recv.port

CreateSession Receive - Port

The port on which the Session Creation Event I/O Processor will be listening for HTTP requests.

Valid values

A valid value is an integer from 1025 to 65535 inclusive.

Default value

4892

Takes effect immediately

createsession.recv.show_error_body

CreateSession Receive Show Error Body

When set to TRUE, a descriptive text will be returned in the response body when an HTTP failure response is given for a request to the Session Creation Event I/O Processor.

Valid values

  • true
  • false

Default value

false

Takes effect immediately

debug_data.dir

Debug Data directory

Debug Data Directory

Default value

$InstallationRoot$/debugdata

Takes effect immediately

debug_data.dir_levels

Debug Data directory Levels

The nesting depth of debug data sub-folders. For example, if the session id is "1234" and directory nesting is set to 2, a file called "debug.dat" will be saved as /1/2/1234/debug.dat. When set to 0, no nesting occurs. Directory nesting can be enabled when there's a need to retain debug data for a lot of sessions, to decrease the number of sub-directories each directory will have.

Default value

0

Takes effect immediately

debug_data.file_levels

Debug Data file Levels

The nesting depth of debug data files. For example, if the session id is "1234" and file nesting is set to 2, a file called "debug.dat" will be saved as /1234/d/e/debug.dat. When set to 0, no nesting occurs. File nesting can be enabled when there's a need to retain debug data for a lot of files, to decrease the number of files each directory will have.

Default value

0

Takes effect immediately

default_caller_id

Default CallerID

Default CallerID

Default value

sip:ccxml@localhost

Takes effect immediately

fetch.timeout

Initial Page Fetch Timeout

The default timeout interval (in seconds) for the initial page fetch completion for new CCXML session to complete.

Default value

30

Takes effect immediately

inactive_session_kill_timeout

Inactive Session Kill Timeout

The amount of time (in seconds) that a session may idle without owning any connections or dialogs and without removing any "external" events from its event queue (An external event is an event that does not have an eventsourcetype of ccxml and an eventsource that is the current session's id). If the limit is reached, then ccxml.kill is sent to the session. If the limit value is not configured or is set to 0, then no limit is placed on the idle time.

Default value

7200

Takes effect immediately

kill_by_other

Kill process externally

If set to True, allow Process to be killed by external entity.

Valid values

  • true
  • false

Default value

true

Takes effect immediately

max_conf_per_session

Max Conf per session

Max Conf per session

Valid values

A valid value is an integer from 1 to 100000 inclusive.

Default value

100

Takes effect immediately

max_conn_per_session

Max connections per session

Max Connections per session

Valid values

A valid value is an integer from 1 to 100000 inclusive.

Default value

100

Takes effect immediately

max_dialog_per_session

Max dialogs per session

Max dialogs per session

Valid values

A valid value is an integer from 1 to 100000 inclusive.

Default value

100

Takes effect immediately

max_internal_loop_count

Maximum Internal Loop Count

The number of times a session iterates through an loop without removing an "external" event from its event queue (An external event is an event that does not have an eventsourcetype of ccxml and an eventsource that is the current session's id.) or without the session's event queue being empty after processing an event. If the limit is reached, then ccxml.kill.unconditional is sent to the session. If the limit value is not configured or set to 0 then no limit is placed on the event processing.

Default value

200

Takes effect immediately

max_num_documents

Max number of documents

Max number of documents

Valid values

A valid value is an integer from 1 to 100000 inclusive.

Default value

6000

Takes effect immediately

max_num_sessions

Max number of sessions

Max number of sessions

Valid values

A valid value is an integer from 1 to 100000 inclusive.

Default value

6000

Takes effect immediately

num_session_processing_threads

Numbers of threads per session

Numbers of threads per session

Valid values

A valid value is an integer from 1 to 5 inclusive.

Default value

5

Takes effect immediately

platform.save_ccxml_files

Save CCXML Files

When set to True, fetch request/response/data for each fetched CCXML page will be saved.

Valid values

  • true
  • false

Default value

false

Takes effect immediately

platform.save_script_files

Save Script Files

When set to True, fetch request/response/data for each fetched ECMAScript file will be saved.

Valid values

  • true
  • false

Default value

false

Takes effect immediately

ssl

Activate SSL

Use SSL to receive CreateSession and BasicHTTP requests

Valid values

  • true
  • false

Default value

false

Takes effect At start/restart

ssl.recv.cert_file

CreateSession Receive and BasicHTTP Receive - SSL Certification File

The path and the filename of the SSL certificate to be used for createsession and BasicHTTP.

Default value

(blank)

Takes effect At start/restart

ssl.recv.password

CreateSession Receive and BasicHTTP Receive - SSL Password

The password associated with the certificate and key pair. Required only if key file is password protected.

Default value

(blank)

Takes effect At start/restart

ssl.recv.private_key_file

CreateSession Receive and BasicHTTP Receive - SSL Private Key File

The path and the filename of the SSL key to be used for createsession and BasicHTTP.

Default value

(blank)

Takes effect At start/restart

ssl.recv.protocol_type

CreateSession Receive and BasicHTTP Receive - Type of SSL Secure Transport

  • The type of secure transport to be used and valid values are:
  • SSLv2 A TLS/SSL connection established with these methods will only understand the SSLv2 protocol. This server will only understand SSLv2 client hello messages.
  • SSLv3 A TLS/SSL connection established with these methods will only understand the SSLv3 protocol. This server will only understand SSLv3 client hello messages. This especially means, that it will not understand SSLv2 client hello messages which are widely used for compatibility reasons.
  • TLSv1 A TLS/SSL connection established with these methods will only understand the TLSv1 protocol. This server will only understand TLSv1 client hello messages. This especially means, that it will not understand SSLv2 client hello messages which are widely used for compatibility reasons.
  • SSLv23 A TLS/SSL connection established with these methods will understand the SSLv2, SSLv3, and TLSv1 protocol. This server will understand SSLv2, SSLv3, and TLSv1 client hello messages. This is the best choice when compatibility is a concern.
  • Valid values

    • TLSv1
    • SSLv2
    • SSLv3
    • SSLv23

    Default value

    TLSv1

    Takes effect At start/restart

    trace_flag

    Trace flag

    Trace flag.

    Valid values

    • true
    • false

    Default value

    true

    Takes effect immediately

    [ems]

    dc.default.logfilter

    Default Upstream Log Filter for Data Collection Sink

    Specifies the filter for logs to be delivered "upstream" to the Reporting Server for Call Events reporting. The format is 'levels|moduleIDs|specifierIDs' (repeated if necessary). The values between the pipes can be in the format: 'm-n,o,p' (ie "0-4, 5,6"). The wildcard character '*' can also be used to indicate all valid numbers. Example: '*|*|*' indicates that all log messages should be sent to the sink. Alternatively, '0,1|0-10|*|4|*|*' inidcates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 wil be sent to the sink; and all INFO(4) level messages will be sent as well.

    Valid values

    Pipe delimited ranges for log levels, module IDs and specifier IDs. Ranges can be comma separated integers or range of integers or '*'.

    Default value

    0-2|*|*

    Takes effect At start/restart

    dc.default.metricsfilter

    Default Metrics Filter for Data Collection Sink

    Specifies the default filter for metrics to be delivered "upstream" to the Reporting Server for Call Events reporting. '*' indicates that all metrics will be sent to the sink. Alternatively, '5-10,50-55,70,71' indicates that metrics with IDs 5,6,7,8,9,10,50,51,52,53,54,55,70 and 71 will be sent to the MF sink. This filter will be used unless the default has been overridden in the tenant or IVR Application profile to which the given call has been associated.

    Valid values

    Comma separated list of metric values or ranges. A metric value must be between 0 and 141 inclusive. The values '*' and blank are also allowed.

    Default value

    1001,1009,1012-1013,1031,1050,1052,1058-1059

    Takes effect At start/restart

    logconfig.DATAC

    Data Collection Sink Log Filter

    Controls the log messages that are sent to the MF sink. The format is 'levels|moduleIDs|specifierIDs' (repeated if necessary). The values between the pipes can be in the format: 'm-n,o,p' (ie "0-4, 5,6"). The wildcard character '*' can also be used to indicate all valid numbers. Example: '*|*|*' indicates that all log messages should be sent to the sink. Alternatively, '0,1|0-10|*|4|*|*' inidcates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 wil be sent to the sink; and all INFO(4) level messages will be sent as well.

    Valid values

    Pipe delimited ranges for log levels, module IDs and specifier IDs. Ranges can be comma separated integers or range of integers or '*'.

    Default value

    0-2|*|*

    Takes effect immediately

    logconfig.MFSINK

    MF Sink Log Filter

    Controls the log messages that are sent to the MF sink. The format is 'levels|moduleIDs|specifierIDs' (repeated if necessary). The values between the pipes can be in the format: 'm-n,o,p' (ie "0-4, 5,6"). The wildcard character '*' can also be used to indicate all valid numbers. Example: '*|*|*' indicates that all log messages should be sent to the sink. Alternatively, '0,1|0-10|*|4|*|*' inidcates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 wil be sent to the sink; and all INFO(4) level messages will be sent as well.

    Valid values

    Pipe delimited ranges for log levels, module IDs and specifier IDs. Ranges can be comma separated integers or range of integers or '*'.

    Default value

    *|*|*

    Takes effect immediately

    metricsconfig.DATAC

    Data Collection Sink Metrics Filter

    Specifies the metrics that are delivered to the Data Collection Sink. '*' indicates that all metrics will be sent to the sink. Alternatively, '5-10,50-55,70,71' indicates that metrics with IDs 5,6,7,8,9,10,50,51,52,53,54,55,70 and 71 will be sent to the MF sink.

    Valid values

    Comma separated list of metric values or ranges. A metric value must be between 0 and 141 inclusive. The values '*' and blank are also allowed.

    Default value

    *

    Takes effect immediately

    metricsconfig.MFSINK

    MF Sink Metrics Filter

    Specifies the metrics that are delivered to the MF Sink. '*' indicates that all metrics will be sent to the sink. Alternatively, '5-10,50-55,70,71' indicates that metrics with IDs 5,6,7,8,9,10,50,51,52,53,54,55,70 and 71 will be sent to the MF sink.

    Valid values

    Comma separated list of metric values or ranges. A CCP metric value must be between 1000 and 1063 inclusive. The values '*' and blank are also allowed.

    Default value

    1000-1001,1003-1005,1007-1016,1019-1021,1024,1027-1036,1039-1045,1048-1050,1052-1054,1056,1058-1062

    Takes effect immediately

    ors.reportinginterval

    OR reporting interval

    Interval (seconds) accumulated operational reports are submitted to the Reporting Server

    Valid values

    An integer between 1-299 inclusive.

    Default value

    60

    Takes effect At start/restart

    rc.batch_size

    Upstream Batch Size

    The number of upstream messages queued up by the reporting client before sending them up to the reporting server. A higher batch size (e.g. 50 records) will lessen bandwidth constraints, at the cost of making sending data at larger intervals.

    Valid values

    An integer between 1-5000 inclusive.

    Default value

    500

    Takes effect At start/restart

    rc.cdr.batch_size

    CDR Batch Size

    The number of CDR messages queued up by the reporting client before sending them up to the reporting server. A higher batch size (e.g. 50 records) will lessen bandwidth constraints, at the cost of making sending CDR data at larger intervals.

    Valid values

    An integer between 1-5000 inclusive.

    Default value

    500

    Takes effect At start/restart

    rc.cdr.local_queue_max

    Maximum Records in the Persisted Local DB File for CDR data

    This option specifies the maximum number of data items to the local database for CDR reporting. Queuing to the local database will occur either when the Reporting Server is unavailable, or when data is being provided to the Client faster than the Server can consume it. A value of -1 indicates an "unlimited" number of records will be allowed. A value of 0 indicates that no records will be persisted locally and data will be discarded if the RS is unavailable.

    Valid values

    An integer greater or equal to -1.

    Default value

    1000000

    Takes effect At start/restart

    rc.cdr.local_queue_path

    Persistent DB File for CDR Data

    The full path of the local database file used to locally persist data for CDRs.

    Valid values

    Path to the DB file.

    Default value

    $InstallationRoot$/config/cdrQueue_ccp.db

    Takes effect At start/restart

    rc.cdr.max_throughput

    Maximum Throughput of CDR data sent to the RS

    This option specifies the maximum rate at which CDR data, in bytes per second, is sent to the Reporting Server. A value of 0 (default) indicates that CDR data will be sent as quickly as possible.

    Valid values

    An integer greater or equal to 0.

    Default value

    0

    Takes effect At start/restart

    rc.certificate

    TLS Certificate for Reporting Client

    The file name of the TLS certificate in "PEM" format. Required to connect to the Reporting Server (ActiveMQ) over TLS.

    Valid values

    File path

    Default value

    (blank)

    Takes effect at start/restart

    rc.local_queue_max

    Maximum Records in the Persisted Local DB File for Upstream Logging

    This option specifies the maximum number of data items to the local database for Upstream Logging. Queuing to the local database will occur either when the Reporting Server is unavailable, or when data is being provided to the Client faster than the Server can consume it. A value of -1 indicates an "unlimited" number of records will be allowed. A value of 0 indicates that no records will be persisted locally and data will be discarded if the RS is unavailable.

    Valid values

    An integer greater or equal to -1.

    Default value

    5000000

    Takes effect At start/restart

    rc.local_queue_path

    Persistent DB File for Upstream Logging

    The full path of the local database file used to locally persist data for upstream logging to the GVP Reporting Client.

    Valid values

    Path to the DB file.

    Default value

    $InstallationRoot$/config/upstreamQueue_CCP.db

    Takes effect At start/restart

    rc.max_throughput

    Maximum Throughput of Upstream Logging data sent to the RS

    This option specifies the maximum rate at which Upstream Logging data, in bytes per second, is sent to the Reporting Server. A value of 0 (default) indicates that Upstream Logging data will be sent as quickly as possible.

    Valid values

    An integer greater or equal to 0.

    Default value

    0

    Takes effect At start/restart

    rc.ors.local_queue_max

    Maximum Records in the Persisted Local DB File for OR data

    This option specifies the maximum number of data items to the local database for Operational Reporting. Queuing to the local database will occur either when the Reporting Server is unavailable, or when data is being provided to the Client fdaster than the Server can consume it. A value of -1 indicates an "unlimited" number of records will be allowed. A value of 0 indicates that no records will be persisted locally and data will be discarded if the RS is unavailable.

    Valid values

    An integer greater or equal to -1.

    Default value

    1000000

    Takes effect At start/restart

    rc.ors.local_queue_path

    Persistent DB File for OR Data

    The full path of the local database file used to locally persist data for Operational Reporting.

    Valid values

    Path to the DB file.

    Default value

    $InstallationRoot$/config/orsQueue_ccp.db

    Takes effect At start/restart

    [fm]

    cachemaxentrycount

    Maximum Cache Entry Count

    The maximum number of cache entries that can be stored in the cache.

    Valid values

    Must be an integer greater than or equal to 0.

    Default value

    1000

    Takes effect At start/restart

    cachemaxentrysize

    Maximum Cache Entry Size

    The maximum size of each cache entry in bytes.

    Valid values

    Must be an integer greater than or equal to 0.

    Default value

    100000

    Takes effect At start/restart

    cachemaxsize

    Maximum Cache Size

    The maximum total size of the cache in bytes.

    Valid values

    Must be an integer greater than or equal to 0.

    Default value

    10000000

    Takes effect At start/restart

    enable100continue

    Enable 100-continue

    Enable or disable the "Expect: 100-continue" header in HTTP 1.1 requests.

    Valid values

    • 0
    • 1

    Default value

    0

    Takes effect At start/restart

    http_proxy

    HTTP Proxy

    The HTTP proxy to be used for HTTP requests.

    Default value

    localhost:3128

    Takes effect At start/restart

    https_proxy

    HTTPS Proxy

    The HTTPS proxy to be used for HTTPS requests.

    Default value

    (blank)

    Takes effect At start/restart

    interface

    Outgoing Interface

    This sets the network interface IP address to be used for outgoing HTTP requests. If this parameter is empty, it will automatically select the network interface to be used. If the Squid HTTP proxy is used, it has to be configured to accept HTTP requests from the interface specified. Otherwise, Squid by default would only accept HTTP requests from the localhost.

    Default value

    (blank)

    Takes effect At start/restart

    localfile_maxage

    Maxage for Local File

    Maxage for cached local file in seconds. Caching of local file can be turned off by setting this to 0.

    Default value

    10

    Takes effect At start/restart

    maxredirections

    Maximum Redirections

    The maximum number of times to follow the Location: header in the HTTP response. Set to 0 to disable HTTP redirection.

    Valid values

    Must be an integer greater than or equal to 0, and less than 99.

    Default value

    5

    Takes effect At start/restart

    no_cache_url_substring

    No Cache URL Substring

    If a URL contains any one of the sub-strings in this comma-delimited list, it will not be cached.

    Default value

    cgi-bin,jsp,asp,?

    Takes effect At start/restart

    portrange

    HTTP Port Range

    The local port range to be used for HTTP requests. If this parameter is not specified, CCP will let the OS choose the local port.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_ca_info

    SSL CA Info

    The file name holding one or more certificates to verify the peer with.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_ca_path

    SSL CA Path

    The path holding multiple CA certificates to verify the peer with. The certificate directory must be prepared using the openssl c_rehash utility.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_cert

    SSL Certificate

    The file name of your certificate. The default format is "PEM" and can be changed with the configuration parameter ssl_cert_type

    Default value

    (blank)

    Takes effect At start/restart

    ssl_cert_type

    SSL Certificate Type

    The format of the certificate.

    Valid values

    • PEM
    • DER

    Default value

    PEM

    Takes effect At start/restart

    ssl_cipher_list

    SSL Cipher List

    The list of ciphers to use for the SSL connection. The list must be syntactically correct, it consists of one or more cipher strings separated by colons. Commas or spaces are also acceptable separators but colons are normally used, , - and + can be used as operators. Valid examples of cipher lists include 'RC4-SHA', 'SHA1+DES', 'TLSv1' and 'DEFAULT'. More details about cipher lists can be found on this URL: http://www.openssl.org/docs/apps/ciphers.html.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_key

    SSL Key

    The file name of the private key. The default format for the key is "PEM" and may be changed by the parameter ssl_key_type.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_key_password

    SSL Key Password

    The password required to use the ssl_key.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_key_type

    SSL Key Type

    The format of the private key.

    Valid values

    • PEM
    • DER

    Default value

    PEM

    Takes effect At start/restart

    ssl_random_file

    SSL Random File Seed

    The path to a file which is read from to seed the random engine for SSL.

    Default value

    (blank)

    Takes effect At start/restart

    ssl_verify_host

    SSL Verify Host

    Specifies how the Common name from the peer certificate should be verified during the SSL handshake

    Valid values

    • 0
    • 1
    • 2

    Default value

    0

    Takes effect At start/restart

    ssl_verify_peer

    Verify Peer Certificate

    Whether or not to verify the peer's certificate. When this option is set, one of ssl_ca_info or ssl_ca_path should be set.

    Valid values

    • 0
    • 1

    Default value

    0

    Takes effect At start/restart

    ssl_version

    SSL Version

    Set what version of SSL to attempt to use. By default, the SSL library will automatically detect the correct version. This parameter can be used to override this automatic detection, for situations where the wrong version is chosen.

    Valid values

    • 0
    • 1
    • 2
    • 3

    Default value

    0

    Takes effect At start/restart

    [log]

    all

    Output for level all

    Specifies the outputs to which an application sends all log events. The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
  • Default value

    ../logs/ccp

    Takes effect immediately

    check-point

    Check point interval

    Specifies, in hours, how often the application generates a check point log event, to divide the log into sections of equal time. By default, the application generates this log event every hour. Setting the option to 0 prevents the generation of check-point events.

    Valid values

    0 - 24

    Default value

    1

    Takes effect immediately

    compatible-output-priority

    Enable 6.X compatible log output priority

    Specifies whether the application uses 6.x output logic.

    Valid values

  • true The log of the level specified by "Log Output Options" is sent to the specified output.
  • false The log of the level specified by "Log Output Options" and higher levels is sent to the specified output.
  • Default value

    false

    Takes effect immediately

    debug

    Output for level debug

    Specifies the outputs to which an application sends the log events of the Debug level and higher (that is, log events of the Standard, Interaction, Trace, and Debug levels). The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
  • Default value

    ../logs/ccp

    Takes effect immediately

    expire

    Log Expiration

    Determines whether log files expire. If they do, sets the measurement for determining when they expire, along with the maximum number of files (segments) or days before the files are removed.

    Valid values

  • false No expiration; all generated segments are stored.
  • [number] file or [number] Sets the maximum number of log files to store. Specify a number from 1-100.
  • [number] day Sets the maximum number of days before log files are deleted. Specify a number from 1-100.
  • Default value

    10

    Takes effect immediately

    interaction

    Output for level interaction

    Specifies the outputs to which an application sends the log events of the Debug level and higher (that is, log events of the Standard, Interaction, Trace, and Debug levels). The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
  • Default value

    ../logs/ccp

    Takes effect immediately

    keep-startup-file

    Keep startup log file

    Specifies whether a startup segment of the log, containing the initial configuration, is to be kept. If it is, this option can be set to true or to a specific size. If set to true, the size of the initial segment will be equal to the size of the regular log segment defined by the segment option. The value of this option will be ignored if segmentation is turned off (that is, if the segment option set to false).

    Valid values

  • false No startup segment of the log is kept.
  • true A startup segment of the log is kept. The size of the segment equals the value of the segment option.
  • [number] KB Sets the maximum size, in kilobytes, for a startup segment of the log.
  • [number] MB Sets the maximum size, in megabytes, for a startup segment of the log.
  • Default value

    true

    Takes effect After restart

    memory

    Memory snapshot file name

    Specifies the name of the file to which the application regularly prints a snapshot of the memory output, if it is configured to do this. The new snapshot overwrites the previously written data. If the application terminates abnormally, this file will contain the latest log messages. Memory output is not recommended for processors with a CPU frequency lower than 600 MHz.

    Valid values

    [string] (memory file name)

    Default value

    (blank)

    Takes effect immediately

    memory-storage-size

    Memory output buffer size

    Specifies the buffer size for log output to the memory, if configured.

    Valid values

  • [number] KB or [number] The size of the memory output, in kilobytes. The minimum value is 128 KB.
  • [number] MB The size of the memory output, in megabytes. The maximum value is 64 MB
  • Default value

    (blank)

    Takes effect When memory output is created

    message_format

    Log messages format

    Specifies the format of log record headers that an application uses when writing logs in the log file. Using compressed log record headers improves application performance and reduces the log file's size. With the value set to short:
  • A header of the log file or the log file segment contains information about the application (such as the application name, application type, host type, and time zone), whereas single log records within the file or segment omit this information.
  • A log message priority is abbreviated to Std, Int, Trc, or Dbg, for Standard, Interaction, Trace, or Debug messages, respectively.
  • The message ID does not contain the prefix GCTI or the application type ID.
    A log record in the full format looks like this:
    2002-05-07T18:11:38.196 Standard localhost cfg_dbserver GCTI-00-05060 Application started
    A log record in the short format looks like this:
    2002-05-07T18:15:33.952 Std 05060 Application started
  • Valid values

    • short
    • full
  • short An application uses compressed headers when writing log records in its log file.
  • full An application uses complete headers when writing log records in its log file.
  • Default value

    short

    Takes effect immediately

    messagefile

    Message file

    Specifies the file name for application-specific log events. The name must be valid for the operating system on which the application is running. The option value can also contain the absolute path to the application-specific *.lms file. Otherwise, an application looks for the file in its working directory.

    Valid values

    [string].lms (message file name)

    Default value

    (blank)

    Takes effect Immediately, if an application cannot find its *.lms file at startup

    print-attributes

    Enable printing extended attributes

    Specifies whether the application attaches extended attributes, if any exist, to a log event that it sends to log output. Typically, log events of the Interaction log level and Audit-related log events contain extended attributes. Setting this option to true enables audit capabilities, but negatively affects performance. Genesys recommends enabling this option for Solution Control Server and Configuration Server when using audit tracking. For other applications, refer to Genesys 7.5 Combined Log Events Help to find out whether an application generates Interaction-level and Audit-related log events; if it does, enable the option only when testing new interaction scenarios.

    Valid values

  • true Attaches extended attributes, if any exist, to a log event sent to log output.
  • false Does not attach extended attributes to a log event sent to log output.
  • Default value

    false

    Takes effect immediately

    segment

    Log Segmentation

    Specifies whether there is a segmentation limit for a log file. If there is, sets the mode of measurement, along with the maximum size. If the current log segment exceeds the size set by this option, the file is closed and a new one is created.

    Valid values

  • false No segmentation is allowed.
  • [number] KB or [number] Sets the maximum segment size, in kilobytes. The minimum segment size is 100 KB.
  • [number] MB Sets the maximum segment size, in megabytes.
  • [number] hr Sets the number of hours for the segment to stay open. The minimum number is 1 hour.
  • Default value

    10000

    Takes effect immediately

    spool

    Folder for the temporary network log output files

    Specifies the folder, including full path to it, in which an application creates temporary files related to network log output. If you change the option value while the application is running, the change does not affect the currently open network output.

    Valid values

    [path] (the folder, with the full path to it)

    Default value

    (blank)

    Takes effect immediately

    standard

    Output for level standard

    Specifies the outputs to which an application sends the log events of the Debug level and higher (that is, log events of the Standard, Interaction, Trace, and Debug levels). The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
  • Default value

    ../logs/ccp_standard

    Takes effect immediately

    time_convert

    Time generation for log messages

    Specifies the system in which an application calculates the log record time when generating a log file. The time is converted from the time in seconds since the Epoch (00:00:00 UTC, January 1, 1970).

    Valid values

    • local
    • utc
  • local The time of log record generation is expressed as a local time, based on the time zone and any seasonal adjustments. Time zone information of the application's host computer is used.
  • utc The time of log record generation is expressed as Coordinated Universal Time (UTC).
  • Default value

    local

    Takes effect immediately

    time_format

    Time format for log messages

    Specifies how to represent, in a log file, the time when an application generates log records.
    A log record's time field in the ISO 8601 format looks like this:
    2001-07-24T04:58:10.123

    Valid values

    • time
    • locale
    • ISO8601
  • time The time string is formatted according to the HH:MM:SS.sss (hours, minutes, seconds, and milliseconds) format.
  • locale The time string is formatted according to the system's locale.
  • ISO8601 The date in the time string is formatted according to the ISO 8601 format. Fractional seconds are given in milliseconds.
  • Default value

    ISO8601

    Takes effect immediately

    trace

    Output for level trace

    Specifies the outputs to which an application sends the log events of the Debug level and higher (that is, log events of the Standard, Interaction, Trace, and Debug levels). The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
  • Default value

    ../logs/ccp

    Takes effect immediately

    verbose

    Verbose Level

    Determines whether a log output is created. If it is, specifies the minimum level of log events generated. The log events levels, starting with the highest priority level, are Standard, Interaction, Trace, and Debug.

    Valid values

    • all
    • debug
    • trace
    • interaction
    • standard
    • none
  • all All log events (that is, log events of the Standard, Trace,Interaction, and Debug levels) are generated.
  • debug The same as all.
  • trace Log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels) are generated, but log events of the Debug level are not generated.
  • interaction Log events of the Interaction level and higher (that is, log events of the Standard and Interaction levels) are generated, but log events of the Trace and Debug levels are not generated.
  • standard Log events of the Standard level are generated, but log events of the Interaction, Trace, and Debug levels are not generated.
  • none No output is produced.
  • Default value

    interaction

    Takes effect immediately

    [mediacontroller]

    allow_dialog_transfer

    Allow Dialog transfer

    Allows SIP dialog transfer. If this parameter is set to false, all incoming SIP REFER will be automatically rejected with SIP 403. Otherwise, the request will be forward to the CCXML application.

    Valid values

    • 1
    • 0
  • true Enable transfers through dialog
  • false Disable transfers through dialog
  • Default value

    1

    Takes effect immediately

    bridge_server

    Address of bridge server

    The address of SIP Bridge Server for use when the two end-points cannot be joined due to media bridging limitations.
    Bridge Server must be able to
  • send media to multiple end-points
  • send and receive from distinct end-points and
  • have transcoding capability.
  • Valid values

    A valid IP address:Port can only contain alphanumeric characters, '.', '-', ':', ' ','/' and '\' characters

    Default value

    $LocalIP$:5060

    Takes effect immediately

    bridge_server.defaultmaxsize

    Bridge Server Default Max Size

    This controls the confmaxsize URI parameter when conference is set up in the bridge server.

    Valid values

    From 1 to 1000 inclusive

    Default value

    4

    Takes effect immediately

    bridge_server.defaultreserve

    Bridge Server Default Reserve

    This controls the confreserve URI parameter when conference is set up in the bridge server.

    Valid values

    From 1 to 1000 inclusive

    Default value

    4

    Takes effect immediately

    bridge_server.profile

    Device Profile of bridge server

    The name of device profile to use with the configured Bridge Server.

    Default value

    Default Conference

    Takes effect immediately

    bridge_sips_server

    Address of sip secure bridge server

    The address of SIP secure Bridge Server for use when the two end-points cannot be joined due to media bridging limitations.
    Bridge Server must be able to
  • send media to multiple end-points
  • send and receive from distinct end-points and
  • have transcoding capability.
  • Valid values

    A valid IP address:Port can only contain alphanumeric characters, '.', '-', ':', ' ','/' and '\' characters

    Default value

    $LocalIP$:5061

    Takes effect immediately

    codec_check_exclusion.payloads

    Codec checking exclusion payload list

    A list of space delimited payloads that will be excluded during codec checking for join result determination.

    Default value

    13

    Takes effect immediately

    conference.defaultreserve

    Default reserve for conference server

    Default URI confreserve parameter for conference server if requested reserve size is not defined

    Default value

    8

    Takes effect immediately

    defaultrejectcode

    Default Reject Code

    Specifies the default SIP Response code to use when an incoming call is rejected by the application

    Default value

    480

    Takes effect immediately

    full_audio_codec

    Full Audio codec

    This defines the audio codecs that get set in the SDP in an initial offer with no media bridge. Codec entry has to be in the format of: payload|name|mime|rate|#channels. Each codec entry is separated by a whitespace.

    Default value

    0|pcmu|audio/basic|8000|1 8|pcma|audio/x-alaw-basic|8000|1 9|g722|audio/g722|8000|1 23|g726-16|audio/g726-16|8000|1 22|g726-16|audio/g726-16|8000|1 2|g726-32|audio/g726|8000|1 125|g726-40|audio/g726-40|8000|1 18|g729|audio/g729|8000|1 3|gsm|audio/x-gsm|8000|1 105|AMR|audio/AMR|8000|1 112|AMR-WB|audio/AMR-WB|16000|1 101|telephone-event|none|8000|1

    Takes effect immediately

    full_video_codec

    Full Video codec

    This defines the video codecs that get set in the SDP in an initial offer with no media bridge. Codec entry has to be in the format of: payload|name|mime|rate|#channels. Each codec entry is separated by a whitespace.

    Default value

    34|h263|video/H263|90000|1 99|h263-1998|video/H263-1998|90000|1 113|H264|video/H264|90000|1

    Takes effect immediately

    inbound_allowed_media

    Inbound allowed Media

    The default allowed media types for an inbound call. All inbound calls will be limited to this set of media types in terms of SDP exchange. If set to dynamic, media type is determined from the capability SDP of the inbound call (if capability SDP is not available, it defaults to audio and video).

    Valid values

    • dynamic
    • audio video
    • audio
    • video
    Must be one of the following:
  • dynamic
  • audio video
  • audio
  • video
  • Default value

    dynamic

    Takes effect immediately

    sdp.defaultipversion

    SDP default IP version

    Default IP version to be used in SDP message, apply to initiated SDP offer to unjoined endpoint. Valid values are "ipv4" or "ipv6".

    Valid values

    • ipv4
    • ipv6

    Default value

    true

    Takes effect immediately

    sdp.localhost

    SDP localhost

    The local host IPv4 address (only the host part) that will be used in SDP.

    Default value

    $LocalIP$

    Takes effect immediately

    sdp.localhost.ipv6

    SDP localhost.ipv6

    The local host IPv6 address (only the host part) that will be used in SDP.

    Default value

    $LocalIPv6$

    Takes effect immediately

    sip.allowedunknownheaders

    Unknown headers allowed for a SIP message

    This parameter takes a space delimited list of acceptable unknown header list. Unknown headers received from SIP messages that are not part of this list will be ignored. It will not be accessable from the application. Specifying a wilcard (*) means all unknown headers are allowed.

    Default value

    *

    Takes effect immediately

    sipproxy

    SIP Proxy

    The address of SIP Proxy for outbound SIP requests. Should be specified like 10.10.30.205:5070

    Valid values

    A valid IP address:Port can only contain alphanumeric characters, '.', '-', ':', ' ','/' and '\' characters

    Default value

    $LocalIP$:5060

    Takes effect immediately

    sipsecure

    Using SIP Secure protocol for out going calls.

    If this flag is set to true, all the outbound sip requests would be in SIP secure protocol. Note, the hints attribute of the CCXML elements that initiates an out bound request can over write this configuration.

    Valid values

    • 1
    • 0
  • true Using SIP Secure protocol
  • false Not using SIP Secure protocol
  • Default value

    0

    Takes effect immediately

    sipsproxy

    SIP Secure Proxy

    The address of SIP Secure Proxy for outbound SIP requests. Should be specified like 10.10.30.205:5071

    Valid values

    A valid IP address:Port can only contain alphanumeric characters, '.', '-', ':', ' ','/' and '\' characters

    Default value

    $LocalIP$:5061

    Takes effect immediately

    [session]

    copy_unknown_headers

    Copy unknown headers

    Copy unknown headers from request to all responses. If this parameter is turned on, all unknown SIP headers found in SIP request will be automatically copied to its responses. When the flag is set to true, unknown Headers will be copied, and if the flag is set to false, unknown headers will not be copied.

    Valid values

    • true
    • false

    Default value

    true

    Takes effect immediately

    [sip]

    copyunknownheaders

    Copy Unknown Headers

    Copy unknown headers from request to all responses. If this parameter is turned on, all unknown SIP headers found in SIP request will be automatically copied to its responses. 0 is disable and 1 is enable.

    Valid values

    • 0
    • 1

    Default value

    1

    Takes effect At start/restart

    localuser

    Contact Header User Name

    Configures the user name portion of the Contact header generated from the platform.

    Default value

    Genesys

    Takes effect At start/restart

    maxtcpconnections

    Maximum TCP Connections

    Defines the maximum number of TCP connections concurrently established. If the maximum number of TCP connections has been reached, new SIP requests to establish TCP connections will be rejected

    Valid values

    The maximum number of connections must be between 1 and 10000

    Default value

    100

    Takes effect At start/restart

    maxtlsconnections

    Maximum TLS Connections

    Defines the maximum number of TLS connections concurrently established. If the maximum number of TLS connections has been reached, new SIP requests to establish TLS connections will be rejected

    Valid values

    The maximum number of TLS connections must be between 1 and 10000

    Default value

    100

    Takes effect At start/restart

    min_se

    Minimum Session Expire Time

    Defines the Min-SE parameter in seconds. This is the minimum duration of session expiry this SIP stack will accept from a user agent client.

    Valid values

    The parameter size must be between 90 and 3600

    Default value

    90

    Takes effect At start/restart

    mtusize

    MTU Size

    Defines the Maximum Transmission Unit (MTU) of the network interfaces. If a SIP request size is within 200 bytes of this value, the request will be sent on a congestion controlled transport protocol, such as TCP.

    Valid values

    The MTU size must be between 1 and 65535

    Default value

    1500

    Takes effect At start/restart

    OPTIONS.header.Accept

    OPTIONS header Accept

    This defines the Accept header value in the SIP OPTIONS response.

    Default value

    application/sdp

    Takes effect immediately

    OPTIONS.header.Accept-Encoding

    OPTIONS header Accept-Encoding

    This defines the Accept-Encoding header value in the SIP OPTIONS response.

    Default value

    (blank)

    Takes effect immediately

    OPTIONS.header.Accept-Language

    OPTIONS header Accept-Language

    This defines the Accept-Language header value in the SIP OPTIONS response

    Default value

    en

    Takes effect immediately

    OPTIONS.header.Allow

    OPTIONS header Allow

    This defines the Allow header value in the SIP OPTIONS response.

    Default value

    INVITE,ACK,CANCEL,BYE,OPTIONS,INFO

    Takes effect immediately

    OPTIONS.header.Supported

    OPTIONS header Supported

    This defines the Supported header value in the SIP OPTIONS response.

    Default value

    (blank)

    Takes effect immediately

    prack.support

    Enable Reliable Provisional Responses

    This parameter will allow the SIP Stack to send reliable the 101-199 provisional responses. The parameter value of 1 or 2 will enable the PRACK support. If the parameter value is set to 2 the CCP will include the "100rel" extension in the Require header of the outbound INVITE request, forcing a remote user that supports PRACK method to sent the provisional responses reliable. If the parameter value is set to 1, the "100rel" extension will be included in the Supported header of the outbound INVITE request giving the remote user the option to send or not the provisional responses reliable. The default parameter value is 0.

    Valid values

    • 0
    • 1
    • 2

    Default value

    0

    Takes effect At start/restart

    preferred_ipversion

    Preferred IP version to be used in SIP

    Preferred IP version to be used in SIP. When multiple IP addresses with different IP versions are resolved from a destination address, the first address from the list with the preferred IP version will be used. However, if there is no sip.transport defined for the preferred version, other version will be used. Valid values are "ipv4" and "ipv6".

    Valid values

    • ipv4
    • ipv6

    Default value

    ipv4

    Takes effect At start/restart

    registerexpiryadjustment

    Register Expiry Adjustment

    Specifies the amount of time (in seconds) that the platform should re-register with the configured registrars before their respective expiration times are reached

    Valid values

    sip.registerexpiryadjustment should be non-negative integer

    Default value

    10

    Takes effect At start/restart

    route.default.tcp

    Default IPv4 route for TCP

    Default IPv4 route for TCP. The number denotes the transport defined in sip.transport.x where x is the value of this parameter and will be used when no IPv4 TCP routes are found.

    Default value

    (blank)

    Takes effect At start/restart

    route.default.tcp.ipv6

    Default IPv6 route for TCP

    Default IPv6 route for TCP. The number denotes the transport defined in sip.transport.x where x is the value of this parameter and will be used when no IPv6 TCP routes are found. If this parameter is not set, the first IPv6 TCP transport found in sip.transport.x becomes the default.

    Default value

    (blank)

    Takes effect At start/restart

    route.default.tls

    Default IPv4 route for TLS

    Default IPv4 route for TLS. The number denotes the transport defined in sip.transport.x where x is the value of this parameter and will be used when no IPv4 TLS routes are found.

    Default value

    (blank)

    Takes effect At start/restart

    route.default.tls.ipv6

    Default IPv6 route for TLS

    Default IPv6 route for TLS. The number denotes the transport defined in sip.transport.x where x is the value of this parameter and will be used when no IPv6 TLS routes are found. If this parameter is not set, the first IPv6 TLS transport found in sip.transport.x becomes the default.

    Default value

    (blank)

    Takes effect At start/restart

    route.default.udp

    Default IPv4 route for UDP

    Default IPv4 route for UDP. The number denotes the transport defined in sip.transport.x where x is the value of this parameter and will be used when no IPv4 UDP routes are found.

    Default value

    (blank)

    Takes effect At start/restart

    route.default.udp.ipv6

    Default IPv6 route for UDP

    Default IPv6 route for UDP. The number denotes the transport defined in sip.transport.x where x is the value of this parameter and will be used when no IPv6 UDP routes are found. If this parameter is not set, the first IPv6 UDP transport found in sip.transport.x becomes the default.

    Default value

    (blank)

    Takes effect At start/restart

    route.dest.0

    Route Destination Instance 0

    This is an entry in routing table.
    Format: sip.route.dest.x=[Destination] [Netmask] [Transport] [Metric]
    To select an entry in routing table, we mask the outgoing IP Address with [Netmask]; if the result matches with the [Destination], we will accept that route. The [Transport] part determines the transport to use and maps to the index 'x' in one of the transports defined as sip.transport.x. In most of the cases, first accepted route will be used. Unless the protocol is specified or required (for example, when the message size is larger than mtusize, tcp is required to be used), the accepted route in routing table is also required to have matched protocol. If there.s no such route, default transport of that protocol will be used.
    If all cases failed, sip.transport.0.s protocol will be obtained. The default transport of the obtained protocol will be used.
    Note that [Metric] entry is needed but not used at this point.
    For example: sip.route.dest.0=138.120.72.0 255.255.255.0 1 0
    For example (ipv6): sip.route.dest.0=2620:0:60:: FFFF:FFFF:FFFF:: 0 0 When we make a call to the machine 138.120.72.20, outgoing IP is masked with [netmask] using .bitwise AND. operator. In this case: 138.120.72.20 & 255.255.255.0 gives 138.120.72.0. This matches the defined [Destination] in the route. Therefore, transport in sip.transport.1 will be used.

    Default value

    (blank)

    Takes effect At start/restart

    route.dest.1

    Route Destination Instance 1

    This is an entry in routing table.
    Format: sip.route.dest.x=[Destination] [Netmask] [Transport] [Metric]
    To select an entry in routing table, we mask the outgoing IP Address with [Netmask]; if the result matches with the [Destination], we will accept that route. The [Transport] part determines the transport to use and maps to the index 'x' in one of the transports defined as sip.transport.x. In most of the cases, first accepted route will be used. Unless the protocol is specified or required (for example, when the message size is larger than mtusize, tcp is required to be used), the accepted route in routing table is also required to have matched protocol. If there.s no such route, default transport of that protocol will be used.
    If all cases failed, sip.transport.0.s protocol will be obtained. The default transport of the obtained protocol will be used.
    Note that [Metric] entry is needed but not used at this point.
    For example: sip.route.dest.0=138.120.72.0 255.255.255.0 1 0
    For example (ipv6): sip.route.dest.0=2620:0:60:: FFFF:FFFF:FFFF:: 0 0 When we make a call to the machine 138.120.72.20, outgoing IP is masked with [netmask] using .bitwise AND. operator. In this case: 138.120.72.20 & 255.255.255.0 gives 138.120.72.0. This matches the defined [Destination] in the route. Therefore, transport in sip.transport.1 will be used.

    Default value

    (blank)

    Takes effect At start/restart

    route.dest.2

    Route Destination Instance 2

    This is an entry in routing table.
    Format: sip.route.dest.x=[Destination] [Netmask] [Transport] [Metric]
    To select an entry in routing table, we mask the outgoing IP Address with [Netmask]; if the result matches with the [Destination], we will accept that route. The [Transport] part determines the transport to use and maps to the index 'x' in one of the transports defined as sip.transport.x. In most of the cases, first accepted route will be used. Unless the protocol is specified or required (for example, when the message size is larger than mtusize, tcp is required to be used), the accepted route in routing table is also required to have matched protocol. If there.s no such route, default transport of that protocol will be used.
    If all cases failed, sip.transport.0.s protocol will be obtained. The default transport of the obtained protocol will be used.
    Note that [Metric] entry is needed but not used at this point.
    For example: sip.route.dest.0=138.120.72.0 255.255.255.0 1 0
    For example (ipv6): sip.route.dest.0=2620:0:60:: FFFF:FFFF:FFFF:: 0 0 When we make a call to the machine 138.120.72.20, outgoing IP is masked with [netmask] using .bitwise AND. operator. In this case: 138.120.72.20 & 255.255.255.0 gives 138.120.72.0. This matches the defined [Destination] in the route. Therefore, transport in sip.transport.1 will be used.

    Default value

    (blank)

    Takes effect At start/restart

    route.dest.3

    Route Destination Instance 3

    This is an entry in routing table.
    Format: sip.route.dest.x=[Destination] [Netmask] [Transport] [Metric]
    To select an entry in routing table, we mask the outgoing IP Address with [Netmask]; if the result matches with the [Destination], we will accept that route. The [Transport] part determines the transport to use and maps to the index 'x' in one of the transports defined as sip.transport.x. In most of the cases, first accepted route will be used. Unless the protocol is specified or required (for example, when the message size is larger than mtusize, tcp is required to be used), the accepted route in routing table is also required to have matched protocol. If there.s no such route, default transport of that protocol will be used.
    If all cases failed, sip.transport.0.s protocol will be obtained. The default transport of the obtained protocol will be used.
    Note that [Metric] entry is needed but not used at this point.
    For example: sip.route.dest.0=138.120.72.0 255.255.255.0 1 0
    For example (ipv6): sip.route.dest.0=2620:0:60:: FFFF:FFFF:FFFF:: 0 0 When we make a call to the machine 138.120.72.20, outgoing IP is masked with [netmask] using .bitwise AND. operator. In this case: 138.120.72.20 & 255.255.255.0 gives 138.120.72.0. This matches the defined [Destination] in the route. Therefore, transport in sip.transport.1 will be used.

    Default value

    (blank)

    Takes effect At start/restart

    route.dest.4

    Route Destination Instance 4

    This is an entry in routing table.
    Format: sip.route.dest.x=[Destination] [Netmask] [Transport] [Metric]
    To select an entry in routing table, we mask the outgoing IP Address with [Netmask]; if the result matches with the [Destination], we will accept that route. The [Transport] part determines the transport to use and maps to the index 'x' in one of the transports defined as sip.transport.x. In most of the cases, first accepted route will be used. Unless the protocol is specified or required (for example, when the message size is larger than mtusize, tcp is required to be used), the accepted route in routing table is also required to have matched protocol. If there.s no such route, default transport of that protocol will be used.
    If all cases failed, sip.transport.0.s protocol will be obtained. The default transport of the obtained protocol will be used.
    Note that [Metric] entry is needed but not used at this point.
    For example: sip.route.dest.0=138.120.72.0 255.255.255.0 1 0
    For example (ipv6): sip.route.dest.0=2620:0:60:: FFFF:FFFF:FFFF:: 0 0 When we make a call to the machine 138.120.72.20, outgoing IP is masked with [netmask] using .bitwise AND. operator. In this case: 138.120.72.20 & 255.255.255.0 gives 138.120.72.0. This matches the defined [Destination] in the route. Therefore, transport in sip.transport.1 will be used.

    Default value

    (blank)

    Takes effect At start/restart

    route.dest.5

    Route Destination Instance 5

    This is an entry in routing table.
    Format: sip.route.dest.x=[Destination] [Netmask] [Transport] [Metric]
    To select an entry in routing table, we mask the outgoing IP Address with [Netmask]; if the result matches with the [Destination], we will accept that route. The [Transport] part determines the transport to use and maps to the index 'x' in one of the transports defined as sip.transport.x. In most of the cases, first accepted route will be used. Unless the protocol is specified or required (for example, when the message size is larger than mtusize, tcp is required to be used), the accepted route in routing table is also required to have matched protocol. If there.s no such route, default transport of that protocol will be used.
    If all cases failed, sip.transport.0.s protocol will be obtained. The default transport of the obtained protocol will be used.
    Note that [Metric] entry is needed but not used at this point.
    For example: sip.route.dest.0=138.120.72.0 255.255.255.0 1 0
    For example (ipv6): sip.route.dest.0=2620:0:60:: FFFF:FFFF:FFFF:: 0 0 When we make a call to the machine 138.120.72.20, outgoing IP is masked with [netmask] using .bitwise AND. operator. In this case: 138.120.72.20 & 255.255.255.0 gives 138.120.72.0. This matches the defined [Destination] in the route. Therefore, transport in sip.transport.1 will be used.

    Default value

    (blank)

    Takes effect At start/restart

    routeset

    Route Set

    Defines a SIP route set for outbound calls. If defined, this route set will be inserted as the ROUTE header for all outgoing calls. This will force the platform to send the SIP messages via this defined route set.

    Each element in the routeset should be seperated by a comma. This parameter can be used to define outbound proxies. Note that this routeset does not apply to SIP REGISTER messages.

    sip.routeset = <sip:ip/host;priority>, ... e.g. sip.routeset=<sip:p1.example.com;lr>,<sip:p2.domain.com;lr>

    In this example, the Genesys Voice platform will route the request to p1.example.com, which will in turn route the message to p2.domain.com, and finally be redirected to its intended destination.

    Valid values

    A valid routeset must have the format as specify in its description

    Default value

    (blank)

    Takes effect At start/restart

    securerouteset

    Secure Route Set

    Defines a SIPS route set for SIPS outbound calls. If defined, this route set will be inserted as the ROUTE header for all outgoing calls. This will force the platform to send the SIP messages via this defined route set.

    Each element in the routeset should be seperated by a comma. This parameter can be used to define outbound proxies. Note that this routeset does not apply to SIP REGISTER messages.

    sip.securerouteset = <sips:ip/host;priority>, ... e.g. sip.securerouteset=<sips:p1.example.com;lr>,<sips:p2.domain.com;lr>

    In this example, the Genesys Voice platform will route the request to p1.example.com, which will in turn route the message to p2.domain.com, and finally be redirected to its intended destination.

    Valid values

    A valid secure routeset must have the format as specify in its description

    Default value

    (blank)

    Takes effect At start/restart

    sessionexpires

    Session Expires

    Defines the default session expiry value in seconds. The session timer defines the duration of which a SIP session will expire if no re-INVITEs are sent/received within this period.

    Valid values

    The parameter size must be between 90 and 3600

    Default value

    1800

    Takes effect At start/restart

    tcp.portrange

    Local TCP port range

    The local TCP port range to be used for SIP transport. If this parameter is not specified, CCP will let the OS choose the local port.

    Valid values

    Possible values are the empty string or low-high, where low and high are integers from 1030 to 65535 inclusive

    Default value

    (blank)

    Takes effect At start/restart

    threadpoolsize

    Threadpool Size

    The size of the thread pool for handling DNS queries.

    Valid values

    The size of the thread pool for handling DNS queries

    Default value

    4

    Takes effect At start/restart

    threads

    Number of Worker Threads

    Specifies the number of worker threads that handles the SIP requests arriving from the SIP transport layer. If the value is 0, all requests are handled within the arriving transport layer thread. Otherwise, all arriving requests are handled by hashing onto the N number of worker threads.

    Default value

    0

    Takes effect After restart

    timer.ci_proceeding

    Client Invite Proceeding Timer

    Defines the client INVITE proceeding timer in milliseconds, default value is 120000. The timer starts after a 1xx response is received for a client INVITE. If a final response is not received before the timer expires, the SIP session and dialog will be destroyed without further notice to the UAS. Note that the CI proceeding timer should be configured to be greater than the connect timeout. This ensures that a CANCEL will be sent to terminate the SIP session properly when connect timeout occurs.

    Valid values

    sip.timer.ci_proceeding must be greater than 0

    Default value

    120000

    Takes effect At start/restart

    tls.portrange

    Local TLS port range

    The local TLS port range to be used for SIP transport. If this parameter is not specified, CCP will let the OS choose the local port.

    Valid values

    Possible values are the empty string or low-high, where low and high are integers from 1030 to 65535 inclusive

    Default value

    (blank)

    Takes effect At start/restart

    transport.0

    Transport Instance 0

    defines transport layer for SIP stack and the network interfaces that are used to process SIP requests Format: sip.transport.x = transport_name
    type:ip:port [parameters]

    where transport_name is any string; type is udp/tcp/tls; ip is the IP address of the network interface that accepts incoming SIP messages; If ip is an IPv6 address, [] must be used. To define a transport to listen to all IPv4 interfaces, use "any" or "any4" for ip. To define a transport to listen to all IPv6 interfaces, use "any6" for ip. port is the port number where SIP stack accepts incoming SIP messages;
    [parameters] defines any extra SIP transport parameters. Note that this is for LMSIP2.

    Example:
    cert=[cert path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS certificate to be used key=[key path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS key to be used. type=[Type of secure transport] Applicable to SIPS only and is optional. The type of secure transport to be used and value can be TLSv1, SSLv2, SSLv3, SSLv23. Default to SSLv23. password=[password] Applicable to SIPS only and is optional. The password associated with the certificate and key pair. Required only if key file is password protected. cafile=[CA cert path and filename] Mandatory for TLS mutual authentication. The path and the filename of the certificate to be used for verifying the peer. The same certificate specified in cert=[cert path and filename] parameter can be used as the value here if using only 1 certificate is preferred. verifypeer=true Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. verifydepth=[max depth for the certificate chain verification] Applicable only to TLS mutual authentication. This parameter sets the maximum depth for the certificate chain verification. For the default Genesys certificate provided, the recommended value is 1.

    Default value

    transport0 udp:any:5068

    Takes effect At start/restart

    transport.0.tos

    IP Type of Service for transport instance 0

    Specifies the IP Differentiaed Services Field (also known as ToS) to set in all outgoing SIP packets over transport instance 0. Note that this configuration does not work for Windows 2008. For Windows 2008, the setting needs to be configured at the OS level through the policy settings. Please refer to the GVP User's Guide.

    Valid values

    Possible values are integers from 0 to 255 inclusive.

    Default value

    0

    Takes effect At start/restart

    transport.1

    Transport Instance 1

    defines transport layer for SIP stack and the network interfaces that are used to process SIP requests Format: sip.transport.x = transport_name
    type:ip:port [parameters]

    where transport_name is any string; type is udp/tcp/tls; ip is the IP address of the network interface that accepts incoming SIP messages; If ip is an IPv6 address, [] must be used. To define a transport to listen to all IPv4 interfaces, use "any" or "any4" for ip. To define a transport to listen to all IPv6 interfaces, use "any6" for ip. port is the port number where SIP stack accepts incoming SIP messages;
    [parameters] defines any extra SIP transport parameters. Note that this is for LMSIP2.

    Example:
    cert=[cert path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS certificate to be used key=[key path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS key to be used. type=[Type of secure transport] Applicable to SIPS only and is optional. The type of secure transport to be used and value can be TLSv1, SSLv2, SSLv3, SSLv23. Default to SSLv23. password=[password] Applicable to SIPS only and is optional. The password associated with the certificate and key pair. Required only if key file is password protected. cafile=[CA cert path and filename] Mandatory for TLS mutual authentication. The path and the filename of the certificate to be used for verifying the peer. The same certificate specified in cert=[cert path and filename] parameter can be used as the value here if using only 1 certificate is preferred. verifypeer=true Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. verifydepth=[max depth for the certificate chain verification] Applicable only to TLS mutual authentication. This parameter sets the maximum depth for the certificate chain verification. For the default Genesys certificate provided, the recommended value is 1.

    Default value

    transport1 tcp:any:5068

    Takes effect At start/restart

    transport.1.tos

    IP Type of Service for transport instance 1

    Specifies the IP Differentiaed Services Field (also known as ToS) to set in all outgoing SIP packets over transport instance 1. Note that this configuration does not work for Windows 2008. For Windows 2008, the setting needs to be configured at the OS level through the policy settings. Please refer to the GVP User's Guide.

    Valid values

    Possible values are integers from 0 to 255 inclusive.

    Default value

    0

    Takes effect At start/restart

    transport.2

    Transport Instance 2

    defines transport layer for SIP stack and the network interfaces that are used to process SIP requests Format: sip.transport.x = transport_name
    type:ip:port [parameters]

    where transport_name is any string; type is udp/tcp/tls; ip is the IP address of the network interface that accepts incoming SIP messages; If ip is an IPv6 address, [] must be used. To define a transport to listen to all IPv4 interfaces, use "any" or "any4" for ip. To define a transport to listen to all IPv6 interfaces, use "any6" for ip. port is the port number where SIP stack accepts incoming SIP messages;
    [parameters] defines any extra SIP transport parameters. Note that this is for LMSIP2.

    Example:
    cert=[cert path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS certificate to be used key=[key path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS key to be used. type=[Type of secure transport] Applicable to SIPS only and is optional. The type of secure transport to be used and value can be TLSv1, SSLv2, SSLv3, SSLv23. Default to SSLv23. password=[password] Applicable to SIPS only and is optional. The password associated with the certificate and key pair. Required only if key file is password protected. cafile=[CA cert path and filename] Mandatory for TLS mutual authentication. The path and the filename of the certificate to be used for verifying the peer. The same certificate specified in cert=[cert path and filename] parameter can be used as the value here if using only 1 certificate is preferred. verifypeer=true Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. verifydepth=[max depth for the certificate chain verification] Applicable only to TLS mutual authentication. This parameter sets the maximum depth for the certificate chain verification. For the default Genesys certificate provided, the recommended value is 1.

    Default value

    transport2 tls:any:5069 cert=$InstallationRoot$/config/x509_certificate.pem key=$InstallationRoot$/config/x509_private_key.pem

    Takes effect At start/restart

    transport.2.tos

    IP Type of Service for transport instance 2

    Specifies the IP Differentiaed Services Field (also known as ToS) to set in all outgoing SIP packets over transport instance 2. Note that this configuration does not work for Windows 2008. For Windows 2008, the setting needs to be configured at the OS level through the policy settings. Please refer to the GVP User's Guide.

    Valid values

    Possible values are integers from 0 to 255 inclusive.

    Default value

    0

    Takes effect At start/restart

    transport.3

    Transport Instance 3

    defines transport layer for SIP stack and the network interfaces that are used to process SIP requests Format: sip.transport.x = transport_name
    type:ip:port [parameters]

    where transport_name is any string; type is udp/tcp/tls; ip is the IP address of the network interface that accepts incoming SIP messages; If ip is an IPv6 address, [] must be used. To define a transport to listen to all IPv4 interfaces, use "any" or "any4" for ip. To define a transport to listen to all IPv6 interfaces, use "any6" for ip. port is the port number where SIP stack accepts incoming SIP messages;
    [parameters] defines any extra SIP transport parameters. Note that this is for LMSIP2.

    Example:
    cert=[cert path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS certificate to be used key=[key path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS key to be used. type=[Type of secure transport] Applicable to SIPS only and is optional. The type of secure transport to be used and value can be TLSv1, SSLv2, SSLv3, SSLv23. Default to SSLv23. password=[password] Applicable to SIPS only and is optional. The password associated with the certificate and key pair. Required only if key file is password protected. cafile=[CA cert path and filename] Mandatory for TLS mutual authentication. The path and the filename of the certificate to be used for verifying the peer. The same certificate specified in cert=[cert path and filename] parameter can be used as the value here if using only 1 certificate is preferred. verifypeer=true Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. verifydepth=[max depth for the certificate chain verification] Applicable only to TLS mutual authentication. This parameter sets the maximum depth for the certificate chain verification. For the default Genesys certificate provided, the recommended value is 1.

    Default value

    (blank)

    Takes effect At start/restart

    transport.3.tos

    IP Type of Service for transport instance 3

    Specifies the IP Differentiaed Services Field (also known as ToS) to set in all outgoing SIP packets over transport instance 3. Note that this configuration does not work for Windows 2008. For Windows 2008, the setting needs to be configured at the OS level through the policy settings. Please refer to the GVP User's Guide.

    Valid values

    Possible values are integers from 0 to 255 inclusive.

    Default value

    0

    Takes effect At start/restart

    transport.4

    Transport Instance 4

    defines transport layer for SIP stack and the network interfaces that are used to process SIP requests Format: sip.transport.x = transport_name
    type:ip:port [parameters]

    where transport_name is any string; type is udp/tcp/tls; ip is the IP address of the network interface that accepts incoming SIP messages; If ip is an IPv6 address, [] must be used. To define a transport to listen to all IPv4 interfaces, use "any" or "any4" for ip. To define a transport to listen to all IPv6 interfaces, use "any6" for ip. port is the port number where SIP stack accepts incoming SIP messages;
    [parameters] defines any extra SIP transport parameters. Note that this is for LMSIP2.

    Example:
    cert=[cert path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS certificate to be used key=[key path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS key to be used. type=[Type of secure transport] Applicable to SIPS only and is optional. The type of secure transport to be used and value can be TLSv1, SSLv2, SSLv3, SSLv23. Default to SSLv23. password=[password] Applicable to SIPS only and is optional. The password associated with the certificate and key pair. Required only if key file is password protected. cafile=[CA cert path and filename] Mandatory for TLS mutual authentication. The path and the filename of the certificate to be used for verifying the peer. The same certificate specified in cert=[cert path and filename] parameter can be used as the value here if using only 1 certificate is preferred. verifypeer=true Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. verifydepth=[max depth for the certificate chain verification] Applicable only to TLS mutual authentication. This parameter sets the maximum depth for the certificate chain verification. For the default Genesys certificate provided, the recommended value is 1.

    Default value

    (blank)

    Takes effect At start/restart

    transport.4.tos

    IP Type of Service for transport instance 4

    Specifies the IP Differentiaed Services Field (also known as ToS) to set in all outgoing SIP packets over transport instance 4. Note that this configuration does not work for Windows 2008. For Windows 2008, the setting needs to be configured at the OS level through the policy settings. Please refer to the GVP User's Guide.

    Valid values

    Possible values are integers from 0 to 255 inclusive.

    Default value

    0

    Takes effect At start/restart

    transport.5

    Transport Instance 5

    defines transport layer for SIP stack and the network interfaces that are used to process SIP requests Format: sip.transport.x = transport_name
    type:ip:port [parameters]

    where transport_name is any string; type is udp/tcp/tls; ip is the IP address of the network interface that accepts incoming SIP messages; If ip is an IPv6 address, [] must be used. To define a transport to listen to all IPv4 interfaces, use "any" or "any4" for ip. To define a transport to listen to all IPv6 interfaces, use "any6" for ip. port is the port number where SIP stack accepts incoming SIP messages;
    [parameters] defines any extra SIP transport parameters. Note that this is for LMSIP2.

    Example:
    cert=[cert path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS certificate to be used key=[key path and filename] Applicable to SIPS only and mandatory if using SIPS. The path and the filename of the TLS key to be used. type=[Type of secure transport] Applicable to SIPS only and is optional. The type of secure transport to be used and value can be TLSv1, SSLv2, SSLv3, SSLv23. Default to SSLv23. password=[password] Applicable to SIPS only and is optional. The password associated with the certificate and key pair. Required only if key file is password protected. cafile=[CA cert path and filename] Mandatory for TLS mutual authentication. The path and the filename of the certificate to be used for verifying the peer. The same certificate specified in cert=[cert path and filename] parameter can be used as the value here if using only 1 certificate is preferred. verifypeer=true Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. verifydepth=[max depth for the certificate chain verification] Applicable only to TLS mutual authentication. This parameter sets the maximum depth for the certificate chain verification. For the default Genesys certificate provided, the recommended value is 1.

    Default value

    (blank)

    Takes effect At start/restart

    transport.5.tos

    IP Type of Service for transport instance 5

    Specifies the IP Differentiaed Services Field (also known as ToS) to set in all outgoing SIP packets over transport instance 5. Note that this configuration does not work for Windows 2008. For Windows 2008, the setting needs to be configured at the OS level through the policy settings. Please refer to the GVP User's Guide.

    Valid values

    Possible values are integers from 0 to 255 inclusive.

    Default value

    0

    Takes effect At start/restart

    transport.dnsharouting

    DNS HA Routing

    Specifies whether the DNS HA routing based on RFC3263 should be turned on. If turned off, alternate records returned from the DNS query will not be tried. Otherwise, alternate records returned from the DNS query will be tried based on RFC3263.

    Valid values

    • true
    • false

    Default value

    false

    Takes effect At start/restart

    transport.localaddress

    Local Transport IPv4 Address

    If specified, the sent-by field of the Via header and the hostport part of the Contact header in the outgoing SIP message will be set to this value if a IPv4 transport is used. The value must be a hostname or domain name. If left empty the outgoing transport's actual IP and port will be used for the Via header and the Contact header. Note that if the domain name used in the SRV record query is specified, sip.transport.localaddress.srv must be set to true to prevent the port part being automatically generated by the SIP stack.

    Default value

    (blank)

    Takes effect At start/restart

    transport.localaddress.srv

    Local Transport Address contains SRV domain name

    Specifies whether the sip.transport.localaddress contains an SRV domain name. If set to true, port part will not be automatically generated by the SIP stack. Otherwise, the outgoing transport's port will used together with the hostname specified by the sip.transport.localaddress.

    Valid values

    • true
    • false

    Default value

    false

    Takes effect At start/restart

    transport.localaddress_ipv6

    Local Transport IPv6 Address

    If specified, the sent-by field of the Via header and the hostport part of the Contact header in the outgoing SIP message will be set to this value if a IPv6 transport is used. The value must be a hostname or domain name. If left empty the outgoing transport's actual IP and port will be used for the Via header and the Contact header. Note that if the domain name used in the SRV record query is specified, sip.transport.localaddress.srv must be set to true to prevent the port part being automatically generated by the SIP stack.

    Default value

    (blank)

    Takes effect At start/restart

    transport.staticroutelist

    SIP Static Route List

    Specifies a list of static routes. Each route group is separated by |. Each static route group is a list of IP addresses separated by comma. Within the route group, each IP address could substitute each other as an alternate route destination if sending a SIP request to one of the IP address fails. For example, 10.0.0.1,10.0.0.2|10.0.10.1,10.0.10.2 specified two static route groups, and each group specified two routes that are alternative to each other. Default value is an empty list.

    Default value

    (blank)

    Takes effect At start/restart

    [snmp]

    SNMP settings.

    timeout

    SNMP Task Timeout

    The maximum amount of time that SNMP can wait for a new task. This value is specified in milliseconds.

    Valid values

    The parameter must be an integer value greater than zero.

    Default value

    100

    Takes effect At start/restart