OT: Twinkle cli

[Igor Gueths]

Hi Alonzo and all. I could have tried that, but didn't due to the fact that I
sort of presumed that Twinkle was no longer in active development, the last
release having been in February of 2009. FYI though, Linphone seems to still be
in active development, and as for the ZRTP issue, it seems that tacking Zfone on
can solve that problem fairly nicely indeed. A couple of problems I did have
with Twinkle that I couldn't seem to pin down, were that I couldn't find a way
to set my local IP different from 255.255.255.255. I eventually seemed to have
no choice but to recompile the binary after redefining AUTO_IP4_ADDRESS in sys.h
I think it was, which for me would not be an optimal solution at all. The other
problem I had was that while testing SIP and RTP connectivity between my laptop
and an Asterisk I have running on the same LAN, Twinkle would for some reason
send packets back to itself according to the log file. The only way I could seem
to preclude this behavior, was to set nat_public_ip, which for testing within
the local network, makes no sense because the client then adds the SIP via:
header to all outgoing requests. If anyone has found a way around the above two
issues, I'd be most definitely interested to hear it, else I'm afraid I'll be
sticking with Linphone for the time being.
On Fri, Jan 28, 2011 at 06:57:26AM -0600, Alonzo Cuellar wrote:
> Hello,
> 
> Email the creator and he will send you a twinkle.cfg file. I had a sample laying around, but i can't seem to find it. I'll look in another drive of mine and see if i can't find it. Good luck.
> 
> Alonzo
> 
> On Jan 26, 2011, at 11:40 AM, Igor Gueths wrote:
> 
> > Hi Kirk. Actually, it seems the Ncurses bits have already been done for us; the
> > only problem that remains however, is the fact that Twinkle itself seems unable
> > to build without at least a partial install of QT somewhere. Ideally I think
> > what we'd want to do is have some sort of flag in the configure script
> > (--enable-console-only for example), that would simply build the console
> > interface, and nothing else UI-wise. I also didn't notice any direct calls to
> > Ncurses or Readline for that matter while poking around the source tree
> > yesterday, so some reading through the files in src/gui is probably in order.
> > On Wed, Jan 26, 2011 at 07:52:50AM -0500, Kirk Reiser wrote:
> >> Hi Igor: I would be surprised if anyone here on this list knows much
> >> about how easy it would be to replace qt with ncurses but I'd say go
> >> for it and try.
> >> 
> >> We have played quite a bit with both twinkle and linphone and they
> >> both have advantages and drawbacks.  Yes twinkle supports zrtp but
> >> linphone supports ipv6 which twinkle does not.  Twinkle has a much
> >> nicer interface in console mode but linphone has better noise
> >> cancellation and echo control.  Linphone is not as robust as twinkle
> >> is however and likes to segfault whenever it gets a chance.
> >> 
> >> They can both be nice to use and iritating when they aren't working as
> >> advertised unfortunately.  So if we could get one feature rich stable
> >> sip client it would be nice.  If anyone knows of any other console
> >> based sip clients we don't know about it would also be useful to hear
> >> about them.
> >> 
> >> I would also like to invite folks interested in playing with sip and
> >> freeswitch to join us at sip:3000 at linux-speakup.org to play.  If we
> >> can get things all working correctly the possibilities seem endless.
> >> I am thinking of language channels for folks interested in learning
> >> and speaking various languages and all sorts of special interest
> >> discussion groups.  We have a fair way to go before we have it all
> >> figured out but the more the merrier from a discussion perspective.
> >> Hell, we might even be able to do a little tech support, who knows!
> >> 
> >> We are currently looking into getting chats working and a skype bridge
> >> up.  There are probably good windows soft phone clients but I don't
> >> know what they are.  I'd be interested in finding out how ekiga works
> >> for blinks also.
> >> 
> >>  Kirk
> >> 
> >> On Tue, 25 Jan 2011, Igor Gueths wrote:
> >> 
> >>> Hi all. I've lately started poking around Twinkle, and it almost seems that it
> >>> is possible to have the whole thing link against NCurses, instead of QT as is
> >>> the regular build procedure. Am I chasing shadows here, or is this indeed
> >>> possible? Twinkle looks much better than Linphone in my opinion, not to mention
> >>> that it supports ZRTP. Thanks.
> >>> --
> >>> Igor
> >>> 
> >>> -- 
> >>> This message has been scanned for viruses and
> >>> dangerous content by MailScanner, and is
> >>> believed to be clean.
> >>> 
> >>> _______________________________________________
> >>> Speakup mailing list
> >>> Speakup at braille.uwo.ca
> >>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>> 
> >> 
> >> --
> >> Kirk Reiser				The Computer Braille Facility
> >> e-mail: kirk at braille.uwo.ca		University of Western Ontario
> >> phone: (519) 661-3061
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup at braille.uwo.ca
> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >> 
> >> -- 
> >> This message has been scanned for viruses and
> >> dangerous content by MailScanner, and is
> >> believed to be clean.
> >> 
> > 
> > -- 
> > Igor
> > 
> > -- 
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.