> I'm looking at the patch for XCF-2736, and I have some questions.
It is patch for XCF-3257, which is related to XCF-2736. > Note that XCF-3262 exists to cover syslog daemon (syslogd) configuration and sipx-snapshot changes. > 1. Do we need to configure the sipXecs syslogd? Could we leave it on always, or do we need to allow the superadmin to turn it off? By default, it is not enabled to accept logging from remote syslog clients. In other words, the logs from remote clients are dropped. I think for XCF-3262, we should add the capability that Admin can turn remote syslog on/off, and "on" as default. > 2. Will syslogd require a configuration change as logging endpoints are added? i.e. Start capturing logging sent by 10.10.10.47. No, it does NOT. > 3. Should we bother exposing Polycom configuration to select the syslog server/transport/facility? I think we should just keep things simple: Polycoms > send their syslogs over UDP to sipXecs, with facility "local use 0". That way the logs can get picked up in a Snapshot. This is what is exposed from TUI. I think we should leave there for some advanced users if they intend to change it, but we can tag it as "advanced" so that normal user would not see this setting. Cheers, Huijun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
