Presence

Version 21 (Adrian Georgescu, 09/18/2012 03:38 pm)

1 1 Adrian Georgescu
h1. Presence
2 1 Adrian Georgescu
3 15 Adrian Georgescu
h2. Design Principles
4 15 Adrian Georgescu
5 21 Adrian Georgescu
Blink should work with any SIP and XCAP servers that supports the same standards as Blink. There is nothing proprietary that would stop interoperability between two Blink clients using any properly configured SIP and XCAP server. Also there is nothing that should stop Blink interoperate with other SIP clients as far as SIP signaling is concerned. The only interoperability issues should be related to accessing the same XCAP documents by different clients. Blink would co-exist with any other SIP client that is using XCAP documens, that is it will preserve any information it did not create in those documents. Unfortunately, we have not found other clients that behave in the same way.
6 1 Adrian Georgescu
7 18 Adrian Georgescu
h3. Disclaimer
8 1 Adrian Georgescu
9 19 Adrian Georgescu
There is no guaranty Blink Presence functionality would interoperate with other SIP clients or SIP servers due to the freedom allowed by the standards. 
10 18 Adrian Georgescu
11 1 Adrian Georgescu
h3. Interoperability
12 1 Adrian Georgescu
13 21 Adrian Georgescu
Presence is a complex issue and the mechanisms used internally by Blink may not necessarily work under your own server environment. If you want to troubleshot when things do not work as expected, first use the built-in Blink accounts that are designed to work with SIP2SIP domain. As protocol traces for signaling and storage are logged to file, you can easily access such debug information and analyze Blink behavior.
14 1 Adrian Georgescu
15 18 Adrian Georgescu
We can provide support, if you encounter interoperability issues with any the following products and services against Blink has been fully tested:
16 1 Adrian Georgescu
17 1 Adrian Georgescu
 * SIP2SIP.info (a public free SIP service)
18 21 Adrian Georgescu
 * Interoperability with any XMPP domain (using SylkServer SIP/XMPP gateway)
19 18 Adrian Georgescu
 * OpenSIPS + OpenXCAP combinations (server software you can run on your premisses)
20 21 Adrian Georgescu
21 16 Adrian Georgescu
22 18 Adrian Georgescu
You can also enable one SIP2SIP account in your Blink instance to perform presence and contact storage operations while using your preferred SIP provider to make phone calls.
23 18 Adrian Georgescu
24 15 Adrian Georgescu
h3. Support
25 15 Adrian Georgescu
26 17 Adrian Georgescu
As presence require proper infrastructure that many SIP service providers simply lack today, do not complain to use when Presence does not work. 
27 15 Adrian Georgescu
28 15 Adrian Georgescu
Contacts are stored on the XCAP server in the resource-lists document under a proprietary name space to avoid conflicts with other end-points that might use the same document as there is no common standard way for how to store a rich address book on a server. This means that different SIP user agents from different vendors cannot read or modify this data in a deterministic way. The contacts in the address-book are then used by standard OMA rls-services and pres-rules XCAP documents. The SIP and XCAP servers need to support OMA style XCAP documents in order to interoperate with Blink.
29 15 Adrian Georgescu
30 12 Adrian Georgescu
h2. Contacts
31 1 Adrian Georgescu
32 1 Adrian Georgescu
Contacts have two Presence related properties that can changed in Edit Contact Panel Subscriptions section:
33 12 Adrian Georgescu
34 1 Adrian Georgescu
 * Subscribe to Contact's Presence Information
35 8 Adrian Georgescu
 * Allow Contact to see my Presence Information
36 18 Adrian Georgescu
 * If an URI part of the contact is labelled as XMPP, when using a SIP2SIP.info account the session request will be forwarded to an XMPP gateway. 
37 1 Adrian Georgescu
38 4 Adrian Georgescu
h2. Watcher Information
39 4 Adrian Georgescu
40 13 Adrian Georgescu
Using SUBSCRIBE for presence.winfo event package, Blink keeps track of presence watchers and their status.
41 6 Adrian Georgescu
 
42 4 Adrian Georgescu
 * Contacts that have subscribed to our presence are rendered in the 'New Contact Requests' group that is rendered on top of the contacts list. Right click or dragging the contact can be used to allow or deny the request. Blocked contacts are displayed in the Blocked group.
43 4 Adrian Georgescu
 * Active watchers are shown in Status -> People Watching  My Presence Activity menu
