In my ongoing quest for finding new and shiny things, I came across the Sennheiser TeamConnect Wireless product range.
I must say its rather exciting to see products evolving in the “huddle room” space. Its been one of those areas that has been catered for by DIYers for some time now. Of course its difficult to justify spending thousands of dollars on gear for the huddle rooms especially when many organizations have so many of them.
Thats why we have seen devices such as the Jabra Speak 510 and the Plantronics Calisto 620. To prove the point just look at the sudden birth of Polycoms RoundTable 100, its targeted at the huddle room space and that all for around $1000 (US).
The Logitech ConferenceCam falls into this space very well (at $499.99 (US). Its great for Huddle rooms (1-6 people).
My first impression was that its aesthetically a beautiful product.
A quick overview of the product is as follows:-
It offers 3 connectivity modes:
Switching between connectivity modes is done by simply touching the mode you want on the top of the ConferenceCam.
The camera is superb!
The Audio is great provided the room isn’t too large, it provides:-
What I really enjoyed is the inclusion of NFC. I paired my Nokia Lumina 920 (I know its older..) using the NFC and it worked very smoothly. Entering the huddle room while on an active mobile call, I was able to flick the call over to the ConferenceCam by simply placing my mobile phone next to the NFC tag, that is awesome!
Its also rather cool that you can connect to the unit over WiFi to stream content to the HDMI connected monitor. I used my Surface Pro running Windows 8.1 to test this functionality.
Once the HDMI monitor is connected, on screen prompts guide the user through the connect steps
The Remote functionality includes:-
The remote is also very responsive with little delay.
Overall I think this is a great idea and believe it will make a very positive impact in the huddle room space.
Creation of Lync Regions (aka OCS Locations)
1. From Voice Routing create a Dial Plan for the Region you need to specify rules for. Remember to add rules to this Dial Plan.
Keep in mind that users residing in this region may dial numbers differently than users from a foreign location.
E.g. a local 7 digit number dialled from a Christchurch user will need to normalize to a Christchurch E.164 number, whereas the same number dialled as a local number from an Auckland user needs to be normalized to an Auckland E.164 number.
2. From the Conferencing tab add a Dial-in Access number for your new region.
3. From the Associated Regions area click on Add to find the Region that was created during STEP 1
4. Confirm that your new conferencing Region is configured complete with its own DDI.
5. Now you are ready to associate the users to the new Region. This is done by changing the user to the Dial plan policy you created in STEP 1.
As mentioned in STEP 1, users in this Dial plan will need Normalization rules matching their expected dialling behaviour. They will probably also have a DDI (Line URI) matching the Region.
6. All that remains is to close both Lync and Outlook and launch them again. This allows for the loading of the new profiles. Now your meeting invites should show location preference.
7. If for some reason the user needs to send a meeting request displaying a number other than their assigned region this can be done from Outlook as below. Select Meeting Options – Audio and Phone. Now select the required location for this meeting request.
Alternativly, you could show any\all of the Dial in numbers in the invite by simply adding the required region to the Conference