On 07/03/14 22:43, Juha Heinanen wrote:
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.
It is a fix of extracting the proper authentication username, otherwise the value of the user field for authentication is 'sip:xyz...', which is clear an invalid sip username format.
Cheers, Daniel