Delivery notifications
Who creates a delivery notification depends on the delivery mode of the corresponding transfer:
- Real-time
- For real-time transfers, delivery notifications can be sent only for file transfers, not for message transfers. After the receiver receives the file, the receiver creates a delivery notification request primitive and sends it via the SIPN to the sender of the file.
- SnF
- After the receiver retrieves a message or file from its SnF queue, it sends an SnFAck primitive to the SIPN. If the transfer was successful and the sender requested a delivery notification, the SIPN creates a system message containing a successful-delivery notification and puts it into the notification SnF queue that was specified in the original SendMsg or SendFile request. If the transfer was unsuccessful, the SIPN creates and delivers a system message containing an unsuccessful-delivery notification regardless of whether the sender requested a delivery notification.
If a scenario uses a T-Copy or Y-Copy service, and if an attempt to transfer a message or file to a third party is:
- Unsuccessful, the SIPN creates a failed-delivery notification for that transfer and passes it to the sender.
- Successful, the SIPN does not create a successful-delivery notification for that transfer.
As long as only successful-delivery notifications are received, the MSIF transfer service regards the transfer as successful, and sets the notification state of the corresponding scenario to SuccessDelivNotif. However, if one or more failed-delivery notifications are received, regardless of whether for the receiver or a third party, the MSIF transfer service regards the transfer as failed and sets the notification state to FailedDelivNotif, regardless of how many successful-delivery notifications were received.