My daughter and I have FPL numbers both managed by the same Asterisk instance. Mostly it works fine though frequently inbound calls go directly to FPL voicemail. Also, sometimes daily, there is some glip on the internets and Asterisk tries to reconnect with the FPL server. This NEVER goes well and by the time we realize this Asterisk has tried *thousands* of times to reconnect. Often one of will get a cell call asking what's broken again with the home number going to voicemail. My wife uses a different VOIP provider and we never see a problem with her line.
In the Asterisk logs you will see this *many* times when the FPL death loop is engaged...
Code: Select all
[2014-03-23 14:00:06] NOTICE[5519] chan_sip.c: -- Registration for '1*********5@voip.freephoneline.ca' timed out, trying again (Attempt #5)
[2014-03-23 14:00:06] VERBOSE[5519] chan_sip.c: -- Got SIP response 486 "Too many requests" back from xxx.xxx.xxx.xxx:5060
[2014-03-23 14:00:07] NOTICE[5519] chan_sip.c: -- Registration for '1*********8@voip.freephoneline.ca' timed out, trying again (Attempt #5)
[2014-03-23 14:00:07] VERBOSE[5519] chan_sip.c: -- Got SIP response 486 "Too many requests" back from xxx.xxx.xxx.xxx:5060
I have tried the settings described here
http://forum.fongo.com/viewtopic.php?f=15&t=9456 but it really does not make a difference. Once in the retry loop it's there until someone configures the FPL trunks off for a while. My guess is that this re-registration block is just a simple minded timer and I understand that y'all are trying to prevent constant unnecessary re-registrations but maybe a bit of smarts could be put into it to allow for internet disruptions that cause a user to re-register early. I expect that this issue also causes others to miss incoming call and not realize it.
Any suggestion about how to configure Asterisk/FreePBX around this FPL issue? Right now my work-around is to use a pay-as-you-go VOIP provider to handle calls when the FPL connections are broken rather than buying FPL credits because it is dependable.
M
