Hi, >From the sndtest result, it seems the sound device worked fine. So the error may be related to resample stuff (e.g PJMEDIA_RESAMPLE_IMP set to PJMEDIA_RESAMPLE_NONE). Please try to add --clock-rate 8000 to the pjsua.config file. Regards, nanang On Thu, Sep 18, 2008 at 10:58 PM, P.Muge Ersoy <muge.ersoy at gmail.com> wrote: > Thanks for the tip > > The capture device i want to use is the VOIP USB phone .I tested it with the > binary and it seems allright.. > > root at IP:/# ./sndtest-sh4-linux --id 0 > 22:02:10.181 sndtest.c Found 3 devices: > 22:02:10.183 sndtest.c 0: VOIP USB Phone : USB Audio > (hw:0,0) (capture=1, playback=1) > 22:02:10.184 sndtest.c 1: default (capture=128, playback=128) > 22:02:10.184 sndtest.c 2: /dev/dsp (capture=16, playback=16) > 22:02:10.203 sndtest.c Testing playback device VOIP USB > Phone : USB Audio (hw:0,0) > 22:02:10.204 sndtest.c Testing capture device VOIP USB Phone > : USB Audio (hw:0,0) > 22:02:10.411 sndtest.c Please wait while test is in progress (~11 > secs).. > 22:02:21.684 sndtest.c Dumping results: > 22:02:21.684 sndtest.c Parameters: clock rate=8000Hz, 80 > samples/frame > 22:02:21.684 sndtest.c Playback stream report: > 22:02:21.685 sndtest.c Duration: 10s.020 > 22:02:21.685 sndtest.c Frame interval: min=0.062ms, max=45.741ms > 22:02:21.686 sndtest.c Jitter: min=5.971ms, avg=19.976ms, > max=45.677ms > 22:02:21.686 sndtest.c Capture stream report: > 22:02:21.686 sndtest.c Duration: 10s.020 > 22:02:21.686 sndtest.c Frame interval: min=0.075ms, max=45.708ms > 22:02:21.688 sndtest.c Jitter: min=5.992ms, avg=19.940ms, > max=45.624ms > 22:02:21.689 sndtest.c Checking for clock drifts: > 22:02:21.689 sndtest.c No clock drifts is detected > 22:02:21.689 sndtest.c Test completed with some warnings > > > I added --capture-dev 0 to my config file than i run root at IP:/# > ./pjsua-sh4-linux --config-file pjsua.config > It gave below error and teminated.. > > 22:06:24.446 pjsua_core.c pjsua version 0.9.0-release for > sh4-unknown-linux-gnu initialized > 22:06:30.735 pjsua_acc.c Registration sent > 22:06:46.301 pjsua_acc.c IP address change detected for account 2 > (192.168.0.224:5060 --> 213.143.229.18:40653). Updating registration.. > 22:06:46.303 pjsua_acc.c Unregistration sent > 22:06:46.307 pjsua_acc.c Registration sent > 22:06:46.428 pjsua_media.c Unable to open sound device: Invalid operation > (PJ_EINVALIDOP) [status=70013] > 22:06:46.439 pjsua_acc.c Unable to create/send REGISTER: Object is busy > (PJSIP_EBUSY) [status=171001] > 22:06:46.508 pjsua_acc.c sip:60000004 at turktelekom.com.tr: registration > success, status=200 (OK), will re-register in 3600 seconds > > Any idea? > > On Thu, Sep 18, 2008 at 5:12 PM, Nanang Izzuddin <nanang at pjsip.org> wrote: >> >> Hi, >> >> What about sndtest for each device below? (e.g "sndtest-xxxx --id >> 0/1/2"). Just FYI, pjsua also has parameter to set playback and >> capture device, so in case the sndtest shows good result on a device, >> you can try to run pjsua using that device. >> >> Regards, >> nanang >> >> >> On Thu, Sep 18, 2008 at 8:40 PM, P.Muge Ersoy <muge.ersoy at gmail.com> >> wrote: >> > I run sndinfo on the board and here is the output below; >> > >> > 19:48:54.434 os_core_unix.c pjlib 1.0-rc1 for POSIX initialized >> > 19:48:55.495 pasound.c PortAudio sound library initialized, >> > status=0 >> > 19:48:55.495 pasound.c PortAudio host api count=2 >> > 19:48:55.496 pasound.c Sound device count=3 >> > 19:48:55.499 pjlib select() I/O Queue created (0x487b74) >> > Device #00: >> > Name : VOIP USB Phone : USB Audio (hw:0,0) >> > # of input channels : 1 >> > # of output channels: 1 >> > Default clock rate : 8000 Hz >> > >> > Device #01: >> > Name : default >> > # of input channels : 128 >> > # of output channels: 128 >> > Default clock rate : 44100 Hz >> > >> > Device #02: >> > Name : /dev/dsp >> > # of input channels : 16 >> > # of output channels: 16 >> > Default clock rate : 44100 Hz >> > >> > >> > It recognize the sound device which is a usb phone . I run another sip >> > stack >> > with media stack , sound was working. >> > >> > What might be the problem ? >> > >> > Regards >> > Muge >> > >> > On Mon, Sep 8, 2008 at 6:55 PM, Nanang Izzuddin <nanang at pjsip.org> >> > wrote: >> >> >> >> Try to run snd_info & snd_test for each sound device (they should be >> >> in pjsip-apps/bin/samples directory), just to make sure whether the >> >> existing pjmedia sound device abstraction (pasound.c in this case) can >> >> works on your board. If it is not working, then you may need to follow >> >> the quoted doc above, creating your own sound device wrapper. Here is >> >> the doc of sound device interface (sound.h): >> >> http://www.pjsip.org/pjmedia/docs/html/group__PJMED__SND.htm >> >> There are some samples of sound device wrapper implementation: >> >> pasound.c, symbian_sound[_aps].c, dsound.c >> >> >> >> Btw, since PJSIP sound device implementation on Linux is using >> >> PortAudio, it may also be useful to find related topics from PortAudio >> >> forums/mailing list archive. >> >> >> >> Regards, >> >> nanang >> >> >> >> >> >> On Mon, Sep 8, 2008 at 9:15 PM, P.Muge Ersoy <muge.ersoy at gmail.com> >> >> wrote: >> >> > Hi All; >> >> > >> >> > I am having trouble about sound on st linux. I compiled the pjsua and >> >> > had >> >> > two assertion. First one was; >> >> > >> >> > "pjsua-sh4-unknown-linux-gnu: >> >> > src/../../../portaudio/src/common/pa_front.c:352: Pa_Initialize: >> >> > Assertion >> >> > `"PortAudio: compile time and runtime endianness don't match" && >> >> > (((char >> >> > *)&nativeOne)[0]) == 0' failed. >> >> > little endian a set ediyoruz pa_endianness.h " >> >> > >> >> > I set it to little endian manually.. Second one was ; >> >> > >> >> > pjsua-sh4-unknown-linux-gnu: >> >> > src/../../../portaudio/src/hostapi/alsa/pa_linux_alsa.c:837: >> >> > BuildDeviceList: Assertion `devIdx < numDeviceNames' failed. >> >> > pa_linux_alsa.c >> >> > >> >> > I simply command out it. >> >> > >> >> > I compiled and when i started pjsua it loaded and registered >> >> > successfully >> >> > ... I made call, connection establish but there was no sound. >> >> > >> >> > There is Alsa driver register on the ST board; >> >> > >> >> > Advanced Linux Sound Architecture Driver Version 1.0.11rc4 (Wed Mar >> >> > 22 >> >> > 10:27:24 >> >> > 2006 UTC). >> >> > ALSA device list: >> >> > #0: STb7100_PCM0 >> >> > #1: STb7100_PCM1 >> >> > #2: STb7100_SPDIF >> >> > #3: STb7100_CNV >> >> > >> >> > I saw below at documentation page; >> >> > >> >> > "Use your own sound device abstraction, rather than PortAudio. If you >> >> > are >> >> > porting PJSIP to an embedded platform, you will need to create your >> >> > own >> >> > sound device abstraction. So supposing we don't use PortAudio and use >> >> > the >> >> > NULL sound device implementation >> >> > (PJMEDIA_SOUND_IMPLEMENTATION=PJMEDIA_SOUND_NULL_SOUND), we will >> >> > reduce >> >> > executable size by approximately 49 KB." >> >> > >> >> > Actually i didn't quite get the meaning of sound device abstraction ? >> >> > How >> >> > would it be done ? >> >> > >> >> > >> >> > Regards >> >> > Muge >> >> > >> >> > _______________________________________________ >> >> > Visit our blog: http://blog.pjsip.org >> >> > >> >> > pjsip mailing list >> >> > pjsip at lists.pjsip.org >> >> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Regards, >> >> nanang >> >> >> >> _______________________________________________ >> >> Visit our blog: http://blog.pjsip.org >> >> >> >> pjsip mailing list >> >> pjsip at lists.pjsip.org >> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> > >> > >> > _______________________________________________ >> > Visit our blog: http://blog.pjsip.org >> > >> > pjsip mailing list >> > pjsip at lists.pjsip.org >> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> > >> > >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >
