Cisco Jabber for Windows plugin twitter

Hi All,

If you would like to show up your twitter messages (or other applications) as a plugin in Jabber Client please do the following:


  1. On a Windows 7 machine, go to the directory: C:\Users\%userprofile%\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config   (best is you do a search in your windows for jabber-config-user.xml)
  2. edit the jabber-config-user.xml file in wordpad (save as text file with extension xml).
Working config:
<?xml version=”1.0″ encoding=”utf-8″?>
   <config version=”1.0″>
<page refresh=”true” preload=”false”>
                  3.  Save the file and ensure its still called jabber-config-user.xml
                  4. restart jabber
It is possible to add multiple applications in the TAB,  for example if you would like to add in linkedin you slide the following after the  </page> :
<page refresh=”true” preload=”false”>
For info on Jabber goto
Have fun,

UC virtualization – Co-residency of 3rd party apps with Cisco UC VMs is now supported!

Customers have been asking for co-residency of 3rd party non-UC applications on the same VMware host / physical server with our UC apps for a very long time. Virtualization has matured, and is common practice in any IT organization. Although it still makes sense to “isolate” virtualized UC applications on dedicated hardware, customers now get the flexibility to mix and match our applications and 3rd party as they prefer. The server industry, including our own UCS portfolio, can nowadays scale servers to 10s of CPU cores, hundreds of gigabytes of RAM and virtually unlimited storage capacity. Customers wanting to maximize and optimize resource utilization and consolidate many servers to limit the server hardware footprint and cost of operation can now also include our UC apps in there…

Not sure if the example is relevant, but basically this means that a customer can now run Cisco Unified Communications Manager, file and print services and a mail server on the same box / VMware host.

The biggest challenge for Cisco was how to guarantee that our apps would get the required resources when they are co-located with others on the same physical server. Getting it working is one, but how can you define a design that you can actually fully support while there are so many things outside of your control… It’s possible,

All relevant details can be found on the following url:  (see topic 2.2)

In summary, this is a short overview of the rules we have set forward for “full co-residency”:

-UC on UCS rules apply with 3rd party VMs (no oversubscription for vCPU, vRAM, vDisks, etc…)

– Not allowed with BE6k

– Not allowed with Cisco UC Virtualization Foundation or Cisco UC Virtualization Hypervisor

– Cisco cannot guarantee the VMs will never starved for resources. If this occurs, Cisco could require to power off or relocated all 3rd party applications

TAC has defined the criteria that need to be met to get their support in an application note that can be found at:

Normalization scripting for SIP Trunking first step

SIP trunks can connect to a variety of endpoints, including PBXs, gateways, and service providers. Each of these endpoints implements the SIP protocol a bit differently, causing a unique set of interoperability issues. To normalize messages per trunk, Cisco Unified Communications Manager allows you to add or update scripts to the system and then associate them with one or more SIP trunks.

The normalization scripts that you create allow you to preserve, remove, or change the contents of any SIP headers or content bodies, known or unknown. After you configure a normalization script in Cisco Unified Communications Manager, you associate the script with a SIP trunk by configuring the Normalization Script fields in the Trunk Configuration window

The language used is Lua it is an open source, lightweight scripting language.

For info on Lua see

As a practical example we change in the SIP invite for a outgoing call on a sip trunk, the IP destination addresses in the SIP URI to a domain name.


INVITE sip:+3227784342@ SIP/2.0

The normalization script:

M = {}

function M.outbound_INVITE(msg)

local method, ruri, ver = msg:getRequestLine()

local uri = string.gsub (ruri, “”, “”)



return M

Changes into:


For some more info see:

The When, Where and How of Cisco versus Microsoft for Unified Communications

Zeus Kerravala, a renown analyst in our industry, published his thoughts on the how, where and whens of Cisco versus Microsoft for Collaboration on a while ago.

Regardless of whether this is an objective view or not, we found it fair enough and worth sharing with you. Please read and judge for yourself…

Cisco Cius Tidbits

Wanted to share some small movies on the Cisco CIUS.

Let us start with a basic Single Number Reach scenario:

To give you a view on the Cisco AppHQ and a sample application:

Basic calling & IM/Chat between Cisco Jabber for Blackberry & Cius

For more information goto

Before and after VXI

Recent studies have revealed that over 60% of enterprise companies plans to deploy desktop virtualization in some way over the next 3 to 4 years.  From a TCO point of view the advantages of desktop virtualization are simply amazing. As we move further into the so called “post-pc era”, having the ability to “port over” the virtual desktop environment to other devices or let’s say locations than the traditional office desk brings unseen flexibility and mobility.  Think of our Cius business tablet that offers you a full desktop environment in the office, while keeping access to the virtual desktop  over wi-fi or 3G/4G connectivity while on the go.

Desktop virtualization however just doesn’t prove to be that good a solution when it comes to integrating real-time audio and video. Using a soft phone or video client over a display protocol such as Citrix ICA or VMWare PCOIP simply doesn’t scale. “Hair-pinning” all the real-time traffic back and forth to the data center where the virtual desktop resides causes delay and jitter and puts a heavy burden on data center resources, not to mention possible bandwidth exhaustion…

Thanks to our Virtual Expirience Infrastructure or simply VXI, we are able to separate real-time traffic out of the VDI display protocol, routing voice and video traffic directly between end points, bypassing the data center.

Please take a moment to view a short video on our VXI solutions, showing you how separating voice and video traffic from the display protocol enhances the user experience. To start with, you will first see what you get without VXI. They say that seeing is believing. Well,  this video really speaks for itself.



To find out more about our VXI offering and VXC clients, please visit the link below, and see how we effectively bring the best of our borderless networking, virtualization and collaboration technologies together.

Trusted Relay Point configuration

The Cisco Unified Communications system can be deployed in a network virtualization environment. Cisco Unified Communications Manager enables the insertion of trusted relay points (TRPs). The insertion of TRPs into the media path constitutes a first step toward VoIP deployment within a virtual network.

The underlying network infrastructure comprises one of the key shared assets in an overall network design. A number of customer use cases require support for network infrastructure virtualization, such as the following examples:

-Guest internet access

-Partner access

-Departmental or divisional separation

-Subsidiaries/mergers and acquisitions

-Application segregation (data/voice)

All these applications include a requirement to maintain traffic separation on the network device as well as between network devices.

Traffic separation translates into concepts such as Virtual Routing and Forwarding (VRF). VRF allows multiple instances of a routing table to co-exist within the same router at the same time. In a virtualized network, these different routing domains, or VRFs, typically cannot communicate directly without transiting through the data center.

This situation challenges applications such as Cisco Unified Communications, where devices in the data VRF domain, such as software endpoints running on PCs, need to communicate directly with hard phones in the voice VRF domain without hairpinning media in the data center and without directly exposing the voice and data VRFs to each other.

Below a sample configuration off TRP.  This sample setup will force softclient RTP streams (voice or video) through the MTP control point in the router. In this router you might want to add additional security settings (FW, ACL, QOS,…). We will focus here on the basic TRP configuration in the  Cisco callmanager and  ISRG2 router.

Basic Principle:


As you can see in this setup we make a direct call between a Cisco EX90 and the CUPC client. Both devices are registered to the Callmanager 8.6.



Continue reading

%d bloggers like this: