?? help-configuration.html
字號:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<title>Configuration Help</title>
<meta name="author" content="Interactive Intelligence" />
<meta name="keywords" content="" />
<meta name="description" content="" />
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<link rel="File-List" href="Help-Configuration_files/filelist.xml">
<link rel="stylesheet" type="text/css" href="styGeneral.css"/>
<link rel="stylesheet" type="text/css" href="styHelp.css" />
</head>
<body lang="EN-US" style="tab-interval: .5in" onload="self.focus();">
<form id="form1" name="form1" method="get" />
<!-- Start Heading Section -->
<div name="divHeading" id="divHeading">
<a name="ancHeading" />
<h1>Configuration</h1>
<p class="i3field"> </p>
<p class="i3field">The configuration section allows administrators to change all of the properties of the proxy server.</div>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End Heading Section -->
<p class="i3field"> </p>
<!-- Start General Section -->
<div name="divGeneral" id="divGeneral">
<a name="ancGeneral" />
<h2>General:</h2>
</div>
<p class="i3field"> </p>
<p class="i3field" align="center"><img src="imgHelpFig4.gif" border="0" /></p>
<p class="i3field"> </p>
<p class="i3field">The General tab is used to configure basic settings for the
proxy server. These settings include:</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Domain Name:</span><br />
The domain name defines the DNS domain this proxy server is
servicing.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Port Number</span><br />
The port number is the number upon which the proxy server
will listen for SIP messages. The default SIP Proxy port is 5060.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">T1 Timer</span><br />
Timer value in milliseconds that represents the initial
incremental delay before the proxy will reattempt sending a packet.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">T2 Timer</span><br />
The maximum allowable delay before the proxy notes that a
sent packet failed to reach its destination.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Maximum Packet Retry</span><br />
The number of attempts the proxy will make to transmit a
packet before it considers a server/device to be unreachable.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Maximum Invite Retry</span><br />
The maximum number of attempts the proxy will make to send
an INVITE request before it considers a server/device to be unreachable.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Maximum registration interval</span><br />
The maximum allowable registration interval in a REGISTER message that will be accepted by the Interaction SIP Proxy. If a REGISTER message is received without an expiration indication, then this value will be used as the expiration interval. If a REGISTER message is received that contains an interval greater than this value, then it will be lowered to this value.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Monitor servers / interval</span><br />
This parameter enables continuous monitoring of all servers in the server plans. If set to true, the Interaction SIP Proxy will send out a SIP OPTIONS message to each server to in an attempt to assess its status. The configured interval determines the frequency at which the servers are assessed. If set to false (default), the servers are monitored only when they fail to accept a call. In this case, the proxy will route the call to the next server in the server plan and will put the failed server in monitor mode until it抯 ready to accept calls again.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Monitoring servers is only available on the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Digest Authentication</span><br />
This parameter forces all SIP requests to be authenticated before the SIP proxy will process them. The Digest algorithm is used to authenticate the requests credentials. When Digest Authentication is enabled, a username and password should be entered on the SIP proxy's Authentication tab for every device that will require the proxy's services. Requests that fail authentication will be refused.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Digest authentication is only available on the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Record-Route</span><br />
If set to Yes, the Interaction SIP Proxy will insert a Record-Route header into SIP messages to force the SIP signaling to travel through the proxy for the duration of the session.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Record-Route is only available on the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Rewrite Request URI</span><br />
In some instances it is desirable to modify a number before
sending it to its destination (e.g. 6142245555 should be dialed 2245555 from a
local gateway). Although the TO field cannot be modified according to the SIP
standard, the proxy can modify the request URI for number translation purposes.
Please note: the endpoint (SIP User Agent) must make use of this Request URI for
the translation to be successful.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Route Unknown URI</span><br />
In some instances it is desirable to route messages with URI抯 that are not targeted for the proxy. By enabling this feature, the proxy will route messages to the Request-URI of the message, but, only if the message doesn抰 match a route pattern or registration entry. This feature will most likely be used when SIP phones or gateways use the proxy as a dedicated outbound proxy and make no routing decisions on their own.
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Match pattern against all routes</span><br />
The Interaction SIP Proxy matches the Request-URI of inbound SIP messages against the patterns on the Routing tab. If a match is found then a list of next-hop targets are computed using the User formatting pattern and applying it to all the servers in the server plan. If this parameter is set to false, then once a pattern match is found the list of targets is returned for the servers associated with the matched pattern only. If this parameter is set to true, then the pattern matching continues through the rest of the pattern entries and a list of targets is returned for all the servers in all matched patterns.
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Redirect Server</span><br />
Set to No, the server will act as a SIP proxy server. Set
to Yes, the server will act as a SIP redirect server for INVITE requests.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Next server on 480 response</span><br />
If set to Yes, the Interaction SIP Proxy will forward the request to the next server in a server plan when a 480 Temporarily Unavailable response is received from the current server. If set to No, the Interaction SIP Proxy will send the response back to the initiator of the request and the transaction will end.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Next server on 480 response is only available in the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Next server on 5xx response</span><br />
If set to Yes, the Interaction SIP Proxy will forward the request to the next server in a server plan when any 500 level response is received from the current server. If set to No, the Interaction SIP Proxy will send the response back to the initiator of the request and the transaction will end.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Next server on 5xx response is only available in the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Next server on 6xx response</span><br />
If set to Yes, the Interaction SIP Proxy will forward the request to the next server in a server plan when any 600 level response is received from the current server. If set to No, the Interaction SIP Proxy will send the response back to the initiator of the request and the transaction will end.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Next server on 6xx response is only available in the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Registration Routing</span><br />
By default, the Interaction SIP Proxy will try to match incoming SIP messages with route item entries and then sequentially route the message to the servers in the server plan associated with the route item. However, in the event that all routes are unreachable, the proxy server can route SIP messages to devices that properly REGISTER with it when this parameter is enabled. If all routes are unreachable or a match was not found then the proxy will try to match it against an address of record in the registration cache, and, if found send it to that device.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Registration has priority</span><br />
If set to Yes, the Interaction SIP Proxy will treat the entries in the registration cache as higher priority targets than the route item matches. For example, if an incoming call matches both a route item and a registration entry, the call will be routed to the registration entry if this value is set to Yes. If set to No, the route item entry would be used first.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Forward Registers</span><br />
This option will forward device REGISTER messages to the
server(s) listed in the Server Plan.</p>
<p class="i3field"> </p>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End General Section -->
<p class="i3field"> </p>
<!-- Start ServerPlan Section -->
<div name="divServerPlan" id="divServerPlan">
<a name="ancServerPlan" />
<h2>Server Plan:</h2>
<p class="i3field"> </p>
<p class="i3field" align="center"><img src="imgHelpFig5.gif" border="0" /></p>
<p class="i3field"> </p>
<p class="i3field">The Server Plan page is used to configure collections of destinations/servers and a distribution model for routing messages to those destinations. The distribution model defines the method in which the Interaction SIP Proxy will distribute messages to the servers when the server plan is selected. The distribution models are,
<ol>
<li><p class="i3field"><b>Prioritize</b> - the list of servers is considered to be a prioritized list of servers that will be tried in the same order every time the plan is selected. If the first device cannot be reached the next device on the list will be attempted. This is the only model available on the free basic version of the SIP proxy.</p></li>
<li><p class="i3field"><b>Round-Robin</b> - the list of servers is treated as a prioritized circular list. Each time the plan is selected the next server in the list becomes the top priority. If it cannot be reached then the next server in the list will serve as the backup and so on.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Round-robin distribution is only available on the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p></li>
<li><p class="i3field"><b>Random</b> - each time the plan is selected, a server from the list is chosen at random to become the top priority. If it cannot be reached then the next server in the list will serve as the backup and so on.</p>
<p class="i3field"> </p>
<p class="i3comment"><span class="i3title">Advanced Feature:</span> Random distribution is only available on the Advanced version of the Interaction SIP Proxy. The Advanced version can be purchased at <a class="i3comment" href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field"> </p></li>
</ol>
</p>
<p class="i3field">The servers entered into the server plan are required to be in a host:port format. The host portion can be a fully qualified domain name (FQDN) or an IPV4 address. The FQDN must be resolvable to an IPV4 address, otherwise it won't be used. The port is optional and defaults to the SIP protocol default, 5060.</p>
<p class="i3field"> </p>
<p class="i3field"><span class="i3title">Examples of fully qualified domain name entries:</span><br />
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -