Hi!
Is there any possibility to share xavp’s between Kamailio nodes? Idea is to share result of ds_select_dst between several nodes and as 5.2 Kamailio stores result in xavp - need to share this structure as well
Right now sharing between nodes is done on sht + dmq and I’m not sure I can save xavp in sht.
Regards, Igor
Am Donnerstag, 11. Oktober 2018, 09:21:28 CEST schrieb Igor Olhovskiy:
Is there any possibility to share xavp’s between Kamailio nodes? Idea is to share result of ds_select_dst between several nodes and as 5.2 Kamailio stores result in xavp - need to share this structure as well
Right now sharing between nodes is done on sht + dmq and I’m not sure I can save xavp in sht.
Hello Igor,
I don't understand your problem completely, sorry. Can't you just access the hash table in a similar way as the xavp? You can of course also just assign the xavp to the htable.
Best regards,
Henning
Idea is I’m not sure I can store XAVP in htable due to different data types they are handle.
Regards, Igor On Oct 15, 2018, 10:39 PM +0300, Henning Westerholt hw@kamailio.org, wrote:
Am Donnerstag, 11. Oktober 2018, 09:21:28 CEST schrieb Igor Olhovskiy:
Is there any possibility to share xavp’s between Kamailio nodes? Idea is to share result of ds_select_dst between several nodes and as 5.2 Kamailio stores result in xavp - need to share this structure as well
Right now sharing between nodes is done on sht + dmq and I’m not sure I can save xavp in sht.
Hello Igor,
I don't understand your problem completely, sorry. Can't you just access the hash table in a similar way as the xavp? You can of course also just assign the xavp to the htable.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio security assessment - https://skalatan.de/de/assessment
The xavps are specific for an transaction, even if you replicate them, it won't make much sense on the other instance if you do not have the transaction to associate the replicated xavps to it.
One of the xavps related to dispatcher is storing the pointer to the local socket to be used for sending out (if specified as attribute). In the past, when dispatcher was using avps, the pointer address was stored formatted as string. In both cases, old or new, replicating this value is useless, because it points to the memory of local kamailio. If you don't set send socket for dispatcher addresses, then this has no effect for the replication.
Given the above, and once again, replication of xavps makes no sense without their associated transaction, the way to replicate xavps is to serialize them to a string, replicate the value using dmq or uac_req_send() and in the other side deserialize. You can serialize to parameters format by doing string concatenation and deserialize with xavp_params_explode(), or serialize to json format and then use json/jansson modules to deserialize. You can also use embedded scripting languages to help with serialization/deserialization.
Cheers, Daniel
On 16.10.18 16:34, Igor Olhovskiy wrote:
Idea is I’m not sure I can store XAVP in htable due to different data types they are handle.
Regards, Igor On Oct 15, 2018, 10:39 PM +0300, Henning Westerholt hw@kamailio.org, wrote:
Am Donnerstag, 11. Oktober 2018, 09:21:28 CEST schrieb Igor Olhovskiy:
Is there any possibility to share xavp’s between Kamailio nodes? Idea is to share result of ds_select_dst between several nodes and as 5.2 Kamailio stores result in xavp - need to share this structure as well
Right now sharing between nodes is done on sht + dmq and I’m not sure I can save xavp in sht.
Hello Igor,
I don't understand your problem completely, sorry. Can't you just access the hash table in a similar way as the xavp? You can of course also just assign the xavp to the htable.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio security assessment - https://skalatan.de/de/assessment
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users