IP Line Operational Measurement report scheduling and generation

Operational Measurement (OM) reports provide important statistical and traffic information and feedback to the system administrator to better engineer the system. The information stored in the OM file applies only to the calls routed over the IP network by way of IP Line. OM reports give a quantitative view of system performance, such as jitter.

A single Voice Gateway Media Card Operational Measurements file can be viewed directly from Element Manager. This OM report is a view of the LTPS and Voice Gateway channel activity on that specific card. Use this procedure to view the individual card information for each Voice Gateway Media Card in the node.

The Voice Gateway Media Card OM file contains the following information:

 • the number of incoming and outgoing calls

 • the number of call attempts

 • the number of calls completed

 • the total holding time for voice calls

To view a single Voice Gateway Media Card OM file directly from Element Manager, follow the steps in Retrieving the current OM file from the Voice Gateway Media Card using Element Manager.

Step Action

 1 In the Element Manager navigator, click IP Network > Maintenance and Reports.The Node Maintenance and Reports window opens.

 2 Expand the node containing the Voice Gateway Media Card by clicking the plus sign (+) to the left of the Node ID.See Node Maintenance and Reports window.

 3 Click the OM RPT button associated with the Voice Gateway Media Card.The View OM File window opens. See View OM File window.

The eight most recent OM Report files are displayed in chronological order for that Voice Gateway Media Card.

 4 To view a OM file, click the radio button for the file to be viewed and then click View OM File.The OM report data appears at the bottom of the window.

Collection period

The file contains collection period information for each hour of the day that the card was running.

The collection periods start with the hour from midnight to 1:00 am. As each hour passes, a collection period is added to the OM file; therefore, there is a maximum of 24 collection periods each day.

Output

The OM report output tracks the statistics for each IP Phone type.

Data is first output for the IP Phones followed by the data for the gateway channels.

Output example

An example of a single hour OM report is as follows:

