Thank you for your reply.
OK, but pardon my ignorance, but how do I do that?
I am guessing here, but does that mean that for the 'inside' IP (192.168.nn.nn) I use the conf\sip_profiles\internal.xml file and define sip_ip and rtp_ip specifically -- not using the $$(internal_etc...) references?
If so, OK
But how do I define the 'outside' (107.1.nnn.nn) sip?
Do I do it in the conf\sip_profiles\external.xml file?
And, if so, what do I put there?
Thanks,
TF
--------------------------------------------
On Tue, 3/31/15, Steven Ayre <steveayre@gmail.com> wrote:
Subject: Re: [Freeswitch-users] Question re: local_ip_v4
To: "FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org>
Date: Tuesday, March 31, 2015, 7:21 AM
-----Inline Attachment Follows-----
You want
to configure 2 sofia profiles, one listening on each
IP.
It might be simpler to
define the IPs within the profiles rather than in
vars.conf.xml (where you're just setting variables that
are referenced elsewhere).
On 30 March 2015 at 21: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
_________________________________________________________________________
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
_________________________________________________________________________
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