Hi Tomi, The "opensipsctl fifo rtpproxy_show" command does not give a 'status', but a 'disabled' value - for example:
Set:: 0 node:: udp:<IP Address>:7898 index=0 disabled=0 weight=1 recheck_ticks=0 node:: udp: <IP Address> :7898 index=1 disabled=0 weight=1 recheck_ticks=0 node:: udp: <IP Address> :7898 index=2 disabled=0 weight=1 recheck_ticks=0 Is this 'disabled' value meant to mean a config or running status? I thought this 'disabled' value is meant to mean whether it has been disabled in config - i.e. if you add "=0" to the URI address of the configured rtpproxy node. This is not these same as whether the rtpproxy is active/healthy - which is what "Memory State" in CP is meant to mean? Thank you. On Wed, 24 Jun 2020 at 17:15, Tomi Hakkarainen <tpai...@gmail.com> wrote: > Hi, > > I believe MU is just typo should be MI > > The ’status’ should also be retrieved differently not with the > > $ opensipsctl fifo rtpproxy_show > > command > > I think you can get the ’status’ directly from the database with SQL > query. > > Tomi > > > On 24. Jun 2020, at 16.33, solarmon <solar...@one-n.co.uk> wrote: > > > Hi Bogdan-Andrei, > > There is only 'Memory State' in CP. There is no 'status' in CP. > > Sorry, what is 'MU'? > > I'm using opensips 2.4.x if that makes any difference. > > Thank you. > > On Wed, 24 Jun 2020 at 13:49, Bogdan-Andrei Iancu <bog...@opensips.org> > wrote: > >> Hi, >> >> In CP, the `status` is the status from the SQL table and the `memory >> status` is the status provided by the MU rtpproxy_show. >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> >> On 6/24/20 12:16 PM, solarmon wrote: >> >> Hi, >> >> The command "opensipsctl fifo rtpproxy_show" does not return the 'status' >> of the rtpproxy node. >> >> In OpenSIPS Control Panel, the RTPProxy table has a '*Memory State*' >> column which seems to be the 'status' of that node. >> >> How can I get this 'Memory State' 'status' in command line form so that >> it can be scripted? I want to be able to get a health status of the >> rtpproxy from OpenSIPS point of view and graph it over a period of time. >> >> Thank you! >> >> _______________________________________________ >> Users mailing >> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users