Re: [SR-Users] evapi:message-received and state

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

Re: [SR-Users] About the Presence service 401 issue

Hi Henning, OK. I will try to find the root issue later. Thanks! BR, Sparkle Zou At 2022-11-02 16:44:34, "Henning Westerholt" wrote: Hello, Thanks. From 3.1.x to 5.6.x is a long time with a lot of changes. Hard to say why this happened. Maybe somebody else can who knows

[SR-Users] evapi:message-received and state

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