Scott Lawrence wrote: > On Mon, 2009-01-26 at 10:11 -0500, Paul Mossman wrote: >> Hi all, >> >> Can anyone think of a good reason to keep the Polycom "SIP Settings in >> DHCP" screen around? >> >> It is cumbersome to use with sipXecs, and I don't think there's a good >> use case for doing so anyway. >> >> Basically, it can be used to configure the Polycom to get the SIP >> server address from DHCP. It still requires Line configuration >> (Username and Password), but if a SIP server is also configured then >> any DHCP value will be ignored. >> >> In sipXconfig all new Lines (Internal or External) must include a SIP >> server value. You can however go back and clear the SIP server value >> after the Line is created, which would allow a DHCP value to be used >> instead. >> >> There is no reason to do this for an Internal Line though, because it >> will only work if the DHCP value is always exactly the same as what >> sipXconfig would use. >> >> For an External Line it is even quite a stretch. If your system has >> Polycoms with External Lines then each is probably an exception, >> rather than many using the same external SIP server. It seems >> unlikely to me that an administrator would have a desire to use DHCP >> (instead of sipXconfig) to change the SIP server address that the >> External Line on a Polycom registers with. >> >> I propose getting rid of this screen entirely. >> >> If there are no objections then I'll proceed. Let me know. Thanks. > > I don't think there is any use for such a parameter in a sipXecs > configuration. >
Make sense to me: yank it. So that means you are not taking patch for http://track.sipfoundry.org/browse/XCF-1030, right? D. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
