analoggateway.ourcompany.com<br />
interationcenter.ourcompany.com:6000</p>
<p class="i3field">&nbsp;</p>
<p class="i3field"><span class="i3title">Examples of IPV4 entries:</span><br />
192.168.1.100<br />
192.168.0.200:5060</p>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End ServerPlan Section -->


<p class="i3field">&nbsp;</p>


<!-- Start Routing Section -->
<div name="divRouting" id="divRouting">
<a name="ancRouting" />
<h2>Routing:</h2>
<p class="i3field">&nbsp;</p>
<p class="i3field" align="center"><img src="imgHelpFig6.gif" border="0" /></p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The Routing tab is used to create and associate regular-expression patterns to server plans.  The servers in a server plan provide a prioritized list of servers to which messages matching this pattern should be sent. The syntax for these patterns is standard regular expressions whose syntax can be found at:</p>
<p class="i3field"><a href="http://www.boost.org/libs/regex/doc/syntax.html" target="_new">http://www.boost.org/libs/regex/doc/syntax.html</a></p>
<p class="i3field">&nbsp;</p>
<p class="i3field">Pattern substitution can be done on the user portion of a SIP address.  See the examples below for help in setting this up.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The Pattern column defines a regular expression that is matched against the Request URI field in incoming SIP messages. If a match occurs, then the value of the User column is concatenated with the servers in the server plan to form the next target(s) for the request.  The first regular expression to match the input Request-Uri is used, so prioritize the route plan entries appropriately. Each server in the server plan associated with the matched pattern is used to form a list of prioritized next targets for the incoming SIP message.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The Run Test button allows administrators to test their expression pattern matching and the resulting route targets. Enter a valid SIP address into the Test Pattern entry box and press the Run Test button.  A new window will pop-up showing the complete target list after running it through the current routing items.  Note: Be sure to enter the Test Pattern in the user@host format if your regular expressions expect a host portion.  For example, if you want to test your dial plan against 555-1212, then enter 5551212@somehost.com.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field"><span class="i3title">Example:</span><br />The administrator wants all extensions (7000-7999) to be handled by a specific SIP application server, such as the Interaction Center.  The following pattern is one of many that could accomplish this.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field"><span class="i3title">Pattern:</span><br /><i>(7[0-9]{3})@.*</i></br>This will select a TO field that starts with "sip:".  The first digit must be a 7 and there must be three more, each being 0 to 9.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field"><span class="i3title">User:</span><br /><i>$1</i></br>This will select the first sub-expression (defined by the parenthesis). In the case where 7005 was dialed, 7005 would be used.  Note:  It's important to use sub-expressions to match the user part of the SIP message when the pattern contains a host portion.  In this case the host portion is @.*, which matches any characters after a required @ sign.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field"><span class="i3title">Server Plan:</span><br /><i>Interaction Center</i></br>The server plan used would include the FQDN or IPV4 address of the Interaction Center. In this example one server is in the server plan, and its address 192.168.0.59.  If the Interaction Center is unreachable, then the Interaction SIP Proxy attempts to match  Registered devices. If a match is found and Registration routing is enabled, then the call will be routed to the Contact address.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">With these settings an INVITE to sip:7005@cic_server would be proxied to 192.168.0.59 as sip:7005@192.168.0.59.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field"><span class="i3title">Other pattern examples:</span></p>
      <table cellspacing="0" cellpadding="2" border="1" bordercolor="#7B756F" class="styReportTable">
        <tr>
          <th class="styReportHeader"><span class="styPageTitle">Pattern</span></td>
          <th class="styReportHeader"><span class="styPageTitle">User</span></td>
          <th class="styReportHeader"><span class="styPageTitle">Comment</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">(sip:[2-9][0-9]{6})@.*</span></td>
          <td nowrap="nowrap"><span class="styPageText">$1</span></td>
          <td><span class="styPageText">Matches 7 digit local numbers<br /><br />ex: sip:2245555@proxy_server</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">(sip:[2-9][0-9]{2}[2-9][0-9]{6})@.*</span></td>
          <td nowrap="nowrap"><span class="styPageText">$1</span></td>
          <td><span class="styPageText">Matches 10 digit long distance numbers<br /><br />ex: sip:6142245555@proxy_server</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">(sip:614)([2-9][0-9]{6})@.*</span></td>
          <td nowrap="nowrap"><span class="styPageText">sip:$2</span></td>
          <td><span class="styPageText">Matches 10 digit long distance number, stripping the area code for local dialing<br /><br />ex: sip:6142245555@proxy_server<br /><br />Number translated to:<br />sip:2245555@proxy_server</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">(.*)@.*</span></td>
          <td nowrap="nowrap"><span class="styPageText">$1</span></td>
          <td><span class="styPageText">Matches anything with an @ sign<br /><br />ex: 123456@whatever</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">(911)@.*</span></td>
          <td nowrap="nowrap"><span class="styPageText">$1</span></td>
          <td><span class="styPageText">Match 911 calls and route appropriately<br /><br />ex: sip:911@proxy_server</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">sip:5@.*</span></td>
          <td nowrap="nowrap"><span class="styPageText">5551212</span></td>
          <td><span class="styPageText">Convert 5 to 5551212, This functions like a speed-dial number<br /><br />ex: sip5@proxy_server is converted to sip:5551212@server</span></td>
        </tr>
        <tr>
          <td nowrap="nowrap"><span class="styPageText">9([0-9].......)</span></td>
          <td nowrap="nowrap"><span class="styPageText">$1</span></td>
          <td><span class="styPageText">Removes the 9 from the dial string and passes along the next 7 characters<br /><br />ex: sip:95551212@proxy_server is converted to sip:5551212@somegateway.com</span></td>
        </tr>
      </table>
