Darkmatter wrote:The only thing is that there was no power outage.
I've just re-read your first post again. I was extremely tired when I responded initially.
https://www.voipmechanic.com/sip-basics.htm
If all calls start dropping after a certain interval (32 seconds is common), like clockwork, that's almost always SIP ALG related.
200 OK is sent to your ATA by FPL. Your ATA is supposed to send ACK (acknowledge) back. If ACK is not received by FPL's server, then
FPL eventually stops waiting for ACK and replies with BYE (possibly around 32 seconds), ending the call. SIP signalling can be completely broken by faulty SIP ALG features in routers or
modem/router combos. SIP ALG features in many routers (but not all) often modify SIP headers, incorrectly:
https://www.voicehost.co.uk/help/sip-al ... our-router.
I'm not sure whether receiving a BYE after 32 seconds (or whatever the interval is for you) should produce a 480 SIP error code by the ATA if ACK is never received by FPL.
That doesn't seem normal to me. And I'm not positive whether that error could be caused by a SIP ALG issue, but when you mentioned the short duration call drop that's the first thing that went through my mind.
https://www.ietf.org/rfc/rfc3261.txt (page 188)
480 Temporarily Unavailable
The callee's end system was contacted successfully but the callee is
currently unavailable (for example, is not logged in, logged in but
in a state that precludes communication with the callee, or has
activated the "do not disturb" feature). The response MAY indicate a
better time to call in the Retry-After header field. The user could
also be available elsewhere (unbeknownst to this server). The reason
phrase SHOULD indicate a more precise cause as to why the callee is
unavailable. This value SHOULD be settable by the UA. Status 486
(Busy Here) MAY be used to more precisely indicate a particular
reason for the call failure.
This status is also returned by a redirect or proxy server that
recognizes the user identified by the Request-URI, but does not
currently have a valid forwarding location for that user.
480 SIP errors are also caused by capacity issues. FPL offers a maximum of 2 channels (you can have a maximum of two concurrent calls) per account. With some service providers, trying to exceed that 2 channel limit produces that 480 error. Possibly trying to register your FPL account with another device or SIP app simultaneously could cause that 480 SIP error. Only one registration per FPL account is allowed at any time. When there are multiple devices/softphones using the same account, only the most recent registration is valid. The previous device will lose registration (despite the ATA's registration status). In other words people sharing their FPL accounts or otherwise trying to register their FPL accounts with smartphone SIP apps/desktop apps while simultaneously using the same FPL account on their ATAs are out of luck.
http://www.dslreports.com/forum/r28918051- (At that link you'll see the 480 error with FPL).
When I've encountered SIP error 480, with other services, it's before the call is connected though (whereas, for you, the call is in progress). So, I am a bit puzzled by you receiving the 480 error with the call already in progress.
I actually do have SIP ALG enabled. I know it isn't recommended for most modem/routers due to improper implementation but without it on to prioritize traffic
That's not how SIP ALG works. That's how QoS works. SIP ALG, by itself, does not prioritize anything and certainly can not affect whether your voice starts sounding choppy or cutting out (that's related to upload bandwidth/upload usage on your LAN or an issue with your ISP).
Whatever happened with your voice not being choppy after enabling SIP ALG was coincidental.
This is what Obihai says about resolving choppy audio:
https://www.obitalk.com/info/faq/Troubl ... ing-choppy
(reducing TX and RX gain is unlikely to resolve the specific issue you were having).
Page 45 from the PDF guide explains how to start troubleshooting choppy audio:
http://forum.fongo.com/viewtopic.php?f= ... 805#p73839.
Regardless, there's enough evidence to suggest other Arris modem/router combos with SIP ALG enabled cause issues for other service providers:
https://kb.intermedia.net/article/3344. Although SIP ALG may not be the root of the problem here, doing to steps below doesn't hurt anything.
so that would be about 6 months with SIP ALG turned on.
Couple of points:
1. SIP ALG isn't faulty in all routers.
2. SIP ALG's behavior could change, in particular after device firmware updates that could be pushed to your Arris device without your knowledge.
A. Read pages 9 and 10 from the PDF guide:
http://forum.fongo.com/viewtopic.php?f= ... 805#p73839.
B. On page 43, do steps 1 (only if you're going to use your own router), 2,3,4,5, and 9.
Steps 4 and 5 should be done, regardless (that's the proper way to configure the ATA for FPL).
Step 9, in particular, should be done when dealing with buggy SIP ALG features in routers. voip4.freephoneline.ca:6060 exists due to SIP ALG. Even if SIP ALG isn't the problem,
doing steps 4, 5, and 9 won't hurt anything (4 and 5 should be done, regardless).
Should you discover that your issue only occurs when calling your mother's phone number, then submit a ticket:
http://forum.fongo.com/viewtopic.php?f= ... 587#p75585.