Sigh... you're not the first one and won't be the last one.
There are so many different BU (Business Units) in Cisco. Each one cares about itself. They claim their products are complaint with "standards" (IETF, IEEE, etc). But how they interact with other products (or end users) is never a priority.
So the product documentations will tell you what each menu/command does. But they'll never tell you how to build a solution or feature with those menu/commands.
There's no UC "solution" from Cisco. They have a series of independant products they called "Unified" (e.g. Unified CM, Unified Presence). But there's no unified architect/roadmap for those products to work together.
For example, VOS (Cisco tuned RedHat Linux) is supposed to be a common OS platform for all voice products. However, after years, it's still considered as part of CUCM (CallManager) instead of a common OS. Thus CUPS 8.0 could have a different OS version than CUCM 8.0. Any bug fix in the OS level has to wait for CUCM update.
Another example, different products (CUCM, CUPS, CER, UCCX) has different licensing mechanism and different user management concepts, which caused lots of confusion and frustration.
You made the right decision going for Office365 and Lync. I've seen quite many customers moving from Unity to Exchange UM. Microsoft is yet to catch up with CUCM in enterprise VoIP. But some phone set vendors (such as Polycom) are selling Lync hard phones (just like Cisco IP phone sets). We'll see.
Depends on how you are using WebEx. Is WebEx hosted and Audio onsite or is MeetingPlace all internal?
As for Lync vs Jabber, I think its pretty close now. You have to weigh how much the customer wants IM/Phone/Presence all on one client. If they do, then Jabber might be a better option. Its nto quite easy to figure out the costs and infrastructure required between the IM clients. Jabber could be hosted or be onsite. (pros/cons with it). Lync could be hosted or onsite (pros/cons)/.
As for Office365 and Untiy Connection, its supported. You can have Connection onsite and connected to Office365 Exchange. Its also evolving as we speak. MS will support more function with the release on Connection.
As for Licensing, the mechanism is quite simply once you figure out the user count if you have CUWL standard or Pro and whats included, etc. (IE, number of devices, mobile, Jabber, VM box, etc)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
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 verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...