All,
mohqueue was updated to use RPC instead of MI commands.
Bob
On Tue, Jan 3, 2017 at 3:22 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
On 02/01/2017 23:49, Robert Boisvert wrote:
I will take a look at mohqueue tomorrow and
see what I can do.
However, if rtpproxy doesn't work, neither will mohqueue.
Thanks, getting mohqueue updated to rpc would be appreciated!
Rtpproxy module has some rpc commands already and the plan is to
implement all of them.
Cheers,
Daniel
Bob
On Mon, Jan 2, 2017 at 5:17 PM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
based on lib linking in Makefiles, the following modules
still use MI,
categorized by their state from my point of view. Hopefully
some other
people will help with those listed in 2) to 6).
1) to be removed
- mi_datagram
- mi_fifo
- mi_rpc
- mi_xmlrpc
- pua_mi
2) rpc commands implemented
- dialog - others modules depend on some mi callback from
it (qos and sst)
- qos - this looks ready to wipe out the mi code, but
didn't get the
time not analyze properly as I don't use it usually
3) some rpc commands implemented and the rest should not be
very complex
- carrierroute - I implemented the dump rpc command, but it was
reported that it has issues, so it needs follow up.
4) rpc commands have to be implemented, expecting not to be
very complex
- cplc
- imc
5) expecting some degree of complexity, but they are
important modules
- rtpengine
- rtpproxy
6) not familiar with the mi commands in these modules, so not
able to
assert what to expect
- ims_dialog - some rpc commands are implemented, not sure
if the rest
of MI are used/usefull
- mohqueue - it doesn't seem complex to implement rpc
commands at
first sight, but the indentation style didn't allowed a fast
analyze on
a quick look
- p_usrloc - several mi commands
- sst - uses some callback for MI from dialog module. qos has
something similar with rpc alternative already implemented
- userblacklist - several mi commands
- utils - there are few mi commands related to some
forwarding rules:
https://www.kamailio.org/docs/modules/devel/modules/utils.html#idp21741924
<https://www.kamailio.org/docs/modules/devel/modules/utils.html#idp21741924>
The 1) to 5) should be done in a way or another, before of
after freeze
of 5.0.0. But 6) would require the devs of the modules (or
the MI parts)
to help if they want those commands via RPC.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio World Conference - May 8-10, 2017 -
www.kamailioworld.com <http://www.kamailioworld.com>
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org <mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev>
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org <mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev>
--
Daniel-Constantin Mierla
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio World Conference - May 8-10, 2017 -
www.kamailioworld.com
<http://www.kamailioworld.com>
_______________________________________________ sr-dev mailing
list sr-dev(a)lists.sip-router.org
<mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev>