From: Moises Silva Date: Mon, 25 Jan 2010 18:52:47 +0000 (+0000) Subject: update BOOST.limitations file X-Git-Tag: v1.0.6~38^3~28 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=08df1fd80cbaef50fc83c776ea5f6c901c2193c8;p=thirdparty%2Ffreeswitch.git update BOOST.limitations file git-svn-id: http://svn.openzap.org/svn/openzap/branches/sangoma_boost@1004 a93c3328-9c30-0410-af19-c9cd2b2d52af --- diff --git a/libs/freetdm/src/ftmod/ftmod_sangoma_boost/BOOST.limitations b/libs/freetdm/src/ftmod/ftmod_sangoma_boost/BOOST.limitations index 6e382ae897..663b7d376a 100644 --- a/libs/freetdm/src/ftmod/ftmod_sangoma_boost/BOOST.limitations +++ b/libs/freetdm/src/ftmod/ftmod_sangoma_boost/BOOST.limitations @@ -18,11 +18,3 @@ == TODO == - proper upper layer management of HW alarms (this must be done in mod_openzap.c) -- proper boost hunting done in openzap based on channels status - -- move all logging calls to macro-based logging to log the file name and line in sangoma prid - -- 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 -