[Freeswitch-users] Question re: local_ip_v4

[T Fred Farmington]

We have 2 network cards on our FS server.
*  One IP goes to the 'outside' world  (IP = 107.1.nn.nn)
*  And the other IP goes to the 'inside' world  (IP = 192.168.nn.nn)

In spite of making suggested changes to   vars.xml   when FS launches it sets itself up to 'listen' to the 'outside' world (IP = 107 etc.) 
But the result of that is that none of the in-house SIP phones can register to it.

The changes I made (following suggestions found on the web)  to   vars.xml   are as follows:
   New entry:
        <X-PRE-PROCESS cmd="set" data="local_ip_v4=192.168.nn.nn"/>   <!-- where nn values are 'real' values -->
   This new line was entered immediately before
       <X-PRE-PROCESS cmd="set" data="domain=$${local_ip_v4}"/>

Additionally another web reference suggested that the following 2 lines be added near the bottom of   vars.xml
      <X-PRE-PROCESS cmd="set" data="internal_sip_ip=192.168.nn.nn"/>
      <X-PRE-PROCESS cmd="set" data="internal_rtp_ip=192.168.nn.nn"/>
        
PROBLEM:   None of that seems to work.   
                    Even after not only ReStarting the FS Service, but also after ReStarting the FS Server itself and then Starting the FS Service

When through FS_CLI  I run:    sofia  status     and/or   sofia status profile internal      both of them show the 107 IP instead of the 192 IP
Those changes have not caused FS to 'see' and 'listen to' the 192  port.

What am I doing wrong?

Your advice/suggestions would be greatly appreciated.

Thanks
TF