[Olympus developers 468]: Re: documentation on Skyper?

José P. González-Brenes joseg at cs.cmu.edu
Wed Feb 19 13:28:10 EST 2014


I worked on a VOIP implementation a long time ago.  (There might be some
code/branch in the SVN).

I used a third-party driver that creates a virtual soundcard that
writes/reads from a network socket.  Just a thought.


--
José P. González-Brenes
www.josepablogonzalez.com


On Wed, Feb 19, 2014 at 8:51 AM, Nitin Dhawan <nitin at imarketingadvantage.com
> wrote:

> Is there any guidance/headstart in this direction?
>
>
>
> *From:* Aasish Pappu [mailto:aasishp at gmail.com]
> *Sent:* Wednesday, February 19, 2014 6:48 PM
>
> *To:* Nitin Dhawan
> *Cc:* olympus-developers
> *Subject:* Re: [Olympus developers 460]: Re: documentation on Skyper?
>
>
>
> I still think you may want to pursue in the direction of freeswitch
> integrated into olympus. Mainly because freeswitch provides all the
> telephony infrastructure with a slew of protocols (googletalk, SIP, skype,
> regular telephone).
>
>
>
> On Wed, Feb 19, 2014 at 8:13 AM, Aasish Pappu <aasishp at gmail.com> wrote:
>
> That's one way to look at the problem. I would think of something more
> scalable rather than device ids (meaning multiple physical devices). You
> could try writing the audio data to a network socket and forward it to the
> audio server. You will have to convert the audio server to accept network
> stream as opposed to reading frm device. There is an example of such
> instance in this branch.
>
>
>
> The audioserver reads the data from a socket and there's an audio client
> that feeds this data.
>
>
>
>
>
> http://trac.speech.cs.cmu.edu/repos/olympus/branches/networkoly/
>
>
>
>
>
> On Wed, Feb 19, 2014 at 8:08 AM, Nitin Dhawan <
> nitin at imarketingadvantage.com> wrote:
>
> From what we understand now , I believe we have to add Skype's device id
>  to the Audio Server configuration. And we will need more than one audio
> server to take care of
>
> a.       Skype
>
> b.      Telephony
>
> c.       Local Microphone Input
>
>
>
> Are we on the right track?
>
>
>
> *From:* Nitin Dhawan [mailto:nitin at imarketingadvantage.com]
> *Sent:* Wednesday, February 19, 2014 12:18 AM
> *To:* olympus-developers (olympus-developers at cs.cmu.edu)
> *Subject:* RE: documentation on Skyper?
>
>
>
> I am able to start Skyper at the start and see it in process monitors. But
> it does not seem to start real server for some reason.
>
>
>
> This is what I have done so far.
>
> a.       I add [Skyper] to Servers  RoomLine-hub.pgm
>
> b.      To startlist_sapi.config, I add
>
> PROCESS: "$OLYMPUS_BIN\skyper"
>
> PROCESS_MONITOR_ARGS: --start
>
> PROCESS_TITLE: SKYPER
>
>
>
> When I start the skyper.exe independently -  it seems to be connecting
> with skype just fine. But when I call in from another skype account into
> this, it does not start a session, and it crashes.  It is not connected to
> the hub instance also like this.
>
>
>
> *From:* Nitin Dhawan [mailto:nitin at imarketingadvantage.com<nitin at imarketingadvantage.com>]
>
> *Sent:* Tuesday, February 18, 2014 7:38 PM
> *To:* olympus-developers (olympus-developers at cs.cmu.edu)
> *Subject:* documentation on Skyper?
>
>
>
> We found skyper within the main code. But we are not able to configure it
> properly. Can someone suggest the right way to configure or if there is any
> documentation.
>
>
>
> Thanks in advance.
>
>
>
>
>
> --
> Aasish Pappu
>
>
>
>
>
> --
> Aasish Pappu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20140219/262e9e68/attachment.html>


More information about the Olympus-developers mailing list