[Blink] Intermittent registration failures against Asterisk

Saúl Ibarra Corretgé saul at ag-projects.com
Fri Feb 11 00:41:29 CET 2011

Hi Ben,

On 02/11/2011 12:12 AM, Ben Klang wrote:
> Hello Blink,
> I have been using Blink for quite some time now with good success.
> Recently I've been having a problem with intermittent registration
> issues. The configuration of the client and the server have not changed.
> On one of the two affected machines I am using Blink Pro 1.0.0; on the
> other I am running Blink 0.23.1. The issue is the same on both versions.
> Asterisk is version
> To get around NAT issues I have my registration timer set to 60 seconds.
> The symptom is very reliable. On launching Blink I get a successful
> registration to Asterisk. About 1 minute later a message pops up on the
> screen saying: "The account verendusf80a822 at pbx-atlanta1.alkaloid.net
> <mailto:verendusf80a822 at pbx-atlanta1.alkaloid.net> could not be
> registered because of an authentication error". About 1 minute after
> that I get another good registration, followed by another failure, and
> so on, indefinitely.
> On the Asterisk console I noticed this message:
> [Feb 10 18:04:37] NOTICE[602]: chan_sip.c:13561 check_auth: Correct
> auth, but based on stale nonce received from '"Ben Klang"
> <sip:verendusf80a822 at pbx-atlanta1.alkaloid.net>;tag=qAD14GlpbUdopGR2n5W29g127MMZ3Psq'
> Note that the message is only visible when I turn on SIP debugging in
> Asterisk's console.
> Is this a bug in Blink or Asterisk?

The stale nonce means that authentication credentials were reused and 
the server rejects them. Could you please send us a the SIP trace when 
this occurs?


Saúl Ibarra Corretgé
AG Projects

More information about the Blink mailing list