linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Linphone 3.5.0 on Blackfin


From: Cameron Barfield
Subject: Re: [Linphone-developers] Linphone 3.5.0 on Blackfin
Date: Fri, 06 Jan 2012 14:41:10 -0800
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16

Thanks for the tip!

Setting up a half-duplex call (receive only) works. I'm able to play incoming audio and my CPU only runs around 1%.

Now to figure out why the soundread process is tanking my board...




On 01/06/2012 09:09 AM, M Walton wrote:
Hi,

I have just finished getting oSip 3.5, eXosip 3.5 and Linphone 3.5
running on a BF537 with uClinux 2010 RC5 and did not see the problem you
speak of.

However, if it helps, i am not using the soundcard or video of the
hardware, in fact i am using a custom plugin to deal with the audio in
and out and putting it back on the network, thus skipping any ALSA/OSS
processing - so maybe the issue you see is related to using the hardware
directly for audio/video processing?

Hope it helps

On 01/05/2012 01:26 PM, Cameron Barfield wrote:
Hi, All --

I'm trying to get Linphone 3.5.0 running on Blackfin (BF527), but I'm
running into some problems.

When I try to establish a call (either inbound or outbound), I get the

ring or ringback tone, but when the call is accepted, my CPU usage
spikes to 96-100% and linphonec becomes unresponsive. When I hang up
on the remote end, the BYE message isn't always seen by linphone.
Whether or not the BYE message is seen, linphonec continues to eat up
96-100% of my CPU usage until I issue a kill -9 on it.

I'm still trying to narrow down where the problem is, but I'm
wondering if anyone else has run into this or has any ideas.

Thanks.


_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers




reply via email to

[Prev in Thread] Current Thread [Next in Thread]