| Re: Qt4 Port
Feb 25 2009 on content Twinkle |
Yes, I want to migrate Twinkle to Qt4/KDE4. I cannot promise when this will be done. |
|  | | Re: Re: Re: Kontact
Jul 1 2006 on content Twinkle |
Yes, put this command "twinkle --call %N" in the phone script hook in the configuration settings of KAddressbook. Optionally you can add the "--immediate" flag (see twinkle --help) |
| | | Re: translations
Jul 1 2006 on content Twinkle |
Thanks. I first have to externalize all texts before they can be translated. |
| | | Re: Kontact
Jul 1 2006 on content Twinkle |
When you build Twinkle on a KDE machine, then the KAddressbook interface should be available (the address button next to dial) |
| | | Re: Re: Re: COmpilat
May 2 2006 on content Twinkle |
This is a bug in commoncpp2-1.3.26 I have been told that this will be solved with 1.4.0 For now, you should use an older version if you want to compile Twinkle. |
| | | Re: COmpilation Prob
Apr 30 2006 on content Twinkle |
It seems the problem is with the commoncpp2 package. I don't know what exactly causes this problem. I still have commoncpp2-1.3.21 on my SuSE system. |
| | | Re: Re: Re: Micro do
Nov 24 2005 on content Twinkle |
www.sipphone.com or www.freeworlddialup.com have echo services. |
| | | Re: Micro doesn't wo
Nov 21 2005 on content Twinkle |
There might be many causes for this. You say you see that data is transmitted. I assume you see that Twinkle sends out RTP packets. If it does, you might want to check if the RTP packets really contain sound (ehtereal can convert an RTP stream into an audio file).
If the outgoing RTP stream is fine, then your friend would have to check if he really receives your RTP stream. If your friend is behind a NAT then that might cause problems. NAT are a pain for SIP based VoIP. If it is the NAT device causing the problems, you'd have to check things like STUN or try static NAT bindings in the NAT device (STUN is not a fool proof solution).
HTH |
| | | Re: Yeah! Grat softw
Nov 19 2005 on content Twinkle |
I have them on my todo list. |
| | | Re: Re: Re: outgoing
Aug 12 2005 on content Twinkle |
I understand your confusion. Twinkle displays the next hop for the REGISTER which indeed isn't truly the registrar.
I have registered multiple endpoints without problems. Twinkle does support multiple contacts. In your case however it seems Twinkle does not recognize the contact header for some reason. Maybe a bug in the parser or a syntax error in the contact header.
I don't know why Twinkle seems to loose a Route header. It shouldn't.
If you want, can you send a SIP trace for the multiple contacts and Record-Route case to my e-mail address? Then I can have a look at it and if there is a bug, I can fix it. |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
