Bro wrote:Ignite WiFi Gateway (Gen 1) modem
Okay, by the way, there is no Grandstream HT-710 ATA. There's an HT-701.
a) If a specific number is blocked by the phone system or handset being used (Rogers side of the call), refer to the phone manual to unblock it.
b) Using the Rogers-side FPL account, login at https://www.freephoneline.ca/doGetCallLogs. Get the call logs for the calls that failed. Is there a "Disconnect Reason" listed? What is it?
c) On the Rogers-side, what is the Primary SIP server being used in the ATA when the problem occurs? Login into the ATA's WebUI. Navigate to FXS Port tab used for FPL. What's listed for Primary SIP server?If this person isn't using a separate router, then do the following (all on Rogers' side):
1.
Arris XB6 from Rogers (that should be Gen1 Ignite gateway)
Open a web browser, and login at 10.0.0.1
Navigate to Advanced-->Options.
Uncheck the SIP box.
Click "Apply".
To understand why SIP ALG often causes horrible problems, please visit
https://www.voip-info.org/routers-sip-alg/ (scroll down to the section on SIP ALG problems).
Also, SIP ALG is potential security risk:
viewtopic.php?f=10&t=20602.
2. a) Dial ***
b) Then dial 02
c) Enter the IP address you hear into a web browser.
d) Login to the Rogers-side ATA.
Default login password is admin.
3. The latest firmware version is 1.0.10.3. I don't accept responsibility for failed firmware updates.
Firmware download is located here:
https://firmware.grandstream.com/Releas ... 0.10.3.zip.
Release notes are here:
https://firmware.grandstream.com/Releas ... 0.10.3.pdf.
Ensure the ATA is using the latest firmware version.
4. For HT-701/2, navigate to the FXS Port used for FPL.
a) Enter "voip4.freephoneline.ca:6060" without the quotation marks for Primary SIP Server.
Using voip4.freephoneline.ca:6060 helps to circumvent SIP ALG in routers. I want to do this even if you disable SIP ALG in the XB6.
b) “NAT-Traversal” should be set to “Keep-Alive”
c) Enable SIP OPTIONS/NOTIFY Keep Alive
Select “Notify”
d) Set SIP OPTIONS/NOTIFY Keep Alive Interval to 20 seconds.
e) i) Set “Use Random SIP Port” to “Yes”.
ii) Set “Random RTP Port” to “Yes”.
Helps with security and also helps to refresh NAT associations when the ATA is rebooted
f)
Set “SIP REGISTER Contact Header Uses” to “WAN address”This helps to ensure data is sent back to the public IP address as opposed to
the LAN IP address (192.100.1.x, for example). If Freephoneline were to send data to 192.100.1.x, it would never reach the ATA. It needs to be sent to your WAN or public IP address first before your router can send or route the data to the local IP address of the Grandstream ATA.
5. Update/Apply ATA settings if changes were made. Turn off Rogers gateway and ATA. Turn on Rogers gateway. Wait for it to be fully up and running first (transmitting data with Wi-Fi SSIDs broadcasting). Turn on ATA after everything else is up and running. That's always the proper device boot order. Your ATA should always be booted last in the device chain. 1. Modem (wait) -->2. Router (wait)-->3. ATA
6. Login at
https://www.freephoneline.ca/showSipSettings.
SIP Status needs to indicate "Connected", and SIP User Agent should reflect the ATA being used.
7. Login to the ATA's WebUI. Ensure the Rogers-side FPL account is registered with the ATA.
Navigate to Status–>Port Status–>FXS–>Registration (also ensure DND shows “No”) to check registrations status in the ATA.
8. Test incoming calls again from Bell-side FPL number. If the calls works, you can stop here.
a) If the incoming call still doesn't work, log back into the Rogers-side ATA's WebUI.
b) Navigate to FXS Port tab used for Freephoneline
c) Try disabling "Allow Incoming SIP Messages from SIP Proxy Only". Change that to "No".
Years ago, with Obihai ATAs, I couldn't get Fongo Mobile to FPL calls to work when "X_AcceptSipFromRegistrarOnly" was enabled and while registered on anything other than voip.freephoneline.ca.
"Allow Incoming SIP Messages from SIP Proxy Only" is basically the same setting in Grandstream ATAs. I just want to see whether disabling that setting matters for FPL to FPL calling.
If disabling "Allow Incoming SIP Messages from SIP Proxy Only" doesn't help, then re-enable it (set to "Yes") to help prevent SIP Scanners, after testing.
d) Update/Apply ATA settings. Reboot or power cycle (turn off/turn on) ATA.
e) Test with an incoming call again. Again, if disabling "Allow Incoming SIP Messages from SIP Proxy Only" doesn't help, then re-enable it (set to "Yes") to help prevent SIP Scanners, after testing.
9. I don't recommend doing this step for very long because the ATA will be unprotected while testing. If the incoming Bell-side FPL call is still not reaching the Rogers-side ATA but is reaching FPL’s voicemail system, attach the ATA directly to the ISP's (gateway or hub in bridge mode) modem via ethernet cable.
Here's how to enable bridge mode:
https://www.rogers.com/support/internet ... your-modem. Then you would disconnect everything and attach the ATA directly to the Rogers gateway.
Test briefly for incoming call from Bell-side FPL number. If the incoming call suddenly starts working properly, you've narrowed down the problem to something involving the router portion in the Rogers gateway/XB6. Keep in mind the Grandstream ATA will not be protected by the XB6's firewall while the XB6 is in bridge mode. After testing, revert back; that is, disable bridge mode, and put everything back to the way it was.
10. If the incoming call still failed while the XB6 was in bridge mode, try making a call using Fongo Mobile to the Rogers-side FPL number. Try while connected to cellular data (cellular data charges may apply) and then again while Fongo Mobile is [this step is Bell-side] connected to your Bell-side Wi-Fi network. If the problem only occurs while connected to Bell Wi-Fi, then the problem is somewhere on the Bell-side LAN, and we can try changing some settings in your ATA as well, in that case, but it doesn't make a lot of sense that you would have to. Hopefully, you won't need to bother with this step. Fongo Mobile is free to use, but you have to provide the cellular data for the smartphone.
https://www.fongo.com/services/fongo-mobile/. Basically, I want to know if you can reproduce this issue when calling from Fongo Mobile when it's connected to Bell-side Wi-Fi.