[cisco-voip] Monitor Voicemail Port Utilization

[Lelio Fulgenzi]

Have you looked at the reports available? Both on Connection and CUCM?  
There are also some tools on ciscounitytools.com

…
Don't look at me, my iPod maid that spilling mistake.

On 2010-08-10, at 9:51 PM, Mike King <me at mpking.com> wrote:

> Isn't always the way, I spent hours researching my question, ask it.
> Then find the answer about 20 minutes later.
>
> Looks like the OID i've been searching for is:
>
> Object ID:  1.3.6.1.4.1.9.9.385.1.2.3
> Instance:  0
> Label:   
> iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoUnityMIB.ciscoUnityMIBObjects.ciscoUnityGlobalInfo.ciscoUnityPortsActive
 

> Type:  Unsigned 32bit Integer
> Access:  Read Only
> Description:
> The total number of ports that are currently active with calls.
>
> Thanks for play.
>
> Anybody got any other OID's that I should monitor?  What do you
> monitor on your Unity (or even your CUCM server)
>
> Mike
> On Tue, Aug 10, 2010 at 9:34 PM, Mike King <me at mpking.com> wrote:
>> I'm trying to figure out what my options are for monitoring Voicemail
>> Port Utilization on our Cisco Unity Connection 7.1 server.
>>
>> I'm looking to setup some long term reports.
>>
>> RTMT looks great, but It doesn't seem to be historical, just point  
>> in time.
>>
>> I've been looking for a SNMP OID i can monitor, but it doesn't look
>> like one exists...   The best I can find is:
>>
>> Object ID:  1.3.6.1.4.1.9.9.385.1.1.2.1.11
>> Instance:  0
>> Label:   
>> iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoUnityMIB.ciscoUnityMIBObjects.ciscoUnityGeneralInfo.ciscoUnityPortTable.ciscoUnityPortEntry.ciscoUnityPortActivity
 

>> Type:  Octet String
>> Access:  Read Only
>> Description:
>> The port activity of the voice mail port. This value is available to
>> monitor port activity over time. The specific value of this object is
>> not as useful as monitoring for the changing of this value. During
>> normal operation this value should change several times during a  
>> call.
>> You can use this value to watch for abnormal operation that might
>> indicate a problem with this voice mail port. For example, if you
>> monitor this value and do not detect a change in value for a long  
>> time
>> (like 60 minutes) it could be an indication of a problem with that
>> voice mail port. There are other explanations as well so more
>> investigation on the server should be conducted before taking any
>> action with the voice mail port.
>>
>>
>> So any suggestions?  I'm really concerned that I'm bouncing off my  
>> port count.
>>
>> Mike
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip