Browse Tag

Snom

Snom phones support for Office365 (Lync Online)

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.

Local area code on a snom desk phone

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!

Wall mountable phones

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.

snom phones – which caller ID to use on inbound calls

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:

  • Advanced => Behaviour => Prioritise PBX Number Lookup

To “off”. Then an internal address book or LDAP server will take precedence.

More information here:

Snom Wiki

*****
UPDATE

This setting has no been superseded. From software version 8.7.3.19 use setting contact_source_priority

Information on snom Wiki:

http://wiki.snom.com/Settings/contact_source_priority

Snom UC edition

Lync LogoUC = Unified Communications.

So the Snom300 and Snom821 UC editions are now `qualified for use with Microsoft Lync 2010`.

snom UC600Snom 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:

  • Deploy SIP now, and upgrade to UC with Lync in the future

  • Use SIP for voice, but use Snom UC for presence. This shadow system is a very good way to migrate.

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.

Snom Summer Special – Buy 5 Get 1 FREE!

snomProVu 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.

snom 821

snom 821

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!**

snom 870

snom 870

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.

Snom phones using SIPS/SRTP encryption with Asterisk 1.8

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:

  • Current Debian Asterisk 1.8 packages maintained by Digium on Debian Squeeze (deb http://packages.asterisk.org/deb squeeze main)

  • My actual Asterisk version at the time of writing is “1.8.4.1-1digium1~squeeze”. Some older ones didn’t work.

  • Snom 300 with 8.4.31 firmware. It will not work with much older versions.

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….

The important bits in Asterisk

OK so I will mention a couple of things in the Asterisk setup… all in sip.conf

  • tlsenable=yes : in general section

  • domain=ast18.provu.co.uk:5061 : this is needed for it to work

  • transport=tls : used in the general section or in each sip peer/friend to turn on tls for SIPS

  • port=5061 : in general or each sip peer/friend. 5061 is the usual port for SIPS

  • encryption=yes : turns on SRTP, if you have set this then the SIP device(s) MUST use it, it’s either on or off, not optional

There are more settings needed than this, please read the Asterisk documentation.

Snom phone setup

Everything is in identity 1, these are obviously examples only! You’ll need to put your own Registrar in etc…

Login tab:

  • Account: sip username

  • Password: sip password/secret

  • Registrar: ast18.provu.co.uk

  • Outbound Proxy: sips:ast18.provu.co.uk:5061

  • Authentication Username: sip username

SIP tab:

  • Support Broken Registrar: on

RTP tab:

  • RTP Encryption: on (should be default…)

  • SRTP Auth-tag: AES-80

  • RTP/SAVP: mandatory

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.

End of an Era – last Snom360

Today ProVu shipped the last black Snom 360.

<%ThickBox(http://www.provu.co.uk/products/snom/PVSnom360/PVSnom360-medium.jpg|)%>

We first shipped this product in March 2005, giving a product life of 6 years.

Snom360 was probably the first really good VoIP phone, with a decent DSP and handset to match. It has lived through 6 major versions of Snom firmware.

The product has been on notice of withdrawal for around a year. It has still sold strongly, but we have finally run out. The range is a little crowded with snom320 just below and snom370 just above.

If you do still want a Snom360, we have 5 white units still in stock – first come first served.

For alternatives, then buy a Snom320 or a Snom370

SnomONE and Voipfone

I’ve just diagnosed an issue a customer had getting a Voipfone SIP trunk Registered on a SnomONE PBX.

The trick to getting this to work is:

    • Turn on long SIP headers. Go to the admin, general settings page and set “Use Short SIP Headers” to “long”

 

    • If you are using IP access control then you need to enable the IP range 195.189.172.1 – 195.189.173.254 to ensure Voipfone will work

 

SnomOne more info