User's Manual

Avaya B179 SIP Conference Phone Installation and Administration Guide

<valid> If this account information is valid or not.

<name> User dened name of the account

<id> The full SIP URL for the account.

<registrar> This is the URL to be put in the request URI for the registration.

<publish_enabled> If this ag is set, the presence information of this account will be published to

the server where the account belongs.

<initial_auth> If this ag 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

specied, a random string will be used.

<force_contact /> Optional URI to be put as Contact for this account. Leave this eld empty, so

that the value will be calculated automatically 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. Normally, if registration is required, at least one credential

should be specied to successfully authenticate the service provider. More

credentials can be specied, 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> 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 congured, 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 oer.

1: SRTP will be advertised as optional and incoming SRTP oer will be accepted.

2: The transport will require that RTP/SAVP media is used.

<use_srtcp> Species whether encryption or no encryption is used for the control protocol.