Hello,
you probably looked already into that, but a “SIP” way of doing this kind of
application would be to use the presence dialog event package. There are the
presence_dialoginfo and pua_dialoginfo modules for example.
Cheers,
Henning
From: Anthony Wittig
Sent: Dienstag, 21. Februar 2023 1
There are innumerable ways to do that. If going with your chosen AMQP broker
approach, just do it in an async fashion, using either this,
https://kamailio.org/docs/modules/5.6.x/modules/async.html
or this:
https://kamailio.org/docs/modules/5.6.x/modules/rtimer.html
https://kamailio.org/docs/mod
Hello,
jumping in to address some topic that was not explicitly addressed from
the initial mail -- see it inline, at the end.
On 21.02.23 18:13, Alex Balashov wrote:
> There are innumerable ways to do that. If going with your chosen AMQP broker
> approach, just do it in an async fashion, using e
Hello,You can use the mqueue module functions to store data about the call on the request route.and use rtimer module to créate additional timer processes to fetch those informations and send it to rabbitmq.You will need to figure Out what interval is best for you to check if data is available on t
Thanks for all the suggestions!
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sende
I've done this with RabbitMQ. I don't send any messages until the 180 ringing
comes through (and then in dialog:start and dialog:end), but there's no reason
why you couldn't do it on the initial INVITE.
Although the advice you received to do it asynchronously is absolutely spot-on,
I currently
I've done this with RabbitMQ. I don't send any messages until the 180 ringing
comes through (and then in dialog:start and dialog:end), but there's no reason
why you couldn't do it on the initial INVITE.
Although the advice you received to do it asynchronously is absolutely spot-on,
I currently
