< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] FW: Registar behaviour


Thank you for your answers!
Others questions...

1/ What does the Resiprocate stack/DUM do when the registration timeout expires?
Does the stack remove the contact from the database 
(InMemoryRegistrationDatabase)?

2/ Could the application ask the stack/DUM to unregister a client?
If yes, what's happened? Is there a REGISTER message sent to the UA?
Does the contact is removed from the database?

Thanks by advance
Nicolas L.


-----Message d'origine-----
De : resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] De la part de Alexander 
Altshuler
Envoyé : mardi 10 octobre 2006 17:29
À : 'resiprocate-devel'
Objet : [reSIProcate] FW: Registar behaviour

Yes, I was wrong here.
Alex

-----Original Message-----
From: Byron Campen [mailto:bcampen@xxxxxxxxxxxx] 
Sent: Tuesday, October 10, 2006 5:59 PM
To: Alexander Altshuler
Cc: 'resiprocate-devel'
Subject: Re: [reSIProcate] Registar behaviour

        Actually, repro does not have a BerkeleyDB or MySQL  
RegistrationPersistenceManager. It can persist _configuration_ using  
these, but it still uses the InMemoryRegistrationDatabase for  
registrations.

Best regards,
Byron Campen


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel