Jump to: navigation, search

vrmrecorder Section



  


sip.localport

Default Value: 7090
Valid Values: The port number must be from 1030 to 65535 inclusive
Changes Take Effect: At start/restart


The Local Non-secure SIP Port used by the VRMRecorder Client when SIP UDP and SIP TCP are used.

sip.localsecureport

Default Value: 7091
Valid Values: The port number must be from 1030 to 65535 inclusive
Changes Take Effect: At start/restart


The Local Secure SIP Port used by the VRMRecorder Client when SIP TLS is used.

sip.preferred_ipversion

Default Value: ipv4
Valid Values: Choose between: IPv4 or IPv6
Changes Take Effect: At start/restart


Preferred IP version to be used in SIP by the VRMRecorder. 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, the other version will be used. Valid values are "ipv4" and "ipv6".

sip.routeset

Default Value:
Valid Values: A valid routeset must have the format as specified in [sip] routeset description
Changes Take Effect: At start/restart


sip.securerouteset

Default Value:
Valid Values: A valid secure routeset must have the format as specified in its description
Changes Take Effect: At start/restart


Defines a route set for secure SIP connections to third party recorders. The URI for secure connections should specify the "sips:" scheme or "tls" transport. If the secure route set is defined, this route set will be inserted as the ROUTE header for all VRMRecorder secure SIP sessions. This will force the MCP to send the secure SIP messages via this defined route set. Please see "[sip] securerouteset" for format and other descriptions. The typical value for this would be the Resource Manager (RM)'s secure address, as all recorder requests go through the RM.

sip.transport.0

Default Value: transport0 udp:any:7090
Valid Values: <transport_name> <type>:<ip-address>:<port> [parameters]
Changes Take Effect: At start/restart


sip.transport.1

Default Value: transport1 tcp:any:7090
Valid Values: <transport_name> <type>:<ip-address>:<port> [parameters]
Changes Take Effect: At start/restart


sip.transport.2

Default Value: transport2 tls:any:7091
Valid Values: <transport_name> <type>:<ip-address>:<port> [parameters]
Changes Take Effect: At start/restart


sip.transport.dnsharouting

Default Value: false
Valid Values: Choose between: true or false
Changes Take Effect: At start/restart


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.

sip.transport.localaddress

Default Value:
Valid Values: Specify a valid IP Address, hostname or domain name
Changes Take Effect: At start/restart


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 [sip].transport.localaddress.srv is set to true, otherwise when [sip].transport.localaddress.srv is set to false an IP address or hostname can be used for the value. 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, vrmrecorder.sip.transport.localaddress.srv must be set to true to prevent the port part being automatically generated by the SIP stack.

sip.transport.localaddress_ipv6

Default Value:
Valid Values: Specify a valid hostname or domain name
Changes Take Effect: At start/restart


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, vrmrecorder.sip.transport.localaddress.srv must be set to true to prevent the port part being automatically generated by the SIP stack.

sip.transport.localaddress.srv

Default Value: false
Valid Values: Choose between: true or false
Changes Take Effect: At start/restart


Specifies whether the mrcpv2client.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 vrmrecorder.sip.transport.localaddress.

sip.transport.staticroutelist

Default Value:
Valid Values: Can be an empty string or a valid "|" separated list of static routes. Check the description for further details.
Changes Take Effect: At start/restart


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.

sip.transport.unavailablewakeup

Default Value: true
Valid Values: Choose between: true or false
Changes Take Effect: At start/restart


Specifies whether unavailable route destinations can be made active if needed before the route recover timer expires. The unavailable destinations would be made active only when all destinations corresponding to a static route group or DNS SRV domain are unavailable. This parameter is applicable when SIP stack is running under HA mode (Static route list or DNS SRV routing).

toheadermode

Default Value: toparams
Valid Values: Choose between: legacy, uriparams, toparams or bothtoanduriparams
Changes Take Effect: Immediately/session


The To Header Mode for Third Party Call Recording. If set to "legacy", the MCP will copy the Request URI of the INVITE request into the To Header, identical to pre-GVP 8.5.0 behavior. If set to "uriparams", the Request URI parameters will be included in the Request URI part of the To Header. If set to "toparams", the Request URI parameters will be included in the To params of the To Header. If set to "bothtoanduriparams", the Request URI parameters will be included in both the Request URI part of the To Header and the To params of the To Header.

This page was last modified on July 24, 2017, at 02:05.

Feedback

Comment on this article:

blog comments powered by Disqus