L2TP Client: SNOM

NOT RECOMMENDED AT THIS TIME

• Some SNOM phones support adding an L2TP firmware patch that gives the phone the ability to connect to a L2TP server.
• This can help bypass firewalls and NAT/CGNAT which can cause problems with VoIP.
• The config files need to be put in a .tar file hosted on a webserver for the SNOM to fetch.
• Further details are on the SNOM website: https://service.snom.com/display/wiki/Install+and+configure+L2TP+on+Snom+Deskphones

Example config files:

Below is config to connect to our L2TP service.

• We do not recommend using our normal L2TP service on a SNOM due to the risks involved in having a SNOM on the internet in this way.
• Be aware though that this will mean the SNOM is on a public IP address and open to the internet and not behind a firewall. A hacker could gain access to the SNOM by guessing your password and could then run up your telephone bill, or worse.
• If you decide to use this as an option, be sure to have very secure http/admin username/passwords on your phone.
• At some point A&A may offer a service that allows the SNOM to connect to a protected, private, network which only has access to the VoIP servers.
• You may adapt the config to connect to your own L2TP server, eg if you have your own FireBrick.

xl2tpd.conf

[lac l2tp_connection]
lns = <L2TP SERVER IP ADDRESS>
ppp debug = yes
pppoptfile = /l2tp/options.xl2tpd
length bit = yes
redial = yes
redial timeout = 30
max redials = 1440

options.xl2tpd

refuse-eap
require-chap
noccp
noauth
mtu 1280
mru 1280
noipdefault
nodefaultroute
usepeerdns
connect-delay 5000
name <USERNAME@a.X>
password <PASSWORD>