No incoming calls
-
- Just Passing Thru
- Posts: 13
- Joined: 11/24/2011
- SIP Device Name: spa2102,SPA122
- Firmware Version: 3.3
- ISP Name: bell
- Computer OS: window7
- Router: ubnt
No incoming calls
I have two freephone incoming calls stop working on both follow me is disabled on both One is link sys other is cisco it was working good till two weeks ago
-
- Technical Support
- Posts: 3278
- Joined: 04/26/2010
- SIP Device Name: Obihai 202/2182, Groundwire
- Firmware Version: various
- ISP Name: FTTH
- Computer OS: Windows 64 bit
- Router: Asuswrt-Merlin & others
Re: No incoming calls
I just checked 3 different Freephoneline numbers in different locations that are working fine for incoming calls. I feel testing further Freephoneline numbers is pointless since the service appears to be working. I tested all Freephoneline proxy servers; they're working normally.
I. The first thing to check is the light patterns on the ATAs. What do they indicate?
i) For the SPA122, visit https://www.cisco.com/c/en/us/support/d ... pa122.html
ii) For SPA2102, visit http://qsupport.wikidot.com/linksys-spa ... t-statuses (I used to be able to locate an official source for LED light patterns, but because the ATA model is discontinued, it's become harder.)
II. Click viewtopic.php?t=20199 and provide the requested information (I don't trust user's forum profiles to have updated information anymore). Specifically, provide the information for 1,2,4 and 5. I don't think you'll find anything interesting from point 6, but take a look anyway.
1) What brand and model modem are you using? (I'm not sure if you're still using a Bell hub, but I need the model regardless)
2) What brand and model router are you using? (I'm not sure if you're still using a Ubiquiti router, but I need the model regardless).
4) What proxy server is being used in the ATAs (for example, voip.freephoneline.ca, voip2.freephoneline.ca, or voip4.freephoneline.ca:6060)?
When there are multiple devices/softphones/Lines (on an ATA) using the same FPL account, only the most recent registration is valid when the same proxy server is used. The previously registered device (or Line, in this case) will lose registration, and, consequently, incoming calls will not ring on it. This is especially important to consider if someone else is using your SIP credentials (username and password) that are found after logging in at https://www.freephoneline.ca/showSipSettings or if you're trying to register your FPL account with a smartphone SIP app (or FPL desktop app), with another device, or more than one ATA line. Registration is required for incoming calls. It is not required for outgoing calls. Only one registration per FPL account is allowed at any time. A single line on an ATA is one registration. A SIP app is another.
5a) What is the registration status for each ATA?
Login to your ATA. Navigate to Voice tab-->Info tab-->Line (used for FPL) Status (this is not a tab)-->Registration State
Ensure your Line is registered.
Unless you own two VoIP unlock keys, you can't register two ATA lines with your FPL account simultaneously when using the same proxy serer.
5b) Also, check the "SIP status" after logging into both Freephoneline accounts at https://www.freephoneline.ca/showSipSettings
Please note that if "SIP User Agent" reflects a different device than the one you're using, someone else is likely using your Freephoneline VoIP unlock key. Only one registration is permitted at any time per Freephoneline VoIP unlock key. Registration is a requirement for incoming calls but not for outgoing calls.
6) Login at at https://www.freephoneline.ca/callLogs to check if you see a "Disconnect reason".
Check and confirm that the "To" and "From" fields represent numbers you expect.
I doubt #6 is useful, but check anyway. Only calls that are answered in some manner (by you or FPL's voicemail system) are listed.
III. After providing requested information, follow the troubleshooting steps slowly and carefully, step by step, down the list from viewtopic.php?t=20532. Do not skip step 13 if you reach that far without getting incoming calls to work. That is, try "voip4.freephoneline.ca:6060" (without the quotation marks) for "Proxy" in the ATA.
I. The first thing to check is the light patterns on the ATAs. What do they indicate?
i) For the SPA122, visit https://www.cisco.com/c/en/us/support/d ... pa122.html
ii) For SPA2102, visit http://qsupport.wikidot.com/linksys-spa ... t-statuses (I used to be able to locate an official source for LED light patterns, but because the ATA model is discontinued, it's become harder.)
II. Click viewtopic.php?t=20199 and provide the requested information (I don't trust user's forum profiles to have updated information anymore). Specifically, provide the information for 1,2,4 and 5. I don't think you'll find anything interesting from point 6, but take a look anyway.
1) What brand and model modem are you using? (I'm not sure if you're still using a Bell hub, but I need the model regardless)
2) What brand and model router are you using? (I'm not sure if you're still using a Ubiquiti router, but I need the model regardless).
4) What proxy server is being used in the ATAs (for example, voip.freephoneline.ca, voip2.freephoneline.ca, or voip4.freephoneline.ca:6060)?
When there are multiple devices/softphones/Lines (on an ATA) using the same FPL account, only the most recent registration is valid when the same proxy server is used. The previously registered device (or Line, in this case) will lose registration, and, consequently, incoming calls will not ring on it. This is especially important to consider if someone else is using your SIP credentials (username and password) that are found after logging in at https://www.freephoneline.ca/showSipSettings or if you're trying to register your FPL account with a smartphone SIP app (or FPL desktop app), with another device, or more than one ATA line. Registration is required for incoming calls. It is not required for outgoing calls. Only one registration per FPL account is allowed at any time. A single line on an ATA is one registration. A SIP app is another.
5a) What is the registration status for each ATA?
Login to your ATA. Navigate to Voice tab-->Info tab-->Line (used for FPL) Status (this is not a tab)-->Registration State
Ensure your Line is registered.
Unless you own two VoIP unlock keys, you can't register two ATA lines with your FPL account simultaneously when using the same proxy serer.
5b) Also, check the "SIP status" after logging into both Freephoneline accounts at https://www.freephoneline.ca/showSipSettings
Please note that if "SIP User Agent" reflects a different device than the one you're using, someone else is likely using your Freephoneline VoIP unlock key. Only one registration is permitted at any time per Freephoneline VoIP unlock key. Registration is a requirement for incoming calls but not for outgoing calls.
6) Login at at https://www.freephoneline.ca/callLogs to check if you see a "Disconnect reason".
Check and confirm that the "To" and "From" fields represent numbers you expect.
I doubt #6 is useful, but check anyway. Only calls that are answered in some manner (by you or FPL's voicemail system) are listed.
III. After providing requested information, follow the troubleshooting steps slowly and carefully, step by step, down the list from viewtopic.php?t=20532. Do not skip step 13 if you reach that far without getting incoming calls to work. That is, try "voip4.freephoneline.ca:6060" (without the quotation marks) for "Proxy" in the ATA.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at http://forum.fongo.com/viewforum.php?f=15.
-
- Just Passing Thru
- Posts: 13
- Joined: 11/24/2011
- SIP Device Name: spa2102,SPA122
- Firmware Version: 3.3
- ISP Name: bell
- Computer OS: window7
- Router: ubnt
Re: No incoming calls
Thanks for suggestions I have two different numbers on different spa 102 and spa 122. both were fine before out going is working ok.
I am in India from last 4 months. It just happen in last month or so. I do not have Pc only a note book. Do not remember what proxy server was using. When I log on the SIP account the status is connected. Three light are on. second light is flickering fast. Log is OK Calling number is shown in log. I really appreciate your answer rest i will check when i get back home. thanks
I am in India from last 4 months. It just happen in last month or so. I do not have Pc only a note book. Do not remember what proxy server was using. When I log on the SIP account the status is connected. Three light are on. second light is flickering fast. Log is OK Calling number is shown in log. I really appreciate your answer rest i will check when i get back home. thanks
-
- Technical Support
- Posts: 3278
- Joined: 04/26/2010
- SIP Device Name: Obihai 202/2182, Groundwire
- Firmware Version: various
- ISP Name: FTTH
- Computer OS: Windows 64 bit
- Router: Asuswrt-Merlin & others
Re: No incoming calls
A notebook computer is a portable PC. They can be used for configuring ATAs.
NAT corruption can develop between a router and ATA without the user doing anything. Refer to step 28 from viewtopic.php?t=20532. Also, ISPs can push firmware updates to modem/router combos, gateways, or hubs that suddenly enable SIP ALG. Users can accidentally enable Do Not DIsturb (dial *79 to disable it) or enable call forwarding (dial *73 to disable it). If the phone handset used has the ability to enable do not disturb as well, that could also be the cause. Also check to ensure the ringer on the phone isn't turned off. Try a different phone. Really, the steps should just be followed down the list instead of trying to randomly guess what the problem is: viewtopic.php?t=20532.It just happen in last month or so
You can check by logging into the ATAs via their webUI. The instructions for logging in are located in step 9: viewtopic.php?t=20532. Then navigate to the Line used for FPL-->Proxy and Registration->-Proxy.Do not remember what proxy server was using
Can you see the failed incoming call after logging in at https://www.freephoneline.ca/doGetCallLogs ? If you can, the incoming call is reaching Fongo’s network.Log is OK Calling number is shown in log
If you can, check to see whether the most recent incoming call is also reaching your ATAs. Login to their web interface, and navigate to Voice tab-->Info tab-->Line (used for FPL) Status (this is not the Line tab; you should be on the Info tab still)-->Last Caller Number. You'll see the most recent incoming call number that reached your ATA. Unfortunately, you can also only see the most recent number (not past ones).
If the failed incoming call is reaching Freephoneline (Fongo's network) but not the ATAs, then the problem could be related to SIP ALG, NAT corruption, a firewall issue, or an intermittent internet issue (severe ping spikes can lead to incoming calls not being received; refer to step 26).
Having Do Not Disturb or call forwarding enabled in the ATAs will force incoming calls to drop straight to Freephoneline’s voicemail system. Also ensure Rings Before Voicemail is greater than 1 in your Freephoneline account web portals.
I need the rest of the information, and, again, you should be following the steps here, step by step, down the list: viewtopic.php?t=20532. For steps 1, 2, and 3, having the brand and model of both the modem and router used helps me to try to ensure SIP ALG isn't causing a problem. Freephoneline's servers are located in Southern Ontario. If the ATAs are in India, pay close attention to step 26 from that link as well. The steps should really be followed in the order that they are presented, but if you want something simple to try, look at step 19. Also ensure that Do Not Disturb has not been accidentally enabled on both ATAs (all of step 10) and in the phone handsets being used (if the option exists). It would be better to go step by step through the list of instructions.
Incoming calls are working fine on all Freephoneline numbers I've tested.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at http://forum.fongo.com/viewforum.php?f=15.