Product Review: Sennheiser MB 660 UC

Let me start by saying that as of this moment the Sennheiser MB 660 UC is (by far..) my new favorite headset. Let me explain..

MB 660 UC

At first glance you could be forgiven for thinking that this is predominantly a music headphone. The absence of a boom microphone is what concerned me as soon as I started unpacking this beauty. I was expecting the MB 660 UC to pickup all the surrounding office sounds as it attempts to find my voice. This was not the case. Not even close!

It was actually quite the opposite. Not only was the MB 660 UC able to find my voice clearly, BUT it was able to filter out all other office sounds so effectively that callers were unable to hear me typing away on my keyboard (I tend to strike the keyboard in a less elegant fashion than most). I have a fairly loud neighbor to my desk (hello Travis) and in my daily Skype for Business calls he is often heard over my voice, despite my best efforts.

That’s no longer the case..

A good headset in my opinion needs to be comfortable, must have great music quality and needs superb conversation audio too. A decent battery life is appreciated and of course if it looks cool and doesn’t fall apart after rigorous use then I am happy.

The MB 660 UC stands above the rest with the use of an adaptive ANC (Active Noise Controller), *SpeakFocus  and  Advanced Own-Voice-Detector. Collectively these innovative technologies are the reasons why this headset is a superbly awesome device. The use of these 3 innovative technologies contribute to the removal of ambient noise while focusing attention to the speaker. Since ambient noise can vary, an adaptive ANC is particularly effective in adjusting to the ever changing ambient noise. Its a lot more technical than that, but you get the idea. Also all ANC claims are not equal, I tend to trust my ears and not the brochures.

The Plantronics Voyager UC has been my go to device in the office because of being wireless and fairly good at ANC. I have also used the Jabra EVOLVE 80 at my home office, primarily because of it being a lot better when it comes to ANC, filters out my squawking cockatiel to some extent but mostly creates a quite space for me to work in.

Don’t get me wrong, BOTH these headsets are really good. However, what has been missing (IMHO) is a device that is a hybrid of these two products. The Sennheiser MB 660 UC does that well.

What I liked:-

  • Touch Pad Controls – really cool to interface to functionality via touch pad
  • very comfortable – despite wearing it all day
  • no boom, I tend to snack at my desk and the boom can get in the way. Pushing the boom up on other headsets works but I do often forget to bring it down again
  • NFC pairing
  • Audio cable with answer button (2.5mm and 3.5mm jack plugs) and in-flight adapter
  • Battery time is great at 30 hours
  • Battery run down? No problem, switch over to cable mode
  • The 3 “braille” like dots on the left hand side of the headset – get left and right correct in the dark. You don’t want to put this puppy on back to front, cause the boom will be projecting to the back of your head 😉

* SpeakFocus and Advanced Own-Voice-Detector are unique to Sennheiser

Areas for improvement:

  • Although the touchpad is really cool, I found that at times I either accidentally disconnected a call or placed the headset on mute.
  • The mute function doesn’t place the Skype for Business call on mute, just the headset, this can be confusing
  • Love the idea of no boom, however it comes with a slight degradation in transmitting audio
  • Would like to see more obvious indication of left and right, you can get these on back to front quite easily if you not paying attention
  • The MB 660 doesn’t pair correctly 100% of the time to my PC, every now and then I have to turn it off and on again before it connects properly
  • The reception range isn’t quite as impressive as my Plantronics Voyager UC


Get the Quick Guide

Posted in Uncategorized | 3 Comments

Free Skype for Business Monitoring in 10 minutes! – V2 Released

Over the past 18 months I have had spells of sleepless nights at my disposal. What better way to utilize this time than to ponder on how best to monitor my Skype for Business environments.

Although this concept isn’t new (I release my initial attempt at this about a year ago), V2 brings many hours of tweaking and polishing. The end result is a more stable, user friendly application that can be deployed in under 10 minutes. That’s including watching my how to video!

Why is it useful?

There are many different schools of thought around how best to monitor environments. Some folks are drawn to the physical aspects and tend to monitor processing, memory and disk. While this is useful information, its hardly sufficient on its own as an acceptable monitoring solution for Lync\Skype for Business.

On the other hand, keeping a close eye on services and event logs can be most useful as well. This can lead to lots of verbose information and, on its own, monitoring services and events don’t quite form a complete solution.

My thinking involves generating traffic by means of synthetic transactions. It also involves a proactive approach rather than being reactive.

For example:-

If you cant send an IM from user A to user B then its broken, regardless of it being a physical resource issue, a stopped service, certificate expiration or some other issue we have yet to uncover. The fact that the IM attempt is failing is sufficient to get my attention and subsequent action.

Another example :-

If your test user cant make a PSTN call to a number of your choosing then there is a problem. Regardless of the true source of that problem (which will likely require an engineer). Be it monitoring service issue, SIP\PSTN issue from the provider or an issue with the SBC. It doesn’t really matter..Why? because the issue has alerted me and I am now looking at it.

What is this package?

It consists of two primary modules:-

  1. Skype Monitoring Tool – This allows you to run a selection of synthetic transactions against any Skype Front End Pool on a frequency of your choosing
  2. Monitoring Report App – This part monitors the results of the Skype Monitoring Tool, generates an alert email when tests fail and can also send daily and\or weekly reports of the test trends

Monitoring Reports.gif


  • The results of each synthetic transaction are recorded in the Event Log of the PC where the tool is running.
  • The Event ID’s represent both success and failure of tests with separate ID’s depending on the result.
  • Event ID’s also contain a brief description of the test being performed, and in some cases a hint to resolution.
  • The tool also has a Schedule tab that will setup a scheduled task to run the synthetic transactions on a repetition interval of your choice.
  • Any test failures can generate an Alert Email so that you can proactively address the problem
  • Instead of trying to replace your existing monitoring tools, this tool generates Event Logs you can simply add to your monitored stack.

What’s been added in version 2?

  • UI improvements
  • Lots  of bug fixes
  • Added an option for weekly reports
  • Split out the reporting and alerting functions allowing reports and alerts to be sent to different email destinations
  • Added the ability to specify the time and day for sending reports
  • Added the ability to specify custom subject text for both reporting and alerting emails. This is useful when monitoring multiple Pools as you can add a pool description in the email subject text
  • Ability to send secure mail, perhaps one of the more painful flaws from the previous version


How To VIDEO Here


This tool is NOT a replacement for the commercially available tools such as Nectar, EventZero or  Prognosis. If you are after statistical data and history, triggered actions, dashboards, network performance, Session Border Controller monitoring or even QoS and network monitoring etc. then please do spend the cash and talk to these folks.

Posted in How To, Lync 2013 Monitoring, Lync 2013 Tools, Lync Monitoring, Monitoring Tools, Skype for Business Monitoring, Synthetic Transactions, Tools, UC Sorted Tools | Tagged , , | 23 Comments

Edge Server: RTCMEDIARELAY Active Sessions high


The issue manifested itself to the agents in the RGS queues. Agents were reporting that the calls were taking long to answer, and as time went by, this issue degraded to the point that they were unable to answer calls.

Later on I also noticed:

  • degradation of meeting audio and video
  • If nothing is done the Edge Server will eventually blue screen

Environment was Lync 2013, Enterprise Front End Pool – 3 Front Ends. Single Edge Server.Logs not reporting any unusual behavior.


Restarting Response Group Service made no difference. A peek at the Edge Server revealed that the RTCMEDIARELAY  Service was reporting a high number of Active Sessions.


Monitoring this service, I noticed that the session count continued to rise over time. What was even more puzzling is that the count rose even though the user count was very low comparatively.

Using netstat I took a peek at active sessions but this was normal, no sign of the sessions reported by the RTCMEDIARELAY Service or of sessions not being closed.

Perhaps a quick restart of the services would free up the sessions I thought, but I couldn’t stop the services either (stop-CsWindowsService). Probably because of the restart service wanting to do this gracefully. Right, Edge server reboot it is.

The Edge server returned after a reboot and all appeared well, until a few days later when the RTCMEDIARELAY session count started to grow again.

Since I was tasked with a new pool as a side-by-side migration to Skype for Business, I decided that its not worth spending any more time chasing this issue as it will be decommissioned soon.

To my surprise, the new Edge Pool with 2 x Edge Servers on Skype for Business displayed the very same behavior. Only have about 10test users on the SFB pool.

Since this is now recurring on a brand new Topology, new Server OS and different product version (too much of a coincidence for my liking), I asked “So what’s the common factor?”

The virtual layer.

A quick call to the infrastructure engineer confirmed that VMWare was the underlying technology and “hasn’t changed since Lync 2013..”

I had since noticed that if the Edge Server with the hogh session count was not assisted then the machine would eventually blue screen. Its the dump data that revealed a “known” issue in VMWare.

The related article titled “Windows virtual machines using the vShield Endpoint TDI Manager or NSX Network Introspection Driver (vnetflt.sys) driver fails with a blue diagnostic screen (2121307) “can be found HERE.


By simply uninstalling the “NSX File Introspection Driver” in the VMWare Tools Setup on the Edge Servers, I was able to remove the faulting culprit.


Of course, one could disable the vShield Endpoint TDI Manager by means of the regedit modification mentioned in the article as well.

Rebooted the server and tested, all good. Monitored over a week to confirm.



Posted in Uncategorized | Tagged | Leave a comment