Michel de Boer
michel at twinklephone.com
Sat Aug 23 15:11:38 CEST 2008
Type: KDE Telephony
Depend: Qt 3.x
Twinkle is a soft phone for your voice over IP
and instant messaging communcations using the SIP
protocol. You can use it for direct IP phone to IP
phone communication or in a network using a SIP
proxy to route your calls.
Some of the features offered are call waiting,
call hold, 3-way conference call, call transfer,
and call reject. It supports STUN or a statically
configured public IP address for NAT traversal.
When using STUN, it will send keep-alive packets
to keep NAT bindings alive. It supports ZRTP for
secure voice communication.
- Send file attachment with instant message.
- Show timestamp with instant messages.
- Instant message composition indication (RFC
- Persistent TCP connections with keep alive.
- Do not try to send SIP messages larger than 64K
- Integration with libzrtcpp-1.3.0
- Xsession support to restore Twinkle after system
- Call snd_pcm_state to determine jitter buffer
exhaustion (some ALSA
implementations gave problems with the old
- SDP parser allows SDP body without terminating
- Russian translation.
- SIP parser did not allow white space between
header name and colon.
- With "send in-dialog requests to proxy" enabled
mode set to "auto", in-dialog requests are
wrongly sent via TCP.
- Crash when a too large message is received.
- Comparison of authentication parameters (e.g.
algorithm) were case-sensitive.
These comparisons must be case-insensitive.
- SDP parser could not parse other media
transports than RTP/AVP.
- Twinkle sent 415 response instead of 200 OK on
in-dialog INFO without body.
- Twinkle responds with 513 Message too large on
an incoming call.
- ICMP error on STUN request causes Twinkle to
- Add received-parameter to Via header of an
incoming request if it contains
an empty rport parameter (RFC 3581)
- Twinkle did not add Contact header and copy
to 180 response.
RFC 3994 - Indication of Message Composition for
More information about the Kde-announce-apps