Howto:VOIP through NAT routers

Abstract

This page discusses NAT traversal of VOIP.

Introduction

VOIP signaling involves the exchange of IP addresses. Signaling addresses and media addresses RTP or T.38).

If the signaling crosses network borders you may get in trouble with private IP addresses. If a private signaling endpoint hands-out a private IP address (signaling or media) the external endpoint won't be able to reach that IP address.

What WILL work

The only leliable way to get the hole thing working is to handle the problem on the private network.
Keep your private signaling endpoint from hand-out private IP addresses.

What you need

You need a Fullcone NAT router and a STUN server in the public network.

How to configure

Configure the public STUN server on your private signaling endpoint. It will use STUN to create a NAT mapping on the fullcone NAT router. It will then hand-out the mapped IP addresses (signaling and media) instead of the private ones.

What MAY work

It MAY work even if the private signaling endpoint does not care about giving private IP addresses to the external endpoint, but only if the external endpoint is clever enough to do a workaround called "".

What you need

You need a NAT router that at least do symmetric NAT.

How to configure

Nothing to do on the private equipment. The private signaling endpoint will hand-out private IP addresses.
The external endpoint will detect and ignore all private IP addresses/ports and will reply to that IP address/port where it receives from (signaling and media).