 priller
join:2000-10-20 Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
1 edit | reply to DracoFelis Re: How multiple ATAs can be behind same NAT router?
A piece you're missing is that it's really PAT. When the translation is done, your return port number is also changed.
For example, leaving the ATA the UDP SIP packet connects to the host on 5060 and says talk back to me on 5060. Now when the xlate is done, the return port is changed. Here's the connection table for one of my ATA's ....
"UDP PAT from inside:zoom5801/5060 to outside:69.255.118.xxx/1061"
... so the VoIP provider is actually talking back to me on 1061. When the packet passes back through the PAT process, that gets changed back to 5060.
The combination of the IP address and the port number being changed is why you can have multiple ATA's registered to the same provider ... all on what you "think" is 5060. But the router is smarter than we are. 
The translation table should never get confused. If it does, get a new router.
FWIW, I've got 5 VoIP lines living well together. |
|
 artisticcheese
join:2004-11-09 Carrollton, TX | I thought UDP are packets are sent and received on the same port number so on router side it shall be receiving also on 5060? |
|
 priller
join:2000-10-20 Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
| said by artisticcheese :I thought UDP are packets are sent and received on the same port number so on router side it shall be receiving also on 5060? That's what you see on the "inside" of your network. But, the port is being changed before it leaves the WAN interface.
The combination of the IP address being translated, as well as the port, is what allows you to have multiple ATA's register to the same VoIP provider and not get confused. |
|
 priller
join:2000-10-20 Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
|  Packet on the inside |  Packet after PAT |
So, to demonstrate this in action. Here is a capture of the same session captured on both the inside interface and the outside interface. Note that port 5060 has been changed to 1061.
|
|