ag at ag-projects.com
Sat Jun 23 09:09:15 CEST 2012
There is no good reason to expose your authentication username part into a temporary network address that only the SIP registrar function needs to know about. This breaks privacy when it desired, and exposes the host to fraud or denial of service attacks. Secondly, in multi account environment like Blink, each account needs a different and unique Contact Address so that when a session request comes in, Blink knows which account has been called.
The way we do it in Blink is technically correct and is best practice to use random string in the username part of a Contact Address, read SIP protocol specification to understand why this is done like this in more detail.
On Jun 23, 2012, at 6:37 AM, Boris Srostlik wrote:
> I noticed, while checking the status, that the registration generate
> random id every time you start the client.
> ie : "<sip:wtgikchm at 192.168.1.5:61783>"
> I was wondering if there is anywhere option to use the real sip id and
> not the random generated string 8 characters long.
> REGISTER 1555<sip:wtgikchm at 192.168.1.5:61783>
> (udp:192.168.1.5:61783)Blink Lite 1.6.2
> PAP2 :
> REGISTER 1555<sip:1555 at 192.168.1.3:8062>;expires=3600
> Blink mailing list
> Blink at lists.ag-projects.com
More information about the Blink