
| Key: |
XCF-1712
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Michael Haag
|
| Votes: |
0
|
| Watchers: |
0
|
|
Available Workflow Actions
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
Created: 2007-05-17 13:06
Updated: 2007-05-17 15:35
|
|
| Component/s: |
snom
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
The sipxconfig screens for snom configuration are organized completely differently than the snom phones' own GUI. Upon identifying a config param in the snom GUI that you'd like to change, it's difficult to find the corresponding param in the sipx GUI (or to confirm that the param isn't supported in the sipx GUI).
It would improve the sipx admin's experience a lot of we re-arranged our snom config screens to be more like snom's own config screens.
|
|
Description
|
The sipxconfig screens for snom configuration are organized completely differently than the snom phones' own GUI. Upon identifying a config param in the snom GUI that you'd like to change, it's difficult to find the corresponding param in the sipx GUI (or to confirm that the param isn't supported in the sipx GUI).
It would improve the sipx admin's experience a lot of we re-arranged our snom config screens to be more like snom's own config screens. |
Show » |
|
Adding search capabilities might be easier.
The best workaround for now:
grep param_name /etc/sipxpbx/snom/*.xml