TCHAggregatedDeliveryReceipt Class Reference
Inherits from | NSObject |
---|---|
Declared in | TCHAggregatedDeliveryReceipt.h |
Overview
Contains aggregated information about a TCHMessage’s delivery statuses across all participants of a TCHConversation.
At any moment during delivering message to a TCHParticipant the message can have zero or more of following delivery statuses:
Message considered as sent to a participant, if the nearest upstream carrier accepted the message.
Message considered as delivered to a participant, if Twilio has received confirmation of message delivery from the upstream carrier, and, where available, the destination handset.
Message considered as undelivered to a participant, if Twilio has received a delivery receipt indicating that the message was not delivered. This can happen for many reasons including carrier content filtering and the availability of the destination handset.
Message considered as read by a participant, if the message has been delivered and opened by the recipient in the conversation. The recipient must have enabled read receipts.
Message considered as failed to be delivered to a participant if the message could not be sent. This can happen for various reasons including queue overflows, account suspensions and media errors (in the case of MMS for instance).
TCHAggregatedDeliveryReceipt class contains aggregated value TCHDeliveryAmount for each delivery status. The TCHDeliveryAmount displays amount of participants which have the status for the message.
total
Maximum number of delivery events expected for the message.
@property (readonly) NSInteger total
Discussion
Maximum number of delivery events expected for the message.
Declared In
TCHAggregatedDeliveryReceipt.h
sent
Message considered as sent to a participant, if the nearest upstream carrier accepted the message.
@property (readonly) TCHDeliveryAmount sent
Discussion
Message considered as sent to a participant, if the nearest upstream carrier accepted the message.
TCHDeliveryAmount of participants that have sent delivery status for the message.
Declared In
TCHAggregatedDeliveryReceipt.h
delivered
Message considered as delivered to a participant, if Twilio has received confirmation of message delivery from the upstream carrier, and, where available, the destination handset.
@property (readonly) TCHDeliveryAmount delivered
Discussion
Message considered as delivered to a participant, if Twilio has received confirmation of message delivery from the upstream carrier, and, where available, the destination handset.
TCHDeliveryAmount of participants that have delivered delivery status for the message.
Declared In
TCHAggregatedDeliveryReceipt.h
undelivered
Message considered as undelivered to a participant, if Twilio has received a delivery receipt indicating that the message was not delivered. This can happen for many reasons including carrier content filtering and the availability of the destination handset.
@property (readonly) TCHDeliveryAmount undelivered
Discussion
Message considered as undelivered to a participant, if Twilio has received a delivery receipt indicating that the message was not delivered. This can happen for many reasons including carrier content filtering and the availability of the destination handset.
TCHDeliveryAmount of participants that have undelivered delivery status for the message.
Declared In
TCHAggregatedDeliveryReceipt.h
read
Message considered as read by a participant, if the message has been delivered and opened by the recipient in the conversation. The recipient must have enabled read receipts.
@property (readonly) TCHDeliveryAmount read
Discussion
Message considered as read by a participant, if the message has been delivered and opened by the recipient in the conversation. The recipient must have enabled read receipts.
TCHDeliveryAmount of participants that have read delivery status for the message.
Declared In
TCHAggregatedDeliveryReceipt.h
failed
Message considered as failed to be delivered to a participant if the message could not be sent. This can happen for various reasons including queue overflows, account suspensions and media errors (in the case of MMS for instance). Twilio does not charge you for failed messages.
@property (readonly) TCHDeliveryAmount failed
Discussion
Message considered as failed to be delivered to a participant if the message could not be sent. This can happen for various reasons including queue overflows, account suspensions and media errors (in the case of MMS for instance). Twilio does not charge you for failed messages.
TCHDeliveryAmount of participants that have failed delivery status for the message.
Declared In
TCHAggregatedDeliveryReceipt.h