[Resolved 8/1/10] 5 - 90 Min into the call and drops out

[Joe B]

My problem of dropped calls has been solved by using the settings from the previous user. Does anyone have any suggestions for someone using a Grandstream 286 ATA. Thanks for the help.

[Joe B]

Again,as I wrote on this or the other thread, to be absolutely honest, I personally do NOT _seem_ to experience the dropped calls issue anymore. The only thing I changed in my ATA settings for that was setting 'NAT Keep Alive Msg:' from the default value of '$NOTIFY' to '$PING', as well as changing the NAT keep-alive time settings to 1 min if I'm not mistaken... And, again, the sequence of events was

- everything worked, no dropped calls
- without any changes on my side, I started experiencing dropped calls 2-3 months ago for any calls longer than 10-15 min. No call went uninterrupted for over an hour (ie, the call would drop some time 10 - 60 min into the call)
--- other people reported the same issue on the FPL board within day or two
- issue got escalated to FPL, Kris mentioned that the problem is on FPL side, has smth to do with Load Balancing (which does make sense to me, since the issue is intermittent and quite hard to reproduce)
- while waiting on the fix from FPL, I searched the net and the 'NAT Keep Alive' setting was smth that was worthwhile to try providing the potential root of the problem
--- the default $NOTIFY setting is not going through properly - if you analyze the log, you'd see the socket connection is not established.
--- The documented $REGISTER setting does more harm than good - seems to cause SIP server to reregister line instead of keeping the connection alive
--- the $PING is an 'undocumented' setting (at least I couldn't find it in any Linksys / CISCO manuals) referenced to me by one of the users on this forum - search the threads...
- Around the time I set 'NAT Keep Alive Msg' setting to '$PING' the dropped calls issue seemed to stop happening
--- right after setting NAT Keepalive settings, I did a few tests at night time making calls to and from my cell. Disconnected myself after the connection was alive for over 1.5 hours straight

So...... I can't reliably tell whether $PING solves the issue or helps to solve it (for that, I would need to turn it off again and run the tests - don't have time for this now). It might have been the setting or it might have been the changes FPL did on their side around the same time. In any case, some change or change in load on the FPL side caused this issue in the first place, as we seem to have reliably eliminated the ISP from the chain at that time, as people using other DSL & Cable ISPs (Bell, Acanac, Rogers, etc) started experiencing the same issue around the same time.

Hopefully this would straighten out the historical trace on this one . And as a general recommendation, try playing with NAT Keepalive settings, especially if you are behind a router - some of those settings actually make sure to overwrite the SIP header with proper values... (see attached screen shots).

Thanks for the help. I have waited over a month to post this to make sure I solved my concern of dropped calls. I have had no dropped calls since making the changes in my ATA recommended by the user.

Anyone have some suggestions for a friend using a Grandstream 286 ATA.

Thanks again.

[volenin]

Hey, thanks for taking time to post back, Joe! So, now we know that those settings do change something... for more than 1 person . For the reference, the screenshots and instructions are here: http://forum.freephoneline.ca/viewtopic ... t=50#p5287. Thanks to brendany for pointing out the '$PING' setting.

Vlad

[beverly]

i didn't but $PING in my ATA setting (PAP2T)

[Yroc]

I experienced this problem for the first time today ... happened twice in a row. Have been using FPL for some time now.. nothing changed in my set up.

[Bloodsong]

Yeah I don't trust anything that happens today. I'd leave your setup be until we hear the final investigation report on the drive crash.

I mean, I suspect they're not doing anything too invasive that would cause micro-disconnects, but anything is possible. I'm sure they have a lot of log data to poll.

[FONGO_steve]

Yeah I don't trust anything that happens today. I'd leave your setup be until we hear the final investigation report on the drive crash.

I mean, I suspect they're not doing anything too invasive that would cause micro-disconnects, but anything is possible. I'm sure they have a lot of log data to poll.

Yeah, there still is a lot going on today, but I don't think it should be affecting any of you - just making my day a little more difficult.

Has anyone with dropped calls noticed any improvement since the new, bigger, drive was put in?

[volenin]

Has anyone with dropped calls noticed any improvement since the new, bigger, drive was put in?

Around what time was this done?.. I haven't seen any update on this one... Is this a recent change?

[FONGO_steve]

Has anyone with dropped calls noticed any improvement since the new, bigger, drive was put in?

Around what time was this done?.. I haven't seen any update on this one... Is this a recent change?

