45
<proxy_uri> Optional URI of the proxies to be visited for all
outgoing requests that are using this account
(REGISTER, INVITE, etc).
<proxy_uri2> Optional URI of the proxies (for redundancy) to be
visited for all outgoing requests that are using this
account.
<reg_timeout> 1800 Optional interval for registration, in seconds. If the
value is zero, default interval will be used.
<cred> Array of credentials. Normally, if registration
is required, at least one credential should be
specied to successfully authenticate the service
provider. More credentials can be specied, for
example when it is expected that requests will be
challenged by the proxies in the route set.
<realm> * Realm. Use ”*” to make a credential that can be
used to authenticate any challenges.
<scheme> Scheme (e.g. ”digest”).
<username> Authentication name
<cred_data_type> 0 Type of data (0 for plaintext password).
<cred_data> The data, which can be a plaintext password or a
hashed digest.
<auto_update_nat> true This option is useful for keeping the UDP
transport address up to date with the NAT public
mapped address. When this option is enabled
and STUN is congured, the library will keep
track of the public IP address from the response
of REGISTER request. Once it detects that the
address has changed, it will unregister current
Contact, update the UDP transport address and
register a new Contact to the registrar.
<ka_interval> 15 Set the interval for periodic keep-alive transmis-
sion for this account. If this value is zero,
keep-alive will be disabled for this account.
The keep-alive transmission will be sent to the
registrar’s address after successful registration.
<ka_data> Specify the data to be transmitted as keep-alive
packets. Default: CR-LF.
<use_srtp> 0 Specify whether secure media transport should be
used for this account.
0: SRTP will be disabled and the transport will
reject RTP/SAVP offer.
1: SRTP will be advertised as optional and incom-
ing SRTP offer will be accepted.
2: The transport will require that RTP/SAVP media
is used.
<srtp_secure_signaling> 1 Specify whether SRTP requires secure signalling.
This option is only used when use_srtp option
above is non-zero.
0: SRTP does not require secure signalling
1: SRTP requires secure transport such as TLS
2: SRTP requires secure end-to-end transport
(SIPS)
MANAGEMENT – UPGRADE AND CONFIGURATION
To Next Page
Loading...
