Fixes since 8.8.2.21:
- provisioning with DHCP Option 67 fixed
- RGS improvements
- audio stack improvements
- Call list handling improvements
- presence hardening
- UCS support
- logging improvements
Get the new firmware here: (login required)
Fixes since 8.8.2.21:
Get the new firmware here: (login required)
snom showed the snom 7EM for the first time at CEBIT 2014.
Photo posted by snom click here. In this picture we can see “Tile View” and USB connector plugged into the side of the snom 715.
Better Photo via https://twitter.com/Luca_Vitali/status/443862997732433920
Another Photo by https://twitter.com/ogerling/status/442965422334558208
“The modules extensions for snom 715, 720 and 760 presented at Cebit. Up to 3 modules positions, USB connection”
Shows that buttons can be assigned any of snom’s functions (contact search, contact list, etc), USB connection and backlit LCD.
Details from twitter photos and snom blogs:
Considering this unit works with the new snom 715 (not Lync Qualified as of this posting), this will likely be the lowest cost “console” setup available for Lync at this time.
I am getting more and more questions on which class of Lync devices is more “advanced”. As Lync Qualified (aka Lync Compatible/ 3PIP) devices get more and more features this question is getting less and less clear. Will Lync Qualified devices become more “Optimized” than LPE devices? This is a real possibility.
At one time I would have said Optimized devices are the information worker device while Qualified/Compatible are for those that want a more PBX-like experience. Qualified/Compatible/3PIP devices certainly remain the devices that provide the most PBX-like experience, but with the addition of Better Together over Ethernet, USB/Bluetooth headset support and video right from the devices (Polycom VVX 500/600), this line has become blurred. I still think that (at this moment) the information worker is best served by LPE devices, but this is becoming more subjective and will likely to change in the future.
Some things that still weigh in favor of LPE in my mind:
NOTE: This article is in progress. Also, if you see any errors/omissions, please comment. Please verify and do your own testing.
snom UC Edition | Polycom UCS 5.0.0 | Audiocodes 4xxHD | LPE “Aries” | |
Qualified | Qualified | Qualified(8) | Optimized | |
Boss/Admin | X | X | ||
BToE (Ethernet Better Together) | Beta | X | ||
USB Better Together | X | |||
Call Park | X | X | X | |
1 Button Call Park | X | X | ||
Parked Call Timer | X | |||
Lync Server FW Updates | X | X | X | |
Lync Address Book Search | X | X | X | |
Lync Address Book | X | X | ||
See Contact’s Lync Note | X | X | ||
ABS Other Contacts Methods | X | |||
Lync Contact Photos | (10) | X | ||
Monitoring Server Media Details | X | |||
Lync Server Setting Provision | X(5) | |||
Device MOH | X | X | ||
Change Device MOH | X(6) | |||
Transfer Directly to VM | X | |||
1 Touch Contact Buttons | X | X | ||
Safe Transfer via 1 Touch Button | X | |||
Visual Voicemail | X | |||
Video from phone | X(1) | |||
Supports Video Call Escalation | X | |||
Safe Transfer | X | |||
2 Button transfer | X | X | ||
Expansion Module | X | X(2) | ||
DESI Less BLF Buttons | some(7) | X | ||
Define buttons from handset | X | X | ||
Phone “In a Call” on handset lift | X | X | X | |
Dedicated “My Presence” Light | X | |||
Support for USB/BT Headset | X(3) | X(3) | ||
PC Port deliver non-default VLAN | X | X | ||
Intercom – Auto pickup, 2 way | X(4) | |||
Skype Federation audio calls | X | |||
Disable 2nd Call audio alert | X | |||
Adaptable RTAudio codec Narrow | X | X | ||
RTAudio Wideband | X | X | ||
View Outlook Calendar | (10) | X | X | |
1 Click Meeting Join | (10) | X | ||
Lync Meeting Roster Display | (10) | X | ||
Initiate Lync Meeting from phone | (10) | X | ||
DR Pool Failover without Reboot | X | X | ||
SBC + WAN Loss Scenario | (9) | X |
1) VVX 500/600 with optional camera, to Lync 2010 client only.
2) Announced, but not here.
3) Some models
4) Works, but not certified feature. Click Here
5) Snom marketing: Click Here; Technical Details Click Here
6) Possible, but not manageable from Lync Click Here
7) snom 760 and 821 have 4 DESI-Less Buttons
8) Only Audiocodes 420HD Lync Qualified as of this article: Click Here
9) as of 3/14 snom has addressed scenario, but FW to be released.
10) as of 3/14 snom UC Edition has demo’d but not yet released this feature: Click Here
More on Lync Phone Edition:
http://windowspbx.blogspot.com/2012/07/feedback-from-field-challenges.html
Another Device Comparison:
http://masteringlync.com/2012/10/25/lync-device-showdown/
Contributions/Credits/Assistance:
https://twitter.com/JonathanSteeman
According to a recent video created by snom, it appears that snom UC Edition (Lync Qualified) will get another new feature: centralized phone setting provisioning. The video references (but not necessarily limited to) the below settings:
The video does not elaborate but considering it notes that “all you need to do is type in your login credentials” it would almost sound like this will somehow leverage native Lync Server functionality.
This is a quite interesting development considering that even Lync Phone Edition devices currently have no way of mass provisioning device and user settings centrally.
Is this the new feature snom has noted it will unveil at IT Expo? I guess we’ll wait and see.
Was glad to chat with Paul Jamieson on the World Wide Partner Conference expo floor and get a demo of the coming “enhanced better together” (better together functionality over IP). I’ve reported before that various manufacturers are mentioning “enhanced better together” in brochures and websites, but it appears snom is the first to demo this feature. (NOTE: At this time there is no indication Lync Phone Edition devices will get this functionality, vendors have only mentioned EBT related to Lync Qualified devices).
snom estimates end of year 2013 availability for this feature.
The snom “Enhanced Better Together” (aka/being called EBT by snom folks) is enabled over TCP/IP without any USB cable between the snom desk phone and computer running the Lync client. The control and interaction of the snom 760 and Lync client was similar to what you would expect from a Lync Phone Edition device and the follow features were demo’d to me:
There appears to be no special user interface plug-ins in the Lync client to control the snom phone, just standard Lync experience. Also the control is bi-directional just like on Lync Phone Edition. For example: You can place or take a call on/off Hold from either snom phone or Lync client and it is reflected on the other endpoint.
On LPE devices if you start a video while making a call from the phone, the phone will switch to acting like a USB audio device for the video coming from the PC attatched. snom did not demonstrated how, or if, this works with snom EBT.
The snom personnel demonstrating EBT did not have technical details of how EBT works, although they did show that the snom phone was included in the Lync Devices in the Lync client just like Lync Phone Edition, headsets, etc as shown below. When I asked what the initial “pairing” experience would be like it was noted that in the final product it will be “plug and play and no extra software”.
And on the Lync 2010 client (Picture via @Alxlvanov)
According to snom folks both Lync 2010 and Lync 2013 client for Windows will support EBT. According to snom PR a new snom firmware will enable EBT but it does not communicate any version numbers at this time. A snom spokesman noted that the 8xx and 7xx series are slated to support EBT.
While I have not yet seen the pairing process, what I have seen seems to be implemented quite nicely from a UI perspective. It is interesting to see the snom UC Edition devices getting features not available for Lync Phone Edition devices. (Actually a quite highly requested feature: click here) Enhanced Better Together will add quite a bit of value to existing snom device installations and I suspect will bring snom to the table when previously only Lync Phone Edition devices were able to fill this requirement.
<end>
If you want to watch the demo (in spite of expo restricted bandwidth :-) you are welcome to below:
snom PDF Demo of functionality Below:
http://windowspbx.blogspot.com/2013/05/enhanced-better-together-lync-client-to.html
snom Doc on EBT:
http://www.snom-uc-edition.com/fileadmin/00_snom_UC_edition/06_Documentation/snom_presentation_EnhancedBetterTogether_2013.pdf
It appears that the the days of the “headset lifter” are finally starting to come to a close! (thankfully!) snom 760 and 720 now also support select USB headsets. (See our previous article/video on Polycom VVX500 supporting USB headsets)
We are using he snom 720 with the UC Edition firmware 8.8.2.8. Using the supported Plantronics Voyager PRO UC Bluetooth device, we just plug the device into the USB port on the side of our snom 720 and it the device worked. (there is no onscreen indication the phone detected the headset, but it seems to work)
There were several issues we noticed with the integration:
Currently Supported USB Headsets for snom 720/760
snom HS BT |
Plantronics Blackwire C620 |
Plantronics Savi W430 (Dect D100) |
Plantronics CS540a (plus APU-70) |
Plantronics Voyager PRO UC BlueTooth |
Note: I tested a Plantronics BlackWire 720 (a relatively new device) and it did not work with snom 720, so supported devices appears to be an important list.
snom wiki on supported headsets:
http://wiki.snom.com/Settings/soundcard_event_map
snom forum thread on USB headsets for snom 7xx:
http://forum.snom.com/index.php?showtopic=10892
The snom 710 is an entry level phone from snom. (which will presumably eventually supercede the snom 300). My first impression is that this device does not feel like an entry level device by size, button layout, button feel/feedback, speakerphone quality and fit and finish. The only place “entry level” shines through is in LCD resolution and 10/100 switch. I think the 710 will be very welcome to the snom lineup.
Here are some quick observations:
Cons
Photos
Below: Closeup of the LCD (128x48/backlit/black/white)
Below: Very close-up of LCD.
Below: 10/100 Ethernet switch and power jack. The 710 is POE enabled.
Below: High angle
Below: Low angle
Below: Wall Mount. Just remove the two base catches and you can mount this on a wall with no additional mounts.
Below: Keypad are hard plastic buttons that have a grippy texture. That are big and feel solid.The 5 defineable buttons on the right also have 1 color LEDs (green) in each button. (This is UNLIKE the snom 720/760 that have bi-color leds) With future UC Edition firmware (not here yet, but noted on the box), these buttons can indicate a Lync Contact’s presence. The Speaker/Headset have green LED to indicate toggle and MUTE red led.
Below: There is no dedicated Transfer button, but there is a context soft button for blind transfer. (You can also use one of the definable buttons for Transfer if this is important)
Below: Speakerphone is below the receiver and seems to work well.
Summary
Once again, the snom 710 is a solid unit with a design and pricepoint that I think will be very welcome.
The snom 360 is no longer a supported snom model on the “Apollo” UC Edition firmware (8.8.1.11) because of hardware limitations. In all fairness the snom 360 was never Lync Qualified and with a quite low screen resolution it makes sense to promote the snom 370 for UC instead.
Please note that UC Edition FW 8.7.2.16 is available for the snom 360 but is not Lync Qualified.
And, In all fairness, Polycom is taking a similar tack with the Polycom Soundpoint IP 670 (Unqualified device). It is supported by Polycom in UCS 4.0.2 but will not be in future releases.
NOTE: While the 720 box says UC Edition, this device currently is NOT Lync Qualified.
Below is my quick video review of the snom 720.
snom is starting to accumulate a bit of a history producing solid state mini PBX hardware: the CS410, Sheeva Plug PBX and now the snom ONE Mini.
Some unique things about this device that I noticed: The unit is, well, mini. The unit can be powered by Power Over Ethernet. (snom says a 60Kwh per year) The snom ONE mini hardware can handle 20 extensions and has quite a few features. The device support IPV6.
An interesting possible use for the device to be a failover PBX server in case the primary communication system fails. A separate and intersting use: This device is not Lync Certified, but it is possible to integrate snom ONE to Microsoft Lync, so by extension snom ONE mini should have no problem. (see guide here)
Below: side view: reset button, power, POE/1GB NIC, 2 unused places, USB 2.0, Another Unused place.
Below: LEDs
Below: back side
Of interest to our Lync audience may be our How to Integrate snom ONE and Microsoft Lync blog:
http://windowspbx.blogspot.com/2011/09/using-snom-one-as-sip-trunk-gateway-for.html
Of interest to our Lync audience may be our How to Integrate snom ONE and Microsoft Lync blog:
http://windowspbx.blogspot.com/2011/09/using-snom-one-as-sip-trunk-gateway-for.html
snom has been working on their “Apollo” Lync UC Edition firmware and it is has been released out of Beta and approved by Microsoft.
New Features in the latest firmware 8.8.1.11:
Here are some more articles to bring you up to date on snom UC Edition latest features:
Some of my testing notes for FW 8.8.1.11
Things that don’t work as expected/Bugs?
Things that need enhancement
Source:
http://forum.snom.com/index.php?showtopic=10090&#entry30242
Get The Firmware:
http://www.snom.com/en/your-personal-menu/snom-uc-edition-firmware-center/snom-uc-edition-88111/
snom has a small tray app for Windows and just today I noticed that DanielHa has written a small Mac utility to interact with snom phones.
Some features noted:
Opensource:
http://code.google.com/p/snomphone/
snom has released a UC Client for the snom ONE IP PBX to add Unified Communication features. Below is a look and video review of some of the features.
Some features on this first iteration
Missing Features (at the moment)
Bugs noticed
Review Notes
See the Video First Impression Review Here:
Get it here:
http://wiki.snomone.com/index.php?title=Installing_the_Attendant_Console
http://wiki.snomone.com/index.php?title=The_snom_Attendant_Console
Pros:
Cons:
Some more points:
Screen shot of configuration of the Vision
Buttons can be defined as:
More details on Microsoft Lync using snom BLF buttons for presence:
http://windowspbx.blogspot.com/2012/02/snom-brings-lync-presence-to-desk-phone.html
More details on snom Vision firmware version 1.2.4 Update:
http://windowspbx.blogspot.com/2012/04/snom-vision-sip-or-lync-attendant.html
A codeplex project aimed at making automating your snom phone has been released. What does this simple class library do?
Some interesting features snom 370 brings to the Microsoft Lync eco system:
Some features that all snom UC Edition devices bring to Lync:
Below is a snom 370 with 3 Expansion Modules:
Note: The snom 370 does NOT integrate via USB to the Microsoft Lync 2010 Attendant client. The presumption is that you are selecting a desk phone attendant scenario if using this phone.
Source: http://www.snom.com/en/products/unified-communications/microsoft-ocs-qualified-products/
snom 370 Specs: http://downloads.snom.net/documentation/data_snom370_en.pdf
UPDATE 3/22/2012 : The snom 370 is now on the Lync Official IP Deskphone page:
http://technet.microsoft.com/en-us/lync/gg278172
Note: While the snom 300 and snom 821 are Lync Qualified devices, the features noted in this article may not be included in the Lync Qualified certification process. I am still awaiting clarification on this point.
I know I am not necessarily in the majority when it comes to being interested in physical buttons on Lync phones but I stick to my guns: some scenarios require buttons for maximum efficiency.
snom is doing some very interesting work in bringing Microsoft Lync presence to phone buttons and indicator lights on their snom 300 and 821 Lync Qualified devices. With the snom UC Edition firmware you can have a button/indicator assigned to show a Lync user’s presence.
Now lets look at the snom 300 we just configured. The red arrow show the light (P4) we assigned to LyncUser01 and it is working! Since it is lit we know that lyncuser01 is either Busy, DND, Off Work, Appear Away or In Call status. This bring up the weakness of a boolean (light on or off) to show presence, but it is much better than nothing.
Here is a how Lync presence states map to the default snom 300 light states:
If you don’t like how snom mapped the lights, don’t get too upset—they’ve also given us a way to map/configure how they work as well! But first, let’s look at snom 821.
While the snom 300 series only has 1 color light, the 821 has 3 colors, which is very very helpful when trying to convey presence. In the picture below P3 Lync user is Away/Inactive and P4 is DND/Busy/In Call.
The default snom 821 Lync presence to light map is something like:
[Note: If the asterisked items above do not light as shown, it is likely because you did not do a Factory Reset on the snom device prior to upgrading from a previous firmware. To correct this you can either do a factory reset or add the state to led_on! as shown below. ]
In the snom web interface, click “Settings”. Find the spot where the below text is and you will see the settings you need to change to change the light mapping.
If you want to quickly change one of the above settings, just plug something like this into a browser:
http://192.168.1.65/dummy.htm?led_red_green=DND&settings=save
* - I’ve noticed when doing a 2 button transfer the experience is a little different than I normally expect: while the user you just transferred is being transferred, you will hear hold music, which will stop when the call is connected.
UPDATE: snom Vision seems to work fine with Lync presence. Upgrading snom Vision to FW 1.2.4 adds several major updates.
snom 821 with FW 8.8.1.1 BETA (above)
snom Vision FW 1.2.4 User Interface (above)
I was doing a bit of reminiscing tonight and decided to checkup on how the snom ONE forum “community” has grown since pbxnsip became snom ONE. I did a post back in Feb 2011 just after snom took in pbxnsip and compared that to today’s forum members to get an idea of the growth:
I’d say not too bad. snom has been doing quite a bit of work in the last year in the PBX area and desk phone area:
snom ONE remains a good PBX solution for SMB’s and hosted scenarios where UC is not a focus.
Source:
http://windowspbx.blogspot.com/2011/02/big-interest-in-snom-one-phone-system.html
The new snom 7xx series phones (snom 720 and 760) have not quite hit distribution as I write this. But a couple of weeks ago at the D&H Hershey show I caught up with Paul Jameison of snom and got a quick glance at the snom 760. Since the demo unit wasn’t plugged in, no pictures of the display.
Quick Summary
Below are some pictures and comments.
The snom 760 layout is a lot like the snom 821 with an extra set of definable buttons between 3.5” QVGA color display and numeric keys. When you return the handset of the 760 back in the cradle it has a very soft feel: Intentionally to avoid the “bang/Clunk” when returning it after a page or intercom. A nice touch.
The button layout around the display is similar to the snom 821 as shown above. There are 12 buttons/2-color indicators on the 760 and 18 buttons/2-color indicators on the 720. The screen is color.
The base of this unit is plastic compared to 8xx metal base. It requires no tools to install or change orientation (tilt level) which will be a welcome change from 8xx series phones.
The back of the 760 is shown above. Notice the USB which can be used for a snom WIFI or Bluetooth dongle. (click here to see snom bluetooth dongle) Also the dual 1GB ethernet plugs include LED’s to indicate the network status. Also the power plug port is shown. The unit can also be Power over ethernet.
The snom 760 keypad above: Once again similar to the 8xx. The mute, speaker and headset button have back light indicators.
Final Opinions/Observations:
Nice Video-Its marketing but shows phone nicely: click here
More detailed specs of 720/760: click here