[Asterisk-Users] 403 forbidden on SIP register

[snacktime]

> md5 instead of plaintext? 

Doesn't asterisk take care of this automatically with SIP?  I have
other providers that use md5 and they all respond with a 401 challenge
and then asterisk generates the md5 and uses the realm given it in the
401.

> Also, I think I just seen a change in the last day or two that had
> something to do with 403's, and if I recall correctly, it also addressed
> upper/lower case something or another.
> 
> Can you use ethereal or sip debug to determine the exact item that was
> sent that might be causing the 403? Either one should at least provide
> a hint.

Here is a sip debug.  All I get back is an immediate 403 forbidden. 
This is also what I get back on other providers if I had the wrong
password.

This is also cvs HEAD from yesterday, although jumping back to a
version from  a month ago didn't make any difference.

Chris


--- (10 headers 0 lines)---
Jun 21 15:42:52 NOTICE[34281]: chan_sip.c:4671 sip_reregister:    --
Re-registration for  snacktime at voip-co1.teliax.com
REGISTER 11 headers, 0 lines
REGISTER attempt 1 to snacktime at voip-co1.teliax.com
Reliably Transmitting (no NAT) to 208.139.204.228:5060:
REGISTER sip:voip-co1.teliax.com SIP/2.0
Via: SIP/2.0/UDP 69.25.136.31:5060;branch=z9hG4bK027fe0e3
From: <sip:snacktime at voip-co1.teliax.com>;tag=as737624ba
To: <sip:snacktime at voip-co1.teliax.com>
Call-ID: 65238eaa016b6ec6343589e426eff283 at 69.25.136.31
CSeq: 102 REGISTER
User-Agent: Asterisk PBX
Expires: 120
Contact: <sip:teliax at 69.25.136.31>
Event: registration
Content-Length: 0


<-- SIP read from 208.139.204.228:5060: 
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 69.25.136.31:5060;branch=z9hG4bK027fe0e3
From: <sip:snacktime at voip-co1.teliax.com>;tag=as737624ba
To: <sip:snacktime at voip-co1.teliax.com>;tag=as3201eb44
Call-ID: 65238eaa016b6ec6343589e426eff283 at 69.25.136.31
CSeq: 102 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY
Contact: <sip:snacktime at 208.139.204.228>
Content-Length: 0