Registrations

YETI is able to send outgoing SIP REGISTER requests(act as registrar client) to remote SIP registrar servers. This object allow to configure this registrar client behavior.

Registration attributes

Id

Unique ID

Name

Name of this registration.

Enabled

Disabled registrations will be ignored.

Pop

Point of presence for registration requests.

Node

Node which will send REGISTER requests.

Transport protocol

SIP transport protocol which will be used for send request.

Domain

RURI,From domain part.

Username

RURI,From user part.

Display username

From display name part.

Auth user

Authorization username.

Auth password

Authorization password.

Route Set

A route set is a collection of ordered SIP or SIPS URI which represent a list of proxies that must be traversed when sending a REGISTER request. Proxy address should specified in SIP URI format eg sip:sip-proxy.example.com. See Registration Flow with Proxy example. Route Set will be added to SIP request as Route headers.

Empty routeset:

Registration sent via proxy:

Two proxies in routeset:

TIP

Read more about Route Set at RFC3261

Contact

Contact header. Should be in a SIP-URI format.

Expire

Registration expiration time.

Force expire

Force re-registration after Expire interval even is server set another value in response.

Retry delay

Set the delay before sending a new REGISTER request to a registrar, when received error code or timeout occurred.

Max attempts

Maximum amount of attempts for sending a REGISTER request, when an error code received from a registrar or timeout occurred. In order to re-enable attempts of registration, you should disable the registration and then enable again.

Sip Interface Name

Name of signalling interface from sems.conf that will be used to build outgoing REGISTER request.

Registration Flow without Proxy

Registration Flow with Proxy