Once again, thanks Eeri, Yes, the Pi will use a SIP account on a registrar - in fact these will be local device which is a combined H.323 Gatekeeper/SIP registrar. The intention is that they will be used in Education establishments for the purposes of providing real time translation services for a live videoconferences (hence the need for only audio output). We actually have a solution in place, but it utilises Cisco IP phones running a SIP image - which is overkill and very expensive. However, the long term goal is to be able to make this portable and to be able to provide additional functionality. We can provide a configuration to register to the local SIP registrar which I hope can be achieved either through the built in Ethernet connection or a Wi-Fi adapter, but I would also like to incorporate an ability to call the device using a standard telephone call via GSM. I'm currently looking at 3G USB dongles that are capable to receiving GSM calls and I have seen similar deployment where a GSM call is handled by Asterisk then transferred to another device using a SIP trunk, however, I want PJSIP to reside on the same machine so get the GSM past to it. I'm pretty sure this is doable, but still - baby steps at the moment. Regards, Chris > -----Original Message----- > From: Eeri Kask [mailto:Eeri.Kask@xxxxxxxxxxxxxxxxxxxxx] > Sent: 11 January 2014 19:08 > To: pjsip at lists.pjsip.org > Subject: Re: Can't find audio device on Raspberry Pi > > On Sat, 11 Jan 2014 16:28:56 -0000, "Swinney C." wrote: > > > > ./pjsua-armv6l-unknown-linux-gnu --capture-dev=02 > > --playback-dev=00 --auto-answer=200 > > > > I now need to look at the Python code in order that I can create an > > application that starts automatically on boot with the correct account > > info and uses the devices as outlined above - but I have finally made > > a start! > > > If starting pjsua as given above is all you need then you probably don't need > python. According to how linux runlevels work on your platform, update > some boot-time user-configurable shell script (like "rc.local" or something), > e.g. in /etc/init.d/ or somewhere else, then put > > /usr/local/bin/pjsua-armv6l-unknown-linux-gnu --config-file=/etc/rc.pjsua > > into it, finally put > > --capture-dev=02 --playback-dev=00 --auto-answer=200 -- > registrar=sip:example.org --realm=example.org --id=sip:user at example.org - > -contact=sip:user at example.org --username=loginname --password=secret > > > into /etc/rc.pjsua, make it 'chmod 400', owned by root, and that should be it, > not? > > (Assuming you have SIP-address "sip:user at example.org" and an account > with credentials "loginname" and "secret" on that server.) > > Eeri Kask > >
