[Asterisk-Users] Sipura 401 Unauthorized.

[Forrest W. Christian]

I'm having ongoing registration fits with some SPA-2000's.

Right now I have one which, based on the debugging output repeatedly fails
with "401 unauthorized":

-----------------
<-- SIP read from 206.127.114.240:5060:
REGISTER sip:voip-proxy.mt.net SIP/2.0
Via: SIP/2.0/UDP 206.127.114.240:50291;branch=z9hG4bK-f4e3f6bc
From: MIC Sipura User
<sip:A0975L1 at voip-proxy.mt.net>;tag=abf0b0fbea0a3e68o0
To: MIC Sipura User <sip:A0975L1 at voip-proxy.mt.net>
Call-ID: 2bdd7787-446b494c at 192.168.1.201
CSeq: 52 REGISTER
Max-Forwards: 70
Contact: MIC Sipura User <sip:A0975L1 at 206.127.114.240:50291>;expires=60
User-Agent: Sipura/Sipura/SPA2000-2.0.13(g)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura


--- (12 headers 0 lines)---
Using latest request as basis request
Sending to 206.127.114.240 : 50291 (NAT)
Transmitting (NAT) to 206.127.114.240:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
206.127.114.240:50291;branch=z9hG4bK-f4e3f6bc;received=206.127.114.240;rport=5060
From: MIC Sipura User
<sip:A0975L1 at voip-proxy.mt.net>;tag=abf0b0fbea0a3e68o0
To: MIC Sipura User <sip:A0975L1 at voip-proxy.mt.net>
Call-ID: 2bdd7787-446b494c at 192.168.1.201
CSeq: 52 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:A0975L1 at 206.127.64.144>
Content-Length: 0


---
Transmitting (NAT) to 206.127.114.240:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
206.127.114.240:50291;branch=z9hG4bK-f4e3f6bc;received=206.127.114.240;rport=5060
From: MIC Sipura User
<sip:A0975L1 at voip-proxy.mt.net>;tag=abf0b0fbea0a3e68o0
To: MIC Sipura User <sip:A0975L1 at voip-proxy.mt.net>;tag=as3bb6fc64
Call-ID: 2bdd7787-446b494c at 192.168.1.201
CSeq: 52 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:A0975L1 at 206.127.64.144>
WWW-Authenticate: Digest realm="asterisk", nonce="36609d12"
Content-Length: 0
-------------------------



This box will register and then be ok for several days and then will go
into this mode.  I've seen other sipuras doing something similar but with
407.  In fact, calls were made with this box yesterday with absolutely no
configuration changes on either end, until I started to try to figure out
why it isn't registering.

With only 5-6 SPA-2000's in test and several of them acting flaky
registration-wise I'm feeling that I'm missing something which causes this
flakiness.

Both the SPA and asterisk have been rebooted.  Asterisk has actually been
updated to the latest CVS version today in case there was an
already-in-cvs fix.

The config I have in asterisk for this sipura box is:

[A0974L1]
type=friend
host=dynamic
context=cosinternational
secret=<REMOVED>
callerid="MIC Sipura User" <406#######>
dtmfmode=rfc2833
reinvite=no
canreinvite=no
nat=yes
qualify=no

Ideas?  Other places I should look?

-forrest