< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate] Register challenged with 407, why not 401?


We noticed at SIPit that a number of UACs did not cope with having their REGISTER challenged with 407 Proxy-authenticate, but instead expected 401 Unauthorised.

 

Dum/ServerAuthmanager.cxx seems to have 407 hard-coded …

 

Does anyone have any strong feelings as to why this is the case? Should we really be sending a 401 when not acting as a proxy?  (Our app is a B2BUA).


Thanks,

 

Steve Coule


Envox UK Ltd