Settings/stun server
From Snom User Wiki
< Settings
- WEB USER INTERFACE
- V6: Identities - NAT(Section): STUN Server
- V7: Identities - NAT (Section): STUN Server
- V8: Identities - NAT (Section): STUN Server
- PHONE USER INTERFACE
- N/A
- FIRMWARE VERSIONS
- V6 V7 V8
- XML CONFIGURATION
- <stun_server idx="INDEX" perm="PERMISSIONFLAG">VALIDVALUE</stun_server>
- DESCRIPTION
- We reintroduced a STUN keep-alive mechanism for SIP, which can be turned on manually by specifying the address of the STUN server followed by the port number. However, we strongly discourage you from using it, because it can not work properly in symmetrical NAT environments (i.e., linux-based router/firewall). The only general SIP NAT solution is a session border controller (SBC) on the service provider’s side.
- VALIDVALUE
- e.g. <217.115.141.99:5062>
- DEFAULTVALUE
- blank
- FURTHER INFORMATION
Categories: Setting:V6 | Setting:V7 | Setting:V8 | Setting:snom3x0 | Setting:snom8xx | Setting:snom MP | Setting:snom PA1
Products > Firmware > Setting
Products > Firmware > Setting
Products > Firmware > Setting
Products > Firmware > Setting
Products > Firmware > Setting
Products > Firmware > Setting
Products > Firmware > Setting
Products > Firmware > V6 > Setting:V6
Products > Firmware > V7 > Setting:V7
Products > Firmware > V8 > Setting:V8
Products > IP phones > Snom3x0 > Setting:snom3x0
Products > IP phones > Snom8xx > Setting:snom8xx
Products > SIP conference phone > Snom MeetingPoint > Setting:snom MP
Products > SIP paging > Snom PA1 > Setting:snom PA1