collection_time : 11/7/2006 2:00
2004Reg_Att: 0
2004Reg_Fail: 0
2004Unreg_Att: 0
2004Aud_Setup: 0
2004Jitter_Avg: 0.0
2004Jitter_Max: 0
2004Latency_Avg: 0.0
2004Latency_Max: 0
2004Pkt_Lost: 0.00
2004Listen_RFactor: 0.0
2004Voice_Time: 0 mins 0 secs
2002Reg_Att: 0
2002Reg_Fail: 0
2002Unreg_Att: 0
2002Aud_Setup: 0
2002Jitter_Avg: 0.0
2002Jitter_Max: 0
2002Latency_Avg: 0.0
2002Latency_Max: 0
2002Pkt_Lost: 0.00
2002Listen_RFactor: 0.0
2002Voice_Time: 0 mins 0 secs
2001Reg_Att: 0
2001Reg_Fail: 0
2001Unreg_Att: 0
2001Aud_Setup: 0
2001Jitter_Avg: 0.0
2001Jitter_Max: 0
2001Latency_Avg: 0.0
2001Latency_Max: 0
2001Pkt_Lost: 0.00
2001Listen_RFactor: 0.0
2001Voice_Time: 0 mins 0 secs
1150Reg_Att: 0
1150Unreg_Att: 0
1150Aud_Setup: 0
1150Jitter_Avg: 0.0
1150Jitter_Max: 0
1150Latency_Avg: 0.0
1150Latency_Max: 0
1150Pkt_Lost: 0.00
1150Listen_RFactor: 0.0
1150Voice_Time: 0 mins 0 secs
1130Reg_Att: 0
1130Reg_Fail: 0
1130Unreg_Att: 0
1130Aud_Setup: 0
1130Jitter_Avg: 0.0
1130Jitter_Max: 0
1130Latency_Avg: 0.0
1130Latency_Max: 0
1130Pkt_Lost: 0.00
1130Listen_RFactor: 0.0
1130Voice_Time: 0 mins 0 secs
2004P2Reg_Att: 0
2004P2Reg_Fail: 0
2004P2Unreg_Att: 0
2004P2Aud_Setup: 0
2004P2Jitter_Avg: 0.0
2004P2Jitter_Max: 0
2004P2Latency_Avg: 0.0
2004P2Latency_Max: 0
2004P2Pkt_Lost: 0.00
2004P2Listen_RFactor: 0.0
2004P2Voice_Time: 0 mins 0 secs
2002P2Reg_Att: 0
2002P2Reg_Fail: 0
2002P2Unreg_Att: 0
2002P2Aud_Setup: 0
2002P2Jitter_Avg: 0.0
2002P2Jitter_Max: 0
2002P2Latency_Avg: 0.0
2002P2Latency_Max: 0
2002P2Pkt_Lost: 0.00
2002P2Listen_RFactor: 0.0
2002P2Voice_Time: 0 mins 0 secs
2033Reg_Att: 0
2033Reg_Fail: 0
2033Unreg_Att: 0
2033Aud_Setup: 0
2033Jitter_Avg: 0.0
2033Jitter_Max: 0
2033Latency_Avg: 0.0
2033Latency_Max: 0
2033Pkt_Lost: 0.00
2033Listen_RFactor: 0.0
2033Voice_Time: 0 mins 0 secs
2050Reg_Att: 0
2050Reg_Fail: 0
2050Unreg_Att: 0
2050Aud_Setup: 0
2050Jitter_Avg: 0.0
2050Jitter_Max: 0
2050Latency_Avg: 0.0
2050Latency_Max: 0
2050Pkt_Lost: 0.00
2050Voice_Time: 0 mins 0 secs
2210Reg_Att: 0
2210Reg_Fail: 0
2210Unreg_Att: 0
2210Aud_Setup: 0
2210Jitter_Avg: 0.0
2210Jitter_Max: 0
2210Latency_Avg: 0.0
2210Latency_Max: 0
2210Pkt_Lost: 0.00
2210Listen_RFactor: 0.0
2210Voice_Time: 0 mins 0 secs
1120Reg_Att: 0
1120Reg_Fail: 0
1120Unreg_Att: 0
1120Aud_Setup: 0
1120Jitter_Avg: 0.0
1120Jitter_Max: 0
1120Latency_Avg: 0.0
1120Latency_Max: 0
1120Pkt_Lost: 0.00
1120Listen_RFactor: 0.0
1120Voice_Time: 0 mins 0 secs
1110Reg_Att: 0
1110Reg_Fail: 0
1110Unreg_Att: 0
1110Aud_Setup: 0
1110Jitter_Avg: 0.0
1110Jitter_Max: 0
1110Latency_Avg: 0.0
1110Latency_Max: 0
1110Pkt_Lost: 0.00
1110Listen_RFactor: 0.0
1110Voice_Time: 0 mins 0 secs
2050MCReg_Att: 0
2050MCReg_Fail: 0
2050MCUnreg_Att: 0
2050MCAud_Setup: 0
2050MCJitter_Avg: 0.0
2050MCJitter_Max: 0
2050MCLatency_Avg: 0.0
2050MCLatency_Max: 0
2050MCPkt_Lost: 0.00
2050MCVoice_Time: 0 mins 0 secs
2211Reg_Att: 0
2211Reg_Fail: 0
2210Unreg_Att: 0
2211Aud_Setup: 0
2211Jitter_Avg: 0.0
2211Jitter_Max: 0
2211Latency_Avg: 0.0
2211Latency_Max: 0
2211Pkt_Lost: 0.00
2211Listen_RFactor: 0.0
2211Voice_Time: 0 mins 0 secs
1160Reg_Att: 0
1160Reg_Fail: 0
1160Unreg_Att: 0
1160Aud_Setup: 0
1160Jitter_Avg: 0.0
1160Jitter_Max: 0
1160Latency_Avg: 0.0
1160Latency_Max: 0
1160Pkt_Lost: 0.00
1160Listen_RFactor: 0.0
1160Voice_Time: 0 mins 0 secs
2212Reg_Att: 0
2212Reg_Fail: 0
2212Unreg_Att: 0
2212Aud_Setup: 0
2212Jitter_Avg: 0.0
2212Jitter_Max: 0
2212Latency_Avg: 0.0
2212Latency_Max: 0
2212Pkt_Lost: 0.00
2212Listen_RFactor: 0.0
2212Voice_Time: 0 mins 0 secs
2007Reg_Att: 0
2007Reg_Fail: 0
2007Unreg_Att: 0
2007Aud_Setup: 0
2007Jitter_Avg: 0.0
2007Jitter_Max: 0
2007Latency_Avg: 0.0
2007Latency_Max: 0
2007Pkt_Lost: 0.00
2007Listen_RFactor: 0.0
2007Voice_Time: 0 mins 0 secs
1140Reg_Att: 0
1140Reg_Fail: 0
1140Unreg_Att: 0
1140Aud_Setup: 0
1140Jitter_Avg: 0.0
1140Jitter_Max: 0
1140Latency_Avg: 0.0
1140Latency_Max: 0
1140Pkt_Lost: 0.00
1140Listen_RFactor: 0.0
1140Voice_Time: 0 mins 0 secs
1175Reg_Att: 0
1175Reg_Fail: 0
1175Unreg_Att: 0
1175Aud_Setup: 0
1175Jitter_Avg: 0.0
1175Jitter_Max: 0
1175Latency_Avg: 0.0
1175Latency_Max: 0
1175Pkt_Lost: 0.00
1175Listen_RFactor: 0.0
1175Voice_Time: 0 mins 0 secs
ChanAud_Setup: 0
ChanJitter_Avg: 0.0
ChanJitter_Max: 0
ChanPkt_Lost: 0.00
ChanVoice_Time: 0 mins 0 secs
H323VtrkInVoCallAttempt: 0
H323VtrkInVoCallComp: 0
H323VtrkOutVoCallAttempt: 0
H323VtrkOutVoCallComp: 0
H323VtrkTotalVoiceTime: 0 mins 0 secs
H323VtrkInFaxCallAttempt: 0
H323VtrkInFaxCallComp: 0
H323VtrkOutFaxCallAttempt: 0
H323VtrkOutFaxCallComp: 0
H323VtrkFallBack: 0
H323VtrkQoSFallBack: 0
H323VtrkATPMFallBack: 0
H323VtrkRelCompFallBack: 0
SIPVtrkInVoCallAttempt: 0
SIPVtrkInVoCallComp: 0
SIPVtrkOutVoCallAttempt: 0
SIPVtrkOutVoCallComp: 0
SIPVtrkTotalVoiceTime: 0 mins 0 secs
SIPVtrkInFaxCallAttempt: 0
SIPVtrkInFaxCallComp: 0
SIPVtrkOutFaxCallAttempt: 0
SIPVtrkOutFaxCallComp: 0
SIPVtrkFallBack: 0
SIPVtrkQoSFallBack: 0
SIPVtrkATPMFallBack: 0
SIPVtrkRelCompFallBack: 0
SIPVtrkTLSAuthenticationFailure: 0
SIPVtrkTLSIncomingAttempt: 0
SIPVtrkTLSIncomingComp: 0
SIPVtrkTLSIncomingFailure: 0
SIPVtrkTLSOutgoingAttempt: 0
SIPVtrkTLSOutgoingComp: 0
SIPVtrkTLSOutgoingFailure: 0
OutTotalH323OvlCallCount: 0
OutSuccessH323OvlCallCount:0
OutOvl2EnblocCallCount: 0
InTotalH323OvlCallCount:0
InSuccessH323OvlCallCount: 0
TotalARQGenerated:0
TotalARJRcvd: 0
TotalACFRcvd:0
H323NrsGatekeeperReq: 0
H323NrsGatekeeperConf: 0
H323NrsGatekeeperRej: 0
H323NrsRegistrationReq: 144
H323NrsRegistrationConf: 144
H323NrsRegistrationRej: 0
H323NrsUnregistrationReqRecd: 0
H323NrsUnregistrationConfSent: 0
H323NrsUnregistrationRejSent: 0
H323NrsAdmissionReq: 0
H323NrsAdmissionConf: 0
H323NrsAdmissionRej: 0
H323NrsLocationReqRecd: 0
H323NrsLocationConfSent: 0
H323NrsLocationRejSent: 0
H323NrsBandwidthReqRecd: 0
H323NrsBandwidthConfSent: 0
H323NrsBandwidthRejSent: 0
H323NrsDisengageReq: 0
H323NrsDisengageConf: 0
H323NrsDisengageRej: 0
SIPNrsRoutingAttempts: 0
SIPNrsRoutingSuccesses: 0
SIPNrsRoutingFailures: 0
SIPNrsRegistrationAttempts: 138
SIPNrsRegistrationSuccesses: 138
SIPNrsRegistrationFailures: 0
SIPCTITotalSoftClientLoginAttempts: 0
SIPCTITotalSoftClientLoginSuccesses: 0
SIPCTITotalAnswerCallRequests: 0
SIPCTITotalAnswerCallSuccesses: 0
SIPCTITotalClearConnectionRequests: 0
SIPCTITotalClearConnectionSuccesses: 0
SIPCTITotalConsultationCallRequests: 0
SIPCTITotalConsultationCallSuccesses: 0
SIPCTITotalDeflectCallRequests: 0
SIPCTITotalDeflectCallSuccesses: 0
SIPCTITotalHoldCallRequests: 0
SIPCTITotalHoldCallSuccesses: 0
SIPCTITotalMakeCallRequests: 0
SIPCTITotalMakeCallSuccesses: 0
SIPCTITotalRetrieveCallRequests: 0
SIPCTITotalRetrieveCallSuccesses: 0
SIPCTITotalSingleStepTransferRequests: 0
SIPCTITotalSingleStepTransferSuccesses: 0
SIPCTITotalTransferCallRequests: 0
SIPCTITotalTransferCallSuccesses: 0
SIPCTITotalMonitorStartRequests: 0
SIPCTITotalMonitorStartSuccesses: 0
SIPCTITotalMonitorStopRequests: 0
SIPCTITotalMonitorStopSuccesses: 0
SIPCTITotalConferenceCallRequests: 0
SIPCTITotalConferenceCallSuccesses: 0
SIPCTITotalSetForwardingRequests: 0
SIPCTITotalSetForwardingSuccesses: 0
SIPCTITotalGetForwardingRequests: 0
SIPCTITotalGetForwardingSuccesses: 0
SIPCTITotalSessionTerminated: 0

