Incoming calls do not work!!

[nick]

"The person you are trying to reach is not available"

I got this issue for a long time.

When someone call my number, always hear: "The person you are trying to reach is not available"

I was thinking it was caused by the router initially. I was using ASUS RT-N13U. I changed to DIR-615 today. It seems that still have the issue.

It looks like it's related with my account setting.

Can someone please help look into it.

[FONGO_steve]

Have you setup port forwarding on any of the routes? It sounds to me like the router is blocking/filtering the incoming SIP requests and thus our system isn't able to "see" that you are actually available.

[nick]

Yes. I have tried to forward ports. Also I have tried to put my PAP2 in DMZ of both routers. thanks

[laurent]

1. Are you using softphone, an ATA device, or an SIP phone?
2. What is the IP address of the device you are using?
3. In your port forwarding of the router, are *all* ports mentioned in the FAQ all manually forwarded to the IP in #2?
4. In you are using a softphone, is there a firewall active on the computer? Have you tried to disable it?

[yannbr]

I have the same problem !
I can call others, but each time they try to reach me, they alway get "The person you are trying to reach is not available". (I try myself with my cell)
I'm using the freephoneline software. I haven't done any configuration on my router (I don't know anything about network and etc.)

Can you help me ?

[laurent]

Sure, we can help! The first thing to do, unfortunately, is going to be to make some network configuration changes.

To get there, we must known what kind of internet service and equipment you have. Please give us a brief description of what you have.

Then, we will be able to tell you what you will need to know.

In a nutshell, we want to have you go in your internet routing/sharing device, and setup a rule to push phone calls that come from the outside of your home, directly to whatever device is responsible for handling that call. In this case, it's a software phone on your computer.

[yannbr]

I'm with Videotron. The modem is linked to my wireless router (Lynksys WRT54G). What more can I give ?

[bridonca]

Upgrade your firmware on your router to something like DD-WRT. The stock firmware is unbelievably atrocious and was bad in 2002. It has not improved with age. You do the upgrade, and magically, your voip problems go away. As a side benefit, other transfer work better also.

[laurent]

In a nutshell, you need to find out the IP address your computer receives in your network. Then you go to your router's web configuration page, and set up port forwarding rules for all the ports detailed on the FAQ page, and you forward these ports to the IP address of your computer.

Once that's done, incoming call should work.

[nick]

As for my case. I am using PAP2-NA.

Yes. I definitely forward all ports to PAP2. also tried put pap2 in DMZ.

I tried ASUS RT-N13U, DIR 615 (VER C1)

Have same issue.

[nick]

In coming call used to work for me in 2009.

At sometime early this year, it is dead.

[bridonca]

Yeah, I feel like something got tweaked at freephoneline that messed up my incoming calls also. When I set up the router to know exactly where to route the packets, it worked again. Dealing with other SIP VOIP providers, I realized this is not the fault of freephoneline. It is an issue with the flakiness of SIP though NAT. Oddly, I never had this problem with my Grandstream devices. Probably why freephoneline switched to Grandstream.

[FONGO_steve]

Probably why freephoneline switched to Grandstream.

We've seen astonishingly better results with the Grandstreams than other devices. Where as most other ATAs require port forwarding, the Grandstreams always seem to work right out of the box.

Earlier this year we also did an upgrade that brought much better NAT traversal to the service. We're seeing far, far fewer cases where port forwarding needs to be done to get things working successfully. Unfortunately we'll likely never get things perfect though, because as you mention SIP doesn't always play nicely with NAT traversal. There's still lots of routers and firewalls that filter it until explicit exceptions are set to allow it.

[OverDrive]

Probably why freephoneline switched to Grandstream.

We've seen astonishingly better results with the Grandstreams than other devices. Where as most other ATAs require port forwarding, the Grandstreams always seem to work right out of the box.

Earlier this year we also did an upgrade that brought much better NAT traversal to the service. We're seeing far, far fewer cases where port forwarding needs to be done to get things working successfully. Unfortunately we'll likely never get things perfect though, because as you mention SIP doesn't always play nicely with NAT traversal. There's still lots of routers and firewalls that filter it until explicit exceptions are set to allow it.

Of those Grandstream devices, you mention that it works out of the box, but is that using UPnP? Because if you have UPnP turned off (for better security) then I'm wondering how the grandstream works without port forwarding.

[zombie999]

Of those Grandstream devices, you mention that it works out of the box, but is that using UPnP? Because if you have UPnP turned off (for better security) then I'm wondering how the grandstream works without port forwarding.

I have UPnP turned off in my router. I have a PAP2, SPA 941 & a Globarange ATA phone all connected to that router. They all work fine with NO port forwarding. I used to have a Mediatrix ATA as well and it also worked fine with no port forwarding.

For those obsessed with port forwarding, you can read more here. Then decide if you need it or not.

http://www.dslreports.com/forum/r231966 ... an-one-ATA

http://www.dslreports.com/forum/r222791 ... l-settings

[bridonca]

I do not have UPNP on my routers. I had a PAP2 work great for months without port forwarding, and then out of the blue, I had issues. I still put the fault to the router not designed to properly handle SIP traffic. When I manually configured the router to use certain ports for my PAP2 ATA, there was no ambiguity, so it just worked.

I suspect the Grandstream ATA just works because it does not assume the ports assigned to it are permanent. I believe the Grandstream ATA has a mechanism to periodically test the connection and adapt as needed. I feel the PAP2 is a simpler device. It works fine as long as the router doesn't change things around.

I might have a fix of sorts for people that are not getting incoming calls. I stumbled upon it myself, and never thought much of it, but it makes sense. Set the SIP registration period to 120 seconds instead of the default 3600 seconds. The reasoning is this:

Checking every hour should be ample time period to keep a SIP registration going. The problem is, some routers will only keep a port reserved for 120 seconds before assigning it to something else. So if you set the SIP registration period to 120 seconds, the ATA can say it is still alive every 120 seconds and keep that port reserved to it. That way, when you do get an incoming call, it can route to your ATA.

[nick]

Although I know it's not related with my router, I still want to give a last try.

Flash the DIR-615 with the latest DD-WRT (BUILD 14896). still have the exact same issue.

So, almost safe to say it's not related with router.

Freephoneline, please try to resolve the issue on your end.

Thanks!!

[FONGO_steve]

Hey Nick,
This issue isn't on our end, it looks to be with your ATA setup. Your ATA is rejecting the calls when our server sends them:

21:57:12.998 | @-> (B? 214/I) ♪ INVITE ----------------------------------------------------------------->|
21:57:13.038 | |<- (B? 214/I) 100 Trying ----------------------------------------------------------------@
21:57:13.045 | |<- (Ba 214/I) ! 488 Not Acceptable Here ----------------------------------------------@
21:57:13.045 | @-> (Ba 214/A) ACK ---------------------------------------------------------------------->|

[nick]

FPL-steve,

Thanks for the reply.

I power off my ATA when I am not home during the day (also there is no point to keep the ATA always on since the incoming calls do not work for me).

Do you guys have office in Kitchener/ON, maybe I can bring in my ATA to let you guys have a look.

I do not believe it's my ATA's issue though.

Before I choose FPL, I used vBuzzer. incoming calls worked perfect for me. Also, FPL worked for me in 2009.

Thanks!!

[FONGO_steve]

Hi Nick,
Your ATA was powered on during that call log I pulled up. I'd start with just a full reset and re-configuration of it - that will likely fix whatever setting has gone astray.

[nick]

Ok..I will do a full reset this weekend. Will let you know if it helps or not. thanks!

[yannbr]

I tried to upgrade my linksys wrt54g but I bricked it doig it.... anyways it was doing strange things these lasts weeks.
Anyways I bougth a NetGear wireless router, and got a lot more option to configure. I set the 6 UDP ports (in the FAQ page) redirecting on the IP of my computer, but i'm always gettings incomming call to the voicemail

I checked in my Windows Seven firewaal service and everything seems to be ok...

And when the softphone is opening, the host i'm picking up is the same IP of my computer

Here's my config : http://www.imagup.com/pics/1284688782.html

I'm am forgetting something ? Help me please !

[OverDrive]

I tried to upgrade my linksys wrt54g but I bricked it doig it.... anyways it was doing strange things these lasts weeks.
Anyways I bougth a NetGear wireless router, and got a lot more option to configure. I set the 6 UDP ports (in the FAQ page) redirecting on the IP of my computer, but i'm always gettings incomming call to the voicemail

I checked in my Windows Seven firewaal service and everything seems to be ok...

And when the softphone is opening, the host i'm picking up is the same IP of my computer

Here's my config : http://www.imagup.com/pics/1284688782.html

I'm am forgetting something ? Help me please !

if you set a static ip of 192.168.1.2 on your computer and plug it into the old router (the one you bricked), can you ping 192.168.1.1? if you can, you can still TFTP the firmware up.

I thought I bricked mine too, but i was able to restore it using TFTP.