Applications MIB (ap-apps.mib)
The Apps mib (ap-apps.mib) contains tables related ENUM, DNS, DoS threshold and STIR statistics and states.
apAppsENUMServerStatusTable Table
The following table all configured ENUM servers' status.
| MIB Object | Description |
|---|---|
| apAppsENUMServerStatusEntry
1.3.6.1.4.1.9148.3.16.1.2.1.1.1 |
Numbered table entry. |
| apAppsENUMConfigName
1.3.6.1.4.1.9148.3.16.1.2.1.1.1.1 |
The name of the enum-config element that contains this ENUM server. |
| apAppsENUMServerInetAddressType
1.3.6.1.4.1.9148.3.16.1.2.1.1.1.2 |
The internet address type of this ENUM server. |
| apAppsENUMServerInetAddress
1.3.6.1.4.1.9148.3.16.1.2.1.1.1.3 |
The IP address of this ENUM server. |
| apAppsENUMServerStatus
1.3.6.1.4.1.9148.3.16.1.2.1.1.1.4 |
The status of this ENUM server. |
apAppsDnsServerStatusTable
The following table all configured ENUM servers' status.
| MIB Object | Description |
|---|---|
| apAppsDnsServerStatusEntry
1.3.6.1.4.1.9148.3.16.1.2.2.1.1 |
An entry designed to hold the status of a single DNS server |
| apAppsDnsInterfaceName
1.3.6.1.4.1.9148.3.16.1.2.2.1.1.1 |
The name of the dns interface that contains this dns server. |
| apAppsDnsServerInetAddressType
1.3.6.1.4.1.9148.3.16.1.2.2.1.1.2 |
The internet address type of this DNS server. |
| apAppsDnsServerInetAddress
1.3.6.1.4.1.9148.3.16.1.2.2.1.1.3 |
The IP address of this DNS server. |
| apAppsDnsServerStatus
1.3.6.1.4.1.9148.3.16.1.2.2.1.1.4 |
The status of this DNS server. |
apAppsStirMIBObjects Table
The apAppsStirMIBObjects is an object that consists of all the STIR-related tables. This table collects and assembles all STIR/SHAKEN MIB data for presentation using SNMP.
Tables within the apAppsStirMIBObjects (1.3.6.1.4.1.9148.3.16.1.2.4) table include:
- apAppsStirServerTable (1.3.6.1.4.1.9148.3.16.1.2.4.1), which references:
- apAppsStirServerEntry
- apStirServerIndex
- apStirServerName
- apAppsStirStatsTable (1.3.6.1.4.1.9148.3.16.1.2.4.2), which references:
- apAppsStirStatsEntry
- apStirStatsServerIndex
- apCounterStatsType
- apStirServerStats
- apStirStatsType
- apAppsStirAgentTable (1.3.6.1.4.1.9148.3.16.1.2.4.3), which references:
- apAppsStirAgentEntry
- apStirAgentIndex
- apStirAgentName
- apAppsStirAgentStatsTable (1.3.6.1.4.1.9148.3.16.1.2.4.4), which references:
- apAppsStirAgentStatsEntry
- apStirStatsAgentIndex
- apCounterStatsAgentType
- apStirAgentStatsType
- apStirAgentStats
- apAppsStirSipInterfaceTable (1.3.6.1.4.1.9148.3.16.1.2.4.5), which
references:
- apAppsStirSipInterfaceEntry
- apStirSipInterfaceIndex
- apStirSipInterfaceName
- apAppsStirSipInterfaceStatsTable (1.3.6.1.4.1.9148.3.16.1.2.4.6), which
references:
- apAppsStirSipInterfaceStatsEntry
- apStirStatsSipInterfaceIndex
- apCounterStatsSipInterfaceType
- apStirSipInterfaceStatsType
- apStirSipInterfaceStats
- apAppsStirRealmTable (1.3.6.1.4.1.9148.3.16.1.2.4.7), which references:
- apAppsStirRealmEntry
- apStirRealmIndex
- apStirRealmName
- apAppsStirRealmStatsTable (1.3.6.1.4.1.9148.3.16.1.2.4.8), which references:
- apAppsStirRealmStatsEntry
- apStirStatsRealmIndex
- apCounterStatsRealmType
- apStirRealmStatsType
- apStirRealmStats
- apAppsStirSystemStatsTable (1.3.6.1.4.1.9148.3.16.1.2.4.9) , which
references:
- apAppsStirSystemStatsEntry
- apCounterStatsSystemType
- apStirSystemStatsType
- apStirSystemStats
apAppsStirServerTable
The table lists STIR server names with object apStirServerName indexed by a persistent index apStirServerIndex.
apAppsStirServerTable
The following table collects information on all configured STIR servers' status.
The apStirServerName OID is 1.3.6.1.4.1.9148.3.16.1.2.4.1.1.2.
The apAppsStirServerStatsTable uses three variables to specify each object, as follows:
- The first index is the server index.
This component of the SNMP table uses the config-object ID the system creates when you create the object. The STI server labels are contained in OID APAPPS-MIB::apStirServerName.
- The second index is an enumeration of the counter types:
- recent = 1
- total = 2
- permax = 3
- The third index is the data category.
For example, the apStirServerStats instances have an OID of the form apStirServerStats.x.y.z, where:
- apStirServerStats is 1.3.6.1.4.1.9148.3.16.1.2.4.2.1.4;
- x is the stir server's index;
- y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
- z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for example, is found within the recent, total, and permax counter types.
| MIB Object | Object ID 1.3.6.1.4.1.9148.3.16.1.2.4.2.1.4.x |
|---|---|
| apStirServerStats.<index>.recent.asQueries | 1.1 |
| apStirServerStats.<index>.total.asQueries | 2.1 |
| apStirServerStats.<index>.permax.asQueries | 3.1 |
To find the complete OID for a data category:
- Start with the OID of apStirServerStats ( 1.3.6.1.4.1.9148.3.16.1.2.4.2.1.4)
- Append your server index (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.2.1.4.10).
- Append your ApCounterStatsType (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.2.1.4.10.2)
- Append your data category (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.2.1.4.10.2.1)
Table 4-1 Data Categories
| Data Category Name | Data Category Number | Description |
|---|---|---|
| asQueries | .1 | Queries made to the named AS server |
| asSuccessResponses | .2 | Successful responses received from the named AS server |
| asFailResponses | .3 | Failed responses received from the named AS server |
| asFailServiceException | .4 | Failed responses received from the named AS server caused by a service exception |
| asFailPolicyException | .5 | Failed responses received from the named AS server caused by a policy exception |
| vsQueries | .6 | Queries made to the named VS server |
| vsSuccessResponses | .7 | Successful responses received from the named VS server |
| vsFailResponses | .8 | Successful responses received from the named VS server |
| vsSuccessVerification | .9 | Successful verifications received from the named VS server |
| vsFailVerification | .10 | Failed responses received from the named VS server indicating verification failure |
| vsFailServiceException | .11 | Failed responses received from the named VS server caused by a service exception |
| vsFailPolicyException | .12 | Failed responses received from the named VS server caused by a policy exception |
| serverUnreachable | .13 | Number of unsuccessful attempts to reach a server |
| asSentInviteswithShakenPASSportA | .14 | Sent INVITES that included a SHAKEN passport with attestation level A |
| asSentInviteswithShakenPASSportB | .15 | Sent INVITES that included a SHAKEN passport with attestation level B |
| asSentInviteswithShakenPASSportC | .16 | Sent INVITES that included a SHAKEN passport with attestation level C |
| asSentInviteswithdivPASSport | .17 | Sent INVITES that included a DIV passport |
| vsReceivedInviteswithNoPASSport | .18 | Recevied INVITEs that had no passport |
| vsReceivedInviteswithShakenPASSport | .19 | Received INVITEs that had at least one SHAKEN passport |
| vsReceivedInviteswithDivPASSport | .20 | Received INVITEs that had at least one DIV passport |
| vsSentInviteswithTNValidationPassed | .21 | Sent INVITES that included a TN validation that passed |
| vsSentInviteswithTNValidationFailed | .22 | Sent INVITES that included a TN validation that failed |
| vsSentInviteswithNoTNValidation | .23 | Sent INVITES that included a no TN validation parameter |
| asServiceUnreachable | .24 | Number of unreachable Service to AS |
| vsServiceUnreachable | .25 | Number of unreachable Service to VS Server |
| vsInviteRejected | .26 | Number of calls rejected based on verstat and reason code from sti-vs server |
| asBypass | .27 | Number of calls that bypassed the STI-AS server signature request based on message contents |
| vsBypass | .28 | Number of calls that bypassed the STI-VS server verification request based on message contents |
| apStirStatsTypeMax | .29 | Marker indicating the end of the stats types |
The apStirStatsTypeMax marks the end of the defined types. No object should have the index with its value. If an object has this value, the number of the apStirServerStatsType values has been expanded and either this MIB Guide or the MIB Package should be updated.
apAppsStirAgentStatsTable
The following table collects information on all configured STIR session agents status. The apAppsStirAgentStats reference is the name for all apAppsStirAgentStatsTable stats elements.
The apStirAgentName OID is 1.3.6.1.4.1.9148.3.16.1.2.4.3.1.2.
The apAppsStirAgentStatsTable uses three variables to specify each object, as follows:
- The first index is the STIR session agent index.
This component of the SNMP table uses the config-object ID the system creates when you create the object. The STI agent labels are contained in OID APAPPS-MIB::apStirAgentName.
- The second index is an enumeration of the counter types:
- recent = 1
- total = 2
- permax = 3
- The third index is the data category.
For example, the apAppsStirAgentStats instances have an OID of the form
apAppsStirAgentStats.x.y.z, where:
- apStirAgentStats is 1.3.6.1.4.1.9148.3.16.1.2.4.4.1.4
- x is the STIR sesion agent's index
- y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
- z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for example, is found within the recent, total, and permax counter types.
| MIB Object | Object ID 1.3.6.1.4.1.9148.3.16.1.2.4.4.1.4.x |
|---|---|
| apStirAgentStats.<index>.recent.asQueries | 1.1 |
| apStirAgentStats.<index>.total.asQueries | 2.1 |
| apStirAgentStats.<index>.permax.asQueries | 3.1 |
To find the complete OID for a data category:
- Start with the OID of apStirAgentStats (1.3.6.1.4.1.9148.3.16.1.2.4.4.1.4)
- Append your STIR session agent index (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.4.1.4.10).
- Append your ApCounterStatsType (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.4.1.4.10.2)
- Append your data category (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.4.1.4.10.2.1)
Table 4-2 Data Categories
| Data Category Name | Data Category Number | Description |
|---|---|---|
| asQueries | .1 | Queries made to the named AS server |
| asSuccessResponses | .2 | Successful responses received from the named AS server |
| asFailResponses | .3 | Failed responses received from the named AS server |
| asFailServiceException | .4 | Failed responses received from the named AS server caused by a service exception |
| asFailPolicyException | .5 | Failed responses received from the named AS server caused by a policy exception |
| vsQueries | .6 | Queries made to the named VS server |
| vsSuccessResponses | .7 | Successful responses received from the named VS server |
| vsFailResponses | .8 | Successful responses received from the named VS server |
| vsSuccessVerification | .9 | Successful verifications received from the named VS server |
| vsFailVerification | .10 | Failed responses received from the named VS server indicating verification failure |
| vsFailServiceException | .11 | Failed responses received from the named VS server caused by a service exception |
| vsFailPolicyException | .12 | Failed responses received from the named VS server caused by a policy exception |
| asSentInviteswithShakenPASSportA | .14 | Sent INVITES that included a SHAKEN passport with attestation level A |
| asSentInviteswithShakenPASSportB | .15 | Sent INVITES that included a SHAKEN passport with attestation level B |
| asSentInviteswithShakenPASSportC | .16 | Sent INVITES that included a SHAKEN passport with attestation level C |
| asSentInviteswithdivPASSport | .17 | Sent INVITES that included a DIV passport |
| vsReceivedInviteswithNoPASSport | .18 | Recevied INVITEs that had no passport |
| vsReceivedInviteswithShakenPASSport | .19 | Received INVITEs that had at least one SHAKEN passport |
| vsReceivedInviteswithDivPASSport | .20 | Received INVITEs that had at least one DIV passport |
| vsSentInviteswithTNValidationPassed | .21 | Sent INVITES that included a TN validation that passed |
| vsSentInviteswithTNValidationFailed | .22 | Sent INVITES that included a TN validation that failed |
| vsSentInviteswithNoTNValidation | .23 | Sent INVITES that included a no TN validation parameter |
| vsInviteRejected | .26 | Number of calls rejected based on verstat and reason code from sti-vs server |
| asBypass | .27 | Number of calls that bypassed the STI-AS server signature request based on message contents |
| vsBypass | .28 | Number of calls that bypassed the STI-VS server verification request based on message contents |
| apStirStatsTypeMax | .29 | Marker indicating the end of the stats types |
The apStirStatsTypeMax marks the end of the defined types. No object should have the index with its value. If an object has this value, the number of the apStirServerStatsType values has been expanded and either this MIB Guide or the MIB Package should be updated.
apAppsStirSipInterfaceStatsTable
The following table collects information on all configured sip-interface status. The apStirSipInterfaceStats reference is the name for all apAppsStirSipInterfaceStatsTable stats elements. The following topics address SNMP changes with new OIDs labeled within the tables below.
The apStirSipInterfaceName OID is 1.3.6.1.4.1.9148.3.16.1.2.4.5.1.2.
The apAppsStirSipInterfaceStatsTable uses three variables to specify each object, as follows:
- The first index is the sip-interface index.
This component of the SNMP table uses the config-object ID the system creates when you create the object. The STI labels are contained in OID APAPPS-MIB::apStirSipInterfaceName.
- The second index is an enumeration of the counter types:
- recent = 1
- total = 2
- permax = 3
- The third index is the data category.
For example, the apStirSipInterfaceStats instances have an OID of the
form apAppsStirSipInterfaceStats.x.y.z, where:
- apAppsStirSipInterfaceStats is 1.3.6.1.4.1.9148.3.16.1.2.4.6.1.4
- x is the sip-interface index
- y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
- z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for example, is found within the recent, total, and permax counter types.
| MIB Object | Object ID 1.3.6.1.4.1.9148.3.16.1.2.4.6.1.4.x |
|---|---|
| apAppsStirSipInterfaceStats.<index>.recent.asQueries | 1.1 |
| apAppsStirSipInterfaceStats.<index>.total.asQueries | 2.1 |
| apAppsStirSipInterfaceStats.<index>.permax.asQueries | 3.1 |
To find the complete OID for a data category:
- Start with the OID of apStirSipInterfaceStats (1.3.6.1.4.1.9148.3.16.1.2.4.6.1.4)
- Append your sip-interface index (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.6.1.4.3).
- Append your ApCounterStatsType (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.6.1.4.3.2)
- Append your data category (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.6.1.4.3.2.1)
Data Categories
| Data Category Name | Data Category Number | Description |
|---|---|---|
| asQueries | .1 | Queries made to the named AS server |
| asSuccessResponses | .2 | Successful responses received from the named AS server |
| asFailResponses | .3 | Failed responses received from the named AS server |
| asFailServiceException | .4 | Failed responses received from the named AS server caused by a service exception |
| asFailPolicyException | .5 | Failed responses received from the named AS server caused by a policy exception |
| vsQueries | .6 | Queries made to the named VS server |
| vsSuccessResponses | .7 | Successful responses received from the named VS server |
| vsFailResponses | .8 | Successful responses received from the named VS server |
| vsSuccessVerification | .9 | Successful verifications received from the named VS server |
| vsFailVerification | .10 | Failed responses received from the named VS server indicating verification failure |
| vsFailServiceException | .11 | Failed responses received from the named VS server caused by a service exception |
| vsFailPolicyException | .12 | Failed responses received from the named VS server caused by a policy exception |
| asSentInviteswithShakenPASSportA | .14 | Sent INVITES that included a SHAKEN passport with attestation level A |
| asSentInviteswithShakenPASSportB | .15 | Sent INVITES that included a SHAKEN passport with attestation level B |
| asSentInviteswithShakenPASSportC | .16 | Sent INVITES that included a SHAKEN passport with attestation level C |
| asSentInviteswithdivPASSport | .17 | Sent INVITES that included a DIV passport |
| vsReceivedInviteswithNoPASSport | .18 | Recevied INVITEs that had no passport |
| vsReceivedInviteswithShakenPASSport | .19 | Received INVITEs that had at least one SHAKEN passport |
| vsReceivedInviteswithDivPASSport | .20 | Received INVITEs that had at least one DIV passport |
| vsSentInviteswithTNValidationPassed | .21 | Sent INVITES that included a TN validation that passed |
| vsSentInviteswithTNValidationFailed | .22 | Sent INVITES that included a TN validation that failed |
| vsSentInviteswithNoTNValidation | .23 | Sent INVITES that included a no TN validation parameter |
| vsInviteRejected | .26 | Number of calls rejected based on verstat and reason code from sti-vs server |
| asBypass | .27 | Number of calls that bypassed the STI-AS server signature request based on message contents |
| vsBypass | .28 | Number of calls that bypassed the STI-VS server verification request based on message contents |
| apStirStatsTypeMax | .29 | Marker indicating the end of the stats types |
The apStirStatsTypeMax marks the end of the defined types. No object should have the index with its value. If an object has this value, the number of the apStirServerStatsType values has been expanded and either this MIB Guide or the MIB Package should be updated.
apAppsStirRealmStatsTable
The following table collects information on all configured STIR realm' status. The apRealmServerStats reference is the name for all apAppsStirRealmStatsTable stats elements.
The apStirRealmName OID is 1.3.6.1.4.1.9148.3.16.1.2.4.7.1.2.
The apAppsStirRealmStatsTable uses three variables to specify each object, as follows:
- The first index is the realm index.
This component of the SNMP table uses the config-object ID the system creates when you create the object. The STI labels are contained in OID APAPPS-MIB::apStirRealmName.
- The second index is an enumeration of the counter types:
- recent = 1
- total = 2
- permax = 3
- The third index is the data category.
For example, the apAppsStirRealmStats instances have an OID of the form
apAppsRealmServerStats.x.y.z, where:
- apStirRealmStats is 1.3.6.1.4.1.9148.3.16.1.2.4.8.1.4
- x is the realm index
- y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
- z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for example, is found within the recent, total, and permax counter types.
| MIB Object | Object ID 1.3.6.1.4.1.9148.3.16.1.2.4.8.1.4.x |
|---|---|
| apStirRealmStats.<index>.recent.asQueries | 1.1 |
| apStirRealmStats.<index>.total.asQueries | 2.1 |
| apStirRealmStats.<index>.permax.asQueries | 3.1 |
To find the complete OID for a data category:
- Start with the OID of apStirRealmStats (1.3.6.1.4.1.9148.3.16.1.2.4.8.1.4)
- Append your realm index (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.8.1.4.3).
- Append your ApCounterStatsType (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.8.1.4.3.2)
- Append your data category (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.8.1.4.3.2.1)
Data Categories
| Data Category Name | Data Category Number | Description |
|---|---|---|
| asQueries | .1 | Queries made to the named AS server |
| asSuccessResponses | .2 | Successful responses received from the named AS server |
| asFailResponses | .3 | Failed responses received from the named AS server |
| asFailServiceException | .4 | Failed responses received from the named AS server caused by a service exception |
| asFailPolicyException | .5 | Failed responses received from the named AS server caused by a policy exception |
| vsQueries | .6 | Queries made to the named VS server |
| vsSuccessResponses | .7 | Successful responses received from the named VS server |
| vsFailResponses | .8 | Successful responses received from the named VS server |
| vsSuccessVerification | .9 | Successful verifications received from the named VS server |
| vsFailVerification | .10 | Failed responses received from the named VS server indicating verification failure |
| vsFailServiceException | .11 | Failed responses received from the named VS server caused by a service exception |
| vsFailPolicyException | .12 | Failed responses received from the named VS server caused by a policy exception |
| asSentInviteswithShakenPASSportA | .14 | Sent INVITES that included a SHAKEN passport with attestation level A |
| asSentInviteswithShakenPASSportB | .15 | Sent INVITES that included a SHAKEN passport with attestation level B |
| asSentInviteswithShakenPASSportC | .16 | Sent INVITES that included a SHAKEN passport with attestation level C |
| asSentInviteswithdivPASSport | .17 | Sent INVITES that included a DIV passport |
| vsReceivedInviteswithNoPASSport | .18 | Recevied INVITEs that had no passport |
| vsReceivedInviteswithShakenPASSport | .19 | Received INVITEs that had at least one SHAKEN passport |
| vsReceivedInviteswithDivPASSport | .20 | Received INVITEs that had at least one DIV passport |
| vsSentInviteswithTNValidationPassed | .21 | Sent INVITES that included a TN validation that passed |
| vsSentInviteswithTNValidationFailed | .22 | Sent INVITES that included a TN validation that failed |
| vsSentInviteswithNoTNValidation | .23 | Sent INVITES that included a no TN validation parameter |
| vsInviteRejected | .26 | Number of calls rejected based on verstat and reason code from sti-vs server |
| asBypass | .27 | Number of calls that bypassed the STI-AS server signature request based on message contents |
| vsBypass | .28 | Number of calls that bypassed the STI-VS server verification request based on message contents |
| apStirStatsTypeMax | .29 | Marker indicating the end of the stats types |
The apStirStatsTypeMax marks the end of the defined types. No object should have the index with its value. If an object has this value, the number of the apStirServerStatsType values has been expanded and either this MIB Guide or the MIB Package should be updated.
apAppsStirSystemStatsTable
The following table collects information on the system's status. The apStirSystemStats reference is the name for all apAppsStirSystemStatsTable stats elements.
The apAppsStirSystemStatsTable uses two variables to specify its data, as follows:
- The first is an enumeration of the counter types:
- recent = 1
- total = 2
- permax = 3
- The second is the data category.
For example, the apStirSystemStats instances have an OID of the form
apStirSystemStats.y.z, where:
- y is the ApCounterStatsType (recent = 1, total = 2, or permax = 3)
- z is the data category
Each data category is found within each ApCounterStatsType. The "asQueries" category, for example, is found within the recent, total, and permax counter types.
| MIB Object | Object ID 1.3.6.1.4.1.9148.3.16.1.2.4.9.1.3 |
|---|---|
| apStirSystemStats.recent.asQueries | 1.1 |
| apStirSystemStats.total.asQueries | 2.1 |
| apStirSystemStats.permax.asQueries | 3.1 |
To find the complete OID for a data category:
- Start with the OID of apStirSystemStats (1.3.6.1.4.1.9148.3.16.1.2.4.9.1.3)
- Append your ApCounterStatsType (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.9.1.3.2)
- Append your data category (for example, 1.3.6.1.4.1.9148.3.16.1.2.4.9.1.3.2.1)
Data Categories
| Data Category Name | Data Category Number | Description |
|---|---|---|
| asQueries | .1 | Queries made to the named AS server |
| asSuccessResponses | .2 | Successful responses received from the named AS server |
| asFailResponses | .3 | Failed responses received from the named AS server |
| asFailServiceException | .4 | Failed responses received from the named AS server caused by a service exception |
| asFailPolicyException | .5 | Failed responses received from the named AS server caused by a policy exception |
| vsQueries | .6 | Queries made to the named VS server |
| vsSuccessResponses | .7 | Successful responses received from the named VS server |
| vsFailResponses | .8 | Successful responses received from the named VS server |
| vsSuccessVerification | .9 | Successful verifications received from the named VS server |
| vsFailVerification | .10 | Failed responses received from the named VS server indicating verification failure |
| vsFailServiceException | .11 | Failed responses received from the named VS server caused by a service exception |
| vsFailPolicyException | .12 | Failed responses received from the named VS server caused by a policy exception |
| asSentInviteswithShakenPASSportA | .14 | Sent INVITES that included a SHAKEN passport with attestation level A |
| asSentInviteswithShakenPASSportB | .15 | Sent INVITES that included a SHAKEN passport with attestation level B |
| asSentInviteswithShakenPASSportC | .16 | Sent INVITES that included a SHAKEN passport with attestation level C |
| asSentInviteswithdivPASSport | .17 | Sent INVITES that included a DIV passport |
| vsReceivedInviteswithNoPASSport | .18 | Recevied INVITEs that had no passport |
| vsReceivedInviteswithShakenPASSport | .19 | Received INVITEs that had at least one SHAKEN passport |
| vsReceivedInviteswithDivPASSport | .20 | Received INVITEs that had at least one DIV passport |
| vsSentInviteswithTNValidationPassed | .21 | Sent INVITES that included a TN validation that passed |
| vsSentInviteswithTNValidationFailed | .22 | Sent INVITES that included a TN validation that failed |
| vsSentInviteswithNoTNValidation | .23 | Sent INVITES that included a no TN validation parameter |
| vsInviteRejected | .26 | Number of calls rejected based on verstat and reason code from sti-vs server |
| asBypass | .27 | Number of calls that bypassed the STI-AS server signature request based on message contents |
| vsBypass | .28 | Number of calls that bypassed the STI-VS server verification request based on message contents |
| apStirStatsTypeMax | .29 | Marker indicating the end of the stats types |
The apStirStatsTypeMax marks the end of the defined types. No object should have the index with its value. If an object has this value, the number of the apStirServerStatsType values has been expanded and either this MIB Guide or the MIB Package should be updated.
apAppsNSEPRealmTable
To produce realm-based SNMP statistics for NSEP traffic, the SBC establishes 3 tables populated within the apAppNSEPRealmMIBObjects group, which is the parent object from which the system organizes this SNMP output:
- apAppsNSEPRealmTable
- apAppsNSEPRealmRvalueTable
- apNSEPRealmRvalueStatsTable
These tables include key value objects that use variables to segregate specific value objects. The system assembles name objects, which specify realm and value names concatenated with the statistic value.
The variables used in building the output include:
- X—represents realm-index
- Y—represents rvalue or dialed-number index
- Z—represents the corresponding counter, per realm and per value
The actual data, realm name, value name and statistic, are present within the MIB as follows:
- apNSEPRealmName (1.3.6.1.4.1.9148.3.16.1.2.6.1.1.2.X)—X ranges from 1 to n, where n is the number of configured realms, and is pulled from all realms for which you have enabled nsep-stats.
- apNSEPRvalueName (1.3.6.1.4.1.9148.3.16.1.2.6.2.1.2.Y)—Y ranges from 1 to n, where n is a fixed number and includes all possible r-values, which is statically assigned and the value 100, which is assigned for dialed numbers. The values correspond to the rvalues you have configured in the nsep-stats-profile. The system chooses the respective number for each rvalue statically assigned in the ApNSEPRealmRvalueDNIndex OID.
- apNSEPRealmStats (1.3.6.1.4.1.9148.3.16.1.2.6.3.1.4.X.Y.Z)—Z ranges from 1 to 8 and is pulled from the apNSEPRealmStatsType OID.
The apNSEPRealmName object has the OID 11.3.6.1.4.1.9148.3.16.1.2.6.1.1.2.X. The apNSEPRvalueName object has the OID 1.3.6.1.4.1.9148.3.16.1.2.6.2.1.2.Y. The apNSEPRealmStats object has the OID 1.3.6.1.4.1.9148.3.16.1.2.6.3.1.4. and produces the statistic value when assembled with the X, Y, and Z variables.
This table lists and describes the apNSEPRealmName MIB objects.
| Sequence Number | Object ID apNSEPRealmName 1.3.6.1.4.1.9148.3.16.1.2.6.1.1.2.X | Description |
|---|---|---|
| 1 | .1 | Gives the starting realm-name |
| 2 | .2 | Gives the consecutive realm-name |
| n | n | Gives the next consecutive rvalue |
This table lists and describes the apNSEPRvalueName MIB objects.
| Sequence Number | Object ID apNSEPRvalueName 1.3.6.1.4.1.9148.3.16.1.2.6.2.1.2.Y | Description |
|---|---|---|
| 1 | .1 |
Gives the starting rvalue |
| 2 | .2 | Gives the consecutive rvalue |
| 3 | n | Gives the next consecutive realm-name |
| 4 | 100 | Gives the index of dialed-numbers |
This table lists and describes the apNSEPRealmStats MIB objects.
| Sequence Number | Object ID apNSEPRealmStats 1.3.6.1.4.1.9148.3.16.1.2.6.3.1.4 + | Description |
|---|---|---|
| 1 | .X.Y.1 |
Current Active Sessions Inbound |
| 2 | .X.Y.2 | Total Sessions Inbound |
| 3 | .X.Y.3 | Max of current window Session Inbound |
| 4 | .X.Y.4 | Total session rejected Inbound |
| 5 | .X.Y.5 | Current Active Sessions Outbound |
| 6 | .X.Y.6 | Total Sessions Outbound |
| 7 | .X.Y.7 | Max of current window Session Outbound |
| 8 | .X.Y.8 | Total session rejected Outbound |
To maintain index values for different rValues, the SBC uses a static mapping between all possible rValues and their corresponding indexes. This mapping resides in a table that assigns an idex to every possible r-value and maps all dialed numbers to the index number 100. This maintains a fixed, non-configurable assignment of a particular index number for each rValues and dialed-numbers.
apAppsLatestPeakLicenseUsage
The latest-peak-license-usage MIBOIDs provide you with data collected by the Latest Peak License Usage feature on the SBC. This data includes total, SRTP, and transcoding peak session utilization. The system collects this data every 15 minutes, and updates each session type's peak usage KPI for that window.
You can access the data captured by this feature using SNMP. The data returned by SNMP includes a response with the timestamp on which the most recent 15-minute window collection event occurred, and the data captured within that window.
Note:
You cannot retrieve the output of the show peak-concurrent-license-usage command via SNMP.The SBC uses a set of tables and indexes to create usable output for this peak license usage feature. The applicable SNMP objects are contained within apapps.mib. The root label for this SNMP table is APAPPS-MIB:: ApAppsLatestPeakLicenseUsageEntry.
The applicable SNMP walk produces the apAppsLatestPeakLicenseUsageTable. This table lists the ApAppsLatestPeakLicenseUsageEntry entries, which consist of one index and two groups.
- Index—ApLatestPeakLicenseUsageSessionsType, which uses the following enumerated
values:
- totalSessions(1)
- srtpSessions(2)
- amrTranscodingSessions(3)
Note:
Although this value appears in each applicable table, it is always set to zero because it is deprecated. - amrwbTranscodingSessions(4)
- evsTranscodingSessions(5)
- opusTranscodingSessions(6)
- silkTranscodingSessions(7)
- evrcTranscodingSessions(8)
- evrcbTranscodingSessions(9)
- sessionsTypeMax(10)
- Group—apLatestPeakLicenseUsageHighCount
- Group—apLatestPeakLicenseUsageTimeStamp
Assuming you have all 9 Session License Usages configured, the SBC would fetch 18 OIDs, two each generated by the 9 Session Types. Each session type would have one highcount OID and one timestamp OID (when highcount is reached).
These system generates all OIDs by appending the digits 1 through 9 to their prefix OID. This table uses the root prefix, apLatestPeakLicenseUsageHighCount (1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.*), with the high count value available via the last digit.
| SessionType | Prefix OID (apLatestPeakLicenseUsageHighCount) | highcount |
|---|---|---|
| totalSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .1 |
| srtpSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .2 |
| amrTranscodingSessions
Note: Although this value appears in this table, it is always set to zero because it is deprecated. |
1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .3 |
| amrwbTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .4 |
| evsTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .5 |
| opusTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .6 |
| silkTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .7 |
| evrcTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .8 |
| evrcbTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.2.* | .9 |
This table uses the root prefix, apLatestPeakLicenseUsageTimeStamp (1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.*), with the timestamp value available via the last digit.
| SessionType | Prefix OID (apLatestPeakLicenseUsageTimeStamp) | timestamp |
|---|---|---|
| totalSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .1 |
| srtpSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .2 |
| amrTranscodingSessions
Note: Although this value appears in this table, it is always set to zero because it is deprecated. |
1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .3 |
| amrwbTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .4 |
| evsTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .5 |
| opusTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .6 |
| silkTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .7 |
| evrcTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .8 |
| evrcbTranscodingSessions | 1.3.6.1.4.1.9148.3.16.1.2.7.1.1.3.* | .9 |
apDosThresholdCountersGroup
The following describes the dos-threshold-counters SNMP MIB.
- ap-apps.mib
- apDosThresholdCountersGroup
- 1.3.6.1.4.1.9148.3.16.5
The following table lists and describes the apDosThresholdCountersGroup MIB objects. To form the OID, add 1.3.6.1.4.1.9148.3.16.5 to the value in the OID # column. The OID for Trusted Minor Counter, for example, is 1.3.6.1.4.1.9148.3.16.5.2.
| MIB Object | Object ID 1.3.6.1.4.1.9148.3.16.5 + | Description |
|---|---|---|
| apDosTrustedMinorCounter | .1 | Counter incremented, when trusted bandwidth crossed the minor threshold percentage |
| apDosTrustedMajorCounter | .2 | Counter incremented, when trusted bandwidth crossed the major threshold percentage |
| apDosTrustedCriticalCounter | .3 | Counter incremented, when trusted bandwidth crossed the critical threshold percentage |
| apDosUntrustedMinorCounter | .4 | Counter incremented, when untrusted bandwidth crossed the minor threshold percentage |
| apDosUntrustedMajorCounter | .5 | Counter incremented, when untrusted bandwidth crossed the major threshold percentage |
| apDosUntrustedCriticalCounter | .6 | Counter incremented, when untrusted bandwidth crossed the critical threshold percentage |
| apDosArpMinorCounter | .7 | Counter incremented, when ARP bandwidth crossed the minor threshold percentage |
| apDosArpMajorCounter | .8 | Counter incremented, when ARP bandwidth crossed the major threshold percentage |
| apDosArpCriticalCounter | .9 | Counter incremented, when ARP bandwidth crossed the critical threshold percentage |
MSRP MIB Objects
The following tables describe the SNMP MSRP Get query objects for the SIP MIB (ap-app.mib). There are two categories, including system-wide statistics and realm specific statistics:
- MSRP System Objects—These OIDs append to apMSRPKPISystemStats (1.3.6.1.4.1.9148.3.16.1.2.5.3.1.3.*). These OIDs are within ap-apps.mib under the package apAppsMSRPKPISystemStatsTable.
- MSRP Realm Objects—These OIDs append to apMSRPKPIRealmStats (1.3.6.1.4.1.9148.3.16.1.2.5.2.1.4.*). These OIDs are within ap-apps.mib under the package apAppsMSRPKPIRealmTable.
System Level Objects
The table below lists and describes the GET query names for MSRP Extended system KPI Objects when reporting on the system.
| GET Query Name | Object IDs:1.3.6.1.4.1.9148.3.16.1.2.5.3.1.3.(counter type).+ | Description |
|---|---|---|
| msrp-AvgSENDTransTx | 1 | The average number of MSRP SEND transactions transmitted by the SBC per session |
| msrp-AvgChatSENDTransTx | 2 | The average number of CHAT message SEND transactions transmitted by the SBC per session |
| msrp-AvgIsTypingSENDTransTx | 3 | The average number of IsTyping message SEND transactions transmitted by the SBC per session |
| msrp-AvgReceiptSENDTransTx | 4 | The average number of Receipt message SEND transactions transmitted by the SBC per session |
| msrp-AvgSENDMsgBytesTx | 5 | The average number of bytes in SEND transactions transmitted by the SBC per session |
| msrp-AvgChatSENDMsgBytesTx | 6 | The average number of bytes in CHAT message SEND transactions transmitted by the SBC per session |
| msrp-AvgIsTypingSENDMsgBytesTx | 7 | The average number of bytes in IsTyping message SEND transactions transmitted by the SBC per session |
| msrp-AvgReceiptSENDMsgBytesTx | 8 | The average number of bytes in Receipt message SEND transactions transmitted by the SBC per session |
| msrp-SENDMsgBytesTx | 9 | The number of bytes in MSRP SEND transactions transmitted by the SBC |
| msrp-ChatSENDMsgBytesTx | 10 | The number of bytes in Chat message SEND transactions transmitted by the SBC |
| msrp-IsTypingMsgBytesTx | 11 | The number of bytes in IsTyping message SEND transactions transmitted by the SBC |
| msrp-ReceiptMsgBytesTx | 12 | The number of bytes in Receipt message SEND transactions transmitted by the SBC |
| msrp-SuccessREPORTTransTx | 13 | The number of Success Reports transmitted by the SBC |
| msrp-FailureREPORTTransTx | 14 | The number of Failure Reports transmitted by the SBC |
| msrp-AvgSuccessREPORTMsgBytesTx | 15 | The average number of bytes in Success Reports transmitted by the SBC per session |
| msrp-AvgREPORTFailureBytesTx | 16 | The average number of bytes in Failure Reports transmitted by the SBC per session |
| msrp-AvgREPORTFailureRateTx | 17 | The average number of Success and Failure Reports that were Failure Reports transmitted by the SBC |
| msrp-AvgREPORTSuccessRateTx | 18 | The average number of Success and Failure Reports that were Success Reports transmitted by the SBC |
| msrp-REPORTResp400Tx | 19 | The total number of Report responses that were 400 messages transmitted by the SBC |
| msrp-REPORTResp401Tx | 20 | The total number of Report responses that were 401 messages transmitted by the SBC |
| msrp-REPORTResp403Tx | 21 | The total number of Report responses that were 403 messages transmitted by the SBC |
| msrp-REPORTResp404Tx | 22 | The total number of Report responses that were 404 messages transmitted by the SBC |
| msrp-REPORTResp408Tx | 23 | The total number of Report responses that were 408 messages transmitted by the SBC |
| msrp-REPORTResp413Tx | 24 | The total number of Report responses that were 413 messages transmitted by the SBC |
| msrp-REPORTResp415Tx | 25 | The total number of Report responses that were 415 messages transmitted by the SBC |
| msrp-REPORTResp423Tx | 26 | The total number of Report responses that were 423 messages transmitted by the SBC |
| msrp-REPORTResp424Tx | 27 | The total number of Report responses that were 424 messages transmitted by the SBC |
| msrp-REPORTResp425Tx | 28 | The total number of Report responses that were 425 messages transmitted by the SBC |
| msrp-REPORTResp428Tx | 29 | The total number of Report responses that were 428 messages transmitted by the SBC |
| msrp-REPORTResp481Tx | 30 | The total number of Report responses that were 481 messages transmitted by the SBC |
| msrp-REPORTResp501Tx | 31 | The total number of Report responses that were 501 messages transmitted by the SBC |
| msrp-REPORTResp506Tx | 32 | The total number of Report responses that were 506 messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes400Tx | 33 | The average number of bytes in 400 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes401Tx | 34 | The average number of bytes in 401 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes403Tx | 35 | The average number of bytes in 403 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes404Tx | 36 | The average number of bytes in 404 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes408Tx | 37 | The average number of bytes in 408 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes413Tx | 38 | The average number of bytes in 413 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes415Tx | 39 | The average number of bytes in 415 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes423Tx | 40 | The average number of bytes in 423 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes424Tx | 41 | The average number of bytes in 424 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes425Tx | 42 | The average number of bytes in 425 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes428Tx | 43 | The average number of bytes in 428 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes481Tx | 44 | The average number of bytes in 481 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes501Tx | 45 | The average number of bytes in 501 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes506Tx | 46 | The average number of bytes in 506 Report Failure messages transmitted by the SBC |
| msrp-TransResponsesTx | 47 | The total number of Responses transmitted by the SBC |
| msrp-SuccessTransResponsesTx | 48 | The total number of Success Responses transmitted by the SBC |
| msrp-TransResp400Tx | 49 | The total number of 400 Responses transmitted by the SBC |
| msrp-TransResp401Tx | 50 | The total number of 401 Responses transmitted by the SBC |
| msrp-TransResp403Tx | 51 | The total number of 403 Responses transmitted by the SBC |
| msrp-TransResp404Tx | 52 | The total number of 404 Responses transmitted by the SBC |
| msrp-TransResp408Tx | 53 | The total number of 408 Responses transmitted by the SBC |
| msrp-TransResp413Tx | 54 | The total number of 413 Responses transmitted by the SBC |
| msrp-TransResp415Tx | 55 | The total number of 415 Responses transmitted by the SBC |
| msrp-TransResp423Tx | 56 | The total number of 423 Responses transmitted by the SBC |
| msrp-TransResp424Tx | 57 | The total number of 424 Responses transmitted by the SBC |
| msrp-TransResp425Tx | 58 | The total number of 425 Responses transmitted by the SBC |
| msrp-TransResp428Tx | 59 | The total number of 428 Responses transmitted by the SBC |
| msrp-TransResp481Tx | 60 | The total number of 481 Responses transmitted by the SBC |
| msrp-TransResp501Tx | 61 | The total number of 501 Responses transmitted by the SBC |
| msrp-TransResp506Tx | 62 | The total number of 506 Responses transmitted by the SBC |
| msrp-AvgSENDTransRx | 63 | The average number of MSRP SEND transactions received by the SBC per session |
| msrp-AvgChatSENDTransRx | 64 | The average number of CHAT message SEND transactions received by the SBC per session |
| msrp-AvgIsTypingSENDTransRx | 65 | The average number of IsTyping message SEND transactions received by the SBC per session |
| msrp-AvgReceiptSENDTransRx | 66 | The average number of Receipt message SEND transactions received by the SBC per session |
| msrp-AvgSENDMsgBytesRx | 67 | The average number of bytes in SEND transactions received by the SBC per session |
| msrp-AvgChatSENDMsgBytesRx | 68 | The average number of bytes in Chat message SEND transactions received by the SBC per session |
| msrp-AvgIsTypingSENDMsgBytesRx | 69 | The average number of bytes in IsTyping message SEND transactions received by the SBC per session |
| msrp-AvgReceiptSENDMsgBytesRx | 70 | The average number of bytes in Receipt message SEND transactions received by the SBC per session |
| msrp-SENDMsgBytesRx | 71 | The number of bytes in MSRP SEND transactions received by the SBC |
| msrp-ChatSENDMsgBytesRx | 72 | The number of bytes in Chat message SEND transactions received by the SBC |
| msrp-IsTypingMsgBytesRx | 73 | The number of bytes in IsTyping message SEND transactions received by the SBC |
| msrp-ReceiptMsgBytesRx | 74 | The number of bytes in Receipt message SEND transactions received by the SBC |
| msrp-SuccessREPORTTransRx | 75 | The number of Success Reports received by the SBC |
| msrp-FailureREPORTTransRx | 76 | The number of Failure Reports received by the SBC |
| msrp-AvgSuccessREPORTMsgBytesRx | 77 | The average number of bytes in Success Reports received by the SBC per session |
| msrp-AvgREPORTFailureBytesRx | 78 | The average number of bytes in Success Reports received by the SBC per session |
| msrp-AvgREPORTFailureRateRx | 79 | The average number of Reports received by the SBC that were Failure Reports |
| msrp-AvgREPORTSuccessRateRx | 80 | The average number of Reports received by the SBC that were Success Reports |
| msrp-REPORTResp400Rx | 81 | The total number of Report responses conveying 400 messages received by the SBC |
| msrp-REPORTResp401Rx | 82 | The total number of Report responses conveying 401 messages received by the SBC |
| msrp-REPORTResp403Rx | 83 | The total number of Report responses conveying 403 messages received by the SBC |
| msrp-REPORTResp404Rx | 84 | The total number of Report responses conveying 404 messages received by the SBC |
| msrp-REPORTResp408Rx | 85 | The total number of Report responses conveying 408 messages received by the SBC |
| msrp-REPORTResp413Rx | 86 | The total number of Report responses conveying 413 messages received by the SBC |
| msrp-REPORTResp415Rx | 87 | The total number of Report responses conveying 415 messages received by the SBC |
| msrp-REPORTResp423Rx | 88 | The total number of Report responses conveying 423 messages received by the SBC |
| msrp-REPORTResp424Rx | 89 | The total number of Report responses conveying 424 messages received by the SBC |
| msrp-REPORTResp425Rx | 90 | The total number of Report responses conveying 425 messages received by the SBC |
| msrp-REPORTResp428Rx | 91 | The total number of Report responses conveying 428 messages received by the SBC |
| msrp-REPORTResp481Rx | 92 | The total number of Report responses conveying 481 messages received by the SBC |
| msrp-REPORTResp501Rx | 93 | The total number of Report responses conveying 501 messages received by the SBC |
| msrp-REPORTResp506Rx | 94 | The total number of Report responses conveying 506 messages received by the SBC |
| msrp-AvgREPORTFailureBytes400Rx | 95 | The average number of Failure Report bytes conveying 400 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes401Rx | 96 | The average number of Failure Report bytes conveying 401 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes403Rx | 97 | The average number of Failure Report bytes conveying 403 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes404Rx | 98 | The average number of Failure Report bytes conveying 404 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes408Rx | 99 | The average number of Failure Report bytes conveying 408 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes413Rx | 100 | The average number of Failure Report bytes conveying 413 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes415Rx | 101 | The average number of Failure Report bytes conveying 415 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes423Rx | 102 | The average number of Failure Report bytes conveying 423 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes424Rx | 103 | The average number of Failure Report bytes conveying 424 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes425Rx | 104 | The average number of Failure Report bytes conveying 425 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes428Rx | 105 | The average number of Failure Report bytes conveying 428 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes481Rx | 106 | The average number of Failure Report bytes conveying 481 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes501Rx | 107 | The average number of Failure Report bytes conveying 501 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes506Rx | 108 | The average number of Failure Report bytes conveying 506 messages received by the SBC per session |
| msrp-TransResponsesRx | 109 | The total number of Response transactions received by the SBC |
| msrp-SuccessTransResponsesRx | 110 | The total number of Success Response transactions received by the SBC |
| msrp-TransResp400Rx | 111 | The total number of Response transactions conveying 400 messages received by the SBC |
| msrp-TransResp401Rx | 112 | The total number of Response transactions conveying 401 messages received by the SBC |
| msrp-TransResp403Rx | 113 | The total number of Response transactions conveying 403 messages received by the SBC |
| msrp-TransResp404Rx | 114 | The total number of Response transactions conveying 404 messages received by the SBC |
| msrp-TransResp408Rx | 115 | The total number of Response transactions conveying 408 messages received by the SBC |
| msrp-TransResp413Rx | 116 | The total number of Response transactions conveying 413 messages received by the SBC |
| msrp-TransResp415Rx | 117 | The total number of Response transactions conveying 415 messages received by the SBC |
| msrp-TransResp423Rx | 118 | The total number of Response transactions conveying 423 messages received by the SBC |
| msrp-TransResp424Rx | 119 | The total number of Response transactions conveying 424 messages received by the SBC |
| msrp-TransResp425Rx | 120 | The total number of Response transactions conveying 425 messages received by the SBC |
| msrp-TransResp428Rx | 121 | The total number of Response transactions conveying 428 messages received by the SBC |
| msrp-TransResp481Rx | 122 | The total number of Response transactions conveying 481 messages received by the SBC |
| msrp-TransResp501Rx | 123 | The total number of Response transactions conveying 501 messages received by the SBC |
| msrp-TransResp506Rx | 124 | The total number of Response transactions conveying 506 messages received by the SBC |
Realm Level Objects
The table below lists and describes the GET query names for MSRP Extended system KPI Objects when reporting on realms.
| GET Query Name | Object IDs: 1.3.6.1.4.1.9148.3.16.1.2.5.2.1.4.(realm ID).(counter type).+ | Description |
|---|---|---|
| msrp-AvgSENDTransTx | 1 | The average number of MSRP SEND transactions transmitted by the SBC per session |
| msrp-AvgChatSENDTransTx | 2 | The average number of CHAT message SEND transactions transmitted by the SBC per session |
| msrp-AvgIsTypingSENDTransTx | 3 | The average number of IsTyping message SEND transactions transmitted by the SBC per session |
| msrp-AvgReceiptSENDTransTx | 4 | The average number of Receipt message SEND transactions transmitted by the SBC per session |
| msrp-AvgSENDMsgBytesTx | 5 | The average number of bytes in SEND transactions transmitted by the SBC per session |
| msrp-AvgChatSENDMsgBytesTx | 6 | The average number of bytes in CHAT message SEND transactions transmitted by the SBC per session |
| msrp-AvgIsTypingSENDMsgBytesTx | 7 | The average number of bytes in IsTyping message SEND transactions transmitted by the SBC per session |
| msrp-AvgReceiptSENDMsgBytesTx | 8 | The average number of bytes in Receipt message SEND transactions transmitted by the SBC per session |
| msrp-SENDMsgBytesTx | 9 | The number of bytes in MSRP SEND transactions transmitted by the SBC |
| msrp-ChatSENDMsgBytesTx | 10 | The number of bytes in Chat message SEND transactions transmitted by the SBC |
| msrp-IsTypingMsgBytesTx | 11 | The number of bytes in IsTyping message SEND transactions transmitted by the SBC |
| msrp-ReceiptMsgBytesTx | 12 | The number of bytes in Receipt message SEND transactions transmitted by the SBC |
| msrp-SuccessREPORTTransTx | 13 | The number of Success Reports transmitted by the SBC |
| msrp-FailureREPORTTransTx | 14 | The number of Failure Reports transmitted by the SBC |
| msrp-AvgSuccessREPORTMsgBytesTx | 15 | The average number of bytes in Success Reports transmitted by the SBC per session |
| msrp-AvgREPORTFailureBytesTx | 16 | The average number of bytes in Failure Reports transmitted by the SBC per session |
| msrp-AvgREPORTFailureRateTx | 17 | The average number of Success and Failure Reports that were Failure Reports transmitted by the SBC |
| msrp-AvgREPORTSuccessRateTx | 18 | The average number of Success and Failure Reports that were Success Reports transmitted by the SBC |
| msrp-REPORTResp400Tx | 19 | The total number of Report responses that were 400 messages transmitted by the SBC |
| msrp-REPORTResp401Tx | 20 | The total number of Report responses that were 401 messages transmitted by the SBC |
| msrp-REPORTResp403Tx | 21 | The total number of Report responses that were 403 messages transmitted by the SBC |
| msrp-REPORTResp404Tx | 22 | The total number of Report responses that were 404 messages transmitted by the SBC |
| msrp-REPORTResp408Tx | 23 | The total number of Report responses that were 408 messages transmitted by the SBC |
| msrp-REPORTResp413Tx | 24 | The total number of Report responses that were 413 messages transmitted by the SBC |
| msrp-REPORTResp415Tx | 25 | The total number of Report responses that were 415 messages transmitted by the SBC |
| msrp-REPORTResp423Tx | 26 | The total number of Report responses that were 423 messages transmitted by the SBC |
| msrp-REPORTResp424Tx | 27 | The total number of Report responses that were 424 messages transmitted by the SBC |
| msrp-REPORTResp425Tx | 28 | The total number of Report responses that were 425 messages transmitted by the SBC |
| msrp-REPORTResp428Tx | 29 | The total number of Report responses that were 428 messages transmitted by the SBC |
| msrp-REPORTResp481Tx | 30 | The total number of Report responses that were 481 messages transmitted by the SBC |
| msrp-REPORTResp501Tx | 31 | The total number of Report responses that were 501 messages transmitted by the SBC |
| msrp-REPORTResp506Tx | 32 | The total number of Report responses that were 506 messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes400Tx | 33 | The average number of bytes in 400 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes401Tx | 34 | The average number of bytes in 401 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes403Tx | 35 | The average number of bytes in 403 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes404Tx | 36 | The average number of bytes in 404 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes408Tx | 37 | The average number of bytes in 408 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes413Tx | 38 | The average number of bytes in 413 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes415Tx | 39 | The average number of bytes in 415 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes423Tx | 40 | The average number of bytes in 423 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes424Tx | 41 | The average number of bytes in 424 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes425Tx | 42 | The average number of bytes in 425 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes428Tx | 43 | The average number of bytes in 428 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes481Tx | 44 | The average number of bytes in 481 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes501Tx | 45 | The average number of bytes in 501 Report Failure messages transmitted by the SBC |
| msrp-AvgREPORTFailureBytes506Tx | 46 | The average number of bytes in 506 Report Failure messages transmitted by the SBC |
| msrp-TransResponsesTx | 47 | The total number of Responses transmitted by the SBC |
| msrp-SuccessTransResponsesTx | 48 | The total number of Success Responses transmitted by the SBC |
| msrp-TransResp400Tx | 49 | The total number of 400 Responses transmitted by the SBC |
| msrp-TransResp401Tx | 50 | The total number of 401 Responses transmitted by the SBC |
| msrp-TransResp403Tx | 51 | The total number of 403 Responses transmitted by the SBC |
| msrp-TransResp404Tx | 52 | The total number of 404 Responses transmitted by the SBC |
| msrp-TransResp408Tx | 53 | The total number of 408 Responses transmitted by the SBC |
| msrp-TransResp413Tx | 54 | The total number of 413 Responses transmitted by the SBC |
| msrp-TransResp415Tx | 55 | The total number of 415 Responses transmitted by the SBC |
| msrp-TransResp423Tx | 56 | The total number of 423 Responses transmitted by the SBC |
| msrp-TransResp424Tx | 57 | The total number of 424 Responses transmitted by the SBC |
| msrp-TransResp425Tx | 58 | The total number of 425 Responses transmitted by the SBC |
| msrp-TransResp428Tx | 59 | The total number of 428 Responses transmitted by the SBC |
| msrp-TransResp481Tx | 60 | The total number of 481 Responses transmitted by the SBC |
| msrp-TransResp501Tx | 61 | The total number of 501 Responses transmitted by the SBC |
| msrp-TransResp506Tx | 62 | The total number of 506 Responses transmitted by the SBC |
| msrp-AvgSENDTransRx | 63 | The average number of MSRP SEND transactions received by the SBC per session |
| msrp-AvgChatSENDTransRx | 64 | The average number of CHAT message SEND transactions received by the SBC per session |
| msrp-AvgIsTypingSENDTransRx | 65 | The average number of IsTyping message SEND transactions received by the SBC per session |
| msrp-AvgReceiptSENDTransRx | 66 | The average number of Receipt message SEND transactions received by the SBC per session |
| msrp-AvgSENDMsgBytesRx | 67 | The average number of bytes in SEND transactions received by the SBC per session |
| msrp-AvgChatSENDMsgBytesRx | 68 | The average number of bytes in Chat message SEND transactions received by the SBC per session |
| msrp-AvgIsTypingSENDMsgBytesRx | 69 | The average number of bytes in IsTyping message SEND transactions received by the SBC per session |
| msrp-AvgReceiptSENDMsgBytesRx | 70 | The average number of bytes in Receipt message SEND transactions received by the SBC per session |
| msrp-SENDMsgBytesRx | 71 | The number of bytes in MSRP SEND transactions received by the SBC |
| msrp-ChatSENDMsgBytesRx | 72 | The number of bytes in Chat message SEND transactions received by the SBC |
| msrp-IsTypingMsgBytesRx | 73 | The number of bytes in IsTyping message SEND transactions received by the SBC |
| msrp-ReceiptMsgBytesRx | 74 | The number of bytes in Receipt message SEND transactions received by the SBC |
| msrp-SuccessREPORTTransRx | 75 | The number of Success Reports received by the SBC |
| msrp-FailureREPORTTransRx | 76 | The number of Failure Reports received by the SBC |
| msrp-AvgSuccessREPORTMsgBytesRx | 77 | The average number of bytes in Success Reports received by the SBC per session |
| msrp-AvgREPORTFailureBytesRx | 78 | The average number of bytes in Success Reports received by the SBC per session |
| msrp-AvgREPORTFailureRateRx | 79 | The average number of Reports received by the SBC that were Failure Reports |
| msrp-AvgREPORTSuccessRateRx | 80 | The average number of Reports received by the SBC that were Success Reports |
| msrp-REPORTResp400Rx | 81 | The total number of Report responses conveying 400 messages received by the SBC |
| msrp-REPORTResp401Rx | 82 | The total number of Report responses conveying 401 messages received by the SBC |
| msrp-REPORTResp403Rx | 83 | The total number of Report responses conveying 403 messages received by the SBC |
| msrp-REPORTResp404Rx | 84 | The total number of Report responses conveying 404 messages received by the SBC |
| msrp-REPORTResp408Rx | 85 | The total number of Report responses conveying 408 messages received by the SBC |
| msrp-REPORTResp413Rx | 86 | The total number of Report responses conveying 413 messages received by the SBC |
| msrp-REPORTResp415Rx | 87 | The total number of Report responses conveying 415 messages received by the SBC |
| msrp-REPORTResp423Rx | 88 | The total number of Report responses conveying 423 messages received by the SBC |
| msrp-REPORTResp424Rx | 89 | The total number of Report responses conveying 424 messages received by the SBC |
| msrp-REPORTResp425Rx | 90 | The total number of Report responses conveying 425 messages received by the SBC |
| msrp-REPORTResp428Rx | 91 | The total number of Report responses conveying 428 messages received by the SBC |
| msrp-REPORTResp481Rx | 92 | The total number of Report responses conveying 481 messages received by the SBC |
| msrp-REPORTResp501Rx | 93 | The total number of Report responses conveying 501 messages received by the SBC |
| msrp-REPORTResp506Rx | 94 | The total number of Report responses conveying 506 messages received by the SBC |
| msrp-AvgREPORTFailureBytes400Rx | 95 | The average number of Failure Report bytes conveying 400 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes401Rx | 96 | The average number of Failure Report bytes conveying 401 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes403Rx | 97 | The average number of Failure Report bytes conveying 403 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes404Rx | 98 | The average number of Failure Report bytes conveying 404 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes408Rx | 99 | The average number of Failure Report bytes conveying 408 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes413Rx | 100 | The average number of Failure Report bytes conveying 413 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes415Rx | 101 | The average number of Failure Report bytes conveying 415 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes423Rx | 102 | The average number of Failure Report bytes conveying 423 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes424Rx | 103 | The average number of Failure Report bytes conveying 424 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes425Rx | 104 | The average number of Failure Report bytes conveying 425 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes428Rx | 105 | The average number of Failure Report bytes conveying 428 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes481Rx | 106 | The average number of Failure Report bytes conveying 481 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes501Rx | 107 | The average number of Failure Report bytes conveying 501 messages received by the SBC per session |
| msrp-AvgREPORTFailureBytes506Rx | 108 | The average number of Failure Report bytes conveying 506 messages received by the SBC per session |
| msrp-TransResponsesRx | 109 | The total number of Response transactions received by the SBC |
| msrp-SuccessTransResponsesRx | 110 | The total number of Success Response transactions received by the SBC |
| msrp-TransResp400Rx | 111 | The total number of Response transactions conveying 400 messages received by the SBC |
| msrp-TransResp401Rx | 112 | The total number of Response transactions conveying 401 messages received by the SBC |
| msrp-TransResp403Rx | 113 | The total number of Response transactions conveying 403 messages received by the SBC |
| msrp-TransResp404Rx | 114 | The total number of Response transactions conveying 404 messages received by the SBC |
| msrp-TransResp408Rx | 115 | The total number of Response transactions conveying 408 messages received by the SBC |
| msrp-TransResp413Rx | 116 | The total number of Response transactions conveying 413 messages received by the SBC |
| msrp-TransResp415Rx | 117 | The total number of Response transactions conveying 415 messages received by the SBC |
| msrp-TransResp423Rx | 118 | The total number of Response transactions conveying 423 messages received by the SBC |
| msrp-TransResp424Rx | 119 | The total number of Response transactions conveying 424 messages received by the SBC |
| msrp-TransResp425Rx | 120 | The total number of Response transactions conveying 425 messages received by the SBC |
| msrp-TransResp428Rx | 121 | The total number of Response transactions conveying 428 messages received by the SBC |
| msrp-TransResp481Rx | 122 | The total number of Response transactions conveying 481 messages received by the SBC |
| msrp-TransResp501Rx | 123 | The total number of Response transactions conveying 501 messages received by the SBC |
| msrp-TransResp506Rx | 124 | The total number of Response transactions conveying 506 messages received by the SBC |
Note:
The system establishes realm level stats OIDs for the first (or single) realm by adding the system-assigned realm identifier and the type and category as the suffix (.first realm identifier.*.*) to the base OID. Should there be multiple realms, the OID is similarly numbered using the suffix (.second realm identifier.*.*) for the second realm, and (.third realm identifier.*.*) for the third realm and so forth.