Obihai OBi110, Руководство администратора

Страница: 94 / 202

Copyright 2010-2012 Obihai Technology, Inc. 94
bridged call (from another trunk, such as PSTN Line or
another SP Service).
Otherwise, device always its own account information to
form the FROM header.
Note that most service provider will not allow originating a
call if the FROM header field does not match the account
credentials. Enable this option only if you are sure that the
service provider allows it, e.g. an IP PBX may allow it.
X_UseRefer Enable the use of SIP REFER for call transfer. If disabled,
device will bridge the call instead when performing a call
transfer (which consume some resources on the device) No
X_ReferAOR Enable the use the target's AOR (Address of Record or
public address) in Refer-To header of SIP REFER. If disabled,
the target's Contact will be used instead Yes
X_Use302ToCallForward Enable the use of 302 response to INVITE for call forward. If
disabled, device will bridge the call legs instead when
forwarding a call (and will consume some resources on the
device) Yes
X_UserAgentName If a value is specified, device includes a User-Agent header
in all SIP Requests, or a Server header in all SIP responses,
that contains exactly the given value OBIHAI/${DM}-${FWV}
X_ProcessDateHeader Enable the device to decode the DATE header sent by the
ITSP in a 200 response to its REGISTER. The DATE header
specifies the current GMT time and the device can use to
adjust its local time and date without relying on NTP Yes
X_InsertRemotePartyID Enable the device to include a Remote-Party-ID header in
its outbound SIP INVITE to indicate to the ITSP the caller’s
preferred privacy setting (either full or none) Yes
X_SessionRefresh Enable session refresh signalling (with SIP Re-INVITE) during
a connected call. This allows the OBi to detect if the
connection with the peer is broken abnormally so it can
release the call. Disable this option if the ITSP does not
support Re-INVITE sent from the client device. Yes
X_AccessList A comma separated list of IP addresses such that the device
only accepts SIP requests coming from one of the given
addresses. If the list is empty, the device accepts SIP
requests from any IP address
X_InsertRTPStats Enable the device to include a X-RTP-Stat header in a BYE
request or 200 response to BYE request at the end of an
established call. This header contains a summary of RTP
statistics collected during the call. Yes
X_MWISubscribe Enable this option to have the device SUBSCRIBE to the
message-summary event package to support MWI and
VMWI service.
Note that device handles NOTIFY of this event package
regardless MWISubscribe is enabled or not
No
X_MWISubscribeURI Blank implies to use the same URL as REGISTER for the TO
and FROM header as well as the Request-URI
Otherwise, if the URI does not contain ‘@’, it is user as the
userid field in TO/FROM header as well as the Request-URI,
which are otherwise same as REGISTER