Tried everything. No incoming.

[steinburgs]

Hello,

I have a Linksys PAP2.

I can make outgoing but cannot receive incoming calls. It goes directly to voicemail.

I've tried everything. I've used settings that I've found in various forum posts and other internet sites.

I've forwarded ports etc.

I've tried one user's provisioning file.

Changed the ring section back to my previous working setting of 25-85.

I've checked it, double checked it, double-double checked it and still no luck.

I've been using this ATA with another provider without problems so I don't think it's a hardware issue. All my outgoing calls always work, no matter how much tampering I do to try and make the incoming work.

I hope someone can help.

Thanks.

[laurent]

Would you be able to grab screenshots of the configuration of your router, and the configuration of your ATA?

I know you've double-double covered those, but it looks like the issue is either device registration or incorrect port forwarding. Perhaps we can take a look at all your config at see if we can spot something?

[steinburgs]

Router.jpg

papinfo.jpg

papsystem.jpg

[steinburgs]

papsip.jpg

papRegional.jpg

papregional2.jpg

[steinburgs]

papline1a.jpg

papline1b.jpg

papline1c.jpg

[steinburgs]

Thanks for your assistance.

If something looks abnormal, it may because I tried a different setting suggested in a forum thread or internet post somewhere.

Feel free to point it out though and I can tell you what I have had in there.

Steve-FPL pointed out that everything looks fine on my account on their servers, however I am not showing registered there. Would I be able to make outgoing calls without be registered? I am making calls now without an issue. Only incoming is an issue.

Thanks for any assistance you can provide.

[bridonca]

To further isolate the fault, could you connect the PAP2 directly to your modem? If the PAP2 works, you still have a routing issue, where either more port configuration needs to be done, or the router firmware could be lacking. Newer/better firmware or a better router may be needed.

[laurent]

Okay

1) in your router configuration, don't forward ports 53 and 69. They serve no purpose for VoIP.

2) You're missing a few ports to forward. You need UDP ports 13000-13001, 5060-5061, 6060-6061 (which you already have). No need to set the type to "BOTH", only UDP is required here. Your ATA doesn't seem to use 5060 though, but mine does.

Both observations shouldn't have much of an effect for your problem.

In *my* case, I use 5060 as my SIP port (and have the router forward it of course). You can change yours to it, instead of 6060, for fun, but this shouldn't do anything.

[OverDrive]

Okay

1) in your router configuration, don't forward ports 53 and 69. They serve no purpose for VoIP.

2) You're missing a few ports to forward. You need UDP ports 13000-13001, 5060-5061, 6060-6061 (which you already have). No need to set the type to "BOTH", only UDP is required here. Your ATA doesn't seem to use 5060 though, but mine does.

Both observations shouldn't have much of an effect for your problem.

In *my* case, I use 5060 as my SIP port (and have the router forward it of course). You can change yours to it, instead of 6060, for fun, but this shouldn't do anything.

YOU ONLY NEED to port forward 5060/5061 WITH AN ATA.
(Don't forget to change your sip port in your ATA to 5060/5061 (line1/line2))

The others are for the software.

I agree with #1 - drop the 53/69.
2- ONLY PORT FORWARD 5060/5061


To quote an admin

Postby admin » Sun Jul 04, 2010 10:02 pm
Yes most SIP goes through UDP, for the software you may need 13,000 & 13,001 and 6060-6061. For the ATA, you will need 5060 - 6061 - These can be changed on your device.
Kris
FreePhoneLine Administrator
admin@freephoneline.ca
Freephoneline.ca
Please remember for urgent issues to always call support before PMing us!

[steinburgs]

Okay. So I've changed the port back to 5060 and the forwarding to the same. It still didn't work.

I've also plugged the PAP2 directly to the modem. This was actually worse. I had no dial tone and no incoming or outgoing. I could see that it wasn't registering.

Still dumbfounded. Any other suggestions?

[zombie999]

If you are using port forwarding (what is normally not needed), you need to enable NAT MAPPING and NAT KEEP ALIVE.
Also change your preferred codec to G711u.

If it still does not work, put your ATA in the DMZ and try.

Also try using other ports, like go up from 5061, 5062, 5063.

Use utorrent port checker to see port 5060 is open.

If it still does not work, what is your ISP? Cable, DSL, wireless?

[zombie999]

Also you can try and get an account with an online PBX. Like pbxes.org. See if your incoming is working then. This will eliminate you network set up as the problem.

[laurent]

ATA directly to the modem only works when the modem is either:
a) a Cable modem which typically has a DHCP server in it
b) a DSL modem with integrated router, like Bell 2wire modems, for example.

