Incidentally have you checked the output of ifconfig?

Does your server have an interface with 192.168.1.5 currently assigned to it? Is that active UP and RUNNING? Perhaps the network has gone down, got unplugged, lost its IP, had a hardware fault or some other failure. That would prevent sofia binding to that IP because it's then an IP no longer assigned to the server.

-Steve




On 18 June 2013 20:32, Steven Ayre <steveayre@gmail.com> wrote:
That internal profile is a skinny not sofia profile


On 18 June 2013 20:05, Oleg Khovayko <khovayko@gmail.com> wrote:
I checked. Everything seems OK

[root@olegh /usr/local/freeswitch/conf]# grep 192.168.1.5
../log/freeswitch.xml.fsxml
       FreeSWICH will default to 192.168.1.5 unless changed. Changing
this setting does
       <param name="h323-ip" value="192.168.1.5"/>
     <param name="ip" value="192.168.1.5"/>
     <param name="rtp-ip" value="192.168.1.5"/>
     <param name="sip-ip" value="192.168.1.5"/>
     <param name="rtp-ip" value="192.168.1.5"/>
     <param name="sip-ip" value="192.168.1.5"/>
[root@olegh /usr/local/freeswitch/conf]#



Seems like "port" value is suspicious (2000), when I expecting 5060:

<profile name="internal">
   <settings>
     <param name="domain" value="olegh.ath.cx"/>
     <param name="ip" value="192.168.1.5"/>
     <param name="port" value="2000"/>
     <param name="patterns-dialplan" value="XML"/>
     <param name="patterns-context" value="skinny-patterns"/>
     <param name="dialplan" value="XML"/>
     <param name="context" value="default"/>
     <param name="keep-alive" value="60"/>
     <param name="date-format" value="D/M/Y"/>
     <param name="odbc-dsn" value=""/>
     <param name="debug" value="4"/>
     <param name="auto-restart" value="true"/>
   </settings>
   <device-types>
     <device-type id="Cisco ATA 186">
         <param name="firmware-version" value="ATA030101SCCP04"/>
     </device-type>
   </device-types>
</profile>

but, anyway - when profile generates error, it prints correct port:

nta: sip:mod_sofia@:*5060*;maddr=192.168.1.5: invalid bind URL


OK.. If problem cannot be resolved - I will try migrate to yate...




On 6/18/2013 2:21 PM, Brian West wrote:
> this is the ticket.
>
> Check your fsxml in $BASE/log/  bet you the ip isn't in the right spot or you need to update.
>
> /b
>
> On Jun 18, 2013, at 11:23 AM, Oleg Khovayko <khovayko@gmail.com> wrote:
>
>> *nta: sip:mod_sofia@:5060;maddr=192.168.1.5: invalid bind URL*
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting@freeswitch.org
> http://www.freeswitchsolutions.com
>
> FreeSWITCH-powered IP PBX: The CudaTel Communication Server
> http://www.cudatel.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org