Tag Archives: cisco

Cisco Jabber 10.5 – Configuring Update URL

1 Open the main jabber-config.xml and in the group element , add the configuration parameter:  Point it to the location where you are planning to create “update.xml”.  Upload the “jabber-config.xml” to all of your TFTP nodes and restart the TFTP Service.
1

Open the main jabber-config.xml and in the “Client” group element , add the configuration parameter: UpdateUrl
Point it to the location where you are planning to create “update.xml”.
Upload the “jabber-config.xml” to all of your TFTP nodes and restart the TFTP Service. 

2 Browse to the folder on your webserver were you want to create “update.xml”. if you want, you can drop your MSI jabber package there as well. In this example, I’ve created both files in Microsoft IIS on a windows 2012 machine
2

Browse to the folder on your webserver were you want to create “update.xml”. if you want, you can drop your MSI jabber package there as well.
In this example, I’ve created both files in Microsoft IIS on a windows 2012 machine 

3 “update.xml”  consists of the following configuration paramaters: : this is the softwarebuild release number of the package you want to release : Contains the major software release number of the package you want to release : contains the weblocation of your MSI package
3

update.xml” consists of the following configuration parameters:
LatestBuildNum: this is the softwarebuild release number of the package you want to release
LatestVersion : Contains the major software release number of the package you want to release
DownloadURL: contains the weblocation of your MSI package 

4 Once you’ve updated “Jabber-config.xml”, created  “update.xml” and placed the corresponding MSI at the correct location, you can restart Jabber and try the “check for updates”
4

Once you’ve updated “Jabber-config.xml”, created “update.xml” and placed the corresponding MSI at the correct location, you can restart Jabber and try the “check for updates” 

5 Cisco Jabber should now try to locate the update.xml and read the information from it regarding the software version and it will compare it with itself.
5

Cisco Jabber should now try to locate the update.xml and read the information from it regarding the software version and it will compare it with itself. 

6 If the version stated in update.xml is higher, it will prompt the user with the option to upgrade
6If the version stated in update.xml is higher, it will prompt the user with the option to upgrade 

7 Once decided to upgrade, the package is downloaded from the URL specified in the update.xml.
7

Once decided to upgrade, the package is downloaded from the URL specified in the update.xml

ESXI Changing NIC to vmxnet3 for CUCM 10.5 upgrade

If you have a CUCM virtual machine and you want to upgrade it to 10.5.x, you probably need to amend the NIC type from “Flexable” to “VMXNET3″. This guide shows you how its done.

001
1

Shut down the node


002
2

In VSphere, select the Host, Summary , right click on the data store and select “Browse Datastore”


003
3

Go to the folder that contains your VM of choice. In that folder, locate the *.vmx file and download it to your pc.


004
4

Once on your pc, open the vmx file with your favourite text editor.

Scroll down to the line “ethernet0.virtualDev – “flexible””

Change the type to vmxnet3 (lowercase)

Note:
If the line is not listed, add it at the end of the file.

Save and close the file.


005
5

Go back to the VMhost of your VM, browse to the datastore and rename the old vmx file to prevent a duplicate


006
6

Upload the amended vmx file from your pc back into the vmguest folder.


007
7

In the vm guest view, right click the guest that needs amending and choose “remove from Inventory”


008
8

Browse back to the datastore of the VM Host


009
9

Go back to the VMhost of your VM, browse to the datastore In the vm guest folder, right click on the amended vmx file and choose “Add to Inventory”


0010
10

The server should now be visible in the vm guest overview


0011
11

Open the properties for the VM guest and verify that the settings are now set to VMXNET3

Job done.