MSRP Protocol Performance

This section describes the different statistics you can access for monitoring MSRP protocol performance.

MSRP Statistics Overview

MSRP defines two request types, or methods.

• SEND requests are used to deliver a complete message or a chunk (a portion of a complete message).

  Note:

  When the SBC receives a SEND message, it identifies and increments KPIs on CHAT and isTyping messages, but does not distinguish between Delivery and Read receipts, incrementing the applicable KPIs as receipts.
• REPORT requests report on the status of a previously sent message, or a range of bytes inside a message. REPORT requests are similar to SEND requests, except that report requests must not include Success-Report or Failure-Report header fields, and must contain a status header field. REPORT requests must contain the Message-ID header field from the original SEND request.

When an endpoint receives a REPORT request, it correlates the report to the original SEND request using the Message-ID and the Byte-Range, if present. If it requested success reports, then it should keep enough state about each outstanding sent message so that it can correlate REPORT requests to the original messages.

When an endpoint receives a message in one or more chunks that contain a Success- Report value of "yes", it must send a success report or reports covering all bytes that are received successfully. Failure-Report header field indicates whether the reports should be sent on failures and Success-Report header field indicates whether the reports should be sent on successes.