|
0:00:13
|
Ok, so we're back and let's take a look at
|
|
0:00:16
|
CUPS integration with CUCM.
|
|
0:00:20
|
So first let's go to our system column in CUCM and
|
|
0:00:24
|
take a look at our application server.
|
|
0:00:27
|
We note that we already have a few.
|
|
0:00:29
|
One from unity when it was integrated
|
|
0:00:31
|
and one for CUPS 7
|
|
0:00:36
|
Notice that if we went back to Unity Connection
|
|
0:00:40
|
it had a specific field for IP address
|
|
0:00:43
|
as well it has application users which we can actually use
|
|
0:00:48
|
didn't need to in our examples for this class, so we have
|
|
0:00:51
|
in actually the deep dives as well as some of the
|
|
0:00:55
|
labs where we use these users or assign these
|
|
0:00:58
|
and this actually allows us to have device phone
|
|
0:01:02
|
from the line capability to create a mailbox
|
|
0:01:04
|
or push AXL from CUCM over to Unity Connection.
|
|
0:01:11
|
But depending on the type of server for CUPS 7
|
|
0:01:14
|
it doesn't have an IP address and we really don't need to put
|
|
0:01:18
|
anything in user or URL or end user URL for this
|
|
0:01:22
|
particular integration and setup.
|
|
0:01:27
|
So we have CUPS 7 again, this needs to be the
|
|
0:01:30
|
host name, so if we don't happen to know the host name
|
|
0:01:33
|
we can SSH
|
|
0:01:39
|
over to CUPS and we can do the same thing in CUCM as well
|
|
0:01:43
|
and say show myself
|
|
0:01:46
|
and it will show the machine name.
|
|
0:01:48
|
Now, this only shows the host name. It does not
|
|
0:01:51
|
show a fully qualified domain name or even if there is
|
|
0:01:54
|
a domain, so for that we would need to
|
|
0:01:57
|
do sh and I believe it's network
|
|
0:02:05
|
and let's do sh network status
|
|
0:02:15
|
No, that's basically a net stat
|
|
0:02:17
|
that was not what we wanted.
|
|
0:02:24
|
show network
|
|
0:02:26
|
I think it's show network ethernet 0
|
|
0:02:36
|
Ok, DNS is not configured.
|
|
0:02:39
|
so that tells us whether DNS is configured or not. That doesn't exactly
|
|
0:02:43
|
tell us -- let's do utils network
|
|
0:02:49
|
No, let's see which one was it?
|
|
0:03:01
|
I believe it is one of the -- Oh, you know what, it might
|
|
0:03:03
|
just be a show status
|
|
0:03:12
|
there we go.
|
|
0:03:14
|
Show status, so here we have host name
|
|
0:03:16
|
so if we had a domain name set
|
|
0:03:19
|
then this would also show CUPS 7 for instance .ine.com
|
|
0:03:24
|
or .cisco.com this would show the fully qualified domain name.
|
|
0:03:27
|
So show myself or really the best one is show status.
|
|
0:03:33
|
Ok, so CUPS 7 was our host name. It's what we have
|
|
0:03:35
|
entered here and we have already run through the
|
|
0:03:39
|
three or four page post installation script over on...
|
|
0:03:44
|
whoops, I didn't actually mean to do it in that window.
|
|
0:03:47
|
I meant to open a new window
|
|
0:03:50
|
for CUPS
|
|
0:03:52
|
for the server administration
|
|
0:03:55
|
we've already run through this post script post installation
|
|
0:03:58
|
script, so we are presented with the standard log on
|
|
0:04:00
|
user pass and we do get to the main administration
|
|
0:04:04
|
web interface
|
|
0:04:06
|
and we show that we're integrated down here
|
|
0:04:09
|
with the particular CUCM server and we can even
|
|
0:04:13
|
look at the topology
|
|
0:04:16
|
as it relates to the CUCM publisher.
|
|
0:04:19
|
So it will actually retrieve real time
|
|
0:04:21
|
publisher status
|
|
0:04:22
|
at least via AXL
|
|
0:04:27
|
and it's updated so we do have reachability.
|
|
0:04:32
|
Pingable AXL IPSec even though we're not
|
|
0:04:36
|
particularly using that and what server that publisher is.
|
|
0:04:39
|
And the CUP server so this .50 has actually
|
|
0:04:43
|
added itself as a form of a subscriber to the
|
|
0:04:48
|
publisher, so if we actually went over and SSHed
|
|
0:04:53
|
to the CUCM publisher
|
|
0:05:00
|
and said sh network cluster
|
|
0:05:04
|
whoops, not CLI, but CLU
|
|
0:05:08
|
we would see that we have the .10, .20 for
|
|
0:05:11
|
Pub and Sub and we have CUPS 7 is one of the subscribers
|
|
0:05:16
|
in terms of parts of the database synchronization.
|
|
0:05:23
|
Ok, so back on the CUCM publisher
|
|
0:05:28
|
we need to go ahead and set up a few things.
|
|
0:05:30
|
So first of all let's set up a device trunk
|
|
0:05:35
|
see what we have. We've got a trunk to corporate gatekeeper
|
|
0:05:39
|
and one to the corporate headquarter as a SIP gateway
|
|
0:05:43
|
to the PSTN. Let's add a new trunk
|
|
0:05:46
|
of type SIP.
|
|
0:05:50
|
And we'll give it a name, we'll call it CUPS 7
|
|
0:05:53
|
if we like, it doesn't need to be the host name
|
|
0:05:56
|
it could just be called CUPS SIP publish trunk
|
|
0:06:04
|
not piblish, publish.
|
|
0:06:08
|
Device pool it's at corporate headquarters.
|
|
0:06:12
|
So whatever MRGLs for media resources that we might
|
|
0:06:17
|
need or anything like that should be pulled.
|
|
0:06:19
|
Location is fine. AAR group there's really no calling
|
|
0:06:22
|
it's a good idea just to set AAR group CSS
|
|
0:06:27
|
and either AAR mask, AAR destination mask
|
|
0:06:31
|
or external phone number mask every we see it
|
|
0:06:33
|
just so that we don't overlook anything, but we
|
|
0:06:36
|
don't really need it for this.
|
|
0:06:43
|
We do definitely -- so again you might set all these things
|
|
0:06:48
|
even though that's really not -- this isn't going to be used for
|
|
0:06:50
|
calling per se, so the main information we want to set
|
|
0:06:57
|
is the 177.1.10.50
|
|
0:07:01
|
which is the IP address of that CUP server.
|
|
0:07:08
|
It's not an SRV service DNS record.
|
|
0:07:12
|
Standard presence group
|
|
0:07:14
|
SIP trunk security profile non-secure, we might want to
|
|
0:07:17
|
check that SIP trunk security profile just to make sure
|
|
0:07:20
|
it is still non-secure.
|
|
0:07:25
|
And really we can leave everything else the same
|
|
0:07:27
|
I mean it might not be a bad idea to set this
|
|
0:07:31
|
rerouting out of dialogue refer.
|
|
0:07:34
|
We don't really need a subscribe calling search space
|
|
0:07:36
|
we're not going to be doing subscribes. We're
|
|
0:07:38
|
going to be doing publish, but you can set it, it's fine.
|
|
0:07:42
|
The SIP profile we have to have something. DTMF
|
|
0:07:45
|
no preference, again, we're not going to be using DTMF
|
|
0:07:48
|
but if it did, it would default to whatever is best
|
|
0:07:53
|
selected RFC 2833 preferably.
|
|
0:07:56
|
So we'll reset this trunk.
|
|
0:08:06
|
We will come over to System> Service Parameters.
|
|
0:08:11
|
CUCM service parameters.
|
|
0:08:15
|
And we're going to the call manager service.
|
|
0:08:25
|
And we're going to do a control F to find publish.
|
|
0:08:31
|
And we find one and the second is the timer.
|
|
0:08:34
|
The third is the expiration.
|
|
0:08:37
|
Fourth, there we go it's the fifth.
|
|
0:08:41
|
CUP publish trunk.
|
|
0:08:45
|
Remember that when you're searching in
|
|
0:08:47
|
service parameters, sometimes especially if you want to search
|
|
0:08:49
|
not only the header, the actual field name, but also
|
|
0:08:54
|
possibly the default values or some of the
|
|
0:08:56
|
possible values to click on the context sensitive
|
|
0:08:59
|
help and do a control find in there.
|
|
0:09:04
|
However, this is good enough for us for right now.
|
|
0:09:08
|
Ok, so now we need to take a look and let's go over
|
|
0:09:14
|
to our CUP server and let's look over at some of the
|
|
0:09:23
|
particular users that we might want to set up.
|
|
0:09:26
|
So first of all, we've got personal communicator
|
|
0:09:30
|
desk phone control and IP phone messenger and
|
|
0:09:32
|
here we're going to have users assigned for these.
|
|
0:09:35
|
So here is the application user name CTI GW
|
|
0:09:40
|
this is where we said we're going to get our Notepad out.
|
|
0:09:49
|
So I've got the user
|
|
0:09:50
|
whoops
|
|
0:09:52
|
CTI GW password cisco
|
|
0:09:57
|
and if I go up to Application> IP Phone Messenger Settings
|
|
0:10:02
|
I'm also going to have this user phone messenger.
|
|
0:10:07
|
Ok, so let's just make sure that the password is cisco
|
|
0:10:10
|
cisco save.
|
|
0:10:15
|
Application> Desk Phone Control> Settings
|
|
0:10:18
|
Application let's flip it to on. The other IP phone messenger
|
|
0:10:22
|
was on and let's go to password cisco cisco
|
|
0:10:27
|
save, in fact, since we're here, we might as well go ahead and
|
|
0:10:29
|
fill in this 177.1.10. let's say 20
|
|
0:10:34
|
and .10 just since we're here.
|
|
0:10:41
|
Now we did that so that we could go back to CUCM
|
|
0:10:43
|
create our application users
|
|
0:10:48
|
and -- we may actually already have these. Let's do a find first real quick.
|
|
0:10:53
|
CTI
|
|
0:10:55
|
or phone -- nope, it doesn't look like we do.
|
|
0:10:58
|
So we're going to grab our CTI gateway user
|
|
0:11:01
|
the password we're going to grab is cisco
|
|
0:11:05
|
let's just put it in all these places although we don't need
|
|
0:11:08
|
the digest credentials for this particular bit.
|
|
0:11:12
|
And these are both of these users.
|
|
0:11:15
|
whoops
|
|
0:11:18
|
CTI gateway is for desk phone control.
|
|
0:11:20
|
Phone messenger is for the IP phone messenger
|
|
0:11:22
|
XML service which needs to be able push information
|
|
0:11:26
|
to the phone, so both of them need CTI control.
|
|
0:11:30
|
And because they're controlling the same phones although we
|
|
0:11:35
|
said it wasn't a good idea and it's not to do with UCCX
|
|
0:11:39
|
in CUPS it's actually ok, it's perfectly fine to do
|
|
0:11:42
|
we're going to give both of these application users
|
|
0:11:46
|
instead of associating devices, we're going to give
|
|
0:11:48
|
them standard CTI control of all devices.
|
|
0:11:54
|
So we'll save.
|
|
0:11:58
|
Good.
|
|
0:12:00
|
And we are going to go ahead and do these four options.
|
|
0:12:05
|
In fact, that reminds me one of the things that we need
|
|
0:12:08
|
to be able -- whoops
|
|
0:12:09
|
sorry -- one of the things that we need to do
|
|
0:12:11
|
or needed to do for the SIP trunk
|
|
0:12:15
|
the SIP publish trunk was come over to the
|
|
0:12:18
|
SIP trunk security profile that was used
|
|
0:12:21
|
either create a new one or in the lab again, this isn't
|
|
0:12:24
|
production network, we wouldn't do this in production
|
|
0:12:26
|
but perfectly fine in the lab. Come down and say
|
|
0:12:29
|
accept present subscription out of dialog refer
|
|
0:12:31
|
unsolicited notification and the SIP replaces header.
|
|
0:12:35
|
And save that and we probably want to reset
|
|
0:12:38
|
that trunk again once we've done that.
|
|
0:12:44
|
Make sure it's set to non-secure. Make sure the port is proper.
|
|
0:12:48
|
Ok, notice there was a port on the SIP trunk
|
|
0:12:50
|
that was the outgoing port that we contact that IP address on.
|
|
0:12:52
|
This is the incoming port that we're listening to.
|
|
0:12:55
|
Both should be 5060
|
|
0:12:57
|
but just something to note there.
|
|
0:13:03
|
So then back to application user
|
|
0:13:05
|
we've got our CTI gateway
|
|
0:13:08
|
we're also going to create a new user for phone messenger.
|
|
0:13:14
|
Password
|
|
0:13:16
|
cisco, cisco, cisco, cisco,
|
|
0:13:19
|
we'll go ahead and do these four.
|
|
0:13:23
|
And go ahead and say add to user group.
|
|
0:13:28
|
And we're going to say standard CTI allow control
|
|
0:13:31
|
of all devices. Add selected.
|
|
0:13:32
|
Save.
|
|
0:13:36
|
And at this point we need to go ahead
|
|
0:13:40
|
and go back.
|
|
0:13:44
|
So we've got our users set up.
|
|
0:13:47
|
We need to go ahead and at this point go
|
|
0:13:50
|
back to system
|
|
0:13:54
|
actually we haven't set up -- we've set up our application
|
|
0:13:57
|
users, but we haven't set up our end users for CUPC yet.
|
|
0:14:00
|
So let's go ahead and say we're going to make Ben Linus
|
|
0:14:03
|
the CUPC user.
|
|
0:14:05
|
Alright.
|
|
0:14:07
|
So we want to -- let's go to User> End User
|
|
0:14:12
|
and let's take a look at B for Ben Linus
|
|
0:14:17
|
or Linus.
|
|
0:14:19
|
And make sure that his -- this is a pin. Remember
|
|
0:14:22
|
password is set through LDAP the way we have it set up
|
|
0:14:24
|
so authentication will effectively proxy depending on what mode
|
|
0:14:29
|
we're in, whether we're in desk phone control or
|
|
0:14:31
|
soft phone mode, we'll proxy through the CUP server to the
|
|
0:14:34
|
CUCM publisher and then from the publisher over to the
|
|
0:14:37
|
Microsoft active directory LDAP database for authentication.
|
|
0:14:41
|
But we want to make sure that we have digest credentials.
|
|
0:14:44
|
So I'm just going to go back and copy
|
|
0:14:47
|
whoops
|
|
0:14:49
|
copy and paste cisco, cisco that way we don't have to
|
|
0:14:53
|
have an access control entry
|
|
0:14:56
|
and just so that we have a one for one understanding of
|
|
0:15:02
|
where we're or what this is alleviating us from doing
|
|
0:15:06
|
this digest credentials is alleviating us over on the
|
|
0:15:10
|
CUP server itself from going to System> Security> Incoming and Outgoing ACL
|
|
0:15:19
|
We already have CUPS 7 set
|
|
0:15:23
|
for incoming.
|
|
0:15:27
|
We also have security outgoing
|
|
0:15:33
|
set for CUPS 7
|
|
0:15:35
|
Now we haven't actually set up the presence settings yet.
|
|
0:15:38
|
As soon as we do and set up actually the gateway
|
|
0:15:40
|
then CUCM publisher will be added here
|
|
0:15:45
|
but this is allowing us or alleviating us I should maybe better state
|
|
0:15:50
|
from having to come in here for outgoing and
|
|
0:15:54
|
incoming access control lists and saying something
|
|
0:15:57
|
like the pattern of all which is basically a permit
|
|
0:15:59
|
IP any any saying for CUPC clients.
|
|
0:16:05
|
So we're not going to do that
|
|
0:16:09
|
instead, we're simply going to add the digest credentials.
|
|
0:16:14
|
Ok,
|
|
0:16:16
|
he has a device associated which is needed.
|
|
0:16:19
|
He has allow control from CTI, but this is
|
|
0:16:23
|
really a subset of extension mobility as is presence group and subscribe
|
|
0:16:26
|
calling search space, so this particular user Ben Linus
|
|
0:16:30
|
doesn't have -- it might have extension mobility
|
|
0:16:33
|
enabled on the phone, but he wasn't the extension mobility
|
|
0:16:35
|
traveler. JShepherd from corporate headquarter phone 1 was.
|
|
0:16:39
|
However, if this were JShepherd corporate headquarter phone 1,
|
|
0:16:43
|
we would need to remember that some extension mobility specifics
|
|
0:16:48
|
not only the available profile that is selected for the
|
|
0:16:51
|
controlled profiles and maybe default profile, but as it relates
|
|
0:16:55
|
to presence, presence group, subscribe calling search space
|
|
0:16:58
|
and allow control of device from CTI when he is hoteling
|
|
0:17:01
|
on another phone, that needs to be done on the end user
|
|
0:17:04
|
but we're not doing that for this particular user.
|
|
0:17:08
|
He does need to have standard CTI enabled
|
|
0:17:11
|
and if he wants to make any changes to not only
|
|
0:17:14
|
his CCM end user page, so the CCM instead of CCM admin
|
|
0:17:20
|
the CCM user page as it pertains to CUCM
|
|
0:17:24
|
but also the -- notice that this CUP server
|
|
0:17:28
|
.50 is still CCM admin for the admin page and it's
|
|
0:17:33
|
CCM user for the end user page as the user pertains
|
|
0:17:37
|
to settings related to CUPS
|
|
0:17:41
|
or CUPC or IP phone messenger such as contacts, so he needs
|
|
0:17:45
|
to have that to login to both.
|
|
0:17:49
|
He needs standard CTI enabled.
|
|
0:17:51
|
We'll say save.
|
|
0:17:56
|
He of course needs to be associated to that device
|
|
0:18:01
|
which he already is
|
|
0:18:03
|
from both the owner user ID
|
|
0:18:09
|
as well as on the line.
|
|
0:18:12
|
And the device itself has allow control of device
|
|
0:18:15
|
from CTI
|
|
0:18:17
|
especially if it's not the extension mobility controlled or logged in
|
|
0:18:22
|
current profile.
|
|
0:18:24
|
And again, remember it sort of is because it has extension
|
|
0:18:28
|
mobility enabled, this particular device is if we click save, it will say
|
|
0:18:33
|
it's currently logged in by a user. Which user?
|
|
0:18:38
|
Well, it's actually -- once this refreshes
|
|
0:18:43
|
again, we said this already in the conversation earlier
|
|
0:18:45
|
it's actually the -- where is it here?
|
|
0:18:49
|
There we go. It's currently the log out profile, so the
|
|
0:18:53
|
auto generated device profile for this device, so
|
|
0:18:55
|
if we looked at it in the database, it would actually be this phone
|
|
0:18:59
|
is SEP Mac address if we're logged in from a
|
|
0:19:03
|
user extension mobility profile, it's UDP and the Mac address
|
|
0:19:08
|
if we are looking at this phone as it's currently it's actually
|
|
0:19:13
|
ADP Mac address for Auto Generated Device Profile
|
|
0:19:16
|
and the Mac address, so that's currently what's happening
|
|
0:19:19
|
but any changes we make to this page and say reset
|
|
0:19:22
|
which we haven't made any changes now, but if we had
|
|
0:19:25
|
it would also reset the auto generated device profile
|
|
0:19:28
|
to match those settings
|
|
0:19:30
|
since that's really a hands-off system controlled device profile.
|
|
0:19:38
|
Ok, and if extension mobility was causing us any problems
|
|
0:19:41
|
and let's say we weren't told to enable it on every phone
|
|
0:19:44
|
then we could simply disable it by unticking this box
|
|
0:19:47
|
but leave it on for any phone of course in the lab that you were told
|
|
0:19:50
|
to enable it for or allow a user to be able to login to that device.
|
|
0:19:57
|
Ok, so we've got our user set up.
|
|
0:20:01
|
We need to go over to System> Licensing and Capabilities Assignment
|
|
0:20:09
|
and allow this particular user
|
|
0:20:14
|
so we'll select him and choose to do bulk assignment even though we're
|
|
0:20:18
|
only assigning capabilities for one particular user.
|
|
0:20:22
|
We need to be able to give him rights for presence
|
|
0:20:28
|
so CUP enabled, Cisco Unified Presence enabled and then
|
|
0:20:31
|
also CUPC or Cisco Unified Presence Communicator
|
|
0:20:35
|
and in fact, let's actually give another user as well because
|
|
0:20:38
|
we'll do the IP phone messenger on that user, so let's do James Ford
|
|
0:20:42
|
as well.
|
|
0:20:46
|
Now, if we go over to our CUP server before we do that
|
|
0:20:49
|
license assignment and we actually take a look at user management
|
|
0:20:54
|
actually let's just go up to topology.
|
|
0:20:59
|
We'll note that we have our default CUPS sub cluster, our
|
|
0:21:03
|
CUPS 7 server assigned to that cluster and how many
|
|
0:21:07
|
users are there. There are currently zero users.
|
|
0:21:09
|
That's because we haven't done any capabilities assignments
|
|
0:21:13
|
over in CUCM.
|
|
0:21:16
|
So this will this show up no users.
|
|
0:21:19
|
If we come over to CUCM, select BLinus and JFord and say
|
|
0:21:22
|
bulk assignment
|
|
0:21:26
|
actually we don't want to do the same. I'm going to
|
|
0:21:28
|
unselect JFord and I'm going to say bulk assignment
|
|
0:21:31
|
just for Ben. We'll do CUP and CUPC
|
|
0:21:35
|
save
|
|
0:21:38
|
and then for JFord I'll do a separate bulk assignment
|
|
0:21:44
|
for only CUP.
|
|
0:21:46
|
And save.
|
|
0:21:50
|
So we can see that JFord has the CUP tick box in the column
|
|
0:21:54
|
BLinus has both.
|
|
0:22:02
|
We should be able to -- let's click away from --
|
|
0:22:06
|
well we still haven't set up all of the integration yet, so
|
|
0:22:09
|
let's go ahead and come back to the CUP server
|
|
0:22:13
|
and we'll begin with the settings over here, so
|
|
0:22:16
|
we're going to the column for -- actually first of all, we need
|
|
0:22:19
|
to go to the column for system and service parameters
|
|
0:22:25
|
and we want to go to the CUPS 7 server
|
|
0:22:29
|
and then as the service, this is where we mentioned we
|
|
0:22:31
|
don't want what would sound logical which is Cisco UP
|
|
0:22:36
|
presence engine, but we actually want SIP proxy and the domain
|
|
0:22:41
|
not set, we just want to set it to something, so let's say
|
|
0:22:43
|
cisco.com
|
|
0:22:50
|
and is this one of those settings that requires us to restart
|
|
0:22:53
|
the service?
|
|
0:22:57
|
It doesn't tell us we do, I don't believe we do.
|
|
0:23:01
|
So now we'll come over to presence column and
|
|
0:23:03
|
go settings
|
|
0:23:06
|
and we need to enable the SIP publish trunk on CUCM.
|
|
0:23:09
|
It already has the right one selected, we just had to click enable.
|
|
0:23:12
|
Do not click CVP enable. We're not using this
|
|
0:23:15
|
as a proxy, SIP proxy server
|
|
0:23:18
|
although the presence server is Cisco's SIP proxy server.
|
|
0:23:23
|
Replacement to what they used to have which was
|
|
0:23:25
|
CSPS, Cisco SIP Proxy Server.
|
|
0:23:27
|
If we tick this box, it will actually say, 'Once further
|
|
0:23:31
|
configuration for CVP is entered, unchecking this will not recreate any
|
|
0:23:34
|
default records that were deleted or modified and could possibly
|
|
0:23:37
|
cause presence services to fail. A reinstall may be required.'
|
|
0:23:40
|
So don't accidentally click this and hit save. Read the warning.
|
|
0:23:44
|
Just leave it as it is, enable the SIP publish and say save.
|
|
0:23:50
|
And then we'll come down to gateways.
|
|
0:23:56
|
Click to find any existing gateways which there are none.
|
|
0:23:58
|
We'll add new.
|
|
0:24:01
|
We want to choose the gateway type is CUCM. We don't have
|
|
0:24:04
|
outlook in the lab, so description
|
|
0:24:07
|
CUCM publisher.
|
|
0:24:12
|
And presence gateway 177.1.10.10 the Pub.
|
|
0:24:18
|
Ok, the add was successful.
|
|
0:24:19
|
If we go back to find list
|
|
0:24:22
|
we're going to note that's what we have
|
|
0:24:24
|
again, remember we cannot add another one, so if you
|
|
0:24:28
|
wanted to say CUCM Sub
|
|
0:24:31
|
177.1.10.20 it's going to say we already have one of the type
|
|
0:24:36
|
CUCM and only one gateway can be defined for each gateway type,
|
|
0:24:41
|
so we don't have the ability nor do we need to configure
|
|
0:24:44
|
a backup gateway there, so no problem.
|
|
0:24:50
|
We're not going to deal with inter-cluster between any other
|
|
0:24:54
|
CUCM or CUPS cluster. We don't need to deal with
|
|
0:24:58
|
inter-domain federations
|
|
0:25:00
|
for instance, dealing with integration or inter -- ability between
|
|
0:25:05
|
CUPS and let's say Microsoft OCS
|
|
0:25:09
|
nor do we need to go down to user agent or routing
|
|
0:25:11
|
which really deals more with the Cisco SIP proxy server
|
|
0:25:14
|
settings and the ability to do routes, number expansion
|
|
0:25:19
|
all the digit manipulation and DN routes and things like that
|
|
0:25:22
|
that you would do with a Cisco SIP proxy server. We're not
|
|
0:25:25
|
using it for that, so we can skip all that
|
|
0:25:28
|
and come over to Cisco Unified Personal Communicator.
|
|
0:25:32
|
So let's go ahead and begin setting up Cisco
|
|
0:25:34
|
Unified Personal Communicator.
|
|
0:25:35
|
Primary TFTP server 177.1.10.10
|
|
0:25:41
|
Maybe we have a backup.
|
|
0:25:44
|
Microsoft Active Directory is we're doing any integration with.
|
|
0:25:49
|
Here is the UPC or Cisco Unified Personal Communicator user fields
|
|
0:25:54
|
and then the LDAP user fields.
|
|
0:25:59
|
And remember that we were back in CUCM
|
|
0:26:04
|
for LDAP
|
|
0:26:05
|
LDAP directory
|
|
0:26:08
|
one of these fields
|
|
0:26:10
|
was not the default and it was the phone number
|
|
0:26:13
|
in the actual Microsoft LDAP, I had it mapped to the
|
|
0:26:16
|
IP phone.
|
|
0:26:20
|
So instead of telephone number, it is -- and we can just
|
|
0:26:24
|
copy, we want case sensitive
|
|
0:26:26
|
IP phone
|
|
0:26:30
|
it might actually be worth pasting that
|
|
0:26:33
|
whoops
|
|
0:26:36
|
pasting that into Notepad just to make sure that
|
|
0:26:40
|
we're getting a pasted version of that, that has no
|
|
0:26:47
|
spaces, line feeds, carriage returns anything like that
|
|
0:26:52
|
so let's go up and press save.
|
|
0:26:54
|
The proxy listener is going to be the default TCP. We don't
|
|
0:26:58
|
have TLS or Transport Layer Security
|
|
0:27:01
|
also sometimes referred to as SSL version 3
|
|
0:27:04
|
we're using TCP, not UDP
|
|
0:27:07
|
or Http or Https, so that's fine.
|
|
0:27:11
|
Go back to personal communicator user settings.
|
|
0:27:18
|
Ok, we don't see any users here yet.
|
|
0:27:24
|
We may need to restart the service over here
|
|
0:27:32
|
and not a problem, we'll just go ahead and configure
|
|
0:27:33
|
everything and then -- actually, let's check the
|
|
0:27:37
|
incoming ACL
|
|
0:27:40
|
I don't see the auto generated for CUCM
|
|
0:27:45
|
so let's go ahead and add that.
|
|
0:28:04
|
And so this was -- let's see are we in incoming or outgoing?
|
|
0:28:11
|
Security, I believe we're in incoming
|
|
0:28:15
|
and security outgoing.
|
|
0:28:30
|
Ok, while we're here, we're actually just going to go ahead
|
|
0:28:32
|
and set up our link over to .30
|
|
0:28:36
|
which is our Voice mail server as well.
|
|
0:29:03
|
Ok, so we've got our link to our Unity Connection server
|
|
0:29:06
|
as well and so let's come up here to
|
|
0:29:11
|
Unified Personal Communicator Voice mail server.
|
|
0:29:15
|
And we're going to go ahead and add a new.
|
|
0:29:20
|
Server type is Unity Connection.
|
|
0:29:21
|
Name, let's just call it CUCX
|
|
0:29:26
|
we would call it probably something more specific if we had more than one
|
|
0:29:28
|
if it was a large installation.
|
|
0:29:30
|
IP address is .30
|
|
0:29:33
|
Web port is 443 for HTTPS
|
|
0:29:38
|
We do want secure communication at least for the SSL 443 web communication
|
|
0:29:44
|
just because Unity Connection is set up for that.
|
|
0:29:47
|
Then we need IMAP settings can be configured on the mail store
|
|
0:29:50
|
so we can click here or go back up to Application> CUPC> Voice Mail
|
|
0:29:56
|
Mail Store and then once we've completed that and the Voice mail
|
|
0:29:59
|
server which is the page we're on now, then we can
|
|
0:30:01
|
do the profile, so it kind of helps you by leading you in the
|
|
0:30:04
|
right direction there. Find.
|
|
0:30:07
|
There are none.
|
|
0:30:08
|
We'll create a new mail store or a reference to a mail store.
|
|
0:30:12
|
And name, we'll just say it's CUCX mail store.
|
|
0:30:20
|
Same IP address. Port 143 which is IMAP
|
|
0:30:26
|
and then what we're going to do is Application> CUPC> Voice mail profile
|
|
0:30:30
|
and we're going to link those two together, so we're going to
|
|
0:30:33
|
link the actual server
|
|
0:30:35
|
and web communication.
|
|
0:30:41
|
So voice messaging pilot.
|
|
0:30:43
|
That's fine.
|
|
0:30:45
|
Let's just use the default.
|
|
0:30:48
|
Although that doesn't look like it's reading integration
|
|
0:30:51
|
from AXL because CUCM has more than that configured.
|
|
0:30:56
|
In fact, let's go up to presence
|
|
0:31:02
|
gateways
|
|
0:31:07
|
CUCM publisher
|
|
0:31:11
|
wait until it retrieves the publisher status.
|
|
0:31:15
|
It says reachable, everything's fine.
|
|
0:31:25
|
But it only shows default and none where actually over
|
|
0:31:28
|
in CUCM there is -- it should be three profiles.
|
|
0:31:34
|
Yeah CUE Voice mail as well
|
|
0:31:36
|
as well as default and no Voice mail.
|
|
0:31:40
|
Ok, we very well may have to reboot these servers in just
|
|
0:31:43
|
a moment. Not a big deal.
|
|
0:31:46
|
So CUCX, our primary Voice mail servers, so this is the
|
|
0:31:50
|
Voice mail server we just defined here in Application> Voice mail server
|
|
0:31:54
|
and then the mail store for the primary mail store.
|
|
0:31:59
|
And we'll just go ahead and say make this the default profile
|
|
0:32:01
|
for the system
|
|
0:32:03
|
and save.
|
|
0:32:06
|
And let's see if there's any users that we can see here yet.
|
|
0:32:13
|
There are no users to be found yet.
|
|
0:32:15
|
That's ok.
|
|
0:32:17
|
Not a problem really just at this point.
|
|
0:32:24
|
So we'll come down -- we don't have a conferencing server
|
|
0:32:27
|
we don't have meeting place express in the lab.
|
|
0:32:30
|
We do have CTI gateway server.
|
|
0:32:36
|
So let's add a new gateway host
|
|
0:32:38
|
and this is going to be -- this is the CTI server, so this
|
|
0:32:41
|
has to be the call manager, so let's say CUCM publisher
|
|
0:32:46
|
.10
|
|
0:32:48
|
2748 TCP, that's CTI or JTAPI
|
|
0:32:53
|
and we will go ahead and add a new or actually copy
|
|
0:32:58
|
this over to the subscriber
|
|
0:33:01
|
as .20, we may not have a subscriber or secondary
|
|
0:33:06
|
presence server, but we do have a secondary CTI
|
|
0:33:08
|
server and again, CTI is going to be used for
|
|
0:33:11
|
personal communicator desk phone control as well as
|
|
0:33:14
|
IP phone messenger.
|
|
0:33:17
|
Ok, so let's just go back, make sure both these were entered properly.
|
|
0:33:21
|
They are.
|
|
0:33:22
|
Application> Personal Communicator and let's go to CTI Gateway Profile
|
|
0:33:29
|
Find.
|
|
0:33:30
|
And we actually don't see any yet
|
|
0:33:32
|
which is a bit interesting, so we should see some
|
|
0:33:38
|
CTI gateway profiles added automatically when we set up
|
|
0:33:43
|
our gateway, so at this point, let's go ahead and
|
|
0:33:46
|
go to serviceability.
|
|
0:33:49
|
And it's possible that we didn't even start the services yet
|
|
0:33:52
|
in fact, that's probable of what happened.
|
|
0:33:55
|
So let's go to -- if we go to feature services
|
|
0:33:59
|
we'll see not only if they're activated, but also if they're
|
|
0:34:02
|
enabled, I think we haven't activated them yet
|
|
0:34:05
|
I believe we skipped right over that.
|
|
0:34:08
|
And in fact, that's the case. Cisco AXL web service
|
|
0:34:12
|
bulk provisioning, serviceability, proxy, presence and sync
|
|
0:34:15
|
so let's just check all.
|
|
0:34:17
|
And say save.
|
|
0:34:19
|
And that's the reason that those ACLs weren't automatically
|
|
0:34:22
|
entered as well.
|
|
0:34:24
|
The ACL or ACEs, the Access Control Entries for both incoming
|
|
0:34:29
|
and outgoing for the CUCM servers.
|
|
0:34:35
|
So give this just a moment more for the services to
|
|
0:34:40
|
complete their activation.
|
|
0:34:45
|
It should be just about done.
|
|
0:34:54
|
And let's go ahead and just check feature services
|
|
0:34:56
|
from control center just to make sure they're not only activated, but
|
|
0:34:59
|
running. One shows deactivating, but that might not actually reflect
|
|
0:35:02
|
what it's really doing right now. It could have just been in a
|
|
0:35:05
|
temporary state of doing that. Sometimes services
|
|
0:35:09
|
activate, seem to be the activating, but then
|
|
0:35:11
|
ultimately are activated and running properly.
|
|
0:35:16
|
And indeed, we see that's the case. This has started and activated
|
|
0:35:19
|
as are the others. Ok, let's go back to Unified
|
|
0:35:24
|
Presence Administration
|
|
0:35:28
|
on the CUP server.
|
|
0:35:33
|
And let's go back and look at our security incoming and outgoing ACL.
|
|
0:35:36
|
And notice that it automatically created .10 and .20, so we can
|
|
0:35:41
|
actually delete our own CUCM publisher.
|
|
0:35:45
|
Now it didn't do anything for .30
|
|
0:35:48
|
so we did have to create that one, but the system
|
|
0:35:51
|
generated allow rule for the Pub and Sub
|
|
0:35:54
|
for incoming
|
|
0:35:56
|
as well as for outgoing is there. We can go ahead and
|
|
0:35:59
|
delete ours, not that they would probably
|
|
0:36:01
|
cause any interference. We also should now have
|
|
0:36:06
|
topology users. Again, we still would have only
|
|
0:36:10
|
seen those users once in CUCM we went to
|
|
0:36:13
|
System > Licensing> Capabilities
|
|
0:36:15
|
and actually did that capability assignment, but we do have
|
|
0:36:18
|
those two users JFord and BLinus.
|
|
0:36:25
|
Correct. Excellent.
|
|
0:36:29
|
And they're already assigned to a particular server.
|
|
0:36:32
|
So we don't need to do anything in regards to assign all
|
|
0:36:35
|
users or assign selected users, that would be if we were assigning
|
|
0:36:37
|
them to a different server in our -- a different CUP server
|
|
0:36:41
|
in our cluster.
|
|
0:36:46
|
Ok, so now we go back to CUPC and go back to
|
|
0:36:49
|
CTI gateway profile
|
|
0:36:53
|
actually let's go back to CUPC gateway server.
|
|
0:36:56
|
CTI gateway server rather.
|
|
0:36:58
|
And here are the automatically created ones.
|
|
0:37:03
|
And it's actually chosen a different port 2749
|
|
0:37:09
|
so we probably don't even need to have -- this is for
|
|
0:37:12
|
CTI TLS hosted -- actually no. That would be for
|
|
0:37:16
|
TLS, so that's for Transport Layer Security. It didn't create
|
|
0:37:19
|
or automatically generate the ones that we had already
|
|
0:37:22
|
generated.
|
|
0:37:24
|
Ok, we do need these for non-secure JTAPI
|
|
0:37:27
|
communication, so Application> Unified Personal Communicator>
|
|
0:37:31
|
CTI Gateway Profile -- actually let's go back to
|
|
0:37:36
|
Voice Mail Profile first
|
|
0:37:40
|
and here we have our voice messaging pilot
|
|
0:37:43
|
of 1850 or 3800
|
|
0:37:46
|
so rather than default, so that's good.
|
|
0:37:49
|
And BLinus is associated to this. The other user JFord is not
|
|
0:37:53
|
because they're associated to a different pilot.
|
|
0:37:57
|
Their user is associated to the line and device which has
|
|
0:38:03
|
actually a different pilot.
|
|
0:38:06
|
So we could set up something there, but the problem is
|
|
0:38:10
|
it's not Unity or Unity Connection, it's Unity
|
|
0:38:12
|
Express and CUPS doesn't have integration with that
|
|
0:38:16
|
so there's no need to set up a profile for the other.
|
|
0:38:19
|
Ok, so Application> CUPC let's go to CTI Gateway Profile
|
|
0:38:23
|
and finally stay there and we see that we've got
|
|
0:38:27
|
corporate headquarters, now here's actually a bit of a
|
|
0:38:30
|
problem. Because I manually created the CTI gateway
|
|
0:38:35
|
server for the 2748 standard TCP or UDP
|
|
0:38:44
|
JTAPI
|
|
0:38:45
|
and then it created the auto generated TLS
|
|
0:38:49
|
profile or TLS gateway server.
|
|
0:38:52
|
It also generated or auto generated the
|
|
0:38:55
|
CTI TLS or Transport Layer Security so JTAPI or CTI
|
|
0:39:02
|
running over Transport Layer Security
|
|
0:39:05
|
or SSL for each of the device pools that I already
|
|
0:39:10
|
had in my CUCM cluster. Branch 1, Branch 2
|
|
0:39:14
|
device pool corporate headquarter MOH
|
|
0:39:16
|
and just device pool corporate headquarter, but it did not create
|
|
0:39:19
|
normally it will create one for each device pool
|
|
0:39:22
|
for TLS, one for CTI UDP and one for CTI TCP
|
|
0:39:28
|
so I'm actually going to have to create some of these myself
|
|
0:39:36
|
or I could probably go back and do this in the proper
|
|
0:39:41
|
fashion. Let's go back to CTI gateway server.
|
|
0:39:45
|
And let's delete these two.
|
|
0:39:51
|
And let's go back to serviceability.
|
|
0:39:57
|
And let's just do a deactivation of all services.
|
|
0:40:10
|
And then once we've deactivated,
|
|
0:40:13
|
we will reactivate
|
|
0:40:16
|
and see if that UP sync agent really is the bit that's doing that.
|
|
0:40:25
|
We'll recreate those or if we have to manually
|
|
0:40:28
|
create them ourselves now.
|
|
0:40:31
|
In the meantime as soon as I go ahead and -- at this page
|
|
0:40:34
|
returns and I go ahead and click check all services to reactivate
|
|
0:40:40
|
and save so that we don't have to sit here and wait
|
|
0:40:43
|
for a long time while doing nothing. We'll go back
|
|
0:40:46
|
to our CUCM server and we'll go ahead and begin
|
|
0:40:50
|
to set up our soft phone.
|
|
0:40:52
|
So we already have Ben Linus's
|
|
0:40:57
|
Branch 1 Phone 1 desk phone
|
|
0:41:00
|
but we need to set up a soft phone.
|
|
0:41:04
|
So the way that we set up a CUPC soft phone mode
|
|
0:41:08
|
is we're going to go to add new
|
|
0:41:10
|
we're going to scroll down and not accidentally hit
|
|
0:41:13
|
mobile communicator, but personal communicator.
|
|
0:41:19
|
And the device name needs to be his user ID, so Ben Linus
|
|
0:41:24
|
probably a good idea to copy and paste and it
|
|
0:41:27
|
needs to be all caps and before that, it needs to be
|
|
0:41:30
|
UPC for Unified Personal Communicator, then the user
|
|
0:41:34
|
ID all caps
|
|
0:41:36
|
just like if we were doing mobile communicator, it would be UMC
|
|
0:41:40
|
and then all caps the user ID.
|
|
0:41:43
|
So Ben Linus CUPC soft phone.
|
|
0:41:49
|
Device pool, he's from Branch 1 we'll set all the things up
|
|
0:41:53
|
typically unless we have -- and this is we very well
|
|
0:41:56
|
may get into a situation where we have something
|
|
0:41:59
|
where our CUPC they're going to be travelling on -- connection through the
|
|
0:42:05
|
internet or VPN and they might be going through lossy networks
|
|
0:42:10
|
that is the internet or packet loss is possible and anything
|
|
0:42:14
|
greater than or equal to one percent packet loss
|
|
0:42:19
|
should use the ILBC codec. We may want to set up
|
|
0:42:23
|
another device pool with another region that has the
|
|
0:42:27
|
G.728 here we'll just go do this real quick
|
|
0:42:32
|
let's go create another region in a new tab here.
|
|
0:42:39
|
We will go to Branch 1 and maybe -- Ah! We can't do a copy.
|
|
0:42:42
|
So let's do add new and say region_CUPC
|
|
0:42:48
|
save
|
|
0:42:49
|
and between it and everything else, not that MOH would probably be
|
|
0:42:53
|
used that often even within CUPC, so from CUPC phone to
|
|
0:42:59
|
another CUPC phone, two different phones that might be
|
|
0:43:02
|
connecting and talking over the internet.
|
|
0:43:05
|
We might want to say G.728/ILBC
|
|
0:43:09
|
it's G.728 if the link loss type is at the default which
|
|
0:43:13
|
is low loss, but it selects the ILBC, the internet low bitrate codec
|
|
0:43:19
|
if we choose lossy.
|
|
0:43:22
|
So maybe we do that.
|
|
0:43:24
|
and probably change the video call bandwidth to whatever
|
|
0:43:28
|
whatever we were instructed and create a new device pool.
|
|
0:43:32
|
Actually let's go back
|
|
0:43:34
|
do find
|
|
0:43:37
|
create an -- grab the Brach 1 device pool and
|
|
0:43:40
|
do a copy and say Branch 1 CUPC
|
|
0:43:44
|
where the region is set to CUPC
|
|
0:43:48
|
just as an example.
|
|
0:43:49
|
And maybe we wouldn't have for instance locations.
|
|
0:43:53
|
I don't know, it depends on the lab requirements.
|
|
0:43:56
|
It depends on your corporate policy whatever
|
|
0:43:59
|
especially if locations are RSVP based, maybe we don't
|
|
0:44:02
|
want that because we won't be able to trigger RSVP based
|
|
0:44:05
|
locations over the internet. Again, it's all going to depend
|
|
0:44:08
|
on again what the lab says or in real life what your
|
|
0:44:11
|
corporate policy would say.
|
|
0:44:14
|
Ok, so then we want to close and come back here and I'm just going to
|
|
0:44:17
|
copy this and I pretty much have to go back
|
|
0:44:25
|
and add new because I opened a new tab, so
|
|
0:44:29
|
first of all, nothing that I had just crated in terms of region
|
|
0:44:33
|
and device pool were present in this we page when it loaded
|
|
0:44:37
|
but also if I hit save it wouldn't have updated anyhow.
|
|
0:44:45
|
So Branch 1 CUPC for instance.
|
|
0:44:48
|
The lab may not have you do anything like that, that's fine.
|
|
0:44:50
|
Whatever. Standard unified communicator SIP for the phone
|
|
0:44:54
|
button template, calling search space wherever you want them
|
|
0:44:56
|
to be able to call. Let's just say anywhere.
|
|
0:44:59
|
Again, it's going to have a line, so you could still do
|
|
0:45:02
|
line/device approach. MRGL is found through the
|
|
0:45:06
|
device pool, location same thing
|
|
0:45:11
|
owner user ID, very important
|
|
0:45:14
|
we're going to set to BLinus
|
|
0:45:17
|
primary phone, so this deals with licensing whether
|
|
0:45:20
|
it is viewed as an adjunct phone
|
|
0:45:23
|
if I have a primary phone, then it's not adjunct
|
|
0:45:26
|
so it takes up another license
|
|
0:45:29
|
DLU if it's -- it doesn't have a primary phone, then it isn't going
|
|
0:45:34
|
to be able to switch over to desk phone control mode very well.
|
|
0:45:36
|
So it's important I know which phone and I don't remember
|
|
0:45:39
|
which. I actually have them right in front of me, so I'll just hit
|
|
0:45:41
|
settings and five, Mac address ends in BAAE
|
|
0:45:46
|
I happened to be on the right one. Maybe I want calling
|
|
0:45:48
|
party to look just the same way, so Branch 1 phones
|
|
0:45:52
|
for localization.
|
|
0:45:54
|
CTI control important.
|
|
0:46:00
|
Presence group, let's leave that there.
|
|
0:46:04
|
Device security profile, non-secure. Might want to check
|
|
0:46:07
|
that to make sure that is truly non-secure.
|
|
0:46:10
|
Rerouting calling search space. Subscribe calling search space.
|
|
0:46:15
|
SIP profile.
|
|
0:46:18
|
And save.
|
|
0:46:23
|
And of course we'll do add a new DN.
|
|
0:46:25
|
This will be 2001
|
|
0:46:29
|
on the internal DNs.
|
|
0:46:34
|
So let's say save.
|
|
0:46:39
|
And it looks like we haven't filled in Ben Linus here.
|
|
0:46:43
|
We'll just do that real quick.
|
|
0:46:45
|
And then if I want some of -- first of all, the other settings
|
|
0:46:48
|
pertaining specifically to this line such as calling search space
|
|
0:46:51
|
maybe I want the same thing, maybe I don't. All those are
|
|
0:46:54
|
already going to be copied over; however, at the bottom
|
|
0:46:58
|
line text label display that might not be
|
|
0:47:02
|
I can easily go up to one of these devices say edit
|
|
0:47:04
|
line appearance, so jump over to the line as it pertains
|
|
0:47:07
|
to that device and go down to the bottom
|
|
0:47:11
|
and select update shared settings, so choose
|
|
0:47:15
|
whatever I want to update
|
|
0:47:18
|
or propagate and say propagate selected.
|
|
0:47:22
|
Now I can go back to line 2001 as it pertains
|
|
0:47:26
|
to UPC or the Unified Personal Communicator.
|
|
0:47:29
|
Go back to edit line appearance and
|
|
0:47:32
|
those settings show up here as well.
|
|
0:47:36
|
Go back to -- actually, I should also associate the
|
|
0:47:38
|
end user with that line.
|
|
0:47:45
|
Save.
|
|
0:47:47
|
And I should reset that soft phone
|
|
0:47:50
|
so that it can be used.
|
|
0:47:56
|
Ok, so now we have the CU -- or the UPC BLinus
|
|
0:47:59
|
for his soft phone set up as well.
|
|
0:48:02
|
It's SIP and status is unknown it hasn't logged in yet.
|
|
0:48:06
|
So let's go back to CUPS and the serviceability.
|
|
0:48:09
|
Go back to presence administration.
|
|
0:48:13
|
And we're going to go take a look to see if the
|
|
0:48:21
|
CTI gateway server
|
|
0:48:23
|
there we go. Now we have TCP for .10 and .20
|
|
0:48:29
|
auto created excellent. Application> CUPC>
|
|
0:48:32
|
Gateway Profile
|
|
0:48:35
|
and it created the TCP -- I'm sorry, it doesn't have a
|
|
0:48:38
|
UDP, I think I mentioned UDP, but it has a TCP and a TLS
|
|
0:48:42
|
for each device pool, so if we click on this
|
|
0:48:48
|
we see what the gateway primary and backup gateway
|
|
0:48:52
|
server so that's important.
|
|
0:48:55
|
We could have created these manually. We also
|
|
0:48:59
|
can make one default for the system. In this case,
|
|
0:49:01
|
our user is Branch 1, but we only have one that's really going to
|
|
0:49:05
|
be using this CTI gateway profile.
|
|
0:49:09
|
Again used for specifically Unified Personal Communicator only.
|
|
0:49:16
|
It doesn't have to do with IP phone messenger.
|
|
0:49:25
|
So we can also go down into this profile and again we want
|
|
0:49:28
|
TCP, not TLS for device pool Branch 1
|
|
0:49:31
|
actually, we may have
|
|
0:49:38
|
created that additional device pool, we did.
|
|
0:49:41
|
After...
|
|
0:49:44
|
Let's go up to here and CTI gateway server.
|
|
0:49:50
|
We actually created that additional device pool
|
|
0:49:53
|
after we had already enabled that service.
|
|
0:49:59
|
Let's see if just serviceability
|
|
0:50:05
|
feature services, we created the additional device pool for
|
|
0:50:08
|
Branch 1
|
|
0:50:12
|
let's just restart this sync agent.
|
|
0:50:16
|
We created it for Branch 1 ILBC or Branch 1 CUPC
|
|
0:50:19
|
is what we called it.
|
|
0:50:21
|
If this doesn't do it, then we'll just switch that
|
|
0:50:24
|
CUPC user back to just a Branch 1 device pool
|
|
0:50:27
|
and we'll simply have created the additional Branch 1
|
|
0:50:33
|
CUPC device pool as a demonstration of how we
|
|
0:50:36
|
might have that CUPC client or all CUPC clients
|
|
0:50:40
|
utilize the ILBC codec.
|
|
0:50:43
|
Back to presence administration.
|
|
0:50:48
|
Application> CUPC> Gateway Profile.
|
|
0:50:53
|
And it did. It grabbed the Branch 1 CUPC for TCP
|
|
0:50:58
|
so perfect. We're going to grab that and add
|
|
0:51:00
|
users to the profile.
|
|
0:51:02
|
And the user is BLinus.
|
|
0:51:08
|
And we'll save that.
|
|
0:51:10
|
So excellent.
|
|
0:51:13
|
Now we're going to go back to CUPC LDAP server.
|
|
0:51:18
|
Find that we don't have any.
|
|
0:51:20
|
We can LDAP host.
|
|
0:51:22
|
Let's call it MSAD
|
|
0:51:26
|
177.1.100.110
|
|
0:51:29
|
is the LDAP server that we have over here
|
|
0:51:36
|
for our directories.
|
|
0:51:40
|
Ben I don't remember if he's an executive or sales.
|
|
0:51:43
|
But let's just go ahead and -- so here was the server IP
|
|
0:51:49
|
and 389 TCP is fine, save.
|
|
0:51:54
|
And we're going to come back to Application> CUPC>
|
|
0:51:56
|
LDAP Profile
|
|
0:51:59
|
find that we don't have any.
|
|
0:52:01
|
Add new.
|
|
0:52:04
|
And we'll call this
|
|
0:52:06
|
whoops
|
|
0:52:10
|
INE executive
|
|
0:52:12
|
let's just actually call it INE.
|
|
0:52:15
|
Distinguished name
|
|
0:52:20
|
is going to be our administrator at ine.com -- actually admin at
|
|
0:52:25
|
ine.com works as well. CCIE Cisco
|
|
0:52:29
|
We would know this from our LDAP schema that we would have to be given.
|
|
0:52:35
|
And the search base.
|
|
0:52:37
|
We're actually just going to give it the entire island natural
|
|
0:52:42
|
exports OU and not limited to executive or sales or anything
|
|
0:52:46
|
like that, choose the LDAP server, make it the default for the system.
|
|
0:52:52
|
Save.
|
|
0:52:55
|
Add successful so this should eliminate the need to add
|
|
0:52:58
|
users to the profile, but we'll just go ahead and do that anyway.
|
|
0:53:04
|
Ok, I know it says update successful. I just like to hit
|
|
0:53:06
|
it again just for my safety and security. BLinus has
|
|
0:53:10
|
got that, so now we've pretty much finished
|
|
0:53:13
|
filling out everything except for -- I think we already did
|
|
0:53:17
|
settings. Yep, that was the first thing we did
|
|
0:53:20
|
TFTP and active directory, the only thing is we haven't gone to
|
|
0:53:23
|
user settings
|
|
0:53:26
|
so BLinus has a Voice mail profile.
|
|
0:53:30
|
We don't have conferencing, CTI and LDAP and that's because we
|
|
0:53:35
|
did user association as we went through those.
|
|
0:53:37
|
Otherwise, if we wouldn't have gone to user association
|
|
0:53:40
|
we could have just gone or come to this CUPC user
|
|
0:53:43
|
settings and assigned it all there.
|
|
0:53:46
|
So then we have the desk phone control. We've
|
|
0:53:48
|
already looked at first of all, application status enabling it
|
|
0:53:52
|
making sure CUCM CTI Pub and Sub or Sub and Pub
|
|
0:53:56
|
however we were instructed is there. We already put in the
|
|
0:53:59
|
password and created the user over on CUCM.
|
|
0:54:03
|
We also did this with IP phone messenger settings
|
|
0:54:05
|
as well, made sure it was on
|
|
0:54:10
|
user and pass cisco, cisco
|
|
0:54:12
|
or whatever you're instructed.
|
|
0:54:15
|
Desk phone control user assignment.
|
|
0:54:17
|
We still do have to assign BLinus
|
|
0:54:25
|
to enable desk phone control, this is just for CUPC.
|
|
0:54:29
|
So we don't need to do anything for JFord.
|
|
0:54:33
|
So now he has user assignment.
|
|
0:54:36
|
And also for desk phone control, we've got this
|
|
0:54:39
|
user troubleshooter. Now this is really useful. It says LCS
|
|
0:54:43
|
or OCS address which is Microsoft servers
|
|
0:54:46
|
but we can simply put in the IP of our CUP server.
|
|
0:54:51
|
And put in the user which we can either search or just
|
|
0:54:54
|
put in his user ID
|
|
0:54:58
|
and click submit. Now this is going to return
|
|
0:55:01
|
one error I can go ahead and tell you because
|
|
0:55:04
|
the access control list for incoming and outgoing
|
|
0:55:07
|
is not set to either all or wherever that particular CUPC
|
|
0:55:14
|
client might have an IP address it might actually be
|
|
0:55:16
|
running from.
|
|
0:55:18
|
That's not a problem because of the digest credentials that we set up
|
|
0:55:21
|
in CUCM for that end user.
|
|
0:55:26
|
However, it might bark at us and tell us that's a problem
|
|
0:55:29
|
whatever.
|
|
0:55:30
|
And here it's going to tell us what the tests are.
|
|
0:55:32
|
So verified desk phone control application is active.
|
|
0:55:36
|
It is. The user exists in the present database and
|
|
0:55:39
|
has been successfully synced from CUCM. It has.
|
|
0:55:42
|
The user's license for CUPS over in CUCM. It is.
|
|
0:55:46
|
Verify user's assigned for desk phone control here in CUPS. It is.
|
|
0:55:50
|
Can we retrieve device line information? We can.
|
|
0:55:54
|
Here's the information we retrieved. Desk phone control
|
|
0:55:58
|
application user name password matches.
|
|
0:56:00
|
Good, that's the CTI gateway user.
|
|
0:56:03
|
Desk phone control is running.
|
|
0:56:05
|
And the desk phone control application it just tells us is
|
|
0:56:09
|
a module that resides within the SIP proxy service.
|
|
0:56:11
|
That's running, so it's activated.
|
|
0:56:14
|
Is the proxy listening and type not set to UDP?
|
|
0:56:17
|
Good.
|
|
0:56:18
|
LCS/OCS is resolvable. That's our own selves.
|
|
0:56:22
|
We could have also put in probably CUPS 7 would have
|
|
0:56:25
|
actually been a little bit better test since that's how the user
|
|
0:56:30
|
will actually be logging in. Ok, still resolvable.
|
|
0:56:33
|
It's reachable, not just resolvable and it has a corresponding access
|
|
0:56:38
|
control entry. This is where it tells us there's a problem.
|
|
0:56:41
|
It'll take us over there. We don't need to worry about that.
|
|
0:56:43
|
Otherwise, this is telling us desk phone control
|
|
0:56:46
|
should work.
|
|
0:56:48
|
IP phone messenger other than the settings, there are
|
|
0:56:51
|
statuses that we can look at.
|
|
0:56:56
|
Ok,
|
|
0:56:58
|
and we can send broadcast messages to users that are logged in
|
|
0:57:01
|
or we also have the ability to create canned responses.
|
|
0:57:08
|
And so we can delete, modify, add new ones.
|
|
0:57:13
|
We don't have anything to do with meeting notification.
|
|
0:57:16
|
We don't need to worry about plug-ins. We should
|
|
0:57:18
|
be pretty much ready to go ahead and test
|
|
0:57:22
|
actual CUPC functionality.
|
|
0:57:26
|
So with that,
|
|
0:57:32
|
let's bring up our XP Utility machine
|
|
0:57:34
|
just like we would RDP into in the lab
|
|
0:57:38
|
maybe not using this cord client.
|
|
0:57:43
|
And let's bring up the Cisco Unified Personal Communicator.
|
|
0:57:51
|
So first of all, before we even do this we need to go
|
|
0:57:53
|
to run and type in Notepad.
|
|
0:57:57
|
c:\windows\system32 and I would just recommend
|
|
0:58:06
|
that you memorize this path if you're not already familiar
|
|
0:58:09
|
with it and you probably are. drivers\etsy\hosts
|
|
0:58:13
|
and memorize it so you can type it in just like this.
|
|
0:58:15
|
So notepad space is saying open Notepad application
|
|
0:58:20
|
and open this file with it.
|
|
0:58:23
|
And if we want, we can get rid of all this.
|
|
0:58:25
|
Whoops, where's my mouse?
|
|
0:58:27
|
It's up to us
|
|
0:58:34
|
and I'm going to put in 177.1.10.50
|
|
0:58:38
|
and say CUPS 7 and again, this is where I was saying
|
|
0:58:42
|
if you had a fully qualified domain name under...
|
|
0:58:45
|
whoops
|
|
0:58:48
|
if you had a fully qualified domain name when you did
|
|
0:58:50
|
show status when you SSHed in the server, you might want to
|
|
0:58:53
|
put in the fully qualified domain name so something like
|
|
0:58:56
|
cups7.cisco.com
|
|
0:59:00
|
not that it really mattered whether it was uppercase or lowercase.
|
|
0:59:03
|
And save it.
|
|
0:59:06
|
And close it.
|
|
0:59:08
|
And now our user name BLinus.
|
|
0:59:11
|
Password should be Cisco.
|
|
0:59:13
|
Let's go ahead and remember my password and automatically
|
|
0:59:15
|
log in and CUPS 7
|
|
0:59:21
|
And as we're doing this -- whoops
|
|
0:59:22
|
login failed
|
|
0:59:25
|
let's make sure we can ping
|
|
0:59:28
|
CUPS 7
|
|
0:59:31
|
we can
|
|
0:59:32
|
Ok, that's good.
|
|
0:59:43
|
And I'm actually not able to ping anything.
|
|
0:59:45
|
Or I mean I'm not -- I don't see the login.
|
|
0:59:48
|
So I'll just restart that.
|
|
0:59:55
|
Ok, well let's not do automatically login then.
|
|
1:00:04
|
Remember to always shut the CUPC down in between attempts
|
|
1:00:08
|
of logging in or whatever. Awesome, ok that's not
|
|
1:00:12
|
going to stay.
|
|
1:00:15
|
So can I just hit enter.
|
|
1:00:17
|
Cisco
|
|
1:00:23
|
let's try 177.1.10.50
|
|
1:00:33
|
Let's switch over here to the CUP server.
|
|
1:00:36
|
And I'm going to go log out.
|
|
1:00:38
|
And instead of CCM admin, I'm going to try to log in
|
|
1:00:43
|
as CCM user.
|
|
1:00:45
|
So the Unified Presence user page.
|
|
1:00:49
|
And try to log in as BLinus
|
|
1:00:51
|
and cisco.
|
|
1:00:55
|
And the password is invalid.
|
|
1:00:58
|
So
|
|
1:01:01
|
let's just make sure we're completely synced with our LDAP server.
|
|
1:01:06
|
Let's make sure it's reachable.
|
|
1:01:12
|
That looks like it worked.
|
|
1:01:16
|
Sales, I believe actually that's where Ben lives,
|
|
1:01:19
|
not that the user synchronization should matter too much as
|
|
1:01:24
|
much as the -- let's just make sure our end users are still here.
|
|
1:01:31
|
Yep, BLinus
|
|
1:01:34
|
is here, password is not being used.
|
|
1:01:37
|
LDAP authentication
|
|
1:01:40
|
ok, let's try
|
|
1:01:42
|
let's just go back to that end user and
|
|
1:01:44
|
verify -- I'm almost positive
|
|
1:01:47
|
that yep we have standard end user and CTI enabled.
|
|
1:01:51
|
So let's go ahead and log out of here CUCM.
|
|
1:01:55
|
And go to CCM user.
|
|
1:02:01
|
And try BLinus and Cisco.
|
|
1:02:06
|
Ok, we can log in here to CUCM, let's try the
|
|
1:02:10
|
presence again BLinus
|
|
1:02:14
|
and cisco
|
|
1:02:22
|
and it's giving us an error, so
|
|
1:02:27
|
let's go see what we might have set up incorrectly
|
|
1:02:31
|
on presence administration.
|
|
1:02:35
|
Let's look at an end user.
|
|
1:02:52
|
Oh ok, we only show it associated with one device.
|
|
1:02:55
|
I see.
|
|
1:02:56
|
So let's go back to CUCM, log out of the user
|
|
1:03:03
|
back in -- whoops
|
|
1:03:05
|
to the CCM admin page
|
|
1:03:11
|
as an administrator.
|
|
1:03:14
|
And let's go back to user management end user.
|
|
1:03:20
|
Look for BLinus.
|
|
1:03:24
|
And he's only controlling one device.
|
|
1:03:26
|
Let's give him device association control
|
|
1:03:30
|
over not only his
|
|
1:03:33
|
desk phone, but also his UPC.
|
|
1:03:40
|
His Cisco Unified Personal Communicator soft phone.
|
|
1:03:46
|
There we go.
|
|
1:03:50
|
Let's go back to device phone
|
|
1:03:57
|
for his Branch 1 Phone 1
|
|
1:04:02
|
Ok, his got the -- ID. Good.
|
|
1:04:05
|
Let's actually just disable extension mobility in case that's
|
|
1:04:08
|
causing any interaction, I don't think it is.
|
|
1:04:10
|
We can come back and enable it later
|
|
1:04:12
|
provided everything works fine.
|
|
1:04:14
|
We'll go back to list, look at is UPC
|
|
1:04:20
|
make sure that he has an owner user ID and
|
|
1:04:22
|
a primary phone. He does.
|
|
1:04:25
|
Good.
|
|
1:04:27
|
And let's reset
|
|
1:04:30
|
both his desk and UPC.
|
|
1:04:40
|
And let's go back to end user.
|
|
1:04:43
|
There we go, now he's got devices two.
|
|
1:04:52
|
So we his soft phone, Unified Personal Communicator and
|
|
1:04:56
|
his desk phone as well.
|
|
1:05:01
|
So now let's go ahead
|
|
1:05:06
|
and try to log out
|
|
1:05:11
|
whoops
|
|
1:05:13
|
CCM user, not CCMA user
|
|
1:05:16
|
and log in as BLinus.
|
|
1:05:19
|
Cisco
|
|
1:05:26
|
Ok, well let's go back to CUCM and temporarily let's
|
|
1:05:29
|
take off LDAP authentication.
|
|
1:05:34
|
So what we're doing here is by unticking the box for
|
|
1:05:38
|
use LDAP authentication, if we go back to our end users
|
|
1:05:43
|
BLinus for instance will have his password
|
|
1:05:45
|
set again, so we're still using LDAP for synchronization for
|
|
1:05:50
|
the users, but we're not
|
|
1:05:54
|
we are not passing authentication request off to
|
|
1:06:01
|
----
|
|
1:06:03
|
so let's just go ahead and enter manually cisco cisco.
|
|
1:06:07
|
And let's make sure his digest credentials
|
|
1:06:10
|
didn't happen to have changed.
|
|
1:06:13
|
Actually that could have something to do with it.
|
|
1:06:15
|
I think we entered those, but I could be wrong
|
|
1:06:17
|
I may not have -- no, I think we did because we
|
|
1:06:19
|
talked about
|
|
1:06:22
|
that specifically.
|
|
1:06:27
|
So let's try this now.
|
|
1:06:32
|
There we go, so we'll deal with the LDAP authentication
|
|
1:06:35
|
issue in a bit, but we can now log in
|
|
1:06:38
|
if we look for contacts
|
|
1:06:40
|
we could add contact incidentally
|
|
1:06:46
|
we could add new contacts here so that they would show up
|
|
1:06:49
|
in the domain cisco.com so as long as they are user
|
|
1:06:52
|
let's say if I do Jack Shep
|
|
1:06:55
|
hard
|
|
1:06:57
|
that's not going to work because that's not a valid name.
|
|
1:07:00
|
However, -- herd
|
|
1:07:02
|
is a valid name and so that would be a contact
|
|
1:07:06
|
that would show up
|
|
1:07:08
|
in his CUPC client
|
|
1:07:10
|
let's go ahead and go back to our desktop.
|
|
1:07:16
|
And we'll shut down and pull up Cisco Unified Personal Communicator again.
|
|
1:07:19
|
BLinus cisco
|
|
1:07:24
|
and now I will go ahead and hit automatically log in
|
|
1:07:26
|
but I want to login to CUPS 7
|
|
1:07:31
|
login and we should always do help and show server
|
|
1:07:34
|
health as we're logging in.
|
|
1:07:38
|
So this is going to show us first of all the TFTP configuration
|
|
1:07:42
|
was contactable and downloaded.
|
|
1:07:44
|
Presence is still contacting, ok, it was green contacted.
|
|
1:07:49
|
So we're good,
|
|
1:07:50
|
soft phone we're connected
|
|
1:07:54
|
to our primary provider and Voice mail failed to connect
|
|
1:07:58
|
no user credentials, no problem here
|
|
1:08:04
|
and we'll go to file preferences
|
|
1:08:07
|
and we'll come over here to accounts
|
|
1:08:10
|
for voice messaging and we need to enter the account
|
|
1:08:13
|
what was the account name? Let's go take a look
|
|
1:08:16
|
let's open up a new window
|
|
1:08:18
|
or a new tab
|
|
1:08:19
|
for Cisco Unified -- or sorry Cisco Unity Connection
|
|
1:08:25
|
administration interface and we still have to go to this
|
|
1:08:28
|
particular user's -- let's make sure the user exists
|
|
1:08:31
|
first BLinus does.
|
|
1:08:34
|
We need to go check out what class of service they have.
|
|
1:08:37
|
They probably have the default right now.
|
|
1:08:41
|
Voice mail user COS versus the only other one currently
|
|
1:08:45
|
which is the system, so we'll go into class of service here
|
|
1:08:48
|
on the left, Voice mail user COS
|
|
1:08:51
|
and we will say -- it looks like we've already done this.
|
|
1:08:53
|
Allow user to access Voice mail using an IMAP client
|
|
1:08:58
|
except on private messages or -- all whatever we want.
|
|
1:09:03
|
Let's say save, so it was already enabled.
|
|
1:09:10
|
User of BLinus.
|
|
1:09:16
|
We had gone to -- let's just do change password.
|
|
1:09:21
|
And this is for the -- is this web application or Voice mail?
|
|
1:09:27
|
Well, I think we set both of them to 12345
|
|
1:09:30
|
so we can certainly test it out.
|
|
1:09:33
|
So let's go back to our RDP XP machine, say BLinus
|
|
1:09:38
|
and 12345
|
|
1:09:42
|
ok,
|
|
1:09:43
|
and we'll go ahead and shut this down again.
|
|
1:09:46
|
Exit.
|
|
1:09:49
|
We'll open it back up.
|
|
1:09:52
|
Show server health.
|
|
1:09:53
|
We're trying to connect.
|
|
1:09:58
|
It's -- presence server.
|
|
1:10:02
|
Good. Soft phone mode is good. Failed to connect
|
|
1:10:04
|
invalid credentials or account locked.
|
|
1:10:07
|
Ok,
|
|
1:10:08
|
so let's see if our -- let's just go back
|
|
1:10:11
|
to our Unity Connection and let's set our Voice mail password to
|
|
1:10:14
|
12345
|
|
1:10:18
|
but it is most likely our
|
|
1:10:22
|
web application password and we'll set that to cisco
|
|
1:10:26
|
well, you know what, we've already set it to 12345
|
|
1:10:29
|
on the other side. Again, in the lab you would do
|
|
1:10:31
|
whatever you were supposed to do. Let's set it to cisco.
|
|
1:10:36
|
That way we can be sure to know which user pass we need.
|
|
1:10:41
|
So let's do preferences.
|
|
1:10:43
|
Accounts.
|
|
1:10:45
|
BLinus.
|
|
1:10:46
|
Let me just retype that in make sure that I typed it in properly.
|
|
1:10:50
|
Cisco
|
|
1:10:51
|
apply
|
|
1:10:53
|
ok,
|
|
1:10:58
|
exit, open it back up.
|
|
1:11:02
|
Help show server health.
|
|
1:11:11
|
I can expand this general as well once we're logged in
|
|
1:11:14
|
we'll see Jack Shepherd that we added and this time
|
|
1:11:17
|
Voice mail looks like it succeeded, so it is the
|
|
1:11:19
|
web application.
|
|
1:11:21
|
And we can see more information on each of the
|
|
1:11:23
|
specific sub configuration sections
|
|
1:11:29
|
as we drill down into these on the left, but all is really good
|
|
1:11:32
|
as a basic just to see if everything's working and
|
|
1:11:34
|
then if something's not working if it doesn't give you a real easy
|
|
1:11:38
|
troubleshooting like that said Voice mail invalid
|
|
1:11:42
|
password something like that which was pretty easy to understand.
|
|
1:11:44
|
We could go and click on each of these individual let's say
|
|
1:11:48
|
desk phone CTI or whatever and gather more information about it.
|
|
1:11:54
|
So right now desk phone control is not active
|
|
1:11:56
|
we can come up here from -- well first of all
|
|
1:11:58
|
we can just use this to try to dial.
|
|
1:12:02
|
Let's try to go off hook and place a call to Jack Shepherd
|
|
1:12:08
|
now it's going to go to look his work phone
|
|
1:12:11
|
so that may not necessarily be what we want.
|
|
1:12:16
|
Let's do add a new contact
|
|
1:12:19
|
and let's search
|
|
1:12:23
|
let's search for J and notice that we are searching the LDAP
|
|
1:12:28
|
directory, everything works fine.
|
|
1:12:32
|
So we can create new groups. We can manually
|
|
1:12:35
|
add a new contact, but that's not going to show any presence
|
|
1:12:37
|
information, so right now because we added Jack
|
|
1:12:41
|
already from our user interface or we could add it here
|
|
1:12:43
|
if we're placing a call it's to the synchronized
|
|
1:12:47
|
phone from the LDAP.
|
|
1:12:49
|
And even though IP phone was the category
|
|
1:12:53
|
that the Microsoft LDAP had, it's in the globalized format.
|
|
1:12:56
|
This may or may not work depending on how we have
|
|
1:12:58
|
our system set up.
|
|
1:13:00
|
We always can of course go off line and just do let's say
|
|
1:13:03
|
1001 and call.
|
|
1:13:09
|
And you can probably hear it ringing.
|
|
1:13:13
|
There we go. It's calling from Ben Linus from 2001
|
|
1:13:17
|
even though we see Ben Linus's we see his little line right here
|
|
1:13:22
|
and I probably didn't do it fast enough, so it's actually
|
|
1:13:25
|
already -- it's now in Voice mail.
|
|
1:13:31
|
But if I do...
|
|
1:13:34
|
just double click this again.
|
|
1:13:40
|
I can see that Ben Linus has a status of off hook
|
|
1:13:45
|
that's because it's a shared line.
|
|
1:13:48
|
Ok, but it's not controlling the desk phone mode
|
|
1:13:53
|
at this particular time, so he's leaving a Voice mail
|
|
1:13:55
|
-- XP machine.
|
|
1:14:00
|
Ok, can we see status from Jack Shepherd?
|
|
1:14:05
|
Let's go ahead and go off hook on Jack Shepherd's primary line.
|
|
1:14:16
|
And we'll go back on hook.
|
|
1:14:23
|
And we're not seeing any status information.
|
|
1:14:25
|
So we'll take a look at that in just a bit.
|
|
1:14:29
|
The reason actually we're not seeing any status information
|
|
1:14:31
|
has to do with the fact that the synchronized phone
|
|
1:14:35
|
is specifically pointed to a DN that is a wrong DN.
|
|
1:14:43
|
So we're kind of trying to watch a DN that doesn't exist
|
|
1:14:47
|
or even any of his DNs work phone or business phone
|
|
1:14:50
|
or anything else.
|
|
1:14:52
|
So -- no we don't want to send an e-mail.
|
|
1:14:57
|
Do we have any Voice mails for Ben? We don't.
|
|
1:14:59
|
Let's go ahead and have Jack actually dial over to Ben
|
|
1:15:04
|
where it not only rings on Ben's desk phone
|
|
1:15:09
|
but it also rings or should be ringing -- there we go.
|
|
1:15:12
|
Answer, answer with video.
|
|
1:15:16
|
whoops
|
|
1:15:25
|
I think I killed my RDP session. Hey Ben, we're just leaving a
|
|
1:15:28
|
voice mail for you from Jack for MWI. Talk to you later.
|
|
1:15:39
|
Ok,
|
|
1:15:41
|
let's go back and connect again
|
|
1:15:42
|
in full screen mode.
|
|
1:15:49
|
And we see that we missed a call from Jack Shepherd.
|
|
1:15:52
|
--take a little while for the MWI to show up.
|
|
1:15:54
|
So we'll just wait for that.
|
|
1:15:57
|
Actually in the meantime, we'll just go ahead and go over
|
|
1:15:59
|
to desk phone mode.
|
|
1:16:01
|
And we'll see over here in status health soft phone
|
|
1:16:03
|
is not active, there we go desk phone it was partially and now it's fully connected.
|
|
1:16:09
|
And in the meantime we saw our MWI populate.
|
|
1:16:12
|
So we can go ahead and open the voice mail, play the
|
|
1:16:15
|
voice mail whatever we want.
|
|
1:16:18
|
We do have over on Benjamin Linus's desk phone
|
|
1:16:25
|
we should see
|
|
1:16:29
|
go off hook and then go back on hook and try to update the screen -- there we go
|
|
1:16:33
|
we've got the little message icon right next to his
|
|
1:16:36
|
line text label and also if we go over to hardware
|
|
1:16:40
|
we see message waiting is set to yes.
|
|
1:16:41
|
So if we go back here we could just say -- you know what, I don't even want to
|
|
1:16:45
|
listen to it let's just delete that voice mail. It's gone.
|
|
1:16:49
|
And if we come back to the phone give it a little bit of time
|
|
1:16:51
|
and it should synchronize.
|
|
1:16:53
|
And here we go.
|
|
1:16:55
|
That envelope is gone. Go back to hardware.
|
|
1:16:58
|
Message waiting is set to no so we've got full control
|
|
1:17:01
|
of -- through IMAP of our Unity Connection
|
|
1:17:06
|
mail store, we've got desk phone control mode.
|
|
1:17:09
|
So if I go off hook now and dial 1001
|
|
1:17:15
|
it's not only calling, but if I take a look
|
|
1:17:18
|
it's actually my desk phone that I'm controlling
|
|
1:17:21
|
to call over to Jack's phone.
|
|
1:17:24
|
And I can control it from either one
|
|
1:17:26
|
from either side.
|
|
1:17:32
|
Ok, so everything looks good at this point.
|
|
1:17:34
|
And we've got our CUPC fully set up and working.
|
|
1:17:40
|
No problems at all. Actually, the only problem
|
|
1:17:42
|
that we had was the authentication. Let's go back to CUCM
|
|
1:17:46
|
and enable the LDAP authentication again.
|
|
1:17:52
|
And we knew that could log in from the CUCM side
|
|
1:17:57
|
in CCM user as BLinus and cisco
|
|
1:18:01
|
so it's not the password over in the LDAP directory
|
|
1:18:04
|
that's not working properly.
|
|
1:18:09
|
Let's see if we shut this down.
|
|
1:18:14
|
And we'll try to log in again from over here.
|
|
1:18:17
|
Yep, we're having a problem logging in through the LDAP
|
|
1:18:20
|
server so it might be just that this version of CUPS
|
|
1:18:27
|
CUP server isn't going to allow LDAP authentication.
|
|
1:18:31
|
We do actually over here in -- if we log out
|
|
1:18:37
|
and log back into CCM admin
|
|
1:18:42
|
from CUPS, so the Unified Presence administration.
|
|
1:18:47
|
We had an LDAP server profile, we didn't have any
|
|
1:18:50
|
LDAP authentication
|
|
1:18:55
|
whoops
|
|
1:19:00
|
so let's just untick this
|
|
1:19:03
|
save.
|
|
1:19:07
|
Try to login again
|
|
1:19:09
|
and it looks like we're just not going to be able to
|
|
1:19:11
|
use so they wouldn't ask you LDAP authentication in this
|
|
1:19:15
|
particular version
|
|
1:19:18
|
routing through CUCM.
|
|
1:19:25
|
Although it could actually just have to do with my
|
|
1:19:27
|
host file, it's possible
|
|
1:19:30
|
let's add this real quick.
|
|
1:19:35
|
What did we call it? I think we called it MS AD
|
|
1:19:40
|
177.1.10 or 100.110
|
|
1:19:43
|
I don't think that's it.
|
|
1:20:14
|
Nope.
|
|
1:20:22
|
And so everything's fine as long as we're not using
|
|
1:20:24
|
LDAP authentication. I don't even think you're probably going to
|
|
1:20:26
|
run into LDAP in the lab environment. The possibility
|
|
1:20:30
|
is there, but it's also very possible and even probable
|
|
1:20:34
|
that they would have you do one such as LDAP synchronization
|
|
1:20:36
|
but not authentication.
|
|
1:20:41
|
And we have a question. Question is,
|
|
1:20:43
|
"Can we control an IP Communicator -- or just CUPC as a phone by itself?"
|
|
1:20:52
|
So I think you're saying could my desk phone from the
|
|
1:20:56
|
CUPC, could my desk phone be an IP Communicator.
|
|
1:20:59
|
Is that what you're asking?
|
|
1:21:01
|
So soft phone mode is standalone and desk phone mode is an IP
|
|
1:21:06
|
Communicator? I'm -- honestly I don't know the answer to that
|
|
1:21:11
|
but I would be very skeptical that it would allow you
|
|
1:21:15
|
to be running -- first of all, if you were controlling
|
|
1:21:19
|
CUPC -- I'm sorry, CIPC from CUPC -- let me think about this.
|
|
1:21:26
|
You would really -- I mean the idea would be that
|
|
1:21:30
|
this CUPC would be running on a laptop maybe and your
|
|
1:21:35
|
CIPC would be running on maybe a desktop, so a different
|
|
1:21:38
|
computer because otherwise, -- want to control CIPC
|
|
1:21:42
|
if it's on the same physical machine as your CUPC
|
|
1:21:47
|
since your CUPC has pretty much all of the
|
|
1:21:50
|
functionality built in.
|
|
1:21:54
|
Oh! You said -- Oh, sorry you re-clarified, you mean
|
|
1:21:56
|
can you use CUPC as a standalone phone.
|
|
1:21:59
|
Absolutely, so that's what soft phone mode
|
|
1:22:01
|
does. When I go to soft phone mode, it is 100 percent
|
|
1:22:05
|
its own individual phone, in fact, it's a shared line with your
|
|
1:22:10
|
desk phone. When I'm using desk phone control mode
|
|
1:22:14
|
I'm not using a shared line, I'm actually controlling my desk
|
|
1:22:18
|
phone, this is just a user interface, another interface just
|
|
1:22:23
|
like my keypad is another interface and my handset is
|
|
1:22:25
|
another interface, but the RTP -- when I'm in desk phone control
|
|
1:22:29
|
mode as I am right now, the RTP stream does not come
|
|
1:22:32
|
to my laptop. When I'm in soft phone mode, the RTP
|
|
1:22:37
|
stream comes to my laptop if I place the call or answer the
|
|
1:22:41
|
call here at my laptop or desktop wherever
|
|
1:22:45
|
but to this computer.
|
|
1:22:46
|
And so at this point, it is a shared line with my desk phone.
|
|
1:22:49
|
And it's a completely independent standalone fairly fully functional
|
|
1:22:55
|
certainly more so in 8 and later versions
|
|
1:23:00
|
of the CUPC client, in fact, CUPC had a major capabilities
|
|
1:23:06
|
upgrade from 7 to 8 and we'll be covering
|
|
1:23:10
|
that real shortly for anyone that cares on the -- and
|
|
1:23:14
|
probably by the time you're watching the recording
|
|
1:23:16
|
is already well covered on the CCNA and actually
|
|
1:23:20
|
mainly the CCNP voice -- the apps -- what is it? The
|
|
1:23:28
|
I believe it's V apps or C apps
|
|
1:23:32
|
exam test and
|
|
1:23:35
|
and -- information that we're covering.
|
|
1:23:39
|
But it is a completely standalone computer. No problem
|
|
1:23:41
|
good question.
|
