There are eight 'Summary Period' Voicemail System Link Statistics objects, which each display statistics collected over a different time interval. Note that the summary periods are preconfigured; you cannot change the summary periods or create new 'Summary Period' Voicemail System Link Statistics objects. All the 'Summary Period' Voicemail System Link Statistics objects have the same fields. All the fields are read only and there are no management actions associated with these objects. However, you can reset all the fields of these objects by clicking on the 'Reset statistics' pushbutton displayed in the Voicemail System Link object.
Parameter |
Type of statistic |
Description |
Count of call history messages | Count | Number of Call History messages sent to the local message center (each message contains information about a call being passed to the local message center). This count corresponds to requirement R4-23 in GR-283-CORE issue 2. |
Count of call history bytes | Count | Total number of bytes sent in Call History messages. This count corresponds to requirement R4-23 in GR-283-CORE issue 2. |
Count of discarded call history bytes | Count | Number of bytes in Call History messages that were discarded because they could not be sent within the required timeout period. This count corresponds to requirement R4-24 in GR-283-CORE issue 2. |
Count of SMDI Block messages | Count | Number of SMDI Block (BLK) messages transmitted to the local message center. A Block message is sent to indicate that a request from the local message center, to activate or deactivate the message waiting indicator for a subscriber, has been discarded because of a short term failure. This count corresponds to requirement R4-25 in GR-283-CORE issue 2. |
Count of SMDI Block bytes | Count | Total number of bytes sent in SMDI Block messages. This count corresponds to requirement R4-25 in GR-283-CORE issue 2. |
Count of SMDI Invalid messages | Count | Number of SMDI Invalid (INV) messages transmitted to the local message center. An Invalid message is sent to indicate that a request from the local message center, to activate or deactivate the message waiting indicator for a subscriber, has been discarded because of a short term failure. This count corresponds to requirement R4-25 in GR-283-CORE issue 2. |
Count of SMDI Invalid bytes | Count | Total number of bytes sent in SMDI Invalid messages. This count corresponds to requirement R4-25 in GR-283-CORE issue 2. |
Count of SMDI Operate messages | Count | Number of SMDI Operate (OP) messages received from the local message center. An Operate message is sent to indicate that the message waiting indicator should be activated for a particular subscriber. This count corresponds to optional requirement O4-35 in GR-283-CORE issue 2. |
Count of SMDI Remove messages | Count | Number of SMDI Remove (RMV) messages received from the local message center. A Remove message is sent to indicate that the message waiting indicator should be deactivated for a particular subscriber. This count corresponds to optional requirement O4-35 in GR-283-CORE issue 2 |
Count of total SMDI Operate and Remove messages | Count | Total number of SMDI Operate and Remove messages received from the local message center. This count corresponds to requirement R4-26 in GR-283-CORE issue 2. |
Count of total SMDI Operate and Remove bytes | Count | Total number of bytes received in SMDI Operate and Remove messages. This count corresponds to requirement R4-26 in GR-283-CORE issue 2. |
Count of invalid messages | Count | The number of received SMDI messages that were not valid. This includes only messages that were correctly formatted, but did not contain valid information. It does not include bytes that could not be translated into valid SMDI messages. This count corresponds to requirement R4-28 in GR-283-CORE issue 2. |
Proportion of asynchronous writes | Percentage | The percentage of writes to the SMDI link that could not complete synchronously. This indicates the percentage of messages that MetaSwitch could not send immediately because the link was busy and the outgoing buffer was full. This replaces the outgoing message buffer traffic measurements, R-29 and R-30, in GR-283-CORE issue 2. |
Proportion of asynchronous reads | Percentage | The percentage of reads from the SMDI link that could not complete synchronously. This indicates the percentage of messages that MetaSwitch received from the local message center but could not process immediately. This replaces the incoming message buffer traffic measurements, R-29 and R-30, in GR-283-CORE issue 2. |