Table Of Contents
Data File Formats
Data Files—Maintenance and Usage
Performance Polling Record Formats
Cisco CallManager Port Usage and CPU Usage—Record Type 100
Cisco CallManager-Controlled Gateway Port Usage—Record Type 101
Cisco IOS Gateway Port Usage—Record Type 102
Notes on Record Type 102
Channelized T1 DS0 Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 103
Record Type 104—Not Used
Cisco Digital PBX Adapter Port and CPU Usage—Record Type 105
Cisco IOS Gatekeeper Zone Usage—Record Type 106
Cisco IOS Device CPU Usage—Record Type 107
Cisco Device Memory Usage—Record Type 108
Cisco IOS Gateway Digital Signal Processor Usage—Record Type 109
T1 PRI DS0 Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 110
E1 PRI DS0 Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 111
Channelized T1 CAS DS0 Channel Status for Cisco IOS Gateways—Record Type 112
Channelized E1 CAS DS0 Channel Status for Cisco IOS Gateways—Record Type 113
T1 PRI DS0 Channel Status for Cisco IOS Gateways—Record Type 114
E1 PRI DS0 Channel Status for Cisco IOS Gateways—Record Type 115
BRI Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 116
BRI Channel Status for Cisco IOS Gateways—Record Type 117
Cisco Unity Express Mailbox Usage—Record Type 118
Cisco CallManager Express Ephone and Key Ephone Usage—Record Type 119
Cisco Survivable Remote Site Telephony Usage—Record Type 120
Cisco Unity Port Usage—Record Type 121
Consolidated DSP Usage for Cisco IOS Devices—Record Type 122
Cisco CallManager Usage 2—Record Type 123
FXS Port Usage for Cisco CallManager-Controlled Gateways—Record Type 124
FXO Port Usage for Cisco CallManager-Controlled Gateways—Record Type 125
Cisco CallManager CTI Manager Usage—Record Type 126
Cisco CallManager Analog Access Gateway Usage—Record Type 127
Cisco CallManager H323 Gateway Usage—Record Type 128
Cisco CallManager Location Usage—Record Type 129
Cisco CallManager Media Streaming Application Usage—Record Type 130
Cisco CallManager MOH Usage—Record Type 131
Cisco CallManager MTP Usage—Record Type 132
Cisco CallManager Hardware Conference Bridge Usage—Record Type 133
Cisco CallManager Software Conference Bridge Usage—Record Type 134
Cisco CallManager Transcoder—Record Type 135
T1 PRI Usage for Cisco CallManager-Controlled Gateways—Record Type 136
E1 PRI Usage for Cisco CallManager-Controlled Gateways—Record Type 137
T1 CAS Usage for Cisco CallManager-Controlled Gateways—Record Type 138
Node-to-Node Test Record Formats
Echo—Record Type 200
Ping Path Echo—Record Type 201
Record Type 202—Not Used
Ping Path Echo—Record Type 204
Jitter MOS, ICPIF, and Processed Data—Record Type 205
Data File Formats
IP Communications Operations Manager (Operations Manager) writes data files for performance polling and node-to-node tests. This topic includes the following:
•Data Files—Maintenance and Usage
•Performance Polling Record Formats
•Node-to-Node Test Record Formats
Data Files—Maintenance and Usage
Table I-1 provides information about data files that Operations Manager generates for node-to-node test and performance polling.
Table I-1 Performance Polling and Node-to-Node Data Files
Data File
|
Node-to-Node Tests
|
Performance Polling
|
Storage Location |
NMSROOT\data\N2NTests\testname |
NMSROOT\data\gsu\_#GSUDATA#_ |
Filenames |
•YYYYMMDD.csv—One data file is written per day; named with year, month, and day; for example:
•IPSLATestInfo.log—Contains all the configuration information for the node-to-node-test. |
•<device_name>[$<port or card name>]_YYYYMMDD.csv—One data file is written per day per device: –<device_name> is the name or IP address of the device. –<port or card name> is optional; it is the name of a T1/E1 port or FXS card on a switch in the Cisco Catalyst 6000 family. A filename that includes not only a device name but a port or card name contains data on individual MGCP gateways within a switch in the Cisco Catalyst 6000 family. |
Retention period |
30 days |
3 days |
Operations Manager daily purging deletes files that are older than the retention period. Note If you want to retain node-to-node test or performance polling data files beyond the retention period, you should back them up or move them to another folder or server. |
Record format |
Fixed 38-field format. The 38th field is reserved and contains the test name. For detailed record formats, see Node-to-Node Test Record Formats |
Fixed 38-field format. The 38th field is reserved and contains an asterisk (*). For detailed record formats, see Performance Polling Record Formats. |
Performance Polling Record Formats
There is one record for each type of data collected. The record types are summarized in Table I-2. Device types and the record types for each are summarized in Table I-3.
Table I-3 lists device types and record types that will be written for each device type.
Table I-3 Performance Polling Record Types for Each Device Type
Device Types
|
Record Number
|
Record Descriptions
|
CallManager Express Gatekeepers H323 Gateways SRST Devices |
102 106 107 108 109 112 113 114 115 117 119 120 122 |
•Cisco IOS Gateway Port Usage •Cisco IOS Gatekeeper Zone Usage •Cisco IOS Gateway or Gatekeeper CPU Usage •Cisco IOS Gateway or Gatekeeper Memory Usage •Cisco IOS Gateway Digital Signal Processor (DSP) Usage •Channelized T1 CAS DS0 Channel Status for Cisco IOS Gateways •Channelized E1 CAS DS0 Channel Status for Cisco IOS Gateways •T1 PRI DS0 Channel Status for Cisco IOS Gateway •E1 PRI DS0 Channel Status for Cisco IOS Gateways •BRI Channel Status for Cisco IOS Gateways •Cisco CallManager Express Usage •Cisco Survivable Remote Site Telephony Usage •Consolidated DSP Usage |
Cisco CallManager |
100 123 126 127 128 129 130 131 132 133 134 135 |
•Cisco CallManager Port Usage •Cisco CallManager Usage 2 •Cisco CallManager CTI Manager Usage •Cisco CallManager Analog Access Gateway Usage •Cisco CallManager H323 Gateway Usage •Cisco CallManager Location Usage •Cisco CallManager Media Streaming Application Usage •Cisco CallManager MOH Usage •Cisco CallManager MTP Usage •Cisco CallManager Hardware Conference Bridge Usage •Cisco CallManager Software Conference Bridge Usage •Cisco CallManager Transcoder Usage |
Cisco Unity |
121 |
Cisco Unity Usage |
Cisco Unity Express |
118 |
Cisco Unity Express Mailbox Usage |
Gateways (MGCP gateways registered to Cisco CallManager) |
101 103 110 111 116 124 125 136 137 138 |
•Cisco CallManager-Controlled Gateway Port Usage •Channelized T1 DS0 Channel Status for Cisco CallManager-Controlled Gateways •T1 PRI DS0 Channel Status for Cisco CallManager-Controlled Gateways •E1 PRI DS0 Channel Status for Cisco CallManager-Controlled Gateways •BRI Channel Status for Cisco CallManager-Controlled Gateways •FXS Port Usage for Cisco CallManager-Controlled Gateways •FXO Port Usage for Cisco CallManager-Controlled Gateways •T1 PRI Usage for Cisco CallManager-Controlled Gateways •E1 PRI Usage for Cisco CallManager-Controlled Gateways •T1 CAS Usage for Cisco CallManager-Controlled Gateways |
Voice Mail Gateways |
105 |
Cisco Digital PBX Adapter Port and CPU Usage |
Cisco CallManager Port Usage and CPU Usage—Record Type 100
This record contains the port usage and CPU usage for a Cisco CallManager. Cisco CallManager supports the following ports:
•T1 PRI
•T1 CAS
•E1 PRI
•BRI
•FXO
•FXS
Table I-4 Format of Record Type 100
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 100. |
100 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time. |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager. |
Example: CCM3 |
5 |
CPU 1 usage |
Number |
Measured percentage CPU utilization for CPU 1 at time stamp. |
Š 0 and £ 100 |
6 |
Active calls |
Number |
Number of calls active at time stamp. This counter shows calls that are fully established and in use. Calls in setup mode or in teardown mode are not reported by this count. |
Š 0 |
7 |
Total PRIs |
Number |
Number of PRI channels (T1/E1 PRI) configured on Cisco CallManager platform. |
Š 0 |
8 |
Active PRIs |
Number |
Number of PRI channels (T1/E1 PRI) active at time stamp. |
Š 0 and £ total PRIs |
9 |
Total T1 CAS |
Number |
Number of T1 CAS channels configured on Cisco CallManager platform. |
Š 0 |
10 |
Active T1 CAS |
Number |
Number of T1 CAS channels active at time stamp. |
Š 0 and £ total T1/E1 |
11 |
Total FXS |
Number |
Number of FXS ports configured on Cisco CallManager platform. |
Š 0 |
12 |
Active FXS |
Number |
Number of FXS ports active at time stamp. |
Š 0 and £ total FXS |
13 |
Total FXO |
Number |
Number of FXO ports configured on Cisco CallManager platform. |
Š 0 |
14 |
Active FXO |
Number |
Number of FXO ports active at time stamp. |
Š 0 and £ total FXO |
15 |
CPU 2 usage |
Number |
Measured percentage CPU utilization at time stamp for CPU 2 or asterisk (*) to indicate that CPU 2 is not present. |
Š 0 and £ 100 or * |
16 |
CPU 3 usage |
Number |
Measured percentage CPU utilization at time stamp for CPU 3 or asterisk (*) to indicate that CPU 3 is not present. |
Š 0 and £ 100 or * |
17 |
CPU 4 usage |
Number |
Measured number CPU utilization at time stamp for CPU 4 or asterisk (*) to indicate that CPU 4 is not present. |
Š 0 and £ 100 or * |
18 |
CPU 5 usage |
Number |
Measured percentage CPU utilization at time stamp for CPU 5 or asterisk (*) to indicate that CPU 5 is not present. |
Š 0 and £ 100 or * |
19 |
Total CPU usage |
Number |
Measured percentage CPU utilization at time stamp for all CPUs. |
Š 0 |
20 |
Total T1 PRI |
Number |
Number of T1 PRI channels configured on Cisco CallManager platform. |
Š 0 |
21 |
Active T1 PRI |
Number |
Number of T1 PRI channels that were active at time stamp. |
Š 0 and £ total T1 PRIs |
22 |
Total E1 PRI |
Number |
Number of E1 PRI channels configured on Cisco CallManager platform. |
Š 0 |
23 |
Active E1 PRI |
Number |
Number of E1 PRI channels active at time stamp. |
Š 0 and £ total E1 PRIs |
24 |
Total BRI |
Number |
Number of BRI channels configured on Cisco CallManager platform. |
Š 0 |
25 |
Active BRI |
Number |
Number of BRI channels active at time stamp. |
Š 0 and £ total BRIs |
26 |
Calls attempted |
Number |
Number of calls attempted on this Cisco CallManager |
Š 0 |
27 |
Calls complete |
Number |
Number of calls completed on this Cisco CallManager |
Š 0 |
28 |
Calls in progress |
Number |
Number of calls in progress on this Cisco CallManager |
Š 0 |
29 |
Percentage active T1 CAS |
Number |
T1 CAS utilization at time stamp for this Cisco CallManager |
Š 0 and £ 100 |
30 |
Percentage FXS |
Number |
FXS port utilization at time stamp for this Cisco CallManager |
Š 0 and £ 100 |
31 |
Percentage FXO |
Number |
FXO port utilization at time stamp for this Cisco CallManager |
Š 0 and £ 100 |
32 |
Percentage active T1 PRI |
Number |
T1 PRI utilization at time stamp for this Cisco CallManager |
Š 0 and £ 100 |
33 |
Percentage active E1 PRI |
Number |
E1 PRI utilization at time stamp for this Cisco CallManager |
Š 0 and £ 100 |
34 |
Percentage active BRI |
Number |
BRI utilization at time stamp for this Cisco CallManager |
Š 0 and £ 100 |
35 |
None |
Null indicator |
Not used. |
* |
Note Fields 36 and 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager-Controlled Gateway Port Usage—Record Type 101
This record contains the port usage for a Cisco CallManager-controlled MGCP gateway. MGCP gateways support the following ports:
•T1 PRI
•T1 CAS
•E1 PRI
•BRI
•FXS
•FXO
Table I-5 Format of Record Type 101
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 101. |
101 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time. |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject gateway. |
Example: sanjose-5720 |
5 |
Active calls |
Null indicator |
Not used. Cisco CallManager does not currently provide this information. |
* |
6 |
Total PRI |
Number |
Number of PRI channels (T1/E1 PRI) configured on the gateway. |
Š 0 |
7 |
Active PRI |
Number |
Number of PRI channels (T1/E1 PRI) active at time stamp. |
Š 0 and £ total PRIs |
8 |
Total T1 CAS |
Number |
Number of T1 CAS channels configured on the gateway. |
Š 0 |
9 |
Active T1 CAS |
Number |
Number of T1 CAS channels active at time stamp. |
Š 0 and £ total T1 CAS |
10 |
Total E1 CAS |
Null indicator |
Not used. Cisco CallManager does not currently support E1 CAS. |
* |
11 |
Active E1 CAS |
Null indicator |
Not used. Cisco CallManager does not currently support E1 CAS. |
* |
12 |
Total FXS |
Number |
Number of FXS ports configured on the gateway. |
Š 0 |
13 |
Active FXS |
Number |
Number of FXS ports active at time stamp. |
Š 0 and £ total FXS |
14 |
Total FXO |
Number |
Number of FXO ports configured on the gateway. |
Š 0 |
15 |
Active FXO |
Number |
Number of FXO ports active at time stamp. |
Š 0 and £ total FXO |
16 |
Cisco CallManager Name |
Text |
Data for the subject gateway was collected from this Cisco CallManager. |
Example: CCM3 |
17 |
Total T1 PRI |
Number |
Number of T1 PRI channels configured on the gateway. |
Š 0 |
18 |
Active T1 PRI |
Number |
Number of T1 PRI channels active at time stamp. |
Š 0 and £ total T1 PRI |
19 |
Total E1 PRI |
Number |
Number of E1 PRI channels configured on the gateway. |
Š 0 |
20 |
Active E1 PRI |
Number |
Number of E1 PRI channels active at time stamp. |
Š 0 and £ total E1 PRI |
21 |
Total BRI |
Number |
Number of BRI channels configured on the MGCP gateway. |
Š 0 |
22 |
Active BRI |
Number |
Number of BRI channels active at time stamp. |
Š 0 and £ total BRIs |
23 |
Active T1 CAS |
Number |
T1 CAS utilization at time stamp for the Cisco CallManager-controlled gateway |
Š 0 and £ 100 |
24 |
Percentage active FXS |
Number |
FXS port utilization at time stamp for the Cisco CallManager-controlled gateway |
Š 0 and £ 100 |
25 |
Percentage active FXO |
Number |
FXO port utilization at time stamp for the Cisco CallManager-controlled gateway |
Š 0 and £ 100 |
26 |
Percentage active T1 PRI |
Number |
T1 PRI utilization at time stamp for the Cisco CallManager-controlled gateway |
Š 0 and £ 100 |
27 |
Percentage active E1 PRI |
Number |
E1 PRI utilization at time stamp for the Cisco CallManager-controlled gateway |
Š 0 and £ 100 |
28 |
Percentage active BRI |
Number |
BRI utilization at time stamp for the Cisco CallManager-controlled gateway |
Š 0 and £ 100 |
29 |
None |
Null indicator |
Not used |
* |
Note Fields 30 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco IOS Gateway Port Usage—Record Type 102
This record contains the port usage for Cisco IOS gateways. Cisco IOS gateways support the following ports:
•T1/E1 PRI
•T1/E1 CAS
•FXO
•FXS
•E&M
•BRI
For additional information, see Notes on Record Type 102.
Table I-6 Format of Record Type 102
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 102 |
102 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject Cisco IOS gateway |
Example: gw1@cisco.com |
5 |
Active call legs1 |
Number |
Number of call legs active at time stamp |
Š 0 |
6 |
Total T1 PRI1 |
Number |
Number of T1 PRI channels configured on Cisco IOS gateway |
Š 0 |
7 |
Active voice T1 PRI1 |
Number |
Number of T1 PRI channels active with voice calls at time stamp |
Š 0 and £ total T1 PRI |
8 |
Total T1 CAS1 |
Number |
Number of T1 CAS channels configured on Cisco IOS gateway |
Š 0 |
9 |
Active voice T1 CAS |
Number |
Number of T1 CAS channels active with voice calls at time stamp |
Š 0 and £ total T1 CAS |
10 |
Total E1 CAS1 |
Number |
Number of E1 CAS channels configured on Cisco IOS gateway |
Š 0 |
11 |
Active voice E1 CAS |
Number |
Number of E1 CAS channels active with voice calls at time stamp |
Š 0 and £ total E1 CAS |
12 |
Total FXS |
Number |
Number of FXS ports configured on Cisco IOS gateway |
Š 0 |
13 |
Active FXS |
Number |
Number of FXS ports active at time stamp |
Š 0 and £ total FXS |
14 |
Total FXO |
Number |
Number of FXO ports configured on Cisco IOS gateway |
Š 0 |
15 |
Active FXO |
Number |
Number of FXO ports active at time stamp |
Š 0 and £ total FXO |
16 |
Total BRI |
Number |
Number of BRI channels active with voice calls at time stamp |
Š 0 |
17 |
Active voice BRI1 |
Number |
Number of BRI channels active with voice calls at time stamp |
Š 0 and £ total BRI |
18 |
Total E&M |
Number |
Number of E&M ports configured on Cisco IOS gateway |
Š 0 |
19 |
Active E&M |
Number |
Number of E&M ports active at time stamp |
Š 0 and £ total E&M |
20 |
Total E1 PRI1 |
Number |
Number of E1 PRI channels configured on Cisco IOS gateway |
Š 0 |
21 |
Active voice E1 PRI1 |
Number |
Number of E1 PRI channels active with voice calls at time stamp |
Š 0 and £ total E1 PRI |
22 |
Active nonvoice E1 PRI1 |
Number |
Number of E1 PRI channels active with nonvoice calls at time stamp |
Š 0 and £ total E1 PRI |
23 |
Active nonvoice T1 PRI1 |
Number |
Number of T1 PRI channels active with nonvoice calls at time stamp |
Š 0 and £ total T1 PRI |
24 |
Active nonvoice T1 CAS |
Number |
Number of T1 CAS channels active with nonvoice calls at time stamp |
Š 0 and £ total T1 CAS |
25 |
Active nonvoice E1 CAS |
Number |
Number of E1 CAS channels active with nonvoice calls at time stamp |
Š 0 and £ total E1 PCAS |
26 |
Active nonvoice BRI 1 |
Number |
Number of BRI channels active with nonvoice calls at time stamp |
Š 0 and £ total BRI |
27 |
Percentage active Voice T1 PRI |
Number |
T1 PRI voice utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
28 |
Percentage active voice E1 PRI |
Number |
E1 PRI voice utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
29 |
Percentage active voice T1 CAS |
Number |
T1 CAS voice utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
30 |
Percentage active voice E1 CAS |
Number |
E1 CAS voice utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
31 |
Percentage active FXS |
Number |
FXS port utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
32 |
Percentage active FXO |
Number |
FXO port utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
33 |
Percentage active voice BRI |
Number |
BRI voice utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
34 |
Percentage active E&M |
Number |
E&M port utilization at time stamp for the Cisco IOS gateway |
Š 0 and £ 100 |
35 |
None |
Null indicator |
Not used |
* |
Note Fields 36 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Notes on Record Type 102
These notes explain some apparent discrepancies you might notice when you analyze the data in record type 102.
Table I-7 Record Type 102 Notes
Note
|
Affected Field Numbers
|
Circumstances
|
Total number of T1/E1 PRI channels differ by type of device. |
6 and 20 |
For supported Cisco Universal Gateways: Total number of T1/E1 PRI channels = Total B channels + 1 D channel per T1/E1 PRI port For supported devices other than Cisco Universal Gateways: Total number of T1/E1 PRI channels = Total B channels |
Total number of T1/E1 CAS channels differ by type of device. |
8 and 10 |
For supported Cisco Universal Gateways, the total T1/E1 CAS channels equal the number of CAS channels configured on the device. For devices other than Cisco Universal Gateways: Total T1 CAS channels = 24 per port Total E1 CAS channels = 31 per port |
There can be a discrepancy between active call legs and either of the following: •Active T1/E1 PRI channels •Active BRI channels |
5, 7, 17, 21, 22, 23, and 26 |
Sometimes BRI or PRI channels are active but the number of active call legs does not include them. |
There can be a discrepancy between active call legs and active T1/E1 CAS channels. |
9 and 11 |
Sometimes CAS channels are active but the number of active call legs does not include them. |
Channelized T1 DS0 Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 103
This record contains the trunk status for each channelized T1. There can be multiple records for a device with one record per T1 CAS port in the Cisco CallManager-controlled MGCP gateway.
Table I-8 Format of Record Type 103
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 103 |
103 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject gateway |
Example: sanjose-5720 |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: T1-DS1 |
6 |
Channel 1 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
7 |
Channel 2 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
8 |
Channel 3 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
9 |
Channel 4 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
10 |
Channel 5 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
11 |
Channel 6 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
12 |
Channel 7 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
13 |
Channel 8 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
14 |
Channel 9 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
15 |
Channel 10 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
16 |
Channel 11 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
17 |
Channel 12 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
18 |
Channel 13 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
19 |
Channel 14 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
20 |
Channel 15 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
21 |
Channel 16 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
22 |
Channel 17 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
23 |
Channel 18 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
24 |
Channel 19 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
25 |
Channel 20 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
26 |
Channel 21 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
27 |
Channel 22 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
28 |
Channel 23 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
29 |
Channel 24 status |
Number |
0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
30 |
None |
Null indicator |
Not used |
* |
Note Fields 31 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Record Type 104—Not Used
Note Record Type 104 is reserved for future use.
Cisco Digital PBX Adapter Port and CPU Usage—Record Type 105
This record contains Cisco Digital PBX Adapter (DPA) port usage: number of voice mail and PBX ports, their usage, and number of unassigned ports. The record also contains CPU usage; DPA supports a single CPU.
Table I-9 Format of Record Type 105
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 105 |
105 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
DPA name |
Text |
Mandatory: name of subject Cisco DPA |
Example: sanjose-5720 |
5 |
Measured 5-second CPU utilization |
Number |
Overall CPU-busy percentage in the last 5-second period; recorded at time stamp |
Š 0 and £ 100 |
6 |
Measured 1-minute CPU utilization |
Number |
Overall CPU-busy percentage in the last 1-minute period; recorded at time stamp |
Š 0 and £ 100 |
7 |
Measured 5-minute CPU utilization |
Number |
Overall CPU-busy percentage in the last 5-minute period; recorded at time stamp |
Š 0 and £ 100 |
8 |
Total voice mail ports |
Number |
Number of voice mail ports on DPA |
Š 0 |
9 |
Total active voice mail ports |
Number |
Number of voice mail ports active at time stamp |
Š 0 and £ total voice mail ports |
10 |
Total PBX ports |
Number |
Number of PBX ports on DPA |
Š 0 |
11 |
Total active PBX ports |
Number |
Number of PBX ports active at time stamp |
Š 0 and £ total PBX ports |
12 |
Unassigned ports |
Number |
Number of DPA ports not in use |
Š 0 |
13 |
Percentage active voice mail Ports |
Number |
Voice mail port utilization at time stamp for the DPA |
Š 0 and £ 100 |
14 |
Percentage active PBX ports |
Number |
PBX port utilization at time stamp for the DPA |
Š 0 and £ 100 |
15 |
None |
Null indicator |
Not used |
* |
Note Fields 16 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco IOS Gatekeeper Zone Usage—Record Type 106
This record contains gatekeeper zone information including bandwidth, error, and usage. A gatekeeper can have multiple records, with one record per zone configured in the gatekeeper.
Table I-10 Format of Record Type 106
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 106. |
106 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time. |
Example: 230000 |
4 |
Gatekeeper name |
Text |
Mandatory: name of subject gatekeeper. |
Example: gw1@cisco.com |
5 |
Zone name |
Text |
Mandatory: name of subject zone. |
Example: 127.in-addr.arpa |
6 |
Zone domain |
Text |
Mandatory: name of subject zone domain. |
Example: cisco.com |
7 |
Total bandwidth |
Number |
Total bandwidth in 100 bps configured for local zone, or one of the following: -1=bandwidth limitation not set. *=field is not applicable (when record is for a remote zone). |
Š 0 , or -1, or * |
8 |
Allocated bandwidth |
Number |
Bandwidth in 100 bps allocated to calls at time stamp for local zone, or asterisk (*) to indicate that the field is not applicable (when record is for a remote zone). |
Š 0 and £ total bandwidth, or * |
9 |
Total inter-zone bandwidth |
Number |
Total interzone bandwidth in 100 bps configured for local zone, or one of the following: -1=bandwidth limitation not set. *=field is not applicable (when record is for a remote zone). |
Š 0 and £ total bandwidth, or -1, or * |
10 |
Allocated inter-zone bandwidth |
Number |
Bandwidth in 100 bps allocated to calls for the local zone, or asterisk (*) to indicate that the field is not applicable (when record is for a remote zone). |
Š 0 and £ total interzone bandwidth, or * |
11 |
arjs |
Number |
Cumulative number of admission rejections for local zone, or asterisk (*) to indicate that the field is not applicable (when record is for a remote zone). |
Š 0 |
12 |
acfs |
Number |
Cumulative number of admission confirms for local zone, or asterisk (*) to indicate that the field is not applicable (when record is for a remote zone). |
Š 0 or * |
13 |
lrqs |
Number |
Cumulative number of location requests for remote zone, or asterisk (*) to indicate that the field is not applicable (when record is for a local zone). |
Š 0 or * |
14 |
Address lookup failures |
Number |
Cumulative number of times the gatekeeper is unable to resolve an address. |
Š 0 |
15 |
End-point timeouts |
Number |
Cumulative number of times the time to live has expired for an endpoint in this zone. |
Š 0 |
16 |
Other failures |
Number |
Cumulative number of call attempts which have failed for reasons other than endpoint timeouts or address lookup failures. |
Š 0 |
17 |
Zone type |
Text |
Mandatory: indicates whether the zone is local or remote. |
local or remote |
18 |
Bandwidth utilization |
Number |
Bandwidth utilization at time stamp for the local zone |
Š 0 and £ 100 |
19 |
Interzone bandwidth utilization |
Number |
Interzone bandwidth utilization at time stamp for the local zone |
Š 0 and £ 100 |
20 |
None |
Null indicator |
Not used. |
* |
Note Fields 21 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco IOS Device CPU Usage—Record Type 107
This record contains the CPU utilization data for Cisco IOS devices of the following device types:
•Gateways and gatekeepers
•SRST devices
•Cisco Unity Express
•Cisco CallManager Express
The record allows for a maximum of five CPUs.
Table I-11 Format of Record Type 107
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 107. |
107 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time. |
Example: 230000 |
4 |
Cisco IOS device name |
Text |
Mandatory: name of subject Cisco IOS device. |
Example: gw1@cisco.com |
5 |
CPU 1 measured 5-second utilization |
Number |
Overall CPU-busy percentage for CPU 1 in the last 5-second period; recorded at time stamp. |
Š 0 and £ 100 |
6 |
CPU 1 measured 1-minute utilization |
Number |
Overall CPU-busy percentage for CPU 1 in the last 1-minute period; recorded at time stamp. |
Š 0 and £ 100 |
7 |
CPU 1 measured 5-minute utilization |
Number |
Overall CPU-busy percentage for CPU 1 in the last 5-minute period; recorded at time stamp. |
Š 0 and £ 100 |
8 |
CPU 2 measured 5-second utilization |
Number |
Overall CPU-busy percentage for CPU 2 in the last 5-second period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 2 is not present. |
Š 0 and £ 100 |
9 |
CPU 2 measured 1-minute utilization |
Number |
Overall CPU-busy percentage for CPU 2 in the last 1-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 2 is not present. |
Š 0 and £ 100 |
10 |
CPU 2 measured 5-minute utilization |
Number |
Overall CPU-busy percentage for CPU 2 in the last 5-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 2 is not present. |
Š 0 and £ 100 |
11 |
CPU 3 measured 5-second utilization |
Number |
Overall CPU-busy percentage for CPU 3 in the last 5-second period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 3 is not present. |
Š 0 and £ 100 |
12 |
CPU 3 measured 1-minute utilization |
Number |
Overall CPU-busy percentage for CPU 3 in the last 1-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 3 is not present. |
Š 0 and £ 100 |
13 |
CPU 3 measured 5-minute utilization |
Number |
Overall CPU-busy percentage for CPU 3 in the last 5-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 3 is not present. |
Š 0 and £ 100 |
14 |
CPU 4 measured 5-second utilization |
Number |
Overall CPU-busy percentage for CPU 4 in the last 5-second period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 4 is not present. |
Š 0 and £ 100 |
15 |
CPU 4 measured 1-minute utilization |
Number |
Overall CPU-busy percentage for CPU 4 in the last 1-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 4 is not present. |
Š 0 and £ 100 |
16 |
CPU 4 measured 5-minute utilization |
Number |
Overall CPU-busy percentage for CPU 4 in the last 5-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 4 is not present. |
Š 0 and £ 100 |
17 |
CPU 5 measured 5-second utilization |
Number |
Overall CPU-busy percentage for CPU 5 in the last 5-second period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 5 is not present. |
Š 0 and £ 100 |
18 |
CPU 5 measured 1-minute utilization |
Number |
Overall CPU-busy percentage for CPU 5 in the last 1-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 5 is not present. |
Š 0 and £ 100 |
19 |
CPU 5 measured 5-minute utilization |
Number |
Overall CPU-busy percentage for CPU 5 in the last 5-minute period; recorded at time stamp. Asterisk (*) in this field indicates that CPU 5 is not present. |
Š 0 and £ 100 |
20 |
None |
Null indicator |
Not used. |
* |
Note Fields 21 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco Device Memory Usage—Record Type 108
This record contains the memory usage information for any of the following:
•Cisco CallManager Express
•Cisco IOS gateway or gatekeeper
•Cisco Unity Express
•SRST devices
•Cisco IOS gateways and gatekeepers.
The record includes memory usage in bytes for each of the following types of memory:
•Processor
•I/O
•PCI
•Fast
•Multibus
Table I-12 Format of Record Type 108
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 108 |
108 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS device name |
Text |
Mandatory: name of subject device |
Example: gw1@cisco.com |
5 |
Processor used memory |
Number |
Amount of memory in bytes |
Š 0 |
6 |
Processor free memory |
Number |
Amount of memory in bytes |
Š 0 |
7 |
Processor largest free |
Number |
Amount of memory in bytes |
Š 0 |
8 |
I/O used memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that I/O memory is not present |
Š 0 or * |
9 |
I/O free memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that I/O memory is not present |
Š 0 or * |
10 |
I/O largest free |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that I/O memory is not present |
Š 0 or * |
11 |
PCI used memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that PCI memory is not present |
Š 0or * |
12 |
PCI free memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that PCI memory is not present |
Š 0 or * |
13 |
PCI largest free |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that PCI memory is not present |
Š 0 or * |
14 |
Fast used memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that fast memory is not present |
Š 0or * |
15 |
Fast free memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that fast memory is not present |
Š 0 or * |
16 |
Fast largest free |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that fast memory is not present |
Š 0 or * |
17 |
Multibus used memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that multibus memory is not present |
Š 0 or * |
18 |
Multibus free memory |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that multibus memory is not present |
Š 0 or * |
19 |
Multibus largest free |
Number |
Amount of memory in bytes, or asterisk (*) to indicate that multibus memory is not present |
Š 0 or * |
20 |
Processor memory utilization |
Number |
Percentage processor memory utilization |
Š 0 and £ 100 |
21 |
I/O memory utilization |
Number |
Percentage I/O memory utilization |
Š 0 and £ 100 |
22 |
None |
Null indicator |
Not used |
* |
Note Fields 23 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco IOS Gateway Digital Signal Processor Usage—Record Type 109
This record contains the digital signal processor (DSP) usage information on Cisco IOS gateways. A device can have multiple records, with one record per DSP.
Note Operations Manager does not write record type 109 for the following devices:
•Cisco 1700 Series Access Routers
•Cisco MC3810 Multiservice Access Concentrators
•Cisco Series 7500 Routers
•VG200 Voice Gateway
Table I-13 Format of Record Type 109
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 109 |
109 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject Cisco IOS gateway |
Example: gw1@cisco.com |
5 |
Entity index |
Number |
An index assigned to the DSP |
Š 0 |
6 |
State |
Number |
1=active, 2=shutdown |
1 or 2 |
7 |
Total channels |
Number |
Number of channels on DSP |
Š 0 |
8 |
Active channels |
Number |
Number of channels on DSP that are active at time stamp |
Š 0 and £ total DSP channels |
9 |
In use channels |
Number |
Number of channels reserved for serving calls |
Š 0 and £ total DSP channels |
10 |
None |
Null indicator |
Not used |
* |
Note Fields 11 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
T1 PRI DS0 Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 110
This record contains the trunk status for each T1 channel configured for ISDN PRI. A device can have multiple records, with one record per T1 PRI port in the Cisco CallManager-controlled MGCP gateway.
Table I-14 Format of Record Type 110
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 110 |
110 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject gateway |
Example: sanjose-5720 |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: T1-DS1 |
6 |
Channel 1 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
7 |
Channel 2 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
8 |
Channel 3 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
9 |
Channel 4 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
10 |
Channel 5 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
11 |
Channel 6 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
12 |
Channel 7 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
13 |
Channel 8 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
14 |
Channel 9 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
15 |
Channel 10 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
16 |
Channel 11 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
17 |
Channel 12 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
18 |
Channel 13 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
19 |
Channel 14 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
20 |
Channel 15 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
21 |
Channel 16 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
22 |
Channel 17 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
23 |
Channel 18 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
24 |
Channel 19 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
25 |
Channel 20 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
26 |
Channel 21 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
27 |
Channel 22 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
28 |
Channel 23 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
29 |
Channel 24 status |
Number |
D channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
30 |
None |
Null indicator |
Not used |
* |
Note Fields 31 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
E1 PRI DS0 Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 111
This record contains the trunk status for each E1 channel configured for ISDN PRI. There can be multiple records for a device with one record per E1 port in the Cisco CallManager-controlled MGCP gateway.
Table I-15 Format of Record Type 111
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 111 |
111 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject gateway |
Example: sanjose-5720 |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: E1-PRI-D1 |
6 |
Channel 1 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
7 |
Channel 2 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
8 |
Channel 3 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
9 |
Channel 4 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
10 |
Channel 5 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
11 |
Channel 6 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
12 |
Channel 7 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
13 |
Channel 8 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
14 |
Channel 9 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
15 |
Channel 10 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
16 |
Channel 11 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
17 |
Channel 12 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
18 |
Channel 13 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
19 |
Channel 14 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
20 |
Channel 15 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
21 |
Channel 16 status |
Number |
D channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
22 |
Channel 17 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
23 |
Channel 18 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
24 |
Channel 19 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
25 |
Channel 20 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
26 |
Channel 21 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
27 |
Channel 22 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
28 |
Channel 23 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
29 |
Channel 24 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
30 |
Channel 25 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
31 |
Channel 26 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
32 |
Channel 27 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
33 |
Channel 28 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
34 |
Channel 29 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
35 |
Channel 30 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
36 |
Channel 31 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
37 |
None |
Null indicator |
Not used |
* |
38 |
None |
Null indicator |
Not used |
* |
Channelized T1 CAS DS0 Channel Status for Cisco IOS Gateways—Record Type 112
This record contains the trunk status for each channelized T1. A device can have multiple records, with one record per T1 CAS port in the Cisco IOS gateway.
Note Operations Manager writes record type 112 for supported Cisco Universal Gateways only.
Table I-16 Format of Record Type 112
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 112 |
112 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject Cisco IOS gateway |
Example: gw1@cisco.com |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: E1-CAS-D1 |
6 |
Channel 1 status |
Number |
200=idle, 300=unknown, 301=other, 302=voice, 303=unrestrictedDigital, 304=unrestrictedDigital56, 305=restrictedDigital, 306=audio31, 307=audio7, 308=video, 309=packetSwitched, 310=fax, 312=unknown, 313=analog, 314=digital, 315=v110, 316=v120 |
200, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 312, 313, 314, 315, or 316 |
7 |
Channel 2 status |
Number |
See field number 6 |
See field number 6 |
8 |
Channel 3 status |
Number |
See field number 6 |
See field number 6 |
9 |
Channel 4 status |
Number |
See field number 6 |
See field number 6 |
10 |
Channel 5 status |
Number |
See field number 6 |
See field number 6 |
11 |
Channel 6 status |
Number |
See field number 6 |
See field number 6 |
12 |
Channel 7 status |
Number |
See field number 6 |
See field number 6 |
13 |
Channel 8 status |
Number |
See field number 6 |
See field number 6 |
14 |
Channel 9 status |
Number |
See field number 6 |
See field number 6 |
15 |
Channel 10 status |
Number |
See field number 6 |
See field number 6 |
16 |
Channel 11 status |
Number |
See field number 6 |
See field number 6 |
17 |
Channel 12 status |
Number |
See field number 6 |
See field number 6 |
18 |
Channel 13 status |
Number |
See field number 6 |
See field number 6 |
19 |
Channel 14 status |
Number |
See field number 6 |
See field number 6 |
20 |
Channel 15 status |
Number |
See field number 6 |
See field number 6 |
21 |
Channel 16 status |
Number |
See field number 6 |
See field number 6 |
22 |
Channel 17 status |
Number |
See field number 6 |
See field number 6 |
23 |
Channel 18 status |
Number |
See field number 6 |
See field number 6 |
24 |
Channel 19 status |
Number |
See field number 6 |
See field number 6 |
25 |
Channel 20 status |
Number |
See field number 6 |
See field number 6 |
26 |
Channel 21 status |
Number |
See field number 6 |
See field number 6 |
27 |
Channel 22 status |
Number |
See field number 6 |
See field number 6 |
28 |
Channel 23 status |
Number |
See field number 6 |
See field number 6 |
29 |
Channel 24 status |
Number |
See field number 6 |
See field number 6 |
30 |
None |
Null indicator |
Not used |
* |
Note Fields 31 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Channelized E1 CAS DS0 Channel Status for Cisco IOS Gateways—Record Type 113
This record contains the trunk status for each channelized E1. A device can have multiple records, with one record per E1 CAS port in the Cisco IOS gateway.
Note Operations Manager writes record type 113 for supported Cisco Universal Access Gateways only.
Table I-17 Format of Record Type 113
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 113 |
113 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject Cisco IOS gateway |
Example: gw1@cisco.com |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: E1-CAS-D1 |
6 |
Channel 1 status |
Number |
200=idle, 300=unknown, 301=other, 302=voice, 303=unrestrictedDigital, 304=unrestrictedDigital56, 305=restrictedDigital, 306=audio31, 307=audio7, 308=video, 309=packetSwitched, 310=fax, 312=unknown, 313=analog, 314=digital, 315=v110, 316=v120 |
200, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 312, 313, 314, 315, or 316 |
7 |
Channel 2 status |
Number |
See field number 6 |
See field number 6 |
8 |
Channel 3 status |
Number |
See field number 6 |
See field number 6 |
9 |
Channel 4 status |
Number |
See field number 6 |
See field number 6 |
10 |
Channel 5 status |
Number |
See field number 6 |
See field number 6 |
11 |
Channel 6 status |
Number |
See field number 6 |
See field number 6 |
12 |
Channel 7 status |
Number |
See field number 6 |
See field number 6 |
13 |
Channel 8 status |
Number |
See field number 6 |
See field number 6 |
14 |
Channel 9 status |
Number |
See field number 6 |
See field number 6 |
15 |
Channel 10 status |
Number |
See field number 6 |
See field number 6 |
16 |
Channel 11 status |
Number |
See field number 6 |
See field number 6 |
17 |
Channel 12 status |
Number |
See field number 6 |
See field number 6 |
18 |
Channel 13 status |
Number |
See field number 6 |
See field number 6 |
19 |
Channel 14 status |
Number |
See field number 6 |
See field number 6 |
20 |
Channel 15 status |
Number |
See field number 6 |
See field number 6 |
21 |
Channel 16 status |
Number |
See field number 6 |
See field number 6 |
22 |
Channel 17 status |
Number |
See field number 6 |
See field number 6 |
23 |
Channel 18 status |
Number |
See field number 6 |
See field number 6 |
24 |
Channel 19 status |
Number |
See field number 6 |
See field number 6 |
25 |
Channel 20 status |
Number |
See field number 6 |
See field number 6 |
26 |
Channel 21 status |
Number |
See field number 6 |
See field number 6 |
27 |
Channel 22 status |
Number |
See field number 6 |
See field number 6 |
28 |
Channel 23 status |
Number |
See field number 6 |
See field number 6 |
29 |
Channel 24 status |
Number |
See field number 6 |
See field number 6 |
30 |
Channel 25 status |
Number |
See field number 6 |
See field number 6 |
31 |
Channel 26 status |
Number |
See field number 6 |
See field number 6 |
32 |
Channel 27 status |
Number |
See field number 6 |
See field number 6 |
33 |
Channel 28 status |
Number |
See field number 6 |
See field number 6 |
34 |
Channel 29 status |
Number |
See field number 6 |
See field number 6 |
35 |
Channel 30 status |
Number |
See field number 6 |
See field number 6 |
36 |
Channel 31 status |
Number |
See field number 6 |
See field number 6 |
37 |
None |
Null indicator |
Not used |
* |
38 |
None |
Null indicator |
Not used |
* |
T1 PRI DS0 Channel Status for Cisco IOS Gateways—Record Type 114
This record contains the trunk status for each T1 channel configured for ISDN PRI. A device can have multiple records, with one record per T1 PRI port in the Cisco IOS gateway.
Table I-18 Format of Record Type 114
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 114 |
114 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject Cisco IOS gateway |
Example: gw1@cisco.com |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: E1-PRI-D1 |
6 |
Channel 1 status |
Number |
B channel 200=idle, 300=unknown, 301=other, 302=voice, 303=unrestrictedDigital, 304=unrestrictedDigital56, 305=restrictedDigital, 306=audio31, 307=audio7, 308=video, 309=packetSwitched, 310=fax, 312=unknown, 313=analog, 314=digital, 315=v110, 316=v120 |
200, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 312, 313, 314, 315, or 316 |
7 |
Channel 2 status |
Number |
B channel See field number 6 |
See field number 6 |
8 |
Channel 3 status |
Number |
B channel See field number 6 |
See field number 6 |
9 |
Channel 4 status |
Number |
B channel See field number 6 |
See field number 6 |
10 |
Channel 5 status |
Number |
B channel See field number 6 |
See field number 6 |
11 |
Channel 6 status |
Number |
B channel See field number 6 |
See field number 6 |
12 |
Channel 7 status |
Number |
B channel See field number 6 |
See field number 6 |
13 |
Channel 8 status |
Number |
B channel See field number 6 |
See field number 6 |
14 |
Channel 9 status |
Number |
B channel See field number 6 |
See field number 6 |
15 |
Channel 10 status |
Number |
B channel See field number 6 |
See field number 6 |
16 |
Channel 11 status |
Number |
B channel See field number 6 |
See field number 6 |
17 |
Channel 12 status |
Number |
B channel See field number 6 |
See field number 6 |
18 |
Channel 13 status |
Number |
B channel See field number 6 |
See field number 6 |
19 |
Channel 14 status |
Number |
B channel See field number 6 |
See field number 6 |
20 |
Channel 15 status |
Number |
B channel See field number 6 |
See field number 6 |
21 |
Channel 16 status |
Number |
B channel See field number 6 |
See field number 6 |
22 |
Channel 17 status |
Number |
B channel See field number 6 |
See field number 6 |
23 |
Channel 18 status |
Number |
B channel See field number 6 |
See field number 6 |
24 |
Channel 19 status |
Number |
B channel See field number 6 |
See field number 6 |
25 |
Channel 20 status |
Number |
B channel See field number 6 |
See field number 6 |
26 |
Channel 21 status |
Number |
B channel See field number 6 |
See field number 6 |
27 |
Channel 22 status |
Number |
B channel See field number 6 |
See field number 6 |
28 |
Channel 23 status |
Number |
B channel See field number 6 |
See field number 6 |
29 |
Channel 24 status |
Number |
D channel Note D channel status is available for Cisco Universal Gateways only. See field number 6 |
See field number 6 |
30 |
None |
Null indicator |
Not used |
* |
Note Fields 31 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
E1 PRI DS0 Channel Status for Cisco IOS Gateways—Record Type 115
This record contains the trunk status for each E1 channel configured for ISDN PRI. A device can have multiple records, with one record per E1 PRI port in the Cisco IOS gateway.
Table I-19 Format of Record Type 115
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 115 |
115 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject Cisco IOS gateway |
Example: gw1@cisco.com |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: E1-PRI-D1 |
6 |
Channel 1 status |
Number |
B channel 200=idle, 300=unknown, 301=other, 302=voice, 303=unrestrictedDigital, 304=unrestrictedDigital56, 305=restrictedDigital, 306=audio31, 307=audio7, 308=video, 309=packetSwitched, 310=fax, 312=unknown, 313=analog, 314=digital, 315=v110, 316=v120 |
200, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 312, 313, 314, 315, or 316 |
7 |
Channel 2 status |
Number |
B channel See field number 6 |
See field number 6 |
8 |
Channel 3 status |
Number |
B channel See field number 6 |
See field number 6 |
9 |
Channel 4 status |
Number |
B channel See field number 6 |
See field number 6 |
10 |
Channel 5 status |
Number |
B channel See field number 6 |
See field number 6 |
11 |
Channel 6 status |
Number |
B channel See field number 6 |
See field number 6 |
12 |
Channel 7 status |
Number |
B channel See field number 6 |
See field number 6 |
13 |
Channel 8 status |
Number |
B channel See field number 6 |
See field number 6 |
14 |
Channel 9 status |
Number |
B channel See field number 6 |
See field number 6 |
15 |
Channel 10 status |
Number |
B channel See field number 6 |
See field number 6 |
16 |
Channel 11 status |
Number |
B channel See field number 6 |
See field number 6 |
17 |
Channel 12 status |
Number |
B channel See field number 6 |
See field number 6 |
18 |
Channel 13 status |
Number |
B channel See field number 6 |
See field number 6 |
19 |
Channel 14 status |
Number |
B channel See field number 6 |
See field number 6 |
20 |
Channel 15 status |
Number |
B channel See field number 6 |
See field number 6 |
21 |
Channel 16 status |
Number |
D channel Note D channel status is available for Cisco Universal Gateways only. See field number 6 |
See field number 6 |
22 |
Channel 17 status |
Number |
B channel See field number 6 |
See field number 6 |
23 |
Channel 18 status |
Number |
B channel See field number 6 |
See field number 6 |
24 |
Channel 19 status |
Number |
B channel See field number 6 |
See field number 6 |
25 |
Channel 20 status |
Number |
B channel See field number 6 |
See field number 6 |
26 |
Channel 21 status |
Number |
B channel See field number 6 |
See field number 6 |
27 |
Channel 22 status |
Number |
B channel See field number 6 |
See field number 6 |
28 |
Channel 23 status |
Number |
B channel See field number 6 |
See field number 6 |
29 |
Channel 24 status |
Number |
B channel See field number 6 |
See field number 6 |
30 |
None |
Null indicator |
Not used |
* |
Note Fields 31 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
BRI Channel Status for
Cisco CallManager-Controlled Gateways—Record Type 116
This record contains the channel status for each BRI configured on a Cisco CallManager-controlled gateway. A device can have multiple records, with one record per BRI port in the Cisco CallManager-controlled gateway.
Table I-20 Format of Record Type 116
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 116 |
116 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject gateway |
Example: sanjose-5720 |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: BRI-DS1 |
6 |
Channel 1 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
7 |
Channel 2 status |
Number |
B channel 0=unknown, 1=out-of-service, 2=idle, 3=busy, 4=reserved |
Š 0 and £ 4 |
8 |
Channel 3 status |
Number |
D channel 0=out-of-service, 1=in-service |
0 or 1 |
9 |
None |
Null indicator |
Not used |
* |
Note Fields 10 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
BRI Channel Status for Cisco IOS Gateways—Record Type 117
This record contains the channel status for each BRI configured on a Cisco IOS gateway. A device can have multiple records, with one record per BRI port in the Cisco IOS Gateway.
Table I-21 Format of Record Type 117
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 117 |
117 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject gateway |
Example: gw1@ cisco.com |
5 |
DS1 name |
Text |
Mandatory: name of subject DS1 |
Example: BRI-DS1 |
6 |
B channel 1 status |
Number |
200=idle, 300=unknown, 302=voice, 303=unrestrictedDigital, 304=unrestrictedDigital56, 305=restrictedDigital, 306=audio31, 307=audio7, 308=video, 309=packetSwitched |
200, 300, 302, 303, 304, 305, 306, 307, 308, 309 |
7 |
B channel 2 status |
Number |
200=idle, 300=unknown, 302=voice, 303=unrestrictedDigital, 304=unrestrictedDigital56, 305=restrictedDigital, 306=audio31, 307=audio7, 308=video, 309=packetSwitched |
200, 300, 302, 303, 304, 305, 306, 307, 308, 309 |
8 |
None |
Null indicator |
Not used |
* |
Note Fields 9 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco Unity Express Mailbox Usage—Record Type 118
This record contains Cisco Unity Express mailbox usage.
Table I-22 Format of Record Type 118
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 118 |
118 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco Unity Express name |
Text |
Mandatory: name of subject Cisco Unity Express |
ASCII characters |
5 |
None |
Null indicator |
Not used |
* |
6 |
Total memory |
Null indicator |
Not used—Reserved for total RAM (Kb) |
* |
7 |
Available memory |
Null indicator |
Not used—Reserved for a available RAM (Kb) |
* |
8 |
Memory utilization |
Null indicator |
Not used—Reserved for percentage RAM utilization |
* |
9 |
Licensed mailboxes |
Number |
Maximum number of mailboxes permitted by license |
Š 0 |
10 |
Orphaned mailboxes |
Number |
Number of mailboxes orphaned at time stamp |
Š 0 and £ licensed mailboxes |
11 |
Percentage orphaned mailboxes |
Number |
Percentage of licensed mailboxes that are orphaned at time stamp |
Š 0 and £ 100 |
12 |
Maximum sessions |
Number |
Maximum number of sessions configured on Cisco Unity Express |
Š 0 |
13 |
Used sessions |
Number |
Number of sessions in use at time stamp |
Š 0 and £ maximum sessions |
14 |
Session utilization |
Number |
Percentage of maximum sessions in use at time stamp |
Š 0 and £ 100 |
15 |
Licensed capacity |
Number |
Number of minutes of storage permitted by license |
Š 0 |
16 |
Allocated capacity |
Number |
Cumulative number of minutes of storage allocated to mailboxes |
Š 0 and £ allocated capacity |
17 |
Used capacity |
Number |
Cumulative number of minutes of storage used by mailboxes |
Š 0 and £ allocated capacity |
18 |
Capacity used for messages |
Number |
Cumulative number of minutes of storage used for storing messages |
Š 0 and £ allocated capacity |
19 |
Free capacity |
Number |
Number of minutes of storage available |
Š 0 and £ licensed capacity |
20 |
Capacity utilization |
Number |
Percentage of storage in use at time stamp |
Š 0 and £ 100 |
21 |
Current messages |
Number |
Cumulative number of messages stored in mailboxes at time stamp |
Š 0 |
22 |
Current saved messages |
Number |
Cumulative number of saved messages in mailboxes at time stamp |
Š 0 |
23 |
Total messages left since last boot |
Number |
Cumulative number of messages left in mailboxes since last reboot of Cisco Unity Express |
Š 0 |
24 |
Total messages retrieved since last boot |
Number |
Cumulative number of messages retrieved in mailboxes since last reboot of Cisco Unity Express |
Š 0 |
25 |
Total messages deleted since last boot |
Number |
Cumulative number of messages deleted from mailboxes since last reboot of Cisco Unity Express |
Š 0 |
26 |
Busy mailboxes |
Number |
Number of busy mailboxes |
Š 0 |
27 |
Mailboxes above 90% full |
Number |
Number of mailboxes that are 90% or more full |
Š 0 |
28 |
None |
Null indicator |
Not used |
* |
Note Fields 29 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Express Ephone and Key Ephone Usage—Record Type 119
This record contains Cisco Call Manager Express ephone and key ephone usage information.
Table I-23 Format of Record Type 119
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 119 |
119 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager Express name |
Text |
Mandatory: name of subject Cisco CallManager Express |
|
5 |
Ephone active call legs |
Number |
Number of ephone call legs active at time stamp |
Š 0 |
6 |
Maximum ephones |
Number |
Maximum number of ephones that can be configured on the Cisco CallManager Express |
Š 0 |
7 |
Ephones registered |
Number |
Number of ephones registered at time stamp |
Š 0 and £ maximum ephones |
8 |
Percentage ephones registered |
Number |
Percentage of ephones that are registered |
Š 0 and £ 100 |
9 |
Key ephones configured |
Number |
Number of key ephones configured |
Š 0 |
10 |
Key ephones registered |
Number |
Number of key ephones registered |
Š 0 and £ key ephones configured |
11 |
Percentage key ephones registered |
Number |
Percentage of configured key ephones that are registered |
Š 0 and £ 100 |
12 |
Ephones seen |
Number |
Maximum number of sessions configured on the CUE |
Š 0 |
13 |
None |
Null indicator |
Not used |
* |
Note Fields 14 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco Survivable Remote Site Telephony Usage—Record Type 120
This record contains Cisco Survivable Remote Site Telephony (SRST) usage information.
Table I-24 Format of Record Type 120
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 120 |
120 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
SRST name |
Text |
Mandatory: name of subject SRST device |
ASCII characters |
5 |
Minutes in SRST mode |
Number |
Cumulative number of minutes the SRST device was in SRST mode |
Š 0 |
6 |
None |
Null indicator |
Not used |
* |
Note Fields 7through 38 are not used and contain the null indicator "*". |
Cisco Unity Port Usage—Record Type 121
This record contains Cisco Unity usage information.
Table I-25 Format of Record Type 121
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 121 |
121 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco Unity name |
Text |
Mandatory: name of subject Cisco Unity |
ASCII characters |
5 |
Total ports |
Number |
Total number of ports |
Š 0 |
6 |
Active ports |
Number |
Number of ports active at time stamp |
Š 0 and £ total ports |
7 |
Port utilization |
Number |
Percentage of total ports active at time stamp |
Š 0 and £ 100 |
8 |
Total inbound ports |
Number |
Total number of inbound ports |
Š 0 |
9 |
Active inbound ports |
Number |
Number of active inbound ports at time stamp |
Š 0 and £ total inbound ports |
10 |
Inbound port utilization |
Number |
Percentage of total inbound ports active at time stamp |
Š 0 and £ 100 |
11 |
Total outbound ports |
Number |
Total outbound ports |
Š 0 |
12 |
Active outbound ports |
Number |
Number of active outbound ports at time stamp |
Š 0 and £ total outbound ports |
13 |
Outbound port utilization |
Number |
Percentage of total outbound ports active at time stamp |
Š 0 and £ 100 |
14 |
None |
Null indicator |
Not used |
* |
Note Fields 15 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Consolidated DSP Usage for Cisco IOS Devices—Record Type 122
This record contains consolidated DSP usage information for Cisco IOS devices. There is one record per Cisco 1OS device.
Table I-26 Format of Record Type 122
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 122 |
122 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco IOS gateway name |
Text |
Mandatory: name of subject device |
ASCII characters |
5 |
Total DSP channels |
Number |
Total number of DSP channels on the device |
Š 0 |
6 |
Total active DSP channels |
Number |
Number of active DSP channels on the device at time stamp |
Š 0 and £ total DSP channels |
7 |
Total DSP channels in use |
Number |
Number of DSP channels on the device that are reserved for serving calls |
Š 0 and £ total DSP channels |
8 |
DSP channel utilization |
Number |
Percentage of DSP channels active on the device at time stamp |
Š 0 and £ 100 |
9 |
None |
Null indicator |
Not used |
* |
Note Fields 10 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Usage 2—Record Type 123
This record contains Cisco CallManager resource utilization for software conference bridge, hardware conference bridge, MTP, MOH, and transcoder.
Table I-27 Format of Record Type 123
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 123 |
123 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM |
5 |
Total MOH multicast resources |
Number |
Total number of MOH multicast resources configured on the Cisco CallManager |
Š 0 |
6 |
Active MOH multicast resources |
Number |
Number of MOH multicast resources active on the Cisco CallManager at time stamp |
Š 0 and £ total MOH multicast resources |
7 |
Available MOH multicast resources |
Number |
Number of MOH multicast resources on the Cisco CallManager available at time stamp |
Š 0 and £ total MOH multicast resources |
8 |
MOH multicast resource utilization |
Number |
Percentage of total MOH multicast resources on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
9 |
Total MOH unicast resources |
Number |
Total number of MOH unicast resources configured on the Cisco CallManager |
Š 0 |
10 |
Active MOH unicast resources |
Number |
Number of MOH unicast resources active at time stamp |
Š 0 and £ total MOH unicast resources |
11 |
Available MOH unicast resources |
Number |
Number of MOH unicast resources on the Cisco CallManager available at time stamp |
Š 0 and £ total MOH unicast resources |
12 |
MOH unicast resource utilization |
Number |
Percentage of total MOH unicast resources on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
13 |
Total MTP resources |
Number |
Total number of MTP resources configured on the Cisco CallManager |
Š 0 |
14 |
Active MTP resources |
Number |
Number of MTP resources active on the Cisco CallManager at time stamp |
Š 0 and £ total MTP resources |
15 |
Available MTP resources |
Number |
Number of MTP resources available on the Cisco CallManager at time stamp |
Š 0 and £ total MTP resources |
16 |
MTP resource utilization |
Number |
Percentage of total MOH resources active on the Cisco CallManager at time stamp |
Š 0 and £ 100 |
17 |
Total transcoder resources |
Number |
Total number of transcoder resources on the Cisco CallManager |
Š 0 |
18 |
Active transcoder resources |
Number |
Number of transcoder resources active on the Cisco CallManager at time stamp |
Š 0 and £ total transcoder resources |
19 |
Available transcoder resources |
Number |
Number of transcoder resources available on the Cisco CallManager at time stamp |
Š 0 and £ total transcoder resources |
20 |
Transcoder resource utilization |
Number |
Percentage of total transcoder resources on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
21 |
Total software conference resources |
Number |
Total number of software conference resources on the Cisco CallManager |
Š 0 |
22 |
Active software conference resources |
Number |
Number of software conference resources on the Cisco CallManager active at time stamp |
Š 0 and £ total software conference resources |
23 |
Available software conference resources |
Number |
Number of software conference resources on the Cisco CallManager available at time stamp |
Š 0 and £ total software conference resources |
24 |
Software conference resource utilization |
Number |
Percentage of total software conference resources on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
25 |
Active software conferences |
Number |
Number of active software conferences on the Cisco CallManager at time stamp |
Š 0 |
26 |
Completed software conferences |
Number |
Number of completed software conferences on the Cisco CallManager |
Š 0 |
27 |
Total hardware conference resources |
Number |
Total number of hardware conference resources on the Cisco CallManager |
Š 0 |
28 |
Active hardware conference resources |
Number |
Number of hardware conference resources on the Cisco CallManager active at time stamp |
Š 0 and £ total hardware conference resources |
29 |
Available hardware conference resources |
Number |
Number of hardware conference resources on the Cisco CallManager available at time stamp |
Š 0 and £ total hardware conference resources |
30 |
Hardware conference resource utilization |
Number |
Percentage of total hardware conference resources on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
31 |
Active hardware conferences |
Number |
Number of hardware conferences on the Cisco CallManager active at time stamp |
Š 0 |
32 |
Completed hardware conferences |
Number |
Number of completed hardware conferences on the Cisco CallManager at time stamp |
Š 0 |
33 |
Registered analog access |
Number |
Number of analog access devices registered with the Cisco CallManager at time stamp |
Š 0 |
34 |
Registered MGCP gateways |
Number |
Number of MGCP gateways registered with the Cisco CallManager at time stamp |
Š 0 |
35 |
Registered hardware phones |
Number |
Number of hardware phones registered with the Cisco CallManager at time stamp |
Š 0 |
36 |
Registered other station devices |
Number |
Number of other station devices registered with the Cisco CallManager at time stamp |
Š 0 |
37 |
None |
Null indicator |
Not used |
* |
38 |
None |
Null indicator |
Reserved |
* |
FXS Port Usage for Cisco CallManager-Controlled Gateways—Record Type 124
This record contains usage statistics for each FXS port on MGCP gateway registered with Cisco CallManager.
Table I-28 Format of Record Type 124
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 124 |
124 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject MGCP gateway registered with Cisco CallManager |
ASCII characters |
5 |
FXS port name |
Text |
Mandatory: name of FXS port |
ASCII characters |
6 |
Calls completed |
Number |
Number of calls completed on this FXS port on the gateway |
Š 0 |
7 |
Outbound busy attempts |
Number |
Number of outbound busy attempts on this FXS port on the gateway |
Š 0 |
9 |
None |
Null indicator |
Not used |
* |
Note Fields 10 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
FXO Port Usage for Cisco CallManager-Controlled Gateways—Record Type 125
This record contains usage statistics for each FXO port on MGCP gateways registered with Cisco CallManager.
Table I-29 Format of Record Type 125
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 125 |
125 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject MGCP gateway registered to Cisco CallManager |
ASCII characters |
5 |
FXO port name |
Text |
Mandatory: name of FXO port |
ASCII characters |
6 |
Calls completed |
Number |
Number of calls completed on this FXO port on the gateway |
Š 0 |
7 |
Outbound busy attempts |
Number |
Number of outbound busy attempts on this FXO port on the gateway |
Š 0 |
8 |
None |
Null indicator |
Not used |
* |
Note Fields 9 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager CTI Manager Usage—Record Type 126
This record contains usage statistics for CTI Manager in Cisco CallManager.
Table I-30 Format of Record Type 126
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 126 |
126 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Total registered CTI ports |
Number |
Total number of CTI ports registered with the Cisco CallManager |
Š 0 |
6 |
CTI link active |
Number |
Number of CTI links active on the Cisco CallManager |
Š 0 |
7 |
CTI connection active |
Number |
Number of CTI connections active on the Cisco CallManager |
Š 0 |
8 |
Devices open |
Number |
Number of CTI devices open |
Š 0 |
9 |
Lines open |
Number |
Number of CTI lines open |
Š 0 |
10 |
None |
Null indicator |
Not used |
* |
Note Fields 11 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Analog Access Gateway Usage—Record Type 127
This record contains usage statistics for each analog access gateway registered with Cisco CallManager.
Table I-31 Format of Record Type 127
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 127 |
127 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Analog access device name |
Text |
Mandatory: name of analog access device registered with Cisco CallManager |
ASCII characters |
6 |
Ports active |
Number |
Number of ports active on this analog access device |
Š 0 |
7 |
None |
Null indicator |
Not used |
* |
Note Fields 8 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager H323 Gateway Usage—Record Type 128
This record contains usage statistics for each H323 gateway registered with Cisco CallManager.
Table I-32 Format of Record Type 128
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 128 |
128 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
H323 gateway name |
Text |
Mandatory: name of H323 gateway added to the Cisco CallManager |
ASCII characters |
6 |
Calls active |
Number |
Number of calls active through the H323 gateway at time stamp |
Š 0 |
7 |
Calls attempted |
Number |
Number of calls attempted through the H323 gateway |
Š 0 |
8 |
Calls completed |
Number |
Number of calls completed through the H323 gateway |
Š 0 |
9 |
Calls in progress |
Number |
Number of calls in progress through the H323 gateway at time stamp |
Š 0 |
10 |
None |
Null indicator |
Not used |
* |
Note Fields 11 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Location Usage—Record Type 129
This record contains bandwidth usage statistics for each Cisco CallManager location.
Table I-33 Format of Record Type 129
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 129 |
129 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Location name |
Text |
Mandatory: name of the location defined in Cisco CallManager |
ASCII characters |
6 |
Maximum bandwidth |
Number |
Total bandwidth (kbps) configured for the location |
Š 0 |
7 |
Available bandwidth |
Number |
Bandwidth available for the location at time stamp |
Š 0 |
8 |
Bandwidth utilization |
Number |
Percentage of maximum bandwidth available at time stamp |
Š 0 and £ 100 |
9 |
None |
Null indicator |
Not used |
* |
Note Fields 10 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Media Streaming Application Usage—Record Type 130
This record contains usage statistics for media streaming applications in Cisco CallManager.
Table I-34 Format of Record Type 130
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 130 |
130 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Total conferences |
Number |
Total number of conferences |
Š 0 |
6 |
Active conferences |
Number |
Number of conferences active on the Cisco CallManager at time stamp |
Š 0 |
7 |
Percentage conferences active |
Number |
Percentage of total conferences active on the Cisco CallManager at time stamp |
Š 0 and £ 100 |
8 |
Total conference streams |
Number |
Total number of conference streams on the Cisco CallManager |
Š 0 |
9 |
Conference streams available |
Number |
Number of conference streams available on the Cisco CallManager at time stamp |
Š 0 |
10 |
Conference streams active |
Number |
Number of conference streams active on the Cisco CallManager at time stamp |
Š 0 |
11 |
Percentage conference streams active |
Number |
Percentage of conference streams active on the Cisco CallManager at time stamp |
Š 0 and £ 100 |
12 |
Active MOH audio sources |
Number |
Number of MOH audio sources active on the Cisco CallManager at time stamp |
Š 0 |
13 |
Total MOH streams |
Number |
Total number of MOH streams configured on the Cisco CallManager |
Š 0 |
14 |
Available MOH streams |
Number |
Number of MOH streams available on the Cisco CallManager at time stamp |
Š 0 |
15 |
Active MOH streams |
Number |
Number of MOH streams active on the Cisco CallManager at time stamp |
Š 0 |
16 |
Percentage MOH streams active |
Number |
Percentage of total MOH streams on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
17 |
Total MTP connections |
Number |
Total number of MTP connections on the Cisco CallManager |
Š 0 |
18 |
Active MTP instances |
Number |
Number of MTP instances active on the Cisco CallManager at time stamp |
Š 0 |
19 |
Total MTP streams |
Number |
Total number of MTP streams on the Cisco CallManager |
Š 0 |
20 |
Available MTP streams |
Number |
Number of MTP streams available on the Cisco CallManager at time stamp |
Š 0 |
21 |
Active MTP streams |
Number |
Number of MTP streams active on the Cisco CallManager at time stamp |
Š 0 |
22 |
Percentage active MTP streamS |
Number |
Percentage of total MTP streams on the Cisco CallManager active at time stamp |
Š 0 and £ 100 |
23 |
None |
Null indicator |
Not used |
* |
Note Fields 24 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager MOH Usage—Record Type 131
This record contains usage statistics for each music on hold (MOH) device registered with Cisco CallManager.
Table I-35 Format of Record Type 131
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 131 |
131 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
MOH device name |
Text |
Mandatory: name of the MOH device registered to the Cisco CallManager |
ASCII characters |
6 |
Highest active resources |
Number |
Highest active resources on the MOH device |
Š 0 |
7 |
Total multicast resources |
Number |
Total number of multicast resources on the MOH device |
Š 0 |
8 |
Available multicast resources |
Number |
Number of multicast resources on the MOH device available at time stamp |
Š 0 |
9 |
Active multicast resource |
Number |
Number of multicast resources on the MOH device active at time stamp |
Š 0 |
10 |
Percentage active multicast resources |
Number |
Percentage of total multicast resources on the MOH device active at time stamp |
Š 0 and £ 100 |
11 |
Total unicast resources |
Number |
Total number of unicast resources on the MOH device |
Š 0 |
12 |
Available unicast resources |
Number |
Number of unicast resources available on the MOH device at time stamp |
Š 0 |
13 |
Active unicast resource |
Number |
Number of unicast resources on the MOH device active at time stamp |
Š 0 |
14 |
Percentage active unicast resources |
Number |
Percentage of total unicast resources on the MOH device active at time stamp |
Š 0 and £ 100 |
15 |
None |
Null indicator |
Not used |
* |
Note Fields 16 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager MTP Usage—Record Type 132
This record contains usage statistics for each media termination point (MTP) registered with Cisco CallManager.
Table I-36 Format of Record Type 132
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 132 |
132 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
MTP device name |
Text |
Mandatory: name of MTP device registered to the Cisco CallManager |
ASCII characters |
6 |
Total resources |
Number |
Total number of resources on the MTP device |
Š 0 |
7 |
Available resource |
Number |
Number of resources available on the MTP device at time stamp |
Š 0 |
8 |
Active resources |
Number |
Number of resources active on the MTP device at time stamp |
Š 0 |
9 |
Percentage active resources |
Number |
Percentage of total resources active on the MTP device at time stamp |
Š 0 and £ 100 |
10 |
None |
Null indicator |
Not used |
* |
Note Fields 11 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Hardware Conference Bridge Usage—Record Type 133
This record contains usage statistics for each Hardware Conference Bridge registered with Cisco CallManager.
Table I-37 Format of Record Type 133
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 133 |
133 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Hardware conference bridge name |
Text |
Mandatory: name of hardware conference bridge |
ASCII characters |
6 |
Completed conferences |
Number |
Number of conferences completed on this hardware conference bridge |
Š 0 |
7 |
Active conferences |
Number |
Number of conferences active on this hardware conference bridge at time stamp |
Š 0 |
8 |
Total resources |
Number |
Total number of resources on this hardware conference bridge |
Š 0 |
9 |
Available resource |
Number |
Number of resources available on this hardware conference bridge at time stamp |
Š 0 |
10 |
Active resources |
Number |
Number of resources active on this hardware conference bridge at time stamp |
Š 0 |
11 |
Percentage active resources |
Number |
Percentage of total resources active on this hardware conference bridge at time stamp |
Š 0 and £ 100 |
12 |
None |
Null indicator |
Not used |
* |
Note Fields 13 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Software Conference Bridge Usage—Record Type 134
This record contains usage statistics for each software conference bridge registered with Cisco CallManager.
Table I-38 Format of Record Type 134
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 134 |
134 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Software conference bridge name |
Text |
Mandatory: name of software conference bridge registered to the Cisco CallManager |
ASCII characters |
6 |
Conferences completed |
Number |
Number of completed conferences on this software conference bridge |
Š 0 |
7 |
Active conferences |
Number |
Number of conferences active on this software conference bridge at time stamp |
Š 0 |
8 |
Total resources |
Number |
Total number of resources on this software conference bridge |
Š 0 |
9 |
Available resource |
Number |
Number of resources available on this software conference bridge at time stamp |
Š 0 |
10 |
Active resources |
Number |
Number of resources active on this software conference bridge at time stamp |
Š 0 |
11 |
Percentage active resources |
Number |
Percentage of resources active on this software conference bridge at time stamp |
Š 0 and £ 100 |
12 |
None |
Null indicator |
Not used |
* |
Note Fields 13 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Cisco CallManager Transcoder—Record Type 135
This record contains usage statistics for each transcoder device registered with Cisco CallManager.
Table I-39 Format of Record Type 135
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 135 |
135 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Cisco CallManager name |
Text |
Mandatory: name of subject Cisco CallManager |
Example: CCM3 |
5 |
Transcoder device name |
Text |
Mandatory: name of transcoder device registered to this Cisco CallManager |
ASCII characters |
6 |
Total resources |
Number |
Total number of resources on the transcoder device |
Š 0 |
7 |
Available resource |
Number |
Number of resources available on the transcoder device at time stamp |
Š 0 |
8 |
Active resources |
Number |
Number of resources active on the transcoder device at time stamp |
Š 0 |
9 |
Percentage active resources |
Number |
Percentage active on the transcoder device at time stamp |
Š 0 and £ 100 |
10 |
None |
Null indicator |
Not used |
* |
Note Fields 11 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
T1 PRI Usage for Cisco CallManager-Controlled Gateways—Record Type 136
This record contains usage statistics for each T1 PRI port on MGCP gateways registered with Cisco CallManager.
Table I-40 Format of Record Type 136
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 136 |
136 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject MGCP gateway registered with Cisco CallManager |
ASCII characters |
5 |
DS1 name |
Text |
Mandatory: name of the T1 PRI port |
ASCII characters |
6 |
Completed calls |
Number |
Number of calls completed on this T1 PRI port on the gateway |
Š 0 |
7 |
Outbound busy attempts |
Number |
Number of outbound busy attempts on this T1 PRI port on the gateway |
Š 0 |
8 |
None |
Null indicator |
Not used |
* |
Note Fields 9 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
E1 PRI Usage for Cisco CallManager-Controlled Gateways—Record Type 137
This record contains usage statistics for each E1 PRI port on MGCP gateways registered with Cisco CallManager.
Table I-41 Format of Record Type 137
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 137 |
137 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject MGCP gateway registered with Cisco CallManager |
ASCII characters |
5 |
DS1 name |
Text |
Mandatory: name of E1 PRI port |
ASCII characters |
6 |
Calls completed |
Number |
Number of calls completed on this E1 PRI port on the gateway |
Š 0 |
7 |
Outbound busy attempts |
Number |
Number of outbound busy attempts on this E1 PRI port on the gateway |
Š 0 |
8 |
None |
Null indicator |
Not used |
* |
Note Fields 9 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
T1 CAS Usage for Cisco CallManager-Controlled Gateways—Record Type 138
This record contains usage statistics for each T1 CAS port on MGCP gateways registered with Cisco CallManager
Table I-42 Format of Record Type 138
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Mandatory: record type 138 |
138 |
2 |
Date |
yyyymmdd |
Mandatory: calendar date |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Mandatory: wall clock time |
Example: 230000 |
4 |
Gateway name |
Text |
Mandatory: name of subject gateway |
ASCII characters |
5 |
DS1 name |
Text |
Mandatory: name of the T1 CAS port |
ASCII characters |
6 |
Calls completed |
Number |
Number of calls completed on this T1 CAS port on the gateway |
Š 0 |
7 |
Outbound busy attempts |
Number |
Number of outbound busy attempts on this T1 CAS port on the gateway |
Š 0 |
8 |
None |
Null indicator |
Not used |
* |
Note Fields 9 through 37 are not used and contain the null indicator "*". |
38 |
None |
Null indicator |
Reserved |
* |
Node-to-Node Test Record Formats
For more information, see Data Files—Maintenance and Usage.
The following are the formats for each node-to-node test record type:
•Echo—Record Type 200
•Ping Path Echo—Record Type 201
•Record Type 202—Not Used
•Ping Path Echo—Record Type 204
•Jitter MOS, ICPIF, and Processed Data—Record Type 205
Echo—Record Type 200
This record format captures end-to-end statistics for the following types of tests:
•ICMP Echo
•UDP Echo
•VoIP Post Dial Delay
•Gatekeeper Registration Delay
Table I-43 Format of Record Type 200
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Record type 200. |
200 |
2 |
Date |
yyyymmdd |
Calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Wall clock time. |
Example: 230000 |
4 |
Completion time |
Number |
Round-trip time (RTT), in milliseconds. |
Between 0 and 4294967295 |
5 |
Completion status |
Number |
The allowed numbers are: •1—OK •2—disconnected •3—overThreshold •4—timeout •5—busy •6—notConnected •7—dropped •8—sequenceError •9—verifyError •10—applicationSpecific •11—dnsServerTimeout •12—tcpConnectTimeout •13—httpTransactionTimeout •14—dnsQueryError •15—httpError •16—error |
Between 1 and 16 |
6 |
Application-specific completion status |
Number |
(Optional) An application-specific status that is valid only when completion status is set to applicationSpecific (10). |
Between 1001 and 2147483647 |
7 |
Status description |
Number |
(Optional) The description for the completion status when completion status is set to applicationSpecific (10). Default value is blank. |
ASCII characters |
8 |
None |
Null indicator |
Not used |
* |
Note Fields 9 through 37 are not used and contain the null indicator "*". |
38 |
Test name |
Text |
Name of the node-to-node test |
Sjc-VGtest |
Ping Path Echo—Record Type 201
This record format captures hop-by-hop statistics for Ping Path Echo tests. The tests record information from source to destination.
Table I-44 Format of Record Type 201
Field
Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Record type 201. |
201 |
2 |
Date |
yyyymmdd |
Calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Wall clock time. |
Example: 230000 |
4 |
Completion time |
Number |
Round-trip time (RTT), in milliseconds. |
Between 0 and 4294967295 |
5 |
Hop ID |
Number |
Unique ID chosen by the study and given to a hop on this path. |
Maximum value is 30 |
6 |
Hop address |
String |
IP Address of the hop. |
ASCII characters |
7 |
Completion status |
Number |
The allowed numbers are: •1—OK •2—disconnected •3—overThreshold •4—timeout •5—busy •6—notConnected •7—dropped •8—sequenceError •9—verifyError •10—applicationSpecific •11—dnsServerTimeout •12—tcpConnectTimeout •13—httpTransactionTimeout •14—dnsQueryError •15—httpError •16—error |
Between 1 and 16 |
8 |
Application-specific completion status |
Number |
(Optional) Application-specific status that is valid only when completion status is set to applicationSpecific (10). |
Between 1001 and 2147483647 |
9 |
Status description |
Text |
(Optional) Description for the completion status when completion status is set to applicationSpecific (10). Default value is blank. |
ASCII characters |
10 |
None |
Null indicator |
Not used |
* |
Note Fields 11 through 37 are not used and contain the null indicator "*". |
38 |
Test name |
Text |
Name of the node-to-node test |
Sjc-VGtest |
Record Type 202—Not Used
Record type 202 is not in use and is reserved.
Ping Path Echo—Record Type 204
This record format captures end-to-end statistics for Ping Path Echo tests. The tests are from the source to the destination.
Table I-45 Format of Record Type 204
Field Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
nnn |
Record type 204. |
204 |
2 |
Date |
yyyymmdd |
Calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Wall clock time. |
Example: 230000 |
4 |
Completion time |
Number |
The round-trip time (RTT) in milliseconds. |
Between 0 and 4294967295 |
5 |
Hop ID |
Number |
Unique ID given to a hop on this path chosen by the study. For this record, the hop ID is always 1. |
1 |
6 |
Hop address |
String |
Mandatory: IP address of the destination. |
ASCII characters |
7 |
Completion status |
Number |
The allowed numbers are: •1—OK •2—disconnected •3—overThreshold •4—timeout •5—busy •6—notConnected •7—dropped •8—sequenceError •9—verifyError •10—applicationSpecific •11—dnsServerTimeout •12—tcpConnectTimeout •13—httpTransactionTimeout •14—dnsQueryError •15—httpError •16—error |
Between 1 and 16 |
8 |
Application-specific completion status |
Number |
(Optional) The application-specific status that is valid only when Completion Status is set to applicationSpecific (10). |
Between 1001 and 2147483647 |
9 |
Status description |
Text |
(Optional) This is the description for the completion status when Completion Status is set to applicationSpecific (10). Default value is blank. |
ASCII characters |
10 |
None |
Null indicator |
Not used. |
* |
Note Fields 10 through 37 are not used and contain the null indicator "*". |
38 |
Test name |
Text |
Name of the node-to-node test |
Sjc-VGtest |
Jitter MOS, ICPIF, and Processed Data—Record Type 205
This record format stores MOS and ICPIF values and processed jitter statistics values.
Table I-46 Format of Record Type 205
Field Number
|
Field ID
|
Content
|
Description
|
Value
|
1 |
Record ID |
205 |
Mandatory: record type 205 |
205 |
2 |
Date |
yyyymmdd |
Calendar date. |
Example: 20051201 |
3 |
Time stamp |
hhmmss |
Wall clock time. |
Example: 230000 |
4 |
ICPIF |
Number |
Mandatory: Icpif Value |
Example |
5 |
Node-to-node quality |
Number |
Mandatory: MOS value |
Example: 3.6 |
6 |
Source to destination packet loss |
Number |
Mandatory: percentage |
Š 0 and £ 100 |
7 |
Destination to source packet loss |
Number |
Mandatory: percentage |
Š 0 and £ 100 |
8 |
Source to destination jitter |
Number |
Mandatory: percentage |
Š 0 and £ 100 |
9 |
Destination to source jitter |
Number |
Mandatory: percentage |
Š 0 and £ 100 |
10 |
Average latency |
Number |
Mandatory: milliseconds |
Š 0 and £ 100 |
11 |
None |
Null indicator |
Not used |
* |
Note Fields 12 through 37 are not used and contain the null indicator "*". |
38 |
Test name |
Text |
Name of the node-to-node test |
Sjc-VGtest |