[Serusers] usrloc and replication

Marian Dumitru marian.dumitru at voice-sistem.ro
Sat Mar 26 18:33:48 CET 2005


Matt,

The replication value must be 0 (and it's not a timeout value) in memory 
and DB. If you get a non-Null value for a registered contact, it means 
somewhere is a problem.
I'm not aware of any documentation about this..... just the code :-).

Best regards,
Marian

Matt Schulte wrote:
> Ok, it's starting to make a little more sense. I didn't force anything
> by hand, the replication flag (in db) is a much higher number than the
> other usrloc replication flags though. Is this format unixtime? Is there
> any documentation on this subject? I have yet to find any definitive.
> 
> Like I said before I didn't force any replication values, I thought that
> was all automatic. :)
> 
> Thanks for your patience, I just wish this was documented a little more
> :-(
> 
> 	Matt
> 
> -----Original Message-----
> From: Marian Dumitru [mailto:marian.dumitru at voice-sistem.ro] 
> Sent: Saturday, March 26, 2005 11:05 AM
> To: Matt Schulte
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] usrloc and replication
> 
> 
> Matt,
> 
> You get the message you mentioned "Keeping binding....."  *only* if the 
> contact is marked for replication. You can check this either in DB 
> column replication, either into memory via "serctl ul show".
> 
> As in code the replication flag is hardcoded to 0 (disabled), I would 
> say you inserted via fifo some contacts with replication value != 0. Or
> ???
> 
> If so, I'm not sure if usrloc will ever remove the contact if the 
> replication flag is still set.
> 
> Best regards,
> Marian
> 
> Matt Schulte wrote:
> 
>>Thanks for the reponse, I gathered that much. My question is how long 
>>before the contact gets "removed"? It's late morning now and it's 
>>still there :-)
>>
>>-----Original Message-----
>>From: Marian Dumitru [mailto:marian.dumitru at voice-sistem.ro]
>>Sent: Saturday, March 26, 2005 5:37 AM
>>To: Matt Schulte
>>Cc: serusers at lists.iptel.org
>>Subject: Re: [Serusers] usrloc and replication
>>
>>
>>Hi Matt,
>>
>>After expiration an before being removed, the contact are still kept 
>>in
>>ZOMBIE state - you can see the state in DB changes.
>>
>>Best regards,
>>Marian
>>
>>Matt Schulte wrote:
>>
>>
>>>Ok, I'm using usrloc db_mode 2, I understand the timer checks every 60
>>
>>
>>>seconds default to see who should be expired and all. What I don't
>>>understand is why I keep getting these messages:
>>>
>>>Keeping binding '+13142664004','sip:s at 69.29.57.253:3105' for
>>>replication
>>>
>>>This contact expired nonetheless and should be removed, is there
>>>something I'm missing?
>>>
>>>+--------------+--------------------------------------+---------------
>>>+--------------+--------------------------------------+--
>>>----+
>>>| username     | contact                              | expires
>>>|
>>>+--------------+--------------------------------------+---------------
>>>+--------------+--------------------------------------+--
>>>----+
>>>| +13142664004 | sip:s at 69.29.57.253:3105              | 2005-03-26
>>>00:42:35 |
>>>| +13142664004 | sip:s at 69.29.57.253:3118              | 2005-03-26
>>>01:24:58 |
>>>+--------------+--------------------------------------+---------------
>>>+--------------+--------------------------------------+--
>>>----+
>>
>>
>>
> 
> 


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




More information about the sr-users mailing list