...
This tab allows you to exclude from your stats calls that meet certain criteria from call statistics. To add an exclusion, click on the
| Inlineimage |
|---|
| URL | /download/attachments/1310815/add_button.png |
|---|
|
button, as shown below:
...
| Criteria_filter |
|---|
| Value3 | 2652626 |
|---|
| Value1 | CLI |
|---|
| Value2 | Does not contain |
|---|
|
Cost
This filter allows you set up an alarm in order to monitor calls below or above a specific cost. To set up the cost criteria, enter the relevant value in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when the cost of a call is greater than
.| Criteria_filter |
|---|
| Value3 | 10 |
|---|
| Value1 | Cost |
|---|
| Value2 | Is greater than |
|---|
|
Destination
This filter allows you set up an alarm based on the destination of the call. To set up the alarm criteria, enter the destination name (or part of its name) in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when the destination of a call is
.| Criteria_filter |
|---|
| Value3 | France |
|---|
| Value1 | Destination |
|---|
| Value2 | Equals |
|---|
|
Dialled number
This filter allows you set up an alarm when a full or partial number is dialled. To set up the alarm criteria, enter the relevant number in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when the dialled number begins with
.| Criteria_filter |
|---|
| Value3 | 074 |
|---|
| Value1 | Dialled number |
|---|
| Value2 | Begins with |
|---|
|
Duration
This filter allows you set up an alarm based on the duration of a call. To set up the alarm criteria, enter the duration in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when a call whose duration is greater than
seconds is logged.| Criteria_filter |
|---|
| Value3 | 3600 |
|---|
| Value1 | Duration |
|---|
| Value2 | Is greater than |
|---|
|
LCR code
This filter allows you set up an alarm based on Least Cost Routing (LCR) codes. To set up the alarm criteria, enter the LCR code in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when a call whose LCR code ends with
is logged.| Criteria_filter |
|---|
| Value3 | 680 |
|---|
| Value1 | LCR code |
|---|
| Value2 | Ends with |
|---|
|
Response time
This filter allows you set up an alarm based on response time. To set up the alarm criteria, enter the response time in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when the response time of a calls is greater than
seconds.| Criteria_filter |
|---|
| Value3 | 20 |
|---|
| Value1 | Response time |
|---|
| Value2 | Is greater than |
|---|
|
Start time
This filter allows you set up an alarm based on the time a call started. To set up the alarm criteria, enter the start time in hh:mm:ss format in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when a call that strted before
is logged in the system.| Criteria_filter |
|---|
| Value3 | 09:00:00 |
|---|
| Value1 | Start time |
|---|
| Value2 | Is less than |
|---|
|
Trunk access code
If your telephone system uses trunk access codes to connect calls using specific channels, you can set up an alarm based on calls made using these codes. To set up the alarm criteria, enter the trunk access code in the box provided and select the appropriate operator. In the example below, an alarm will be triggered when a call whose trunk access code is
is logged.| Criteria_filter |
|---|
| Value3 | 5480 |
|---|
| Value1 | Trunk access code |
|---|
| Value2 | Equals |
|---|
|
User
This filter allows you set up an alarm in order to monitor the calls of a particular user. To set up the alarm criteria, click on the
| Inlineimage |
|---|
| URL | /download/attachments/1310815/add_button.png |
|---|
|
icon to locate the user in the Directory; select the user and choose an appropriate operator. In the example below, an alarm will be triggered when a call is logged for the user .| Criteria_filter |
|---|
| Value3 | John Smith |
|---|
| Value1 | User |
|---|
| Value2 | Equals |
|---|
|
Weekday
This filter allows you set up an alarm in order to monitor the call activity for a particular day of the week. To set up the alarm criteria, choose the relevant weekday from the list provided and select an appropriate operator. In the example below, an alarm will be triggered when a call is logged on a Sunday.
| Criteria_filter |
|---|
| Value3 | Sunday |
|---|
| Value1 | Weekday |
|---|
| Value2 | Equals |
|---|
|
| 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> |
...