Hi,

 

Suppose a freeswitch configuration has the following defined in event_socket.conf.xml:

 

<configuration name="event_socket.conf" description="Socket Client">

  <settings>

    <param name="nat-map" value="false"/>

    <param name="listen-ip" value="0.0.0.0"/>

    <param name="listen-port" value="8021"/>

    <param name="password" value="ClueCon"/>

    <!--<param name="stop-on-bind-error" value="true"/>-->

               

     <param name="apply-inbound-acl" value="localnet.auto"/>

                <list name="localnet.auto" default="allow">

                                <node type="allow" cidr="10.47.26.28/32"/>

                </list>

  </settings>

</configuration>

 

The above configuration will allow a remote PC with an IP address of 10.47.26.28 to issue commands to freeswitch (e.g. bgapi).

 

Now, suppose we wanted to update the apply-inbound-acl list like this:

 

     <param name="apply-inbound-acl" value="localnet.auto"/>

                <list name="localnet.auto" default="allow">

                                <node type="allow" cidr="10.47.26.28/32"/>

                                <node type="allow" cidr="10.47.26.44/32"/>

                </list>

 

The list has been updated to allow a remote PC with an IP address of 10.47.26.44 to connect to freeswitch.

 

The only way to get this to work is to restart freeswitch. We were wondering if there is another way that would not require a stop & start of freeswitch.

 

The following has already been tried:

 

-          Moved the apply-inbound-acl to acl.conf.xml. Invoke the “reloadxml” and “reloadacl” commands

 

Thanks,

Steve

NOTE: This e-mail (including any attachments) is for the sole use of the intended recipient(s) and may contain information that is confidential and/or protected by legal privilege. Any unauthorized review, use, copy, disclosure or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please notify Mitel immediately and destroy all copies of this e-mail. Mitel does not accept any liability for breach of security, error or virus that may result from the transmission of this message.