ShoreTel Contact Center C2G Interaction Reports

Prior to release of ShoreTel Contact Center Version 5.0, reporting was essentially statistical analysis. The Contact Center had very useful report generation capabilities that included the ability to add and delete columns to existing pre-defined reports. The reports, however, were generated largely as summary reports based on accumulated totals of events. For example, you could generate an Agent Performance report that could report the total number of calls presented; total call answered; average call holding time; average talk time over a specified interval. Though very useful for tracking aggregate call volume, the reports could not track individual agents events. The Shoretel Contact Center had no equivalent of the Call Detail Reporting that you might find in the ShoreTel IPBX database. What information was available, was derived by arithmetic manipulation of totals or the equivalent of “peg counters”. Each agent had a bucket for total calls, but the details of each call were not archived in the database. This led to reports that indicated total calls for the period were 19.2 as calls were averaged over an interval.

ShoreTel Contact Center 5.0 takes a major step forward in the area of reporting. A new feature named variously “interaction reporting” or “cradle to grave” reporting has made a major positive contribution to the contact centers already strong feature set. The database has also migrated from Sybase to MySQL, which completes the database migration strategy that ShoreTel began with version 7 of the IPBX. In the ECC database contains a table structure that can be generally summarized as a configuration database. A second database, named C2G has been created and does not appear in contact centers before version 5. This database contains about 22 tables of which four are effectively the equivalent of “CDR” records. A table named events, tracks all the incoming event detail and includes a GUID that can be used to link back to the CDR record in the IPBX. This database makes it possible to create very detailed reports. For example, assume you needed a report that listed each call handled by a specific agent over an specified interval. Additionally, you want the agent detail to include a call disposition status or wrap code. Prior to the C2G database, this type of report would have been impossible. With the new C2G database, you can generate the report very easily using any MySQL administration tool, like SQLyog. Interaction reporting is a major step forward for ShoreTel Contact Center and one that the market will be very excited to receive. Look for a video update in our online library for a “hands on” look at how to setup configure and make use of Interaction reporting!

ShoreTel Enterprise Contact Center Interation Reporting

To VOIP QOS or not to VOIP QOS?

In telephony, IP QOS is somewhere between a science and an art. Setting up VOIP QOS on your network is essential for toll quality voice from end point to end point, especially across a WAN. Historically, in ShoreTel, IP packets were marked with the DSCP value set in the Call Control Options page. Generally this is generally set as a value of 184 or Precedence Level 5, what CISCO would call Express Forwarding or EF. This value is represented as 184 (10111000 or 46) but as a TOS/Differential Service Control Point marking it is only applied to the IP layer and has no impact on your LAN. Additionally, IP packets were only marked on the media stream between IP phones, not between the switches or between the phones and the switches. Version 9 of ShoreTel, now reports “system wide” TOS/DSCP support, which represents a significant improvement in your ability to control VOIP QOS. At the LAN level, it is important to know that you are working with Ethernet frames and for this reason the only QOS marking available to you is a VLAN tag. Inside the VLAN tag, three bits have been set aside for precedence markings and are named COS for “class of service”. If you are NOT running SIP on your network, you have another QOS tool available to you. ShoreTel media streams in other than SIP environments run on UDP port 5004 enabling you to prioritize voice over data at the transport level. ShoreTel also provides the opportunity for you to establish “admission bandwidth control” per site, to assure that the next phone call does not exceed the limits you have set with this parameter. Beware that this parameter exists only within the ShoreTel architecture and has no real knowledge about the actual bandwidth utilization of your network. Establishing this threshold is left entirely to the engineer designing the network. In large part IP QOS is best determined at the IP level and is heavily dependent on establishing queue in your routers that service latency sensitive traffic, voice and video, over less sensitive best efforts traffic. Knowing about these different QOS markings is the science. Knowing how to pass markings from one level to the next is the art of QOS!