Hi,
I successful did my changes, thanks for your help.
Now I have the problem that on shutting down the application the library
is not terminated correctly (clean). There are five threads that are
terminated with exit code 1. That are the housekeeper and the garbage
collector threads. On shut down I call already
ClearAllCalls();
if( sipEndPoint != NULL ) {
sipEndPoint->GetUserAgent()->GetStack().Terminate();
}
// Shut down the cleaner thread
garbageCollectExit.Signal();
garbageCollector->WaitForTermination();
Can someone help me?
Thanks.
M.Dreißig
Joegen E. Baclor schrieb:
Matthias Dreißig wrote:
Thanks for fast your answer.
And if I want to adapt the registration I have to implement a subclass
of RegisterSessionManager and RegisterSession, am I right?
Right. If you need to modify the behavior of the RegisterSession, then
you may also subclass it. However, if you don't need to, just
sub-classing RegisterSessionManager would be ok too. All the necessary
callbacks for authentication of each session is already exposed in the
manager. Take a look at OpalOSSEndPoint.cxx specifically
OpalOSSRegistrar class for a sample implementation.
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel