Xorcom XP0100, User Manual

Page: 63 / 71

XP0100 Enterprise IP Phone Using the Advanced Phone Functions
Xorcom Ltd. 56 www.xorcom.com
The table below shows part of the available object identifiers (OID) on the phone:
OID Description
MAX-ACCESS
1.3.6.1.2.1.37459.2.1.1.0
The textual identification of the contact
person for this managed node,
together with information on how to
contact this person. If no contact
read-only
1.3.6.1.2.1.37459.2.1.2.0
An administratively-assigned name for
this managed node. By convention, this
is the node's fully-qualified domain
name. If the name is unknown, the
value is the zero-length string.
read-only
1.3.6.1.2.1.37459.2.1.3.0 The physical location of this node (e.g.,
`telephone closet, 3rd floor'). If the
location is unknown, the value is the
zero-length string.
read-only
1.3.6.1.2.1.37459.2.1.4.0 The time (in hundredths of a second)
since the network management portion
of the system was last re-initialized.
read-only
1.3.6.1.2.1.37459.2.1.5.0 The IP Phone's Firmware version read-only
1.3.6.1.2.1.37459.2.1.6.0 The IP Phone's Hardware version read-only
1.3.6.1.2.1.37459.2.1.7.0 Model of machine read-only
1.3.6.1.2.1.37459.2.1.8.0 The IP Phone's MacAddress read-only
1.3.6.1.2.1.37459.2.1.9.0 The IP Phone's IPAddress read-only
1.3.6.1.2.1.37459.2.1.10.0 The IP Phone's LastUpVersion read-only
We recommend a SNMP test suite which is available at http://www.net-snmp.org/.
The phone supports only SNMP v2c. Basic GET requests can be run in order to retrieve
information from an SNMP-capable device. For example:
>snmpget v2c –c public 192.168.3.10 1.3.6.1.2.1.37459.2.1.5.0
Action URL
Action URLs are HTTP GET Requests allowing the phone to interact with web server
applications. To use this feature, you should specify a HTTP URL corresponding to the
predefined event. In case the predefined event has taken place, a HTTP GET to the
specified URL is performed.
HTTP GET requests may contain variable names and variable values, which are
separated by “=”. Each variable value starts with $ in the query part of the URL (e.g.
http://192.168.10.1/help.xml? MAC=$mac).
Action URLs can be triggered only by predefined events (e.g. Log on).