44 4 Adrian Georgescu
45 6 Adrian Georgescu
h2. Published Presence
46 1 Adrian Georgescu
47 13 Adrian Georgescu
Using PUBLISH method for presence event package, the following information is published by Blink:
48 1 Adrian Georgescu
49 7 Adrian Georgescu
h3. Basic Status
50 7 Adrian Georgescu
51 7 Adrian Georgescu
Open or closed.
52 7 Adrian Georgescu
53 14 Adrian Georgescu
h3. Extended Status
54 7 Adrian Georgescu
55 14 Adrian Georgescu
Blink uses a proprietary extension for indicating the extented status compatible with XMPP end-points. 
56 7 Adrian Georgescu
57 6 Adrian Georgescu
h3. Location
58 1 Adrian Georgescu
59 6 Adrian Georgescu
Location is based on CIPID map extension. Location can be disabled per account in Presence section of account preferences.
60 6 Adrian Georgescu
61 6 Adrian Georgescu
h3. Homepage
62 6 Adrian Georgescu
63 6 Adrian Georgescu
A home page can be entered in Presence section of account preferences. Homepage is based on CIPID homepage extension.
64 1 Adrian Georgescu
65 3 Adrian Georgescu
h3. Note
66 6 Adrian Georgescu
67 14 Adrian Georgescu
Presence note can be typed in the text area right to own icon in the main GUI window. Note is attached to the service.
68 5 Adrian Georgescu
69 5 Adrian Georgescu
h3. Status
70 1 Adrian Georgescu
71 7 Adrian Georgescu
Presence status can be changed from the main GUI window and Status menu. Last combination of Presence state and note are saved in the history build at the end of the menu. 
72 1 Adrian Georgescu
73 5 Adrian Georgescu
h3. Icon
74 1 Adrian Georgescu
75 1 Adrian Georgescu
User icon is uploaded to XCAP server using OMA pres-content application, replicated among multiple Blink instances and location of icons storage URL on XCAP server is published in PIDF.
76 1 Adrian Georgescu
77 1 Adrian Georgescu
h3. Offline Presence
78 1 Adrian Georgescu
79 1 Adrian Georgescu
In status menu, one can change its presence state and also an offline state when Blink is offline. This is done using pidf-manipulation XCAP application.
80 1 Adrian Georgescu
81 1 Adrian Georgescu
h3. Media Capabilities
82 1 Adrian Georgescu
83 1 Adrian Georgescu
Type of media supported by the end-point.
84 1 Adrian Georgescu
85 1 Adrian Georgescu
h3. Device Information
86 1 Adrian Georgescu
87 1 Adrian Georgescu
The following information is published:
88 1 Adrian Georgescu
89 1 Adrian Georgescu
 * Hostname
90 1 Adrian Georgescu
 * Time offset
91 9 Adrian Georgescu
 * Idle status
92 1 Adrian Georgescu
 * GRUU contact address
93 8 Adrian Georgescu
94 10 Adrian Georgescu
h2. Subscribe To Presence
95 3 Adrian Georgescu
96 8 Adrian Georgescu
Using SIP SUBSCRIBE for RLS, Bink subscribes to the SIP addresses stored in rls-services document uploaded on the XCAP server by contacts management actions in the GUI (add/update/delete contacts).
97 1 Adrian Georgescu
 
98 10 Adrian Georgescu
h3. Presence Notifications
99 10 Adrian Georgescu
100 6 Adrian Georgescu
Presence information received from the SIP URIs as RLMI notifications from the RLS server is used to update each contact in the contacts list with:
101 1 Adrian Georgescu
102 1 Adrian Georgescu
 * Status icon overlaid on botton right of user icon, indicating away, busy, extended-away or available
103 1 Adrian Georgescu
 * Rectangular presence indicator on right side of the tile to provide a quick overview about availability
104 1 Adrian Georgescu
 * Presence note is rendered on second line, multiple notes and pending authorizations are rotated every 10 seconds
105 1 Adrian Georgescu
 * User icon is retrieved and updated when necessary from URL advertised by user 
106 2 Adrian Georgescu
107 2 Adrian Georgescu
Selecting  Show Presence Information menu item from contextual contact menu show a panel with detailed information, not all information may have been rendered in the GUI.
108 1 Adrian Georgescu
109 1 Adrian Georgescu
h2. Sessions
110 1 Adrian Georgescu
111 1 Adrian Georgescu
 * When subscribed to Presence, if information is received, the contextual menu of each contact is updated with the possibility of starting a session to a specific device. This requires the remote device to use GRUU.