Replies: 3 comments 2 replies
-
|
Hi @jelenatko do you know at least S/N & model for this phone to check if we can find them in the walk ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jelenatko brochure is not useful. Anyway I inspected a little more your snmp walk. And I saw a lot of "Wrong Type" issue. This happens on sysObjectID, on IPs, and few gauge. The one on sysObjectID is still a big problem. Also sysName (oid .1.3.6.1.2.1.1.5.0) is just not the system name, it contains a lot of information separated by newline chars... This is a non-sens. I found also network port mac addresses are wrongly encoded. Maybe you didn't use the required command to generate the snmpwalk, but I better think snmp is wrongly supported on this device. Why IP phones manufacturers produces such shit ? IMHA, you should just complain to the Htek manufacturer and ask them to provide firmwares which really supports SNMP standards. Can you anyway test the Htek.pm module included in this archive ? This module tries to fix as much as possible important datas with some assumptions, but I'm really not sure it will work as expected on live device. You just have to copy the module into the |
Beta Was this translation helpful? Give feedback.
-
|
The devices are imported and linked via their MAC addresses in Network devices. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Your idea
Please add Htek IP phone, I did not find MIB file for this device, at this document mentioned about UNICORN_MIB.mib
snmpwalk.zip
Beta Was this translation helpful? Give feedback.
All reactions