
63
VoIP Subscriber Gateways
-
Off
–when the following tag is received in 'INVITE' request–required: 100rel, reject the
request with message 420 and provide the following tag–unsupported: 100rel.
Otherwise, perform unreliable transfer of provisional replies.
-
Enable timer
– when checked, enables support of SIP session timers (RFC 4028). After
connection establishment, if both sides are supporting timer, one of them periodically
send re-INVITE queries for connection control (if both sides are supporting UPDATE
method (it should be pointed in 'Allow' header) session update is being processed by
periodical UPDATE messages sending); The following settings are available for
configuring:
Minimal session time (Min SE, sec) – minimal time interval for connection health
checks (90 to 1800s, 120s by default). The value shouldn’t be more then value
specified in the field ‘Session time’;
Session expires, s – period of time in seconds that should pass before the forced
session termination if the session is not renewed in time (90 to 80000s,
recommended value–1800s, 0–unlimited session);
-
Periodic SIP server polling (Keepalive NAT sessions)
– allows you to support active UDP-
session when you work on NAT. It obviates the necessity to create the rules of port
forwarding on the external router. Session activity is supported by periodical sending
one of the message types to SIP server: OPTIONS, NOTIFY or CLRF.
Mode – message type selection for sending to SIP server (OPTIONS, NOTIFY or
CLRF), Off – disable SIP server polling;
Keepalive timeout, s – SIP server polling time period to support active UDP
connection;
-
Three-party conference
– service provides establishing connection between three
subscribers;
Mode
– selection of three-party operation mode:
Local – conference assembly is performed locally by the TAU-8.IP device after
pressing 'flash+3'; operation mode algorithm is described in the section 4.3.1;
Remote (RFC4579) - conference is intended on remote server. Then, after pressing
'flash+3' combination Invite message sending on server to number, pointed in the
'Conference server' field. In this case conference processing by algorithm, described
in RFC4579. For detailed description, see section 4.3.2.
-
Conference server
- conference connection establishment server address processed by
algorithm, described in RFC4579. Address sets in SIP-URI format: user@address:port. It
is available to set only user part URI - in this case Invite message will be sent to SIP proxy
address.