Hi Takeshi,
Thanks for the note here, I will check the PR.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 5-16 Dec 2022, online
https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/
On 10/22/22 12:53 PM, mayamatakeshi
Hi,
I've been following this discussion as I have a similar use case.
I have created a PR offering a new function t_reply_by_callid for the
module tm to simplify this:
https://github.com/OpenSIPS/opensips/pull/2937
Regards,
Takeshi
On Thu, Oct 20, 2022 at 4:04 PM Bogdan-Andrei Iancu
wrote:
>
Ivan,
Actually a simpler approach will be to use t_wait_for_new_branches()
instead of that t_write function, it should do the same trick
(postponing the deletion of the transaction), but without any side effects.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.open
Sorry, I mean no sleep, i mean async( sleep($var(wait_time)), after_sleep
);
Regards, Ivan.
вт, 18 окт. 2022 г. в 14:42, Bogdan-Andrei Iancu :
> Hi,
>
> yes, call it before ending the REQUEST route. I'm 100% the transaction is
> not deleted before the end of the route. And try to use the unix soc
Hi,
yes, call it before ending the REQUEST route. I'm 100% the transaction
is not deleted before the end of the route. And try to use the unix sock
flavor for the function, not the fifo one.
DO NOT use the sleep, you will block your whole opensips.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Fou
Hi Ryzhik,
Right, the transaction must be forced to stay until you are done with a
final reply. Unfortunately there is no clear way to do this from script
(this may be subject of further small improvements), but you can try
taking advantage of the `t_write_req` [1] for this purpose, even if yo
Perfect !!!
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
https://www.opensips.org/events/Summit-2022Athens/
On 10/12/22 1:09 PM, Ryzhik Ivan wrote:
I found a solution. hex strings are reversed).
Thank you very
Thank you, Bogdan.
I got stuck with tm documentation.
1) MI t_reply command has named parameters, ok, no problem.
2) trans_id - transaction identifier (has the hash_entry:label format) -
what is this? if i use $T_id i got reply "Invalid trans_id".
3) Where can I get to_tag from script level
Hi Ivan,
you can use timer_route, but as there is no way to send a reply for a
particular transaction from script level (only to the currently
processed request), you will have to trigger the MI cmds from the timer
route, which is a bit hackish
Regards,
Bogdan-Andrei Iancu
OpenSIPS Fo
Hi Ryzhik,
Without a t_relay() it makes not much sense to have an dialog structure
at all - the dialog module in opensips is actually design for proxied
calls, not for UAC calls.
IMO, you should keep it a transaction level, by sending replies back
only. When getting the INVITE, put its call-
Hello!
My opensips version is 3.1 with tm,dialog and rtpengine modules.
On incoming INVITE i'm creating an early dialog with 183 replies and i'm
playing audio to caller with rtpengine, no t_relay() on this step, OS is
acting as UAS endpoint.
If the caller cancels the invite with a CANCEL message -
11 matches
Mail list logo
