NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 with 1 RBS50s - Wifi Calling Drops Constantly - on latest firmware V2.7.2.102
Hi All, I've been working on this issue for 2+ months and have made all the rounds - to Apple, to Verizon, and read through all the forums here for similar issues. It seems no matter what I try,...
UPDATE - xfinity modem replaced, connectors on my line snipped and reconnected, and wifi calling seems to be working. 20 minute call is just completed and still running. I believe that was ultimately the issue.
So, after investigating with Netgear equipment, Apple phones, my network, various settings, etc... it came down to the cable / internet provider. I don't know that I'll ever know what caused it, but happy it appears to be fixed! Hopefully, this helps someone else.
Thanks for the response - please see below:
- The ISP Modem is a xfinity XB6-A
- Home size is 2,000 square ft. plus or minus (with 1 router and 2 satellites I have very strong signal throughout the house)
- Distance router to satellite is 15 ft. (but going through a couple of walls) on one and 25 ft. (going through a door) for the other. This has been the configuration for 2 years or so with no issues until the last 2.5 months.
- 2.4Ghz was Auto, changed setting to manual channel 1
- Wifi Neighbors - just one shows up and only 2 bars (ATT)
- Beamforming and MIMO were already enabled from prior post suggestions - left those on
- Factory reset and setup - done just before I updated to the latest firmware today.
- Per the other post you included a link to I have now given both satellites static IP addresses as well.
- All other configurations are as you suggested.
RESULT: wifi calling is still dropping after 2-3 minutes on average, this continues to happen if I am on wifi only (airplane mode with VZW Wi-Fi on the iPhone), or have the cellular on (my at home cell service is terrible, hence the need for wifi calling - definitely is harming my work at this point...)
What mode is your modem working in? Router or modem only. Thats a modem with built in wifi and router I believe. This would be a double NAT (two router) condition which isn't recommended. https://kb.netgear.com/30186/What-is-Double-NAT
https://kb.netgear.com/30187/How-to-fix-issues-with-Double-NAT
Couple of options,
1. Configure the modem for transparent bridge or modem only mode. Then use the Orbi router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, configure AP mode on the Orbi router. https://kb.netgear.com/31218/How-do-I-configure-my-Orbi-router-to-act-as-an-access-point and https://www.youtube.com/watch?v=H7LOcJ8GdDo&app=desktop
The 1 RBS thats 15 feet from the RBR is too close. 30 feet is needed. 2000sq ft maybe too small an area for two RBS. Try turning OFF 1 of the RBS.
Thanks again, please see below:
- Xfinity XB6 was already set to bridge mode - just confirmed that
- Wi-Fi disabled on Xfinity XB6
- Orbi is in router mode
- That's interesting, I didn't realize too close was an issue. What would be strange is that it worked like this for a couple of years with nothing changing and then stopped, but stranger things have happened. I moved both satellites farther away from the router - now one is about 35 feet and the other is about 30 (we have the space). The irony would be that I thought I should be moving closer if anything!
RESULT: Just hit 10 minutes on a wifi only test call for the first time in a long time. I'm hopeful that this could be the fix I have been looking for! I'll update here after running some additional tests over the next day or so. If this is the fix, it would be helpful for others pulling their hair out to know that this particular sub-optimal physical configuration of less than 30 feet causes this specific wifi-calling drop issue (maybe these keywords help) - would have saved me about 12 hours of my life :)