What triggers the issue could be in Kamailio, but it is hard to figure out with
no clue of what the driver doesn't like. The parameters should be ok, as
freetds goes on fine.
Kamailio initiates libssl with its own shared memory manager, which then is
reused by other libs linked to libssl, as libssl was designed with a context
per process.
Also, the mutex locking systems is set to the one for kamailio, that's why the
second core leads back to kamailio to locking_f() function from tls module. But
for first core, the backtrace stack doesn't go back to kamailio, so the crash
happens in external code.
Could be some options/params that the drivers doesn't like, but cannot be
guessed without sources or someone from their dev team saying. Once that is
learn, kamailio should be easy to adjust, all sources are out there...
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/501#issuecomment-198386863
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
