Forum Fongo Community Forums

To see whether the issue is related to double NAT, you can connect the ATA directly to the Bell Hub while SIP ALG is disabled in it. No matter what, keep SIP ALG off in the Bell Hub (probably under Advanced Tools and Settings). ... ... For this one... I'm on Bell Fibe. I have gigabit Fibe and have been stable on it for a decade or more... BUT I don't use the Bell HomeHub. That best serves as a boat anchor... In my case the Homehub has sat in a closet for the last decade dust. My Bell ONT goes directly into a "GTek Ethernet Media Converter", which then goes into the WAN port on the Unify USG3. From there the USG router goes to an array of Unifi switches and access points. And so yes, the Unifi USG router uses pppoe and manages the Bell connection directly. My LAN has been setup like this for years, and has been very stable with 1Gbps speeds. I run Unifi Network Application in a local docker container running on 24/7 server on my network. I don't see "SIP ALG" config settings anywhere in my router config. There doesn't appear to be any kind of SIP specific config in my router UI.

Steps 8 through 10 below, I feel, are probably the most important to check first, but I don't want to rewrite everything. If the ATA isn't even sending the call properly, as can be determined in step 10 by checking "Last Called Number" in the ATA, then the PPPoE passthrough instructions don't matter. Similarly, SIP ALG, bridge mode (double NAT issue), and DMZ wouldn't matter either. Try a different phone, and don't use pulse dialing. If the number you dial is not being sent by ATA or rejecting it, the problem isn't with Freephoneline. Instead, the problem is far more likely to be with the phone (potentially defective button, stuck on pulse dialing, inserting extra digits or a prefix that you don't expect, etc.), the phone not being plugged into the right phone port on the back of the ATA, or the ATA's dial plan. Consequently, it's important to be checking "Last Called Number" in the ATA, and I would do that as a first step. I would also be inclined to test with another phone. Hi @Liptonbrisk, thanks so much for the detailed and quick reply!! Really appreciate your expertise here and lots for me to check! I'll try to check and reply as I cross things off the list you've created. I did check the ATA "Last Called Number" and it is blank. Nothing there. I tried 2 different phones in my house and they both get an instant fast busy signal as soon as I enter the 10th digit on the phone. I'm trying to call my cell from FPL landlines in my house. I'm on Line 1 and it shows connected.

Lastly, instead of steps 5 to 7 (make sure you reach step 4 first to determine whether the issue is with USG3) from the previous post, you're probably better suited to just performing PPPoE login using your SPA112, as a quick test. You would need to login to your ATA and navigate to Network Setup-->Basic Setup-->Internet Settings-->Internet Connection type (PPPoE). You'll need your username and password credentials from your ISP. Test an outbound call. If that works (because the problem persisted when removing the USG3), then the problem is with the Bell Hub. The issue with using PPPoE passthrough in the SPA112 is that the SPA112 is not going to be protected by the Bell Hub or the USG3. Why is that a problem? Visit https://www.theregister.com/security/20 ... hem/440471 . So, ultimately, I would try to get outbound calls working without using PPPoE connectivity directly through the SPA112. What I'm suggesting to try in this post is for brief testing purposes only.

To see whether the issue is related to double NAT, you can connect the ATA directly to the Bell Hub while SIP ALG is disabled in it. No matter what, keep SIP ALG off in the Bell Hub (probably under Advanced Tools and Settings). 1. For example, i) Open your web browser, and login at 192.168.2.1 with your Bell Hub's administration password. Check your Hub's manual (or contact Bell for the IP). ii) Navigate to "Advanced tools & settings"-->"Networking" iii) Disable "SIP ALG". (save/apply settings) 2. Connect ATA's ethernet cable to a LAN port on Bell Hub. 3. Connect phone to the Phone port that's registered on the SPA112. 4. Test an outbound call. Works? Then the problem is related to your USG3. Stop here and refer to the previous post. Doesn't work? I'm reluctant to suggest trying DMZ. But you could try it as a quick test to see if Bell Hub's firewall is causing issues. 5. Login at to 192.168.2.1. Navigate to Advanced Tools and Settings --> DMZ. 6. Select the ATA from the device list. Its MAC address should be on the label underneath the unit. 7. Save. Leave "Advanced DMZ" unchecked. That option is what hands a public IP to a router for the full bridge-style setup, which you don't need for this test. Also, some user reports suggest Advanced DMZ is buggy. Reboot the ATA, wait for the registration, and test an outbound call. Works? Problem is Bell Hub's firewall. You would need to use PPPoE passthrough in USG3 or bypass the Bell Hub. Afterwards, make sure you disable DMZ in the B

Hello, I'm almost positive this started around the time I signed up for Fongo Mobile. Does anyone know if this is a known issue? No. Fongo Mobile and Freephoneline use separate accounts, regardless of whether email addresses are the same. I have tried outbound calls on 3 FPL accounts today, and they're all working normally. So are the Fongo Mobile accounts I tested on the same LAN. However, if Fongo Mobile also isn't working while it's connected to your LAN's Wi-Fi, then that's meaningful for troubleshooting, and I would like to know. Have not changed anything Changing ISPs, changing modem/router combos (including Bell Hubs), or ISPs making changes to its network (CGNAT, for example) matters. A fast busy can indicate a router/firewall or SIP ALG problem, but it can also result from the ATA rejecting the dialed number or another call-setup failure. I doubt the wrong phone port being used is the issue, since inbound calls ring your phone (which means it's plugged into the port tied to the registered line). However, if you have more than one phone, or have moved phones around, confirm the phone you dial from is the same one you're receiving incoming calls on. On a two-port SPA112, the phone making outbound calls should be plugged into the port that matches the line registered with FPL. If FPL is on Line 1, use the Phone 1 port on the back of the ATA, not Phone 2. Log in to the ATA's web UI, and navigate to Voice--> Info-->Status to see which line shows "Registered". That's the L

Hi! I'm a bit stuck. I have had a working freephoneline system for at least a decade I think... It's been trouble free and I almost never need to touch it. I downloaded the Fongo Mobile app recently and signed up for another number using the same email as my FPL account. I never thought this might cause a problem... but now I've noticed I can no longer make outbound calls on my FPL landline. I'm almost positive this started around the time I signed up for Fongo Mobile. Does anyone know if this is a known issue? My setup is: Cisco ATA SPA112. Configured a decade ago... Have not changed anything. Working flawlessly for 10+ years. VoiP unlock key purchased long ago. FPL current status shows "connected". I am currently paying for 911 service... No problem there, except I cannot actually dial out to 911 if I wanted to. Inbound calls work fine. No problem inbound. freephoneline.ca/doGetCallLogs shows incoming calls. It does not show any outbound calls at all. I've contacted Fongo Mobile to describe this problem and they told me FPL is unsupported. Does anyone have any suggestions? Totally stumped. Thanks!!! ----------------- https://www.freephoneline.ca/showSipSettings : YOUR SIP STATUS SIP Status:connected SIP User Agent:Cisco/SPA112-1.3.5(004p) Your SIP Settings SIP Username: SIP Password: Inbound/Outbound Proxy:voip.freephoneline.ca Local SIP Port:RANDOM Local RTP Port:RANDOM Registration Expires:3600 Enabled Codecs:G711u/PCMU and G729a ONLY Use Preferred Codec:G711u/PCMU or G72

Thanks. You're welcome!

Thanks. You're welcome!

Thanks. You're welcome!

Thanks. You're welcome!

Thanks. You're welcome!

Thanks. You're welcome!