No incoming calls

[Ironman1734]

Ive had FPL for 2 years now and haven't had this problem yet. As of August 1st I have been unable to receive calls. I can call out with no issues. When I call my home number from another phone it's silent for about 20 seconds then starts a quick beeping. It doesn't go to voicemail at all. If I set the followme settings to forward when unavailable it does the same thing. When I set the followme settings to always forward to my cell phone calls will then forward. I'm at a loss with this I have made no changes to hardware or settings. I have the Linksys pap2 ata that I got from FPL.

I have tried cycling the power on the modem, router and ata and that has not helped.

Has anyone ran into this issue? It has worked perfectly for over 2 years up to this point. Any help would be appreciated.

Thanks!

[dibsmft]

Have you recently changed any devices, settings or started running voip on say a PC?
Try running STUN (stun.ekiga.nat) and "NAT Mapping Enable" whic might help. There are other things you can try such as resetting your PAP2 possibly back to factory (at your own risk especially if it has been unlocked!) and then reconfigure the ATA. If that does not work then I suspect that the router/ATA are actually mis/not configured and so your should go through the complete procedured of assigning a static IP to your ATA and forwarding ports from the router to the ATA.
It is very difficult to offer help for your problem as you have given so little information about the set up that you are using.

[bf7041]

Another thing to try - if you are using a STUN server - don't.

Turn it off and try it without STUN - this may solve the issue.

good luck.

John

[dibsmft]

Yes, bf7041, that is a good point. But if STUN is not being run it is the very thing that may make things work as it may be needed with the PAP2 to get and retain the local IP. Difficult to guess what will work as the user has not given much information.

[Bloodsong]

Ive had FPL for 2 years now and haven't had this problem yet. As of August 1st I have been unable to receive calls. I can call out with no issues. When I call my home number from another phone it's silent for about 20 seconds then starts a quick beeping. It doesn't go to voicemail at all. If I set the followme settings to forward when unavailable it does the same thing. When I set the followme settings to always forward to my cell phone calls will then forward. I'm at a loss with this I have made no changes to hardware or settings. I have the Linksys pap2 ata that I got from FPL.

I have tried cycling the power on the modem, router and ata and that has not helped.

Has anyone ran into this issue? It has worked perfectly for over 2 years up to this point. Any help would be appreciated.

Thanks!

While "nothing has been changed" that is not the same as "nothing has changed".
Is your networking hardware all statically addressed? Check the IP on your ATA (pick up phone, dial: **** 110 # )
Is this the same IP that your portforwarding is set to in your router?

Now check your router's DHCP server settings, does the IP address of the ATA fall OUTSIDE of the given range? This is important as the router may accidentally assign the IP to someone's laptop or cellphone when they connect and then you'll have address conflicts.

As stated above STUN/ICE/Jingle servers can be useful or detrimental and should be tested for independently.

Have any new systems recently been added to your home network? Again are they static or DHCP? Do they offer a conflict against your ATA's IP address?

Have you logged into the ATA and checked the status page? What does it tell you about the registration status of your FPL account? Remember these ATAs can be configured to allow you to dial-out without first establishing a registered connection. When this happens it will use your FPL account credentials only to initiate a call, but will not register and therefor will not take inbound calls. (This is great if you want to run a VoIP COCOTS and steal a bit of the Bell market pay-phone market share.)

Please respond back to this thread in the format of:

Code: Select all

A) Issue: Is the ATA IP address static?
Fix: I set the ATA IP address to 192.168.13.42

B) Is the port forwarded to the correct IP address?
I checked the router's port forwarding settings and they point 5060-5061 and 10000-20000 at 192.168.13.42

etc.

That way we can see easily what has been tested and tried, and can make suggestions without wasting effort or time.

This will also serve to help you collect your own thoughts and perhaps come to a fix before we are able to respond.

[Ironman1734]

