Copyright 2010-2015 Obihai Technology, Inc.
192
the service is provided by an OBiPLUS system
X_AcceptResync
Control whether to accept a SIP NOTIFY request with
event=resync to trigger a reboot of the device (so it can
download new f/w or configuration upon boot up).
Available choices are:
no (do not accept resync trigger)
yes with authentication (accept after challenging the
sender)
yes without authentication (accept w/o challenging the
sender)
yes without
authentication
SIP Credentials (VoiceService.1.VoiceProfile.1.Line.
n
.SIP.),
n
= 1 – 6
AuthUserName
The User ID to authenticate to a SIP UAS (User Agent
Server) when an outbound SIP request sent by the
device is challenged by the UAS with a 401 or 407
Response
AuthPassword
The Password (corresponding to AuthUserName) to
authenticate to a SIP UAS (User Agent Server) when an
outbound SIP request sent by the device is challenged
by the UAS with a 401 or 407 Response
URI
This parameter affects the way the AOR is formed by
the device in outbound SIP Requests. The AOR has the
format: user@domain.
If the value of URI is empty, device gets the user portion
of its AOR from the AuthUserName, and the domain
portion the value of ITSP Profile’s UserAgentDomain if it
is not empty, or that of the ProxyServer otherwise.
If the value URI is not empty and does not contain “@”,
it is used as the user portion of the AOR while the
domain portion is formed the usual way.
If the value of URI contains “@’, it is interpreted as a full
AOR and device takes it as the AOR as is.
Some Examples:
1) Let ProxyServer =
sip.myitsp.com
, AuthUserName =
4089991123
, URI=[empty], UserAgentDomain=[empty],
then
AOR =
2) Change UserAgentDomain to
users.myitsp.com
, then
AOR =
3) Change URI to bobdylan, then
AOR =
4) Change URI to
,
then
AOR =
Note: In all cases, device uses AuthUserName and
AuthUserPassword to compute authorization if