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

Страница: 111 / 220

Copyright 2010-2013 Obihai Technology, Inc. 111
X_InboundCallRoute Routing rule for directing incoming calls on this service. The
default rule is to send all incoming calls to the PHONE port (ph).
See
OBi Call Routing and Digit Map Section for a description of
the syntaxes for specifying this parameter
ph
X_RegisterEnable Enable registration for this line. If set to YES, device sends
periodic SIP REGISTER to the service provider according to the
settings in the ITSP Profile. Otherwise, device does not send any
SIP REGISTER for the service Yes
X_NoRegNoCall Enable this option to disallow making or receiving calls on this
service unless registeration with the SIP server is successful. No
X_KeepAliveEnable Enable sending keep alive message. If set to YES, device sends
periodic keep-alive messages to the destination specified in
X_KeepAliveServer and X_KeepAliveServerPort, at the interval
specified in X_KeepAliveExpires. The content of this message is
the ASCII string “keep-alive\r\n” No
X_KeepAliveExpires Keep alive period in seconds 15
X_KeepAliveServer Hostname or IP address of keep alive server
X_KeepAliveServerPort UDP port of the keep alive server 5060
X_KeepAliveMsgType The type of keep alive messages to send out periodically if keep-
alive is enabled. It can be one of the following choices:
- keep-alive: The string “keep-alive”
- empty: A blank line
- stun: A standard STUN binding request; device will use the
binding response to form its contact address for
REGISTRATION
- custom: use the value of X_CustomeKeepAliveMsg (note:
option not available on OBi100/OBi110)
keep-alive
X_CustomKeepAliveMsg Defines the custom message to be used when
X_KeepAliveMsgType is “custom”. The value should have the
following format:
mtd=NOTIFY;event= <whatever> ;user= <anyone>
Where
- NOTIFY may be replaced by any other SIP method, such
as PING,
- event parameter is optional and is only applicable if
method is NOTIFY. If event is not specified, the 'keep-
alive' event will be used with NOTIFY
- user parameter is optional; if not specieifed, the
request-uri will not have a userid, and the TO header
field will use the same userid as the FROM header
(which is the local account userid). If user is specified, it
will be used as the userid in the Request-URI and TO
header.