local_ip_v4 and local_ip_v6 will always resolve to the IP on the interfaces that can reach the internet. Anything else such as your setup will require you to set the values on the sofia profiles specifically. On Tue, Mar 31, 2015 at 4:02 AM, Vallimamod Abdullah <vma@440hz.fr> wrote:
Hi,
Try to set the following in your internal profile:
<param name="sip-ip" value="$${internal_sip_ip}”/> <param name="rtp-ip" value="$${internal_rtp_ip}"/>
along with the following in 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”/>
Keep also in mind that you need to restart freeswitch everytime you change any X-PRE-PROCESS statement.
Best Regards, Vallimamod .
On 30 Mar 2015, at 22:57, T Fred Farmington <tfred31@yahoo.com> wrote:
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- *Brian West* brian@freeswitch.org *Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com ClueCon 2015 Call for Speakers <https://www.cluecon.com/call-for-speakers/> | Register <https://freeswitch.com/cart.php?gid=1> TODAY! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest