> This is like when you send a mail. The SMTP protocol just asserts you > that the mail has been received in the destination server, but you > have no way to determine if it has been delivered to the final user > (let's forget mail-receipt-configuration features, who uses that?). >
There is no concept of a 'session' in email, so the server can just reply with an error, or send you an email back. In MSRP it might be too late if the session is already finished. > So IMHO, at SIP/MSRP protocol your scenario is working correctly. It's > not MSRP business the final usage/storage of the received data (and it > must not be). I assume that your SIP device should warn the user about > the loss or corruption of the received data (but again, it has nothing > to do with MSRP). > The problem is not warning the recipient, but warning the sender. I see no means to communicate the sender *why* the transfer failed. Regards, -- /Saúl http://saghul.net | http://sipdoc.net _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
