Please find the attached HTML document, download and open it on your PC. This provides an easy to use form where you simply answer a few questions and it will render the proper jabber-config.xml file for you to copy/paste. There is built in logic to verify you are entering in the correct information for the deployment selected, as well as valid XML characters.
Update 2015-07-09: Updated with 11.0 keys, testing new automated method to mine key values from public facing documentation, new UI. Feedback on the new UI is welcome
Update 2015-03-12: Update default selection for new keys.
Update 2015-02-18: Added more keys from 10.6.
Update 2015-01-28: Update for 10.6 keys.
Update 2014-12-17: Update value generation when using reserved characters (&/&) so that only substitution takes place once.
Update 2014-11-19: Reworked the Jabber-Plugin additions, relaxed hostname verification, more import enhancements, updated missing keys in 10.5, corrected default value selection.
Update 2014-10-22: Updated CSS, corrected a few default values to match updated documentation and user comments in this forum, enhanced import function, added optional Telemetry Suggestion from existing data.
Update 2014-10-09: Added text import of existing jabber-config.xml file to pre-populate the form (works in FireFox & Chrome, IE not tested). Removed SHA Hash generation of TelemetryCustomerID field.
Update 2014-08-29: Added 10.5 J4W keys which should apply to the other 10.5 releases as well, with additional logic to aid with some of the more complex key configuration.
Update 2014-05-12: Modified UI slightly, also corrected problem with checkbox inputs
Update 2014-05-09: Updated logic to include PhoneMode keys for versions past 9.2; although not all clients support PhoneMode yet.
Update 2014-04-24: Corrected misspelled keys, and validation errors.
Update 2014-04-21: Added J4W 9.7 specific fields, as well as simplifying data entry for BDI fields. If using BDI, simply make sure you've selected OSX, iOS, or Android, and the script will copy whatever fields you have entered for the EDI integration, and automatically create the BDI specific keys for you.
Update 2014-01-02: Added partial Mac 9.2 specific fields for BDI, Windows 9.6 specific fields.
Update 2013-07-25: Modified Search Base validation logic to include the default CN in addition to OU's
Update 2013-05-17: Added 9.2 specific fields.
Update 2012-12-29: Added 9.1 specific fields and implented version switching for it to work with both 9.0, 9.1, and any future version dependent fields
Update 2012-08-16: resolution to CSCua39052 in Jabber 9.0(4) resolved the Base Filter open/close bracket problem. Updated validation tests to reflect this change. As such, this script will only work for Jabber 9.0(4) and later when using a custom Base Filter; if using Jabber prior to 9.0(4), simply remove the last closing bracket in the Base Filter tag before uploading to TFTP.
Good day, We are planning to upgrade unity connection from 9.1 to 12.5 currently Unity 9.1 is hosted on esxi version is 6.0 We wish to upgrade esxi to version 6.5we know UC 9.1 is not compatible with esxi 6.5, however if we should upgrade t...
Hi There, We are trying to install CUCM PUB 12.5 and we are struck on the black blank screen from past two hours. we can wee RAM is being utilized 100% and CPU is around 20%. Is this normal? If yes, how long we have to wait until this black screen is...
A customer has a Jabber Directory Integration with LDAP. From the Jabber search, he should be able to search users by various other LDAP Attributes. The feature generally works (e.g. he can search for a City, and it will show him all users that have the C...
HelloIn the macro framework, is there a way I can register to the HttpClientResult response after I send an HTTP get request?In putty, affter sending a xcommand HttpClient get, I get this:*r HttpClientGetResult Body: example I would like to get that ...
I'm struggling to understand why the From in our outbound INVITE to our primary ITSP is using the IP address of our secondary ITSP, instead of the IP address of our CUBEs sending interface. INVITE from Jabber to CUBE is fine:Received:INVITE sip:80781...