|
0:00:14
|
|
|
0:00:19
|
First in talking about Presence, we need to describe some terminology
|
|
0:00:23
|
and look at an overview of how Presence operates.
|
|
0:00:28
|
So here we see on the left, we have BLinus
|
|
0:00:31
|
Benjamin linus at ine.com and we´re going to call him person A
|
|
0:00:36
|
and this person is going to publish their status
|
|
0:00:42
|
or their Presence information to the Presence service.
|
|
0:00:46
|
Now the presence service is something that resides in the CUCM.
|
|
0:00:51
|
Contrary to some belief, there is in fact of course the Unified
|
|
0:00:56
|
Presence server, Cisco Unified Presence Server or CUPS,
|
|
0:00:59
|
but that is actually not what´s responsible for maintaining
|
|
0:01:03
|
status of Presence or status of individual phone dns.
|
|
0:01:10
|
In fact, it´s the CUCM server that actually maintains that state
|
|
0:01:14
|
and the CUPS server, the Unified Presence server is
|
|
0:01:19
|
something that subscribes to that state and then is used for
|
|
0:01:23
|
third party the tools, we´ll take a little bit more to look at that,
|
|
0:01:25
|
but the Presence service that we see here,
|
|
0:01:28
|
is in fact running on the CUCM server
|
|
0:01:32
|
and so the person A or BLinus that is publishing their status.
|
|
0:01:39
|
We could think of them as the publisher, but that might get
|
|
0:01:43
|
you know confusing with the term publisher for the database
|
|
0:01:48
|
for all of the CUOS or Cisco Unified Operating System Platforms
|
|
0:01:54
|
And so what we refer them as is the presentity.
|
|
0:01:58
|
They are presenting their state, they are the presentity.
|
|
0:02:02
|
So they publish their status and of course a registration
|
|
0:02:06
|
of their phone will have and their dns and everything will
|
|
0:02:10
|
obviously preceeded that publish and then we have watchers
|
|
0:02:15
|
again they are subscribing to a particular service or to a particular
|
|
0:02:22
|
dn that they would like to watch,
|
|
0:02:25
|
but to call them a subscriber could confuse them with the database.
|
|
0:02:28
|
So we refer to them as the watcher, now
|
|
0:02:32
|
a lot of times and I would say, most of the time
|
|
0:02:38
|
both the person A on the left, the presentity
|
|
0:02:42
|
and the watcher on the right
|
|
0:02:45
|
are actually performing both, that is their presenting their own
|
|
0:02:51
|
dn status and their requesting or watching other dns. OK, so
|
|
0:02:57
|
everyones is essentially publishing their status and the
|
|
0:03:05
|
or they are also watching
|
|
0:03:09
|
the other person or many other people or a few other select peoples
|
|
0:03:13
|
dns status, now we don´t watch people, we don´t watch users
|
|
0:03:19
|
and we don´t watch phones, it´s important to note that we watch dns.
|
|
0:03:24
|
So a watcher as we see over here on the right they will be subscribing
|
|
0:03:28
|
through a few different various methods that we´ll take a look at,
|
|
0:03:31
|
let´s just say for simplicity now through a BLF
|
|
0:03:34
|
or Busy Lamp Field speed dial, they´ll be watching the
|
|
0:03:41
|
at least one of the dns from person A.
|
|
0:03:45
|
OK, the person A might have multiple dns and if so
|
|
0:03:49
|
then the watcher, if they wish to watch more than one dn
|
|
0:03:53
|
of person A they would have to have the rights
|
|
0:03:56
|
to do so and we´ll talk about how that´s done in just a little while.
|
|
0:04:02
|
So let´s take a look at the Presence components.
|
|
0:04:05
|
We see our phone here, let´s just call this Phone A
|
|
0:04:10
|
just like we had had Person A on the last slide
|
|
0:04:13
|
and Phone B here and we´ve got the CUCM presence or status server.
|
|
0:04:18
|
So Phone A goes off hook and that is sent
|
|
0:04:22
|
down to a BLF speed dial which we see an example of here
|
|
0:04:26
|
on the screen, an example screen shot of their display.
|
|
0:04:30
|
That status is sent to Phone B, so it´s really pushed
|
|
0:04:36
|
by the CUCM to Phone B to tell them to.
|
|
0:04:41
|
Not only show the actual display, but they would have a transluscent
|
|
0:04:45
|
line button here or really just button and that would be
|
|
0:04:49
|
this is a BLF speed dial, BLF stands for Busy Lamp Field.
|
|
0:04:53
|
Busy Lamp Field actually goes far far back to old
|
|
0:04:59
|
KSU or Keys System Unit or PBXs
|
|
0:05:02
|
where there was actually a physical lamp there that was lit.
|
|
0:05:08
|
We would have multiple 25 pairs of cables run, you know
|
|
0:05:12
|
let´s say a reception type example or
|
|
0:05:16
|
assistant to a manger would be a common
|
|
0:05:20
|
place that we would have these Busy Lamps.
|
|
0:05:23
|
But they´re still in the industry referred to as a Busy Lamp
|
|
0:05:26
|
Field and we do have that little transluscent LED
|
|
0:05:29
|
light for the line button that will show a different color for status.
|
|
0:05:36
|
We´ll also see on the display, so here on the display
|
|
0:05:39
|
you might see two little phones and you see what are 12
|
|
0:05:44
|
little white squares behind those and those represent the keypad
|
|
0:05:49
|
and the 2 phones over top of the key pad represent the fact that
|
|
0:05:54
|
there is a call and that would switch to just a keypad when that was an idle
|
|
0:06:01
|
but this pushed from the CUCM and of course this is only if the user
|
|
0:06:05
|
or administrator had configured a BF speed dial
|
|
0:06:10
|
on this particualr phone and this particular phone had the proper rights
|
|
0:06:15
|
which is something called to subscribe CSS,
|
|
0:06:17
|
we´ll take a look at in just a little while
|
|
0:06:20
|
another thing that can be updated simply from the CUCM,
|
|
0:06:25
|
is call history list, so if we hit our directories button
|
|
0:06:30
|
and we go in to missed calls, placed calls or received calls
|
|
0:06:35
|
and we see that we have missed, placed or received calls
|
|
0:06:39
|
for a user that is internal to our directory
|
|
0:06:43
|
that is they have a dn that is existing on our internal numbering plan.
|
|
0:06:51
|
And if we enabled it which this is not enabled by default,
|
|
0:06:55
|
BLF for call history list is something that we have to enable
|
|
0:06:59
|
enterprise parameters, not service parameters but enterprise parameters.
|
|
0:07:04
|
and if we´ve enabled it and we´ve restarted the
|
|
0:07:08
|
call manager service I believe is required after we enable that.
|
|
0:07:13
|
It will tell you if it is on the particular version you´re working with
|
|
0:07:19
|
After we´ve enabled that, then we also have to and
|
|
0:07:22
|
we´ll talk a little bit more about this and show it in the demo
|
|
0:07:25
|
but we also have to set up what are called Presence groups.
|
|
0:07:28
|
So in order for BLF speed dial to work, all we need is
|
|
0:07:32
|
a subscribe CSS on the watcher phone that can see
|
|
0:07:37
|
the dn or that contains the dn of
|
|
0:07:41
|
the dn that we´re trying to watch contains the partition, I should say
|
|
0:07:44
|
rather of the dn that we are attempting to watch with our BLF speed dial.
|
|
0:07:49
|
That´s all we need is that subscribed CSS, for BLF call history to work
|
|
0:07:54
|
we need Presence groups to work as well as the subscribed CSS.
|
|
0:08:00
|
So we´ll talk a little bit more about Presence groups, as we go along.
|
|
0:08:05
|
Aside from just the BLF speed dials and the BLF call history list,
|
|
0:08:12
|
we do have to ability that publish that information status
|
|
0:08:15
|
to the CUP server, the Presence server and this gives us
|
|
0:08:19
|
multiple clients as well as inter domain
|
|
0:08:24
|
cluster or inter cluster federations or Presence information between
|
|
0:08:32
|
clusters as well as, so the clients that it gives us
|
|
0:08:35
|
are the IP phone messenger, as we see an example of display.
|
|
0:08:40
|
This is an xml IP phone service that we configure on CUCM
|
|
0:08:45
|
and subscribe the individual phones to this IP phone service.
|
|
0:08:52
|
However, the service itself point the url for this
|
|
0:08:57
|
xml service that we create points to the CUP server.
|
|
0:09:01
|
So we configured on the CUCM, we pushed it out to the phone
|
|
0:09:04
|
when they press services and choose the IP phone messenger service
|
|
0:09:07
|
that directs a web request towards the CUP server
|
|
0:09:11
|
and then the CUP server is responsible for providing that functionality
|
|
0:09:15
|
of course if it´s configured properly and this does use
|
|
0:09:18
|
CTI or Computer Telefany Integration so there is actually 2 different
|
|
0:09:24
|
CTI integrations between CUPS and CUCM.
|
|
0:09:28
|
One is for the IP phone messenger so that it can control
|
|
0:09:33
|
so that the CUPS server can tell the CUCM
|
|
0:09:36
|
to push a message such as an instant message
|
|
0:09:40
|
or a status change out to an individual phone.
|
|
0:09:45
|
and then we also have the personal communicator up here, so this is the CUPC
|
|
0:09:50
|
CUPC or CUP C, The Cisco Unified Personal Communicator.
|
|
0:09:55
|
In this case, we´re looking at the 8.5 client
|
|
0:09:59
|
and we see an example, we´ll take a look more on the demo
|
|
0:10:02
|
both at the 7.X client first and then
|
|
0:10:08
|
we´ll take a look at the changes in 8 and look at the 8.X client
|
|
0:10:14
|
but we have the Unified Personal Communicator, if we have a
|
|
0:10:18
|
VTA advantage camera or if the phone that we happened to be controlling
|
|
0:10:24
|
happens to be a phone with a camera like a 9971 with a
|
|
0:10:29
|
CP can added or an 8941 or 45 with the built in.
|
|
0:10:35
|
We have the ability to control our,
|
|
0:10:41
|
really we have 2 functions wtih the CUPC
|
|
0:10:44
|
we have the ability to control our hardware phone and that´s the
|
|
0:10:47
|
second CTI integration between CUPS
|
|
0:10:50
|
and CUCM, it´s called desk phone control.
|
|
0:10:53
|
So there´s another CTI control here, so that
|
|
0:10:56
|
the personal communicator talking to the CUPS server
|
|
0:11:00
|
and tell the CUCM to control the individual phone
|
|
0:11:04
|
that this Personal Communicator is using.
|
|
0:11:07
|
In the 7.X client, there was a little button up here at the top right
|
|
0:11:11
|
that we would select and we´ll take a look at that in the demo
|
|
0:11:14
|
to choose between soft phone or desk phone mode.
|
|
0:11:18
|
in the 8.0 and 8.5 client and beyond, we´ve got
|
|
0:11:23
|
a little tick box down here that says use my Cisco
|
|
0:11:26
|
In this case, Cisco 7961 for audio
|
|
0:11:30
|
and we can choose whether to use
|
|
0:11:36
|
this phone as desk phone control by ticking that box.
|
|
0:11:41
|
So when we tick that all of a sudden, we go from soft phone mode
|
|
0:11:45
|
to desk phone mode and desk phone mode a personal communicator is
|
|
0:11:49
|
communicating through XMPP if it´s the version 8 client.
|
|
0:11:54
|
back to the CUPS server, it´s communicating through SIP and simple
|
|
0:11:58
|
back to the CUPS server if it´s a version 7 client.
|
|
0:12:02
|
And CUPS through CTI is telling the CUCM to control
|
|
0:12:06
|
a hardware phone, to go off hook, to make calls, etcetera.
|
|
0:12:11
|
If we are not in desk phone control mode,
|
|
0:12:15
|
so I don´t have this tick box tick because I don´t hearing this
|
|
0:12:18
|
screen shot that I tookthen we´re in soft phone mode
|
|
0:12:23
|
which means that the audio and or video if it´s a video call
|
|
0:12:27
|
are coming to the desktop to the laptop to the
|
|
0:12:31
|
desktop computer whatever it is that I happen to be running this on
|
|
0:12:36
|
In desk phone control there is no RTP media, there is only control media
|
|
0:12:41
|
sent from the laptop or dekstop, PC or Mac.
|
|
0:12:46
|
In softphone I have not only controlled but the audio
|
|
0:12:50
|
and or video is coming to the desktop
|
|
0:12:53
|
and so if I´m in soft phone mode, I have to have a VTA advantage camera
|
|
0:12:58
|
or applicable third party camera if I want any sort of video
|
|
0:13:03
|
to come here, it´s not going to work to the phone
|
|
0:13:06
|
but both of these the CUPC and the IP phone messenger require the CUP sever
|
|
0:13:17
|
So looking at the CUCM Presence components, we have the BLF speed dials.
|
|
0:13:22
|
The call history list for BLF, as I mentioned enable enterprise parameters
|
|
0:13:27
|
I mentioned the subscribed CSS this is on the watcher phone.
|
|
0:13:31
|
This is just another Calling Search Space that you would set up,
|
|
0:13:35
|
it´s not really use for calling in any way.
|
|
0:13:38
|
This is where I´ve said I think at some point, Cisco maybe
|
|
0:13:43
|
might rename CSS from Calling Search Space because
|
|
0:13:47
|
our CSSs and partitions have gone well beyond their original intended use
|
|
0:13:52
|
of being used for calling, paritioning for calling
|
|
0:13:58
|
and now they´re just use as search spaces
|
|
0:14:00
|
which is what Unity Connection calls them
|
|
0:14:03
|
search spaces to find partitions for various things, in this case
|
|
0:14:08
|
I might have a callin search space on my phone
|
|
0:14:11
|
that allows me to call, let´s say 1001
|
|
0:14:16
|
but I might have a subscribed CSS, that´s a different
|
|
0:14:20
|
CSS and it does not contain the partition
|
|
0:14:24
|
for 1001 and so therefore I can call 1001, but I can not see
|
|
0:14:29
|
1001 even if I or at least I can´t see any of their status
|
|
0:14:33
|
and changes even if I configure them as a BLF speed dial on my phone.
|
|
0:14:39
|
That button will still work as a speed dial, but it will not work
|
|
0:14:45
|
in terms of updating me to state changes of their dn.
|
|
0:14:50
|
Of course, if I have a subscribed CSS that does contain the partition
|
|
0:14:53
|
of the dn I´m trying to watch, then I will see state changes.
|
|
0:14:58
|
And again you do not Presence groups or there is a standard Presence group.
|
|
0:15:03
|
I guess I should say it doesn´t matter what Presence
|
|
0:15:06
|
groups you have configured on your phone in order for
|
|
0:15:11
|
the simple BLF speed dials to work. You can have the Presence group.
|
|
0:15:15
|
The watch dn could have a Presence group
|
|
0:15:18
|
and there is a disallow subscription between those
|
|
0:15:21
|
You would still be able to see the state change,
|
|
0:15:24
|
but just on the BLF speed dial.
|
|
0:15:29
|
So looking at Presence groups, this is needed for BLF
|
|
0:15:33
|
call history list and for CUPS applications.
|
|
0:15:37
|
So CUPC or IP phone messenger or even third party
|
|
0:15:42
|
web applications or something else interfacing with CUPS, to be able to see
|
|
0:15:46
|
the Presence or status associated with lines.
|
|
0:15:49
|
There is one standard Presence group to begin with.
|
|
0:15:52
|
You can add more Presence groups, the default
|
|
0:15:56
|
system default is of course in service parameters
|
|
0:15:59
|
and it states to disallow subscription between any newly created
|
|
0:16:04
|
Presence groups if we don´t otherwise specify and allow subscription.
|
|
0:16:12
|
And these are not 2-way subscription, so if I have
|
|
0:16:16
|
Presence group A and Presence group B and Presence group A
|
|
0:16:21
|
as explicitly configured to allow subscription to Presence group B
|
|
0:16:26
|
then the users in or the phones in Presence group A
|
|
0:16:30
|
will when they go to look at their, let´s say BLF
|
|
0:16:34
|
call history list, we´ll be able to see the state changes of the phones
|
|
0:16:38
|
that have their dns in Presence group B.
|
|
0:16:42
|
But Presence group B might have a disallow subscription to Presence group A
|
|
0:16:48
|
and so this would mean that if the phones and Presence group
|
|
0:16:52
|
went to do the same thing, look at BLF
|
|
0:16:54
|
speed dial or sorry not speed dial, but BLF call history list.
|
|
0:16:58
|
Looking at dns for, dns that belong in phones
|
|
0:17:04
|
or actually dns themselves in Presence groups A
|
|
0:17:07
|
and I´ll clairfy that in a moment.
|
|
0:17:10
|
They would not be able to see them, it is a one way relationship
|
|
0:17:15
|
and if you wanted to a relationship to allow, you have to set it both sides.
|
|
0:17:20
|
So dealing with the presenced groups, the phone
|
|
0:17:25
|
is what actually contains the BLF speed dial or the
|
|
0:17:30
|
call history list and really what we´re looking at
|
|
0:17:33
|
here, just with Presence groups dealing with BLF call history list.
|
|
0:17:38
|
If we´re looking at a call history list,
|
|
0:17:40
|
we´re not looking at a call history list
|
|
0:17:41
|
from a line or from a dn, we´re looking at it from the phone.
|
|
0:17:46
|
So the reason I´m enumerating these and we´ll go in to this in the example
|
|
0:17:51
|
is that our phone devices
|
|
0:17:55
|
in CUCM the configuration have a Presence group
|
|
0:17:59
|
option to conifgure and our lines, the dns on our devices
|
|
0:18:04
|
also have a Presence group and these two
|
|
0:18:07
|
places that we can configure the Presence group are
|
|
0:18:10
|
an important distinction to make. The Presence group that I configure
|
|
0:18:13
|
on my phone deals with me being able to be a watcher
|
|
0:18:20
|
or BLF call history list.
|
|
0:18:23
|
The Presence group on a dn or a line deals with my
|
|
0:18:30
|
being a watchee, a presentity, the person that is being watched.
|
|
0:18:35
|
So the dn is what is watched, so the Presence group there if
|
|
0:18:39
|
let´s say phone A wants to watch dn B on phone B.
|
|
0:18:46
|
then phone A needs to have a Presence group on the device, on the phone
|
|
0:18:51
|
that has allow subscription to whatever Presence group is on
|
|
0:18:56
|
phone B´s dn, so really not on the phone B itself, but ont the dn, the line
|
|
0:19:03
|
on that phone. OK, really doesn´t matter what
|
|
0:19:07
|
Presence group is on the phone B, it just matters what´s on the dn B.
|
|
0:19:14
|
And one other thing that´s important to note is that if to
|
|
0:19:20
|
entities, so let´s say a phone and a dn or in the same Presence group
|
|
0:19:25
|
there is an implicit and non configurable allow.
|
|
0:19:28
|
So if you´re in the same Presence group
|
|
0:19:32
|
at my phone as another dn, I will be able to watch that dn.
|
|
0:19:36
|
If I want to separate that in any way, I need to put that
|
|
0:19:40
|
other dn in another Presence group, dealing with BLF call history list.
|
|
0:19:52
|
So this is kind of going over some of the things I´ve already said
|
|
0:19:55
|
the BLF speed dial presence status, the only thing that´s
|
|
0:19:57
|
necessary is that a watcher has a subscribed CSS
|
|
0:20:00
|
that contains the presentity dns partition, we already said that.
|
|
0:20:04
|
We talked about the BLF call history list, I do want to bring
|
|
0:20:07
|
up one point on the slide which is that there is an exception
|
|
0:20:12
|
to the BLF call history list that
|
|
0:20:17
|
if a watcher on their phone device
|
|
0:20:22
|
is trying to watch the presentity their dn
|
|
0:20:27
|
and the Presence groups are different and the watcher
|
|
0:20:32
|
their phone device Presence group has a disallow
|
|
0:20:34
|
subscription to the presentities, dn Presence group
|
|
0:20:39
|
that would normally result in not being able to see the
|
|
0:20:45
|
the dn status change in the BLF call history list. However,
|
|
0:20:51
|
if that presentity has a shared line with a remote destination profile
|
|
0:20:57
|
so that is to say mobile connect, single number reach,
|
|
0:20:59
|
however, you want to call that then they will
|
|
0:21:02
|
also be able to watch that BLF call history list
|
|
0:21:06
|
is regardless of the inter presence subscribed policy.
|
|
0:21:10
|
OK, you do still have to have the subscribed CSS but
|
|
0:21:14
|
if that presentity has a single number reach
|
|
0:21:18
|
associated so therefore inherently has a shared line.
|
|
0:21:21
|
And they could have a shared line on their phone
|
|
0:21:26
|
but that´s not the dn that we´re trying to watch, in that case that
|
|
0:21:29
|
everything´s out the door because again we watch her dn.
|
|
0:21:33
|
Not per device, not all the dns on a device, it´s per dn
|
|
0:21:37
|
but if the dn that we´re trying to watch is a shared line with a
|
|
0:21:43
|
mobile connect single number reach, remote destination profile
|
|
0:21:47
|
then the inter presence subscribed policy will be out the window.
|
|
0:21:55
|
So looking at the Unified Presence server now, CUPS.
|
|
0:21:59
|
There´s a detailed process to perform the integration between the two.
|
|
0:22:03
|
It´s not very diffult, in fact it can go rather quickly once you
|
|
0:22:08
|
gone through the steps a few times and of course there is a check list.
|
|
0:22:13
|
So that you´re sure not to miss anything out on Cisco´s website
|
|
0:22:18
|
on their configuration documentation.
|
|
0:22:22
|
So use that installationg uide when you´re practicing this
|
|
0:22:25
|
in order to get more familiar to ensure that you cover each task
|
|
0:22:29
|
and do so in the correct order, sometimes the order matters
|
|
0:22:34
|
it really doesn´t matter the order too much except to save it.
|
|
0:22:37
|
Some things you can´t do until you´ve done other things for instance you.
|
|
0:22:41
|
You can´t configure or assign the CUPS published trunk in the CUPS server
|
|
0:22:47
|
until you´ve actually created it in CUCM, but follow that guide.
|
|
0:22:51
|
It´s not a difficult process, it´s actually quite quick and it´s the same
|
|
0:22:55
|
task everytime, do you´ll become very familiar with it.
|
|
0:23:00
|
Most common scenarios with CUPS server or CUPS server
|
|
0:23:05
|
involved CUPS, soft phone or desk phone control
|
|
0:23:11
|
and voicemail integration as well as the IP phone messenger
|
|
0:23:16
|
So the instant messenging client and calendaring scheduling client that goes
|
|
0:23:21
|
as an IP phone service on the individual phones.
|
|
0:23:25
|
Now there is other things that we can do to integrate CUPC with calendaring
|
|
0:23:32
|
if we have a meeting place server with conferencing
|
|
0:23:36
|
if we have either meeting place, meeting place express and or web ex
|
|
0:23:43
|
as well as a number of other things but most of the time
|
|
0:23:49
|
what we do, you know in terms of inter cluster
|
|
0:23:53
|
status between clusters and things like that and LDAP
|
|
0:23:56
|
we´ll certainly take a look at that, actually
|
|
0:24:00
|
the first example that we´re going to take a look at, I believe
|
|
0:24:04
|
I have set up without, we´re taking a look at 7.X client
|
|
0:24:09
|
integrating and by the way, although we´ll take a look at the 7.X
|
|
0:24:13
|
client integarting with the 7.0 server which isn´t
|
|
0:24:16
|
too very different from the 8. We will look at the 8 server as well
|
|
0:24:21
|
but it should be noted that the reason that we are including that
|
|
0:24:26
|
is that while the 7.0 CUPC, the Cisco Unified Personal Communicator client
|
|
0:24:33
|
can integrate with of course a 7.0 CUP server
|
|
0:24:37
|
a 7.0 CUPC client can also integrate with an 8.0 or 8.5 server
|
|
0:24:44
|
or beyond so it´s important to note that and note some of the
|
|
0:24:49
|
differences there especially if you´re ask any questions about them
|
|
0:24:54
|
but in the first demo that we´ll look at with the 7.0 client.
|
|
0:24:57
|
I don´t believe we rely on LDAP or integrate that too much
|
|
0:25:01
|
when we look at the changes and differences in the
|
|
0:25:05
|
CUPS 8.5 server as well as the 8.5
|
|
0:25:10
|
CUP client or personal communicator slient then
|
|
0:25:16
|
we will take a look at an LDAP integration and for real world
|
|
0:25:20
|
implementations, CUPS really does not
|
|
0:25:23
|
do much of anything without an LDAP server, OK. So it´s
|
|
0:25:27
|
it´s actually quite crucial to gain any and really
|
|
0:25:32
|
all of the functionality that it can provide to have it integrated
|
|
0:25:35
|
with an LDAP server and of course you wouldn´t any major environment
|
|
0:25:42
|
as mentioned here, it´s important to note that each of these
|
|
0:25:46
|
soft phone, desk phone, voicemail control
|
|
0:25:49
|
with CUPS requires dependency on servers other than CUPS
|
|
0:25:52
|
and really they depend on the CUCM server.
|
|
0:25:58
|
As well as voicemail depends on enabling IMAP
|
|
0:26:02
|
in the Unity Connection sever under the class of service
|
|
0:26:07
|
or whatever users you want to, allow access to
|
|
0:26:12
|
their voicemail through CUPC, so CUPC can not only show you
|
|
0:26:17
|
just a standard, kind of rudimentary message waiting indicator
|
|
0:26:22
|
like a light, but it can show you how many messages, you
|
|
0:26:24
|
can access those messages, play them back, etcetera.
|
|
0:26:27
|
Have a lot of full functionality delete them from the CUPC client
|
|
0:26:31
|
but it does all that through IMAP integration with
|
|
0:26:35
|
Unity Connection, so you to first enable that. It´s not enabled by default.
|
|
0:26:40
|
Also what´s important to note right up front and we´ll take a look
|
|
0:26:43
|
at it in the actual demonstration that when we´re
|
|
0:26:48
|
taking and integrating or provisioning a soft phone
|
|
0:26:55
|
if we´re just doing desk phone control that resides in CUPS
|
|
0:26:58
|
and really there´s not too much that we need to do in CUCM
|
|
0:27:01
|
there´s a little bit we need to tell the phone
|
|
0:27:03
|
and the user associated with the phone that they have CTI control
|
|
0:27:07
|
and we´ll take a look at that, but if we´re
|
|
0:27:11
|
wanting to use the CUPC client and soft phone mode as well
|
|
0:27:15
|
and most of the time, you provision, I would say 99% of the time and
|
|
0:27:20
|
normal environement to provision both.
|
|
0:27:24
|
If we´re provisiong soft phone mode, we actually create
|
|
0:27:27
|
an instance or another instance of a phone with the shared line in CUCM.
|
|
0:27:32
|
And the important distinction is if we´re provisioning a CUPC 7.X client
|
|
0:27:40
|
regardless of what server it´s integrating with,
|
|
0:27:43
|
whether it´s integrating with a 7.0 or an 8.0 server.
|
|
0:27:47
|
We provision it as just what it says Cisco Unified Personal Communicator
|
|
0:27:53
|
when we click add phone that´s the type that we add.
|
|
0:27:56
|
If we´re provisioning an 8.0 CUPC client
|
|
0:28:00
|
We provision it not as a Cisco Unified Perosnal Communicator but
|
|
0:28:04
|
instead as a Cisco Unified Services Framework client.
|
|
0:28:08
|
OK and we´ll take a look at both of those as we do the demo.
|
|
0:28:14
|
So just a brief rundown of some of the things in the checklist that we need
|
|
0:28:18
|
to do on CUCM and then on the CUP server.
|
|
0:28:22
|
On CUCM we need to make sure that users have
|
|
0:28:26
|
the devices that the´re going to be associated with
|
|
0:28:30
|
but they actually have that device association in the end user
|
|
0:28:35
|
configuration window. They also need to have standard CTI enabled
|
|
0:28:41
|
and it´s a good idea to have CUCM standard end user
|
|
0:28:45
|
enabled as a group or role, really as a group that adds the roles.
|
|
0:28:50
|
It´s also important to note that if you´re running on the newer
|
|
0:28:54
|
6691 phone or I´m sorry the 6900 series phones
|
|
0:29:01
|
Then you need to have an additional CTI
|
|
0:29:08
|
group that you subscribed to and we´ll go over which one that is
|
|
0:29:12
|
and if you are a 8900 or 9900 series phones
|
|
0:29:18
|
there is a different CTI group that you need to have enabled.
|
|
0:29:21
|
So we´ll take a look at each of those when we look at the 8.0 client
|
|
0:29:27
|
also the user needs to have the primary extension assigned.
|
|
0:29:33
|
We need to set the owner-user ID now over on the device
|
|
0:29:37
|
It´s also important that on the line of not only the
|
|
0:29:41
|
phone that´s going to use CUPC, but any phones that wish to be
|
|
0:29:46
|
in a watch so as a presentity status that they have the
|
|
0:29:54
|
user associated to the line as well, this is just for CUPS.
|
|
0:29:59
|
So it really doesn´t matter whether that user has a
|
|
0:30:02
|
CUPC client assign, but if I wish to watch
|
|
0:30:08
|
all 500 of my employees at different times through my CUPC.
|
|
0:30:11
|
It´s important that all 500 employees, all of their dn s
|
|
0:30:15
|
are associated with their user ID.
|
|
0:30:22
|
and of course that they ahve the licensing for CUP
|
|
0:30:25
|
or the CUPS server, not necessarily for CUP and CUPC
|
|
0:30:29
|
only the people with CUPC client actually need
|
|
0:30:32
|
the license capability for CUP and CUPC.
|
|
0:30:36
|
We´ll also have the application user for CTI gateway this is what
|
|
0:30:40
|
that will allow desk phone control mode and that will have a lousy
|
|
0:30:44
|
CTI control of all devices, we will build a SIP trunk
|
|
0:30:48
|
pointing to the IP address or fully qualified domain name
|
|
0:30:51
|
if we´re using dns of the CUP server.
|
|
0:30:55
|
And this CUP publish trunk will be set under the CUCM
|
|
0:30:59
|
or CUCM service paramaters. I mentioned briefly licensed
|
|
0:31:04
|
capabilities, we need to do this for CUP´s users again.
|
|
0:31:08
|
Any users that are going to be watched
|
|
0:31:10
|
by the CUPS server, need to have at least the CUP license.
|
|
0:31:14
|
and then taking more dl use would be the CUPC
|
|
0:31:19
|
as well as the cup license capabilities, so those are two
|
|
0:31:22
|
incremental license capabilities that we can enable per user.
|
|
0:31:28
|
The soft phone for soft phone mode for CUPC requires the new device.
|
|
0:31:34
|
We already talked about 7.0 clients gets Cisco Unified Personal
|
|
0:31:37
|
Communicator new device type 8.0 gets Cisco Unified
|
|
0:31:43
|
Client Services Framework or CSF device type.
|
|
0:31:47
|
The device name always must be UPC
|
|
0:31:53
|
and then the user ID and so there´s some restrictions from these so
|
|
0:31:59
|
this is if we´re creating a soft phone
|
|
0:32:01
|
and this is the same whether we´re creating the 8.0 CSF
|
|
0:32:05
|
of client or the 7.0 CUPC client.
|
|
0:32:10
|
All of the letters in the naming convention have
|
|
0:32:13
|
to be capitalized, by the way this the same for mobile communicator.
|
|
0:32:18
|
If the, so it´s always UPC for Unified Personal Communicator
|
|
0:32:26
|
and then the user ID and after UPC, there can only be 12 characters
|
|
0:32:35
|
and they can only be letters or number so a user ID
|
|
0:32:40
|
could that is to say that the CUCM user ID that we create
|
|
0:32:46
|
in CUCM end user could have been called, let´s say
|
|
0:32:52
|
JJ Abrams, but it could have been JJ_Abrams for instance.
|
|
0:32:58
|
OK, if that were the case, the way we would provision the CUPC
|
|
0:33:02
|
client is to say UPC JJ ABRAMS all caps, all capital, but no
|
|
0:33:10
|
dash or underscore, whatever had been used to hyphenate his name.
|
|
0:33:15
|
If there was a number in his name, that´s fine.
|
|
0:33:19
|
Numbers and letters are fine, but we omit, we simply sandwich together
|
|
0:33:25
|
any hyphenation or underscore or any other
|
|
0:33:29
|
character other than alpha numeric and again
|
|
0:33:33
|
12 characters max after UPC. So if it was JJABRAMS,
|
|
0:33:41
|
I don´t know, let´s say JJABRAM son or something like
|
|
0:33:47
|
that, you know something long, we would trunkate the name
|
|
0:33:51
|
after 12 characters, but not 12 including
|
|
0:33:53
|
UPC 12 after the UPC, just want to make that perfectly clear.
|
|
0:33:58
|
And then we also have to define the application server
|
|
0:34:01
|
which is the actual CUPS server and all of this has been done in CUCM.
|
|
0:34:07
|
So on the CUP server, we need to create inbound outbound access list.
|
|
0:34:13
|
Now this will actually, already have been done, once we
|
|
0:34:15
|
acivate the necessary services in the CUPS
|
|
0:34:20
|
Unified Service ability window and once we´ve provisioned
|
|
0:34:25
|
the integration between CUCM and the CUP server
|
|
0:34:29
|
and once you go through that. If you´re doing a new installed
|
|
0:34:33
|
and you have just fired up the dvd
|
|
0:34:38
|
and run the installation process to install CUPS.
|
|
0:34:42
|
There´s a quick 3 page wizard that just asks you for the
|
|
0:34:47
|
the host name and IP address of the CUCM publisher,
|
|
0:34:52
|
the secret password and then
|
|
0:34:57
|
the secret cluster password and then also the axl
|
|
0:35:02
|
username and password for the CUCM cluster.
|
|
0:35:06
|
And all of this, what this actually does is this makes
|
|
0:35:08
|
the CUPS server, one of the new subscribers
|
|
0:35:12
|
not a call processing engine subscriber, but just a database subscriber.
|
|
0:35:16
|
to that CUCM cluster and there is actually then one way database replication
|
|
0:35:22
|
from the publisher on the CUCM side to that CUPS server
|
|
0:35:27
|
just like there is from the publisher to all the other
|
|
0:35:29
|
subscribers servers in the CUCM cluster.
|
|
0:35:33
|
So any CUCM server that were apart
|
|
0:35:39
|
of that cluster, they would automatically have
|
|
0:35:43
|
access control inbound and access control list outbound entries added
|
|
0:35:47
|
in the CUP server, so there´s no need or shouldn´t be any need
|
|
0:35:50
|
to manually add those if you don´t see them
|
|
0:35:53
|
then you´ve likely missed some sort of the step
|
|
0:35:56
|
either the integration or the gateway.
|
|
0:36:00
|
This step here, where we say add CUCM or CUCM as a
|
|
0:36:04
|
gateway and only the publisher is allowed to be.
|
|
0:36:08
|
Once we´ve done that and once we´ve activated the services
|
|
0:36:13
|
in the CUP server, then we should see those access control list show up
|
|
0:36:17
|
as well as we should see something called CTI
|
|
0:36:20
|
gateways and CTI profiles that we´ll look at in the demonstration
|
|
0:36:25
|
we should see those automaticall show up,
|
|
0:36:27
|
they´re should be no need to create those manually.
|
|
0:36:31
|
the only things that we might need to add to the inbound
|
|
0:36:34
|
outbound access list are other third party server, so if we are
|
|
0:36:38
|
If we have some sort of an inter cluster
|
|
0:36:42
|
federation or an inter domain federation
|
|
0:36:46
|
possibly with another CUPS cluster
|
|
0:36:50
|
and subsequently CUCM cluster or possibly with a Microsoft
|
|
0:36:55
|
OCS, LCS / the newer you know Microsoft link
|
|
0:37:00
|
type presence integration or
|
|
0:37:04
|
inter domain federation is what we would set up there, we would add those
|
|
0:37:08
|
servers also Unity Connection any in all Unity Connection server
|
|
0:37:13
|
what we will have imap connections to for our users.
|
|
0:37:16
|
those will need to be added, what do not need to be added
|
|
0:37:19
|
at anytime are the IP addresses
|
|
0:37:25
|
for all the CUPC clients now we´ll show you how you certainly
|
|
0:37:30
|
could do that within access control list defined as
|
|
0:37:34
|
capital ALL, which is pretty much like a permit IP any any
|
|
0:37:39
|
but that´s really not the way that we would ever set this up
|
|
0:37:44
|
in real life, it´s just one way that we could do it
|
|
0:37:48
|
for both inbound and outbound the way that we would do it
|
|
0:37:50
|
to authenticate those users or those CUPC clients
|
|
0:37:54
|
is simply not only to have a password in their end user configuration
|
|
0:37:57
|
but also to have configured digest credentials.
|
|
0:38:04
|
Then we want to make sure that we enter the domain
|
|
0:38:06
|
under the service parameters for Cisco SIP proxy.
|
|
0:38:12
|
So this in the CUPS or a CUPS server
|
|
0:38:16
|
service parameters specifically not for
|
|
0:38:21
|
presence but not for the presence engine service but for the proxy
|
|
0:38:26
|
service. Now the domain name will actually already be set
|
|
0:38:30
|
if upon installation which is fairly typical in larger installations
|
|
0:38:36
|
if initial, when you did the initial set up, the initial
|
|
0:38:43
|
spinning of the dvd to install, you had told that domain name
|
|
0:38:48
|
or used dns, yes and set a domain name, this will already be set there
|
|
0:38:53
|
then we´ll configure our CUPC settings
|
|
0:38:56
|
which involves soft phone, desk phone, LDAP.
|
|
0:39:00
|
Potentially, if you have a meeting place or web X server
|
|
0:39:03
|
conferencing or calendaring as well as voicemail integration
|
|
0:39:08
|
and we´ll enable the access on Unity Connection.
|
|
0:39:12
|
So Unified Personal Communicator, client does run
|
|
0:39:16
|
on windows it also runs on
|
|
0:39:21
|
mac as well, there´s a mac client. You should certainly complete the entire
|
|
0:39:26
|
integration between CUPS in CUCM before attempting to try to launch it.
|
|
0:39:32
|
When you do login with the host name or
|
|
0:39:35
|
fully qualified domain name of the CUPS server
|
|
0:39:38
|
just depending on your particular
|
|
0:39:42
|
host so of the operating system that you´re working on has
|
|
0:39:47
|
in its network card configuration, if it´s already set
|
|
0:39:51
|
to apend a certain domain name like
|
|
0:39:53
|
.ine.com or ine.com, then you
|
|
0:39:58
|
if the CUPS server is on the same domain,
|
|
0:39:59
|
then you could just go ahead and login with the host name
|
|
0:40:02
|
but of course your client has to be pointing to dns,
|
|
0:40:05
|
if not you can always set up a manual host file on both windows and mac
|
|
0:40:12
|
login with the username and password of the user from CUCM
|
|
0:40:17
|
and the user database will be pushed from CUCM down to
|
|
0:40:22
|
the CUPS server regardless of whether the user database was
|
|
0:40:26
|
originally and solely native to CUCM
|
|
0:40:29
|
or whether the CUCM can actually synchronize the users
|
|
0:40:32
|
or at least parts of the users from a common LDAP.
|
|
0:40:38
|
You check both the soft phone and desk phone mode and it´s
|
|
0:40:41
|
always a good idea when you´re first setting up CUPS
|
|
0:40:44
|
to make sure that you on the CUPC client
|
|
0:40:47
|
in your Windows 7 or Mac operating system
|
|
0:40:51
|
that you go up to help and show server health
|
|
0:40:55
|
to check for any issues and really just to check that everything is good
|
|
0:40:58
|
and if it´s not good then it will give you a lot of information.
|
|
0:41:01
|
Not a helpful information on what might be wrong for troubleshooting
|
|
0:41:06
|
and then the other thing that you´ll do is once you open your CUPC client,
|
|
0:41:10
|
you will go up to file options and the second one down will be accounts
|
|
0:41:17
|
and there are 2 accounts that you´ll set up there
|
|
0:41:19
|
one is your voicemail username and password
|
|
0:41:22
|
and one is your LDAP username and password.
|
|
0:41:25
|
And most likely with LDAP synchronize across everything
|
|
0:41:28
|
these will be the same user, pass
|
|
0:41:32
|
for each other as well as the same username and password
|
|
0:41:35
|
that you used to login to CUPC.
|
|
0:41:39
|
And finally, we can enable presenceon CUCME
|
|
0:41:45
|
Communication Manager Express, the configuration is very simple.
|
|
0:41:53
|
We simply in global config modes say SIP UA
|
|
0:41:56
|
and under that we say Presence enable.
|
|
0:41:59
|
Go back out to global config, if we want to enable BLF
|
|
0:42:03
|
for call history list, so this will do BLF speed dial,
|
|
0:42:07
|
but if we want to call history list, we say Presence
|
|
0:42:10
|
and then under that Presence call list.
|
|
0:42:13
|
And then for each of our ephone dns, we have two here.
|
|
0:42:17
|
We say allow watch, so that allows me to be a presentity
|
|
0:42:22
|
and then under the ephone, I of course have my normal button mapping
|
|
0:42:26
|
button 1 map to dn 1 and here button 1 map to dn 2.
|
|
0:42:32
|
And then let´s say the 6th line button, I want to
|
|
0:42:36
|
first of all there´s an M for monitor, but that doesn´t give you full
|
|
0:42:40
|
presence funcitonality or full status funtionallity.
|
|
0:42:42
|
The better one is W for watch, so 6 watch
|
|
0:42:46
|
so my 6th line button is watching dn 2.
|
|
0:42:50
|
And over here on ephone 2, my 6th line is watching ephone dn tag 1.
|
|
0:42:56
|
|
