Cisco IP Phones are only discovered via CDP and CAM table entries. Since the phones reside on a different VLAN, the OnPlus Agent device is unable to discover them using other methods. If phones are plugged into a router/switch that is not supported by the OnPlus Portal, they will not display in the Topology.
A single phone should only be accessed once. The following information will be gathered: Serial number, information to make a PIDVID, and the software version. No other information is read or set, but the backup/restore and firmware via the management capabilities item in the Info tab are disabled.
Once the serial number has been set for a phone, it will not be accessed again. In some cases the phone will be accessed multiple times until the full discovery information is sent to the SN and then back down to the OnPlus Agent in the consumer_sani.xml file.
A phone may be accessed multiple times if it has a load from the factory that does not support HTTP access. Once the phone has been configured into a PBX system that supports HTTP access and has an upgraded the phone load, it will be accessed to obtain the needed information.
Note: Cisco OnPlus Service was tested with the 6921, 6941, and 6961 models, with feature support expected to apply to all other models in the series.
I have a working CME system with all 7975 phones and CUE that works correctly including MWI. I added an ATA-186 and it too works but the MWI on my AT&T cordless analog phone connected to it. The stutter tone does work when a message is lef...
Hi,I have an RV340w configured to talk to a VDSL modem that is in bridge mode via PPPoE. Both the IPv4 and IPv6 connectivity uses the shared PPPoE credentials and receives an IPv4 address (29 bit subnet) and IPv6 addresses - an ND prefix (64 bits) and a P...
Hi, Hardware: RV340W running Firmware 1.0.03.20 In my captive portal instance, I have set the parameter "Idle Timeout" to "0" as I don't want any timeout. However, when someone successfully logs in to the captive portal, they are kicked out imme...
I administer three RV340s. They're all running firmware 1.0.03.20. This fault has been observed in every RV340 I've tested, on this point: i.e., two. I say it's a bug in the firmware of the RV340. Moreover, ...