Hello
Is it possible not to close it?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3997#issuecomment-2493065385
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamai
Hello
I've tested it.
It works.
Kamailio is now sending the ACK for the 487.
Bellow traces.
<==[387 bytes]==[2024-11-14 19:03:58.592143] 10.192.117.6:5030 =>
10.192.117.6:5084
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP
10.192.117.6:5084;branch=z9hG4bKfb0b.dc0ab91200
Hello
I use the ‘**tm.t_uac_star**t’ function to send an INVITE and then the
**‘tm.cancel**’ function to cancel the INVITE.
But the ‘**tm.cancel**’ function immediately deletes the transaction. Kamailio
can't acknowledge message 487 because the transaction has been deleted.
**Callflow descriptio
Hello
I tested:
KSR.timer.timer_enable("tmr4", 0) and KSR.timer.timer_enable("tmr4", 1)
It works.
Thanks
Juan
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4008#issuecomment-2445103412
You are receiving this because you are subscribed to this th
Hello
The timer_enable() function does not exist in KEMI.
Can you implement the equivalent of this function in KEMI?
BR
Juan PASCUAL
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4008
You are receiving this because you are subscribed to this thr
The documentation indicates that the function: KSR.hdr.append(...) applies to
request and reply.
https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/core/#ksrhdrappend
KSR.hdr.append(...)
int KSR.hdr.append(str "hdrval")
Append header to current SIP message (**request or reply**). It
Hello
In the function ksr_tm_event_response_sent(evname), header and body
modifications are not applied.
**Example of modification:**
KSR.textops.set_body("application/test", "teststbody")
KSR.textops.remove_hf("Contact")
KSR.hdr.append("X-My-Hdr: testhdrappend \
Hello
I tested it. The bug is fixed.
BR
Juan
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3831#issuecomment-2382614828
You are receiving this because you are subscribed to this thread.
Message ID: __
Hello
I tested it. The bug is fixed.
BR
Juan
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3979#issuecomment-2382612168
You are receiving this because you are subscribed to this thread.
Message ID: ___
Hello
I tested the correction.
Now , the tm.cancel function generete “tm:local-request” event.
But the pseudo variables correspond to the INVITE equest and not to the CANCEL
request.
Example: $rm = INVITE
Can you reopen the issue?
BR
Juan
--
Reply to this email directly or view it on GitHub:
ht
Hello
Following the correction of issue #383, pseudo-variables are erroneous for
tm.cancel function.
The pseudo variables in “tm:local-request” correspond to the INVITE equest
and not to the CANCEL request.
Example: $rm = INVITE
BR
Juan
--
Reply to this email directly or view it on GitHub:
h
Issue 383 is reopen
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3977#issuecomment-2355563032
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Develo
Closed #3977 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3977#event-14290357038
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Devel
Hello
The tm.t_uac_start function generates a “tm:local-request” event.
But the tm.cancel function doesn't generete “tm:local-request” event.
Is it possible to activate a parameter in the TM or TMX module to generate the
event?
Thanks
Juan
--
Reply to this email directly or view it on GitHub
14 matches
Mail list logo
