kenmirrors
/
freeswitch
mirror of https://github.com/signalwire/freeswitch.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

updated todo 

git-svn-id: http://svn.openzap.org/svn/openzap/branches/sangoma_boost@961 a93c3328-9c30-0410-af19-c9cd2b2d52af
This commit is contained in:
Moises Silva 2010-01-15 14:59:53 +00:00
parent 200b25e256
commit baec5f24a8
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
libs/freetdm/src/ozmod/ozmod_sangoma_boost/BOOST.limitations
View File

@ -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