That's probably a bug in the "upload" script.   Unfortunately I cannot say for certain where that bug is. There was significant re-work done to improve the way the keys are generated.   Future versions of the script will have a "wizard" to guide the user through which configuration keys need to be populated, based on the type of infrastructure they have. If this doesn't go over well, it's easily reversible.   What the "wizard" will do, when/if there are configuration parameters that are not valid or redundant, it will remove them on behalf of the user. The behavior you're describing sounds a lot like that.    I'm going to update it with the 11.1 keys and will re-post here, then we can test with that version and go from there. ... View more

Thanks! Done! I'm working on a script to double check the default values documented on CCO but that's going to be a few months out. If there are others we catch, please let me know. ... View more

What browser are you using? The download works fine for me in Chrome Version 40.0.2214.115 (64-bit). What program are you using to extract the ZIP file? The Jive platform requires it to be uploaded as a ZIP file, and it adds the "_" character after upload, but I can extract it just fine using the Archive Utility.app. If there's another application that doesn't extract this, I'd like to try and reproduce the behavior. The direct download link is: https://supportforums.cisco.com/sites/default/files/attachments/document/jabber-config.html__0.zip ... View more

The script just takes the parameters that are published in the documentation and performs some input validation on the values. For a full list, please refer to this page: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and_chapter_01010.html#CJAB_RF_G345C5C0_00 ... View more

thanks, there were apparently a good number of keys that I missed from the pre-FCS documentation. I've updated the script with everything I could find on cisco.com now. ... View more

Thanks for reporting this. I'll need to update the code to catch when the HTML code is already in the string so we don't convert it twice. ... View more

This is pretty old, but it'll still works for the Windows PRTs. The challenge comes with Mac, iPhone, and Android PRTs.. I have another prototype for those as well as a full feature log parser, but since those clients don't have the auto-upload functionality yet, it's not really that helpful in its current form but is useful in certain situations for log management. I'll have to check if I have something worth updating on this post. ... View more

I updated this verification to allow the hostname/domains to begin with any alphanumeric character.  However it will still fail if you simply enter in the hostname (i.e. 123CUCM), you'll need to populate the field with the FQDN (i.e. 123CUCM.local) for it to pass the validation test. ... View more

Thanks for catching that, I corrected this problem and uploaded a version which allows that to be generated. ... View more

The key names are hard coded to those values "Home", "Other", etc.  This allows the client to know which keys to lookup consistently.  However, you can change the value of these keys to whatever attribute exists in the directory. ... View more

It will work with CUCILync.  The only thing that is in CUCILync, that is not in this script are the "Internet Explorer Pop-up" parameters used for the toast notifications. ... View more

The validation is checking that the value entered is not empty, and matches a regular expression.  The JavaScript logic for this is: (e.value !== '' && (e.value.match(/^(OU=).+,\s*(DC=).+/i) === null || e.value.match(/[^\w-_\s=,]/ig) !== null)) From your example, it appears you're using a Container rather than an OU for the Search Base.  And the logic is hard coded to check specifically for "OU" at the begining of the line.  I'll have to make some changes to that regex to allow "CN" to be included as well. In the short term, you could edit the file you downloaded in a text editor and simply comment out or remove lines 2528 to 2530 and this will remove the validation checking for the Search Bases. ... View more

The same methods would work for 9.x, however some of the naming may have changed slightly.  The core configuration sections are still the same between 8.x and 9.x.  I believe starting with 10.x there will be a different, more streamlined, flow to the configuration/deployment. ... View more

BDI would be configured similar to how you configure non-AD LDAP integrations.  Esentially it's setting up EDI but manually specifying the LDAP servers to connect to and a service account for them to connect with.  This guide may help some: http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config_chapter_0101.html#JABW_RF_O1D72112_00 Once Jabber Mac 9.2 is posted, I'll revise this script to work with that as well if there are any additional paramters that need to be added. ... View more

The traceback seems to imply that it cannot find a column named 'Device Name' inside the "HKPhonesEdit.txt" file. The way this should happen, is at startup it should call "open_file" where it will open "HKPhonesEdit.txt" and then pass its content to "csv.reader" with the delimiter set to ",".  Which it then dumps all that data into an object called "csv" by using "csv.DictReader".  This happens around line 266 in the script. With that information, "get_dn_list" is called with what should be the "csv" object returned from "open_file".  If you can PM me the input files you're trying to use, I can try to reproduce and find a fix to this issue. ... View more