Re: [Astlinux-users] Do you have trunks that stop registering for some reason
> Am 10.04.2018 um 13:43 schrieb Michael Keuter : > >> >> Am 10.04.2018 um 13:37 schrieb Michael Knill >> : >> >> Here’s an interesting one as an FYI. >> >> I have one provider that I use (have to unfortunately) that requires >> registration. >> Very occasionally the trunk lost its registration and it could not receive >> incoming calls and I couldn't work it out. >> Recently I had this happen which affected all my trunks to this provider so >> I rang up the provider and found that their SBC cluster had failed over that >> evening due to a network issue. >> After doing some debugging, I found that Asterisk was not registering any >> more and would not start again until a reload was done. Why? >> >> Well I found this sip.conf parameter: >> register_retry_403 - This will cause Asterisk to treat 403 responses to >> registrations as if they were 401 responses and continue retrying according >> to normal retry rules. It is set to no by default e.g. it will stop trying >> to register if it gets a 403 – Forbidden ☹ >> >> I got the provider to do a debug from my IP Address after the failover and >> you guessed it, 403 – Forbidden was sent during the failover which I >> understand is during the settling period. >> I have now set this to yes and hopefully we don't have this issue again. >> >> Regards >> Michael Knill > > Thanks, that sounds interesting. > I will keep an eye on that, the next time I have registration issues. > > Michael Hi Michael, I found this related: https://community.freepbx.org/t/sip-trunk-turns-to-rejected-and-only-re-registers-after-a-reload/44552 Michael http://www.mksolutions.info -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] Do you have trunks that stop registering for some reason
> Am 10.04.2018 um 13:37 schrieb Michael Knill > : > > Here’s an interesting one as an FYI. > > I have one provider that I use (have to unfortunately) that requires > registration. > Very occasionally the trunk lost its registration and it could not receive > incoming calls and I couldn't work it out. > Recently I had this happen which affected all my trunks to this provider so I > rang up the provider and found that their SBC cluster had failed over that > evening due to a network issue. > After doing some debugging, I found that Asterisk was not registering any > more and would not start again until a reload was done. Why? > > Well I found this sip.conf parameter: > register_retry_403 - This will cause Asterisk to treat 403 responses to > registrations as if they were 401 responses and continue retrying according > to normal retry rules. It is set to no by default e.g. it will stop trying to > register if it gets a 403 – Forbidden ☹ > > I got the provider to do a debug from my IP Address after the failover and > you guessed it, 403 – Forbidden was sent during the failover which I > understand is during the settling period. > I have now set this to yes and hopefully we don't have this issue again. > > Regards > Michael Knill Thanks, that sounds interesting. I will keep an eye on that, the next time I have registration issues. Michael http://www.mksolutions.info -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
[Astlinux-users] Do you have trunks that stop registering for some reason
Here’s an interesting one as an FYI. I have one provider that I use (have to unfortunately) that requires registration. Very occasionally the trunk lost its registration and it could not receive incoming calls and I couldn't work it out. Recently I had this happen which affected all my trunks to this provider so I rang up the provider and found that their SBC cluster had failed over that evening due to a network issue. After doing some debugging, I found that Asterisk was not registering any more and would not start again until a reload was done. Why? Well I found this sip.conf parameter: register_retry_403 - This will cause Asterisk to treat 403 responses to registrations as if they were 401 responses and continue retrying according to normal retry rules. It is set to no by default e.g. it will stop trying to register if it gets a 403 – Forbidden ☹ I got the provider to do a debug from my IP Address after the failover and you guessed it, 403 – Forbidden was sent during the failover which I understand is during the settling period. I have now set this to yes and hopefully we don't have this issue again. Regards Michael Knill -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
