[sr-dev] UAC Issue

[Bernhard Suttner]

Hi,

some more informations I got during testing:

1. if I dont set l_uuid and set reg_contact_addr to "ip-addr" then I get a Contact like: "@ip-addr".
2. if I dont set l_uuid and set reg_contact_addr to "user at ip-addr" then I get a Contact like "user at ip-addr"
3. if I set l_uuid and set reg_contact_addr to "ip-addr" then I get a Contact like "l_uuid at ip-addr". 
4. if I set l_uuid and set reg_contact_addr to "user at ip-addr" then I get a Contact like "l_uuid at user@ip-addr".

Thanks!

Best regards,
Bernhard


-----Ursprüngliche Nachricht-----
Von: Daniel-Constantin Mierla [mailto:miconda at gmail.com] 
Gesendet: Freitag, 3. Dezember 2010 10:35
An: Bernhard Suttner
Cc: sr-dev at lists.sip-router.org
Betreff: Re: [sr-dev] UAC Issue

Hello,

On 12/3/10 10:24 AM, Bernhard Suttner wrote:
> Hi,
>
> I am using UAC to register to an outbound provider. Kamailio (3.1.0) does send the following REGISTER:
>
> E..'A... at .=...P...P9......\1REGISTER sip:172.16.0.57 SIP/2.0
> Via: SIP/2.0/UDP 172.16.0.130;branch=z9hG4bKa69c.50411006.0
> To: sip:SIP001 at 172.16.0.57
> From: sip:SIP001 at 172.16.0.57;tag=533cb9e91f4b999cf76861cbb9ed54ed-c10d
> CSeq: 10 REGISTER
> Call-ID: 7bad8cfd-13535 at 127.0.0.1
> Content-Length: 0
> User-Agent: kamailio (3.1.0 (i386/linux))
> Contact:<sip:@172.16.0.130>
> Expires: 600
> Authorization: Digest username="SIP001", realm="asterisk", nonce="1be9f4f2", uri="sip:172.16.0.57", response="e46d865eb495e170fdef058b857d7b76", algorithm=MD5
>
> I am not really 100% sure, but I think the Contact address is not valid. Within the database I have only set the host part. I think the Contact should be the following then:
>   Contact:<sip:172.16.0.130)
>
> (without the @).
this is wrong, indeed. The username in database was somehow supposed not 
to be empty, because should be the ID of a local user. I will fix it.

> In addition, I think the Call-ID could be better. I know, that it is valid to set it like that, but the IP Address 127.0.0.1 could be misunderstood somewhere.
>
It shouldn't be at all misunderstood, Call-ID must be just a unique 
token, with no meaning to routing or something else.

Thanks,
Daniel

-- 
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com