I missed this Snom UC/Lync firmware release on December 6, 2011 . This is the 2nd official OCS/Lync firmware release for the Snom UC phones. The phones that are supported are listed below.
I have been running this firmware all day on my Snom 821 and its working very well. BTW the best feature of the Snom UC/Lync phone for me is the ability to be logged into multiple Lync accounts at once!
I do not believe this firmware is available publicly, so you need to be a Snom partner (http://www.snom.com/en/ocs/) or ask your Snom partner to get it for you. I’ve posted the release notes for this release below.
snom UC edition 8.7.2.13
Snom 300 snom300-SIP 8.7.2.13
Snom 320 snom320-SIP 8.7.2.13
Snom 360 snom360-SIP 8.7.2.13
Snom 370 snom370-SIP 8.7.2.13
Snom 820 snom820-SIP 8.7.2.13
Snom 821 snom821-SIP 8.7.2.13
Snom 870 snom870-SIP 8.7.2.13
Snom MP snomMP-SIP 8.7.2.13
Snom PA1 snomPA1-SIP 8.7.2.13
New Features & Fixes –
Feature – Server side Address Book Search (ABS)
Feature – Phone follows server side keyboard lock
Feature – User can set presence state on phone
Feature – New display user interface (with scrolling for long text)
Feature – Added CAC support
Feature – Added E911 support
Feature – Exponential backoff algorithm on “registration, TCP disconnect, reboot”
Feature – Different audible Ringtones for “Response Group” and “private line”
Feature – Added MS-conversation ID to support certain Attendant console transfer scenarios
Feature – Added support for Lync (W14) level call forwarding
Feature – Added support for Lync (W14) level message waiting indication
Fixes:
The splash screen of the UC version was wrong (fuzzy)
snom 300 Dialing PSTN number from call logs dials
snom 300 No update of missed call and received call in snom 300 call log
snom 300 restarts in call deflection scenario of lync client
Issue with not releasing TURN ressources found in MS IT scenario fixed
snom 300 : Snom 300 displays mediation server FQDN when Attendant console does consultative transfer between PSTN Number and Snom 300 user
Unresolved Issues and Caveats
snom 300: On older series phones, there can appear weird characters during bootup
When user places an E911 call on hold, the UI does not display a forbidden message
In certain environments indication for 2nd incoming call might not work
In certain environments audio of one participant of a local conference might be missing
During PSTN call with snom 300, second PSTN incoming call overrides identity of first connected call on display
