WAN Mode
The WAN mode page allows you to configure how your router should use your external Internet connections, for example your WAN1 and WAN2 port connections.
NAT is a technique which allows several computers on a LAN to share an Internet connection. The computers on the LAN use a "private" IP address range while the WAN port on the router is configured with a single "public" IP address.
Along with connection sharing, NAT also hides internal IP addresses from the computers on the Internet.
NAT (Network Address Translation)
Select NAT if your ISP has assigned only one IP address to you. The computers that connect through the router will need to be assigned IP addresses from a private subnet (example: 192.168.1.0). If your ISP has assigned an IP address for each of the computers that you use, select Classic Routing.
Note: The router will delete all inbound firewall rules when switching between NAT and Classic Routing.
Load Balancing Settings
These options allow you to configure the router to balance internet traffic across all of the configured WAN ports, or to use a redundant ISP link for backup purposes.
Select Load Balancing mode to distribute your internet load among configured ISP's simultaneously. The active WAN interfaces (at least 2) will carry data for the protocols that are bound to them. Protocol bindings can be specified in the Protocol Bindings menu. For example, if the HTTP protocol is bound to WAN1 and FTP protocol is bound to WAN3, then the router will automatically channel FTP data from and to the computers on the LAN through the WAN3 port. All HTTP traffic will be routed through the WAN1 port. This feature can be used to segregate traffic between links that are not of the same speed. High volume traffic can be routed through a port connected to a high speed link and low volume traffic can be routed through a different port connected to the slow link. When the router is configured in Load Balancing Mode, it checks the connection of both the links at regular intervals to detect its status. If WAN is configured for Idle Timeout, then Load Balancing Mode is not applicable.
This device supports Weighted Load Balancing (LB), where balance weights are calculated based on WAN link speed and available WAN bandwidth. This is the default and most efficient balancing algorithm. With Round-robin load balancing, new traffic connections are sent over a WAN link in a serial method irrespective of bandwidth or link speed. For example if WAN1, WAN2, and WAN3 are active in round-robin load balancing, a HTTP request will first be sent over WAN1, and then a new FTP session will start on WAN2, and then any new connection to the internet will be made on WAN3. This method ensure that any one WAN will not have a disproportionate distribution of sessions over that single link.
Primary WAN mode should be used when load balancing is not required, and all internet traffic should be sent over the selected primary WAN (choose between WAN1 to WAN4). Enable Auto Rollover to use a single WAN for all internet connectivity until a failure on that link is detected. Once a failure on the primary WAN link is detected, all active connections to the internet will be rolled over to the selected secondary WAN port.
Note: If Auto Rollover mode is selected, you must configure the primary WAN port's Failure Detection Method, located in the WAN Advanced Options page.
Note: IPsec VPN policies will be rolled over in both Load balancing and failover mode.
If you have a commercial router or one that allows direct binding of public IP to internal asterisk server, then you do not need port forward. All default SIP, IAX, RTP ports can be used for the asterisk.
However, if you can use only NAT mode, then multiple asterisk servers can only be accessible by having different SIP, IAX, RTP ports for each server. Adjustment of the settings are required to ensure the servers are accessible and functional.
Last time I had problem in connecting with my Intel ATOM-based Asterisk server. I do not know whether the problem came from the setting for type, which I mistyped as typp. I will check it on Monday morning to see any improvement if I changed it to type.
Not your fault. Sometimes, we also mix up the wan mode and number of IPs we have.
BTW, did you implement cdr-stats in your system? I saw the information in your website