On Thu, Jun 7, 2012 at 3:31 AM, Daniel Ullfig <dan.u@grmcompany.com> wrote:
Hello everybody:
 
I’m new to the list, and I’m new to cobbler. I stumbled upon cobbler looking for a solution to an idea I have. I’m working on a voip server idea. Mostly a front end to FreeSwitch. I think most voip systems handle new phone configuration backwards. You enter configuration information into the system before plugging the phone in, and then you plug the phone in. It seems backwards to me.
What I want to do is the following:
1 – plug new IP phone into wall jack
2 – IP phone asks DHCP server for IP address
3 – DHCP server detects by the vendor code and/or MAC address, that someone has plugged a new phone in
4 – DHCP server tells cobbler that there is a new phone attached
5 – cobbler writes a default configuration file tailored for the new phone and stores it in the tftp folder.
6 – DHCP assigns an IP address to the phone.
7 – The phone gets its configuration file from the tftp server
8 – Now, even though no one input configuration info into the system, you can already dial certain numbers like 611, 911, and maybe 0. So now the installer, even if he is in a remote location, can use the phone to call a central location and configure the phone using the same IP phone. No need for a second phone, no need to be near the phone server.
 

You might consider looking into http://theforeman.org/projects/smart-proxy/wiki, it should allow you to configure dhcp/tftp via an rest API and could probably make it easy to drive the needed changes.

Ohad


Does this seem like something that would be easy to implement in Cobbler? I like that it has a nice Web interface, and that it is extensible.
 
Dan Ullfig

_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler