snom EHS Advance adaptors purchased from ProVu Communication Ltd (after Jan 2013) now come with the cable required for electronic hook switch capabilities on the snom 7XX series; this includes the snom 710, 720 and the 760. This is great news for users wanting to use a wireless headset.
Check out our new headset selector to help you to find a suitable headset for your customer’s requirements.
Yes it is hard to believe, but it is now 10 years since ProVu supplied their first snom phone. Back in 2002 when England had just lost again to a fluky Ronaldinho goal in the Japanese World cup and Broadband was just becoming widely available with speeds of just 256K ProVu reached agreement with snom to become their first UK Distributor.
Even in those days it was clear that VoIP was going to represent a major challenge to the long established traditional communication methods of ISDN and analogue lines. And with the advent of affordable Broadband and the SIP voice protocol it was clear that businesses were going to want to take advantage of the flexibility to call colleagues and customers anywhere in the world using the same Internet connection that they were using for normal business data.
The first snom model to be sold by ProVu was the snom 100 (view the snom 100 datasheet) which had an elegant designed handset. This also had the habit of elegantly sliding off the cradle with the slightest of knocks or vibrations to the table. snom quickly moved on to the snom 190 and 200 which set the standard for SIP phones with their ability to be provisioned automatically and technically superior SIP stack.
Ten years on snom have moved from strength to strength, with a wide range of phones and ancillary equipment that is still considered at the cutting edge of internet telephony.
ProVu are delighted and proud to have been snom’s UK Distributor for over 10 years now and look forward to achieving even greater success over the coming years.
With growing interest in MS Lync, more people are moving to Lync online(Office 365) to benefit from the Microsoft feature rich platform. Some people think it’s a good investment and some think its not. Well I shall leave it to people to decide.
Coming back to the original subject, we are being asked if Snom Lync firmware supports Lync Online or not. The short answer at the moment is No. We understand all the customers requesting Lync Online (Office 365) support in Snom UC edition. The main challenge for Snom devices/development is a new additional login mechanism. To login to O365, Snom need to implement a new OrgID authentication method in their Lync firmware. By the way: in on-premise or Hosted-Edition deployments of Lync Server there is no such additional login using OrgID Authentication. Support for OrgID is on Snom’s roadmap, but an ETA is not available. We hope for the beginning of next year.
Personally, I expect that when we have O365 supported Snom firmware, clients will start requesting Lync On-Premise feature-set, that Snom as a device vendor wont be able to deliver(this may change). In other words OrgID support will be a resolution causing new “challenges”.
Please note: clients requesting phone support in O365 should carefully have a look on the O365 Plans (P1,P2,..,E1,E3,.. etc.) as only E4 support phone/pbx features/PSTN break out’s. E4 plan costs £17.75 per user per month. For the small organisation it’s reasonable but when you start adding more people to the system the cost increases to a level where it would be better to have an on-premises Lync device. Sangoma has recently introduced a Lync appliance that allows O365 integration along with a built-in VoIP gateway.
Find out more information on the Sangoma NetBorder Lync Express Gateway.
There are many ways you can build a dial plan on a snom phone.
The full range of features are documented on the snom wiki Dial Plan regex
As a quick example, here is how I can dial a local number in the area code 01484:
|^([2-9][0-9]{5})$|sip:014841@d
For many people, this may well be the only dial plan rule that they wish to use.
Get reading the documentation and see what you can do!
Post updated January 2022 to include new handsets
Recently we’ve been getting more and more enquiries as to which of our phones are wall mountable.
Wall mounting is perfect for corridors and communal areas such as kitchens and staff rooms. These are ideal to be used with SIP door entry phones, allowing you to answer the door even when you’re not sat at your desk.
I have put together a guide below outlining our range of wall mountable phones:
| Brand | Phones | Mounting details |
|---|---|---|
| Yealink | T18P, T19P, T21P, T20P, T22P and T32G | Direct to back of the phone |
| Yealink | T30P, T31P, T31G, T33P, T33G | Direct to back of the phone |
| Yealink | T27P and T29G | T29WM Wall mounting bracket required |
| Yealink | T40PN, T41P and T42G | T42WM Wall mounting bracket required |
| Yealink | T46G | T46WM Wall mounting bracket required |
| Yealink | T48G | T48WM Wall mounting bracket required |
| Snom | 300, 320, 360 and 370 | By using the phones stand |
| Snom | 821 and 870 | Wall mounting bracket required (Snom-800Wall) available in light grey and black |
| Snom | 710, 720, 760, D710, D712, D715, D725, D765 | Using Snom Wall Mounting Bracket for 700 Series Phones (00003820) |
| Aastra | 30i, 31i, 35i, 37i, 39i, 55i and 57i | Wall mounting bracket included |
| Cisco | 301G, 303G, 502G, 504G and 525G2 | Wall mounting bracket required (MB100) |
| Cisco | 7811 | Wall mounting bracket required (CP-7811-WMK) |
| Cisco | 7821 and 7841 | Wall mounting bracket required (CP-7800-WMK) |
| Cisco | 7861 | Wall mounting bracket required (CP-7861-WMK) |
| Cisco | 8811, 8841, 8851 and 8861 | Wall mounting bracket required (CP-8800-WMK) |
| Cisco | 8845 and 8865 | Wall mounting bracket required (CP-8800-VID-WMK) |
| Gigaset | Maxwell 3 and Basic | Wall mounting bracket required (S30853-H4032-R101) |
| Gigaset | Maxwell 10 | Wall mounting bracket required |
| Gigaset DECT | A510H, A540H, C300H, C430H, C610H, E49H, R410H, R630H, S510H, S650H and S810H | Direct to the back of the cradle |
| Gigaset | DE310 and DE410 | Wall mounting bracket included |
| Gigaset DECT | N300IP, N510IP | Direct to back of base station |
| Panasonic | KX-UT113 and KX-UT123 | Requires wall mounting kit (KX-A432-B) |
| Panasonic | KX-UT133 and KX-UT136 | Requires wall mounting kit (KX-A433-B) |
| Panasonic | KX-HDV130 | Requires wall mounting kit (KX-A440XB) |
| Panasonic | KX-HDV23 and KX-HDV330 | Using bracket provided |
| Panasonic | KX-TPA65 | Requires wall mounting kit KXA440XB |
| Polycom | SoundPoint IP 32x/33x and 430 phones | Using the reversible base stand/wallmount unit (included with phone) |
| Polycom | SoundPoint IP 450 | Requires wall mount kit (2200-11611-002) |
| Polycom | SoundPoint IP 550, 560, 650, and 670 | Requires wall mount kit (2200-12611-001) |
| Polycom | VVX 101, 201 | Reversible deskstand/wallmount (comes with phone as standard) |
| Polycom | VVX 300/310, 300/410, 500 and 600 | Requires wall mount kit (2200-44514-002) |
| Mitel | 6863, 6865,6867 and 6869 | Requires wall mount kit (80C00011AAA-A) |
| VTech | VSP715A, VSP725A and VSP735A | Direct to back of phone |
| VTech | VSP600A | Using bracket provided |
| VTech | VSP601A | Direct to the back of the cradle |
Phones that cannot be mounted to the wall: SL750H, DE700IP PRO, DE900IP PRO, DX800a, SL400H, SL610H PRO, T26P, T28P and the T38G.
There are several ways a snom phone can get Caller ID Name for an inbound call.
The first is from the Invite message of the inbound call from the sending SIP end-point. If a “Name” part of the Caller ID exists then this will be used by the Snom phone to display the name on the screen.
The phone can also get a name from it’s internal address book or an LDAP server if one is configured. However, it will only use this if there is no “Name” part of the Caller ID in the incoming Invite.
If you want to change this behaviour set this setting in the Snom phone’s web interface:
To “off”. Then an internal address book or LDAP server will take precedence.
More information here:
*****
UPDATE
This setting has no been superseded. From software version 8.7.3.19 use setting contact_source_priority
Information on snom Wiki:
UC = Unified Communications.
So the Snom300 and Snom821 UC editions are now `qualified for use with Microsoft Lync 2010`.
Snom have also launched the UC600. A USB phone which is `optimized for Microsoft Lync`.
For full details on the announcement, see the full UC release.
If you want to place an order, contact your account manager at ProVu.
The main USP of the Snom UC edition phones is that they are a phone for Lync but also a full open standards SIP phone. This gives a few options:
So buy the Snom UC edition to have a phone which is both a stand alone SIP phone and a UC phone for Lync. Protect your investment by buying open standards.
We’ve rehosted the old snom tools:
– screen viewer
– ringtone generator
– idle screen generator
Check out http://snom.provoip.co.uk/
ProVu are delighted to bring you the ‘snom summer sales special’, until the middle of August we are running a promotion on the snom 821 and snom 870.
The most popular handset in the 8 series range due to its versatility, price and feature set which recently qualified for Microsoft Office Communications Server 2007 R2.
**Buy 5 snom 821s and get one snom 821 free, all with snom OCS edition Firmware included!**
The latest model of the 8 series is the snom 870 with 5 way call conferencing, 12 different SIP identities, 12 freely programmable virtual keys and an advanced touchscreen display enabling 5-way conferencing via drag and drop.
**Buy 5 snom 870s and get one snom 870 for free!**
ProVu and snom are offering you the following snom summer sales special, valid until August 15, 2011.
To place your order for this amazing offer please contact a member of the ProVu Sales Team on 01484 840048.
I’ve been looking forward to the time when Asterisk catches up with the rest of the SIP world and starts working with encrypted SIP and encrypted RTP (SIPS & SRTP respectively). Asterisk has supported it since the recent release of version 1.8 so I had to get it working.
Asterisk only supports a fairly fixed set of encryption options so you’ve got to set the phone up just right for it to work. I’d also say that SIPS & SRTP is very much new functionality in Asterisk so I’d treat it as for testing purposes only right now….although it’s looking promising.
Snom phones have supported both SIPS & SRTP for years (in fact I think they were the first IP phones on the market to do so). So if any phone can get it right it should be them, perfect to test with.
I am using the following to test with:
I’m not going to go into the setup of Asterisk itself as there is plenty of information on this out on the Internet, not to mention quite a lot of different ways of doing it. I will just mention that I am using a self-signed SSL certificate, this means you either have to leave server verification turned off on the phone (which it is by default on this firmware version) or import your own CA into the phone. Neither of which are ideal for a real world deployment, you’d buy a server certificate from a recognised CA in that case but for testing….
OK so I will mention a couple of things in the Asterisk setup… all in sip.conf
There are more settings needed than this, please read the Asterisk documentation.
Everything is in identity 1, these are obviously examples only! You’ll need to put your own Registrar in etc…
Login tab:
SIP tab:
RTP tab:
That should be it. As mentioned the Snom phones do not verify the server certificates by default. If you want to turn this on then go to the “Certificates” page in the phone setup and click “Activate”. But bear in mind you must either use a certificate from a known CA or import your own certificate into each phone manually. Certificates must be in DER format for this.
To confirm it’s working, look for the little lock symbol on the phone screen during calls. It should look closed when the call is secure. For further confirmation you can do a pcap trace on the phone, open this up in Wireshark and then not be able to view the SIP packets or decode the audio to anything but white-noise.
Let me know if anyone thinks it’s worth me putting together a how-to with the full Asterisk config too.