[Freeswitch-users] setting up freeswitch on virtualbox configuring Localconnections

[Steven Ayre]

The profile on 127.0.0.1 is your problem. You need the profile to be bound
to the 192.168.56.X assigned to the VM by DHCP

127.0.0.1 is Loopback, on the VM its only reachable from on the VM. There's
no such mapping.


On Wednesday, June 19, 2013, Beto A wrote:

> It was restarted...I just double checked and got:
> No chain/target/match by that name
>
> when I run netstat -vaun
> I can see that 5060,5080 on 127.0.0.1 which I assume Virtualbox maps back
> to 192.168.56.255 <http://192.168.56.255:22/> not sure where else to look.
>
> thanks again.
> -r
>
>   ------------------------------
>  *From:* Steven Ayre <steveayre at gmail.com <javascript:_e({}, 'cvml',
> 'steveayre at gmail.com');>>
> *To:* FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org<javascript:_e({}, 'cvml', 'freeswitch-users at lists.freeswitch.org');>>
>
> *Sent:* Wednesday, June 19, 2013 11:25 AM
> *Subject:* Re: [Freeswitch-users] setting up freeswitch on virtualbox
> configuring Localconnections
>
> That will disable the iptables script at startup, but it won't disable any
> firewall you've already started.
>
> See what this says: iptables -Ln
>
> -Steve
>
>
>
> On 19 June 2013 15:52, Beto A <astro_sk at yahoo.com> wrote:
>
> not bridging but host-only adapter
> first thing I do with local vm is chkconfig iptables off
>
> maybe something else on the vm blocking it?  I'm still digging
>
> cheers
> -B
>
>   ------------------------------
>  *From:* Claus Andersen <clan at wheel.dk>
>
> *To:* FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> *Sent:* Wednesday, June 19, 2013 9:14 AM
>
> *Subject:* Re: [Freeswitch-users] setting up freeswitch on virtualbox
> configuring Localconnections
>
> On Wed, 19 Jun 2013, Beto A wrote:
>
> > Thanks Steve,
> > Host adaptor works when I ssh (@192.168.56.255:22) into it but still
> times out when attempting  5060. "Failed - Request Timeout" from FSComm.
> >
> > any ideas?
>
> Might be too obvious but it has bitten me many a times. I assume that you
> are now bridging rather than port forwading. Have you remembered the
> firewall? Iptables is default on CentOS but will allow ssh.
>
> sudo service iptables status
> sudo service iptables stop
>
> Kind Regards,
> Claus Andersen
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at 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 at freeswitch.org
>  <http://www.freeswitchsolutions.com/>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130619/8cf15f11/attachment.html