Issue A: Static IP? - Yes, IP is set to 192.168.0.253 and is reserved on the router(assuming this means it will not assign that IP to another devise, (I tried chaning the settings and setting the ATA outside of the DHCP range and disabled DHCP on the PAP2, but when I did that the line would not register and I got no dial tone, when its in the DHCP range it registers and there is dial tone)

Issue B: Port Forwarding? - 192.168.0.253 is forwarded to TCP - 5060-5064, UDP - 10000 - 20000, also is in my routers DMZ

Issue C: Other devices? - No new devices have been added to the network

Issue D: STUN/ICE/Jingle servers - I don't have any of these in use

Issue E: ATA Status - I have logged in and it shows as being registered
Hook State: On Registration State: Online
Last Registration At: 8/15/2012 20:17:42 Next Registration In: 3509 s
Message Waiting: Yes Call Back Active: No

Issue F: i don't and never have used VOIP using the desktop application, only with the ATA

Hardware:
Router: Dlink - DIR-655
ATA: Linksys PAP2T

in the last couple of days, when making an inbound call to my number it has been flipping between going to direct to voicemail and just giving silence for 5 seconds and then a slow beeping or saying this number is not active.

I appreciate everyones responses, if I can give any more information please let me know, other than that I'm puzzled as to why this just stopped working.

thanks again all!

[Ironman1734]

and one further point, I checked my call log from this current month.

There are a number of incoming calls that show the following:
0:05 15.08.12 21:32:24 15.08.12 21:32:28 Unallocated (unassigned) number Kitchener-Waterloo ON

there are approx. 25 instances of this, all occurring after the point the line stopped working.

And there are some instances that show the disconnect reason as: Normal Call Clearing, i'm assuming those are the times it goes to voicemail and I hang up.

[nikidd]

Did you find solution for this problem? I have exactly the same problem. My phone was ported from another provider yesterday. When I tested the phone yesterday I was able to receive calls. Today I can't.

[Ironman1734]

No solution yet still working on it. I currently have the line forwarded to a cell phone, this is the only way it will go to voicemail, otherwise it just beeps or says number unavailable when trying o call in.

[FONGO_mike]

Did you find solution for this problem? I have exactly the same problem. My phone was ported from another provider yesterday. When I tested the phone yesterday I was able to receive calls. Today I can't.

Have you updated the number in your ATA device yet?

[dibsmft]

No solution yet still working on it. I currently have the line forwarded to a cell phone, this is the only way it will go to voicemail, otherwise it just beeps or says number unavailable when trying o call in.

Your router has SIP Alg. Try turning SIP ALG off and see if it helps.

[Ironman1734]

I tried turning sip alg off, still just oes direct to voicemail, does not ring at all.

[Bloodsong]

Issue A: Static IP? - Yes, IP is set to 192.168.0.253 and is reserved on the router(assuming this means it will not assign that IP to another devise, (I tried chaning the settings and setting the ATA outside of the DHCP range and disabled DHCP on the PAP2, but when I did that the line would not register and I got no dial tone, when its in the DHCP range it registers and there is dial tone)

Issue B: Port Forwarding? - 192.168.0.253 is forwarded to TCP - 5060-5064, UDP - 10000 - 20000, also is in my routers DMZ

Issue C: Other devices? - No new devices have been added to the network

Issue D: STUN/ICE/Jingle servers - I don't have any of these in use

Issue E: ATA Status - I have logged in and it shows as being registered
Hook State: On Registration State: Online
Last Registration At: 8/15/2012 20:17:42 Next Registration In: 3509 s
Message Waiting: Yes Call Back Active: No

Issue F: i don't and never have used VOIP using the desktop application, only with the ATA

Hardware:
Router: Dlink - DIR-655
ATA: Linksys PAP2T

in the last couple of days, when making an inbound call to my number it has been flipping between going to direct to voicemail and just giving silence for 5 seconds and then a slow beeping or saying this number is not active.

I appreciate everyones responses, if I can give any more information please let me know, other than that I'm puzzled as to why this just stopped working.

thanks again all!

Thanks for the response, sorry for my delay on picking up on it.

If port-forwarding is set correctly than you shouldn't turn on DMZ as these two things may conflict with each other. (That is the DMZ may over-ride the port forward settings in some routers.)

Otherwise as Mike said, check your username and ensure you are registering the current in-use eleven digit phone number as the user name.

Judging by what you see in the call logs, it's probably worth calling in with that specific information, as it gives them something to look at.

[seagame2001]

No solution yet still working on it. I currently have the line forwarded to a cell phone, this is the only way it will go to voicemail, otherwise it just beeps or says number unavailable when trying o call in.

Are you in Mississauga or GTA area I can help you out

[Ironman1734]

Kitchener area

[dibsmft]

It seems to me that I would start by deleting the port forwarding etc to the factory and then set everything in a methodical way....
You do have sip alg and it seems that it may work. So I suggest that you cancel the forwarding, DMZ etc and turn sip alg back on. Set the ATA on DHCP. Power down the router and the ATA, wait 5 minutes and then power up the router followed by the ATA. See if it gets an IP OK and check the external IP that it gets and is it able to log in. Is there a dila tone. Note carefully what happens an let us know.

[seagame2001]

I think you should go buy another router and try it but don't buy D-link just get different brand

[nikidd]

Did you find solution for this problem? I have exactly the same problem. My phone was ported from another provider yesterday. When I tested the phone yesterday I was able to receive calls. Today I can't.

Have you updated the number in your ATA device yet?

Yes, I did that and I still have the same problem. If i reboot my ATA everything works fine for ~5 min and after that I can't receive calls.

[486dx]

Im kinda in my mind thinking at this point,.

run a speed test.net and post the link to your results,
also go run a pingtest.net with the toronto servers for both.

then try the ata direct to your internet for a few hours. if it works flawless like I hope it would, then your router is experiencing problems, maybe getting ready to die, which is why it worked hassle free for a few years and now not working consistant as it should day to day. also id recomment a 5port switch which could be had for 29.99 (futureshop, online tigerdirectm ncix.com ) and plug your internet source in first, then the ata box, then on the third port plug your router in. now since the switch is unmanaged, it will have no firewall and no ports needed to forward to keep the ATA connected. basically it simplifes the connection from the internet direct to it, and your network then begins with the router where all of your computers can share files, printers ..etc