Hi Jeff,

So, from CP, using the FIFO backend, the enabling works, but the disabling doesn't ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 09.06.2016 22:30, Jeff Wilkie wrote:
Bogdan,

Based on what you have provided, I decided to change the boxes.global.inc.php file as follows:

$box_id=0;


// mi host:port pair || fifo_file

*$boxes[$box_id]['mi']['conn']="127.0.0.1:8080 <http://127.0.0.1:8080>";*

//boxes[$box_id]['mi']['conn']="/tmp/opensips_proxy_fifo";


It now is able to disable and enable the gateways. I'm not sure if anything else is broken as a result but I will go through the testing. Is there a reason why it would not work using the fifo file instead?


Jeff Wilkie
Chief Technology Officer
US IP Communications
919.297.1057


/"This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. Any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of USIPCOM, LLC. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you". /

On Thu, Jun 9, 2016 at 11:14 AM, Bogdan-Andrei Iancu <bog...@opensips.org <mailto:bog...@opensips.org>> wrote:

    Jeff,

    To have the CP connecting to OpenSIPS you can use any of the MI
    backends - FIFO, XMLRPC, UDP...any will do the trick. The downside
    of FIFO is that the CP and OpenSIPS must be on the same server.

    Regards,

    Bogdan-Andrei Iancu
    OpenSIPS Founder and Developer
    http://www.opensips-solutions.com

    On 09.06.2016 17:38, Jeff Wilkie wrote:
    Is XMLRPC required to make this function work?  Currently, we are
    only using the fifo method as the boxes.global.inc.php only
    referencing this method.  The documentation for CP says to use
    one or the other but does not mention that some functions will
    not work if not using XMLRPC.

    Thanks
    Jeff

    Jeff Wilkie
    Chief Technology Officer
    US IP Communications
    919.297.1057 <tel:919.297.1057>


    /"This e-mail communication and any attachments may contain
    confidential and privileged information and is for use by the
    designated addressee(s) named above only. Any files transmitted
    with it are confidential and intended solely for the use of the
    individual to whom it is addressed. Any views or opinions
    presented are solely those of the author and do not necessarily
    represent those of USIPCOM, LLC. If you are not the intended
    addressee, you are hereby notified that you have received this
    communication in error and that any use or reproduction of this
    email or its contents is strictly prohibited and may be unlawful.
    If you have received this communication in error, please notify
    us immediately by replying to this message and deleting it from
    your computer. Thank you". /

    On Tue, Jun 7, 2016 at 6:52 AM, Bogdan-Andrei Iancu
    <bog...@opensips.org <mailto:bog...@opensips.org>> wrote:

        Hi Jeff,

        So, FIFO works ok for you, but CP (using xmlrpc fails). Can
        you make a capture of the XMLRPC traffic between CP and
        OpenSIPS and post it somewhere ?

        Regards,

        Bogdan-Andrei Iancu
        OpenSIPS Founder and Developer
        http://www.opensips-solutions.com

        On 31.05.2016 17:27, Jeff Wilkie wrote:

        OpenSIPS Control Panel version 5.0


        Jeff Wilkie
        Chief Technology Officer
        US IP Communications
        919.297.1057 <tel:919.297.1057>


        /"This e-mail communication and any attachments may contain
        confidential and privileged information and is for use by
        the designated addressee(s) named above only. Any files
        transmitted with it are confidential and intended solely for
        the use of the individual to whom it is addressed. Any views
        or opinions presented are solely those of the author and do
        not necessarily represent those of USIPCOM, LLC. If you are
        not the intended addressee, you are hereby notified that you
        have received this communication in error and that any use
        or reproduction of this email or its contents is strictly
        prohibited and may be unlawful. If you have received this
        communication in error, please notify us immediately by
        replying to this message and deleting it from your computer.
        Thank you". /

        On Tue, May 31, 2016 at 3:28 AM, Bogdan-Andrei Iancu
        <bog...@opensips.org <mailto:bog...@opensips.org>> wrote:

            Hi Jeff,

            What OpenSIPS Control Panel version are you using ?

            Regards,

            Bogdan-Andrei Iancu
            OpenSIPS Founder and Developer
            http://www.opensips-solutions.com

            On 21.05.2016 00:15, Jeff Wilkie wrote:
            OPENSIPS 1.10.x
            I have the following set

            opensips.cfg

            #### FIFO Management Interface

            loadmodule "mi_fifo.so"

            modparam("mi_fifo", "fifo_name",
            "/tmp/opensips_proxy_fifo")

            modparam("mi_fifo", "fifo_mode", 0666)


            opensipsctlrc

            ## path to FIFO file

            OSIPS_FIFO="/tmp/opensips_proxy_fifo"


            Attempting to disable gateways via the CP gives the
            following errors:


            From DROUTING-Gateway interface:


            Error while disabling gateway 2
            (the GWID is 2 for the gateway I'm attempting to disable)

            From the MI Commands:
            Initiating the following command: *dr_gw_status 2 0*
            404 GW ID not found

            From the DROUTING-Gateway interface I am able to enable
            the interface if it is disabled
            I'm able to also enable the Gateway from the MI
            Commands section.

            I'm also able to enable and disable the Gateway using
            opensipsctl fifo commands

            opensipsctl fifo dr_gw_status 2

            Enabled:: yes

            opensipsctl fifo dr_gw_status 2 0

            opensipsctl fifo dr_gw_status 2

            Enabled:: no

            opensipsctl fifo dr_gw_status 2 1

            opensipsctl fifo dr_gw_status 2

            Enabled:: yes


            Not sure where the problem is but I feel its somewhere
            in the syntax of how its delivered. I'm sure it's
            something easy I've overlooked. Any help on this?

            Thanks
            Jeff


            _______________________________________________
            Users mailing list
            Users@lists.opensips.org <mailto: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

Reply via email to