OCS Quality of Experience (QoE)

By -

OCS Quality of Experience (QoE)

While preparing my last post, I consolidated some quick facts about the QoE functionality that should benefit people who are considering deploying this role:

1. There is no additional server license (to your enterprise or standard license) required for this role. For OCS 2007,the role can be downloaded here.

2. In OCS 2007 R2, the QoE functionality and the Call Detail Record (CDR) functionality were merged into the OCS 2007 R2 Monitoring Role.

3. Supported OCS 2007 QoE Collocation:
a. The OCS 2007 QoE Monitoring Server cannot be collocated with other Office Communications Server 2007 server roles.
b. The OCS 2007 QoE SQL Database can be collocated with the QoE server, or installed on a dedicated server.

4. Supported OCS 2007 R2 Monitoring Role Collocation:
a. A variety of collocation scenarios are supported depending on your scalability requirements.
b. The OCS 2007 R2 Monitoring Role service and database can be collocated with a computer running Standard Edition (very small deployments only). If you do this, the full edition of SQL Server must be installed on the server (instead of the SQL Server Express Edition that is normally used).
c. The OCS 2007 R2 Monitoring Role cannot be collocated with a Consolidated Enterprise Edition.
d. It can be collocated with other individual roles such as the Archiving Server.

5. It can serve multiple pools.

6. A certificate is required on the QoE server, so that other OCS servers can use MTLS to communicate with it. This can be a self-signed certificate.

7. For QoE database sizing, the Office Communications Server 2007 Quality of Experience (QoE) Monitoring Server Guide has a formula that helps you size your database depending on retention settings and expected volumes.

8. Key software requirements:
a. 2005 Reporting Services SP1 or SP2 on the backend QoE / Monitoring role SQL database to get reports
b. For the OCS R2 Monitoring Role, you need to install the optional Report Pack for Monitoring server component.
c. Message Queuing must be installed on the computer that will run the QoE Monitoring Server.

9. Basic Hardware Requirements for OCS 2007 QoE
a. +2.6 Ghz dual processor with 4 Gb RAM
b. 1 Gb network adapter
c. 2 x 18 Gb disk for O/S and Page File
d. 2 x 36 Gb disks for database data and database log files

10. There is one known issue if you have an R2 pool and an OCS 2007 pool. From the OCS 2007 R2 release notes:

Office Communications Server 2007 R2 Pools Display Incorrectly in the Office Communications Server 2007 QoE Monitoring Server MMC Snap-in: “After installing Office Communications Server 2007 R2 Standard Edition or Enterprise Edition pool, the Office Communications Server 2007 QoE Monitoring Server MMC snap-in incorrectly shows the new pool as being a QoE Monitoring Server. If you try to connect through the snap-in, an error message is display. Resolution: You can safely ignore any pools that show up as a QoE Monitoring Server in the Office Communications Server 2007 QoE Monitoring Server MMC snap-in.

How the QoE data is Collected (high level):

1. QoE metrics are collected at the end of every VoIP and Video call from participant endpoints which include Office Communicator, Office Live Meeting, the A/V Conferencing Server, Mediation Servers and IP phones. The metrics are collected and sent in a SIP header to the server.

2. A QoE agent runs on each Front-End server. The agent then uses Microsoft Message Queuing (MSMQ) to transmit the data to the QoE or Monitoring Server. These agents are installed automatically on every Front End Server and Standard Edition server. They are activated automatically but no data is recorded unless a Monitoring Server is deployed and associated with that Enterprise pool or Standard Edition server.

3. The Monitoring Server takes the information from the queue and puts it into the SQL database.

Additional Links:

Office Communications Server 2007 Quality of Experience (QoE) Monitoring Server Guide

Office Communications Server 2007 Quality of Experience (QoE) Monitoring Server Audio and Video Metrics Processing Guide

Office Communications Server 2007 Document: Archiving and CDR Server Deployment Guide

Office Communications Server 2007 Document: Planning Guide

Microsoft TechNet – Archiving and Monitoring for Office Communications Server 2007 R2

Comments

Post a Comment

Popular posts from this blog

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", how...
Read more

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media ...
Read more

SIP port on Checkpoint firewalls

By -
Image
So here is another issue I have come across twice this week alone. When setting up the TCP 5061 rules on firewalls between DMZ Internal and LAN on Checkpoint Firewalls, the default SIP rule being chosen by admins is SIP_TLS_AUTHENTICATION. However while a simple telnet will work between the servers (it may take 7-8 seconds extra) and it will look like it works but no logs in the Logger or errors about certificates. What I found is that if you change the rule to SIP_TLS_NOT_INSPECTED this resolved the issue. We could then see traffic coming completely through. Here is some information from checkpoint directly: Source: https://sc1.checkpoint.com/documents/R76/CP_R76_VoIP_WebAdmin/87769.htm
Read more