[CTIC]

copy-originatingleg-headers

Copy Call Originating Leg Headers

The CTI Connector shall copy all headers matching the configured list of prefixes on to other call legs towards MCP and agent

Default value

X-Genesys-GVP-Session-Data

Takes effect After restart

CTIFramework

CTI Framework

This parameter indicates which CTI Framework to be used by CTI Connector for CTI functionalities.

Valid values

  • IVRServerClient
  • CiscoICMClient

Default value

IVRServerClient

Takes effect After restart

DefaultDNIS

Default DNIS

The value of this parameter defines Default DNIS, incase I-Server does not send DNIS.

Default value

(blank)

Takes effect After restart

disable_cdr

Disable CTI Connector's CDR update

This Parameter is included to Disable/Enable the CRD feature from CTI-C

Valid values

  • true
  • false

Default value

false

Takes effect After restart

fips_enabled

FIPS Mode Enabled

Specifies whether to enable FIPS mode in CTI Connector. 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 After restart

GetDNISFromIServer

Fetch DNIS From IVR Server

The value of this parameter indicates whether CTIConnector needs to get the DNIS value from IVR Server.

Default value

false

Takes effect After restart

IVRPortBaseIndex

IVRPort Base Index

CTI Connector would use this parameter as starting IVRport number and it would increment the IVRPort by (1). If this parameter is set to (-1) CTIC will not generate IVR Port rather it will take the port base on DNIndicator.

Default value

-1

Takes effect After restart

MaxIVRPorts

Max IVRPorts

CTI Connector would use this parameter as upper bound to generate IVRPort number.

Default value

2000

Takes effect After restart

[ems]

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|*|*' indicates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 will 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

logconfig.TRAPSINK

SNMP Trap Sink Log Filter

Specifies the metrics that are delivered to the SNMP Trap Sink.

Default value

*|*|*

Takes effect At start/restart

trace_flag

Trace Flag

Flag specifying whether debug level logging is enabled. When enabled (flag is set to TRUE), debug level logs will be processed and filtered like other log levels. When the flag is set to FALSE, debug level log messages will never be processed.

Valid values

  • FALSE
  • TRUE

Default value

FALSE

Takes effect immediately

[ICMC]

CancelResponseTimeoutMSec

Timeout for Cancel Response

CTI Connector waits for the (CONNECT/RELEASE) response to CancelResponse message from ICM for the specified time. If no response is received with in the configured time then CTIConnector shall clear the call.

Default value

2500

Takes effect After restart

ConnectMsgTimeoutMSec

Timeout for Re-Connect

CTI Connector waits for the (CONNECT_TO_RESOURCE/CONNECT/RELEASE) response from ICM for the specified time. If no response is received with in the configured time then CTIConnector shall clear the call.

Default value

3500

Takes effect After restart

DNISIndicator

DNIS mapping attribute from RUN_SCRIPT_REQ message

This parameter value indicates which field fron RUN_SCRIPT_REQ message should be used for fetching the DNIS value.

Valid values

  • sid
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10

Default value

(blank)

Takes effect After restart

eccSessionIdVarName

ECC SessionID Variable Name

CTI Connector shall take the SessionId and send it to ICM through this variable. Example : userECCVar1 The variable name configured here ("userECCVar1" in the example) should be specified in the ECC Variables list. If not, the SessionId will not be sent in the NEW_CALL message. By default, it will be set to "userSessionId" and the SessionId will be sent through userSessionId. If it is empty, the SessionId will not be sent in the NEW_CALL message.

Default value

userSessionId

Takes effect At start/restart

eccvariablelist

ECC Variables

CTI Connector shall take the configured list of ECC variable names and register it with ICM through initial REGISTER_VARIABLES message. The ECC variable names along with their tag values should be separated by comma. The ECC variable may be specified without a tag, in which case, CTIC will generate a tag for it. Example: userECCVar1:5010,userECCVar2,userECCVar3:5011 Default value is userSessionId:5000

Default value

userSessionId:5000

Takes effect At start/restart

enablePreRouting

Enable Pre-Routing

This parameter should be set to true when call is pre-routed to ICM (for Network VRU deployment type 2/3/7/8/). In this case the CTI Connector sends REQUEST_INSTRUCTION message for establishing the call with ICM.

Default value

false

Takes effect After restart

ICMInterface

ICM Interface to use

This parameter indicates about the interface that CTIC shall use to communicate with ICM. By default CTIConnector shall use the Service Control Interface to communicate with ICM.

Valid values

  • 0
  • 1

Default value

0

Takes effect After restart

NewCallTimeoutMsec

Timeout for NewCall response

CTI Connector waits for the (RUN_SCRIPT_REQ/CONNECT/RELEASE) response to NEW_CALL message from ICM for the specified time. If no response is received with in the configured time then CTIConnector shall clear the call.

Default value

1500

Takes effect After restart

RunScriptResultTimeoutMsec

Timeout for Run Script Result response

CTI Connector waits for the (RUN_SCRIPT_REQ/CONNECT/RELEASE) response to Run Script Result message from ICM for the specified time. If no response is received with in the configured time then CTIConnector shall clear the call.

Default value

2500

Takes effect After restart

SessionIdleTimeoutMSec

Timeout for Session Idle Time

Maximum time the call will be kept active in CTIConnector, after the timeout CTIConnector will clear the call.

Default value

120000

Takes effect After restart

translation-routed-call

Use Translation Label

This parameter value indicates CTIC whether the incoming is translation routed or normal call. The default value for this parameter is false.This should be set to true for Type 8 Network VRU deployment.

Default value

false

Takes effect After restart

TrunkGroupID

Trunk Group ID

