Call Quality Dashboard Config/Use

Overview

The Call Quality Dashboard (CQD) is a new feature that allows you to have a new view of your CDR/QoE information.  Unlike the existing Monitoring Server, this feature doesn’t require or rely on SQL Reporting Servers (SRS) but rather used the SQL SAAS Cube, Archive Database and a web portal.

EXPERT NOTE: Do not confuse the Skype for Business Archive database that is used as part of CQD offering.  The archive database is a copy of your existing archiving data into another database.  This database is used as the back end database used by the SAAS Cube.

The software ships as a separate download then the main SfB Server and is available on the Microsoft Download Page here.

It is important to know that you should deploy a separate server for the purposes of CQD and not attempt to re-provision another server as the performance hit of SAAS can be significant.

Setup/Install

The setup and configuration of the server is well established here.

It boils down to a few main steps:

1) Install IIS Pre-Reqs

add-windowsfeature Web-Server, Web-Static-Content, Web-Default-Doc, Web-Asp-Net, Web-Asp-Net45, Web-Net-Ext, Web-Net-Ext45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Url-Auth, Web-Windows-Auth, Web-Mgmt-Console

2) Install SQL Server

3) Product Install

This really boils down to three main areas within the configuration.

a

Here we indicate the the location that stores our existing Lync QoE Data.  Second we specify the instance name of the QoE Archive server.  Again, this is the server you just installed SQL Server and Analysis Server onto.  You also must pick a location where to store the files.  These should NOT be on your C (system) drive.  The partition (single vs multiple) is based on if you installed Standard vs Enterprise.  If you have a large amount of data you will see a significant performance increase by selecting multiple partitions/Enterprise SQL.  Lastly, you must specify a username and password that has the correct permissions.  In this instance it is read to Lync QoEMetric database and account that can login to the QoE Archive server (the one we are creating now).

b

On the Cube Configuration page you will specify the instance name of where the QoE Archive database is (NOT YOUR QoEMetrics Database).  You also need to specify which server will run the cube analysis.  In a larger deployment you might split the Archive DB and Cube to different servers.  Lastly, you need to enter a user with the correct permissions.  In this instance it is a user that will run permissions, read/write on the QoE Archive database.

c

On the Portal Configuration page you must specify the QoE Archive SQL Server (AGAIN, NOT THE QoEMetrics Server), Cube Analysis and Repository Server.  This can be the same server in all three instances if you are doing a single server deployment.  Additionally you must specify an account that will run as the portal user.  Setup will create a login security principal to QoE Archive database (with read privilege), a login security principal to Repository database (with read and write privilege) , and a member in QoERole (with full control privilege) for the Cube.

EXPORT NOTE: The installation recommends that you use three different accounts for access.  Clearly it is possible to use a single account.  Outside of a strict security concern there isn’t a technical reason one account won’t work.

Using the Portal

At this point in time your portal is configured and should work.  There are steps for configuring debug mode on TechNet (which you should do) and limiting access on the server.  To access the server, simply browse to the URL (http://server.domain.com/CDQ/).  You should see something very similar to this.

d

Troubleshooting

For the most part I have not run into many problems.  You can check the health of your system by viewing the health page at http://server.domain.com/CQD/#/Health .

The largest issue I’ve seen is when I’ve needed to re-install the product because of corruption or upgrade.  When attempting to re-install the product you can select to reuse the same QoE Archive database but on the Cube Configuration page you will be prompted that a QoECube already exists and you cannot continue.

To solve this problem:

1) Launch SQL Management Studio

2) Select Analysis Server and connect to your database.

1

Don’t pick Database Engine.  You won’t find the object and the installer will continue to fail.

3) Select the QoECube object and delete.

2

In the coming days I’ll be posting some neat tricks and how-to articles on using the Cube.  It’s a powerful application that allows you to create your own reports.  It doesn’t have nearly the feature set of paid products like EventZero or IRPrognosis but it certainly can insight then the standard reports.

 

 

