Incoming calls fail

[warkior]

We've been using DellVoice with SIP credentials and a Linksys PAP2T to run our home phone service and lately have had no end of trouble with incoming calls. We never have any problems calling outbound, and after we have called out then incoming calls work for a little while (hour?) but eventually they start to fail. Basically, the person will call our number, and simply hear silence for 20 seconds (give or take) until their phone just hangs up. It does not ring on our end, nor do they hear it ringing on their end.

It's super frustrating. Any suggestions?

Any ideas what to look at for finding the cause?

Thanks,
James W.

[TheHardy]

Even though you may not have changed anything on your end, make sure that the port forwarding for the router etc has not changed and is set as per the recommendation documentation on this forum. Short of that, I share your frustration.

After a certain time, even with an ATA, the call should dump to voicemail and be answered.

One thing I would ask, is are the FAILED calls showing up in your online account log? Zero-duration calls are NOT sorted in correctly and appear at the bottom of the call log (dunno why, please ask someone who can answer that). If they are not even showing in the log, then it is a network side error/problem where the calls are not even being processed by the network correctly!

[warkior]

Hi TheHardy,

The failed calls do appear to show up in the account log. They're shown simply as zero duration though they do appear to be sorted correctly. They show up in the form of:
Duration Date Disconnect Reason Location Cost
0:00 18/10/2012 15:23:03 Normal call clearing Vancouver BC $ 0.00

As for the port forwarding, it is set up as so...
# Service Name Start Port End Port Server IP Address
1 IP_Phone 5060 5060 [removed]
2 IP Phone RTP 16384 16482 [removed]

I've gone through all the SIP settings again on the PAP2T and configured them according to what is written here, and we'll see if it makes a difference.
http://blog.voipdiy.com/2012/02/dell-vo ... -voip.html

James W.

[warkior]

An added note... On the router, I have NAT filtering set to "secured" and I have NOT disabled SIP ALG. Notes from the router instructions...

NAT Filtering

This option determines how the router deals with inbound traffic. The Secured option provides a secured firewall to protect the PCs on LAN from attacks from the Internet, but it may cause some Internet games, point-to-point applications, or multimedia applications not to work. The Open option, on the other hand, provides a much less secured firewall, while it allows almost all Internet applications to work.

Disable SIP ALG

Some SIP applications have their own way to work around the NAT firewall issue, and the SIP ALG would conflict with those solutions. In most cases, you do not have to disable the SIP ALG. However, if your SIP applications cannot work with the router, you can disable the SIP ALG and try the applications again.

[warkior]

Still no luck. Although, it would seem that on my latest try, I called once, but two calls were recorded in the call log. One at 24/10/2012 17:41:12 and the other at 24/10/2012 17:41:23. Both from the number that I used to call with. This is a really frustrating problem.

[warkior]

I'm cautiously optimistic that I may have resolved the problem by enabling NAT Keep Alive. The coming days will tell for certain.

[TheHardy]

If they show in the call log, then it is not a Fongo-network problem. Disable the SIP ALG, btw, as that is known to cause problems!

[mayoni]

I have a weird problem. I can call the Dellvoice app from Telus cellphone, but when I tried to call from my other VOIP phone, I get "number you have dialed is not in service"? Is it because I just signed up today and it's not fully setup yet? I'm using the android app on Samsung galaxy S3. I tried using 3G data and also wifi on the phone, calling out is good, but receiving calls is another matter. Even calling from Telus cellphone is not 100% received. Any thoughts on this?

[TheHardy]

I have a weird problem. I can call the Dellvoice app from Telus cellphone, but when I tried to call from my other VOIP phone, I get "number you have dialed is not in service"? Is it because I just signed up today and it's not fully setup yet? I'm using the android app on Samsung galaxy S3. I tried using 3G data and also wifi on the phone, calling out is good, but receiving calls is another matter. Even calling from Telus cellphone is not 100% received. Any thoughts on this?

Getting the NIS recording is 100% due to the originating carrier (Telus or whatever VOIP provider) -- it means that they are not routing the call correctly. If you just get DEAD AIR with no recording, or a fast busy, that can at times be a Fongo issue.

Pretty well as soon as you sign up, your Fongo # is active on that end of things --- I have started receiving calls within SECONDS of having an account set up!

Which area are you in and what # are you assigned (first 6 digits -- NPA-NXX ... area-code & exchange) ... some are relatively new.

Also, some other VOIP providers DO seem to have trouble routing to Fongo-based numbers correctly, I think it might be competitive jealousy of a sort!

[FONGO_mike]

I have a weird problem. I can call the Dellvoice app from Telus cellphone, but when I tried to call from my other VOIP phone, I get "number you have dialed is not in service"? Is it because I just signed up today and it's not fully setup yet? I'm using the android app on Samsung galaxy S3. I tried using 3G data and also wifi on the phone, calling out is good, but receiving calls is another matter. Even calling from Telus cellphone is not 100% received. Any thoughts on this?

Getting the NIS recording is 100% due to the originating carrier (Telus or whatever VOIP provider) -- it means that they are not routing the call correctly. If you just get DEAD AIR with no recording, or a fast busy, that can at times be a Fongo issue.

Pretty well as soon as you sign up, your Fongo # is active on that end of things --- I have started receiving calls within SECONDS of having an account set up!

Which area are you in and what # are you assigned (first 6 digits -- NPA-NXX ... area-code & exchange) ... some are relatively new.

Also, some other VOIP providers DO seem to have trouble routing to Fongo-based numbers correctly, I think it might be competitive jealousy of a sort!

If the number can be reached by one carrier, it can be (should be) reached by all carriers.

In this case, i agree, the other voip provider is who you would need to contact about not being able to reach the number.

[TheHardy]

If the number can be reached by one carrier, it can be (should be) reached by all carriers.

In this case, i agree, the other voip provider is who you would need to contact about not being able to reach the number.

Not the case at ALL Mike ... each carrier must update it's OWN rates&routing table, and some of them are notoriously slow for doing so. I have had this experience on several occasions and have filed MANY a trouble ticket. Some carriers get them loaded as soon as they are published by CNAC, others take a while. WIND responds to trouble tickets VERY slowly, and Telus Mobility very quickly, just by way of example.