[Spce-user] Troubleshooting an asterisk server that keeps losing registration.

[Daniel Grotti]

Thanks Metthew!
Didn't remember that :)

Daniel

On 1 Nov 2014 10:51, Matthew Ogden <matthew at tenacit.net> wrote:
>
> Hi Danel & Kalen 
>
> Is this not the same issue I had? Mine was because it's using a stale 
> nonce - which NGCP rejects. Basically if you send to many 401s or 407s the 
> LB will ban it with a 403. 
> So we were seeing a lot of asterisk boxes give up (and ours was an appliance 
> that cannot retry automatically after 403) 
>
> You can stop spce from blocking stale nonce registrations.  See this thread: 
> http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html 
>
> Daniel's suggestion was to add the P-NGCP-Stale header in the proxy, and 
> then make the LB only do a 401 if it wasn't present. 
>
> It saved me from a LOT of headaches. 
>
> Thanks again! 
>
>
> -----Original Message----- 
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of 
> Daniel Grotti 
> Sent: 01 November 2014 10:57 AM 
> To: Kalen Krueger 
> Cc: spce-user at lists.sipwise.com 
> Subject: Re: [Spce-user] Troubleshooting an asterisk server that keeps 
> losing registration. 
>
> Mmm...yes this is well know issue of asterisk. 
> But spce should send 403 only when a user is blocked. 
> Don't get the scenario when PBX get 403 during a normal registration. 
>
> In the worst case you can change the 403 reply on spce. But only of you 
> really need. This is an asterisk issue. 
>
> Daniel 
>
> On 1 Nov 2014 09:12, Kalen Krueger <kalen at npinfo.com> wrote: 
> > 
> > Upon further review it appears that we’re getting this error out of the 
> > blue…. 
> > 
> > 
> > 
> > 
> > 
> > Then based on the “Forbidden” (I’m assuming 403 error), it stops trying 
> > until we force it to. 
> > 
> > 
> > 
> > I’ve added the new option available in the PBX configuration to see if 
> > this helps, but I’m just wondering why this would happen out of the blue? 
> > 
> > 
> > 
> > register_retry_403=yes 
> > 
> > ; Treat 403 responses to registrations as if they were 
> > 
> >                               ; 401 responses and continue retrying 
> > according to normal 
> > 
> >                               ; retry rules. 
> > 
> > 
> > 
> > Kalen Krueger 
> > Technical and Project Manager 
> > NP Information Systems 
> > www.npinfo.com 
> > 
> > kalen at npinfo.com 
> > desk:  (253) 479-1321 
> > office: (253) 852-1543 
> > mobile: (206) 963-1309 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of 
> > Kalen Krueger 
> > Sent: Friday, October 31, 2014 4:00 PM 
> > To: spce-user at lists.sipwise.com 
> > Subject: [Spce-user] Troubleshooting an asterisk server that keeps losing 
> > registration. 
> > 
> > 
> > 
> > We’ve got one particular PBX we’re having a problem with.     At seemingly 
> > random intervals sip:wise thinks it’s lost registration, while the PBX 
> > still thinks it’s registered.  Therefore sip:wise forwards the calls to 
> > the caller wave have listed in “Call Forward Unavailable”. 
> > 
> > 
> > 
> > We’ve been working on this for several weeks… trying different things… and 
> > I need to reach out for some guidance.   What information can provide to 
> > the community that would helpful? 
> > 
> > 
> > 
> > We’re running mr3.4.2 and the subscriber is FreePBX 2.11.0.37. 
> > 
> > 
> > 
> > Here’s a screenshot (some info scrubbed) of our trunk setup in FreePBX, 
> > and the registration in sip:wise… in case we have something obviously 
> > wrong.    I’m happy to collect tsharks, etc. to assist…. Just feel at this 
> > point like I’m running in circles. 
> > 
> > 
> > 
> > Thanks ahead of time for any guidance. 
> > 
> > 
> > 
> > 
> > 
> > Kalen Krueger 
> > Technical and Project Manager 
> > NP Information Systems 
> > www.npinfo.com 
> > 
> > kalen at npinfo.com 
> > desk:  (253) 479-1321 
> > office: (253) 852-1543 
> > mobile: (206) 963-1309 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > ________________________________ 
> > 
> > 
> > This email and any files transmitted with it are confidential and intended 
> > solely for the use of the individual or entity to whom they are addressed. 
> > If you have received this email in error please notify the system manager. 
> > Please note that any views or opinions presented in this email are solely 
> > those of the author and do not necessarily represent those of the company. 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user