Help For Blink Pro

Version 33 (Tijmen de Mes, 06/25/2012 02:19 pm)

1 1 Tijmen de Mes
h1. Help for Blink Pro on MacOSX
2 1 Tijmen de Mes
3 33 Tijmen de Mes
Help page for Blink QT is available "here":help-qt.phtml
4 2 Tijmen de Mes
5 33 Tijmen de Mes
Blink allows you to communicate in real time over the Internet. To use Blink you need a SIP account from a SIP service provider. Same like using an email program, you must configure Blink with the account you have obtained from your service provider. If things do not work they way you expect, the reasons can be caused mainly by two things, one is Blink software itself and the another one is the communication with the SIP Service Provider. While Blink may not be bug free, most of the problems you encounter when using Blink are related to the network communication with the SIP Service Provider. It is not the end-user who should understand the mechanics about how things work, so the main responsibility of making sure that things work correct falls into the hands of the SIP service provider who must properly setup its SIP infrastructure and support its user base.
6 2 Tijmen de Mes
7 2 Tijmen de Mes
h2. Refund Policy
8 2 Tijmen de Mes
9 2 Tijmen de Mes
Mac App Store does not provide refunds. If you purchased an application that do not like you are stuck with it. If you are not happy with this policy is Apple you must complain to, not us.
10 2 Tijmen de Mes
11 2 Tijmen de Mes
h2. Service Provider Problems
12 2 Tijmen de Mes
13 33 Tijmen de Mes
If you encounter connectivity problems like inability to receive incoming calls or failure to make outbound calls, you can find the reason by going to _Menu Window -> Logs -> SIP_. You should contact your SIP Service Provider and provide it with the information obtained from Blink logs.
14 2 Tijmen de Mes
15 2 Tijmen de Mes
h2. Software Problems
16 2 Tijmen de Mes
17 33 Tijmen de Mes
To report a problem, send an email to "support@ag-projects.com":mailto:support@ag-projects.com. Please paste the relevant logs as explained below.
18 2 Tijmen de Mes
19 33 Tijmen de Mes
You can also check the history of the public "Blink Support Forum":http://support.icanblink.com.
20 2 Tijmen de Mes
21 4 Tijmen de Mes
h3. Critical Errors
22 2 Tijmen de Mes
23 4 Tijmen de Mes
If you experience a software crash, please send the complete crash report available in the crash reporter window (just copy and paste from it). Crash reports are saved in _~/Library/Logs/DiagnosticReports/_.
24 2 Tijmen de Mes
25 1 Tijmen de Mes
h3. Non-Critical Errors
26 23 Tijmen de Mes
27 33 Tijmen de Mes
Non-critical programming errors are logged in the system log file _/var/log/system.log_. You can isolate the entries by opening _Applications -> Utilities -> Console_, selecting _LOG FILES -> system.log_ and typing Blink in the search bar. Please provide us with this information when you report the problem you encountered.
28 1 Tijmen de Mes
29 2 Tijmen de Mes
h3. Configuration File
30 4 Tijmen de Mes
31 2 Tijmen de Mes
Blink accounts and settings are stored in a flat-text configuration file. The location of the configuration file is _~/Library/Application Support/Blink Pro/config_. Do not edit this file manually. If you did and Blink does not start you must delete the file and start all over again.
32 5 Tijmen de Mes
33 33 Tijmen de Mes
Please report your OS name and version and Blink version. You can find Blink version in menu _Blink -> About_.
34 5 Tijmen de Mes
35 11 Tijmen de Mes
h2. SIP Accounts
36 11 Tijmen de Mes
37 33 Tijmen de Mes
"!images/BlinkScreenshot-Enrollment.jpg!":images/BlinkScreenshot-Enrollment.jpg
38 6 Tijmen de Mes
39 33 Tijmen de Mes
To use Blink, you need a SIP Account. At first start, Blink shows the _Add Account_ "window":screenshots.phtml#enrollment that helps you configure the initial SIP Account.
40 1 Tijmen de Mes
41 33 Tijmen de Mes
If you do not have a SIP Account, Blink can create one for you using the free service provided by SIP2SIP. For more information about the features of the SIP service go to "http://sip2sip.info":http://wiki.sip2sip.info
42 6 Tijmen de Mes
43 33 Tijmen de Mes
If you already have a SIP Account from a SIP service provider, select this option then enter the SIP address in the form of _user@domain_ and the _password_. If the SIP service provider has set his infrastructure correctly, all server address settings will be automatically discovered by Blink. If the SIP service provider was not capable of doing this, you may need to set some of the settings like server address, port and transport protocol manually, see the advanced settings section below.
44 6 Tijmen de Mes
45 33 Tijmen de Mes
You may configure Blink to use multiple SIP Accounts. To add a new SIP Account, go to menu _Preferences->Accounts_ and click the _+_ button. The _Add Account_ window shows up and you can repeat the steps described above.
46 6 Tijmen de Mes
47 33 Tijmen de Mes
After you have configured an account, you can see the status of the registration in the account list of _Main Window_ window. Solid color means that the account has successfully registered, gray color means that the registration has failed or is in progress. You can also see the status of the registration in the account list of _Preferences_ window. Green color means that the account has successfully registered, Red color the registration has failed and Yellow means that he registration process is in progress.
48 6 Tijmen de Mes
49 6 Tijmen de Mes
A successful registration means that you are able to receive incoming calls with Blink.
50 1 Tijmen de Mes
51 6 Tijmen de Mes
h3. Advanced Account Settings
52 8 Tijmen de Mes
53 1 Tijmen de Mes
h4. Outbound Proxy
54 6 Tijmen de Mes
55 33 Tijmen de Mes
If the SIP provider does not have proper DNS records set for his domain to point to its SIP server address and port numbers as defined by RFC3263, Blink will not be able to auto-discover its location. In such case you must set the Outbound Proxy setting in _Preferences -> SIP Account -> Advanced -> SIP Signaling_. Also you can use this setting to force a specific transport or port different than the ones discovered from DNS. The outbound proxy format is _host.example.com:5060;transport=udp_.
56 6 Tijmen de Mes
57 6 Tijmen de Mes
h2. Main Interface
58 1 Tijmen de Mes
59 33 Tijmen de Mes
"!images/BlinkScreenshot-Contacts.jpg!":images/BlinkScreenshot-Contacts.jpg
60 12 Tijmen de Mes
61 33 Tijmen de Mes
Blink presents a _Contacts driven_ "interface":screenshots.phtml#main_interface as the main window. The design allows to locate a Contact then to start an action for it, for example to start an _Audio Call_. You can toggle to and from a dial-pad interface in the _Contacts_ menu.
62 6 Tijmen de Mes
63 33 Tijmen de Mes
The main interface can be collapsed into a "compact mode":screenshots.phtml#collapsed_gui that hides the Contact List or dialpad. Click on the *+* Green button of the window to collapse and expand the main interface.
64 6 Tijmen de Mes
65 6 Tijmen de Mes
Hover the mouse over the GUI elements to see a short description of their function.
66 6 Tijmen de Mes
67 6 Tijmen de Mes
h3. SIP Account
68 6 Tijmen de Mes
69 33 Tijmen de Mes
You can select the SIP Account used for outbound sessions in the _Accounts drop down box_ presented on the top of the main interface.
70 1 Tijmen de Mes
71 6 Tijmen de Mes
h4. Bonjour Account
72 6 Tijmen de Mes
73 33 Tijmen de Mes
_Bonjour Account_ is a special type of account that is designed to announce itself and discover other neighbours on the local area network. This account does not require a server or SIP service in order to operate.
74 1 Tijmen de Mes
75 6 Tijmen de Mes
h3. Search Bar
76 6 Tijmen de Mes
77 6 Tijmen de Mes
The Search bar is used for finding an existing contact or for entering a SIP address or telephone number.
78 6 Tijmen de Mes
79 33 Tijmen de Mes
To search for a contact in Blink's _Contacts List_, system _Address Book_ and optionally configured LDAP directory of the active account, fill in the name in the _Search Bar_. You may select a Contact that matched the typed text or use the typed text as the Contact for the next action.
80 6 Tijmen de Mes
81 33 Tijmen de Mes
Use the buttons presented at the bottom of the main window to start a session to the current selected Contact or press on _Add Contact_ to add the typed address to the _Contacts List_.
82 6 Tijmen de Mes
83 6 Tijmen de Mes
Pressing enter or return after entering text in the search bar will start an audio call to that address.
84 6 Tijmen de Mes
85 6 Tijmen de Mes
h3. Contacts List
86 1 Tijmen de Mes
87 6 Tijmen de Mes
Contacts can be organized in Groups. The Groups support ordering and can be collapsed or expanded when clicking on their left-side triangle. Groups can be dragged in different order. Contacts can be dragged from one group to another.
88 6 Tijmen de Mes
89 1 Tijmen de Mes
Right click on a Contact to see all possible actions for each of them.
90 1 Tijmen de Mes
91 7 Tijmen de Mes
h4. Address Book
92 6 Tijmen de Mes
93 33 Tijmen de Mes
The group named _Address Book_ cannot be deleted, it is dynamically populated with entries from the system _Address Book_. To reload changes made in the _Address Book_ collapse and expand the group again.
94 6 Tijmen de Mes
95 33 Tijmen de Mes
For Address Book entries, to have a SIP Address recognized by Blink you must have entries in either Email or URL sections that start with the _sip:_ prefix.
96 6 Tijmen de Mes
97 6 Tijmen de Mes
One can initiate an audio call using Blink Pro directly from the AddressBook application by clicking on the Phone, Email or URL fields of an AddressBook contact. For this you must install the AddressBook plugins available at:
98 6 Tijmen de Mes
99 33 Tijmen de Mes
"http://download.ag-projects .com/BlinkABPlugins/":http://download.ag-projects.com/BlinkABPlugins/
100 1 Tijmen de Mes
101 6 Tijmen de Mes
The plugins work with Blink Pro version 1.8.2 or newer.
102 1 Tijmen de Mes
103 6 Tijmen de Mes
h4. Bonjour Neighbours
104 6 Tijmen de Mes
105 33 Tijmen de Mes
_Bonjour Neighbours_ appear in the _Contacts List_ as a separate Group. When selecting _Bonjour_ as the default account, _Bonjour Neighbours_ group is expanded and moved on top of the Contacts list. When changing back to a regular SIP Account, the groups in the Contacts list reshuffle to their previous positions.
106 6 Tijmen de Mes
107 6 Tijmen de Mes
Chat sessions are automatically accepted from Bonjour Neighbours.
108 1 Tijmen de Mes
109 6 Tijmen de Mes
Audio sessions can be automatically accepted based on the correspondent setting from Account menu.
110 6 Tijmen de Mes
111 1 Tijmen de Mes
h4. Edit Contact
112 7 Tijmen de Mes
113 33 Tijmen de Mes
You can edit a Contact by right clicking on it and select Edit menu option. _Edit Contact_ "window":screenshots.phtml#add_contact appears. To set the _Icon for the Contact_, click on the Icon area, a file selection dialog appears.
114 1 Tijmen de Mes
115 1 Tijmen de Mes
h4. Add Contact
116 1 Tijmen de Mes
117 33 Tijmen de Mes
You can add a Contact to the _Contacts List_ by clicking on the _+_ button presented on the bottom left of the main interface. _Add Contact_ "window":screenshots.phtml#add_contact appears.
118 6 Tijmen de Mes
119 1 Tijmen de Mes
h4. Server Storage
120 7 Tijmen de Mes
121 6 Tijmen de Mes
If a contact is associated with an account and the SIP service that provides the account has XCAP storage capabilities, the contact is then also stored on the XCAP server. Multiple Blink instances can be synchronized in real time by using this feature.
122 6 Tijmen de Mes
123 6 Tijmen de Mes
h4. Special Groups
124 1 Tijmen de Mes
125 1 Tijmen de Mes
In Preferences Contact section, special groups like Favorites or Missed Calls can be enabled.
126 6 Tijmen de Mes
127 1 Tijmen de Mes
h3. Start Session
128 7 Tijmen de Mes
129 6 Tijmen de Mes
Use the buttons presented at the bottom of the main window to start a session to the current selected Contact.
130 6 Tijmen de Mes
131 33 Tijmen de Mes
Clicking on _Return key_ or double-clicking a Contact will start the default session type depending on the preferred media configured for each Contact. The default action is to start an _Audio Call_.
132 1 Tijmen de Mes
133 6 Tijmen de Mes
h2. Alert Panel
134 7 Tijmen de Mes
135 33 Tijmen de Mes
"!images/BlinkScreenshot-AlertPanel-DS.jpg!":images/BlinkScreenshot-AlertPanel-DS.jpg
136 13 Tijmen de Mes
137 33 Tijmen de Mes
Incoming session requests bring up the <em>"Alert Panel":screenshots.phtml#alert_panel</em>. Click on the _Accept Button_ to accept a session request. There are two options for rejecting an incoming session request:
138 6 Tijmen de Mes
139 33 Tijmen de Mes
* Click on the _Reject button_. The session is rejected with SIP response code 603 and all other SIP devices registered for the same account stop ringing. Forwarding to voicemail or other destinations, when available in the SIP server is also cancelled. You must use this option to terminate all call processing associated with the request.
140 33 Tijmen de Mes
* Click on the _Busy button_. Blink sends a 486 code back to the caller and stops ringing, other SIP devices keep ringing and forwarding to other destinations remains active as set in the SIP server. You must use this option when you want to pick up the call at a different location or allow the Server to perform other pre-configured routing decisions.
141 7 Tijmen de Mes
142 33 Tijmen de Mes
When the _Answering Machine_ is enabled, a countdown appears in the Alert Panel. While the countdown counts you can still disable the _Answering Machine_ from the Account menu.
143 33 Tijmen de Mes
144 6 Tijmen de Mes
The currently selected input and output audio devices are showed for incoming Audio Call requests.
145 6 Tijmen de Mes
146 7 Tijmen de Mes
h2. Audio Calls
147 1 Tijmen de Mes
148 33 Tijmen de Mes
"!images/BlinkScreenshot-AudioSessions.jpg!":images/BlinkScreenshot-AudioSessions.jpg
149 6 Tijmen de Mes
150 33 Tijmen de Mes
_Audio Calls_ are displayed in the lateral "drawer":screenshots.phtml#audio_sessions attached to the main interface.
151 6 Tijmen de Mes
152 33 Tijmen de Mes
To start an _Audio Call_, select an existing contact or enter a SIP address or telephone number in the search bar. Once text is entered in the search bar just press enter to start an audio call to that address. Alternatively, you can turn on the dialpad in the Contacts menu and press its keys.
153 1 Tijmen de Mes
154 33 Tijmen de Mes
When a Contact is selected, you may click on the _Green Handset_ located at the bottom of the main interface or right click on thr Contact and select _Start Audio Session_ from the contextual menu. For each new call an entry is added to the _Audio Calls_ drawer.
155 1 Tijmen de Mes
156 6 Tijmen de Mes
To switch between multiple calls just click on another call in the audio sessions drawer. When switching to a particular session, the audio stream is connected to the input and output device and all other Audio Calls are put on hold.
157 6 Tijmen de Mes
158 33 Tijmen de Mes
To add _Chat_ to an existing _Audio Call_, right click on the session displayed in the Audio Drawer and select an _Add Chat_
159 1 Tijmen de Mes
160 6 Tijmen de Mes
To mute your microphone click on the bottom right microphone icon. To un-mute click it again.
161 6 Tijmen de Mes
162 1 Tijmen de Mes
h3. Codecs
163 6 Tijmen de Mes
164 33 Tijmen de Mes
Audio codecs can be set in _Preferences -&gt; Advanced -&gt; RTP Media_ section and can be overwritten per account in _Advanced -&gt; RTP Media section_. By default, the audio codecs are prioritized to allow for highest quality and second, compatibility with SIP services.
165 6 Tijmen de Mes
166 6 Tijmen de Mes
If you have changed the defaults or want to set the codecs manually, for high quality conversations is recommended to use G.722 codec as first choice and leave PCMA and PCMU enabled for compatibility reasons. Some details about the codecs used by Blink:
167 6 Tijmen de Mes
168 33 Tijmen de Mes
* G.722 is the most compatible wideband codec supported by both software and hardware phones
169 33 Tijmen de Mes
* Speex is another high quality codec that works with many softphones
170 33 Tijmen de Mes
* PCMA and PCMU are the most interoperable codecs that work with almost any device
171 33 Tijmen de Mes
* GSM and iLBC use less bandwidth than the other codecs but they have less support in service provider equipment
172 1 Tijmen de Mes
173 1 Tijmen de Mes
h3. DTMF
174 1 Tijmen de Mes
175 6 Tijmen de Mes
Dial tones are used to interact with PBX and IVR systems or legacy PSTN gateways. To send DTMF tones, focus the Audio Call by clicking on it. The current call is already focused if you just started it. What you then type on the keyboard is automatically translated into DTMF tones. Alpha-numeric keys are translated into numeric DTMF keys as they are on a numeric telephone keypad. Also you may use the dialpad for this purpose.
176 6 Tijmen de Mes
177 33 Tijmen de Mes
If a telephone number with a # sign is dialed, what comes after the # sign will be automatically entered as DTMF codes once the call is connected. Supported DTMF codes are 0-9&#42;#. You can use the comma sign ',' to insert a one second pause (version &gt;=1.5.1).
178 6 Tijmen de Mes
179 1 Tijmen de Mes
h3. Hangup
180 1 Tijmen de Mes
181 31 Tijmen de Mes
To hangup click on the _Red handset_ displayed for each Audio Session in the right hand side of the drawer or press the Escape key.
182 1 Tijmen de Mes
183 1 Tijmen de Mes
h3. Hold/Unhold
184 1 Tijmen de Mes
185 6 Tijmen de Mes
The shortcut key for hold and unhold of the selected session is Space.
186 1 Tijmen de Mes
187 1 Tijmen de Mes
h3. Record
188 1 Tijmen de Mes
189 33 Tijmen de Mes
To record click on the _Black circle_. While recording, the circle will toggle between red and black. Recorded sessions can be found in menu _Audio -&gt; Recordings_.
190 6 Tijmen de Mes
191 8 Tijmen de Mes
h3. Transfer
192 1 Tijmen de Mes
193 1 Tijmen de Mes
To blindly transfer a call, just drag it to a contact in the Contacts list. You can also enter a number or address in the search bar, to transfer a call to an arbitrary address.
194 1 Tijmen de Mes
195 6 Tijmen de Mes
To perform an assisted call transfer, first establish a call to each party. Then, click on the T button for completing the transfer, a contextual menu is presented.
196 1 Tijmen de Mes
197 1 Tijmen de Mes
h3. Call History
198 6 Tijmen de Mes
199 33 Tijmen de Mes
History of previous sessions is available in the _History_ menu. If you have registered a SIP Account with Blink, you can review the missed calls while Blink was off-line in _Account-&gt; Settings on SIP Server -&gt; History_ menu.
200 1 Tijmen de Mes
201 1 Tijmen de Mes
h3. Redial
202 6 Tijmen de Mes
203 6 Tijmen de Mes
To redial the last session type Command-R, to redial a previous session select it in the History menu.
204 6 Tijmen de Mes
205 8 Tijmen de Mes
h3. iTunes Integration
206 1 Tijmen de Mes
207 33 Tijmen de Mes
iTunes automatically pauses playing before any _Audio Call_ pauses and resumes playing after all _Audio Calls_ have finished.
208 6 Tijmen de Mes
209 8 Tijmen de Mes
h3. Audio Information
210 6 Tijmen de Mes
211 33 Tijmen de Mes
"!images/BlinkScreenshot-ICE.jpg!":images/BlinkScreenshot-ICE.jpg
212 6 Tijmen de Mes
213 6 Tijmen de Mes
Audio Calls have status indication about the progress of establishment of the RTP stream and ICE negotiation, the negotiated codec and the presence of encryption for signaling and media.
214 1 Tijmen de Mes
215 1 Tijmen de Mes
The RTP end-points and negotiated ICE candidates (when ICE negotiation succeeded) are displayed when hovering the mouse over the Audio codec information area.
216 1 Tijmen de Mes
217 1 Tijmen de Mes
h3. Calling Telephone Numbers
218 1 Tijmen de Mes
219 33 Tijmen de Mes
To dial a telephone number, just enter the number in the _Search Box_ followed by Enter or Return key.
220 1 Tijmen de Mes
221 1 Tijmen de Mes
When dialing numbers by selecting entries from the Address Book it is recommended that you store your numbers in international E.164 format (that is + sign followed by the country code then the subscriber number).
222 1 Tijmen de Mes
223 33 Tijmen de Mes
You can set in the account _Advanced -&gt; Phone Numbers_ preferences section how to replace the + sign with another prefix recognized by your SIP service provider or PBX. For example if you set _Replace Starting +_ with 001, when you dial +44XXX the number will be dialed as 00144XXX.
224 6 Tijmen de Mes
225 33 Tijmen de Mes
Optionally, phone numbers can be also prefixed before dialing out, for example if a 9 is required by your PBX by setting the _External Line Prefix_ option.
226 6 Tijmen de Mes
227 33 Tijmen de Mes
If you have created a SIP Account with Blink, you can call to PSTN numbers if you must have a positive credit. You can use a Credit Card to add _Credit_ to your SIP Account in menu _Tools -&gt; Call To Phone Numbers..._. You may request the assignment of a PSTN Caller Id by opeing a ticket in the server support interface. Recognized number formats are _+_ or _00_ followed by the _Country Code_ and then _Subscriber Number_.
228 1 Tijmen de Mes
229 1 Tijmen de Mes
If you use another SIP Account than the one provided by Blink, access to the PSTN is subject to the support provided by your SIP service provider. The number format depends as well on the conventions imposed by the SIP service provider in question.
230 1 Tijmen de Mes
231 1 Tijmen de Mes
h3. Voicemail
232 8 Tijmen de Mes
233 33 Tijmen de Mes
Voicemail is a feature provided for SIP accounts created by Blink. It is provided by the network while Blink is offline, when the call forwarding to Voicemail is activated. To change the settings of your SIP2SIP voicemail box dial _1233_. You can record your unavailable message and listen to your messages stored on the server. The voicemail delivered method (by email attachement or by dialing into the server) is set in menu _Tools -&gt; Settings on SIP server_ in the Voicemail section.
234 6 Tijmen de Mes
235 6 Tijmen de Mes
h3. Answering Machine
236 1 Tijmen de Mes
237 33 Tijmen de Mes
When the _Answering Machine_ is enabled, Audio Call requests will be automatically answered with either the standard or the custom recorded message after the delay configured set in _Preferences -&gt; Answering Machine_ settings.
238 6 Tijmen de Mes
239 33 Tijmen de Mes
You can enable the _Answering Machine_ using the menu item _Tools -&gt; Enable Answering Machine_. The incoming Audio Calls are then recorded and can be listened to later in _Tools -&gt; Recordings_ menu.
240 1 Tijmen de Mes
241 33 Tijmen de Mes
While the _Answering Machine_ is handling an Audio Call, you can hear what the remote party is speaking while your microphone is muted. If you wish you can take over by clicking on the _Green Handset_ icon in the Audio drawer. The recording stops and the session is connected to the microphone.
242 1 Tijmen de Mes
243 6 Tijmen de Mes
h3. Audio Conference
244 6 Tijmen de Mes
245 33 Tijmen de Mes
"!images/BlinkScreenshot-AudioConference.jpg!":images/BlinkScreenshot-AudioConference.jpg
246 8 Tijmen de Mes
247 33 Tijmen de Mes
Drag and drop _Audio Calls_ on top of each other to create a <em>"Conference":screenshots.phtml#audio_conference</em> or use the button presented at the botton at the _Audio Drawer_ to start a _Conference_ with all active _Audio Calls_.
248 1 Tijmen de Mes
249 33 Tijmen de Mes
Add new participants to a Conference by dragging Contacts from the _Contacts list_ onto an _Audio Call_.
250 6 Tijmen de Mes
251 6 Tijmen de Mes
Each participant can be muted individually by pressing on the microphone symbol that appears on each conferenced session.
252 1 Tijmen de Mes
253 33 Tijmen de Mes
To end an _Audio Conference_ drag the session out of the conference area or press the _Conference_ button again.
254 6 Tijmen de Mes
255 33 Tijmen de Mes
There can be only one active _Audio Conference_ at any given time.
256 6 Tijmen de Mes
257 6 Tijmen de Mes
h2. Chat Sessions
258 6 Tijmen de Mes
259 33 Tijmen de Mes
"!images/BlinkScreenshot-ServerConference.jpg!":images/BlinkScreenshot-ServerConference.jpg
260 8 Tijmen de Mes
261 33 Tijmen de Mes
_Chat Sessions_ are displayed into the "Chat window":screenshots.phtml#chat_sessions. For each recipient there is a new Tab created at the bottom of the window. The Tabs are matched based on the SIP Address of the recipient and the _Chat Aliases_ configured for the Contacts.
262 22 Tijmen de Mes
263 6 Tijmen de Mes
The lateral drawer display the active participants present in the chat session or multi-party conference.
264 1 Tijmen de Mes
265 33 Tijmen de Mes
_Chat Sessions_ are encrypted using TLS and handled like the _Audio Sessions_, a _Chat Session_ is established only to the device where the user accepts the session. _Chat sessions_ can carry arbitrarily large amounts of text information.
266 6 Tijmen de Mes
267 33 Tijmen de Mes
You can start a _Chat Session_ by right-clicking on a _Contact_ and chose _Start Chat Session_.
268 1 Tijmen de Mes
269 6 Tijmen de Mes
Messages typed before the session is accepted by the remote party are queued and delivered once the session has been established. If the session fails to establish, the undelivered messages will be resent at the next successful attempt.
270 6 Tijmen de Mes
271 1 Tijmen de Mes
Message marked with a red color background have failed to be delivered.
272 6 Tijmen de Mes
273 33 Tijmen de Mes
To an established _Chat Session_ you can add _Audio_ or start a _Screen Sharing_ session by clicking on the buttons presented on the toolbar.
274 1 Tijmen de Mes
275 33 Tijmen de Mes
To review previous chat conversations go to menu _History -&gt; Chat Conversations_.
276 6 Tijmen de Mes
277 6 Tijmen de Mes
To insert an empty line use Shift-Enter combination.
278 1 Tijmen de Mes
279 1 Tijmen de Mes
The rendering of Emoticons can be disabled in each chat window, this can be useful to transfer programming code snippets without interpreting the special characters as emoticons.
280 6 Tijmen de Mes
281 6 Tijmen de Mes
h2. Short Messages
282 6 Tijmen de Mes
283 33 Tijmen de Mes
_Short Messages_ is the way to interact with legacy SIP IM clients that do not support session based _Chat Sessions_ using MSRP protocol.
284 9 Tijmen de Mes
285 33 Tijmen de Mes
_Short Messages_ end-up on all SIP devices registered for the remote SIP Account, including hardware phones that accept such messages but do not display them, the recipient has no control where to receive them. _Short Messages_ have no end-to-end delivery report and cannot be encrypted the way Chat Sessions are.
286 1 Tijmen de Mes
287 33 Tijmen de Mes
A _Short Message_ cannot exceed 1300 characters on IP networks and 160 on PSTN mobile networks.
288 6 Tijmen de Mes
289 33 Tijmen de Mes
You can send a _Short Message_ by right-clicking on a _Contact_ and chose _Send SMS_.
290 6 Tijmen de Mes
291 33 Tijmen de Mes
Previous exchanged messages can be reviewed in the menu _Window -&gt; Chat History_.
292 1 Tijmen de Mes
293 6 Tijmen de Mes
h2. File Transfers
294 6 Tijmen de Mes
295 33 Tijmen de Mes
"!images/BlinkScreenshot-FileTransfer.jpg!":images/BlinkScreenshot-FileTransfer.jpg
296 9 Tijmen de Mes
297 33 Tijmen de Mes
To send a file you can use drag and drop from Finder or other application like iPhoto onto a Contact, to a Chat Window or by right clicking on a Contact and then selecting _Send File..._ option.
298 1 Tijmen de Mes
299 33 Tijmen de Mes
_File Transfers_ are displayed in a "separate window":screenshots.phtml#file_transfers. Each file has a progress bar attached with estimated transfer speed and remaining time.
300 6 Tijmen de Mes
301 6 Tijmen de Mes
h2. Screen Sharing
302 6 Tijmen de Mes
303 6 Tijmen de Mes
Screen Sharing is implemented by using standard VNC protocol over an MSRP connection. The minimum bandwidth required for a reasonable experience us 1 Mbit/s. Make sure that all debugging is disabled during Screen Sharing as it can overload the CPU.
304 1 Tijmen de Mes
305 33 Tijmen de Mes
The party sharing the Screen must have enabled _Screen Sharing_ in _System Preferences_ and set the option _Anyone may request permission to control screen_ in Computer Settings section of the _Share Screen_ panel.
306 1 Tijmen de Mes
307 33 Tijmen de Mes
!images/BlinkScreenshot-ScreenSharingServerSetup.jpg!
308 20 Tijmen de Mes
309 33 Tijmen de Mes
310 9 Tijmen de Mes
h3. Screen Sharing Party
311 1 Tijmen de Mes
312 1 Tijmen de Mes
First Blink alerts the user about an incoming request for Screen Sharing. If accepted, MacOSX VNC server will asks to confirm the Screen Sharing request. The request originates from the localhost (127.0.0.1) as the connection runs through Blink.
313 19 Tijmen de Mes
314 33 Tijmen de Mes
!images/BlinkScreenshot-ScreenSharingServerConfirmation.jpg!
315 6 Tijmen de Mes
316 33 Tijmen de Mes
317 6 Tijmen de Mes
h3. Screen Viewer Party
318 1 Tijmen de Mes
319 6 Tijmen de Mes
The party asking for Screen Sharing must select the option 'Connect by Asking for Permission' when prompted by the VNC viewer.
320 18 Tijmen de Mes
321 33 Tijmen de Mes
!images/BlinkScreenshot-ScreenSharingClientRequest.jpg!
322 9 Tijmen de Mes
323 33 Tijmen de Mes
324 6 Tijmen de Mes
h2. NAT Traversal
325 6 Tijmen de Mes
326 9 Tijmen de Mes
For NAT traversal you must rely on your SIP service provider. In general, every SIP service provides relaying for both signaling and media, which takes care of the NAT issue. This means that no special settings are necessary in the client.
327 6 Tijmen de Mes
328 28 Tijmen de Mes
h3. Audio
329 6 Tijmen de Mes
330 33 Tijmen de Mes
For _Audio Calls_ you can enable the use of ICE negotiation in _Advanced -&gt; NAT Traversal -&gt; Use ICE_. ICE requires the presence of STUN servers, they must be provided by the SIP service provider. The ICE negotiation details are displayed in "RTP Logs window":screenshots.phtml#logs_ice. While the ICE negotiation progresses, its status is also displayed in the Audio Call information, for example the gathering of ICE the candidates and the probing of the remote candidates.
331 6 Tijmen de Mes
332 33 Tijmen de Mes
Once the audio stream is established, the audio information area is updated with the negotiated codec type and the sample rate. The active RTP end-points and the ICE candidates types are displayed while "hovering the mouse":screenshots.phtml#rtp_endpoints over the audio status information area.
333 6 Tijmen de Mes
334 28 Tijmen de Mes
h3. IM and File Transfers
335 6 Tijmen de Mes
336 33 Tijmen de Mes
To traverse the NAT for MSRP related sessions (Instant Messaging, File Transfer) a "MSRP relay":http://msrprelay.org configured for the called party domain is needed. The SIP service provider that provides the SIP Account must support this feature (e.g. http://sip2sip.info).
337 6 Tijmen de Mes
338 28 Tijmen de Mes
h3. Screen Sharing
339 6 Tijmen de Mes
340 33 Tijmen de Mes
To traverse the NAT for Screen Sharing sessions a "MSRP relay":http://msrprelay.org configured for the called party domain is needed. The SIP service provider that provides the SIP Account must support this feature (e.g. http://sip2sip.info).
341 6 Tijmen de Mes
342 6 Tijmen de Mes
h2. Growl Notifications
343 6 Tijmen de Mes
344 6 Tijmen de Mes
Growl notifications are raised for missed sessions and the Dock Icon badge is updated with the number of missed sessions.
345 6 Tijmen de Mes
346 9 Tijmen de Mes
When sessions are accepted elsewhere and the SIP server supports the Reason header, the sessions will be logged in the incoming section rather than the missed section.
347 6 Tijmen de Mes
348 6 Tijmen de Mes
h2. Logs
349 6 Tijmen de Mes
350 33 Tijmen de Mes
"Logs Window":screenshots.phtml#logs helps troubleshoot network traffic for various protocols used by Blink. For example, one can follow in the self scrolling interface the time sequence of all DNS lookups and SIP messages exchanged with the other end-points.
351 6 Tijmen de Mes
352 33 Tijmen de Mes
To see what Blink is doing under the hood go to the menu _Window -&gt; Logs_. It is advisable not to leave MSRP Trace and Notifications Logs turned on unless you really need them for debugging purposes, they are very demanding in terms of CPU load during File Transfer and Screen Sharing sessions.
353 6 Tijmen de Mes
354 17 Tijmen de Mes
h2. Server Settings
355 6 Tijmen de Mes
356 33 Tijmen de Mes
"!images/BlinkScreenshot-DND.jpg!":images/BlinkScreenshot-DND.jpg
357 6 Tijmen de Mes
358 6 Tijmen de Mes
Blink is integrated with the SIP2SIP server functionality. One can change settings directly on the SIP server like Call Forwarding, Do Not Disturb, list of last missed sessions and other settings.
359 6 Tijmen de Mes
360 33 Tijmen de Mes
The settings are displayed in "Server Settings window":screenshots.phtml#server_settings. The window is actually a web interface that loads the URL configured in the _Advanced -&gt; Server -&gt; Settings URL_ for each SIP Account. The remote web server can support digest authentication, Blink sends the SIP Account credentials when prompted by the server.
361 6 Tijmen de Mes
362 26 Tijmen de Mes
h2. Audio Devices
363 6 Tijmen de Mes
364 33 Tijmen de Mes
Blink auto-detects audio devices there are plugged in and out on the fly and prompts the user to switch to a new added device. You can switch automatically by setting this option in Preferences -&gt; Audio section.
365 6 Tijmen de Mes
366 33 Tijmen de Mes
To selected a particular audio device use the menu _Audio_.
367 6 Tijmen de Mes
368 16 Tijmen de Mes
h2. Preferences
369 6 Tijmen de Mes
370 33 Tijmen de Mes
"!images/BlinkScreenshot-Preferences.jpg!":images/BlinkScreenshot-Preferences.jpg
371 6 Tijmen de Mes
372 33 Tijmen de Mes
To change Blink configuration go to menu _Preferences_. The Preferences "window":screenshots.phtml#preferences appears.
373 1 Tijmen de Mes
374 6 Tijmen de Mes
Find out more information about a particular setting by hovering the mouse over it.
375 6 Tijmen de Mes
376 25 Tijmen de Mes
Each SIP Account has advanced options available, to reveal them click on the small triangle presented under the SIP Address.
377 1 Tijmen de Mes
378 6 Tijmen de Mes
Blink preferences are stored in _~/Library/Application Support/Blink Pro_ folder. You can reset Blink by deleting this folder.
379 1 Tijmen de Mes
380 33 Tijmen de Mes
Blink SIP accounts and settings are stored in _~/Library/Application Support/Blink Pro/config_ file.
381 6 Tijmen de Mes
382 6 Tijmen de Mes
GUI preferences are stored in _~/Library/Preferences/com.agprojects.Blink.plist_ file. (e.g. size, location of the windows and other MacOSX related settings).
383 1 Tijmen de Mes
384 33 Tijmen de Mes
If you ever want to move your Blink configuration to another login account you must edit the content of your _config_ file and replace the absolute file paths accordingly. You can edit this file with any text editor as long as you do not break the return lines and formatting of the file.
385 1 Tijmen de Mes
386 24 Tijmen de Mes
h3. Codecs
387 6 Tijmen de Mes
388 33 Tijmen de Mes
Blink supports _G722_ and _Speex_ wide-band codecs. The order of the codecs can be configured in menu _Preferences -&gt; Advanced -&gt; RTP Media_ and for each SIP Account in _Preferences -&gt; Accounts -&gt; Advanced -&gt; RTP Media_.
389 9 Tijmen de Mes
390 6 Tijmen de Mes
h3. Open Browser on Incoming Call
391 1 Tijmen de Mes
392 33 Tijmen de Mes
You can configure Blink Pro to automatically open a web browser on an incoming call event. For this set the _Alert URL_ in _Preferences -&gt; Advanced -&gt; Server Settings_ section.
393 6 Tijmen de Mes
394 9 Tijmen de Mes
The URL may contain the following variables that will be replaced with the actual information from the incoming session:
395 9 Tijmen de Mes
396 33 Tijmen de Mes
* $caller&#95;party - the SIP address of the caller party
397 33 Tijmen de Mes
* $called&#95;party - the SIP address of the account being called
398 1 Tijmen de Mes
399 33 Tijmen de Mes
Example: http://www.example.com?caller=$caller&#95;party&amp;called=$called&#95;party
400 1 Tijmen de Mes
401 1 Tijmen de Mes
h2. History Database
402 1 Tijmen de Mes
403 9 Tijmen de Mes
Blink stores the history of sessions and chat messages in a Sqlite database. The location of the database is:
404 6 Tijmen de Mes
405 33 Tijmen de Mes
bc. ~/Library/Application Support/Blink Pro/history/history.sqlite
406 9 Tijmen de Mes
407 33 Tijmen de Mes
408 6 Tijmen de Mes
If for any reason the database becomes corrupted, which may manifest itself by errors reported graphically by Blink itself or in the Console application you may work around the problems in several ways.
409 6 Tijmen de Mes
410 33 Tijmen de Mes
First, backup your database in case you need the uncorrupted data in the future. You can do this by copying the history.sqlite file to another location. The file can be opened in *Terminal* application using *sqlite3* program. You can dump the old data in the corrupted database as follows:
411 9 Tijmen de Mes
412 33 Tijmen de Mes
bc. #:~/Library/Application Support/Blink Pro/history$sqlite3 history.sqlite 
413 6 Tijmen de Mes
SQLite version 3.7.7 2011-06-25 16:35:41
414 6 Tijmen de Mes
Enter ".help" for instructions
415 6 Tijmen de Mes
Enter SQL statements terminated with a ";"
416 6 Tijmen de Mes
sqlite> select * from sessions;
417 6 Tijmen de Mes
sqlite> select * from chat_messages;
418 9 Tijmen de Mes
419 33 Tijmen de Mes
420 9 Tijmen de Mes
h3. Restore Procedure
421 9 Tijmen de Mes
422 6 Tijmen de Mes
Try the following in this order to solve a data corruption problem:
423 6 Tijmen de Mes
424 33 Tijmen de Mes
* Clear the session history table, go to menu _History-&gt; Clear History_. The session table will be emptied and the chat messages are not affected. Restart Blink.
425 33 Tijmen de Mes
* Stop Blink. Remove history.sqlite file, the history database will be recreated at start time. Use the backup file for reading the old data using the sqlite3 command line utility.