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

Key: XCF-2562
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

Polycom configs: insert Polycom's template revision number in generated configs

Created: 2008-05-19 14:25   Updated: 2008-05-19 14:45
Component/s: polycom
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
When sipxconfig generates configs files for a Polycom they've based on some version of Polycom's sip.cfg and phone1.cfg templates. It would be useful for debugging Polycom issues if the configs generated by sipxconfig included the Polycom template revision number.

Here are examples of Polycom template files, and their revision numbers:

 [root@sipxchange polycom]# more /var/sipxdata/configserver/phone/profile/tftproot/sip.cfg
 <?xml version="1.0" standalone="yes"?>
 <!-- SIP Application Configuration File -->
 <!-- $RCSfile: sip.cfg,v $ $Revision: 1.233.2.32 $ -->

 [root@sipxchange polycom]# more /var/sipxdata/configserver/phone/profile/tftproot/phone1.cfg
 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 <!-- Example Per-phone Configuration File -->
 <!-- $RCSfile: phone1.cfg,v $ $Revision: 1.83.2.2 $ -->


 All   Comments   Work Log   Change History      Sort Order:
Damian Krzeminski - 2008-05-19 14:45
Let's not use RCS keywords though: Velocity treats $ as variable indication.