...
To exclude calls based on a type of call, select the call type from the list provided and choose the appropriate operator. In the example below, the stats collector will collate exclude all type types of calls, except internal calls.
This option allows you to exclude calls from stats based on call type. To set up your criteria, select the call type from the list
| Criteria_filter |
|---|
| Value3 | Internal |
|---|
| Value1 | Call type |
|---|
| Value2 | Does not equal |
|---|
|
Carrier
To exclude calls based on carrier (tariff table) used to cost the calls, choose a carrier from the list provided and select the appropriate operator. In the example below, the stats collector will exclude all calls that are not routed over a
carrier.| Criteria_filter |
|---|
| Value3 | BT |
|---|
| Value1 | Carrier |
|---|
| Value2 | Does not equal` |
|---|
|
Channel
This filter allows you to set up an alarm based on the call traffic going over your telephone lines. To set up the alarm criteria, click on the
| Inlineimage |
|---|
| URL | /download/attachments/1310815/add_button.png |
|---|
|
icon to locate the relevant channel in the Directory; select the channel and choose the appropriate operator. In the example below, an alarm will be triggered when channel is used to log a call.| Criteria_filter |
|---|
| Value3 | T234 |
|---|
| Value1 | Channel |
|---|
| Value2 | Equals |
|---|
|
Chargeband
This filter allows you to set up an alarm based on the chargeband used to cost calls. To set up the alarm criteria, enter the chargeband's name (or a sequence of characters you want to be matched) in the box provided and select the appropriate operator. In the example below, calls whose account code is an alarm will be triggered when a call's chargeband begins with the characters
will not be collated by the stats collector.| Criteria_filter |
|---|
| Value3 | Mob |
|---|
| Value1 | Chargeband |
|---|
| Value2 | Begins with |
|---|
|
CLI
This filter allows you to set up an alarm based on CLI. To set up the alarm criteria, enter the CLI (or part of the CLI number) in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when a call's CLI contains the digits
.
| Criteria_filter |
|---|
| Value3 | Tandem2652626 |
|---|
| Value1 | Call typeCLI |
|---|
| Value2 | EqualsContains |
|---|
|
Carrier
| HTML |
|---|
<p>To edit a Stats Collector, simply left-click on it and select <span class="button">Properties</span> from the pop-up menu, as shown below:</p>
<img class="screenshot" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/stats_collector_properties_1.png" alt="Stats Collector properties" />
<h2>General properties</h2>
<p>After clicking on the <span class="button">Properties</span> of your Stats Collector, the following screen will appear:</p>
<img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/stats_collector_properties_2.png" alt="Stats Collector properties" />
<h4>Subject</h4>
<p>You will need to decide on the <span class="reference">Subject</span> for those stats points. You can select among the following options:</p>
<ul>
<li><span class="keyword">User: </span>Stats are accumulated based on individual user stats. This is normally used when you want to compare call stats for a number of users e.g. a Leaderboard showing which user answered the most calls, spent the longest duration on outbound calls etc. </li>
<li><span class="keyword">User group: </span>Stats are accumulated based on User group. This is ofren used when you want to compare stats for groups of users e.g. how many calls are answered by the service team compared to the sales team. It may even be used to show calls stats for a number of teams across different sites e.g. all UK sales teams.</li>
<li><span class="keyword">Site: </span>Stats are accumulated based on site. This is ideal when comparing call traffic across a number of sites.</li>
<li><span class="keyword">Cost centre: </span>Stats are accumulated based on Cost centre. This is ideal when comparing call traffic across a number of cost centres.</li>
<li><span class="keyword">Division: </span>Stats are accumulated based on Division. The divisions can be on one site or spread across multiple sites.</li>
<li><span class="keyword">PBX: </span>Stats are accumulated based on individual PBX. This is ideal when comparing call traffic across a number of different PBXs. The PBX can be on one site or spread across multiple sites.</li>
<li><span class="keyword">Dialled number: </span>Stats are accumulated based on dialled number.</li>
<li><span class="keyword">CLI: </span>Stats are accumulated based on CLI. This is often used to recognise clients that call on a regular basis.</li>
<li><span class="keyword">Chargeband: </span>Stats are accumulated based on chargeband. This allows you to clearly identify frequently used chargebands.</li>
<li><span class="keyword">Destination: </span>Stats are accumulated based on destination. This allows you to easily identify destinations that are frequently dialled.</li>
<li><span class="keyword">Half hour time slot: </span>Stats are accumulated based on half hour time slot. Allows you to easily identify peak times during the day.</li>
<li><span class="keyword">Account code: </span>Stats are accumulated based on account code. See Account codes that are often used or those rarely used at all.</li>
<li><span class="keyword">Channel: </span>Stats are accumulated based on channel. Identify how busy your channels are.</li>
<li><span class="keyword">Channel group: </span>Stats are accumulated based on channel group. Often used to determine if you have enough lines or reach capacity on particular line groups.</li>
</ul>
<h4>Reset frequency</h4>
<p>You also need to deside on the <span class="reference">Reset frequency</span>, among Minutes, Hours, Days, Weekdays,
Weeks, Months.</p>
<p>e.g. If the reset frequency is set to <b>Daily</b>, the counter will reset to '0' each day at the appointed time. If set to <b>Weekly</b> then the counter will automatically reset to '0' once a week at the appointed time.</p> |
...