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

An additional piece of information that may be helpful in determining what is going wrong..... After having the FS service up and running I attempt to Register a SIP phone by doing a ReStart on it. Its extension is 105 and there is an associated 'extension' xml file for 105 in the conf\directory\default directory (note - it used to work on another FS server) When that Registration attempt is 'seen' by FS I get the following message through FS_CLI: Can't find user [105@192.168.nn.nn] from <the phone's IP address> You must define a domain called <FS 'inside' IP address 192.168.nn.nn> in your directory and add a user with the ID '105' attribute and you must configure your device to use the proper domain in its authentication credentials I am sure that message is telling me something important, but I thought that I had already done everything that it is now telling me to do again. 1. I have extension 105 defined in the directory 2. I hope to have configured FS to 'see' domain 192.168.nn.nn as its internal SIP IP 3. I have the phone configured to Register on FS's 'internal' domain What is wrong? And, specifically what do I need to do to resolve this? Thanks TF -------------------------------------------- On Tue, 3/31/15, Vallimamod Abdullah <vma@440hz.fr> wrote: Subject: Re: [Freeswitch-users] Question re: local_ip_v4 To: "FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org> Date: Tuesday, March 31, 2015, 3:02 AM 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

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 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 -----Inline Attachment Follows----- _________________________________________________________________________ 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

OK Within the file: conf/directory/default.xml I specifically defined the <domain name="192.168.nn.nn"> to be the 'inside' IP which the SIP phones are to use. And in the conf/sip_profiles/internal.xml I defined sip-ip <== 'inside' IP rtp-ip <== 'inside' IP ext-sip-ip <== 'outside' IP ext-rtp-ip <== 'outside' IP Just in case I also put the same definitions into conf/sip_profiles/external.xml After a FS ReStart I still only see FS_CLI (sofia status) referring to the 'outside' IP And on doing a ReStart of the SIP phone, I still get the same error message as before as seen on FS_CLI Can't find user [105@192.168.nn.nn] from <the phone's IP address> You must define a domain called <FS 'inside' IP address 192.168.nn.nn> in your directory and add a user with the ID '105' attribute and you must configure your device to use the proper domain in its authentication credentials Obviously I am still missing something. Suggestions? Thanks TF

Again, thank you for your reply. OK, I'll make the change to ext-sip-ip and ext-rtp-ip and make them the same IP address as sip-ip and rtp-ip respectively I'll will readily set up 2 profiles once I understand how to do so. There is a simple description named: SETTING THE SIP PROFILES TO USE DIFFERENT ETHERNET PORTS on the previous FreeSWITCH wiki ( http://wiki.freeswitch.org/wiki/Multi_home_tutorial#INTERNAL_LAN ) And I did what they said to do there (except for making the mistake of not following their ext-sip-ip & ext-rtp-ip settings). But that did not seem to do what I need to do. I'll try it again with the ext- settings corrected and see how it goes. What about the phone registration problem where it cannot find the user [105@192.168.nn.nn] ? I thought that I had everything in place for that to work, but I cannot register any SIP phones because of that problem. 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, 12:17 PM You want to have ext-sip-ip and ext-rtp-ip the same as sip-ip and rtp-ip. Those settings are to handle some NAT situations where you're listening on your LAN IP but outside are visible on your nated WAN IP.

From what you descibed your box is assigned your external address directly in which case you need 2 profiles