P a g e
|
43
HT813 Administration Guide
Version 1.0.1.2
SIP REGISTER
Contact Header
Uses
Specifies which address (LAN or WAN address) the device will detect to use it in SIP
Register Contact Header. When set to
LAN
, Contact header will include local IP from
ATA in REGISTER messages, while if set to
WAN
, host/port/contact will be updated
from SIP 401/403/404/407 Via header "received"/"rport" parameters in REGISTER
messages. Default is
LAN Address
.
Caller ID Fetch
Order
Selects the Caller ID display order which need to be respected by the HT813. The
available options are:
●
Auto
: When set to “Auto”, the HT813 will look for the caller ID in the order of P-
Asserted Identity Header, Remote-Party-ID Header and From Header in the
incoming SIP INVITE.
●
Disabled
: When set to "Disabled", all incoming calls are displayed with
"Unavailable".
●
From Header
: When set to “From Header”, the HT813 will use the FROM header
to display the caller ID.
SIP T1 Timeout
Defines T1 timeout value.
It is an estimate of the round-trip time between the client and server transactions.
For example, the HT813 will attempt to send a request to a SIP server.
The time it takes between sending out the request to the point of getting a response is
the SIP T1 timer. If no response is received the timeout is increased to (2*T1) and then
(4*T1). Request re-transmit retries would continue until a maximum amount of time
defined by T2. Default is
0.5
seconds.
SIP T2 Interval
Identifies maximum retransmission interval for non-INVITE requests and INVITE
responses. Retransmitting and doubling of T1 continues until it reaches T2 value.
Default is
4
seconds.
SIP Timer D
Configure the SIP Timer D defined in RFC3261. 0 - 64 seconds. Default 0
DTMF Payload
Type
Defines payload type for DTMF using RFC2833.
Preferred DTMF
method (in order)
Sorts DTMF methods (in-audio, via RTP (RFC2833) or via SIP INFO) by priority.
Disable DTMF
Negotiation
Uses above DTMF order without negotiation. Default is
No
.
Generate
Continuous
RFC2833 Events
When enabled the RFC2833 events are generated until key is released. Default is
No
.