Each collection period provides the following information:

 • The date and time for the collection period hour.

 • LTPS information for IP Phones that are registered to the LTPS on the Voice Gateway Media Card during that hour. During normal operation, the LTPS values for the Voice Gateway Media Card can be zeros as the IP Phones normally register to the LTPS on the Signaling Server.

 • Voice Gateway channel information accumulated during the hour. The Voice Gateway data is prefixed by Chan.

 • Notes indicating whether the machine has been rebooted during the hour.

 • Virtual Trunk statistics display only for a Signaling Server that has been running the VTRK H.323 Signaling Server in the last hour.

The OM file relates to the omreport.xxx file on the Voice Gateway Media Card, where xxx indicates the numbers of days since December 31.

In general, no relationship exists between the IP Phones registered on a Voice Gateway Media Card and the Voice Gateway channels on the card (if two or more cards are used) in the node. If only one Voice Gateway Media Card is used (with multiple IP Phones), a partial correlation might exist between the IP Phones and the card information. However, even with only one Voice Gateway Media Card, there still is not a 100% correlation, as an IP Phone can still call another IP Phone without involving the Voice Gateway channels.

Element Manager supports the ability to view OM files only. TM can optionally be used to support other Operational Measurements tasks such as scheduling reports, generating reports, opening reports, and viewing reports.

See Operational Measurement report scheduling and generation for more information.