fix mod_spandsp on systems with libjbig
1.2.9 rev bump
FS-5383 --resolve
FS-5325
FS-5168 --resolve
Revert "fixed stuck mod_rtmp session when the call is killed from fs side, such as using uuid_kill"

This reverts commit d8edc031faa41d4e570aad1e347a0ed6c0d6c1d8.

Conflicts:
	src/mod/endpoints/mod_rtmp/mod_rtmp.c
FS-5371 --resolve typo
FS-5327 --resolve
FS-5288 --resolve
Undo previous change
FS-5085 I discovered that the bowout is happening from both legs at once, we only need to check this condition on the A side of the loopback bridge
FS-5395: --resolve Resolve another mod_rtmp crash where oh specific hangup scenarios there would be a free of variable that wasn't ever malloced
FS-5395: False alarm on a reported valgrind memory leak. The io_private is alloc'd from a memory pool which valgrind sucks at tracking. No need to free this, because it'll get cleared when the memory pool on the rsession is destroyed.
FS-5398
FS-5390 --resolve
FS-5360 --resolve fields are exec-on-max-failures exec-on-max-timeouts pin, needs testing
FS-5325 i'll put the nonblocking in but I still think this is a problem with openssl, a short read is not there every single time you connect, When the lib is in full blocking mode it should be handling the complicated actions internally.  As complicated as socket programming is, async ssl is even worse because it requires you to do your own buffering and attemps to read may fail waiting for you to write or vice-versa which should have been handled for us in the lib.  non-interruptable syscalls are getting pretty outdated and not enabling it is much less complex than making every socket app on earth be non-blocking
FS-5399 --resolve
move log message to avoid logging null
FS-5403 --resolve