Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.5003.8.1.1.67 | Mediant 1000 | 6.40 |
| 1.3.6.1.4.1.5003.8.1.1.71 | M1000 ESBC | 6.60A |
| 1.3.6.1.4.1.5003.9.10.10.2.6.4.22 | Mediant 800 | 6.60A |
Some AudioCodes models can not be auto-detected by CLI, because they do not report a valid model name that can be easily parsed. SNMP discovery will work with all models.
This note applies only for drivers that use HTTP requests for driver functions. HTTP proxy operations are supported by setting the device access variable "http_proxy" to "ip:port", replacing with the IP and port values of the proxy server. SNI-requiring devices (e.g CloudGenix & Cisco Meraki) can be supported by using the device access variable "alternate_host" to contain the DNS name of the host. The host name will be used rather than the normal management IP address for all HTTP requests, effectively supporting SNI.
Discovery tasks for Javascript drivers handle More prompts by using timeouts, which can cause problems with the third-party SSH client code, which interprets the timeout as a disconnection. There are two options to work around the problem. Setting the RCX option [<option name="Driver/Discovery/UsePollRead">true</option>] in site_options.rcx will effect the workaround for all affected devices. Alternatively, it could be applied to a single device by setting the device access variable "PollRead" to "true".
Discovery tasks for Javascript drivers use wakeup characters are sent during device connection, to ensure that the device is responding. Normally, these characters do not echo to the console, but some devices may echo them. In this case, this causes the prompt detection phase to fail, which in turn can cause More prompts to not be handled properly, and discovery may fail. If these characters are echoed from the device [check the session log to see this], then set the device access variable "skip_ctrl_u" to skip the sending of the wakeup characters. Note that setting this option on a previously working device could cause discovery tasks to fail, but it only affects CLI discovery. SNMP discovery is unaffected.