cancel
Showing results for 
Search instead for 
Did you mean: 

Phone status show "Status Never Provided"

Devan Arumugam
05 Base Camper

Phone status show "Status Never Provided"

Hello,

 

After adding the CUCM cluster, the phone status shows " Status Never Provided"

 

I verified the SNMP string. Did an SNMP Walk and I get replies. 

 

Any other place to look what exactly is going on? WVLog doesn't help either. 

 

Appreciate any help

 

Thanks.  

 

 

4 REPLIES 4
LindaYu
Sage

Re: Phone status show "Status Never Provided"

Hi Devan Arumugam

 

Thanks for the posts.

 

In general, to check the phone status, Prognosis needs to perform an SNMP walk against the Call Manager the phones are registered to of following MIBs.  

 

cmaPhoneTable:  .1.3.6.1.4.1.9.9.156.1.2.1

- To get Phone Name: .1.3.6.1.4.1.9.9.156.1.2.1.1.20

- Status: .1.3.6.1.4.1.9.9.156.1.2.1.1.7

 

hrSystemDate: .1.3.6.1.2.1.25.1.2

 

Please verify if you received SNMPwalk response for these MIBs.

 

HTH

Devan Arumugam
05 Base Camper

Re: Phone status show "Status Never Provided"

Linda - Could you clarify the MIB's because after running snmpwalk I am seeing output like this and not seeing anything as you mentioned. 

 

iso.3.6.1.2.1.54.1.2.3.1.9.0.0.1 = Timeticks: (195208) 0:32:32.08

 

If I consider 'iso.' as 1 and look for the number in your 'cmaPhoneTable:  .1.3.6.1.4.1.9.9.156.1.2.1' it doesn't match any.

 

Is there a command that I can try to check this MIB directly.

 

I appreciate your help.

LindaYu
Sage

Re: Phone status show "Status Never Provided"

Hi Devan Arumugam,

 

Thank you for the posts.  On Prognosis server, command line prompt, you can use snmpwalk tool under \Prognosis\Server\x64 directory to query CM server for the listed OIDs and review the output.


Syntax should be:

> snmpwalk -v2c -c <community_string> <CM_ip> <OID>

 

example:

example.jpg

 

HTH

 

Devan Arumugam
05 Base Camper

Re: Phone status show "Status Never Provided"

Linda,

 

I opened a case and found out that the memory allocated for each cluster in prognosis configuration was not sufficient. Increasing them fixed few issues related to this.

 

thanks.