|
0:00:15
|
OK. So let's take a look at the some practical differences
|
|
0:00:18
|
and there aren't too many in our presence server and presence client
|
|
0:00:22
|
in the 8.0 versions or 8.5 versions.
|
|
0:00:26
|
And the first thing actually, we're gonna look at the CUCM,
|
|
0:00:29
|
the only thing really that's changed here from the 7.0 or
|
|
0:00:32
|
or 7.x series in terms of what we need to do
|
|
0:00:35
|
different is on the device and the phone, we've already mentioned this earlier
|
|
0:00:42
|
but when we create a unified personal communicator,
|
|
0:00:46
|
if we're creating a 7.0 client to integrate with
|
|
0:00:51
|
the 8.0 or 8.5 server, then we still create
|
|
0:00:57
|
the type of Cisco Unified Personal Communicator.
|
|
0:01:00
|
If we're creating a soft phone on CUCM for
|
|
0:01:05
|
a client that's gonna be using the 8.0 or 8.5,
|
|
0:01:12
|
Unified Personal Communicator and it's still called and downloaded from
|
|
0:01:15
|
CCO as the Cisco Unified Personal Communicator
|
|
0:01:18
|
8.X but when we set it up on CUCM, we need to set it up at
|
|
0:01:22
|
this the Cisco Unified Client Services Framework or CSF.
|
|
0:01:29
|
So going back to our find, we have created this
|
|
0:01:33
|
we noticed the little different icon there and if we hover
|
|
0:01:35
|
the mouse over, we see the Cisco Unified Client Services Framework pop up,
|
|
0:01:40
|
but we've created this UPC, the naming is still the same
|
|
0:01:44
|
for Hurley or Hugo and we've switched Hugo over to an 8.5 client,
|
|
0:01:50
|
pretty much everything else is still the same.
|
|
0:01:54
|
You know other than the fact that the security profile
|
|
0:01:57
|
represents the naming difference because there's a
|
|
0:02:01
|
you know security profile for each different type of device,
|
|
0:02:04
|
other than that everything else is the same. the line is the same,
|
|
0:02:07
|
it's just the type of device that we happen to use.
|
|
0:02:10
|
That's the only thing different really in CUCM
|
|
0:02:14
|
that we need to change, over on presence server,
|
|
0:02:18
|
the first thing we'll take a look at, nothing really has changed
|
|
0:02:21
|
in terms of the service parameters or cluster topology,
|
|
0:02:25
|
how we integrated with CUCM, but we'll look at presence settings,
|
|
0:02:31
|
the gateway is still the same.
|
|
0:02:37
|
On presence settings, notice it looks a little different here,
|
|
0:02:41
|
first of all we talked about availability sharing,
|
|
0:02:46
|
sorry I disabled that, so it's telling me to restart the XCP router
|
|
0:02:50
|
so there are new services because 8.0 introduced
|
|
0:02:54
|
the Jabber protocol when Cisco acquired Jabber.
|
|
0:02:57
|
And of course the 8.0 CUPC client
|
|
0:03:02
|
uses Jabber and XMPP, the Extensible Messaging Presence Protocol,
|
|
0:03:08
|
rather than SIP or Simple. When 8.5 servers talking to
|
|
0:03:12
|
the 7.0 client which it can simultaneously have along with 8.0 clients,
|
|
0:03:18
|
it uses still the SIP and Simple protocols,
|
|
0:03:22
|
but we can change availability sharing.
|
|
0:03:27
|
We also can enable the use of email address
|
|
0:03:32
|
look ups when federating with other domains either with a
|
|
0:03:37
|
Microsoft OCS or link server or possibly another CUPS
|
|
0:03:42
|
we also the have the ability to use DND status when the user is on the
|
|
0:03:46
|
phone or in a meeting, so by default,
|
|
0:03:48
|
when a user's on a phone or in a meeting they
|
|
0:03:51
|
show a busy status, if we click this, it's system wide
|
|
0:03:56
|
and it, for all future calls, not currently active calls this
|
|
0:04:03
|
shows a do not disturb rather than a busy.
|
|
0:04:09
|
I also have maximum contact list and maximum watchers
|
|
0:04:13
|
per user, so the maximum people I'm allowed to watch,
|
|
0:04:18
|
the maximum people that are watching me per user, the maximum
|
|
0:04:21
|
contact list for my user contact list, I also have something called
|
|
0:04:25
|
adhoc presence subscriptions.
|
|
0:04:28
|
This is on by default, what this basically is
|
|
0:04:32
|
BLF for call history list in a sense or actually I should say BLF
|
|
0:04:36
|
or corporate directory in a sense. Back in CUCM
|
|
0:04:40
|
only presence, when we talked about BLF for call history list,
|
|
0:04:44
|
this actually also in CUCM when we did system enterprise parameters
|
|
0:04:51
|
and we allowed BLF for call history list,
|
|
0:04:55
|
this also enabled BLF for corporate directory
|
|
0:04:58
|
but that's just on the phone itself, here with CUPS,
|
|
0:05:02
|
we're talking about the CUPC client, the Cisco Unified Personal Communicator,
|
|
0:05:06
|
so when we do, first of all when we have contacts added,
|
|
0:05:10
|
already added to our CUPC client,
|
|
0:05:14
|
then we have a presence subscription, that is we're watching their status.
|
|
0:05:19
|
Assuming we have all the right permissions that we talked about already.
|
|
0:05:23
|
However, when we do a corporate directory look-up
|
|
0:05:27
|
we don't necessarily see status, well we actually do by default, it is enabled.
|
|
0:05:32
|
We could disable this and this would basically
|
|
0:05:37
|
when we're looking up a user in corporate directory,
|
|
0:05:40
|
basically in the LDAP from our CUPC software client,
|
|
0:05:44
|
and we'll take a look an example of doing that in just a moment,
|
|
0:05:48
|
if we disable this, then all of a sudden
|
|
0:05:51
|
we don't see the status of that user in the corporate directory
|
|
0:05:54
|
unless we add them as a contact. With this enabled, like it is by default,
|
|
0:05:59
|
then we are basically doing an adhoc subscription
|
|
0:06:03
|
and it might not become a permanent presence subscription from our client.
|
|
0:06:07
|
If we don't add that contact from the LDAP to our
|
|
0:06:11
|
contact list, in our CUPC client, then we won't have a permanent subscription.
|
|
0:06:16
|
If we do, then we will have a permanent subscription.
|
|
0:06:20
|
But with this enabled by default, then we have an adhoc temporary so this is
|
|
0:06:25
|
fairly similar to BLF for corporate directory or call history list,
|
|
0:06:29
|
but just with CUPC and then we have the SIP publish trunk
|
|
0:06:33
|
which hasn't changed from CUCM.
|
|
0:06:39
|
In the messaging section,
|
|
0:06:42
|
for settings, we have the ability to enable instant messaging of course
|
|
0:06:47
|
supress offline instant messaging, so this is not ticked by default,
|
|
0:06:52
|
if we tick this box, what this means,
|
|
0:06:56
|
excuse me, is that
|
|
0:06:59
|
basically if a user is offline or they appear to be offline,
|
|
0:07:04
|
we won't as a client be able to send messages, it will
|
|
0:07:08
|
pretty much say, like any instant message client, you know
|
|
0:07:10
|
the user appears to be offline, you could send this later,
|
|
0:07:14
|
but we're not gonna send it now.
|
|
0:07:16
|
By unticking this, it does allow us to go ahead and send that
|
|
0:07:20
|
isntant message and when the user comes back online,
|
|
0:07:22
|
they'll get that instant message.
|
|
0:07:26
|
And then we also have the ability to
|
|
0:07:28
|
tell supported clients not to be able to allow logging of their messages.
|
|
0:07:34
|
Now this gets into something dealing with
|
|
0:07:36
|
this is all dealing with instant mesaging, this gets into something
|
|
0:07:39
|
dealing with compliance so certain industries, certain verticals
|
|
0:07:44
|
don't want their messages recorded unless they have
|
|
0:07:47
|
to be by law and you know for instance the financial
|
|
0:07:51
|
industry, I don't remember what it is, I think
|
|
0:07:53
|
in the US there's a law that you must keep
|
|
0:07:57
|
voicemails I think it's dfferent for emails
|
|
0:08:00
|
and instant message and voicemails all three separate but
|
|
0:08:03
|
I think you must keep voicemails for, I don't know it's either
|
|
0:08:07
|
one year or it's 90 days or 60 days, I can't remember really which
|
|
0:08:12
|
a friend of mine that consults a lot in that industry,
|
|
0:08:16
|
was telling me about this, but they want those messages deleted
|
|
0:08:20
|
the moment that they're allowed to delete them so that there's no
|
|
0:08:23
|
incriminating evidence if there's ever you know someone in the company
|
|
0:08:26
|
that did something bad that obviously wasn't known about.
|
|
0:08:30
|
I'm not getting into the right and wrong of anything but
|
|
0:08:32
|
I'm just simply saying that there are compliance issues certain
|
|
0:08:35
|
vertical certain industries want to be able to delete or preserve,
|
|
0:08:40
|
messages as soon as or for as long as respectively
|
|
0:08:45
|
that they want, so we can set up
|
|
0:08:48
|
the ability to tell clients not to be able to log messages
|
|
0:08:51
|
so they couldn't look back in their chat history,
|
|
0:08:56
|
and we also can set up external messaging servers
|
|
0:09:00
|
third party and compliant servers that will
|
|
0:09:06
|
that will allow us to you know set whether it's not configured
|
|
0:09:11
|
just the message archiver which we have to specify a database,
|
|
0:09:15
|
or third party compliant server if we set up that,
|
|
0:09:18
|
that will go ahead and log all these messages for whatever
|
|
0:09:21
|
period of time they're configured to do so.
|
|
0:09:24
|
We also have group chat and persistent chat, so group chat
|
|
0:09:30
|
is just what it sounds like, I can have multiple people form an adhoc,
|
|
0:09:34
|
groupchat window or chatroom, persistent chat
|
|
0:09:39
|
is the same thing as group chat, but instead of adhoc so
|
|
0:09:42
|
it's created when you know two or really three users want to
|
|
0:09:48
|
begin someone wants to start a chatroom so
|
|
0:09:51
|
more than two users can enter it,
|
|
0:09:54
|
and all talk together but it's destroyed as soon as they're done,
|
|
0:09:57
|
as soon as they all exit that adhoc group chat room
|
|
0:10:02
|
if you will, persistent allows me to create a persistent
|
|
0:10:08
|
room that's always open but I do have to have a
|
|
0:10:11
|
persistent chat database so again something that I need to set up
|
|
0:10:15
|
with external databases in order to deal with that.
|
|
0:10:21
|
We don't have an external database server, adhoc groupchat is
|
|
0:10:26
|
was on by default and we'll go ahead and allo that
|
|
0:10:30
|
but we're not going to enable persistent
|
|
0:10:33
|
because we don't have an external server.
|
|
0:10:36
|
So then looking over at CUPC, nothing's changed in
|
|
0:10:40
|
deskphone control or IP phone messenger,
|
|
0:10:46
|
what we do have is a few new settings
|
|
0:10:52
|
if you take a look here, first of all voicemail
|
|
0:10:55
|
user settings hasn't really changed except for
|
|
0:10:58
|
the two new fields that we're gonna talk about.
|
|
0:11:00
|
This is just the user being assigned any or
|
|
0:11:04
|
all of these profiles that we may create
|
|
0:11:06
|
the voicemail server pointing to the IMAP server
|
|
0:11:11
|
actually pointing to the https
|
|
0:11:14
|
AXL integration to this unity connection or unity server
|
|
0:11:18
|
the mail store pointing to the IMAP
|
|
0:11:22
|
of that unity connection or unity server,
|
|
0:11:24
|
and then aggregating those two under the profile,
|
|
0:11:27
|
none of that's changed and then you assign the profile to the user,
|
|
0:11:30
|
so none of that's changed, conferencing server
|
|
0:11:34
|
I don't think we really took a look at this too much,
|
|
0:11:36
|
but again we don't have meeting place classic
|
|
0:11:40
|
meeting place express, or webx server so we're not
|
|
0:11:43
|
gonna set this up, if we did, there it is, you know name
|
|
0:11:47
|
an IP address and whether it's you know 443
|
|
0:11:52
|
SSL or port 80 http,
|
|
0:11:57
|
as well as the conferencing profile,
|
|
0:12:01
|
that aggregates that particular server and
|
|
0:12:04
|
adds users and possibly a server certificate if we're dealing with security.
|
|
0:12:10
|
CTI gateway server and profile, those haven't changed
|
|
0:12:13
|
the LDAP server and profile, they haven't changed, I don't
|
|
0:12:16
|
remember if we took a look at those, so let's just go ahead
|
|
0:12:19
|
I've already set up an LDAP host here,
|
|
0:12:22
|
and this is setting it up in very similar, well really
|
|
0:12:25
|
all the same settings that we set up in
|
|
0:12:29
|
CCM, CUCM, its just that it's doing it
|
|
0:12:33
|
a little bit differently, so really everything that we
|
|
0:12:37
|
hit set up on this LDAP directory or synchronization
|
|
0:12:41
|
agreement as it's called,
|
|
0:12:44
|
so not only the, just give it a name, but the
|
|
0:12:48
|
user and pass to authenticate a search base
|
|
0:12:53
|
what fields are mapped to what and the server IP itself,
|
|
0:12:57
|
and of course port SSL etc. all of that is
|
|
0:13:03
|
pread out in actually three separate places here, so the LDAP host
|
|
0:13:07
|
configuration just gives us the name, the IP address of the LDAP
|
|
0:13:12
|
the port and protocol, whether it's TCP, UTP
|
|
0:13:15
|
or TLS that we're contacting that LDAP host.
|
|
0:13:20
|
The LDAP profile then
|
|
0:13:24
|
aggregates or uses the host
|
|
0:13:28
|
primary and of course we can have back ups and normally would
|
|
0:13:31
|
give it a name of the profile, the user and PAS
|
|
0:13:35
|
and then to authenticate against
|
|
0:13:38
|
and then the search context and whether it's
|
|
0:13:42
|
recursive or not so in other words if it's non-recursive,
|
|
0:13:47
|
and we're searching OU Island Natural Exports,
|
|
0:13:50
|
DC INE DC COM,
|
|
0:13:51
|
we won't search anywhere below this OU.
|
|
0:13:55
|
So this is the top second level,
|
|
0:13:59
|
Island Natural exports, we won't search anywhere below this OU.
|
|
0:14:03
|
If it's recursive, we dive down into the recursive containers
|
|
0:14:09
|
organizational units.
|
|
0:14:11
|
We can either make this the default for the system which if we do,
|
|
0:14:14
|
it tells us that selecting this profile
|
|
0:14:19
|
will unselect any other previous
|
|
0:14:22
|
however it will not change the LDAP profile,
|
|
0:14:25
|
value for CUPC enabled users who are already
|
|
0:14:29
|
synced and are already associated with a particular
|
|
0:14:33
|
LDAP, so we can be more specific
|
|
0:14:35
|
with associating users to a different LDAP if we have multiples,
|
|
0:14:39
|
however this just means that we won't really have to assign each user
|
|
0:14:44
|
either here at this stage or we could
|
|
0:14:48
|
go up to user management end user and do it or in application
|
|
0:14:52
|
CUPC user settings which is where we associate
|
|
0:14:56
|
all of these information together.
|
|
0:14:59
|
So here we look for our users, grab the user that we want
|
|
0:15:04
|
and assign a voicemail profile, conferencing, CTI gateway profile,
|
|
0:15:08
|
LDAP audio which we'll talk about in CCM CIP.
|
|
0:15:17
|
And then the other place that we deal with LDAP,
|
|
0:15:20
|
specifically if we look back at the CUCM,
|
|
0:15:23
|
we covered the IP address and protocol
|
|
0:15:27
|
and then we covered the user and PAS and search space, there is
|
|
0:15:31
|
no custom filter there at this time.
|
|
0:15:34
|
But we don't have a synchronization because
|
|
0:15:39
|
we the CUP server is not synchronizing just to be clear,
|
|
0:15:43
|
the CUP server is not synchronizing users from the LDAP
|
|
0:15:48
|
that we're setting up here, notice that all of this information
|
|
0:15:51
|
is under the application for Cisco Unified Personal Communicator.
|
|
0:15:55
|
This is only LDAP information that's relevant
|
|
0:15:57
|
to the client, not to the server itself.
|
|
0:16:01
|
The server itself always pulls it's users and really
|
|
0:16:06
|
does a database subscription,
|
|
0:16:09
|
and synchronizes it's users from the publisher,
|
|
0:16:12
|
now the publish may in turn be synchronizing from the LDAP,
|
|
0:16:15
|
and that's fine, and that's really the desired
|
|
0:16:20
|
place that they should be, however
|
|
0:16:24
|
the CUP server is synchronizing from CUCM.
|
|
0:16:29
|
OK. So the LDAP
|
|
0:16:33
|
we define the server, the IP address
|
|
0:16:37
|
with the search base, but if we go back up to settings,
|
|
0:16:41
|
we saw, first of all, we've got our CUPC
|
|
0:16:46
|
I think I skipped this
|
|
0:16:48
|
the tftp server which really hasn't changed any from
|
|
0:16:52
|
7.0 we've got some new 8.0 settings,
|
|
0:16:55
|
and these only apply to the 8.0 client,
|
|
0:16:58
|
so if we have a 7.0 client, then they don't have any bearing with this,
|
|
0:17:02
|
we can have certificate directory for security
|
|
0:17:06
|
authenticaton credentials, where should the credentials be
|
|
0:17:09
|
pulled for voicemail or web conferencing? Should they pulled
|
|
0:17:13
|
pretty much not set which means they have to be
|
|
0:17:17
|
defined as usual on the individual CUPC client,
|
|
0:17:22
|
under file options accounts
|
|
0:17:25
|
or should they pulled from the CUPS server
|
|
0:17:31
|
or from a web conferencing server and in this case for
|
|
0:17:36
|
these are actually a show backwards, voicemail service
|
|
0:17:39
|
from web conferencing and web conferencing from voicemail so
|
|
0:17:42
|
obviously a little bit of a
|
|
0:17:45
|
interesting programming issue there on the server side.
|
|
0:17:51
|
But then we can also say what's the maximum message size
|
|
0:17:55
|
for instant messages, when should call records
|
|
0:17:59
|
be deleted after.
|
|
0:18:02
|
And then allow cut and paste and instant message
|
|
0:18:05
|
for compliance we can unselect that,
|
|
0:18:07
|
and then also should we always begin video
|
|
0:18:11
|
calls or calls that have a vta advantage
|
|
0:18:14
|
camera and client installed, should we always be in them
|
|
0:18:17
|
with video muted and then they have to unmute the video.
|
|
0:18:21
|
It's off by default, then in terms of active directory,
|
|
0:18:24
|
we choose which kind of directory we're syncing with of course,
|
|
0:18:27
|
but then we also have the ability from the
|
|
0:18:30
|
UPC side to not only rename the way they look but
|
|
0:18:35
|
specify what are the LDAP user fields
|
|
0:18:40
|
so for instance, maybe in the LDAP, maybe in Microsoft active directory,
|
|
0:18:43
|
I don't want to pull from telephone number,
|
|
0:18:45
|
I want to pull from IP phone which is another valid field.
|
|
0:18:49
|
Spell it properly and you can make those
|
|
0:18:52
|
association changes there.
|
|
0:18:59
|
So then other than that, in assigning the LDAP profile to the user,
|
|
0:19:02
|
we've got two new things and these again are only for the
|
|
0:19:05
|
8.0 client and hire
|
|
0:19:08
|
we've got CCM CIP profile which CCM CIP
|
|
0:19:15
|
are services, IP phone services supplied from
|
|
0:19:21
|
typically the CUCM servers
|
|
0:19:25
|
one or more servers and
|
|
0:19:30
|
you know we can certainly move these around but in this case
|
|
0:19:33
|
we're just using those servers, so we're just putting the IP
|
|
0:19:35
|
address of the pup and sub or sub and pub
|
|
0:19:39
|
obviously in a larger deployment, we wouldn't be using
|
|
0:19:42
|
a publisher at all, that's just what we happen to have
|
|
0:19:44
|
in our lab environment here,
|
|
0:19:46
|
and choosing if there's any sort of
|
|
0:19:48
|
certificate well there is a certificate whether it's just
|
|
0:19:52
|
self signed or whether we're actually using
|
|
0:19:55
|
some sort of a key store only or any certificate
|
|
0:20:00
|
we can assign users, we can do that in the user
|
|
0:20:03
|
settings or we can make it a default profile.
|
|
0:20:07
|
And then we have very nice and new
|
|
0:20:11
|
I dont think we have any set up right now, but we have a new
|
|
0:20:13
|
audio profiles, so this is to deal with
|
|
0:20:16
|
users that are using CUPC over the internet,
|
|
0:20:19
|
and potentially running into audio quality issues,
|
|
0:20:24
|
we can give this a name and we can
|
|
0:20:27
|
let's just say
|
|
0:20:30
|
let's just call it CUPC A, audio
|
|
0:20:37
|
audio profile, I guess we don't have to use dashes here
|
|
0:20:43
|
and give it a description if we want and
|
|
0:20:46
|
we have the ability to deal with automatic gain control so
|
|
0:20:51
|
should automatic gain control be used
|
|
0:20:54
|
in a situation where we're talking to a
|
|
0:21:00
|
a foreign, maybe through a PSTN gateway
|
|
0:21:02
|
that is a digital gateway, so in other words a E1 or T1,
|
|
0:21:09
|
CAS or ISTN PRI or something like that
|
|
0:21:14
|
or for analog FXO, FXS connections only or for both,
|
|
0:21:21
|
do we want noise suppression?
|
|
0:21:23
|
OK. So noise cancellation basically
|
|
0:21:26
|
and what's the policy, do we want to try to supress
|
|
0:21:30
|
noise at a low rate at a moderate rate,
|
|
0:21:34
|
high noise environment or more aggressive or an
|
|
0:21:38
|
extremely aggressive noise supression which we have to
|
|
0:21:41
|
keep in mind may deal with clipping of the audio,
|
|
0:21:46
|
as it tries to cancel out all noise at a very noisy environment,
|
|
0:21:50
|
voice activity detection, so we've said that VAD is bad,
|
|
0:21:55
|
but again in terms of VAD, it really has to do with
|
|
0:21:59
|
how is it implemented, so it certainly had been bad in the
|
|
0:22:03
|
past with better software in this case for
|
|
0:22:09
|
CUPC or even in terms of newer DSPs, newer PVDMs,
|
|
0:22:13
|
newer hardware when we're dealing with audio calls out to a PSTN,
|
|
0:22:17
|
or through a gateway,
|
|
0:22:20
|
if we have better algorithms and better hardware,
|
|
0:22:23
|
sometimes obviously we can get into this becoming a good thing again.
|
|
0:22:28
|
But anyway, in terms of your test taking, you just
|
|
0:22:31
|
need to know that it's there, it's possible
|
|
0:22:33
|
it could result in clipping still and so if you were dealing with
|
|
0:22:37
|
trouble shooting of presence, obviously if there was some sort of clipping,
|
|
0:22:41
|
we might want to take off voice activity detection
|
|
0:22:44
|
or possibly noise supression.
|
|
0:22:48
|
Or at least possibly experiment with
|
|
0:22:51
|
lowering the aggressiveness of these
|
|
0:22:56
|
two mechanisms, one to deal with noise and one to
|
|
0:23:00
|
stop transmitting voice when not there.
|
|
0:23:04
|
And then we have ecans or echo cancellers.
|
|
0:23:07
|
So we can deal with echo cancellation
|
|
0:23:12
|
whether we have a normal small amount basically
|
|
0:23:15
|
a high amount of echo,
|
|
0:23:17
|
whether we have an attenuation or we want to attenuate the echo
|
|
0:23:20
|
so attenuation I think we've said before defined as the
|
|
0:23:25
|
the loss of a signal across the given medium, so we're
|
|
0:23:30
|
in layman's terms very loosely
|
|
0:23:33
|
though not really that accurate, turning down the volume of the echo,
|
|
0:23:39
|
and do we want to cancel it or supress it?
|
|
0:23:43
|
So do we want to just cancel duplicate signals out all together?
|
|
0:23:46
|
Or do we simply want to try to supress them?
|
|
0:23:49
|
rather than cancelling them out altogether which
|
|
0:23:53
|
may result in the echo still being there
|
|
0:23:57
|
a little bit, maybe we would use supression along
|
|
0:24:01
|
attenuate but it wil hopefully be a lot more
|
|
0:24:06
|
faint if present at all and hopefully not very annoying.
|
|
0:24:11
|
If you've ever been on a call with echo where you can,
|
|
0:24:13
|
where it's very pronounced, it is
|
|
0:24:17
|
it's almost impossible, some people can do it
|
|
0:24:19
|
it's almost impossible for me to keep talking because
|
|
0:24:22
|
I'm just completely, I'm gonna log this out because
|
|
0:24:26
|
the other side logged out.
|
|
0:24:30
|
It's alomost impossible to keep talking just because I'm
|
|
0:24:33
|
so distracted by hearing my own voice.
|
|
0:24:37
|
I think it
|
|
0:24:41
|
it's just at CUPC 8,
|
|
0:24:45
|
audio profile 1
|
|
0:24:51
|
but the thing is, is that supression
|
|
0:24:55
|
while it might not completely eliminate the echo,
|
|
0:24:59
|
it also won't do what sometimes an echo
|
|
0:25:02
|
canceller versus an echo supressor might do
|
|
0:25:06
|
and that is that sometimes an echo canceller can
|
|
0:25:08
|
not only cancel out, well it cancels out signals that look
|
|
0:25:13
|
like the exact same signature audio wave
|
|
0:25:17
|
form signature from the transmit and the receive path
|
|
0:25:21
|
in a given amount of delay.
|
|
0:25:24
|
So over a period of 32 or 64 or 128 milliseconds or whatever hour
|
|
0:25:30
|
it can tail end echo canceller is set to
|
|
0:25:36
|
in terms of loss policy, it can cancel out
|
|
0:25:41
|
frequencies that or waveform signatures that look identical
|
|
0:25:45
|
sometimes those aren't actually echo and that's the problem.
|
|
0:25:49
|
So that's why we have the option to supress rathen than cancel
|
|
0:25:52
|
if sometimes information is being dropped that is
|
|
0:25:58
|
information or signal on the receive side that should have been there.
|
|
0:26:04
|
So we can go to user settings,
|
|
0:26:06
|
and we'll just add this audio policy,
|
|
0:26:08
|
to HReyes and save that.
|
|
0:26:13
|
And then we'll go fire up his client, one of the other thing
|
|
0:26:16
|
that I don't think we looked at the deskphone
|
|
0:26:18
|
control troubleshooter that isn't in any way different
|
|
0:26:21
|
one of the things I don't know if we looked at before was the
|
|
0:26:23
|
presence viewer, so we can actually say, let's say HReyes,
|
|
0:26:29
|
and click submit and this will show us information
|
|
0:26:32
|
about HReyes, his department, his manager
|
|
0:26:35
|
how many contacts he has, currently he doesn't have any
|
|
0:26:40
|
and whether those contacts
|
|
0:26:43
|
how many other contact were also watching this user
|
|
0:26:46
|
how many contacts we're not, pending
|
|
0:26:49
|
how many people are watching him, currently no one is
|
|
0:26:53
|
he has two devices, we can look at these
|
|
0:26:56
|
that same information from over here, what are those devices
|
|
0:26:59
|
is unified personal communicator through the
|
|
0:27:03
|
client services framework, the associated lines
|
|
0:27:06
|
the hardware phone, associated lines and capabilities
|
|
0:27:10
|
does it support audio, video or instant messaging,
|
|
0:27:15
|
all this information about him, deskphone control
|
|
0:27:18
|
is configured and looks like it should work properly,
|
|
0:27:21
|
license but logged out and he doesn't have any calender integration.
|
|
0:27:25
|
But we can also do something,
|
|
0:27:28
|
which is we can view a user ID from perspective
|
|
0:27:31
|
of someone else, so I could say what does Jack Shepherd
|
|
0:27:36
|
look like from the perspective of HReyes? If HReyes
|
|
0:27:39
|
was logged into a CUPC, how would Jack Shepherd appear?
|
|
0:27:43
|
And I click submit, he's currently unavailable,
|
|
0:27:46
|
and you know we see informatio about him.
|
|
0:27:49
|
So I could also go off hook on Jack's phone,
|
|
0:27:53
|
and then click submit and I see that Jack Shepherd is
|
|
0:27:57
|
busy from the perspective of the user HReyes.
|
|
0:28:02
|
Go back on hook and he's unavailable, now he would be
|
|
0:28:06
|
available if he were logged in into a CUPC client.
|
|
0:28:09
|
But because he doesn't have CUPC running,
|
|
0:28:11
|
that's why he shows as unavailable.
|
|
0:28:15
|
OK? So let's take a look at our
|
|
0:28:18
|
XP desktop and fire up unified personal communicator 8
|
|
0:28:23
|
and this desktop, we got rid of the host file
|
|
0:28:28
|
instead what we have is we are
|
|
0:28:33
|
pointed our network card or our TCIP properties are pointed to our
|
|
0:28:39
|
LDAP server which also is more importantly in this case our DNS server.
|
|
0:28:44
|
So HReyes is gonna log in with the password of Cisco,
|
|
0:28:48
|
and down here change server, I'm logging in with
|
|
0:28:51
|
the DNS name,
|
|
0:28:56
|
So we'll sign in, we can see that HReyes is
|
|
0:29:00
|
available which means that if we went
|
|
0:29:02
|
and said hey let's see what Jack Shepherd
|
|
0:29:06
|
what HReyes would look like from the perspective of Jack Shepherd,
|
|
0:29:12
|
it would see, we would say that HReyes
|
|
0:29:15
|
HReyes is available and
|
|
0:29:19
|
yuo know all the information about him.
|
|
0:29:23
|
OK? So we can see we don't have any contacts,
|
|
0:29:27
|
I can first of all, let's go to, actually let's go to file,
|
|
0:29:31
|
options and accounts.
|
|
0:29:35
|
And my voicemail user name and password has been set,
|
|
0:29:40
|
my LDAP is actually being controlled by CUP right now,
|
|
0:29:47
|
otherwise I would see an LDAP account
|
|
0:29:51
|
there I can still go to show server health, it looks a little different,
|
|
0:29:56
|
it's kinda nice but we've got all the information here,
|
|
0:30:00
|
I've got presence, I've got phone on my computer,
|
|
0:30:05
|
voice message store, looks like it's up and connected through IMAP,
|
|
0:30:09
|
voicemail itself is up and connected through
|
|
0:30:12
|
https, everything looks good here.
|
|
0:30:17
|
So I can also
|
|
0:30:21
|
let's go ahead and begin searching for a user,
|
|
0:30:25
|
and this search result is showing me from contact
|
|
0:30:28
|
which I don't have any contacts but also from history
|
|
0:30:31
|
so I've made a call to Jack before.
|
|
0:30:33
|
I could do something like search for Ben,
|
|
0:30:35
|
no results found, hit directory search, then is already there,
|
|
0:30:40
|
and I see Benjamin Linus and I can see information about him.
|
|
0:30:47
|
Now again let's do search for Jack,
|
|
0:30:51
|
and let's do directory search, so here I see Jack
|
|
0:30:55
|
and if I were to go off hook on him,
|
|
0:30:59
|
I can see because of that adhoc
|
|
0:31:02
|
subscription that he's offline currently on the phone.
|
|
0:31:07
|
I can also see that he has phone capabilities,
|
|
0:31:10
|
but I don't or I can email him, I can choose to do whichever
|
|
0:31:14
|
I can choose whether I just want to make
|
|
0:31:16
|
audio calls or a video call before I
|
|
0:31:20
|
you know go ahead and try to call him.
|
|
0:31:24
|
I can add him as a contact,
|
|
0:31:26
|
if I add him as a contact, from there it just goes ahead and adds him,
|
|
0:31:30
|
if I choose this user then I can choose to add him to a
|
|
0:31:34
|
group or create a new group.
|
|
0:31:37
|
And add him to that new group, so again I can see presence
|
|
0:31:40
|
information about him, status information, he's offline on the phone,
|
|
0:31:46
|
of course if he pressed DND, Do Not Disturb,
|
|
0:31:50
|
and that's active, he's not going off hook,
|
|
0:31:52
|
but you don't see any status change,
|
|
0:31:54
|
because he's in DND mode, I go off DND
|
|
0:31:58
|
and we see status again.
|
|
0:32:00
|
So currently because we don't have the 7961
|
|
0:32:03
|
tick box checked, if I go to call him,
|
|
0:32:07
|
just by clicking on the phone, and actually I can
|
|
0:32:13
|
hang up, I can hover over
|
|
0:32:15
|
and I can see more information about him, I could go to a chat
|
|
0:32:19
|
I could do the same thing here to edit the contact,
|
|
0:32:23
|
email him, but I could chat with him, he appears to be offline so it's
|
|
0:32:27
|
probably not gonna try to work, but I could you know from here call
|
|
0:32:32
|
just audio call or call it video,
|
|
0:32:35
|
to look up my history just with Jack,
|
|
0:32:37
|
my conversation history just with Jack
|
|
0:32:39
|
or else I can view all conversation history
|
|
0:32:43
|
but I'm gonna go ahead and call him,
|
|
0:32:46
|
and so this is calling him, it's calling him directly
|
|
0:32:48
|
from my laptop and because I actually don't have
|
|
0:32:52
|
a sound, or not my laptop but the XP client here in my
|
|
0:32:56
|
development rack and because I don't have a sound card with that
|
|
0:32:59
|
because it's a VM ware, instance and I have an assigned one,
|
|
0:33:03
|
then it doesn't actually complete the call but I can certainly call.
|
|
0:33:07
|
Now I can also tick 7961, actually let me
|
|
0:33:15
|
it's already done here so it's
|
|
0:33:19
|
in the process of trying to associate, I wanted to show
|
|
0:33:21
|
server health at the same time and so I can untick this
|
|
0:33:29
|
and when I ticked this, what happened was it was
|
|
0:33:32
|
trying to bring over deskphone and we see the alert
|
|
0:33:35
|
but that's just for deskphone video
|
|
0:33:38
|
because CDP can't detect a phone or
|
|
0:33:43
|
really a video client attached to the phone.
|
|
0:33:47
|
OK? So there's no camera attached to the phone.
|
|
0:33:51
|
If I had this CUPC controlling one of my 9971s
|
|
0:33:56
|
that I have with a camera, then it would work just fine.
|
|
0:33:59
|
But I can see that voice is fine so
|
|
0:34:02
|
connected through the quick buffer protocol, the CTI
|
|
0:34:06
|
2748 jtapi protocol, everything should be fine I can go ahead and call
|
|
0:34:13
|
and when I do call, it's actually placing a call
|
|
0:34:16
|
from my other client and then go ahead and answer the call,
|
|
0:34:25
|
then I have full cotrol over the call, I can hold the call
|
|
0:34:33
|
I can unpause the call and I can hang up
|
|
0:34:38
|
so really that's it, it's not too much different
|
|
0:34:40
|
in too many ways but there are a few new
|
|
0:34:45
|
fairly nice things about 8, there is one last thing that
|
|
0:34:50
|
I forgot to mention and that is over in CUCM
|
|
0:34:54
|
so let's open that server back up again,
|
|
0:34:57
|
over in CUCM under user management end user
|
|
0:35:04
|
and I'll just use HReyes as an example,
|
|
0:35:08
|
and he has standard CCM end users
|
|
0:35:12
|
and standard CTI enabled which all he needs for
|
|
0:35:15
|
the older generation 3 phones but if he does
|
|
0:35:19
|
happen to have a 6900 series phone,
|
|
0:35:23
|
then he needs to, let's actually just look at contains CTI
|
|
0:35:31
|
if he has a 6900 series phone, he needs to add this
|
|
0:35:36
|
group and subsequent roles, allow control of phone supporting roll over
|
|
0:35:42
|
that's just for the 6900 series.
|
|
0:35:44
|
And if he has an 8900 or 9900
|
|
0:35:49
|
phones so a 8941, 8945, 8961
|
|
0:35:54
|
or a 9951 or 9971 then he needs to have
|
|
0:36:00
|
CTI control of phones supporting connected transfer
|
|
0:36:03
|
and conference. OK? Those two are very important
|
|
0:36:08
|
to note and again the connected transfer and conferences for 8999
|
|
0:36:14
|
and the role over is for 6900 phones.
|
|
0:36:18
|
Don't confuse them, don't add both
|
|
0:36:21
|
and something important to remember.
|
|
0:36:26
|
OK? Other than that those are the differences from 8.0 to 7.
|
|
0:36:30
|
|
