Twinkle

A standard library with C++11 support (at least version 4.9 for libstdc++) ucommon GNU uCommon C++ ccRTP (version = 1.5.0) GNU RTP Stack libxml2 libsndfile libmagic libreadline Qt 5 – more specifically, the following submodules: base declarative tools alsa-lib (also known as libasound) libzrtpcpp (version = 0.9.0) ZRTP library, ccRTP support must be enabled bcg729 G.729A codec library Speex and SpeexDSP Speex codec library iLBC iLBC codec library Akonadi (specifically, the core library) and KContacts Run cmake with a list of build options cmake .. -Dexample option=On On first run Twinkle will create the .twinkle directory in your home directory. In this directory all user data will be put: twinkle -h will show you some command line options you may use. If you do not have any configuration file, the configuration file editor will startup so you can create one. If you have configuration files, then Twinkle lets you select an existing configuration file. See below for some hints on settings to be made with the profile configuration editor. If you specify a configuration file name, then Twinkle will such for this configuration file in your .twinkle directory. If you have put your configuration file in another location you have to specify the full path name for the file, i.e. starting with a slash. NOTE: the configuration file editor only exists in the GUI. If you run the CLI mode, you must have a configuration file. So first create a configuration file in GUI mode or hand edit a configuration file, before running the CLI mode. If you run the CLI mode and you do not specify a file name on the command line, then Twinkle will use twinkle.cfg 1. Your SIP provider uses a Session Border Controller 2. Your SIP provider offers a STUN server 3. Make static address mappings in your NAT for SIP and RTP Twinkle will then use this IP address inside SIP headers and SDP bodies instead of the private IP address of your machine. If you have changed the SIP/RTP ports in your profile you have to change the port forwarding rules likewise. During execution Twinkle will create the following log files in your .twinkle directory: A user profile contains information about your user account, SIP proxy, and several SIP protocol options. If you use Twinkle with different user accounts you may create multiple user profiles. When you create a new profile you first give it a name and then you can make the appropriate settings. The name of the profile is what later on appears in the selection box when you start Twinkle again. Or you can give the name.cfg at the command line ( -f option) to immediately start that profile. The user profile is stored as .cfg in the .twinkle directory where is the name you gave to the profile. By default only out-of-dialog requests (eg. REGISTER, OPTIONS, initial INVITE) are sent to the outbound proxy. In-dialog requests (eg. re-INVITE, BYE) are sent to the target indicated by the far end during call setup. By checking 'send in-dialog requests to proxy' Twinkle will ignore this target and send these requests also to the proxy. Normally you would not need this. It could be useful in a scenario where the far-end indicates a target that cannot be resolved to an IP address. By checking "Do not send a request to proxy if its destination can be resolved locally" will make Twinkle always first try to figure out the destination IP address itself, i.e. based on the request-URI and Route-headers. Only when that fails the outbound-proxy will be tried, but only for the options checked above. I.e. if you did not check the 'in-dialog' option, then an in-dialog request will never go to the proxy. If its destination cannot be resolved, then the request will simply fail. The 'expiry' value is the expiry of your registration. Just before the registration expires Twinkle will automatically refresh the registration. The expiry time may be overruled by the registrar. The 'registrar at startup option' will make Twinkle automatically sen