I never use it. It was a nice feature, but it is hard to maintain because a patch or update has to be issued, plus code for every phone type and its associated mac address pattern.
If we already "know" what this is, then why not a default config instead. Seems like a natural progression to me. Besides, the current autoconfig is a real step closer to hoteling. On 5/4/10, Alfred Campbell <[email protected]> wrote: > On 5/4/2010 3:20 PM, Lazieburd wrote: >> On Tue, May 4, 2010 at 2:06 PM, Alfred Campbell<[email protected]> wrote: >> >>> Due to the addition of the auto phone provisioning service we are going >>> to remove the old device discovery feature. >>> >> 4.2 or trunk? >> >> Is there any way to make it optional? I'm not familiar w/the >> dependencies of the feature, is preflight one of them? >> > 4.2 and Trunk.. Of course it could be made optional however with the > support issue we have seen its of little value from what I see. Does > anyone rely on this ? Tony, others? > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- Sent from my mobile device ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
