Hi Ovidiu,
Thanks for taking the time for explaining. I am sure some of us can take
advantage of
It!
Mario San Vicente
Best regards
> El 3 nov 2020, a la(s) 22:51, Ovidiu Sas escribió:
>
> Hello Mario,
>
> If you have CP working fine, you don't really need mi_html.
> If you want to have
Hello Mario,
If you have CP working fine, you don't really need mi_html.
If you want to have it as an alternative, load the module and set a
new root path:
modparam("mi_html", "root", "opensips_mi")
Then you should be able to access the embedded management interface
via
Hello Răzvan / Ovidiu,
After disabling mi_html, my CP is working fine, i will be enabling more
modules on it. Thanks for your help!
Ovidiu, It would be good to have both portals running,but i am not
getting to work the following comment:
"If you want to keep mi_html, then set a different
Hello Mario,
It seems that you have both mi_http and mi_html modules loaded.
By default, both modules have the root path set to mi and one of the
modules is stealing the root path from the other.
In your case, when you hit http://x.x.x.x:/mi , you are hitting a
standalone management interface
I am not sure why you're saying it is not reflecting the real info - I
can see the MI returning data for rtpproxy, are you sure that's not
correct? And you're probably not having any ongoing calls, that's why
dlg_list returns 0.
Running MI HTTP is a completely different story, what you're
Hello Răzvan ,
I was wrong with my diagnosis, cause i stopped receiving the http / 400
error. But when trying to monitor calls i see that the portal is not
reflecting the real info, i tested dialogs and rtpproxy.
I do see the json reply on a trace, but it is not updated on the portal:
T
Hello Răzvan ,
Thanks alot, that made the trick.
I will check if something is not matching with the monit page cause that is
not working , but that's another story.
Best regards.
Mario
On Thu, Oct 29, 2020 at 3:49 AM Răzvan Crainea wrote:
> As I see in your logs, OpenSIPS CP uses the
As I see in your logs, OpenSIPS CP uses the `json` URL path for querying
MI, whereas the default root path is `mi`[1]. Either change the `root`
to `json`, or modify your OpenSIPS CP boxes config to `mi`.
[1] https://opensips.org/docs/modules/3.1.x/mi_http.html#param_root
Best regards,
Răzvan
Thanks for the answer Johan,
But i see that; the *mi_json* module has been renamed to *mi_http* module.
and so: failed to load module mi_json.so
https://www.opensips.org/Documentation/Migration-2-4-0-to-3-0-0
I am using opensips 3.1
I have this modules:
loadmodule "httpd.so"
You need to use mi_json
Outlook voor iOS<https://aka.ms/o0ukef> downloaden
Van: Users namens Mario San Vicente
Verzonden: Wednesday, October 28, 2020 8:06:09 PM
Aan: OpenSIPS users mailling list
Onderwerp: [OpenSIPS-Users] Opensips-cp 8.3.0 HTTP/1.1 4
Hello Everyone,
Here i have a quick question.
I installed opensips-cp 8.3.0 in a Centos installation from
sources version: opensips 3.1.
I seems to me that the configuration is fine, mysql DB, and users.
But Opensips-cp can't speak MI to opensips.
I get the following at trace level:
T
11 matches
Mail list logo
