Hi Jeff,
What do you mean ? I tried the "version" command via the MI tool and it
properly works - what kind of error do you experience ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 02/24/2017 07:21 PM, Jeff Wilkie wrote:
Thanks Bogdan, I will dl 2.2.3 and retest. This error occurred on
the following BTW
Array
(
[Server] => OpenSIPS (2.3.0-dev (x86_64/linux))
)
Jeff Wilkie
On Fri, Feb 24, 2017 at 4:46 AM, Bogdan-Andrei Iancu
<bog...@opensips.org <mailto:bog...@opensips.org>> wrote:
Hi Jeff,
There was an issue on how the MI output of the address_dump was
formated when using JSON. This issue was leading to an invalid
JSON being returned. And CP was dropping the returned JSON as not
able being able to parse it. If you do the direct web query, there
is nothing to parse/validate the JSON, so it is displayed.
The issue was fixed in latest 2.2, so please grab the 2.2.3 and
give it a try please.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com <http://www.opensips-solutions.com>
On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
Ok, question part 2, now that the proper module is loaded :)
From the MI interface in CP, I have 1 small issue. Using json to
interface with opensips, I execute the command "*address_dump"
*and execute. I receive the output of address dump** |
son:127.0.0.1:8888/json <http://127.0.0.1:8888/json>Successfully
executed, no output generated. Other commands like domain_dump
work as expected in the SYSTEM/MI interface. If I bypass CP and
use web direct command 127.0.0.1:8888/json/address_dump
<http://127.0.0.1:8888/json/address_dump> I receive the proper
output. Not sure why CP provides no output from this command
though.
The web query directly looks like this as a response when not
using MI via CP
http://10.10.20.229:8888/json/address_dump
<http://10.10.20.229:8888/json/address_dump>
{"part": [{"value":"default", "children":{"dest": [{"value":" 8 <10.10.10.99,2, 5060, 1, NULL, 1515599999>"},
{"value":" 19 <10.10.20.193,2, 5060, 1, NULL, 1515599999>"}, {"value":" 81 <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}
It's not a show stopper but bugging me why it doesn't work for
that command only from what I can tell from initial testing.
Jeff Wilkie
Yes, you did overlook to load the dialplan module into your
OpenSIPS (the dp_reload command is prvided by this modules).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
<http://www.opensips-solutions.com>
On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
When using the mi_json module combined with CP, it appears
that not all of the functions were ported over for this
interaction to complete 100%. JSON enabled
in opensips-cp/config/boxes.gl <http://boxes.gl>obal.inc.php
only allows some commands to work. One particular command
that appears to not be working is under SYSTEM/DIALPLAN of
CP when you attempt to hit "apply to server". I receive a
Sending to *json:127.0.0.1:8888/json
<http://127.0.0.1:8888/json>* : Error code 500 (Command not
found) for the dp_reload command. If I do the same thing
under the SYSTEM/PERMISSIONS page "apply to server" returns
success for address_reload. Is this a known issue? Did I
overlook something small in the config? How do I remedy
this issue?
Thanks
Jeff Wilkie
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<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
