[Freeswitch-users] Fscomm unable to detect devices

[Rob Dyck]

I couldn't remember if I had done an install so I ran it. It didn't make any 
difference though.

Some observations
Freeswitch is not installed in my usual path
Fscomm is not installed by make install
Fs_cli only works if I start freeswitch first
Pa list ( as you suggested earlier ) is not a valid command

Here is the output of lsof -i
fscomm  642 rdyck   12u  IPv4 230854      0t0  UDP 192.168.1.3:57205-
>192.168.1.99:nat-pmp 
fscomm  642 rdyck   24u  IPv4 231766      0t0  UDP 192.168.1.3:italk 
fscomm  642 rdyck   25u  IPv4 231767      0t0  TCP 192.168.1.3:italk (LISTEN)
fscomm  642 rdyck   28u  IPv4 231902      0t0  TCP localhost.localdomain:oa-
system (LISTEN)

I could not find anything in the netstat output that pertained to freeswitch or 
fscomm.


On Wednesday 17 March 2010 04:37:01 pm João Mesquita wrote:
> No, not at all. Do a lsof -i or a netstat. You should be able to see it all
> there. Oh! Wait! Have you made a "make install" on freeswitch trunk?
> 
> Regards,
> João Mesquita
> 
> On Wed, Mar 17, 2010 at 4:51 PM, Rob Dyck <robert.dyck at shaw.ca> wrote:
> > I can see a process for fscomm. Should I be seeing a process for the
> > core.
> > 
> > When starting fscomm it reports -
> > Initializing globals...
> > 
> > Initializing core...
> > 
> > Everything OK, Entering runtime loop ...
> > 
> > BTW, not Windows but Fedora 11, KDE flavour
> > 
> > Thanks for looking into this
> > RD
> > 
> > On Wednesday 17 March 2010 05:01:15 am João Mesquita wrote:
> > > Rob, I believe that the core has failed to load. I have not added any
> > 
> > type
> > 
> > > of check on the code level for those cases yet as I believed it would
> > 
> > never
> > 
> > > really fail to load. Those cases have been more frequent than what I
> > > originally expected so I will add that to code today (hopefully later
> > > tonight).
> > > 
> > > Meanwhile, what you can do is check if the ports are open or not on the
> > 
> > OS.
> > 
> > > I am not sure how to do that on Windows. Or, maybe we already have logs
> > 
> > on
> > 
> > > the log folder?
> > > 
> > > Regards,
> > > João Mesquita
> > > 
> > > On Wed, Mar 17, 2010 at 4:49 AM, Rob Dyck <robert.dyck at shaw.ca> wrote:
> > > > Is there something wrong with my build?
> > > > 
> > > > fs_cli yields "[ERROR] libs/esl/fs_cli.c:1181 main() Error Connecting
> > > > [Socket
> > > > Connection Error]" with fscomm running.
> > > > 
> > > > RD
> > > > 
> > > > On Tuesday 16 March 2010 02:36:28 pm William Suffill wrote:
> > > > > With FSComm running you can use fs_cli to try pa list. If u can't
> > 
> > list
> > 
> > > > the
> > > > 
> > > > > devices that would be the problem. I'm going to try to dig into
> > > > > this further on 1 of my desktops w/ pulseaudio.
> > > > > 
> > > > > -- W
> > > > 
> > > > _______________________________________________
> > > > 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
> > 
> > _______________________________________________
> > 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