Hello,
On 9/4/12 12:40 AM, David J wrote:
Thanks Fred.
I think this was it.
I think there were some updates to the app_lua module since.
Do you know if this is still relevant?
the changes were more related to the addition of new kamailio
functions/modules to the Lua API (sr package in Lu
Hello,
the readme is wrong regarding the name of the event route, it should be:
event_route[dialog:failed]
I will fix the docs.
Cheers,
Daniel
On 9/3/12 11:00 AM, Uri Shacked wrote:
Hi,
i seems to me that the "event_route[dialog:failure]" does not
recognize dialog failures.
i use dlg_manage
Hello,
You set r-uri ($ru) to an IP address only -- it has to be a full SIP
URI.
Cheers,
Daniel
On 9/4/12 5:34 PM, Fatima
Chahrour~Vanrise Support wrote:
Hello,
Thanks for your
Hello,
interesting, it is one of the oldest functions of the tm, from early ser
days, but probably the readme in ser didn't have it all the time. Just
add it, the functionality hasn't change, it is grepping the sip reply
code of the current/wining branch in transaction.
Cheers,
Daniel
On 9/
It is true. It disappeared from the docs after the 3.0 sip-router convergence.
It is present in 'tm' docs in <= 1.5.x, though.
The current docs do have t_grep_status(), which seems in many respects
identical. I wonder if one is an alias for another now.
--
Alex Balashov - Principal
Evariste Sy
looks like t_check_status is not documented in any readme file.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Thanks for your reply.. am able to make the call reach from 3CX to Kamailio
using the src_ip, thank you, but still not able to redirect the call invite
from Kamailio to 3CX and send the 302 message.
Kamailio
192.168.111
