[Freeswitch-users] Fscomm unable to detect devices

[Rob Dyck]

After figuring out how to get portaudio to build and install, I thought I would 
get somewhere. Alas, it was not to be.

Attempting to load mod_portaudio put me back where I started - no devices

2010-03-17 23:51:02.007720 [ERR] mod_portaudio.c:980 Cannot find an input 
device
2010-03-17 23:51:02.009147 [ERR] mod_portaudio.c:990 Cannot find an input 
device                                                                        
2010-03-17 23:51:02.009147 [CRIT] switch_loadable_module.c:882 Error Loading 
module /usr/local/freeswitch/mod/mod_portaudio.so                          
**Module load routine returned an error** 

Probably, I can't test tomorrow. It's my day with the grandchildren.

RD

On Wednesday 17 March 2010 09:17:51 pm João Mesquita wrote:
> I think that the problem is that the core is not able to find the
> modules....
> 
> Try installing the mods on /usr/local/freeswitch/mods. My guess is that
> everything will load just fine.
> 
> Regards,
> João Mesquita
> 
> On Wed, Mar 17, 2010 at 10:46 PM, Rob Dyck <robert.dyck at shaw.ca> wrote:
> > 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.