History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XCF-1966
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Michael Haag
Votes: 0
Watchers: 0
Available Workflow Actions

Resolve
Request Information
Operations

If you were logged in you would be able to see more operations.
sipXconfig

default snom config generated in 3.8 uses syslog server configured in sipx; unable to change the default

Created: 2007-11-07 11:27   Updated: 2008-03-20 09:26
Component/s: snom
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: 3.8 (GA release)


 Description  « Hide
in sipx 3.8 a syslog server can be defined (on the 'Devices | Network Params' screen). If a syslog server is thus defined, then by default snom phones' configs will enable syslogging to that server. However, the snoms can generate a substantial amount of syslog output, and there's little reason to enable syslogging unless actively troubleshooting a problem. So, it would be better if syslogging were not enabled by default on the snoms.

Unfortunately, there's no on/off switch for syslogging on a snom. It's configured just by the presence of a syslog server's addr. So, in sipx there's no way to disable syslogging via a phonegroup, since the sipxconfig default is to include the syslog server addr (if defined in sipx as described above).

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.