Grandstream HT503 User Manual - Manual (Page 36)

FIRMWARE VERSION 1.0.14.1 HT503 USER MANUAL Page 34 of 64
Range: 0 - 3600
NAT UDP Timeout NAT TCP idle timeout in seconds. Connection will be closed after preconfigured,
timeout if not refreshed.
Range: 0 – 3600, default is 300
Uplink Bandwidth The maximum uplink bandwidth permitted by the device. This function is disabled by
default. The total bandwidth can be set as: 128K, 256K, 512K, 1M, 2M, 3M, 4M, 5M,
10M or 15M. The primary function of this setting is to limit the uplink bandwidth for the
device internal system, signaling and NATed traffic. Example: if 512k is configured,
there will be at least 512kbps limited for internal system, signaling and NATed traffic.
Voice or RTP stream will never be limited. See figure 3.
Downlink Bandwidth The maximum downlink bandwidth permitted by the device. This function is disabled
by default. The total bandwidth can be set as: 128K, 256K, 512K, 1M, 2M, 3M, 4M, 5M,
10M or 15M. The primary function of this setting is to limit the download bandwidth for
the device internal system, signaling and NATed traffic. Example: if 128 is configured,
there will be at least 128kbps limited for internal system, signaling and NATed traffic.
Voice or RTP stream will never be limited. See figure 3.
Enable UPnP When set to “Yes”, the HT503 acts as an UPnP gateway for your UPnP enabled
applications. UPnP = “Universal Plug and Play”
Reply to ICMP on WAN
Port
When set to “Yes”, the HT503 responds to the PING command from other computers,
but is also made vulnerable to DOS attacks. Default is No.
WAN Side HTTP/Telnet
Access
When set to “Yes”, the user can access the web configuration pages through the WAN
port, instead of through the PC port. Warning: this configuration is less secure than the
default option. Default is No.
White list for WAN side List the IP address or IP range in the White list
Note for list Rules:
HTTP/telnet:
Case 1: WAN side telnet/HTTP access enabled
- If white list exists, then ONLY these IP addresses are ALLOWED to web and telnet
access.
- If black list exists and white list is empty, then ONLY these IP addresses are NOT
ALLOWED to web and telnet access.
Case 2: WAN side telnet/HTTP access is not allowed:
-All addresses are NOT ALLOWED http and telnet access.
SIP/RTP:
- If both white list and black list are empty, the behavior is same as before.
- If white list exists, then ONLY these IP addresses are ALLOWED SIP/RTP access.