Is there any module in kamailio that enables proxies to handle transactions that weren’t created by that proxy? Anything which stores the transaction state in the database? Did a bit of looking but I didn’t see anything that looked like it did that and nothing in the FAQ.
Alas, there is not. It’s periodically discussed. However, it turns out that serialising, storing and reanimating transactions not created in the same runtime instance of Kamailio is actually not straightforward.
However, it’s also mot necessary in most cases. Kamailio falls back to stateless routing and can route almost anything just based on the SIP message contents themselves. It’s really just a few edge cases like CANCEL handling that drive the demand for this, and even then, there are workarounds.
What problem are you trying to solve? Perhaps there is a better, or alternative but adequate way.
-- Alex
On Jan 15, 2018, at 10:30 PM, Malcolm O'Hare sac_malcolm@msn.com wrote:
Is there any module in kamailio that enables proxies to handle transactions that weren’t created by that proxy? Anything which stores the transaction state in the database? Did a bit of looking but I didn’t see anything that looked like it did that and nothing in the FAQ. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
Alex Balashov -
Malcolm O'Hare