How to Identify Object Identifiers in Cisco Unity Diagnostics [Cisco Unity]

Document ID: 27013

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Identifying the OID
      Step-by-Step Instructions
      An Example of Identifying OID
Related Information

Introduction

This document describes how to identify the meaning of an Object Identifier (OID) value in Cisco Unity Diagnostics traces. This is useful when you are looking through the traces and want to find out what you are looking at.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco Unity 3.1.4 and also applies to Unity 4.0.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Identifying the OID

The steps below guide you through a simple overview of how to identify the OID and its meaning.

Step-by-Step Instructions

Complete these steps:

Copy the OID from the trace. An example is shown here:

AVP_OBJECT_ID,03:{5A42B9DD-B2FD-449D-A0F5-7B7C3AC33C92}

Open the DohPropTest window from the Commserver\techtools directory.
You can open up this tool without entering the password; this allows read-only access. An error comes up, but you can click Ignore.
Click FindByOid and enter the OID string, in this case 03:{5A42B9DD-B2FD-449D-A0F5-7B7C3AC33C92}.

This shows you the OID referred to in the trace file. In this case, it is a mailuser ID.

Note: These values have only a local meaning and can only be identified when entered on the local server.

An Example of Identifying OID

As an example, phone 302 rings to Cisco Unity and transfers out to a subscriber. The external user hears the opening greeting. This example shows a call coming in to Cisco Unity:

12:22:50:079,AvMiu_MC,641,-1,-1,MiuGeneral,17,2,CAvMiuCall:
:get_CallerID,SysReAllocString,BSTR,8,0x00000E70
12:22:50:078,AvMiu_MC,645,-1,-1,MiuIntegration,10,Line 2,
#00#302##,12:22:50,1,Call Info,Line Call Info: 
Origin:Internal Reason:Direct Calling 
Number:302,0x00001014
12:22:50:079,AvMiu_MC,556,-1,-1,MiuIntegration,11,[Port 2] 
CAvDigitCollector::EventFired()exited | Queue <>,
0x00001014

This example shows that this is a direct call (check this against the settings in the avanalog.avd file):

Data1= #00#I(3-10)## DIRECT
Data2= 00#I(3-10)## DIRECT
Data3= 0#I(3-10)## DIRECT


12:22:50:109,AvConvPHTransfer_MC,101,3696,2,ConvPH Transfer,
1,RunInit,PHTransfer
12:22:50:110,AvConvPHTransfer_MC,115,3696,2,ConvPH Transfer,
14,SetPropBool,bUseDialingDomainXfer,0x80040300,1469,
e:\views\cs_ue3.1.3.43\un_Conv2\AvConvPhoneHandler\
AvConvPHTransferSvr\AvConvPHTransfer.cpp

The opening greeting is being played, as shown in this example:

12:22:50:110,AvConvPHTransfer_MC,119,3696,2,ConvPH Transfer,24,
AVP_OBJECT_ID,03:{5A42B9DD-B2FD-449D-A0F5-7B7C3AC33C92},
1547,e:\views\cs_ue3.1.3.43\un_Conv2\AvConvPhoneHandler\
AvConvPHTransferSvr\AvConvPHTransfer.cpp

To check what the OID means, copy the string (in this example, 03:{5A42B9DD-B2FD-449D-A0F5-7B7C3AC33C92}) and look it up in the DohPropTest. That tells you the opening greeting is being streamed.