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.
Hello All, My organization would like to integrate a future system using Rest API and also most importantly integration our ticketing system (IVANTI "HEAT") so that the agents would not have to have multiple windows opened at all times because they a...
I have this idea for video conference security. In my idea there is encryption on an end to end connection with ssh that has video encryption and sound encryption for ultimate security with alternating variables in the sound and video .I invented a n...
Hello,I need Support ASAPI have problem that users with correct service profile and IM & P option check configured not show in presence topology in IM and PresenceI try many things and restart and on troubleshooter I see unassigned users so I assign p...
Hi,We have a 3945 with Version 15.5(3)M5 with CUCM 10.5 We have a new ITSP provider that require authentication. We have configured the authetication in dial-peer level:dial-peer voice 20 voip
description ** Outbound SIP-ISP **
Hello,we change our ISP from ISDN to SIP. With the new ISP we use SRTP. With our phones it is no problem to call via this connection. The phones have certificats and all is fine. But with our VG310 i have a question. I know i can connect the VG310 via TLS...