Template:SIP Profile Test NAT b: Difference between revisions
Jump to navigation
Jump to search
(New page: The provider cannot handle calls to clients behind NAT. Clients are requires to use NAT-traversal methods like STUN. Drawback of this solution is that STUN doesn't work for all NAT routers...) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
The provider cannot handle calls to clients behind NAT. Clients are | The provider cannot handle calls to clients behind NAT. Clients are required to use NAT-traversal methods like STUN. Drawback of this solution is that STUN doesn't work for all NAT routers (i.e. routers doing symmetric NAT). Because of this limitation, it depends on the customer network equipment whether the SIP-trunk is usable or not. However MediaRelay is required, since the provider does not support a change of the remote RTP-endpoint during a call. | ||
Latest revision as of 18:46, 1 August 2017
The provider cannot handle calls to clients behind NAT. Clients are required to use NAT-traversal methods like STUN. Drawback of this solution is that STUN doesn't work for all NAT routers (i.e. routers doing symmetric NAT). Because of this limitation, it depends on the customer network equipment whether the SIP-trunk is usable or not. However MediaRelay is required, since the provider does not support a change of the remote RTP-endpoint during a call.