|
0:00:14
|
The servers are rebooted, lets bring up the interface again
|
|
0:00:22
|
phones in front of me are up so everything should be rebooted
|
|
0:00:29
|
we'll just check to make sure that our enterprise parameter is still set as it should be to
|
|
0:00:35
|
auto registered SIP it is, good. Let's delete the phone
|
|
0:00:43
|
Auto Registered Skinny Phone
|
|
0:00:51
|
get the port shut down it's not registered
|
|
0:00:54
|
go ahead and delete the
|
|
0:01:04
|
Okay go back to the vice and we will bring up our
|
|
0:01:09
|
switch, and we'll know shut that port
|
|
0:01:15
|
power detected on F02
|
|
0:01:19
|
we're not gonna see the CDNP information for a while
|
|
0:01:26
|
and hopefully it wont take very long for it to
|
|
0:01:28
|
get it's IP address from DHCP
|
|
0:01:33
|
we can even debug IP DHCP
|
|
0:01:36
|
server, events
|
|
0:01:42
|
hasnt already gotten it's IP address
|
|
0:01:44
|
as we've noted in previous modules
|
|
0:01:56
|
and Rebel sorry if I wasnt able to well actually answer the question
|
|
0:02:00
|
but then if i switched to the demo
|
|
0:02:02
|
to the different layout to quickly for you to read the whole thing
|
|
0:02:06
|
the answer to your question of how many weeks is the deep dive
|
|
0:02:09
|
there's atleast 6 weeks left
|
|
0:02:12
|
probably about 6 and a half
|
|
0:02:14
|
and there will inevitably be other topics that come up
|
|
0:02:18
|
there is the DHCP request and assignment
|
|
0:02:22
|
so un-debug all just a moment
|
|
0:02:29
|
doesnt yet show that it has the IP address
|
|
0:02:33
|
but it should be
|
|
0:02:35
|
assigning it to itself
|
|
0:02:37
|
fairly soon
|
|
0:02:41
|
and it's still registering as Skinny
|
|
0:02:44
|
okay we might have some trouble shooting to do
|
|
0:02:48
|
this doesn't even show an IP address yet
|
|
0:02:51
|
here it does show 30
|
|
0:02:53
|
we can bring that information up
|
|
0:02:56
|
we do see that it's Skinny
|
|
0:02:58
|
it's not getting the proper SIP
|
|
0:03:01
|
load that we instructed it to
|
|
0:03:14
|
so it is registered
|
|
0:03:16
|
and it's not getting the
|
|
0:03:18
|
proper SIP code that we instructed it to
|
|
0:03:20
|
this is very interesting
|
|
0:03:27
|
little bit disconcerting
|
|
0:03:29
|
at this point what we'll do
|
|
0:03:30
|
is we will
|
|
0:03:33
|
take and not just have the subscriber
|
|
0:03:36
|
but have the publisher
|
|
0:03:39
|
allow an auto registration range
|
|
0:03:50
|
set
|
|
0:03:54
|
devices we will first go to serviceability
|
|
0:04:03
|
log in and shut down
|
|
0:04:17
|
more simply gonna shut down call manager service and
|
|
0:04:21
|
although it should never be being contacted
|
|
0:04:23
|
because it's not being advertised as an IP DHCP
|
|
0:04:27
|
we'll go ahead and shut down the TFTP on the sub as well and we're just gonna leave them shut
|
|
0:04:42
|
one of the fun things with SIP is that it's a
|
|
0:04:47
|
in Call Manager and much more so in Call Manager Express
|
|
0:04:52
|
it's still a little finicky in how it works
|
|
0:04:54
|
it doesn't exactly do what it's told to the first time everytime
|
|
0:05:03
|
Skinny is definitely still the way to go okay
|
|
0:05:05
|
Call Manager and TFTP are not running on the sub, on the pub
|
|
0:05:13
|
just so that we don't have any interaction I'm just going to shut the Call Manager down
|
|
0:05:34
|
going to restart TFTP
|
|
0:05:44
|
and once i restart TFTP I will start
|
|
0:05:47
|
Call Manager service and to continue what I was saying about the deep dive
|
|
0:05:51
|
about 6 and a half probably almost 7 weeks left of some other topics that we need to come up
|
|
0:05:57
|
and the idea is to as we mentioned just go extremely in depth with each topic
|
|
0:06:04
|
beyond just the regular, information that we'll be covering partaining the CCIE voice lab
|
|
0:06:23
|
we will continue on the deep dive series,sorry im just reading the question
|
|
0:06:32
|
or rather a comment
|
|
0:06:34
|
and continue on the deep dive series into things not necessarily pertaining to the CCIE voice lab
|
|
0:06:42
|
but certainly good to know, things that a number of students
|
|
0:06:46
|
through out the many years have asked me about
|
|
0:06:49
|
let's say voice security and or design scalability things of that nature
|
|
0:06:56
|
just part of what i put down on that
|
|
0:07:07
|
Joe your right the firmware issue seems to be a pretty big issue with Cisco yeah
|
|
0:07:11
|
Cisco phone firmware can be a bit
|
|
0:07:22
|
fun to deal with okay so we will quickly actually shutting and no shutting should be good enough
|
|
0:07:29
|
for this phone to
|
|
0:07:31
|
sorry not shutting and no shutting, but just deleting that phone
|
|
0:07:35
|
will cause it to reset
|
|
0:07:38
|
hopefully now the publishers the only thing available since everyones registered to pub
|
|
0:07:44
|
for it to get it's TFTP
|
|
0:07:58
|
we need to bounce the port as we can
|
|
0:08:01
|
but we'll just sit here
|
|
0:08:03
|
now unfortunately we wont be able to see it's
|
|
0:08:07
|
I should have tried to control it before I got rid of it that actually probably would
|
|
0:08:12
|
continue to have control over it
|
|
0:08:16
|
in fact while we're waiting for that to come up
|
|
0:08:19
|
because if it's trying to download it's new firmware that could take a little bit of time
|
|
0:08:25
|
I choose the corporate headquarter phone because it's on the same lan
|
|
0:08:29
|
as the server not even across our literal T1 even though it's just a cross over T1 cable
|
|
0:08:35
|
a literal T1 line to branch 1
|
|
0:08:40
|
so it takes some time but not too long
|
|
0:08:44
|
and it looks like it has already registered as skinny awesome.
|
|
0:08:52
|
So it is not taking it's cue from enterprise parameters
|
|
0:09:01
|
Okay i've seen this before
|
|
0:09:03
|
it's not fun when it happens but the idea is we have to set it back to Skinny
|
|
0:09:09
|
and then save restart the services and at this point
|
|
0:09:17
|
I will not restart the sub, I will only restart the pub
|
|
0:09:23
|
well actually shut down the sub altogether and then we have to actually change it back to SIP
|
|
0:09:30
|
sometimes the database you know what let's just do this
|
|
0:09:33
|
sometimes the data base needs a little bit of a kick
|
|
0:09:35
|
I don't know if anyone has experienced this certainly in .0 releases
|
|
0:09:42
|
but sometimes you'll make a change to a setting and it doesn't exactly take
|
|
0:09:49
|
another words the functionality
|
|
0:09:51
|
I mentioned yesterday could be a replication issue
|
|
0:09:54
|
but if your only having the phones home to the pub
|
|
0:09:56
|
then it's not a replication issue any longer
|
|
0:09:59
|
cannot be, so at that point sometimes what you find and as if you
|
|
0:10:03
|
change a value back to it's original
|
|
0:10:07
|
click save to update and then change it back to where you wanted it
|
|
0:10:12
|
in the first place and then click save that kicks the database it forces the field to update
|
|
0:10:19
|
in the database which unfortunately sometimes rarely but sometimes
|
|
0:10:24
|
I have seen those sequel inserts, to be technical about it
|
|
0:10:30
|
not actually take and commit the transaction to the database
|
|
0:10:34
|
so in that case that's where I said you change it back to the original then change it back to your
|
|
0:10:40
|
manipulative value then it will take unfortunately in this case
|
|
0:10:45
|
it's one that we actually have to restart all the services
|
|
0:10:50
|
so it will take a little bit of time, what we'll do in the meantime actually
|
|
0:10:57
|
is let's just go ahead and take a look at what we still needed to do
|
|
0:11:03
|
so lets take a look at SIP and for those who wanna stick around for the reboot they can do that
|
|
0:11:08
|
otherwise they can watch the recorded portion later.
|
|
0:11:12
|
But we'll ensure that all SIP phones attempt to re-register with the CUCM every 30 minutes
|
|
0:11:18
|
even though at this point we don't have any SIP phones
|
|
0:11:20
|
that's found under device settings SIP profile, note there is SIP Profile
|
|
0:11:27
|
under device settings and then under system
|
|
0:11:30
|
there is, on security profile there is SIP trunk security profile
|
|
0:11:34
|
Okay? SIP trunk has both the SIP profile and a SIP trunk security profile
|
|
0:11:43
|
one deals with timers and various things at the SIP profile and the security deals with
|
|
0:11:50
|
specific features related to SIP security, which some we actually have to take a look at primarily
|
|
0:11:58
|
when it comes to unity connection innegration with SIP
|
|
0:12:01
|
or the present server the rest we'll be taking a look at on the security deep dive module
|
|
0:12:10
|
which is I mentioned will be done after the CCI related deep dive modules are done
|
|
0:12:15
|
so here there's a lot of parameters and we can go over all of them
|
|
0:12:21
|
there's a lot here to look at what we specifically wanna look at is registration
|
|
0:12:27
|
so we see timer register expires which is 3600
|
|
0:12:34
|
and we note that it's in seconds we bring up our calculator
|
|
0:12:37
|
say 3600 divided by 60 is how many minutes that's 60 minutes
|
|
0:12:43
|
so, we could change this to 30 x 60 seconds is 1800
|
|
0:12:52
|
or we could just divided that in half if we already knew that it was 60 minutes
|
|
0:12:56
|
Okay? Now that is 30 minutes however
|
|
0:13:00
|
note ensure that all SIP phones attempt to re-register with the CUCM every 30 minutes
|
|
0:13:07
|
well here's the only problem that's when the registration expires
|
|
0:13:13
|
not necesarily when the phone tries to re-register,register delta
|
|
0:13:18
|
actually plays a part in that and I could just tell you but instead i'll could go to help for this page
|
|
0:13:24
|
as we mentioned we'd be doing a lot of looking at the documentation and if I look at Timer Register
|
|
0:13:32
|
this is the value that the phone running SIP will send the expire header of the register message
|
|
0:13:38
|
and register delta this parameter in conjunction with the timer register expire setting
|
|
0:13:44
|
or works in conjunction with the phone will re-register timer delta seconds
|
|
0:13:51
|
or in other words this many seconds before registration period ends so what does that mean,
|
|
0:14:01
|
5 was the default and here 3600 is the default so 1 hour it's un-registered or expired
|
|
0:14:09
|
and 5 seconds before 1 hour it will attempt to re-register so if i just change this to 1800
|
|
0:14:15
|
that does not yield me the required task of making sure that the phone attempts to re-register every 30 mins
|
|
0:14:25
|
at this point it attempts to register 5 seconds before 30 mins
|
|
0:14:29
|
so I can either say 1795 and 5 then it will attempt to register every 5 sorry every 30 mins
|
|
0:14:39
|
or I could have left this at the default 3600 and just said 1800 seconds
|
|
0:14:45
|
30 mins before the expire which is an hour try to register 30 mins before
|
|
0:14:51
|
either one of those would have been fine or any combination equalling this number
|
|
0:14:57
|
this number rather minus this number so actually I think I said 1795
|
|
0:15:06
|
it should have rather been 1805 and then 5 Okay?
|
|
0:15:12
|
or 1800 and 3600 so this number minus this number as when the phone will attempt to re-register
|
|
0:15:20
|
now I actually cant make changes to this
|
|
0:15:23
|
so I would actually have to copy this in order for this to be proper and change it to
|
|
0:15:29
|
you know 30 minute re-reg profile and say 1800
|
|
0:15:41
|
save,
|
|
0:15:44
|
and then when i have the phone assign that SIP profile to the SIP phone
|
|
0:15:50
|
okay so that answers that portion go back and take a look at what we were told to do
|
|
0:15:58
|
ensure that newly created phones have the default functionality DND we should probably test those
|
|
0:16:05
|
I believe that we set headquarter phone 2 was it? Or the 1002 DN or busy and no answer to
|
|
0:16:24
|
that's a 3002 so let's bring up quarter phone 2 and lets also bring up
|
|
0:16:38
|
another one for
|
|
0:16:45
|
3002,
|
|
0:17:01
|
tell both of these to refresh every 3 seconds
|
|
0:17:09
|
and we actually probably need one more phone to place the call,
|
|
0:17:39
|
we've got 1001. So currently if 1001 calls 1002
|
|
0:17:47
|
it's just ringing normally Okay? We'll go ahead and go back on hook
|
|
0:17:51
|
we see IDivert by the way that's good we were told to do that
|
|
0:17:55
|
add the default softkey and note we didn't modify anything there for the softkey
|
|
0:18:06
|
still on none. Okay now if we do DND, we dont have DND as softkey so we have to first add that
|
|
0:18:14
|
weren't told to add it but obviously it is necessary if we want to enable the functionality
|
|
0:18:23
|
configure the softkey layout and let's just leave it on hook that's where we can enable DND
|
|
0:18:31
|
i'll go do not disturb and we'll bump it up one that way it's not part of more
|
|
0:18:43
|
and we'll reset and restart any phones associated
|
|
0:18:49
|
actually we don't really need to restart all the phones, just rather restart that one phone
|
|
0:19:31
|
and now it's re-registered and my refresh isn't gonna work is it?
|
|
0:19:39
|
Say vice control
|
|
0:19:47
|
device associate there. Okay select from the list we'll try it again
|
|
0:19:59
|
here we go
|
|
0:20:04
|
Okay so now we'll say let's go off hook and then on hook to get rid of
|
|
0:20:10
|
one missed call, we'll say DND but do not disturb is active and now we'll try to redial
|
|
0:20:20
|
and note
|
|
0:20:22
|
that it's forwarded to 1002 so we did in fact meet our requirements of by default
|
|
0:20:33
|
when DND is active having that phone forward to 3002 or to werever the or forward all sorry or forward busy was set to
|
|
0:20:47
|
and by the way this is the forward busy DND isconsidered being busy
|
|
0:20:53
|
okay?
|
|
0:20:56
|
now it rings normal
|
|
0:21:01
|
okay, so we met that requirement let's see was there anything else that we were instructed to do
|
|
0:21:05
|
we were instructed to delete auto registered DN's ah, the CUCM CCM user page
|
|
0:21:14
|
okay? so lets
|
|
0:21:19
|
go to forward slash CCM user
|
|
0:21:25
|
and we actually created a user started to and never associated it with the device yet so
|
|
0:21:34
|
let's grab our user
|
|
0:21:36
|
associate it with the, with a device
|
|
0:21:41
|
choose headquarter phone 2 I think is what we,
|
|
0:21:47
|
gave the user the name of
|
|
0:21:52
|
save the selective change
|
|
0:21:54
|
back to the user
|
|
0:21:57
|
save it although we shouldn't have to do anything there, there we go
|
|
0:22:06
|
and i forgot to add myself as an end user
|
|
0:22:17
|
find it here, there it is standard CCM user
|
|
0:22:41
|
cheers for that David I did forget to add that okay so
|
|
0:22:47
|
I have it relate to the device I have things like line settings
|
|
0:22:53
|
and I can forward all calls but that's it, I cannot forward all of the
|
|
0:23:00
|
other pieces lets see what we were told to do line text label we could edit
|
|
0:23:06
|
and only call forward all not display any of the four features so line text label
|
|
0:23:15
|
here's my line text label for the line that I happen to be selected to the only line I have
|
|
0:23:21
|
but if i had multiple then i can could choose from the drop down
|
|
0:23:23
|
which line i wanted to forward calls and line text label but if i go ahead and open
|
|
0:23:29
|
i'll just open the admin interface back up and show the contrast
|
|
0:23:34
|
which is from enterprise parameters
|
|
0:23:38
|
and
|
|
0:23:42
|
the for, lets show all settings
|
|
0:23:50
|
that and if we refresh the page gonna make me log in again
|
|
0:24:05
|
now I can see all of the forward settings
|
|
0:24:08
|
okay we'll change it back to where we were instructed to
|
|
0:24:11
|
but just wanted to show the contrast
|
|
0:24:23
|
problem of having multiple tabs open at the same time
|
|
0:24:27
|
I believe it took only forward all
|
|
0:24:31
|
save
|
|
0:24:34
|
there we go, this will probably want me to go log in again. It does
|
