http://www.cisco.com/en/US/products/hw/phones/ps379/index.html
Nifty idea, mostly pushed by Cisco. The idea is that instead of wiring your buildings with Ethernet and phone, you just wire them with Ethernet and you use VoiceOverIP. So you have very nifty phones that plug into Ethernet and use DHCP, H.323 etc. Very nifty.
Sorry for messing up this page - busy :)
First Looks:
Configuration - Central, via DHCP, and config files/images via TFTP.
Note for configuring a TFTP Server - the file/RPM to get (FC2) is 'tftp-server', NOT simply 'tftp'. That is a client...
If the TFTP server is NOT running on the DHCP server:
The phone will grab this address, and hopefully get all of its SIPDefault.cnf/images/etc from here.
For specifying the hardware address, use:
' host { hostname <your-phones-hostname> { hardware-ethernet <phones-MAC-address-here> } } '
To be completed...
More dhcpd.conf tomfoolery...
Apparently you need to use 'custom' dhcp options to let the phone get the tftp-servers location from dhcp server...
More mess:
I first managed to get the new SIP image loaded into the phone using something like (in dhcpd.conf);
'group {
- VoIP Phones Group
next-server <tftp-server-ip-addy-here> hostname <your-phones-hostname> { hardware-ethernet <phones-MAC-address-here> }
}'
OK.
So far:
To get SIP image loaded into your phone, use the 'group' bit above in yer dhcpd.conf. It now appears as though you need to tell the phone more options - 'scuse the pun - (possibly the 'option 66/150' mentioned previously?) to be able to get further than loading just the phone images...
One page links to IPPhones:
lib/BlockParser.php:505: Notice: Undefined property: _tight_top