So, what are some of the challenges that you should be mindful of? The challenges can be grouped by End User Challenges and Business Challenges. However, when introducing this into your production environment you will need to pay attention to a few things. In a lab environment, it is relatively simple to get the Cisco Jabber for iPad client up and running. So, I thought I'd use that as an excuse to put this thing together. However, there are lots of steps and the document is a tad on the clunky side. The Cisco Jabber for iPad administration guide provides detailed steps for provisioning.
Cisco jabber video for telepresence administrator guide for mac#
Those of us who have been using the Jabber for Mac ( not Jabber Video for Mac, which is just Movi) client are probably familiar with this behavior. The client won't run both services simultaneously (unless there is something I don't know). So, for example, you can provision CUPS and then back out to provision WebEx Connect. With the Jabber for iPad client certain configurations are mutually exclusive, but it is a relatively simple matter to re-provision the client to use different services. After provisioning the Presence/IM provider then you provisioned the call processing solution. The way that the Jabber clients work (well, typically?) is that you would provision your Presence service first, whether that be WebEx Connect or CUPS. It has been one of those summers! In this installment I am going to do a walk through of provisioning Cisco Jabber for iPad to use CUCM for voice/video call processing and CUPS for presence.
I had 80% of this thing written 3 weeks ago.
0 kommentar(er)
