Despite a good old college try to implement the
Flexisip server from the CentOS-packaged RPM, we've thrown in the towel and will leave it to Linphone to provide the server platform. Hopefully, theirs is more stable. Zero server support anywhere that we could find. Flexisip is dual-licensed just like Asterisk, and they keep solutions close to the vest (unless you pay) just like the early Asterisk days.
We were chugging along all fat, dumb, and happy thinking we had a solid implementation, and it did actually work which is pretty amazing given what we discovered. When we turned on the journal, we were met by an endless stream of what you see below. The referenced Linphone database is nowhere to be found in the config file so this is obviously hidden in the source code. Pulseaudio is a monumental train wreck as well. No clue at all on the crashes. So the journal log grows by roughly 500MB per day.
We now plan to leave Flexisip running and use the platform as a honey pot and nothing more. And, boy, is it a doozy of a honey pot. The SIP attacks in the transaction log almost match the journal in size and frequency with no simple way to block them. The log structure rules out Fail2Ban. Lots of creeps in the world from our favorite countries. So we're gonna pass on this one.
p.s. We love the Linphone clients and Linphone's server platform. So life is good!