Reference12r2:IP4/General/STUN: Difference between revisions
m (→TURN Servers) |
|||
Line 20: | Line 20: | ||
==TURN Password== | ==TURN Password== | ||
The password for communication with the TURN server. | The password for communication with the TURN server. | ||
== Known Issues == | |||
Note: In v12r1 and higher version it's no longer necessary to enable NAT for the STUN/TURN services be enabled. If NAT it's disable make sure the UDP-NAT port range values are also deleted / not set. |
Revision as of 10:52, 19 April 2017
STUN Servers
The default STUN servers that should be used on a box by ICE and SIP, if no configuration is given at the individual registrations. The field must contain a string in the following format:
- up to two STUN servers which shall be queried in parallel, separated by semi-colon (
;
)
Each STUN server is denoted as
- either a single DNS name and an optional port (e.g.
stun.example.com:1234
) - or a comma separated list of one or two IP addresses and optional ports (e.g.
172.16.13.1:1234,172.16.13.2
)
<br\> This format is also used for the STUN server configuration in the DHCP innovaphone Vendor Option 219 .
TURN Servers
You can configure up to one TURN server in one of the following formats.
- either a single DNS name and an optional port (e.g.
turn.example.com:1234
) - or a comma separated list of one or two IP addresses and optional ports (e.g.
172.16.13.1:1234,172.16.13.2
)
A TURN server configuration can optionally be followed by a protocol specification such as e.g. turn.company.tld?protocol=
prot where prot can be either tcp
or udp
.
TURN Username
The user name for communication with the TURN server.
TURN Password
The password for communication with the TURN server.
Known Issues
Note: In v12r1 and higher version it's no longer necessary to enable NAT for the STUN/TURN services be enabled. If NAT it's disable make sure the UDP-NAT port range values are also deleted / not set.