Daniel-Constantin Mierla writes:
Some devices uses user@domain for username part of the
authorization
header, which I guess is not allowed as well. But we support it for long
time, the reason of having ha1 and ha1b in subscriber table. Now I
discovered that some snom puts even sip: in front of usern@domain when
doing xcap operations. So it is just a safety check, skipping the scheme
if it is, otherwise authentication fails. The parser in that part is not
a full uri parser, it uses char find.
so it looks to me that this commit to 4.1 didn't fix any bug in kamailio,
but was an enhancement (= new feature) and thus the commit should not
have been made.
-- juha