That field takes a XX:XX:XX:XX:XX:XX MAC address string, not a range. That's why I revised the wiki.
thats the wrong form.
And when I define the device with the phone's specific MAC address, that parameter seems to work. I get Orbiter messages about the 7970 while it's configuring. I'd prefer a range, because that would let me make a template that works with any number of devices. It's not really "plug & play" if I have to create a device for each phone I plug into the LAN. But a single MAC addr is what that form currently takes.
again, its the wrong form. You are not editing the device template (the ranges go in the table DHCPDevice:
mysql> describe DHCPDevice;
| Mac_Range_Low | bigint(20) | NO | | 0 | |
| Mac_Range_High | bigint(20) | NO | | 0 | |
OK, but without a CTL file I get status messages on the phone complaining that CTLFile.tlv is not found.
whats the problem with that?
Including an empty CTL<MAC>.tlv (MAC with no ":" chars) gives me onky "CTL update failed", instead of "File Not Found: CTLFile.tlv" and "No CTL installed" with no file available for tftp. No success either way.
if you don't want to believe me that this file is not needed you can further try submitting random files to your selsius ethernet phone (wonder where that SEP comes from?).
I still think I'm very close, but not because of the range. Thanks for helping out.
that may be fine for you but you destroyed correct information. The old page was sufficient to extend the device template. Please repair it (you have touched the 7970 Orbiter, too).
I was hoping to use SCCP to start, partly because I heard that LMCE supports SCCP better than it does SIP. Maybe upgrading the phone to SIP will work better, or produce more detailed failure results. I have a Cisco account through which I bought the SIP firmware upgrade. But I don't have concise directions for upgrading to SIP first.
sccp works fine. I simply prefer the sip image to have other lines provisioned outside lmce/asterisk.