Yesterday between 4:30pm-9:30pm (Sorry I don't have a more specific time frame)

[etrain]

same here...dropping calls everytime i use it...i did the $PING and things are still the same...actually seemed to start dropping as soon as i paid for the config file

[beverly]

got a dropped call
161336665XX 161342253XX 15:51 2010-04-28 12:47:38.0 2010-04-28 13:03:29.0

[Joe B]

I guess I replied to soon, 2 dropped calls yesterday.... I guess I solved part of the problem, it doesn't seem to happen as often as before.

[smartoakville]

I guess I replied to soon, 2 dropped calls yesterday.... I guess I solved part of the problem, it doesn't seem to happen as often as before.

Its called coincidence.

[brddd]

Just adding to the "me too" list. I experience dropped calls using a SPA-2102. I am now trying the $PING setting for NAT Keep Alive Msg, and will see if that helps. Based on from what I have read here it likely won't fix the issue.

It can't be my ISP (Rogers) as everything works fine with my SPA-2102 using VBuzzer.

<sigh> Is there anything wrong with the server side?

[beverly]

happened twice so far today
just now

[brddd]

Just adding to the "me too" list. I experience dropped calls using a SPA-2102. I am now trying the $PING setting for NAT Keep Alive Msg, and will see if that helps. Based on from what I have read here it likely won't fix the issue.

It can't be my ISP (Rogers) as everything works fine with my SPA-2102 using VBuzzer.

<sigh> Is there anything wrong with the server side?

It still happens even with this configuration. I called a 613 number from a 647 fpl number and had no issues for a hour conversation. Then a 416 number it dropped the during the call.

[mokongo]

I'm experiencing dropped calls since I got FPL about 5 months ago, generally the service is ok except the dropped calls. I don't see many answers on this forum related to this, for people who need a reliable phone service I wouldn't recommend it, when you are talking to a government agency, a lawyer or a future employer you just can't have the call dropped, it just will put you on RED, big time!!

[smartoakville]

I'm experiencing dropped calls since I got FPL about 5 months ago, generally the service is ok except the dropped calls. I don't see many answers on this forum related to this, for people who need a reliable phone service I wouldn't recommend it, when you are talking to a government agency, a lawyer or a future employer you just can't have the call dropped, it just will put you on RED, big time!!

Agree 100%. I suspect FPL is just waiting for the issue to resolve itself, as we dont see an official position from the company regarding the issues. For the most part, its just members talking to other members trying to guess what might work, and since the issue is intermittent, some actions may give the false impression that they solved the problem, until it happens next time.

I already gave up. I've been with FPL for a while now and went from "an admirer who recommended the services to all friends and family" to a "disappointed client" who signed up for a more reliable service. I cannot afford to call Bell TV to complain about my satellite service, and after waiting 12 minutes on hold and another 18 speaking to someone, then the call is dropped for no reason. Like others mentioned here before, it seems like the most important calls are the ones that drop all the time (i know it is just coincidence).

Since I already paid for the config file, I got nothing to lose so the number is now my "recreational" phone number, but the service I use for my everyday needs is working flawlessly with the SAME ATA, SAME PROVIDER, SAME ROUTER.

[FONGO_kris]

My first point, is please do not advertise on this forum.

Secondly, I assure you were are anything BUT waiting for this to resolve itself, we have people frantically running around looking for reasons this can be happening. I've heard some rumblings and we're getting close. I'll update you all on Monday as soon as I can.

[beverly]

I'm very confident FPL will find an fix the problem sooner or later and we'll be on the next problem that arise's or the same problem but earlier dropped/static calls, but till then, they won't know till a bunch of us (beta testers) tell them when, what, who, where, setup, what and using ASAP, as it happen's. Someone is watching to find the solution someday, as cheaply as possible. The more people report the bigger the problem is..

But till then,

[FONGO_steve]

I'm very confident FPL will find an fix the problem sooner or later and we'll be on the next problem that arise's or the same problem but earlier dropped/static calls, but till then, they won't know till a bunch of us (beta testers) tell them when, what, who, where, setup, what and using ASAP, as it happen's. Someone is watching to find the solution someday, as cheaply as possible. The more people report the bigger the problem is..

But till then,

Although not directly related to call dropping - I spent my entire 8 hours at work on Friday working with a couple co-workers on something that may have a positive affect on this once figured out.

[njchan]

I'm trying the settings from this post ...

http://forum.freephoneline.ca/viewtopic ... t=50#p5287

hopefully it goes well ... will let you know. had 3 dropped calls last night. ;( all around the 17-19min mark.

[TSellers]

I just tried the settings suggested by volenin (thanks volenin for that).

One thing I ran across in another forum was the suggestion you set the NAT Keep alive to just under 60:

Since timeout intervals are in whole minute intervals (e.g. the 180 seconds that seems the be the most popular figure), wouldn't it make sense to set the keep-alive interval to just under a whole minute interval? (e.g. 175 seconds if time-out interval is 180 seconds).

I'd probably do 55 or 85 seconds - that way if a packet gets dropped, it has another chance to keep the port open. But, some routers don't require a reply so it may not matter.

Accordingly I set mine to 55.

[FONGO_steve]

I just tried the settings suggested by volenin (thanks volenin for that).

One thing I ran across in another forum was the suggestion you set the NAT Keep alive to just under 60:

Since timeout intervals are in whole minute intervals (e.g. the 180 seconds that seems the be the most popular figure), wouldn't it make sense to set the keep-alive interval to just under a whole minute interval? (e.g. 175 seconds if time-out interval is 180 seconds).

I'd probably do 55 or 85 seconds - that way if a packet gets dropped, it has another chance to keep the port open. But, some routers don't require a reply so it may not matter.

Accordingly I set mine to 55.

Try as low as 20 seconds
Our Grandstreams use a 20s interval and have significantly less problems than the Linksys' did in this regards

[beverly]

mine is set to 15