From baec5f24a87f1ce89b3cd53647cc7273c5ea4792 Mon Sep 17 00:00:00 2001 From: Moises Silva Date: Fri, 15 Jan 2010 14:59:53 +0000 Subject: [PATCH] updated todo git-svn-id: http://svn.openzap.org/svn/openzap/branches/sangoma_boost@961 a93c3328-9c30-0410-af19-c9cd2b2d52af --- .../src/ozmod/ozmod_sangoma_boost/BOOST.limitations | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/libs/freetdm/src/ozmod/ozmod_sangoma_boost/BOOST.limitations b/libs/freetdm/src/ozmod/ozmod_sangoma_boost/BOOST.limitations index 6da43bae34..6e382ae897 100644 --- a/libs/freetdm/src/ozmod/ozmod_sangoma_boost/BOOST.limitations +++ b/libs/freetdm/src/ozmod/ozmod_sangoma_boost/BOOST.limitations @@ -4,12 +4,14 @@ any openzap span using sigboost must have only channels belonging to the corresponding physical span. + This is the reason we added group functionality in openzap core, furthermore, previous groups in openzap + were only possible through adding of b-channels to a single span, but this forces the user to create groups + of channels only whithin the same type of trunk among other things. + - all spans must be configured and then started, cannot configure, start, configure start etc this is due to netborder telesoft abstraction. that requires configuring everything and then starting everything at once. -- just per-span hunting for now. We must remove the hunting from sigmods and delegate to ozmod_sangoma_boost - - sangoma_prid and sangoma_brid on Windows had to be compiled hacking make/Makefile.platform to comment all VC runtime checks, otherwise when running in debug mode exceptions are thrown due to loss of data ie short to char conversions. @@ -20,10 +22,6 @@ - move all logging calls to macro-based logging to log the file name and line in sangoma prid -- add zap_span_get_signaling_status that will check the overall span signaling status - -- fix segfault on unload of mod_openzap, probably due to threads in smgprid not being stopped - - remove FORCE_SEGFAULT from sangoma_sprid and check if there is anything like that in sangoma_brid we should be using zap_assert or zap_assert_return which will abort depending on the openzap crash policy