On 18.07.2009 21:57 Uhr, Andrei Pelinescu-Onciul wrote:
On Jul 18, 2009 at 22:18, Juha Heinanen jh@tutpro.com wrote:
i have now managed to get all my stuff working using sr except t_uac_dlg. t_uac_dlg is not working because for some reason sr tm module does not implement t_uac_dlg and mi_rpc tells "async mi cmd not implemented yet".
i would prefer native support of t_uac_dlg in tm module,
there is an alternative that you can use: dlg_bridge from K dialog module:
http://sip-router.org/docbook/sip-router/branch/master/modules_k/dialog/dial...
It does the c2d logic internally. The difference is that you do not get feedback from all requests/replies of c2d flow. It initiate the c2d process and returns - it is sync mode and easier to use via MI (just one command).
You need just to create the table, load the module and set few parameters, you don't have to track calls with dialog module, so no runtime overload.
Cheers, Daniel
because the idea was that sr will use ser tm module. if t_uac is difficult to implement in ser tm module or if that would still not make t_uac_dlg to work via rpc, then i guess i need to wait until mi_rpc supports async mi functions.
t_uac_dlg was removed long time ago from ser (that's also were kamailio/openser inherited it from). There were 2 versions one working with the fifo and another one with unixsocks, but both were removed when we switched to RPC. IIRC the idea was to make a separate module implementing it, but we stopped when sems got its own sip stack (sems was the only known user).
t_uac exists in sr tm and is exported by the tm api. t_uac_dlg is/was just a wrapper reading and writing to fifo/unixsock/mi and then calling t_uac. It should be possible to revive the t_uac_dlg implementation in a separate module but the problem is that proper async support is easy to implement only using the old fifo (and passing a "reply" fifo) or datagram sockets (the async support in mi_xmlrpc is a joke: it just waits in a loop, _polling_ a shared memory variable until someone writes it or timeouts and then sends the xmlrpc reply).
That being said there is some work on an application server interface using the binrpc protocol (see ftp://ftp.iptel.org/pub/sug/sersum.pdf and http://tracker.iptel.org/browse/SER-347), which far exceeds t_uac_dlg needs. From what I know all the required tm changes are in-place, we only have to wait for Bogdan Pintea to commit the rest of it.
otherwise things thus look pretty good to me. thanks for your efforts.
Thanks a lot for testing.
Andrei
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev