Filter
Top Products
17
some settings do not need an adjustment on the NAT server, such as the SMC barricade
The master must have a public IP address
Only one slave device with a private IP address may be installed on each NAT domain. This
means that cascading to increase the density of channels by using private IP addresses is not
supported
Some In-bound/Out-bound address translation rules may time out on a NAT server. In this
instance, users may need to restart the voice gateway.
Management Interfaces under NAT
Since the device works with private IP addresses, users cannot access the management interfaces (Web or
Telnet) from the Internet if they do not specify the redirection settings on the NAT server. Even if you are
able to specify redirection rules to redirect these (Web or Telnet) requests to the voice gateway, some of the
well known ports (such as TCP port 80 for Web, TCP port 23 for Telnet and TCP port 21 for FTP) will already
be occupied by public servers that are using private IP addresses. In this instance , you will need to change
the port numbers to gain access to the voice gateway as well as to maintain public access to internal
servers. You will then need to change the service port numbers for Web and Telnet on the voice gateway.
The commands are as follows (you can only use Telnet or Console to modify the service port information):
1. Show the current service port information
PBX Gateway>enable
PBX Gateway#show service_port
FTP Service Port: 21
Telnet Service Port: 23
Web Service Port: 80
PBX Gateway#
2. Modify the service port
PBX Gateway#config
Enter configuration commands, one per line. End with CTRL/Z
PBX Gateway(config)#service port
PBX Gateway(config)#service_port ?
ftp Set ftp service port number
telnet Set telnet service port number
web Set web service port number
PBX Gateway(config)#service_port web <new port number i.e.88>