[Blink] Blink Chat

Adrian Georgescu ag at ag-projects.com
Mon May 2 16:55:03 CEST 2016


> "SIP SIMPLE messaging”

That is wrong as that means MSRP protocol only and they did not implement it.

SMS is an old form of sending messages using a SIP protocol method called MESSAGE. This has nothing to do with SIP SIMPLE standards which emerged several years after.

The wikipedia page is poorly written in general and confusing starting with the title:

“SIMPLE (instant messaging protocol)“

SIMPLE is a set of extensions for SIP protocol for presence, multi-party chat, and file transfers. It is not an “instant message protocol’.

Adrian

> On 02 May 2016, at 11:47, Mike Nagie <promike1987 at gmail.com> wrote:
> 
> Got it, thank you!
> 
> My information is based on these:
> https://en.wikipedia.org/wiki/CSipSimple
> The key features of this software are: [...] SIP SIMPLE messaging [...]
> 
> https://en.wikipedia.org/wiki/SIMPLE_(instant_messaging_protocol)
> SIMPLE, the session initiation protocol for instant messaging and
> presence leveraging extensions, is an instant messaging (IM) and
> presence protocol suite...
> 
> Purpose; sending short messages, analogous to SMS or two-way paging;
> 
> See also; Message Session Relay Protocol (MSRP)
> 
> I hope I haven't taken out of context.
> 
> 
> 
> On 16-05-02 10:49:57, Adrian Georgescu wrote:
>>     On 02 May 2016, at 10:31, Mike Nagie <[1]promike1987 at gmail.com> wrote:
>>     I did a tiny research. Theoretically CSipSimple uses SIP SIMPLE protocol
>>     for instant messaging.
>> 
>>   No, it does not. SIMPLE is a set of specifications for chat and presence.
>>   [2]https://datatracker.ietf.org/wg/simple/documents/
>>   For SIMPLE chat, MSRP protocol has been defined.
>>   [3]https://tools.ietf.org/html/rfc4975
>> 
>>     I saw that Blink has SIMPLE protocol (Presence
>>     Agent mode).
>> 
>>   Presence is not chat, is something else than chat. Nevertheless Blink
>>   implements both chat and presence from SIMPLE specifications and
>>    CSipSimple implements neither of them.
>> 
>>     Does it mean they can communicate with each other?
>> 
>>   No, they cannot as CSipSimple has not implemented anything from SIP SIMPLE
>>   specifications.
>>   I am not sure they claimed otherwise either, where have you see that
>>   CSipSimple implements SIMPLE specs?
>> 
>>     On 16-04-27 10:16:58, Adrian Georgescu wrote:
>> 
>>       Blink uses MSRP protocol standardised for session based chat. Eking
>>       does not implement his protocol.
>> 
>>       [4]https://tools.ietf.org/html/rfc4975
>> 
>>       Adrian
>> 
>>         On 27 Apr 2016, at 09:08, Mike Nagie <promike1987 at gmail.com> wrote:
>> 
>>         I was wondering how chat actually works?
>> 
>>         I use Blink, of course, and the others either Ekiga client or
>>         CSipSimple.
>> 
>>         When I sent something with Ekiga client in the past, the others
>>         received
>>         the message. I could write messages and receive messages.
>> 
>>         So now, I'm trying to send something from Blink to Ekiga.
>>         At the search bar I type "johndoe at sip2sip.info" and I click on the
>>         'start a chat session' button.
>>         Blink chat window pops up and I see 'Status Disconnected'.
>>         I type 'hello', and Ekiga starts to ring.
>>         Even if I accept the call I see 'Status Ringing' in Blink, and I
>>         don't
>>         receive the message 'hello'.
>> 
>>         Other way around, if I write something from Ekiga, nothing happens
>>         here.
>> 
>>         Between Blink and CSipSimple (Android)
>>         I opened the chat window, typed something, and Blink said: 'Status:
>>         Not
>>         Acceptable Here'
>> 
>>         Does chat only work between 2 (or more) Blinks?
>> 
>>         [I have not tested with v2.0.0 but theoretically CSipSimple supports
>>         video calls, and it didn't work with earlier versions of Blink, but
>>         maybe things are changed since then and this is not really about
>>         'chat', but the question would be the same, does video chat only
>>         work
>>         between Blinks?]
>> 
>>         Mike
>>         --
>>         You may be a victim of software counterfeiting
>>         _______________________________________________
>>         Blink mailing list
>>         Blink at lists.ag-projects.com
>>         http://lists.ag-projects.com/mailman/listinfo/blink
>> 
>>       _______________________________________________
>>       Blink mailing list
>>       Blink at lists.ag-projects.com
>>       http://lists.ag-projects.com/mailman/listinfo/blink
>> 
>>     --
>>     You may be a victim of software counterfeiting
>>     _______________________________________________
>>     Blink mailing list
>>     [5]Blink at lists.ag-projects.com
>>     http://lists.ag-projects.com/mailman/listinfo/blink
>> 
>> References
>> 
>>   Visible links
>>   1. mailto:promike1987 at gmail.com
>>   2. https://datatracker.ietf.org/wg/simple/documents/
>>   3. https://tools.ietf.org/html/rfc4975
>>   4. https://tools.ietf.org/html/rfc4975
>>   5. mailto:Blink at lists.ag-projects.com
> 
>> _______________________________________________
>> Blink mailing list
>> Blink at lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
> 
> 
> --
> You may be a victim of software counterfeiting
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20160502/0391f55d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20160502/0391f55d/attachment-0001.sig>


More information about the Blink mailing list