Hello, iirc, the continue is done by the same worker process that executes the event route, so you can pass it via $var(...), otherwise you can propagate it to other process via mqueue (+rtimer). Using htable with a key based on transaction ids should be fine as well, at the end htable is designed as a fast key/value in-memory storage.
Cheers, Daniel On 07.11.22 05:36, Alex Balashov wrote: > Hi, > > I am t_continue()ing a transaction inside of > event_route[evapi:message-received]. The $evapi(msg) has quite a bit of > payload that will be needed by the resumed transaction. > > Is there a good way to inject this data into the transaction scope > externally? No [X]AVPs created in the event_route persist, of course, since > the route is scoped outside of the transaction. > > I have been using htable to pass data into the transaction, keyed by the > index and label. But, this strikes me as a kind of clumsy memory > synchronisation anti-pattern. Is there a better way? > > Cheers, > > — Alex > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the > sender! > Edit mailing list options or unsubscribe: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users