Yealink MeetingEye 600 Administrator's Manual page 56

STUN is a client/server protocol, which allows the system behind a NAT to discover the NAT presence
firstly, and the mapped public IP address, and then the port number that the NAT has allocated for the UDP
flows to remote parties. Those information is used to establish UDP communication between two system
behind the NATs.
STUN is a client/server protocol. The system works as a STUN client, sending exploratory STUN
messages to the STUN server. After that, the STUN server uses those messages to determine the public
IP address and the port (which is used to connect the public network to the intranet), and then informs the
client. For more information, refer to RFC3489.
Capturing packets after you enable the STUN feature, you can find that the VCS sends Binding Request
to the STUN server, and then the mapped IP address and the port are placed in the Binding Response:
Binding Success Response MAPPED-ADDRESS: 59.61.92.59:19232
The system will send SIP message using the mapped IP address and the port.
Note:
STUN does not enable the incoming TCP connections through NAT, so H.323 is not supported. And
STUN does not support the incoming UDP packets through symmetric NAT.
Configuring STUN
•
Enabling STUN Feature for SIP Protocol
•
Configuring STUN
Procedure
1. Do one of the following:
• On your web user interface, go to Network > NAT/Firewall > STUN Config.
• On your VCS:
For MeetingEye 600/MeetingEye 400, go to More > Setting > Network > Wired Network > NAT/
Firewall > STUN Config.
For VC880/VC800/VC500/PVT980/PVT950, go to More > Setting > Advanced > NAT/Firewall >
STUN Config.
For VC200, go to More > Network > Wired Network > NAT/Firewall > STUN Config.
For VP59, tap Setting > Advanced > NAT/Firewall > STUN Config.
•
On your CTP20, tap
2. Configure and save the following settings:
> Setting > Network > Host Network > NAT/Firewall > STUN Config.
| Traditional Deployment Methods | 56