FT MAX SIZE - Receiver sends 603 DECLINE instead of 403 FORBIDDEN

Prerequisites:
1. A and B in idle mode.
2. A has enough free storage space to receive file.
3. The file size being transferred is larger than FT MAX SIZE of MNO A but less 
than the warning file size (FT WARN SIZE) of MNO B.
4. Clients A and B do not support HTTP-based FT according to former capability 
exchange.
5. A, B parameters: FT MAX SIZE B is larger than for A.

Actions:
1. B selects one file from the local storage and then selects the file transfer 
option.
2. A receives the file transfer notification and sees an error message due to 
file size.
3. The file cannot be opened as it is not transferred to A.

Expected result:
A sends 403 Forbidden with a Warning header set to “133 Size exceeded”

What do you see instead?
A sends 603 DECLINE

Additional information:
See specification

If the file is bigger than FT MAX SIZE, a warning message is displayed when 
trying to
send or receive a file larger than the mentioned limit and the transfer will be 
cancelled
(that is at protocol level, the SIP INVITE request will never be sent or an 
automatic
rejection response SIP 403 Forbidden with a Warning header set to “133 Size
exceeded” will be sent by the entity that detects that the file size is too 
big to the other
end depending on the scenario).

Original issue reported on code.google.com by lemordan...@gmail.com on 21 Mar 2014 at 4:52

alminah / android-rcs-ims-stack

FT MAX SIZE - Receiver sends 603 DECLINE instead of 403 FORBIDDEN #251