[Serusers] http / https in Userloc db

[Marian Dumitru]

Hi Martin,

As far as I know it could be one of the new SNOM specific feature - it 
advertise the http location of the web configuration page. But if recall 
correctly, the header name should by WWW-Contact, not Contact.

Anyhow, it will be a good idea for register to check the contact 
validity before inserting into usrloc.

Best regards,
Marian

Martin Koenig wrote:
> Here is the according REGISTER request:
> 
> REGISTER sip:toplink-voice.de SIP/2.0.
> Via: SIP/2.0/UDP 192.168.0.206:2051;branch=z9hG4bK-nl2lqphgqhwx;rport.
> From: "Toplink" <sip:D1089081000 at toplink-voice.de>;tag=tcxf5l3ttk.
> To: "Toplink" <sip:D1089081000 at toplink-voice.de>.
> Call-ID: 3c267009b239-jdcz81xdwoag at snom360.
> CSeq: 549 REGISTER.
> Max-Forwards: 70.
> Contact: 
> <sip:D1089081000 at 192.168.0.206:2051;line=syp6dded>;q=1.0;+sip.instance="<urn:uuid:fd0d970e-34fc-48aa-8007-4a9c64a1231a>";audio;mobility="fixed";duplex="full";description="snom360";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO". 
> 
> Contact: <http://192.168.0.206:80>.
> Contact: <https://192.168.0.206:443>
> User-Agent: snom360-3.57t.
> P-NAT-Refresh: 15;method="crlf,stun".
> Supported: gruu.
> Allow-Events: dialog.
> X-Real-IP: 192.168.0.206.
> Authorization: Digest 
> username="xxx",realm="toplink-voice.de",nonce="xxx",uri="sip:toplink-voice.de",qop=auth,nc=00000001,cnonce="xxx",response="xxx",algorithm=md5. 
> 
> Expires: 3600.
> Content-Length: 0.
> .
> 
> See the strange Contact Header field. This is probably a Bug in the SNOM 
> hardphone. Nevertheless, the contacts should not end up in UserLoc?
> 
> Regards,
> Martin
> 
> 
> Martin Koenig schrieb:
> 
>> Hello,
>>
>> how can something like this happen:
>>
>> ~~~Contact(0x422be558)~~~
>> domain    : 'location'
>> aor       : 'd1089081000'
>> Contact   : 'http://192.168.0.206:80'
>> Expires   : 2981
>> q         :       0.00
>> Call-ID   : '3c267009b239-jdcz81xdwoag at snom360'
>> CSeq      : 547
>> replic    : 0
>> User-Agent: 'snom360-3.57t'
>> State     : CS_NEW
>> Flags     : 1
>> next      : 0x422c04d0
>> prev      : 0x422bf330
>> ~~~/Contact~~~~
>> ~~~Contact(0x422c04d0)~~~
>> domain    : 'location'
>> aor       : 'd1089081000'
>> Contact   : 'https://192.168.0.206:443'
>> Expires   : 2981
>> q         :       0.00
>> Call-ID   : '3c267009b239-jdcz81xdwoag at snom360'
>> CSeq      : 547
>> replic    : 0
>> User-Agent: 'snom360-3.57t'
>> State     : CS_NEW
>> Flags     : 1
>> next      : (nil)
>> prev      : 0x422be558
>> ~~~/Contact~~~~
>>
>> HTTP/HTTPS contacts in userloc? Causes the following error, besides 
>> that calls to that contact will probably fail:
>>
>> Mar  1 15:51:23 s-p1 /usr/local/sbin/ser[1716]: ERROR: parse_uri: bad 
>> uri,  state 0 parsed: <http> (4) / <http://192.168.0.206:80> (23)
>> Mar  1 15:51:23 s-p1 /usr/local/sbin/ser[1716]: error: 
>> mediaproxy/pingClients(): can't parse contact uri
>> Mar  1 15:51:23 s-p1 /usr/local/sbin/ser[1716]: ERROR: parse_uri: bad 
>> uri,  state 0 parsed: <http> (4) / <https://192.168.0.206:443> (25)
>> Mar  1 15:51:23 s-p1 /usr/local/sbin/ser[1716]: error: 
>> mediaproxy/pingClients(): can't parse contact uri
>>
>> How can this uri get into Usrloc in the first place?
>>
>> With best regards,
>> Martin
>>

-- 
Voice System
http://www.voice-system.ro