Hi all, I had a look at the existing polycom-config script at http://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXtools/src/ It didn't do quite what I was looking for, so I added some new scripts:
polycom_config_dump.rb ---------------------- This script parses the specified Polycom SoundPoint/SoundStation IP master configuration file and extracts the individual sip and phone1 configuration parameters, which it dumps (sorted) into a flat INI file. (DUMP_<MAC>.ini) The key thing here is that it starts with the <MAC>.cfg then parses multiple CONFIG_FILES, applying overrides in the same manner as the actual phone. As an added convenience, the script can retrieve files given a URI: ./polycom_config_dump.rb ftp://PlcmSpIp:[EMAIL PROTECTED]/0004f2064015.cfg polycom_ini_diff.rb ------------------- This script compares to the two specified INI files (that were generated by polycom_config_dump.rb) and reports the following differences (in sorted order): D=> Parameters that appear in both files, but with different values. 1=> Parameters that appear only in the first file. 2=> Parameters that appear only in the second file. Yes, I re-invented the "diff" wheel. But, I needed an easy way to see which parameters were missing from one file or the other, versus those that just had different values. The impetus for creating these tools was to find all the parameters from Polycom default files that are missing from our generated profiles. (Which is the root cause for issues such as XCF-2877, which was originally raised against Polycom.) -Paul [EMAIL PROTECTED] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
