...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The following describes how to setup a Vega gateway for use in a NAT'ed environment through internally configured port translation using both a router and the Vega.
...
Although NAT/PAT routers translate the Return IP address and port and route the packets appropriately, unfortunately both SIP and H.323 protocols send IP addresses and port numbers within the protocol, to for example, tell the far end where to send the media and signalling information. Standard NAT/PAT routers, those that are not VoIP aware, can only modify the VoIP header and so pass these values through without change. When the far end device tries to send, for example, some media packets it will try to send them to the private IP address that will not be known, and will not be route-able within the Public Internet.
Possible Soution - VoIP aware NAT/PAT routers / firewalls solve the NAT problem
...
In this way, additional entries can be configured
NOTE The configuration changes made here will need to the submit button selected - please follow the onscreen prompts
...
Note This address will be specified in the SDP sent by the Vega to the Public IP based ITSP
NOTE The configuration changes made here will need to the submit button selected - please follow the onscreen prompts
...
The default NAT Port entry list will use all NAT Port Entries configured. Below are examples of the NAT Port Entry configuration based on the example information above:
NOTE The configuration changes made here will need to the submit button selected - please follow the onscreen prompts
...
NOTE The save process creates a select "Continue" on this window.
Checking the configuration
...