[Spce-user] multiple identical active Registrations

Jon Bonilla (Manwe) jbonilla at sipwise.com
Mon Jun 24 06:39:56 EDT 2013


El Mon, 24 Jun 2013 12:03:10 +0200
Thilo Bangert <thilo.bangert at gmail.com> escribió:

> On Monday, June 24, 2013 11:49:03 AM Jon Bonilla wrote:
> > El Thu, 13 Jun 2013 13:28:22 +0200
> > 
> > Theo <axessofficetheo at gmail.com> escribió:
> > > Hi
> > > 
> > > Just to chime in - in my case, running that command I get:
> > > 
> > > 
> > > Contact:: <sip:tri1 at 192.168.0.249:3799
> > > ;transport=udp;line=zaa5d7>;q=;expires=58;flags=0x0;cflags=0xC0;socket=<ud
> > > p: 127.0.0.1:5062>;methods=0xFFFFFFFF;received=<sip:10.206.10.142:3799> 
> > > >;user_agent=<snom-m9/9.6.2-a>;path=<<sip:lb at 127.0.0.1
> > > 
> > > ;lr;received='sip:10.206.10.142:3799';socket='sip:xxx.xx.xxx.xxx:5060'>
> > 
> > multiple db contacts have been reported before. These are almost impossible
> > to reproduce. I think it might be related to bad IO servers acording to the
> > past reports.
> > 
> > I'd like to have access to a server with this problem but never had it :(
> 
> i havent had this issue yet, but one that may be related. 
> 
> i had a subscriber which i gave a static registration, but which then itself 
> also registered with the spce with the same contact. i was expecting to see 
> two registrations (the static one and the dynamic one), but the result was 
> that you only see one registration (the one from the device) but when i tried 
> to delete it, it wouldnt disappear. 
> 
> i checked the database and there i could also only see one registration,
> which i then delete manually.
> 
> not a real issue for us, but wanted to chime in, hoping it might help you...
> 

Seen this before in a customer. The result was that the registration was
overwriting the permanent contact (which is a fake register with no expires)
and the contact was being lost because the new register had expiration.

Result: The client was seeing that the permanent contact was erased once per
day :) You case is a bit different as not being able to delete it also shows a
discrepancy between kamailio and mysql. But this is not the same case.

It's unrelated I think . What we see here is the same registration introduced
multiple times in mysql. Need to check why as kamailio keeps it in mem only
once.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130624/09015da8/attachment-0001.asc>


More information about the Spce-user mailing list