_________________________________________________________________________________
_________________________________________________________________________________
92
Universal Network Terminal TAU-32M.IP
On
– SIP-proxy will be used for outgoing calls in all cases;
With busy tone
–SIP-proxy will be used for outgoing calls in all cases. If subscriber port is not
registered for some reason, busy tone will be played on this port, when the phone is offhook.
–
Dial timeout (for Outbound)
–dialling timeout for the next digit (in 'Outbound' mode), in seconds. To dial
without a timeout, you should use prefixes with the definite quantity of digits or use
'Stop dial at #'
setting
separately for subscriber ports
;
This setting is effective for 'Dialplan table' routing plan only.
–
Expires
–registration renewal time period;
–
Authentication
–defines device authentication mode:
Global
– enable SIP server authentication with common user name and password for all subscribers;
User defined
– enable SIP server authentication with different user names and passwords for each
subscriber, user name and password for ports could be defined in 'PBX/Ports'.
–
Username
–username for
'global'
mode authentication;
–
Password
–password for
'global'
mode authentication (
'password'
, by default);
–
Alert Info
–process INVITE request 'Alert Info' header to send a non-standard ringing to the subscriber port.
Cadence for a non-standard ringing may be configured in 'Alert Info' tab of the corresponding SIP profile;
–
Ringback at answer 183
–when checked, 'ringback' tone will be sent upon receiving '183 Progress' message.
When this setting is used, the gateway will not generate a ringback tone to the local subscriber, if the voice
frequency path is already forwarded at the time when the message 183 is received, or if message 183
contains SDP session description for the frequency path forwarding;
–
Ringback at callwaiting
–send
180
or
182
message, when the second call is received on the port with an
active Call waiting service. Used to notify the caller (with a ringback tone of specific tonality) that their call
is queued and waiting for response. Depending on the received message (180 Ringing or182 Queued), the
caller gateway generates either a standard ringback (180 Ringing) or a non-standard one (182 Queued);
–
Remote ringback
–parameter defines, whether the gateway should send a ringback tone upon receiving an
incoming call:
Don’t send ringback in RTP (180)
–when an incoming call is received, the gateway will not generate a
ringback tone and will return '180 ringing' response;
Don’t send ringback in RTP (183)
–when an incoming call is received, the gateway will not generate a
ringback tone and will return '183 progress' response;
Ringback with 180 ringing
–when an incoming call is received, the gateway will generate a ringback
tone and send it to the communicating gateway in the voice frequency path. Voice frequency path
forwarding will be performed along with '180 ringing' message transmission via SIP protocol;
In addition to static Outbound SIP server configuration, you may define dynamic configuration
with DHCP Option 120. When this option is received, the gateway will use it in the first SIP profile
(Profile 1) only; at that,
'Proxy/Registrar address'
settings will remain in effect and will still be
used as SIP-proxy and registration server addresses. If you want to use addresses specified in
Option 120 as SIP-proxy and registration server addresses, leave
'Proxy/Registrar address'
settings blank. As this option allows to send addresses of a multiple outbound SIP servers,
Proxy
redundancy modes
described above will also work in this case.