VoIP client

[Stephan Hermann]

Hi Udo,

Am Sonntag, den 18.09.2005, 12:01 +0200 schrieb Udo Puetz:
> On Sun, 18.09.05, Stephan Hermann <sh at sourcecode.de> wrote:

> > It works ;) But it's not mature enough to be used by endusers, there is
> > a lot of work to do...advantage of shtoom is: it's written in python, so
> > you can easily change some source :)
> 
> I see it's advantage of core library -> different gui interfaces but, lets
> face it, it's rather old now. You really have to show it some love to get it
> working.

Yes...let's see what we can do :)


> > I just had a look on minisip. I think next week I will test it and
> > prepare some packages.
> > 
> > Let's see how it works..nevertheless, I don't think encryption is a
> > standard now for SIP.
> 
> I looked a little into SIP the last few days and yes, encrytion isn't
> standard in SIP. But the way minisip does it is in my eyes rather logical,
> it's not some mumbo jumbo with proprietary stuff but uses standard libs and,
> since the authors of minisip have developed the encrytion part as part of
> their master thesis, I tend to think it's well researched and thought
> through. And minisip also works without the encrytion stuff so it's a bonus,
> not a hindrance. I for one are in favor of encryption :) and it might also
> be a selling point (over e.g. skype): "look, with minisip you are using the
> standard and can communicate to all the other sip users and your talk is
> secured from eavesdropping!"

Right, but it makes no sense to have one client with, even with
opensource libs, encryption, when it's not in the standards. You can't
encrypt voip streams between lets say kphone and minisip or between
minisip and other hardware phones.

And actually, we're waiting as well for Phils solution ;)

Have a nice, sunny, Sunday :)

\sh