Jack,
Yes it is a bug and it's now fixed in CVS. Thanks for reporting it.
Regarding how to persist registrations in a DB, there is an old inactive
code that stores registration in an SQLite DB. You may either try to
activate this code by linking opensipstack to SQLite 3 or have the code
as a basis to store registration information to your Database of
choice. You can take at look the the registration db constructor for
particulars which I am pasting below:
File: RegisterSessionManager.cxx
RegistrationDatabase::RegistrationDatabase()
{
#if HAS_CPPSQLITE
m_HasContactRecovery = PrepareContactRecoveryDB(
"ContactRecovery.sqlite" );
if( m_HasContactRecovery )
RecoverRegistrations();
#endif
}
Jack Damn wrote:
Hello,
Looks like there is a problem in the log files management when we switch
to a new day. A new logfile seems to be created for SIP Log, but the
PTRACE
log keeps using the file the OSBC opened at startup.
Can anyone confirm that bug ?
Im running OSBC 1.1.5 on Solaris 10.
Also, is there a way to save the entries currently in the registrar memory
when operating in B2BUpperReg mode so that a server reboot or simply OSBC
restart keeps the user location states ? SER does it that via a DB.
Thanks,
JD
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel