I have a RV042 with a DSL (WAN1) and cable (WAN2) internet connection in Load Balance Mode. The DSL provider also provides internet telephony when registered via his line. When I disable the WAN2 port, my IP phone successully registers with the registration server of the DSL provider. I also defined protocol bindings for SIP (port 5060) and RTP (ports 5004 to 5020) to be bound to WAN1. My IP phone is set up to listen on only these ports.
The rules are in detail:
SIP(UDP/5060~5060) -> "myPhoneIP"~"myPhoneIP" ("RegistrationServerP"~"RegistrationServerIP") WAN1 [Enabled]
SIP(UDP/5060~5060) -> "RegistrationServerIP"~"RegistrationServerIP" ("myPhoneIP"~"myPhoneIP") WAN1 [Enabled]
RTP(UDP/5004~5020) -> "myPhoneIP"~"myPhoneIP" ("RegistrationServerP"~"RegistrationServerIP") WAN1 [Enabled]
RTP(UDP/5004~5020) -> "RegistrationServerIP"~"RegistrationServerIP" ("myPhoneIP"~"myPhoneIP") WAN1 [Enabled]
With these protocol bindings in place when I re-enable WAN2, then after some time the phone reports "registration failed".
Do I need to set something else apart from protocol binding to force the VoIP traffic to go via WAN1?
Thanks for your help
Solved! Go to Solution.
I am still hoping for some help. My problem is still unsolved. If I did not make my problem clear enough, please ask for further information. Or, if there is some principle limitation that prevents binding VoIP traffic to one WAN port, please let me know so that I can take further steps (terminate phone service with DSL provider). Currently I cannot use my fast cable connection if I still want to be accessible by phone via my slow DSL connection.
Hi Felix, can you try to set the protocol bind specifying all services with source IP being what you're using, destination IP address 0.0.0.0 using the WAN 1?
Hi Thomas, thanks for responding. In addition to the rules I specified above, I added the following rules:
All Traffic [TCP&UDP/1~65535]->"myPhoneIP"~"myPhoneIP"(0.0.0.0~0.0.0.0)WAN1 [Enabled]
All Traffic [TCP&UDP/1~65535]->0.0.0.1~0.0.0.254("myPhoneIP"~"myPhoneIP")WAN1 [Enabled]
Result is again: Phone reports "Registration failed".
Anything else that I could try?
Pardon my memory if I am mistaken, when configuring the protocol bind for the WAN port, there are 4 or 5 options. Service, which of course is 1~65535, source IP, in this scenario it should be the phone or PBX, whatever you're using. The destination IP should be 0.0.0.0 and interface is your desired WAN, WAN 1 or 2.
Wan 1- Cable Wan 2 - Dsl
| ________________ |
| Computer 192.168.10.100
On this example to route the Telephone / PBX to WAN 1
All services 1~65535
Source IP 192.168.10.250
Destination IP 0.0.0.0
Interface WAN 1
Please correct me if I am mistaken, I'm currently not at work due to the US holiday
Thomas, I really appreciate you working on the US holiday.
To be specific here is my setup:
WAN1 - DSL WAN2 - Cable
Thanks for the picture. Delete all other rules except the all traffic that is hi-lited.
To clarify, if you use either WAN without a load balance, the phone/PBX are always working without issues?
To clarify: the phone is only working with WAN1 enabled and WAN2 disabled. With WAN2 enabled and WAN1 disabled, the phone reports "Registration failed". (with protocol binding adjusted to WAN2 when enabled).
Interestingly enough when WAN1 is enabled and WAN2 disabled but protocols are bound to WAN2 the phone successully registers. How can this be?!
In the event of a WAN failure, the protocol binding is going to fail over to the working WAN. The connection you're using on WAN 2 is the cable, has the phone ever registered successfully through that connection either using the cable as the only WAN?
When you connect a computer directly to the cable connection, what IP address do you receive?
These are the IP addresses I receive when both WANs are enabled. Does it make a difference whether the RV042 gets the IP or a "computer connected directly" to the cable modem?
A lot of ISP provide a modem/router device. It would be curious to see if your WAN 2 information is a NAT address if a computer connects directly to the device. What is the model # of that modem?
Sorry, I don't understand the NAT issue. I would assume there is no difference.
The cable modem is a Cisco EPC3208. It has been set up by the technician when he installed my cable connection. I don't have the admin password.
This seems to be a normal modem device. When using the WAN 2, does your internet work fine, only the phone register fails?
Is it possible to change the DNS server for WAN 2 primary to 18.104.22.168 and secondary to 22.214.171.124 ?
If the configuration is dynamic, there should be a check box to use different DNS servers. Let's give this a try to see if the phone does not care for the DNS configuration.
What is the firmware version on the router, also, can you reboot the router?
Firmware is v4.2.1.02 (Jan 18 2012 14:10:55)
I already checked for more recent firmware. My version seems to be the most current.
I will reboot the router and report the result here as soon as it is up again.
Thomas, are you still there?
I have to admit I changed the DNS settings back to "automatic" out of "aestetical reasons", and because I didn't understand why DNS plays a role (we are dealing with IP addresses, not domain names).
After "Registration failed" I switched back to 126.96.36.199/188.8.131.52 and rebooted. First again "Registered", then after some minutes "Registration failed".
It looks like if I solved my problem. The key hint was Thomas' remark that in the event of WAN failure, protocol bindings fail over to the working WAN. In my setup I had Network Service Detection enabled with Default Gateway selected as the target for the ping attempts. What I was observing in the System Log were strange messages of "NSD FAIL WAN". I did not understand these because WAN1 was working fine. Now I had the idea to try to ping the Default Gateway of WAN1 manually in a command prompt window and obtained "Request timed out". I guess this machine simply drops ICMP packets but works OK as a gateway since I do not experience any problems using WAN1 for internet access.
Now I disabled Network Service Detection and since then my IP-Phone keeps being registered via WAN1 with my DSL provider.