I have had a lot of success with the snom UC Edition software for snom phones. Currently the snom 300, snom 370, snom 710, snom 720, snom 760 and snom 821 are officially qualified for Lync 2013. The snom UC600 is a traditional IP desk phone especially designed for use with Microsoft Lync.
It is still possible to install the UC edition software on phones that are not officially qualified, the most recent for me being a snom PA1. Obviously there are no guarantees that all functionality will work, but so far I haven’t had any issues. The snom PA1 is a PA switch which picks up incoming calls automatically and outputs the audio to the built in 4 Watt amplifier, or to a line out connector if you want to connect it to a building PA system. In my case I have configured it as a Lync endpoint and connected to the speaker system throughout the building. Calling the configured Lync user enables staff make announcements.
The following guide has been generalised to assist with configuring any snom UC device. If you have not already installed UC edition then you will need to visit the Snom website and register, then copy the URL to the download file:
Once you have plugged in and powered up the device, browse to the web management portal.
Finding the phones IP:
- Snom PA1 – The default address is 192.168.0.2/16, otherwise if you have DHCP the device will get an address this way. On the PA1 you can get its IP address by pushing
the IP/Reset button and it will read it out. - Snom 710 – Press and hold the “X” at the welcome screen, then find it under “System Info” – “IP Adr”.
e.g. https://192.168.0.2
admin password and the HTTP web interface password navigate to “Setup”-“Advanced”-“QoS/Security”:
Select “Apply” then log back on using the HTTP server credentials you just set. Note that in some cases you may need to select “Save” at the top of the settings page:
Account Setup
web interface:
Important settings
Display Name: Name to display on phone where applicable
Account: SIP sign-in address NOT including @sipdomain.com e.g. peter.pan
Password: your lync password
Registrar: SIP domain e.g. neverland.co.nz
Authentication Name: Username e.g. [email protected] or NEVERLANDPeter.Pan
Optional Settings
TCP/Port 5060) sip.domain.com:5061;transport=tls (Use TLS/Port 5061)
Ensure that “Server Type Support” is set to OCS/UC:
RTP Encryption should be set on “ON”:
If you have any issues check out the SIP Trace and Log, unlike a lot of products these logs are very useful in finding the problem.
Thanks for the article, Andrew. I know its a bit dated, but I wonder if you’ve had follow up experiences with the PA1, specifically for SfB Online / Cloud PBX deployments? I have a customer who wants to be 100% cloud but continue to leverage their PA system and I don’t see why this wouldn’t work. Granted, the end users would need to call the DID associated to the lync/sfb user account in O365 but technically, I think it should work. Have you had any experience with the Snom PA1 and SfB Online deployments?
Sorry for the delay, I missed this! I haven’t used a PA1 in SfB Online, and unfortunately Snom no longer qualify their products for SfB. I’d say give it a go and see what happens.