This morning SIPWitch became "architecturally" complete, at least enough
to actually build initial call server functionality. This means that
final issues with how call sessions will be managed, how session locking
for the state machine will actually work, and how the background timer
thread will interact with session management have all been resolved.
The locking model has been greatly simplified for parallel operation,
and some registry management issues have also been closed.
The next step in sipwitch will be to begin call/session state
development for actual call features and functionality, as well as
message handling for subscribe/publish events, simple messaging, etc.
_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel