Headset review: Plantronics v8200 UC

Another headset review coming up. This time it’s the new Plantronics Voyager 8200 UC, a boom less headset for the business market aimed at the productive worker needing a headset to block out unwanted noise in an open office environment.

The Plantronics Voyager 8200 UC is such a headset. It’s delivered in a soft pouch together with a USB Bluetooth dongle(always use it when connecting to your PC/Mac), a USB charging cable and a mini jack cable for those times when Bluetooth cannot be used(in flight mode for example). The headset is available in two colors, black(the one showed in this post) and white. It has a quite nice finish with leather and aluminum, and no microphone boom.

The boom less construction is surprisingly effective, and both audio quality during conversations and the reduction of background noise is quite good. The callee is not able to hear any noise in the background when making a call, even in a quite noisy environment. The ANC has two settings when turned on, that is Medium and High. With my limited hearing I’m not able to separate the two 🙂

There are also functions for open mic, mute etc. all controlled from the buttons on the headset. When playing music, you can control play/pause, skip forward and backward etc. Incoming calls are prioritized, and answering calls are done with the buttons on the headset or by the auto answer function if the headset is lying on your desk. This is one of my favourite features with Plantronics headsets designed for UC and certified for Skype for Business. The proximity sensors allows for automatic features as ANC on/off and automatic pause of movies/music and answer/mute calls when the headset is put on or taken off. The automatic disabling of ANC when the headset is not used also acts as a power saving feature.
There are however something to bear in mind when it comes to proximity sensors and machine connectivity. As mentioned earlier in this post, the USB dongle has to be used when connecting to a PC or Mac. That being said, I’ve experienced differences between Mac OSx and Windows operating systems when it comes to operating the headset. Specially the Mac OSx seems somewhat limited in regards to controlling playback of music from the headset. I’m sure this is a problem related to the operating system API and not the headset as it works fine in a Windows Client.

When it comes to playing music or watching movies using this headset, it delivers very good sound(at least in my opinion). When using the BT dongle that comes with the headset, I’ve not experienced any problems with audio playback. Some people has experienced audio delay when streaming audio over Bluetooth, but this is not my impression. I’ve tested audio streaming both with USB dongle on my MacBook and with my iPhone and experienced no audio delay.

The Plantronics Voyager v8200 UC is in my opinion a very good all round headset which delivers excellent performance both when used as a productivity headset and as an entertainment headset streaming music and watching movies. It’s a very good alternative to the Plantronics Voyager Focus UC, which in my opinion has been the best UC headset on the market up until now 🙂

Advertisements

Headset review: Jabra Evolve 75 UC

After a long time without writing anything, I thought it would be nice with a review of a new headset I got to try out.

Previously, I’ve linked to Staale Hansen’s review of the Plantronics Voyager Focus UC headset. This headset is, in my opinion, one of the best UC headsets on the market.

My review this time will be of the Jabra Evolve 75 headset, which is Jabra’s alternative to Plantronics Voyager Focus UC and a step up from the Jabra Evolve 65 which I wrote about in an earlier post.

The headset comes in two different variants, one with just the headset and the other with a USB desk stand for charging the headset. The Jabra Evolve 75 is certified for Skype for Business and has passed Microsofts test regime for UC headsets(or should I say IC headset (intelligent Communications)). It has ha quite nice “pouch” to cary it around in, which is kind of a hard case which keeps the headset in place and has a little pocket in the lid for the USB cable. It also has a small slot for the USB dongle(which you would want to use together with your PC/LapTop/Mac as this is automatically paired with the headset to give you all the softphone features).

Using the headset is quite easy. The button for power on/off and bluetooth pairing is located on the same earpod as the microphone boom. The boom auto-mutes the headset when you raise it to an upright position and it’s beeing kept in place by a small magnet. The power switch can be somewhat difficult to locate when wearing the headset, as it is quite small. On the other earpod, the buttons for listening in(disabling the ANC) and ANC on/off are located.

The mute button on top of the right earpod also allows for interaction with Siri(on iPhones). Press once, and Siri pops up on your phone asking what she can do for you 🙂

Press volume up/down simultaneously will turn on and off the Busylight indicator located on each of the earpods. This is one of the features of this headset that I like and miss with other vendors.

The Jabra Evolve 75 has the possibility to connect to two different Bluetooth devices simultaneously, giving you the option to stream music and answer calls on your preferred device.

All in all, Jabra Evolve 75 is a very good UC headset. Compared to the Plantronics Voyager Focus UC, it has some limitations and some advantages. The clearly visible Busylight beeing the one feature which I miss with the Voyager Focus, but the lack of smartsensors that are a very nice feature with the Foucs puts it in a 2’nd place in my opinion.
One example: On the Jabra Evolve, The ANC has to be switched off manually in order to save battery power. If you leav it on, it will consume your battery even if the headset is not used.

When it comes to audio playback and noise cancellation, both headsets are quite good and my ears are not in a state to be able to separate one from the other 🙂

Exchange: Renaming of room mailbox, Yeay or Nay?

From time to time we come across scenarios where a meeting room or resource has been removed, relocated or we simply would like it to show another name than the original one in our system.

So, is there an easy way to rename the resource in Exchange and have it reflected in the users calendar for previous bookings?

The answer is Yes, and No.

Renaming of the resource is fairly simple using PowerShell. You have to change the attributes Name, Alias, DisplayName, SamAccountName, and UserPrincipalName.

Set-Mailbox “TestRoom” -Name “NewTestRoom” -Alias “new_testroom” -DisplayName “New Test Room” -SamAccountName newtestroom -UserPrincipalName newtestroom@yourdomain.com

You also have to change the FirstName attribute using the Set-User command:
Set-User “NewTestRoom” -FirstName “NewTestRoom”

So, does this do the trick?

The answer is yes, in regards to new bookings. The problem is that the name change does not reflect in the previous bookings of the resource. The old name will still show in the booking, but if you click on the name of the room, the new name will show in the properties of the resource.

There is no way to change the name of the room without deleting the booking and make a new reservation with the new name. The room is reserved in the system with the old name, and there is no way for Exchange to display the new name in available resources(if you choose Change Room in the booking) without deleting the reservation and making a new one.

Skype for Business Event ID 1034.

After migrating to Skype for Business and removing Lync 2010/2013 pools, you may encounter an event ID 1034 stating that the LS File Transfer Agent encountered an error while accessing a file share.

The file share referenced will be the share on the removed Lync 2010/2013 pool. If you run the command Get-CsCentralManagementStoreReplicationStatus -CentralManagementStoreStatus, you will se an entry of DeletedReplicas that states the server FQDN of your deleted Lync pool/server. If the server is deleted from the topology not to be used again, you can proceed with deleting the server from the XDS database.

 

The easiest way to accomplish this, is to make sure that all Lync server components are removed from the Lync server in question. Simply go ahead and remove the Lync components from the server using Add/Remove programs. Make sure to reboot the server after the removal of the Lync components. The error message in the event log should disappear after this operation.

If this is not successfull, you will have to remove the replica ID’s from the SQL database(XDS).

This procedure from the UC Lobby blog by David Paulino should do the trick.

Issuing certificates with longer validity

Nice post, should be carried out in every environment where internal certificates are in use. Having the Lync/Skype for Business service beeing interrupted every second year because of short term internal certificates is nothing else but annoying.

Rune's blog about things I see and UC

In my previous job as a hired consultant I generally wanted the Lync/Skype for Business servers to have certificates lasting beyond the two year default validity period. Why? Because I, along with the customer, would consider a Lync or Skype for Business solution to have a horizon stretching beyond two years – and therefore issuing a certificate that would expire only after two years would be meaningless.

View original post 87 more words

How to set IPv4 as preferred IP on Windows Server using PowerShell

Nice tip from Ståle Hansen on how to set IPv4 as preferred IP on Windows Server using PowerShell.

msunified.net

IPv6 Internet

Sometimes working with Lync and Skype for Business I see that the services are trying to contact other servers or localhost which returns an IPv6 address. If the service is set to run only on IPv4 the service will fail and not find the listening interface since it is not listening on IPv6. In these cases I do not disable IPv6 but prefer IPv4. This needs to be done in registry and a reboot is required after the change. Do not disable IPv6 on the network card because that will not work.

Here is a simple way to do it using PowerShell

Check the values below for other options

  1. Type to re-enable all IPv6 components (Windows default setting).
  2. Type 0xff to disable all IPv6 components except the IPv6 loopback interface. This value also configures Windows to prefer using IPv4 over IPv6 by changing entries in the prefix policy table. For more…

View original post 75 more words

Skype for Business Online and PSTN Conferencing

As you all probably know, Microsoft has enabled the possibility of having Dial-in PSTN Conferencing in Skype for Business Online. In order to do this, you either have to have an E5 license plan in O365, or you can purchase the add-on for PSTN Conferencing in your excisting E1 or E3 plan.

PSTN Conferencing is a very valuable add-on to the O365 Skype for Business as it will enhance the possibilities of joining meetings without having to use a client.

To read more about PSTN Conferencing, visit this site on Microsoft.com:

Dial-in conferencing in Office 365

To se which countries have PSTN Conferencing available, check out the list here.

Skype for Business Server 2015 Updates and Build Numbers.

In this post I will try to keep you updated with the current releases and build numbers for Skype for Business 2015 Server.

As of now, there has been released five updates for Skype for Business Server 2015. The Microsoft download page is updated with the latest SkypeServerUpdateInstaller, so the link will always point to the most recent CU.

Server updates and Build Numbers:

May 2017 Update – Build number 6.0.9319.281(CU6)
Be adviced: CU6 has been reported to break Web Conferencing Edge service due to updates to the .Net Framework.
Check out this TechNet article if you experience problems.

February 2017 Update – Build number 6.0.9319.277(CU5)

November 2016 Update – Build number 6.0.9319.272(CU4)

June 2016 Update – Build number 6.0.9319.239(CU3)

March 2016 Update – Build number 6.0.9319.235(CU2)

November 2015 Update – Build number 6.0.9319.102 (CU1)

 

This post will update as new CU’s are released.

Missed Call Notification – Not Working…..

A known problem and the solution 🙂

UC Consultant Blog...

Since November 2015 there has been issues with Missed Call Notification from Lync/S4B to Outlook.
There has been written many blogpost about this, but I will here try to summarize how to fix it – Until Microsoft release a permanent fix for the issue.

The following Windows Update’s are relevant for this issue.

I have been trying to solve this at several customers, but made a breaktrough today.

I have been searching for KB3101496 – Nothing to find!
Searched in Registry clearly shows that the patch is installed, but it’s not visible in Control Panel

Additional research pointet me in the direction of KB3114351.

Looking for KB3114351 in Control Panel showed that this patch was installed.
Did a Uninstall of this patch, with a following reboot.
After a reboot, the KB3101496 was again visible in Control Panel.
Did a uninstall of this patch as well, following with a…

View original post 61 more words