L2TP Client: SNOM: Difference between revisions
Appearance
	
	
Content deleted Content added
|  Created page with "__NOTOC__<indicator name="L2TP">link=:Category:L2TP|30px|Back up to the L2TP Category</indicator> Category:Incoming L2TP  == Example config files: =..." | mNo edit summary | ||
| Line 1: | Line 1: | ||
| __NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:L2TP|30px|Back up to the L2TP Category]]</indicator> | __NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:L2TP|30px|Back up to the L2TP Category]]</indicator> | ||
| [[Category:Incoming L2TP]] | [[Category:Incoming L2TP]] | ||
| * 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: == | == Example config files: == | ||
Revision as of 15:15, 12 November 2021
- 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:
xl2tpd.conf
[lac l2tp_connection]
lns = 90.155.53.19
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
