| Key: |
XCF-2619
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Kevin Thorley
|
| Votes: |
0
|
| Watchers: |
0
|
|
Available Workflow Actions
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
Created: 2008-06-04 10:51
Updated: 2008-08-26 10:13
|
|
| Component/s: |
None
|
| Affects Version/s: |
3.11.3
|
| Fix Version/s: |
4.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
registrar-config support was added to sipXconfig in 3.11.3. sipXconfig now maintains the registrar-config settings in the database and handles replication of the file, eliminating the need for registrar-config.in. However, no upgrade support is included. sipXconfig needs to be able to read registrar-config.in on an upgrade and migrate the data to the database. Once this is done, the registrar-config.in file can be deleted
|
|
Description
|
registrar-config support was added to sipXconfig in 3.11.3. sipXconfig now maintains the registrar-config settings in the database and handles replication of the file, eliminating the need for registrar-config.in. However, no upgrade support is included. sipXconfig needs to be able to read registrar-config.in on an upgrade and migrate the data to the database. Once this is done, the registrar-config.in file can be deleted |
Show » |
| There are no comments yet on this issue.
|
|
sipXconfig needs to provide support for upgrade of registrar-config