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