30 Dec
2008
30 Dec
'08
1:32 p.m.
This is because the ua sends it's registration refresh unauthenticated. The registrar will then push back an authentication challenge request so the ua can prove its identity, at which point the ua then repeats the same transaction, but with authentication credentials attached.
Why does it do that? Every time I do a debug, I see the first request denied as unauthorized and then it always comes right back and gets registered ok. Is it part of the SIP spec to try unauthenticated first? I would think you could set something on the UA to cut out the extra traffic.