If what you have is a plain-vanilla DSL modem, like a SpeedTouch or something like that, then plugging the ATA directly in it will NOT work unless you *also* instruct your ATA to initiate the internet connection through PPPoE. (Yes, more acronyms.)

So I suggest we start from the beginning and work our way to the ATA, validating all steps.

First, what is your internet connection provider and type? Cable, DSL, satellite?

[steinburgs]

ya..I realized how dumb that was after I did it and posted.

It's a dsl connection requiring a managed UserID and Password. My dsl modem is connected to my router and I use that to make my login.

I'm still stuck and frustrated. Like I said in my original post, I've had another provider for over a year. Incoming works with them so I don't know what I am missing here.

[bridonca]

What do you have for gear? What is the brand on model number of the DSL modem? What is the brand on model number of the router?

[nick]

I have exact same issue here.This issue started in 2010. Originally, incoming call works. I also tried different routers. Ata in DMz. Looks like to be a fpl's problem.

[steinburgs]

I have a Belkin F5D8236-4 v3000 router and the modem is an Aztech DSL-605EU.

I did the uTorrent Port Checker and it's not showing 5060 or 5061 as open but it's not showing 80 or 110 open either.

I've turn off my router firewall (and my windows firewall too just to see).

[steinburgs]

BTW, I tried Line 2 with the FPL settings and no luck.

I switched everything back to my current voip provider. It took 2 minutes and it worked flawlessly. I really want the FPL to work. I don't understand.

[bridonca]

I see your problem. You are trying to run your VOIP ATA through 2 NAT routers. That will not work. You are going to have to disable one of those NATs.

I would normally recommend you run your wifi router in Bridge mode, but your Belkin F5D8236-4 is unable to do that. It is not a very good router.

You will need to run the router on the DSL modem in bridge mode. This might help, http://www.acanac.ca/docs/routersetup2007.pdf When you do that, your Belkin F5D8236-4 has to take care of the PPPoE login. If you do not have the PPPoE login info, you will have to get it from your ISP.

[laurent]

BTW, I tried Line 2 with the FPL settings and no luck.

I switched everything back to my current voip provider. It took 2 minutes and it worked flawlessly. I really want the FPL to work. I don't understand.

Just for kicks, what are the port forward settings for your other VoIP provider, which happens to work with your combination of modem/router/ata? Perhaps we can learn from "what works".

[steinburgs]

Argh... Well, I think that I had the modem in bridge mode before but I had trouble getting to the setup page so I had to do a reset. I put it in (or back in?) bridge mode. Still does not work.

Tried the provisioning file again for sh and giggles. Still not working.

As for port forwarding with my other voip provider, I did not need any. It just seemed to work.

I don't know how much more tinkering I can do but I am up for more suggestions.

Thanks for trying to help guys/gals.

p.s. FPL is saying that I am showing registered on their end.

[steinburgs]

I disabled ICMP blocking on the router while testing open ports because the port checker tool couldn't access the router. The port checker isn't showing any open ports. I'm lost.

[steinburgs]

Enable DMZ did nothing.

[laurent]

There's very little chance you can actually check for UDP open ports with a single tool. It doesn't work like TCP where an acknowledgement is sent back to validate that the port is open and listened to. UDP is "dumb" in that regards, so by all means, your test doesn't really show anything, be it positive or negative.

There's a number of times where your situation should have been resolved, like when you tried DMZ, for example.

I fear that I have nothing more to suggest to you, without being physically present.

[FONGO_steve]

p.s. FPL is saying that I am showing registered on their end.

You're definitely registering (ie. you can communicate with us)
But this problem is falling with us trying to communicate back to you and being blocked/filtered.

I've only skimmed this thread, but have you tried using a non-bridged modem connected directly to the ATA with only our service on it? Ie. disable your other VOIP service on that ATA if they share one.

There's definitely some sort of filtering/port blocking happening somewhere.