Konftel 300IP Installation And Administration page 20

PRovISIoNINg – uPgRADE AND CoNFIguRAtIoN
<publish_enabled> If this flag is set, the presence information of this account will be
Published to the server where the account belongs.
<initial_auth> If this flag is set, the authentication client framework will send an empty
Authorization header in each initial request.
<initial_algo /> Specify the algorithm to use when empty Authorization header is to be
sent for each initial request (see above).
<pidf_tuple_id /> Optional PIDF tuple ID for outgoing PUBLISH and NOTIFY. If this value
is not specified, a random string will be used.
<force_contact /> Optional URI to be put as Contact for this account. It is recommended
that this field is left empty, so that the value will be calculated automati-
cally based on the transport address.
<require_100rel> Specify whether support for reliable provisional response (100rel and
PRACK) should be required for all sessions of this account.
<proxy_uri /> Optional URI of the proxies to be visited for all outgoing requests that are
using this account (REGISTER, INVITE, etc).
<reg_timeout> Optional interval for registration, in seconds. If the value is zero, default
interval will be used.
<cred> Array of credentials. If registration is desired, normally there should be
at least one credential specified, to successfully authenticate against the
service provider. More credentials can be specified, for example when
the requests are expected to be challenged by the proxies in the route
set.
<realm> Realm. Use "*" to make a credential that can be used to authenticate
against any challenges.
<scheme /> Scheme (e.g. "digest").
<username> Authentication name
<cred_data_type> Type of data (0 for plaintext password).
<cred_data> The data, which can be a plaintext password or a hashed digest.
<auto_update_nat> 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 configured, 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> Set the interval for periodic keep-alive transmission 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> Specify whether secure media transport should be used for this account.
0: SRTP will be disabled, and the transport will reject RTP/SAVP offer.
36
PRovISIoNINg – uPgRADE AND CoNFIguRAtIoN
1: SRTP will be advertised as optional and incoming SRTP offer will be
accepted.
2: The transport will require that RTP/SAVP media shall be used.
<srtp_secure_signaling> Specify whether SRTP requires secure signalling to be used. 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)
<account>
Same as above for account 2
<provisioning>
<upgrade>
<url> Place to find software upgrades. The supported URL types are: HTTP,
FTP, and TFTP.
<www>
<enable_https> Secure communication to the 300IP web server. Default is false.
Export configuration
 Click on the Export button.
The configuration file is shown in the web browser.

Choose to save the page as an xml file.
The xml file is as default saved in your folder for downloaded files.
 If needed, edit the xml file in a suitable editor.
Import configuration
 Click on the browse... button.
 Select the xml file and choose to open it.
 Click on the Import button.
37