[OpenSIPS-Users] Registrations from different ports?

[David Cunningham]

Hi,

We've got an issue with some SNOM phones that use a different port
every time they renew their registration, and this is causing us to
have lots of entries in our 'location' table for that phone.
Is there any way for us to know that it's the same phone - maybe using
the sip.instance information?

Here's a trace from the phones point of view. Thank you in advance!


REGISTER sip:foo.com SIP/2.0
Via: SIP/2.0/TCP yy.yy.yy.yy:3780;branch=z9hG4bK-9zds9w1n5a74;rport
From: "User" <sip:2852262 at foo.com>;tag=pnri1ju4h7
To: "User" <sip:2852262 at foo.com>
Call-ID: 3270263c6643-7rizdqvsj15t
CSeq: 32 REGISTER
Max-Forwards: 70
Contact: <sip:2852262 at yy.yy.yy.yy:3780;transport=tcp;line=o7erzloh>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:7effe79a-0c74-4fd5-90a4-a42cfa13d0cc>"
User-Agent: snom870/8.3.6
Supported: gruu
Allow-Events: dialog
X-Real-IP: yy.yy.yy.yy
Authorization: Digest
username="2852262",realm="foo.com",nonce="4c1fdc2000000e9e8bc9c948cf44afc00f6661e6706c532d",uri="sip:foo.com",response="c6c2fa947289428cf134afdc1ea4b92f",algorithm=MD5
Expires: 3600
Content-Length: 0

Received from tcp:xx.xx.xx.xx:5060 at 21/6/2010 23:38:59:484 (2601 bytes):

SIP/2.0 200 OK
Via: SIP/2.0/TCP yy.yy.yy.yy:3780;branch=z9hG4bK-9zds9w1n5a74;rport=3780
From: "User" <sip:2852262 at foo.com>;tag=pnri1ju4h7
To: "User" <sip:2852262 at foo.com>;tag=75e36b5e47a93c5980f0d1922a187c43.b730
Call-ID: 3270263c6643-7rizdqvsj15t
CSeq: 32 REGISTER
Contact: <sip:2852262 at yy.yy.yy.yy:3780;transport=tcp;line=o7erzloh>;q=1;expires=3600;received="sip:yy.yy.yy.yy:3780;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3485;transport=tcp;line=o7erzloh>;q=1;expires=3420;received="sip:yy.yy.yy.yy:3485;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3484;transport=tcp;line=o7erzloh>;q=1;expires=3243;received="sip:yy.yy.yy.yy:3484;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4022;transport=tcp;line=o7erzloh>;q=1;expires=3043;received="sip:yy.yy.yy.yy:4022;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3904;transport=tcp;line=o7erzloh>;q=1;expires=2860;received="sip:yy.yy.yy.yy:3904;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3903;transport=tcp;line=o7erzloh>;q=1;expires=2655;received="sip:yy.yy.yy.yy:3903;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4727;transport=tcp;line=o7erzloh>;q=1;expires=2470;received="sip:yy.yy.yy.yy:4727;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4407;transport=tcp;line=o7erzloh>;q=1;expires=2257;received="sip:yy.yy.yy.yy:4407;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4406;transport=tcp;line=o7erzloh>;q=1;expires=2074;received="sip:yy.yy.yy.yy:4406;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3601;transport=tcp;line=o7erzloh>;q=1;expires=1866;received="sip:yy.yy.yy.yy:3601;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4940;transport=tcp;line=o7erzloh>;q=1;expires=1648;received="sip:yy.yy.yy.yy:4940;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4299;transport=tcp;line=o7erzloh>;q=1;expires=1439;received="sip:yy.yy.yy.yy:4299;transport=TCP",
<sip:2852262 at zz.zz.zz.zz:53961;rinstance=1f160dbed959f34c;transport=TCP>;expires=1278;received="sip:zz.zz.zz.zz:53961;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3280;transport=tcp;line=utx6owpw>;q=1;expires=706;received="sip:yy.yy.yy.yy:3280;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:4724;transport=tcp;line=7z54agaq>;q=1;expires=401;received="sip:yy.yy.yy.yy:4724;transport=TCP",
<sip:2852262 at yy.yy.yy.yy:3311;transport=tcp;line=7z54agaq>;q=1;expires=182;received="sip:yy.yy.yy.yy:3311;transport=TCP"
Server: Telviva SIP proxy
Content-Length: 0
Warning: 392 xx.xx.xx.xx:5060 "Noisy feedback tells: pid=5271
req_src_ip=yy.yy.yy.yy req_src_port=3780 in_uri=sip:foo.com
out_uri=sip:foo.com via_cnt==1"


-- 
David Cunningham, Voisonics
http://voisonics.com/
US toll-free: +1 888 842 2720
UK: +44 (0) 20 3298 1642
Australia: +61 (0) 2 9037 2180