Presence

Version 40 (Adrian Georgescu, 09/21/2012 12:49 pm)

1 1 Adrian Georgescu
h1. Presence
2 1 Adrian Georgescu
3 15 Adrian Georgescu
h2. Design Principles
4 15 Adrian Georgescu
5 30 Adrian Georgescu
 * Blink should work with any SIP and XCAP servers that supports SIP SIMPLE standards
6 1 Adrian Georgescu
 * Blink uses only TCP or TLS transports for signaling
7 38 Adrian Georgescu
 * Blink presence payload is based on "RPID schema":http://tools.ietf.org/html/rfc4480
8 36 Adrian Georgescu
 * Blink relies on a Presence Agent collocated with the SIP Registrar that supports PUBLISH method and XCAP
9 40 Adrian Georgescu
 * Presence Agent must support handling of presence rules using org.openmobilealliance.pres-rules XCAP document
10 40 Adrian Georgescu
 * Presence Agent must support external references from rls-services to resource-lists
11 40 Adrian Georgescu
 * Presence Agent must support external references from rls-services to  org.openmobilealliance.pres-rules
12 40 Adrian Georgescu
 * Presence Agent must support presence and presence.winfo event packages
13 40 Adrian Georgescu
 * Presence Agent may support xcap-diff event package for XCAP documents replication
14 40 Adrian Georgescu
 * Presence Agent must support RLS subscriptions and RLMI notifications
15 40 Adrian Georgescu
 * XCAP server must support the following XCAP applications: rls-services, resource-lists, xcap-caps, org.openmobilealliance.pres-content, org.openmobilealliance.pres-rules, org.openmobilealliance.xcap-directory
16 40 Adrian Georgescu
 * XCAP server may support pidf-manipulation for offline status
17 28 Adrian Georgescu
18 29 Adrian Georgescu
There is nothing that should prevent Blink interoperate with any other SIP end-points as far as SIP signaling is concerned (PUBLISH, SUBSCRIBE and NOTIFY methods). Blink will preserve contacts related information it did not create in XCAP documents. Unfortunately, we have not found other clients that behave in the same way. Sharing the same XCAP documents with other SIP clients is therefore strongly discouraged as is guaranteed to cause failures.
19 29 Adrian Georgescu
20 25 Adrian Georgescu
h3. Standards
21 25 Adrian Georgescu
22 25 Adrian Georgescu
http://sipsimpleclient.com/projects/sipsimpleclient/wiki/SipFeatures#Presence
23 18 Adrian Georgescu
24 1 Adrian Georgescu
h3. Disclaimer
25 19 Adrian Georgescu
26 29 Adrian Georgescu
There is no guaranty Blink Presence functionality would interoperate with other SIP clients due to the freedom allowed by the standards in modeling the data used for contacts storage.
27 27 Adrian Georgescu
28 1 Adrian Georgescu
h3. Interoperability
29 1 Adrian Georgescu
30 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.
31 1 Adrian Georgescu
32 32 Adrian Georgescu
We can provide support, if you encounter interoperability issues with any the following products and services against which Blink has been fully tested:
33 1 Adrian Georgescu
34 1 Adrian Georgescu
 * SIP2SIP.info (a public free SIP service)
35 33 Adrian Georgescu
 * Interoperability with XMPP domains (using SylkServer SIP/XMPP gateway)
36 1 Adrian Georgescu
 * OpenSIPS/OpenXCAP combination (server software you can run on your premisses)
37 27 Adrian Georgescu
38 27 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.
39 18 Adrian Georgescu
40 15 Adrian Georgescu
h3. Support
41 15 Adrian Georgescu
42 34 Adrian Georgescu
As presence require proper infrastructure that many SIP service providers simply lack today, do not complain to us when Presence does not work with your SIP service provider.
43 15 Adrian Georgescu
44 15 Adrian Georgescu
h2. Contacts
45 24 Adrian Georgescu
46 34 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. Contacts have two Presence related properties that can changed in Edit Contact Panel Subscriptions section:
47 1 Adrian Georgescu
48 1 Adrian Georgescu
 * Subscribe to Contact's Presence Information