The Trunk Group ID information is sent to ICM for every call through VRU-PG for ICM reporting purpose

Default value

0

Takes effect After restart

[IServer_Sample]

clientname

IVR Client Name

The IVR Group Name on the CME

Default value

(blank)

Takes effect After restart

enablekeepalivereq

Enable KeepAlive Request

To Enable the KeepAlive Request from IVR-SC (Heartbeat IVR-SC -> IVR-Server)

Default value

0

Takes effect After restart

iserveraddr

IVR Server Host IP Address

The IP Address of the IVR Server machine

Default value

(blank)

Takes effect After restart

iserversocket

IVR Server Communication Port

The gli_server_address port on the IVR Server. Usually the port is 9090

Default value

(blank)

Takes effect After restart

IVRSCClientPortRange

Client Side TCP Port Range for IVR Server Client

This parameter defines CTI Connector TCP port range used for communication with IVR Server. The lower and upper limit is 1030 and 65535 respectively. If value is not specified then CTI Connector will let OS choose the local port value. For example : 7775-7780

Default value

(blank)

Takes effect After restart

keepalivereqinterval

KeepAlive Request Interval

The KeepAlive Request Interval

Default value

5

Takes effect After restart

keepaliveresptimeout

KeepAlive Response Timeout

KeepAlive Response Timeout

Default value

3

Takes effect After restart

noofkeepalivereqtosendinfailurecase

Number of KeepAlive Request

Number of request to be sent to IVR-Server before being marrked as unavailable

Default value

3

Takes effect After restart

[IVRSC]

customeriserverslist

Customer IVR Servers List

Lists all the IVR Servers

Default value

IServer_Sample;

Takes effect After restart

fetchscriptidfromurs

Fetch Script ID from URS

For fetching the user defined key value from framework Default is set to 0

Default value

0

Takes effect After restart

scriptidkeyname

Script ID Key Name

Key name which is configured in Framework side and which will be used in UdataGet message by IVR Server Cleint.Applicable only when IVR Server Mode set to 'Behind the Switch' Mode.

Default value

(blank)

Takes effect After 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/CTIConnector

    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/CTIConnector

    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

    20

    Takes effect immediately

    interaction

    Output for level interaction

    Specifies the outputs to which an application sends the log events of the Interaction level and higher (that is, log events of the Standard and Interaction levels). The log outputs 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/CTIConnector

    Takes effect immediately

    keep-startup-file

    Keep startup log file

    Specifies whether a startup segment of the log, containing the initial T-Server 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

    false

    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

    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.
  • 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.
  • Valid values

    • true
    • false

    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 Standard level. 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/CTIConnector

    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).
  • Local Time (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.
  • Coordinated Universal Time (utc) The time of log record generation is expressed as Coordinated Universal Time (UTC).
  • Valid values

    • local
    • 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
  • HH:MM:SS.sss (time) The time string is formatted according to the HH:MM:SS.sss (hours, minutes, seconds, and milliseconds) format.
  • According to the system's locale (locale) The time string is formatted according to the system's locale.
  • ISO 8601 format (ISO8601) The date in the time string is formatted according to the ISO 8601 format. Fractional seconds are given in milliseconds.
  • Valid values

    • time
    • locale
    • ISO8601

    Default value

    time

    Takes effect immediately

    trace

    Output for level trace

    Specifies the outputs to which an application sends the log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels). The log outputs 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/CTIConnector

    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

    standard

    Takes effect immediately

    [mediacontroller]

    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

    sdp.defaultipversion

    Default IP version in SDP

    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

    Local IPv6 Address for SDP

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

    Default value

    $LocalIPv6$

    Takes effect immediately

    suppress_bye_after_refer

    Suppress BYE after successful REFER

    Suppress BYE after successful REFER. Turn on this feature if the call flow expects to receive BYE, this will avoid BYE messages from both direction.

    Valid values

    • 1
    • 0
  • 1 Enable suppression
  • 0 Disable suppression
  • Default value

    false

    Takes effect immediately

    [session]

    [sip]

    localuser

    Contact Header User Name

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

    Default value

    CTIConnector

    Takes effect At start/restart

    mtusize

    Maximum Transmission Unit

    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.

    Default value

    1500

    Takes effect After restart

    tcp.portrange

    Local TCP Port Range

    The local TCP port range to be used for SIP transport. If this parameter is not specified, CTIC 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

    tls.portrange

    Local TLS Port Range

    The local TLS port range to be used for SIP transport. If this parameter is not specified, CTIC 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; 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.

    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:5080

    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; 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.

    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:5080

    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; 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.

    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:5081 cert=$InstallationRoot$/config/x509_certificate.pem key=$InstallationRoot$/config/x509_private_key.pem

    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

    [Tenant1]

    Ports

    Peripheral Gateway Communication Port Numbers

    List of listener port numbers separated by comma on which CTIConnector waits for TCP connection from Cisco VRU-PG. Optionally the Trunk Group IDs supported by the PIMs can also be configured here. The Trunk Group IDs can be listed for a particular PIM separated by &. For example: 6000:1&2,7000,8000:3&4 In the above example 6000 supports Trunk Group IDs 1 and 2, 7000 does not specify the TG IDs it supports and 8000 supports TGIDs 3 and 4. Note: 1) Valid range for TG IDs is 0-65535. 2) Same TG IDs should not be mentioned by more than one PIM. TG IDs should be unique across all the PIMs. 3) The value mentioned as the default TrunkGroupID under ICMC section should not be specified by any of the PIMs as a supported TG.

    Default value

    9000

    Takes effect After restart

    TenantName

    Tenant Name

    This parameter specifies the name of the Tenant.

    Default value

    (blank)

    Takes effect After restart