<p class="i3field">&nbsp;</p>
</div>
<p class="i3field">&nbsp;</p>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End Routing Section -->


<p class="i3field">&nbsp;</p>


<!-- Start Authentication Section -->
<div name="divAuthentication" id="divAuthentication">
<a name="ancAuthentication" />
<h2>Authentication:</h2>
<p class="i3field">&nbsp;</p>
<p class="i3field" align="center"><img src="imgHelpFig10.gif" border="0" /></p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The Authentication tab allows the administrator to configure user names and passwords on the proxy so that SIP requests can be challenged before they are processed. The username and password entered here must match the username and password entered on the device. The Interaction SIP Proxy uses Digest authentication to authenticate credentials provided by SIP phones and gateways requesting the proxy's services.</p> 
<p class="i3field">&nbsp;</p>
<p class="i3field">The Aliases list provides an alternate set up names/numbers to associate with a user when one of the users devices registers and passes the authentication challenge.  All the entries in the users Aliases list can be dialed to contact the user.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">Authentication must be enabled on the Configuration/General tab and is only available with the Advanced version of the Interaction SIP Proxy.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">Each user has the option of being associated with dialing aliases.</p>  
<p class="i3field">&nbsp;</p>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End Authentication Section -->


<p class="i3field">&nbsp;</p>


<!-- Start License Section -->
<div name="divLicense" id="divLicense">
<a name="ancLicense" />
<h2>License:</h2>
<p class="i3field">&nbsp;</p>
<p class="i3field" align="center"><img src="imgHelpFig7.gif" border="0" /></p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The license tab is used to apply a permanent license key to the Interaction SIP Proxy. It must be activated within 30 days of installation to continue functioning.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The Basic version of the Interaction SIP Proxy contains all the trial features can be purchased at <a href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">The Advanced version of the Interaction SIP Proxy, which contains user authentication and advanced distribution models, such as load-balancing, can also be purchased at <a href="http://www.inin.com/sipproxy">http://www.inin.com/sipproxy</a>. The advanced features are activated by this license key.</p>
<p class="i3field">&nbsp;</p>
<p class="i3field">When the Interaction SIP Proxy is purchased, you'll receive an activation license via email. The activation license needs to be copied into the entry box on the License tab and then submitted using the Submit button. If the permanent license is valid, then the proxy features will function indefinitely.</p>
</div>
<p class="i3field">&nbsp;</p>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End License Section -->


<p class="i3field">&nbsp;</p>


<!-- Start Administration Section -->
<div name="divAdministration" id="divAdministration">
<a name="ancAdministration" />
<h2>Administration:</h2>
<p class="i3field">&nbsp;</p>
<p class="i3field" align="center"><img src="imgHelpFig8.gif" border="0" /></p>
<p class="i3field">&nbsp;</p>
<p class="i3field">This tab allows the administrator to change the user name and password required to manage the proxy server.  This information is sent in clear text on the administration page.  It is strongly recommended that you change this setting on the proxy server itself.</p>
</div>
<p class="i3field">&nbsp;</p>
<div align="right"><a class="styHelp" href="#">[Top]</a></div>
<!-- End Administration Section -->

<p class="i3field">&nbsp;</p>
<p class="i3field">&nbsp;</p>


</form>
</body>
</html>