Fscomm unable to detect devices
16987 on Fedora I realize fscomm is an immature project. I get an error message when it tries to detect my devices ( pci sound card, usb handset, usb camera with microphone ). Is this the expected result? Detection works in Twinkle and Ekiga. Second question - is video support on the roadmap?
FSComm interfaces with sound devices via portaudio at this point. If portaudio can't use your devices correctly that would cause it not to work in any portaudio application including FSComm. What version of Fedora? I'm sure this is fixable but really depends more on the underlying system more than code in FSComm. -- W
F11, KDE4.4.1, pulseaudio Is portaudio another sound server? RD On Tuesday 16 March 2010 11:29:32 am William Suffill wrote:
FSComm interfaces with sound devices via portaudio at this point. If portaudio can't use your devices correctly that would cause it not to work in any portaudio application including FSComm.
What version of Fedora? I'm sure this is fixable but really depends more on the underlying system more than code in FSComm.
-- W
PortAudio is a free, cross platform, open-source<http://www.portaudio.com/license.html>, audio I/O library. It lets you write simple audio programs in 'C' that will compile and run on many platforms <http://www.portaudio.com/status.html>including *Windows, Macintosh (8,9,X), Unix (OSS), SGI, and BeOS*. PortAudio is intended to promote the exchange of audio synthesis software between developers on different platforms. PortAudio provides a very simple API for recording and/or playing sound using a simple callback function. Example programs are included that synthesize sine waves and pink noise, perform fuzz distortion on a guitar, list available audio devices, etc. http://www.portaudio.com/ http://wiki.freeswitch.org/wiki/Mod_portaudio Technically it is possible to get portaudio based applications to work with pulseaudio but it seems to be an area of some difficulties now that pulseaudio is used by default by newer distros. I've had this same issue on my system w/ pulseaudio since it wants to control all the sound devices itself. Killing pulseaudio should release the devices and partaudio should detect them in that case. Not a long term fix I know but still yet to spend enough time to discover the best alternative. https://tango.0pointer.de/pipermail/pulseaudio-discuss/2009-January/003037.h... seems to indicate that it has been an area of confusion for some time. -- W
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
Thanks for the help W! João Mesquita On Tue, Mar 16, 2010 at 6:36 PM, William Suffill <william.suffill@gmail.com>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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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
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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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@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@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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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@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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users
_______________________________________________ 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
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@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.
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@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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users
_______________________________________________ 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
_______________________________________________ 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
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@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.
Rob Dyck <robert.dyck@shaw.ca> wrote:
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
I've seen this before; it was a permission problem, solved by adding the freeswitch user to the audio group so that it could access the ALSA devices. Whether this is the cause in your case depends on how your operating system controls access to audio devices.
participants (4)
-
Jason White
-
João Mesquita
-
Rob Dyck
-
William Suffill