TIM Professional allows you to apply different rates to specific calls, depending on whether they were made over certain trunks, by particular extensions, by using a particular trunk access codes or from specific sites. This can be achieved by creating a routing table, such as the one shown below.
Some criteria takes precedence over others and the hierarchy is as follows:
Each set of criteria should be listed in its own section, which will be defined by inserting the section name in square brackets.
A typical routing configuration may look like this:
[Extension] 3000 = Payphone 3001 = Payphone 3002 = Payphone 3003 = Payphone [Trunk] 2001 = NTL 2002 = NTL 2003 = NTL 2004 = NTL 2005 = NTL 2006 = NTL 2007 = NTL [Access Code] 78 = PrivateWire [Site] Default Site = BT |
In the example above, assuming the default tariff table is set to BT, any call data from the site would be reinforced as a BT call.
If, however, a call was made using the trunk access code 78, this would be costed as a PrivateWire call. This would be overridden if the call was made over any of the trunks 2001 to 2007 and it would be costed at rates. In the same way, if the call was made from any of the extensions 3000 to 3003, it would be priced using the
rate, taking precedence above all other conditions.
<p>Open the <span class="keyword">ROUTING.CFG</span> file found in the <span class="keyword">\config</span> folder within the main program folder.</p>
<p>Calls can be priced differently when made over certain trunks, by particular extensions,
by using different trunk access codes, and from different sites.</p>
<p>This is made possible by use of this routing table. Some criteria takes precedence over
others and the hierarchy is as follows:</p>
<ul>
<li>Extension Routing</li>
<li>Least-Cost Routing</li>
<li>Hard Trunk Routing</li>
<li>Trunk Access Routing</li>
<li>Site Routing</li>
</ul>
<p>Each set of criteria should be listed in its own section. Sections are defined by
inserting the section name in square brackets.</p>
<p>A typical routing configuration may look like this:</p> |
[Extension] 3000 = Payphone 3001 = Payphone 3002 = Payphone 3003 = Payphone [Trunk] 2001 = NTL 2002 = NTL 2003 = NTL 2004 = NTL 2005 = NTL 2006 = NTL 2007 = NTL [Access Code] 78 = PrivateWire [Site] Default Site = BT |
<p>In this example, assuming the default tariff table is set to BT, then any call data from the site 'Default Site' would be reinforced as a BT call.</p> <p>If, however, a call was made using the trunk access code <span class="keyword">78</span>, it would be costed as a <span class="reference">PrivateWire</span> call.</p> <p>This would be overridden if the call was made over any of the trunks 2001 to 2007. In this case it would be costed at NTL rates.</p> <p>However, taking precedence above all of this, if the call was made from any of the extensions 3000 to 3003, it would be priced using the Payphone rate.</p> |