49 8 Adrian Georgescu
 * Allow Contact to see my Presence Information
50 34 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.
51 1 Adrian Georgescu
52 4 Adrian Georgescu
h2. Watcher Information
53 4 Adrian Georgescu
54 13 Adrian Georgescu
Using SUBSCRIBE for presence.winfo event package, Blink keeps track of presence watchers and their status.
55 6 Adrian Georgescu
 
56 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.
57 4 Adrian Georgescu
 * Active watchers are shown in Status -> People Watching  My Presence Activity menu
58 4 Adrian Georgescu
59 6 Adrian Georgescu
h2. Published Presence
60 1 Adrian Georgescu
61 13 Adrian Georgescu
Using PUBLISH method for presence event package, the following information is published by Blink:
62 1 Adrian Georgescu
63 7 Adrian Georgescu
h3. Basic Status
64 7 Adrian Georgescu
65 7 Adrian Georgescu
Open or closed.
66 7 Adrian Georgescu
67 14 Adrian Georgescu
h3. Extended Status
68 7 Adrian Georgescu
69 14 Adrian Georgescu
Blink uses a proprietary extension for indicating the extented status compatible with XMPP end-points. 
70 7 Adrian Georgescu
71 6 Adrian Georgescu
h3. Location
72 1 Adrian Georgescu
73 6 Adrian Georgescu
Location is based on CIPID map extension. Location can be disabled per account in Presence section of account preferences.
74 6 Adrian Georgescu
75 6 Adrian Georgescu
h3. Homepage
76 6 Adrian Georgescu
77 6 Adrian Georgescu
A home page can be entered in Presence section of account preferences. Homepage is based on CIPID homepage extension.
78 1 Adrian Georgescu
79 3 Adrian Georgescu
h3. Note
80 6 Adrian Georgescu
81 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.
82 5 Adrian Georgescu
83 5 Adrian Georgescu
h3. Status
84 1 Adrian Georgescu
85 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. 
86 1 Adrian Georgescu
87 5 Adrian Georgescu
h3. Icon
88 1 Adrian Georgescu
89 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.
90 1 Adrian Georgescu
91 1 Adrian Georgescu
h3. Offline Presence
92 1 Adrian Georgescu
93 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.
94 1 Adrian Georgescu
95 1 Adrian Georgescu
h3. Media Capabilities
96 1 Adrian Georgescu
97 1 Adrian Georgescu
Type of media supported by the end-point.
98 1 Adrian Georgescu
99 1 Adrian Georgescu
h3. Device Information
100 1 Adrian Georgescu
101 1 Adrian Georgescu
The following information is published:
102 1 Adrian Georgescu
103 1 Adrian Georgescu
 * Hostname
104 1 Adrian Georgescu
 * Time offset
105 9 Adrian Georgescu
 * Idle status
106 1 Adrian Georgescu
 * GRUU contact address
107 8 Adrian Georgescu
108 10 Adrian Georgescu
h2. Subscribe To Presence
109 3 Adrian Georgescu
110 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).
111 1 Adrian Georgescu
 
112 10 Adrian Georgescu
h3. Presence Notifications
113 10 Adrian Georgescu
114 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:
115 1 Adrian Georgescu
116 1 Adrian Georgescu
 * Status icon overlaid on botton right of user icon, indicating away, busy, extended-away or available
117 1 Adrian Georgescu
 * Rectangular presence indicator on right side of the tile to provide a quick overview about availability
118 1 Adrian Georgescu
 * Presence note is rendered on second line, multiple notes and pending authorizations are rotated every 10 seconds
119 1 Adrian Georgescu
 * User icon is retrieved and updated when necessary from URL advertised by user 
120 2 Adrian Georgescu
121 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.
122 1 Adrian Georgescu
123 1 Adrian Georgescu
h2. Sessions
124 1 Adrian Georgescu
125 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.