|
0:00:14
|
Let's go to device defaults
|
|
0:00:18
|
and that the phone button template for the four
|
|
0:00:21
|
that we already took a look at, we could have done here
|
|
0:00:23
|
and now we will do, for 61 SIP and Skiny
|
|
0:00:27
|
and then 61 GE SIP and Skinny
|
|
0:00:30
|
So module 3, module 3, module 3 enhanced and module 3 enhanced
|
|
0:00:36
|
Ok, hope to save
|
|
0:00:41
|
The address successful
|
|
0:00:44
|
We already mentioned that we already took care of the
|
|
0:00:46
|
soft key template by choosing the
|
|
0:00:49
|
use the soft key, the default soft key
|
|
0:00:52
|
and then common phone profile
|
|
0:00:57
|
The standard common phone profile is the default that's used by all the phones
|
|
0:01:03
|
and we'll set the DND option to Call Reject
|
|
0:01:06
|
and Incoming Call Alert to Disable.
|
|
0:01:09
|
Save and make sure it update successfully, it does.
|
|
0:01:13
|
Now we can go on to our next task which will be
|
|
0:01:17
|
to auto-register of Skinny phones
|
|
0:01:20
|
So here were instructed and tasked 114 to auto-register all IP phones
|
|
0:01:24
|
both those in front of you and
|
|
0:01:25
|
attach directly to the rack as per your topology
|
|
0:01:28
|
So this is assuming you have hardware phones or
|
|
0:01:31
|
maybe you're using a software based phone
|
|
0:01:35
|
in terms of maybe IP blue
|
|
0:01:38
|
again noting that it won't do many of the features needed
|
|
0:01:42
|
to be tested by the lab, many of the soft keys and it will not do globalization
|
|
0:01:49
|
or you could use VOIP integration as a remote control tool for the once
|
|
0:01:55
|
on the rack if you don't have any in front of you when you are studying
|
|
0:01:58
|
Auto-register those phones to the CUCMSub CPE
|
|
0:02:03
|
as Skinny-based firmware phones except, so all IP phones except
|
|
0:02:09
|
the IP Phone at Corporate Headquarter attached to the 3560 (SW1)
|
|
0:02:14
|
port Fa0/2. Do not allow that phone to register at this time
|
|
0:02:19
|
Well, I have some use, if we already, back in
|
|
0:02:27
|
Well let's see, first back in task 11 activated all the services on the Pub and Sub
|
|
0:02:33
|
into, made the Sub priority CPE over the Pub
|
|
0:02:37
|
and then in three enabled auto-registration and gave it a range
|
|
0:02:42
|
Our phones have probably all already been
|
|
0:02:46
|
auto-registered to our system by the time we are getting down here to
|
|
0:02:51
|
Task 114, let's go check.
|
|
0:02:55
|
I would venture to guess that they have them
|
|
0:02:58
|
and they're sitting in front of me so that I can see that I have them
|
|
0:03:01
|
I watch them register quite some time ago.
|
|
0:03:03
|
So they're all registered, so we're going to go ahead and
|
|
0:03:06
|
at this point since they didn't get
|
|
0:03:08
|
necessarily all those default features
|
|
0:03:11
|
We're going to go ahead and delete them all but before we do,
|
|
0:03:15
|
we were instructed to make sure that the one phone
|
|
0:03:19
|
attached to Corporate Headquarter SW1
|
|
0:03:27
|
port Fa0/2
|
|
0:03:31
|
not register, now it may have already register as I mentioned but
|
|
0:03:35
|
We'll go ahead and
|
|
0:03:43
|
We'll go ahead and do Show CDP neighbor
|
|
0:03:47
|
this there under Fa0/2
|
|
0:03:49
|
We already have DHCP and TFTP options
|
|
0:03:52
|
and default gateway setup from
|
|
0:03:54
|
the module
|
|
0:03:55
|
on Monday for network infrastructure
|
|
0:03:58
|
So we'll dive into interface Fa0/2 and just shut it down
|
|
0:04:03
|
and we don't have tor mon turned on so we'll do that
|
|
0:04:06
|
We probably just lost the power
|
|
0:04:09
|
message but we'll go ahead and show power in line
|
|
0:04:13
|
We'll see that there's no power this time, there was
|
|
0:04:17
|
Show CVP neighbor, doesn't show up in the table anymore
|
|
0:04:21
|
show IP interface brief
|
|
0:04:23
|
with an output modifier Pipe 2 include 0/2
|
|
0:04:30
|
You see it and all the 0/20's is administratively down so we're good so far
|
|
0:04:35
|
Ok, so now we'll go ahead and delete all the phones
|
|
0:04:42
|
Cause we gave a DN auto-registration range of
|
|
0:04:46
|
a thousand DN's, we should have plenty enough.
|
|
0:04:51
|
And all the phones are clearing in front of me, I'll go ahead and fire up the
|
|
0:04:56
|
control remote phone
|
|
0:05:05
|
VOIP integration control application
|
|
0:05:09
|
which won't control them until they register to CUCM,incidentally
|
|
0:05:16
|
need some sort of a CTI control mechanism like the administrative
|
|
0:05:21
|
user or AXL or
|
|
0:05:26
|
a specific user-tied to device association
|
|
0:05:30
|
In fact we were told that we needed to create a user to test something
|
|
0:05:33
|
so while those phones are registering,
|
|
0:05:36
|
we'll take a little bit of time, let's go and create and N user
|
|
0:05:39
|
but we won't talk too much about all the features in Users
|
|
0:05:41
|
because that's we are going to talk about
|
|
0:05:43
|
in the module tomorrow
|
|
0:05:45
|
make sure they are ready
|
|
0:05:47
|
They are not, so we'll create one called
|
|
0:05:51
|
HQ Phone 1
|
|
0:05:54
|
actually let's make it Phone 2
|
|
0:05:57
|
Password, surprise surprise, it's gonna be Cisco
|
|
0:06:01
|
or INE, pin 12345
|
|
0:06:04
|
although we don't have to put that information in
|
|
0:06:07
|
and HQ Phone 2
|
|
0:06:15
|
Enough
|
|
0:06:20
|
In now, let's check our phones
|
|
0:06:23
|
see if they are registered
|
|
0:06:26
|
and we have 12345
|
|
0:06:29
|
of them registered which are five of the ones that
|
|
0:06:33
|
I have in front of me, now look
|
|
0:06:36
|
we don't have IP address or status
|
|
0:06:39
|
but I can see in front of and you can probably hear
|
|
0:06:48
|
phones are registered, in fact you can see
|
|
0:06:53
|
the phone registered
|
|
0:07:01
|
up here
|
|
0:07:05
|
there are number of phones that are registered so I'll just grab 5011
|
|
0:07:11
|
that one phone unregistered
|
|
0:07:14
|
Please select another device, wait a minute
|
|
0:07:17
|
it's unregistered, I can tell it's registered and you can even see it
|
|
0:07:21
|
Why does it show up it's unregistered from remote control
|
|
0:07:26
|
and why did you just here it actually ringing for placing a call
|
|
0:07:35
|
anyone wanna speak up and give me idea from
|
|
0:07:39
|
troubleshooting from yesterday
|
|
0:07:43
|
Web UI and command line module,
|
|
0:07:45
|
what could be the problem with the status
|
|
0:07:49
|
or IP addresses of the phones if they actually show up as registered
|
|
0:07:53
|
is that the database replication issue, or there's something else
|
|
0:08:05
|
one person answered properly
|
|
0:08:09
|
Anyone else?
|
|
0:08:20
|
What service do I need to restart?
|
|
0:08:22
|
Is it the CCM service?
|
|
0:08:29
|
That's correct, it's the RIS database service, now under serviceability
|
|
0:08:35
|
Where do I find it?
|
|
0:08:37
|
Is it under control center feature services or control center network services?
|
|
0:08:49
|
That's correct, it's under Network Services and
|
|
0:08:53
|
which server do I need to restart if for?
|
|
0:08:57
|
Everyone should be registered to the Sub
|
|
0:09:00
|
and if I in front of me although you can't see it
|
|
0:09:03
|
remote control because it doens't show up as registered
|
|
0:09:05
|
which is by the way, the reason that this
|
|
0:09:08
|
phone remote control lab doesn't see it registered because
|
|
0:09:12
|
Call Manager RIS doesn't see it
|
|
0:09:15
|
but if we know that we setup our CPE
|
|
0:09:19
|
primary or the sub
|
|
0:09:22
|
or the secondary for the pub
|
|
0:09:24
|
then on the phone, you have it in front of you, you could go and see
|
|
0:09:29
|
Unified CM 1 is active and Unified CM 2 is standby so select CM 1
|
|
0:09:33
|
and see that the IP address is 177.1.10.20
|
|
0:09:38
|
so it is the sub that I actually need to restart it for
|
|
0:09:42
|
Now the pub may also need restarting, it's a good idea to restart both
|
|
0:09:46
|
as someone pointed out but
|
|
0:09:48
|
I at least need to restart it for
|
|
0:09:51
|
the sub so that's what I'm gonna go ahead and do
|
|
0:09:54
|
Also not this is the restart, this is refresh
|
|
0:09:58
|
Now it's over long enough, we'll show you that
|
|
0:10:06
|
Let's wait for this to restart
|
|
0:11:35
|
So the restart is successful, so I'll go ahead and go back to Administration
|
|
0:11:42
|
and to revise Phone
|
|
0:11:44
|
see that they hopefully now are all
|
|
0:11:47
|
registered to 20 with their IP addresses, good
|
|
0:11:53
|
and we have 6 phones
|
|
0:11:56
|
which I have 5 plus a PSTN phone in front of me so that leaves the sixth phone for
|
|
0:12:09
|
phone for the rack which I can tell by the IP address is 1772
|
|
0:12:14
|
and control now works.
|
|
0:12:23
|
Let's go ahead and start a new remote control
|
|
0:12:32
|
Grab 5012 as well
|
|
0:12:36
|
and in the mean time I'm going to go ahead and dive into each phone
|
|
0:12:43
|
Let's start with 11, well actually, in front of me it doesn't really matter
|
|
0:12:50
|
Let's call it headquarter phone 2, Corporate Headquarter Phone 2
|
|
0:12:59
|
and it's got the proper device pool, it's got the new phone button template
|
|
0:13:03
|
it doesn't have a soft key template, but note it's not a required option
|
|
0:13:09
|
but there are soft keys assigned to the phone
|
|
0:13:12
|
it's because it's the default soft key template
|
|
0:13:15
|
none indicate default and we are already
|
|
0:13:19
|
indicated the default at the soft key template, the new one that we created
|
|
0:13:24
|
using the standard common phone profile
|
|
0:13:27
|
So we'll see if that takes because
|
|
0:13:30
|
down here were we can explicitly define "Do Not Disturb" settings
|
|
0:13:36
|
It still sows Ringer off or Common Phone Profile
|
|
0:13:42
|
None uses the Common Phone Profile
|
|
0:13:45
|
So we'll update that
|
|
0:13:47
|
We have to update the phone before we can update the lines
|
|
0:13:52
|
We were not actually told to update the lines
|
|
0:13:54
|
So we'll just go ahead and leave them as, we'll go ahead and change them
|
|
0:14:00
|
1002, we don't have any partitions or calling search bases so we don't need to
|
|
0:14:06
|
mess any of that, actually because we're going to test forwarding
|
|
0:14:11
|
let's go ahead and test or go ahead and set rather
|
|
0:14:16
|
Forward, no answer. We don't have Voicemail setup
|
|
0:14:20
|
so we'll set it to 3002
|
|
0:14:24
|
and also, not for No Coverage but for Busy
|
|
0:14:30
|
5002, now we would to, we'll talk about this later. We would need
|
|
0:14:34
|
specify the Calling Search Base if they were any
|
|
0:14:36
|
but the null or default Calling Search Base is
|
|
0:14:43
|
well is the default and does contain the
|
|
0:14:45
|
only partition that's in the system so far which is the null
|
|
0:14:49
|
or default, none partition
|
|
0:14:52
|
So we're fine there in terms of a forward and also in terms of
|
|
0:15:02
|
our primary Calling Search Base to be able to call any other phones
|
|
0:15:10
|
So we'll set 5012
|
|
0:15:17
|
Corporate Headquarter Phone 1
|
|
0:15:23
|
Well, save that
|
|
0:15:31
|
1001, tab off of it before we save
|
|
0:15:37
|
So that it can refresh the whole
|
|
0:15:39
|
page and make sure it's not a shared line and if so update
|
|
0:15:42
|
everything has a shared line
|
|
0:15:48
|
and 5013 is in front of me as my
|
|
0:15:57
|
to phone 1
|
|
0:16:00
|
So we will assign the Device Pool accordingly
|
|
0:16:05
|
No, I can leave the location provided that the
|
|
0:16:09
|
Device Pool is set so I can click on "View Details" so I can see what that
|
|
0:16:14
|
bring the window over, we bet Device Pool has set
|
|
0:16:17
|
for a location which is branch 2, proper date time group, etc.
|
|
0:16:21
|
So that will be fine
|
|
0:16:30
|
PSTN to 3000
|
|
0:16:35
|
that was phone 1
|
|
0:16:47
|
5009 as my branch 2 phone 2
|
|
0:16:56
|
Device Pool
|
|
0:17:06
|
5002
|
|
0:17:22
|
5010
|
|
0:17:30
|
1 phone 1, so we'll change Device Pool to branch 1
|
|
0:17:42
|
and the number to 2001
|
|
0:17:51
|
Now these phones are actually updating live in front of me
|
|
0:17:53
|
I could press restart but actually
|
|
0:17:56
|
and we can certainly see that
|
|
0:17:58
|
with actually this don't have refresh set to
|
|
0:18:02
|
any rate so let's go ahead and turn auto-refresh on
|
|
0:18:14
|
One is refreshing properly, the other ones
|
|
0:18:19
|
not exactly wanting to cooperate, let's just close that down
|
|
0:18:37
|
started up again, so we've already got headquarter phone 1, now we want phone 2
|
|
0:18:42
|
Control it.
|
|
0:18:46
|
and last but not least the phone that was not
|
|
0:18:49
|
in front of us, at the rack and that is
|
|
0:18:55
|
branch 1, phone 2 then Device Pool for branch 1
|
|
0:19:24
|
So all of our phones have been re-numbered
|
|
0:19:27
|
Do note that earlier we were told to
|
|
0:19:30
|
delete all unused DN's
|
|
0:19:35
|
So let's click actually unassigned DN's to find
|
|
0:19:41
|
and we will just click on delete
|
|
0:19:44
|
all found items which only shows up for unassigned DN's
|
|
0:19:48
|
Now that's not always safe to do, there are many times
|
|
0:19:52
|
in a installation, possibly even your lab if you use them for the
|
|
0:19:57
|
that you might want to create dummy DN's
|
|
0:20:00
|
In previous versions of CUCM
|
|
0:20:02
|
before we have the ability to create just the DN
|
|
0:20:06
|
Directory Number separate from an actual phone line
|
|
0:20:11
|
We used to create CTI route points mainly because
|
|
0:20:14
|
Sounded good, route point had to load device weight
|
|
0:20:18
|
and it had a DN
|
|
0:20:19
|
and have to load device weight, so now we can just
|
|
0:20:22
|
create DN's without actually taking up a CTI route point
|
|
0:20:25
|
not assigning to a device like a route point
|
|
0:20:29
|
Unassigned DN's is not always to delete but
|
|
0:20:32
|
when you're doing
|
|
0:20:35
|
or populated your system with a dial plan
|
|
0:20:38
|
that's probably the only time that is safe
|
|
0:20:41
|
or in a small lab environment when you know what you put in there
|
|
0:20:47
|
So let's go back to device phone, everything's set there
|
|
0:20:54
|
We'll go back to our tasks
|
|
0:21:14
|
and now the next task 115, we're told
|
|
0:21:18
|
to auto-register the IP phone attach to that port that we just shut down
|
|
0:21:22
|
to the sub CPE as a SIP based firmware phone
|
|
0:21:26
|
Do not set this phone up to the CUCM database manually
|
|
0:21:34
|
How are we going to auto-register this if all the other auto-registration just took effect
|
|
0:21:38
|
and every device came up
|
|
0:21:40
|
with the device protocol as Skinny
|
|
0:21:44
|
How are we gonna change it so that the next one
|
|
0:21:47
|
comes up as SIP. Now we could create new
|
|
0:21:53
|
7961 phone
|
|
0:21:55
|
We know that's what it is, and it is
|
|
0:21:58
|
and choose the protocol SIP
|
|
0:22:01
|
but and put in the MAC address but we were told not to put it manually so that's no good
|
|
0:22:06
|
But how can we do this?
|
|
0:22:09
|
Go back to, in this case it's actually Enterprise Parameters
|
|
0:22:15
|
and we actually see
|
|
0:22:18
|
auto-registration phone protocol
|
|
0:22:22
|
So again, how could I search for it?
|
|
0:22:26
|
I can go to
|
|
0:22:27
|
Service Parameters and search for Skinny or SIP
|
|
0:22:32
|
Skinny being what's been supported forever and so
|
|
0:22:36
|
Obviously, I'm gonna find a lot more references to SSCP so I would
|
|
0:22:41
|
search for the thing that I'm going to find less references to which is SIP
|
|
0:22:44
|
But under Service Parameters, I'm
|
|
0:22:46
|
still going to find a lot of references to
|
|
0:22:49
|
SIP attributes
|
|
0:22:53
|
So, I could search there
|
|
0:22:56
|
that might be a starting place
|
|
0:22:58
|
or I might wanna start in Enterprise Parameters and do a search for SIP
|
|
0:23:03
|
and I see Cluster Fully Qualified Domain Name, nope that's not the right one
|
|
0:23:10
|
and I actually don't see
|
|
0:23:14
|
what it is I wanted to see
|
|
0:23:19
|
That's because the default here is
|
|
0:23:22
|
Skinny and it doesn't actually tell me what the options are
|
|
0:23:24
|
or typically they're pretty good in telling you what the options are
|
|
0:23:27
|
specially in a drop down, but
|
|
0:23:30
|
suffice that to say thats one of the reasons it's good to look through every
|
|
0:23:34
|
service and enterprise parameter
|
|
0:23:37
|
did say that this is a good method
|
|
0:23:39
|
searching in a context sense of help but it's not
|
|
0:23:41
|
going to destinately yield you everything you need so you should
|
|
0:23:46
|
know and search for them ahead of time
|
|
0:23:49
|
in your own self-study time. So auto-registration phone protocol
|
|
0:23:52
|
Now let's see what this actually does say about it
|
|
0:23:56
|
This parameters specifies the protocol auto-registered
|
|
0:23:58
|
phone should boot with during initialization
|
|
0:24:01
|
Now, here's something interesting about this
|
|
0:24:07
|
This really doesn't have much to do with auto-registration per se.
|
|
0:24:12
|
What it does have to do with is TFTP
|
|
0:24:16
|
and configuration files served up
|
|
0:24:20
|
So if you remember back to the TFTP network infrastructure,
|
|
0:24:24
|
module, we discussed the fact that when the phone boots up
|
|
0:24:31
|
it looks for a number of things
|
|
0:24:33
|
by default, what are the first files, does anyone remember what are the first files
|
|
0:24:37
|
that every phone we'll search for is
|
|
0:24:40
|
naming convention of that file
|
|
0:24:49
|
anyone wanna speak up in comment or put it in to
|
|
0:24:56
|
Questions area, load? Just who says
|
|
0:25:00
|
Yes, firmware load
|
|
0:25:02
|
in a sense but actually it doesn't ask for the firmware load,
|
|
0:25:08
|
device that is trying to get TFTP
|
|
0:25:10
|
from gives it some sort of file, configuration file
|
|
0:25:14
|
and it gets it's load information or what
|
|
0:25:17
|
load information it should be running
|
|
0:25:19
|
from the configuration file but it actually looks for another file
|
|
0:25:23
|
before it looks for a configuration file, does anyone remember that one is
|
|
0:25:28
|
Rival says default xml file
|
|
0:25:30
|
that's actually the third file that it looks for
|
|
0:25:33
|
Then anyone remember what the first one is?
|
|
0:25:45
|
Very first file that it looks for is
|
|
0:25:51
|
CTL and then MAC address
|
|
0:26:00
|
.tlv that's the first file that it looks for
|
|
0:26:06
|
The second file it looks for
|
|
0:26:09
|
is SEP MAC address
|
|
0:26:21
|
.cnf.xml
|
|
0:26:29
|
The third file that it looks for
|
|
0:26:48
|
The third file it looks for is
|
|
0:26:51
|
and this actually depends
|
|
0:26:53
|
on if the phone is already in a Skinny
|
|
0:26:56
|
based firmware or if it's in a SIP based firmware
|
|
0:27:01
|
So, actually these are still the files it will look for if it's still Skinny
|
|
0:27:06
|
Sorry, if it's SIP, it will still for SEP MAC address
|
|
0:27:09
|
.cnf.xml
|
|
0:27:11
|
before it will look for, actually kind of indent
|
|
0:27:19
|
if the phone is SIP
|
|
0:27:24
|
If SIP then, third is going to be SIP MAC address .cnf
|
|
0:27:42
|
not that .cnf.xml, just .cnf it's a straight text file
|
|
0:27:47
|
Skinny Celsius ethernet phones use a xml format
|
|
0:27:52
|
but all SIP phones even if their Celsius
|
|
0:27:56
|
Cisco IP phones use just a flat text file as for the SIP RFC
|
|
0:28:02
|
So then, third is kind of like a
|
|
0:28:06
|
as a subtext. Then the third file if it's a Skinny
|
|
0:28:13
|
already in a Skinny firmware is going to then be default
|
|
0:28:19
|
default xml .cnf.xml
|
|
0:28:28
|
and then if it were a SIP phone, it will look for
|
|
0:28:33
|
and a 3.1 if it were SIP
|
|
0:28:37
|
it would look for default
|
|
0:28:41
|
.cnf, actually sorry, it's not just defaul cnf
|
|
0:28:50
|
it is more specifically SIP default .cnf
|
|
0:29:03
|
So, the reason I bring this up is that
|
|
0:29:08
|
changing the enterprise parameter or auto-registration protocol
|
|
0:29:13
|
changes this file right here
|
|
0:29:22
|
and what it does is it changes, modifies
|
|
0:29:26
|
for all device types
|
|
0:29:29
|
inside the default .cnf.xml file
|
|
0:29:33
|
all of them from the Skinny
|
|
0:29:37
|
firmware to the SIP phone firmware
|
|
0:29:40
|
So, what it is actually change it to, let's take a look
|
|
0:29:50
|
let's go ahead and change this, the SIP and by the way note
|
|
0:29:54
|
auto-registration phone protocol restart
|
|
0:29:56
|
all services for the parameter change to take effect
|
|
0:30:00
|
really you need to restart
|
|
0:30:02
|
Call Manager and TFTP
|
|
0:30:05
|
on probably safe to do on both servers
|
|
0:30:08
|
if you really have to restart all services
|
|
0:30:10
|
it's gonna be a lot quicker just to reboot all the boxes
|
|
0:30:17
|
Now this isn't gonna cause any problems
|
|
0:30:21
|
for our phones that are already registered. Why?
|
|
0:30:24
|
Take a look again. Because they will
|
|
0:30:29
|
look for their CTL file and they won't find it
|
|
0:30:32
|
but then they'll look for SEP MAC address
|
|
0:30:39
|
So the specific configuration file
|
|
0:30:42
|
for their phones and they will find that file
|
|
0:30:45
|
Since they'll find it,
|
|
0:30:47
|
they don't need to go on and ever look for this file
|
|
0:30:52
|
that is the phones, the default xml file
|
|
0:30:54
|
that's the phones that are already registered
|
|
0:30:58
|
and even if they were already registered as SIP,
|
|
0:31:02
|
then they might not find the first SEP file but they would
|
|
0:31:06
|
find SIP MAC address .cnf file
|
|
0:31:09
|
before ever going to default .cnf .xml
|
|
0:31:15
|
So again, it's safe to go ahead and set
|
|
0:31:19
|
the auto-registration protocol to a new protocol
|
|
0:31:23
|
or different protocol other than the one currently set at
|
|
0:31:27
|
SIP vs Skinny, your Skinny vs SIP whichever way you're going
|
|
0:31:31
|
If all of your other phones are already registered
|
|
0:31:34
|
and therefore alread have,
|
|
0:31:36
|
their SEP or SIP MAC address integration files built
|
|
0:31:45
|
and so what it's gonna do is just gonna change the default
|
|
0:31:49
|
xml .cnf.xml
|
|
0:31:55
|
and what is it gonna change it to
|
|
0:31:58
|
or we already had a peak at device, device defaults
|
|
0:32:06
|
or whatever the given SIP or Skinny
|
|
0:32:11
|
load is or that respective device
|
|
0:32:16
|
So far looking at 61 where I was here ago, here's the
|
|
0:32:21
|
load for 61 or 61GE
|
|
0:32:25
|
for SIP or load for 61 or 61GE Skinny phone
|
|
0:32:31
|
So they alread know what files to load, it's just a matter of
|
|
0:32:34
|
in xml, cnf xml which
|
|
0:32:37
|
load type should put in there, what firmware
|
|
0:32:40
|
file should we populate.
|
|
0:32:42
|
It does it for all of the files, that defaul xml file
|
|
0:32:45
|
is rather large for CUCM, is much smaller for CME
|
|
0:32:50
|
not because it's not as many phone types that is supported
|
|
0:32:53
|
such as the older like 30 bit for instance
|
|
0:32:55
|
We don't have firmware in those anymore but anyway
|
|
0:33:00
|
So now we go restart our services.
|
|
0:33:24
|
We're on there but we accidentally close the window altogether
|
|
0:33:27
|
We meant to open any tab
|
|
0:33:30
|
So I can get started
|
|
0:33:37
|
Pub and Sub at the same time
|
|
0:33:46
|
Call Manager but Pub and Call Manager, the Sub
|
|
0:34:08
|
It's still loading, there we go
|
|
0:34:16
|
Restart successful, TFTP, restart for Pub
|
|
0:34:24
|
Now though everyone will be getting their files, their TFTP files
|
|
0:34:27
|
from the Pub and then registering to the Sub
|
|
0:34:30
|
We'll go ahead and still restart, both for both
|
|
0:34:44
|
Restart is done on the Pub
|
|
0:34:57
|
And restart is done on the Sub
|
|
0:35:00
|
So at this point, I should be able to
|
|
0:35:14
|
Go to my port, now shut it, bring it back up
|
|
0:35:22
|
Power detected.
|
|
0:35:28
|
What power I'm drawing, 7 watts
|
|
0:35:32
|
CDP neighbor, but I don't see it show up in the CDP
|
|
0:35:36
|
the table just, yet but that's ok it will take a little while
|
|
0:35:40
|
Now when I do
|
|
0:35:45
|
Once I do show it up,
|
|
0:35:49
|
I'll be able to go and do detail
|
|
0:35:52
|
Right now there is none, and that will actually tell me
|
|
0:35:57
|
by default or just actually anytime
|
|
0:36:00
|
What firmware file is loaded on to the phone?
|
|
0:36:09
|
So currently, it's got version Skinny
|
|
0:36:13
|
Or 18-4-1S
|
|
0:36:16
|
Note that it doesn't have an entry IP address because it's just booting up
|
|
0:36:20
|
And it kind has one in reserve just in case
|
|
0:36:23
|
it can't contact the DHCP server but it should be able to
|
|
0:36:27
|
and I could also do a Show IP, DHCP
|
|
0:36:31
|
bindings first that this 11.30
|
|
0:36:36
|
has already been handed for, let's see
|
|
0:36:40
|
MAC address ending in 4436 which is
|
|
0:36:44
|
this phone or it will get this soon, still doesn't have it
|
|
0:36:50
|
Well it doesn't, let's go ahead and note that the hardware address
|
|
0:36:54
|
Maybe in a bit different format that you're used to if you have never seen
|
|
0:36:58
|
The format that get's handed out
|
|
0:37:01
|
from IP DHCP server
|
|
0:37:03
|
which is that it always takes and places 01
|
|
0:37:08
|
on the beginning of an ethernet based device
|
|
0:37:12
|
So that's why you see the aux set, that's actually the MAC address
|
|
0:37:16
|
This is the client identifier hardware address
|
|
0:37:21
|
So if we're actually
|
|
0:37:24
|
ever wanting to reserve an IP for a specific host
|
|
0:37:28
|
PC, Macintosh
|
|
0:37:34
|
Or phone or anything like that, we would actually specify the
|
|
0:37:38
|
Cisco client hardware, Cisco client identifier
|
|
0:37:42
|
and it would be 01 and then the MAC address
|
|
0:37:44
|
Let's look at the detail again
|
|
0:37:46
|
Now it's got its IP address, it still shows Skinny
|
|
0:37:49
|
That's ok, now that it has its IP address,
|
|
0:37:53
|
it also has, still run type 2 section IP DHCP
|
|
0:38:00
|
right section isn't supported on switches
|
|
0:38:03
|
I always forget that so let us just begin with
|
|
0:38:06
|
and for the corporate phones, it has option 66 for 1771 10 10
|
|
0:38:15
|
So it has its TFTP server
|
|
0:38:19
|
could be contacting at, let's just go back over to
|
|
0:38:23
|
CUCM, if you have any new phones that is showing up
|
|
0:38:26
|
we do have a new phone that is showing up
|
|
0:38:30
|
and hopefully, it will be registering with
|
|
0:38:34
|
SIP or at least registering then maybe un-registering
|
|
0:38:38
|
But it looks like it may actually stay up
|
|
0:38:41
|
We may have to restart the whole server
|
|
0:38:46
|
to get the auto-registration to work
|
|
0:38:51
|
typically do but for the sake of
|
|
0:38:53
|
Rather the, in time it's good and try to control it
|
|
0:39:01
|
if it shows up as staying, registered and up
|
|
0:39:11
|
and it is actually showing up
|
|
0:39:19
|
And it's able to call 1002, so it's staying up
|
|
0:39:25
|
So we will have to do is we will have to
|
|
0:39:28
|
restart the servers to get that to take effect
|
|
0:39:30
|
and we'll delete this phone and allow it to auto-register
|
|
0:39:40
|
So let's go ahead and put this interface to begin with
|
|
0:39:51
|
hop over to the Pub and the Sub
|
|
0:39:58
|
We'll do a utils system restart
|
|
0:40:05
|
Here utils system restart
|
|
0:40:10
|
Allow these two to reboot
|
|
0:40:13
|
And then we'll come back and
|
|
0:40:18
|
finish our task to auto-register that phone with SIP
|
|
0:40:23
|
and then we're told one last task to ensure that all SIP phones
|
|
0:40:28
|
attempt to re-register with CUCM every
|
|
0:40:31
|
30 minutes, so we'll take look at that task.
|
|
0:40:33
|
We can't make changes to the database right now
|
|
0:40:38
|
Actually we might still have access
|
|
0:40:40
|
to look at things even though we can't make changes
|
|
0:40:44
|
We're gonna find that under SIP profile
|
|
0:40:47
|
it's already restarted the cache
|
|
0:40:50
|
Can't do much at this point.
|
