Hi!
In the Documentation of the TMX Module for the t_reply function there is given a list of Parameters as can be seen here:
http://www.kamailio.org/docs/modules/3.1.x/modules_k/tmx.html#id2822345
The third parameter is a trans_id. I cannot find any references for this. Is it possible to send a query to the MI Datagram socket, to do a lookup of the trans_id for a given callid or is there any other solution to get this information through the MI datagram socket, to be able to execute t_reply?
It seems that t_reply_callid is doing what I want to do, but currently not through the MI Datagram socket and not including a body or new headers.
Greetings Torge
Hello,
On 5/6/11 11:01 AM, Torge Szczepanek wrote:
Hi!
In the Documentation of the TMX Module for the t_reply function there is given a list of Parameters as can be seen here:
http://www.kamailio.org/docs/modules/3.1.x/modules_k/tmx.html#id2822345
The third parameter is a trans_id. I cannot find any references for this. Is it possible to send a query to the MI Datagram socket, to do a lookup of the trans_id for a given callid or is there any other solution to get this information through the MI datagram socket, to be able to execute t_reply?
the function should be used together with t_write_req()/t_write_unix() which give the transaction id. Note this was the way of communicating with SEMS in the past, which is now pretty much obsolete, SIP is preffered way to send to SEMS.
What exactly do you need to do, maybe there are some other options around?
Cheers, Daniel
It seems that t_reply_callid is doing what I want to do, but currently not through the MI Datagram socket and not including a body or new headers.
Greetings Torge _______________________________________________ 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
Hi Daniel!
What exactly do you need to do, maybe there are some other options around?
I am currently trying to implement some kind of protocol translation in a external daemon process.
The idea is:
A SIP Requests comes in and is processed in the following way in a REQUEST_ROUTE
if ((is_method("...") & ...) { t_newtran(); forward_udp(HOST,PORT); exit; }
A new transaction is then created and the Daemon listening on HOST:PORT should do some protocol translation, waiting for some reply through the other protocol and then reply to the original SIP request sending out a SIP reply.
t_reply seems to be the right function, but I need to be able to reply for example to the callid.
t_reply_callid might also be a solution, but this is not exported to MI Datagram and does not allow to specify a body, which I would also need.
Should I write a patch for this to export a MI function for t_reply_callid including a body parameter or is there another solution?
Greetings Torge
-
Daniel-Constantin Mierla -
Torge Szczepanek