OfflineMessaging

Version 14 (Saúl Ibarra Corretgé, 06/21/2012 11:02 am)

1 8 Adrian Georgescu
h1. Offline Message Storage Application
2 1 Adrian Georgescu
3 13 Saúl Ibarra Corretgé
h2. Approach 1
4 13 Saúl Ibarra Corretgé
5 10 Adrian Georgescu
 * Add failure route to OpenSIPS for chat sessions
6 4 Adrian Georgescu
 * SylkServer answers the session in behalf of the called user 
7 11 Adrian Georgescu
 * SylkServer sends an automatic answer with 'I am offline but you can type a message'
8 12 Adrian Georgescu
 * Session is kept open for 90 seconds so that remote party has the chance to write something if he did not already before connect
9 3 Adrian Georgescu
 * Session is closed and saved to local history database
10 5 Adrian Georgescu
 * SylkServer detects when targeted user comes online
11 2 Adrian Georgescu
 * Establish a new session to the user that came online and fake the original caller, deliver the stored messages, hangup and wipe delivered messages
12 1 Adrian Georgescu
13 13 Saúl Ibarra Corretgé
h2. Approach 2: VoiceMail style
14 13 Saúl Ibarra Corretgé
15 13 Saúl Ibarra Corretgé
 * Add failure route to OpenSIPS for chat sessions
16 13 Saúl Ibarra Corretgé
 * SylkServer answers the session in behalf of the called user 
17 13 Saúl Ibarra Corretgé
 * SylkServer sends an automatic answer with 'I am offline but you can type a message'
18 13 Saúl Ibarra Corretgé
 * Every time a chat message is received SylkServer sends a MWI (RFC 3842) PUBLISH on behalf of the caller to the proxy.
19 13 Saúl Ibarra Corretgé
   The payload contains Text-Messages instead of Voice-Messages (RFC 3458, sec 6.2).
20 13 Saúl Ibarra Corretgé
 * When the user comes back online she will subscribe to MWI and learn that she has offline text messages waiting. She can get them by starting a chat session to the URI in the Message-Account field of the MWI payload.
21 13 Saúl Ibarra Corretgé
 * When the user fetches all messages SylkServer will terminate the session and send one last PUBLISH indicating that there are no new offline messages.
22 13 Saúl Ibarra Corretgé
 * SylkServer will provide a single URI for all users to fetch messages, the From header URI will be used to select the appropriate user. This assumes SylkServer is deployed behind a SIP proxy, which a by-design feature of SylkServer.
23 13 Saúl Ibarra Corretgé
24 13 Saúl Ibarra Corretgé
Things to be clarified:
25 13 Saúl Ibarra Corretgé
26 13 Saúl Ibarra Corretgé
 * What happens if the user has both voice and text messages waiting? Does OpenSIPS aggregate payloads? Do we care? SylkServer can keep publising until the user fetches the offline messages, but Asterisk won't.
27 1 Adrian Georgescu
28 14 Saúl Ibarra Corretgé
h3. Refinement
29 14 Saúl Ibarra Corretgé
30 14 Saúl Ibarra Corretgé
 * The SIP client will send a second MWI subscription to himself but with a Sylk-App: textmail header to the proxy.
31 14 Saúl Ibarra Corretgé
 * Proxy will route that SUBSCRIBE to SylkServer, which will act as the endpoint, this avoids the problems caused by multiple entities publishing on behalf of the same user.
32 14 Saúl Ibarra Corretgé
33 1 Adrian Georgescu
34 1 Adrian Georgescu
35 1 Adrian Georgescu