Hi,
you can consider using exec in async way, with launch() for example:
https://opensips.org/html/docs/modules/3.4.x/exec.html#afunc_exec
But imho anything else (non-blocking) may be better than exec, to avoid
the penalty for forking new processes ; rest_client, in async way is
also an option
Hi Ronald
For our case, we use exec on development environment too. For the production,
we will use rabbitmq and custom events to decouple pn delivery from the script.
Volkan Oransoy
On 3 Feb 2024 at 20:54 +, r...@rvgeerligs.nl, wrote:
> Hi,
>
> Currently experimenting with the EXEC module.
Hi,
Currently experimenting with the EXEC module. Still all advice is welcome.
Regards,
Ronald
February 3, 2024 at 4:39 PM, r...@rvgeerligs.nl wrote:
>
> Hi,
>
> I managed to integrate pn in opensips 3.4 as I get as reply to register from
> my opensips server:
>
> SIP/2.0 200 OK
>
> Vi
Hi,
I managed to integrate pn in opensips 3.4 as I get as reply to register from my
opensips server:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.1.14:57993;received=x.x.x.x;branch=z9hG4bK.wxwvFfCSG;rport=57993
To: sip:xx;tag=eeba.752562b862ac8bd9236fb7979b3044b6
From: ;tag=mFddPGSw6
Call-ID: UF
