Jump to: navigation, search

cluster Section



  


cafile

Default Value: $InstallationRoot$/config/x509_certificate.pem
Valid Values:
Changes Take Effect: After restart


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 certfile parameter can be used as the value here if using only 1 certificate is preferred

certfile

Default Value: $InstallationRoot$/config/x509_certificate.pem
Valid Values:
Changes Take Effect: After restart


The path and the filename of the TLS server certificate to be used. The certificate should be in x509 format

certkeyfile

Default Value: $InstallationRoot$/config/x509_private_key.pem
Valid Values:
Changes Take Effect: After restart


The path and the filename of the TLS key to be used for TLS server certificate.

electiontimer

Default Value: 3000
Valid Values: Number must be from 1000 to 10000 inclusive
Changes Take Effect: After restart


Election timer in milli-seconds. If there is no response from remote member(s) for the election process after the specified milli-seconds, this node will become the master. Local resource manager will become the active node.

failoverscript

Default Value: $InstallationRoot$/bin/NLB.bat
Valid Values:
Changes Take Effect: After restart


Absolute path to the executable fail over script. For NLB: NLB.bat

ha-mode

Default Value: none
Valid Values: none, active-standby, active-active
Changes Take Effect: After restart


By default, this will be set to none (stand-alone mode). For active-standby HA configuration this parameter should be set to active-standby, where only one RM is capable of taking calls at a time. For active-active configuration this parameter should be set to active-active, where both RM instances are capable of handling requests. The configuration cluster.virtual-ip is also mandatory if running in active-standby or active-active mode.

heartbeattimer

Default Value: 2000
Valid Values:
Changes Take Effect: After restart


Heart beat interval between cluster members for determining health of each other.

hotstandby

Default Value: false
Valid Values: true, false
Changes Take Effect: After restart


This parameter has effect only if cluster.virtual-ip parameter is non-empty. If "true", this parameter mandates that the RM cluster run in hot-standby redundancy mode where call data is replicated to other RM node for SIP dialog redundancy. Otherwise, this parameter mandates that the RM cluster be run in warm-standby redundancy mode where SIP dialog redundancy is not supported, but the new requests will be handled by the other healthy RM node.

initial-electiontimer

Default Value: 10000
Valid Values: Number must be from 1000 to 60000 inclusive
Changes Take Effect: After restart


Election timer in milli-seconds for initial election during RM startup. If there is no response from remote member(s) for the election process after the specified milli-seconds, this node will become the master. Local resource manager will become the active node.

member.1

Default Value:
Valid Values:
Changes Take Effect: After restart


Describes the IP and TCP port on which the member ID 1 can be reached. The format is IP:Port where IP and Port specifies where this RM node can be reached for cluster communication.

member.2

Default Value:
Valid Values:
Changes Take Effect: After restart


Describes the IP and TCP port on which the member ID 2 can be reached. The format is IP:Port where IP and Port specifies where this RM node can be reached for cluster communication.

members

Default Value: 1 2
Valid Values:
Changes Take Effect: After restart


List of ID's of the members in the cluster (unsigned integers 1 to 32 delimited by space). For NLB, the ID's correspond to the unique host identifier (priority) number specified for each of the NLB cluster machines.

mymemberid

Default Value:
Valid Values:
Changes Take Effect: After restart


Indicates this cluster manager instance's member ID (select one among the ID's listed in cluster.members).

other-active-rmnode-ip

Default Value:
Valid Values:
Changes Take Effect: After restart


If non-empty, this parameter indicates that this RM node is part of a RM active-active cluster and the value specifies the IP address of other active RM in the same cluster. In active-active HA mode using SIP Server, this value should be configured with IP address which takes SIP traffic in other active RM node. In stand-alone, active-standby and active-active (Using load balancer like F5) HA modes, this parameter must be left empty.

tlstype

Default Value: TLSv1_2
Valid Values:
Changes Take Effect: After restart


The type of secure transport to be used and value can be TLSv1, SSLv3, SSLv23, TLSv1_1, TLSv1_2. Defaults to TLSv1_2. Note that SSLv2 is no longer supported. Note that this needs to be set to the same value on both RM nodes.

usetls

Default Value: 0
Valid Values:
Changes Take Effect: After restart


This parameter sets whether to use TCP or TLS for inter-node communication. Setting this paramter value to 0 makes RM use TCP as the transport, and TLS otherwise. Default value is '0'

verifydepth

Default Value:
Valid Values:
Changes Take Effect: After restart


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. This could be an integer. The default OpenSSL supported value is 100.

verifypeer

Default Value: false
Valid Values: true, false
Changes Take Effect: After restart


Mandatory for TLS mutual authentication. This parameter turns on the TLS mutual authentication. Defaults to false

virtual-ip

Default Value:
Valid Values:
Changes Take Effect: After restart


If non-empty, this parameter indicates that this RM node is part of a RM cluster and the value specifies the virtual IP address of the RM cluster this RM node is part of. In HA mode, this value gets written into the Record-Route and Via header (if cluster.virtual-ip-in-via is true). This parameter takes precedence over proxy.sip.transport.localaddress if both are specified. In stand-alone mode, this parameter must be left empty.

virtual-ip-in-via

Default Value: true
Valid Values: true, false
Changes Take Effect: After restart


This parameter takes effect only in HA mode. If set to true, virtual-ip will be written into the Via header when the SIP requests are forwarded. Otherwise, address specified by the proxy.sip.transport.localaddress parameter or the private IP address associated with the transport will be written into the Via header.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on July 24, 2017, at 01:06.