23 thoughts on “Call Quality Dashboard Config/Use

  • May 6, 2015 at 6:30 am
    Permalink

    Thank you for this. Could you please provide some more details on this new feature. We’re currently in the middle of an S4B implementation using just a single FE and Edge (about 60 users). Enterprise Voice will be used, but no Monitoring server has been deployed yet.

    Can we just deploy Monitoring with CDR/QoE and also add CQD to the same server. Does it complement or fully replace the existing feature set…

    Reply
    • May 11, 2015 at 9:28 pm
      Permalink

      CQD does not fully replace the QoE/Monitoring database. Think of it as an addition and more information in your environment.

      Reply
  • May 11, 2015 at 2:59 pm
    Permalink

    I’ve installed the CQD but when i browse to the web page for the CQD the page loads but doesn’t generate any report. Instead it gives the error:- “We couldn’t perform the query while running it on the Cube. Use the Query Editor to modify the query and fix any issues. Also make sure that the Cube is accessible”.

    Any ideas what could be causing this error?

    Reply
    • May 17, 2015 at 12:15 pm
      Permalink

      I have the same issue an was going to ask the same question.

      I have actually install CQD on the Monitoring server, albeit that the CQD stuff has gone into its own instance – the MS information at https://technet.microsoft.com/en-us/library/mt126221.aspx “Single Server Configuration” indicates that this is a support scenario, even though Richard has not recommend this deployment above. I have used a single domain user for all access.

      Even more odd, I have just attempted to log back on and am now see just the “Loading …” screen.

      Reply
      • May 19, 2015 at 8:14 pm
        Permalink

        As mentioned, it’s definitely supported to do a single server but the general guidance is to do a different box for CQD to run on.

        Reply
    • May 18, 2015 at 4:52 pm
      Permalink

      Ok,, I think I’ve figured why this wasn’t working. The default installation of CQD places the “QoE Archive Data” database in the “C:Program FilesSkype for Business 2015 CQD” folder (first step of the wizard above). You can, of course, place this elsewhere (as Richard suggests), but for me this would be fine. I don’t have a second VHD attached to this machine either.

      However, the golden nugget that I think is missed above but on Microsoft CQD deployment steps (Step 6 on https://technet.microsoft.com/en-us/library/mt126252.aspx), in the NOTE box for this step is an important bit of information that tells us we need to add NTFS file permissions to folder that contains the “QoE Archive Data” database for the service account that actually run the instance of SQL in which the this database is housed. For me this is the account “NT ServiceMSSQL$LYNCCQD” on the local computer (your SQL Instance name may vary). I gave this user full access to the “C:Program FilesSkype for Business 2015 CQD” folder, but if you use Multiple Partitions and specify different directories, you will need to give that user permission in both locations.

      It would seem that the other Database entities (the QoERepository Database, and the QoECube, get installed to the default SQL locations, and as such, the correct folder permission are already applied.

      So, I got it working – but what can I actually do with this…….. I’m not entirely sure. OOTB, I have a couple of bar charts (‘All Audio Streams’ and ‘User-reported Call Quality Rating Histogram’), but still can’t see a simple way to drill down into the actually faulting calls. It seem like a very high level overview showing that you had ‘some’ issues along the way, but not exactly what. I’m sure there will be others much cleverer that I who would be able to make additional reports, but this is not my specially by a long shot.

      In addition, as it still relies on the QoE Metric DB, I don’t think it will give any kind of real time analysis.

      Reply
  • May 13, 2015 at 5:43 pm
    Permalink

    Hi Shawn,

    This morning I have deployed CQD for Skype For Business, and also got the notification like you. Then, I went to Setting > System Health on CQD page and figured out that “No data is currently being transferred from the QoEMetrics database to the QoEArchive database. ” .

    I have still figured out why data is not transferred from QoEMetrics to QoEArchive. So, I will re-post whenever got the reason 🙂 Have a nice day!!

    Reply
    • May 20, 2015 at 2:03 pm
      Permalink

      Hi Shaw, see my post above – it might help you out

      Reply
    • May 23, 2015 at 12:49 am
      Permalink

      Hey,
      I had a similar issue which was resolved by processing the Cube from the SQL management studio.
      You can take a look in the following post http://wp.me/p2Czvk-15E and see if that would help.

      Reply
  • May 17, 2015 at 9:49 am
    Permalink

    I’m just in the process of setting this up to see what it can do. My main worry is that it will still be unable to deliver real time analysis on on going calls, and be unable to break down the call analysis hop by hop. What I really want to know on a call that has packet loss, is where that packet loss happened – i.e. between the internal client and the FE, or to the edge and an external client etc. Point to point call may well be difficult to break down especially if the media is direct, but if it traverses additional ‘video’ hops in the Lync environment, then it would be nice to know what is going on.

    Reply
  • November 3, 2015 at 1:13 pm
    Permalink

    When you say:

    “It is important to know that you should deploy a separate server for the purposes of CQD and not attempt to re-provision another server as the performance hit of SAAS can be significant.”

    Are you talking about a separate SQL server? If only speaking of a separate SQL server, do we just run the install on the FE server to see the portal?

    Reply
  • November 9, 2015 at 6:20 am
    Permalink

    Problem after deploying the CQD, I give the correct right to the database folder, I do a Process on the Cube but no data are transferred from the QoEArcive database into the Cube.

    Database QoEArchive is correctly populated, but the cube is empty ….
    No error in the System Health, no error in the event log …..

    Any tips ?

    Reply
    • January 26, 2016 at 2:36 pm
      Permalink

      Good article, but missing some more in dept info. I also struggled like many with the error :
      “No error in the System Health, no error in the event log”
      ” “We couldn’t perform the query while running it on the Cube. Use the Query Editor to modify the query and fix any issues. Also make sure that the Cube is accessible”

      What I did first was to grant run account full access permission to where database are stored.
      Then this guide to process : https://guybachar.wordpress.com/2015/05/18/skype-for-business-server-2015-call-quality-dashboard-cqd-does-not-display-data-after-initial-deployment/
      Then be sure qoe account has read permission to qoemetrix database on the monitoring server.
      Now that everything is up, I need to understand how to read it and create my own reports. Lets see how deep it can go 🙂

      Reply
  • February 4, 2016 at 12:02 am
    Permalink

    I can’t get this installed – at the cube configuration page after I put in the information it just says “we couldn’t connect to the cube server.” I’m trying to install on the same server from which I am running the installer and yes I am a local admin on that server and I tried using both a service account as well as my own account which is part of all the domain and local admin groups.

    Reply
    • July 14, 2016 at 9:56 pm
      Permalink

      Jason – when you are installing on the same server as Monitoring Server you may have originally installed SQL Server without the SSAS (SQL Server Analysis Services) feature as Monitoring/Archiving server does not need this. As shown in the top of this blog, make sure “Analysis Services” is installed. In the SQL Server Installation Center you can select on the Installation tab to add features to your existing installation where you can add this service

      Reply
  • February 8, 2016 at 9:04 am
    Permalink

    Who knows where to change the QoEMetrics SQL Server after installation?
    We changed the backend.

    Reply
  • August 4, 2016 at 5:55 am
    Permalink

    HI

    Great Article.

    I have deployed the CQD while opening the report i only see Audio streams as i see you have also pasted the screen short which also shows only “Audio streams” can you please tel do you see the Audio/application sharing reports.

    Thanks & Regards
    Raju

    Reply
  • August 12, 2016 at 1:14 am
    Permalink

    Creating custom report is quite cumberso. Has anyone ‘published’ particularly useful/practical CDQ reports by chance? (i.e., reports that provide meaningfull information that is actionable.)

    Reply
  • October 31, 2016 at 1:30 pm
    Permalink

    Hi,

    Could you please advice what to check if I’ve got an error right from the beginning (at QoE Archive configuration screen) saying the: “We couldn’t connect to the QoEMetrics SQL server. Please make sure the server name is correct, and that you have access to the server, Also please make sure that the computer you’re installing is in the same domain as the QeEMetrics SQL server”?

    I’m trying the install CQD on the same SQL server where is the Monitoring and Archiving instance, and yes, I’ve Installed the Analytics Service on the SQL instance and configured the Sql mappings on the QoEMetrics database.
    I’m also able to connect with SQL Management studio using SQLSeverMONARCH instance with my windows credentials.

    Thanks,

    Reply
  • November 17, 2016 at 1:51 pm
    Permalink

    I have installed QoE Archive on our back-end databse server. This was succesfull.

    However I want to install Cube and Poral on a different server

    The installer assumes incorectly that the Archive database is on the same server.

    How can I solve this?

    Reply
  • September 26, 2017 at 12:42 am
    Permalink

    CQD is up and running fine but I would like to import the Operations Framework templates. In CQD online there is an import link in the detailed reports section. In my on-premises installation that link is not present. Any clue why? I’ve tried signing onto the Portal box with the service/user account, with a local administrator account and neither works when using localhost/cqd. Of course, the link isn’t there when accessing the CQD page from outside the server too.

    Reply

Leave a Reply to Michael Cancel reply

Your email address will not be published. Required fields are marked *