I agree with Vikram on this. A UAC *could* choose to display some sort
of message when it receives a 202 response. But there is certainly no
reason for the UAS to *expect* that to happen. If the UAS wants to
ensure a message is displayed, then it had better send its own MESSAGE
in the other direction.
This would be a potential area for further standardization. I think I
once saw a draft on store/forward messaging, but I don't recall it going
anywhere.
Paul
Vikram Chhibber wrote:
> "Eventhoug RFC might not have specifically considered the case."
> Like all other SIP RFCs, RFC 3428 is an intend to introduce SIP
> MESSAGE on which we can build IM type application. It does not
> specifically define a high level application specific behavior. What
> you are asking for is application specific and that understanding
> would be restricted with the implementors and the users of that
> implementation. Please understand the difference here.
> Sending back 2xx implies that the MESSAGE has been accepted and
> achieved. Informing the user that the IM would be delivered would be
> next logical option. Sending final failure response to MESSAGE would
> definitely mean "transaction failure".
>
> On Feb 4, 2008 7:50 PM, KASTURI Narayanan (kasnaray) <[EMAIL PROTECTED]>
> wrote:
>> And it will give an impression that the other user is receiving the message
>> but not replying back ( meaning ignoring ).
>>
>> So a message with the info indicating that the message has been received and
>> delivered when the user comes online is the best option.
>>
>> Eventhoug RFC might not have specifically considered the case.
>>
>> Kasturi
>>
>>> -----Original Message-----
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED] On
>>> Behalf Of Iñaki Baz Castillo
>>> Sent: Monday, February 04, 2008 8:16 AM
>>> To: [email protected]
>>> Subject: Re: [Sip-implementors] Response code when MESSAGE is
>>> storedbecauseuser offline?
>>>
>>> On Monday 04 February 2008 14:46:24 Vikram Chhibber wrote:
>>>> In my opinion 202 Accepted is the best response with Warning header
>>>> you can send.
>>> But that header or code description will not be shown by the
>>> human user since the UAC will accept that "202" as MESSAGE
>>> received by the UAS.
>>>
>>> --
>>> Iñaki Baz Castillo
>>> [EMAIL PROTECTED]
>>>
>>> _______________________________________________
>>> Sip-implementors mailing list
>>> [email protected]
>>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>>
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
