|
0:00:11
|
So looking at our next Task 1.8
|
|
0:00:13
|
or CUCM system device tools.
|
|
0:00:17
|
We´re instructed to modify the default Device Pool
|
|
0:00:21
|
and rename to DP_Corporate Headquarters
|
|
0:00:25
|
and then you configure two additional Device Pools
|
|
0:00:27
|
to be later assigned all Branch1
|
|
0:00:29
|
and Branch2 devices, respectively.
|
|
0:00:31
|
Name them intuitively following the format of
|
|
0:00:34
|
Corporate headquarter Device Pool.
|
|
0:00:36
|
Assign the proper respective Regions,
|
|
0:00:39
|
Date/Time groups, Location and SRST references
|
|
0:00:42
|
to each Device Pool that we´ve created. So everything
|
|
0:00:46
|
of those entities that we just got done creating.
|
|
0:00:50
|
and then also kind of an add, on which is that.
|
|
0:00:53
|
We are told to ensure that if any on hold call revert
|
|
0:00:57
|
and simultaneously a new call is incoming and ringing
|
|
0:01:01
|
at any Corporate headquarter IP phone,
|
|
0:01:04
|
but the call that was on hold should have the priority
|
|
0:01:07
|
to being selected when that IP phone user goes off hook.
|
|
0:01:13
|
We´ll take a look at that,
|
|
0:01:16
|
so we´re going to go to our Device Pools
|
|
0:01:19
|
check to see what we have, of course we have the default
|
|
0:01:25
|
and we´ll rename it as we were instructed to DP_Corporate headquarters
|
|
0:01:33
|
We already have the proper sub then pub CPE ordered CUCM group.
|
|
0:01:40
|
because that´s the only one, because we modified
|
|
0:01:42
|
default, that´s one of the reasons we modified default
|
|
0:01:45
|
for any entities that have a default because otherwise,
|
|
0:01:48
|
we could very well forget to change it from default.
|
|
0:01:54
|
And or later just forget and leave something at default, rather than
|
|
0:02:00
|
you know maybe changing it to Coporate headquarter.
|
|
0:02:03
|
We have a created entity called Corporate headquarters,
|
|
0:02:06
|
rather if we just change whatever entity we´re on.
|
|
0:02:09
|
from default to our main site,
|
|
0:02:12
|
then we don´t have to worry about accidents later.
|
|
0:02:17
|
Calling Search Space for auto registration,
|
|
0:02:19
|
no we don´t have any yet so.
|
|
0:02:21
|
We´re not really going to care, we´ll just go manually
|
|
0:02:23
|
assign them or most likely use the bat tool if we have
|
|
0:02:28
|
multiple devices to assign the same CSS tool.
|
|
0:02:33
|
What´s this next one? Reverted Call Focus Priority
|
|
0:02:36
|
sound similar to what we are being told.
|
|
0:02:39
|
Ensure that if an on hold call reverts
|
|
0:02:43
|
and simultaneously a new call is incoming
|
|
0:02:45
|
which is ringing at that Corporate phone.
|
|
0:02:48
|
The call that was on hold will have the priority
|
|
0:02:51
|
to being selected versus the new incoming ringing call
|
|
0:02:56
|
when the IP phone user goes off hook.
|
|
0:02:58
|
What´s with it sounds like?
|
|
0:03:00
|
Well wait a minute, that´s default or highest?
|
|
0:03:02
|
You really make much sense, in terms of values.
|
|
0:03:08
|
To answer your question real quick Joseph, do you have the bat?
|
|
0:03:11
|
tool during the exam. Is it something you recommend?
|
|
0:03:16
|
We talked a link yesterday about the bat tool,
|
|
0:03:19
|
I realized I don´t think you were able to make until later, but
|
|
0:03:22
|
we do have the bat tool because it´s installed by default.
|
|
0:03:26
|
I definitely recommend you go back and look at that
|
|
0:03:29
|
previous module on web UI and command line because we
|
|
0:03:32
|
looked at that and RTMT and command line and features
|
|
0:03:36
|
quite a bit yesterday anything that is installed
|
|
0:03:39
|
by default for like the bat tool.
|
|
0:03:43
|
Also I´m not going to go there right now because
|
|
0:03:45
|
what we´re on, but servicability, DNA or Dialed Number Analyzer
|
|
0:03:49
|
Also from the plug ins page, we can get RTMT,
|
|
0:03:53
|
but that´s actually already installed on your candidate XP.
|
|
0:03:58
|
Remote desktop, Protocol access, workstation in the lab.
|
|
0:04:03
|
All of those are available by default
|
|
0:04:09
|
by the servers that are listed on the blueprint
|
|
0:04:12
|
so the answer to all of those is yes.
|
|
0:04:14
|
The one thing that we did briefly take a look at
|
|
0:04:16
|
yesterday just to see how cool it was,
|
|
0:04:18
|
but will not be on the exam
|
|
0:04:20
|
is the VLT, the Voice Log Translator, very nice.
|
|
0:04:24
|
Will not be on the exam though, will not be available
|
|
0:04:27
|
because that´s actually a separate download from Cisco.
|
|
0:04:31
|
OK, so Reverted Call Focus
|
|
0:04:34
|
Default and Highest. Don´t really tell us much so
|
|
0:04:37
|
let´s go to help or this page.
|
|
0:04:41
|
Now of course we can go to the documentation website,
|
|
0:04:44
|
but that´s what this does, as we´ve already mentioned today.
|
|
0:04:47
|
CM administration guide and scrolling down system guide,
|
|
0:04:50
|
features and services. It not only goes to the documentation,
|
|
0:04:53
|
but it takes us directly to where we need it.
|
|
0:04:56
|
Dveilce Pool configuration settings, so let´s look at the
|
|
0:05:01
|
fax for Reverted Call Focus Priority
|
|
0:05:03
|
Choose a clusterwide priority setting for reverted call
|
|
0:05:05
|
that are invoked by the hold reversion feature.
|
|
0:05:08
|
By the way, this setting applies to
|
|
0:05:11
|
hold reverted call that did not apply to Park reverted calls.
|
|
0:05:17
|
Default. If you choose this option, incoming calls have the priority
|
|
0:05:22
|
they could have just said incoming.
|
|
0:05:26
|
If you choose this option for highest, reverted calls
|
|
0:05:29
|
have the priority. So say reverted, for the value say
|
|
0:05:34
|
incoming and reverted or hold reverted, but
|
|
0:05:38
|
for whatever reason this is what they view sees value
|
|
0:05:42
|
So we´re intsructed to have hold-calls
|
|
0:05:45
|
that are reverted have the highest priority
|
|
0:05:50
|
over incoming calls, but that was just
|
|
0:05:53
|
for Corporate Headquarter phone.
|
|
0:05:55
|
Now it didn´t say, by the way it didn´t say
|
|
0:05:58
|
only headquarter phones it just said at any
|
|
0:06:02
|
headquarter phones, so if you did this for
|
|
0:06:04
|
other Device Pools are use to copy and forgot to change it
|
|
0:06:08
|
it probably be okay, but
|
|
0:06:11
|
it´s best to do exactly what you´re told on the exam, OK.
|
|
0:06:17
|
Yes, local route group this is going to get
|
|
0:06:20
|
heavily in to, what we´ll talk about in terms of
|
|
0:06:22
|
local route groups, standard local route group,
|
|
0:06:26
|
which is a brand new feature in CUCM 7 and we´ll get
|
|
0:06:29
|
heavily into all of the new features.
|
|
0:06:32
|
In fact it´s probably, we´ll spend most of our time
|
|
0:06:34
|
talking about during that dial plan module, we actually have
|
|
0:06:37
|
3 dial plan modules not taking in to account cube
|
|
0:06:41
|
or taking into account
|
|
0:06:46
|
the gatekeeper or anything like that that three separate dial plan modules
|
|
0:06:52
|
coming up in I believe 3 weeks, right after
|
|
0:06:57
|
networkers so the first full week of July.
|
|
0:07:02
|
So we´ll leave that alone, Date/Time group,
|
|
0:07:07
|
we did actually not modify CM local.
|
|
0:07:10
|
OK, so we talk about modifying default.
|
|
0:07:13
|
This particular lab, we were instructed to create
|
|
0:07:15
|
versus modify, but we probably would have been find to
|
|
0:07:19
|
modify, I being the proctor and you being being
|
|
0:07:22
|
the student asking me, I would have said either one is fine
|
|
0:07:25
|
modify or create, but always safe is to do what you´re told.
|
|
0:07:29
|
So Date/Time group for Corporate headquarter region,
|
|
0:07:33
|
we modified default so that´s already Corporate headquarter.
|
|
0:07:38
|
MRGL that will come under the media section, location.
|
|
0:07:43
|
OK? So hub-non for Corporate headquarters, now
|
|
0:07:48
|
just like, just about everythine else
|
|
0:07:50
|
not everything else, not Date/Time group, not Region but
|
|
0:07:53
|
but MRGL certainly, location
|
|
0:07:57
|
some other various things, Calling Search Space
|
|
0:08:02
|
If we modify or set one of these entities setting
|
|
0:08:07
|
on a device such as a gateway or a phone,
|
|
0:08:12
|
then those settings have priority over top of
|
|
0:08:16
|
what is set on the Device Pool because you have to assign
|
|
0:08:21
|
a Device Pool to every device or I should rather say
|
|
0:08:26
|
every device must be assigned to a Device Pool.
|
|
0:08:31
|
OK? By default is the default Device Pool
|
|
0:08:33
|
which is Corporate so we need to change those on the
|
|
0:08:36
|
devices after we auto-register them, in later task today.
|
|
0:08:41
|
If a setting has not been set
|
|
0:08:45
|
it is been left at default or use system default
|
|
0:08:49
|
on a device such as a gateway or a phone
|
|
0:08:52
|
then it reverts back to what is the setting
|
|
0:08:55
|
on the Device Pool that I´m a member of.
|
|
0:08:58
|
In terms of, and the reason I´m bringing
|
|
0:09:00
|
this up now, in terms of location
|
|
0:09:03
|
there is no such thing or I should say there is no
|
|
0:09:07
|
entity that´s called or no drop down from any device
|
|
0:09:10
|
that´s called for location
|
|
0:09:14
|
purposes nothing that´s called default or use system default.
|
|
0:09:20
|
Instead, what we have is Hub_None, so one thing we didn´t
|
|
0:09:25
|
talk about when we talked about locations was
|
|
0:09:28
|
why is the default now, why is it now called hub_none?
|
|
0:09:34
|
Does the hub have none? Well, sort of
|
|
0:09:38
|
the hub has no band width, 0 band width use to equal unlimited
|
|
0:09:42
|
still does, you just don´t do 0, you now choose the radio button
|
|
0:09:46
|
which effectively tells the database 0
|
|
0:09:48
|
and effectively tells the programming, unlimited
|
|
0:09:52
|
OK? So in a sense, the hub
|
|
0:09:56
|
Essentialized headquarter site does have no bandwidth
|
|
0:09:59
|
or unlimited bandwidth, however you want to look at it.
|
|
0:10:03
|
But is also has a dual meaning, OK?
|
|
0:10:06
|
Hub in the sense that it´s at your hub, your central site
|
|
0:10:12
|
but then none in the sense that if I am leaving any phone
|
|
0:10:18
|
or gateway or any sort of a device
|
|
0:10:21
|
music on hold server, anything that transcode
|
|
0:10:25
|
or anything that can have a location assigned to it
|
|
0:10:28
|
has to have a location, as we just told or system default.
|
|
0:10:33
|
So by default everything will have Hub_None.
|
|
0:10:35
|
If we leave it set at Hub_None
|
|
0:10:38
|
it takes the none setting and basically says look back
|
|
0:10:41
|
at the device pool and use whatever the device pool set to
|
|
0:10:45
|
Now, if the Device Pool is also
|
|
0:10:47
|
as in the case of Corporate headquarters
|
|
0:10:50
|
set for location to Hub_None, then it truly
|
|
0:10:53
|
uses the Hub_None location.
|
|
0:10:57
|
If any of the other devices, like let´s say Branch1
|
|
0:11:00
|
or Branch2 phones that we will set up later.
|
|
0:11:03
|
If they on their device, on their phone have location
|
|
0:11:08
|
of Hub_None, it looks back to their respective
|
|
0:11:11
|
device pool which we will be creating here, momentarily
|
|
0:11:14
|
and those will have specifically Branch1 or Branch2.
|
|
0:11:20
|
OK? So Hub_None on the device looks back to the
|
|
0:11:23
|
Device pool, and if the Device Pool is set Hub_None
|
|
0:11:26
|
uses Hub_None, but otherwise uses whatever
|
|
0:11:29
|
the Device Pool has, now if the device
|
|
0:11:32
|
is not left to Hub_None, then
|
|
0:11:39
|
another words it´s set to something more specific
|
|
0:11:42
|
then that value will take precedence over the Device Pool
|
|
0:11:48
|
depends where we want to administer it.
|
|
0:11:50
|
And the only other thing to keep in mind
|
|
0:11:53
|
which we really won´t be getting in today, as I mentioned
|
|
0:11:56
|
is this all fall in Device Pool under a section called
|
|
0:11:59
|
Roaming Sensitive Settings and there other
|
|
0:12:02
|
pieces called Device Mobility Related Information.
|
|
0:12:05
|
All of those sections has nothing to do with normal
|
|
0:12:10
|
phones in normal situations, normal call situation
|
|
0:12:14
|
they have to do with Device Mobility in a roaming context.
|
|
0:12:20
|
OK? So as for the headings there, Roaming
|
|
0:12:23
|
Sensitive Settings and Device Mobility related information.
|
|
0:12:28
|
You can kind of keep that in the back of your mind
|
|
0:12:31
|
for the device mobility module that we´ll have separately, but
|
|
0:12:35
|
we won´t be talking about device mobility today
|
|
0:12:38
|
but that´s what those pertain to however,
|
|
0:12:43
|
even if we are not in a Device Mobility Roaming situation
|
|
0:12:48
|
all of these setting are able to take effect
|
|
0:12:52
|
for the devices contained within this Device Pool.
|
|
0:12:56
|
OK? So they´re used in normal situations
|
|
0:12:59
|
and then they can also be used independent of one another
|
|
0:13:02
|
as sub sections in device mobility situations.
|
|
0:13:06
|
So we are looking at them in a normal
|
|
0:13:09
|
normal phone device mobility disabled for all phones or
|
|
0:13:14
|
it´s never enabled for gateways, but
|
|
0:13:17
|
normal settings for all devices situation
|
|
0:13:20
|
OK? So network local, we can do that
|
|
0:13:23
|
the none if we want to default which is English.
|
|
0:13:29
|
So for now, that´s probably fine we weren´t instructed
|
|
0:13:33
|
to do anything different probably would be good in a
|
|
0:13:36
|
real environment to do something different.
|
|
0:13:39
|
SRST reference, we really, we´ll just leave this to disable for
|
|
0:13:45
|
Corporate headquarters, because we don´t have SRST
|
|
0:13:47
|
we weren´t told to set it up.
|
|
0:13:50
|
Single button barge join across lines
|
|
0:13:52
|
again anything that you´re wondering, what it might
|
|
0:13:55
|
do that we might not intuitively or already.
|
|
0:14:01
|
So such as connection monitor
|
|
0:14:03
|
we can read about in the administration guide, always help
|
|
0:14:08
|
for this page. How can I click it just because it load be
|
|
0:14:11
|
very same page again it´ll take a little bit of time.
|
|
0:14:14
|
So for instance connection monitor duration
|
|
0:14:16
|
the setting define of the time that IP phone monitors
|
|
0:14:19
|
disconnection to CUCM manager before
|
|
0:14:21
|
before it unregisters from SRST and registers to CUCM.
|
|
0:14:25
|
So this is not the amount of time that is use for a phone
|
|
0:14:33
|
when it´s connected to a standard cluster
|
|
0:14:36
|
for the pair or you know triplicates subscribers
|
|
0:14:39
|
or in this case a subscriber and then a publisher
|
|
0:14:43
|
to service, this is not the amount of time that it looks
|
|
0:14:45
|
and does a, sort of a ping or hello to find out
|
|
0:14:52
|
is the primary CPE that I´m registered to as it´s still live
|
|
0:14:56
|
or is the secondary CPE or tertiary CPE,
|
|
0:15:00
|
call processing engine that I might need to register to
|
|
0:15:03
|
is that still alive, that is not the value for that
|
|
0:15:05
|
those values can be found in system service parameters.
|
|
0:15:09
|
And there´s a different value for your primary
|
|
0:15:13
|
and then your secondary and tertiary connections
|
|
0:15:16
|
typically the secondary and tertiary connections are twice.
|
|
0:15:24
|
This is if I fall in back to SRST
|
|
0:15:29
|
then how long should I wait to
|
|
0:15:33
|
check and if it´s available unregister and reregister to CUCM
|
|
0:15:37
|
actually once I know CUCM is available.
|
|
0:15:41
|
How long should I wait, it still uses the standard primary
|
|
0:15:45
|
because that would be the active CPE.
|
|
0:15:48
|
It uses the primary to see, primary interval
|
|
0:15:51
|
I should say to see, is my or secondary
|
|
0:15:56
|
maybe because it would be secondary at that point,
|
|
0:15:58
|
is the call manager back available,
|
|
0:16:01
|
rather than the CME that I´m using as SRST or the
|
|
0:16:04
|
true SRST router and then when it is
|
|
0:16:09
|
wait for extra amount of seconds before reregistering.
|
|
0:16:14
|
OK?
|
|
0:16:16
|
So by default is a hundred and 20 seconds
|
|
0:16:20
|
So single button Barge determines whether devices or phone
|
|
0:16:23
|
users in the device pool have single button access
|
|
0:16:26
|
for barge and CBarge.
|
|
0:16:29
|
OK, Join Across lines, the settings
|
|
0:16:32
|
setting determines whether the Join Across lines
|
|
0:16:35
|
feature is enable for devices or phone users.
|
|
0:16:40
|
OK? So again to define those features more
|
|
0:16:43
|
if you´re not familiar with those features you happen not to be
|
|
0:16:46
|
then you can go read about those further
|
|
0:16:50
|
but this is just enabling or disabling some of those features
|
|
0:16:53
|
for all devices inside of a device pool.
|
|
0:17:04
|
Physical location, again that gets in to device mobility
|
|
0:17:07
|
as does device mobility group, so we´ll look at those
|
|
0:17:10
|
during another situation so does device
|
|
0:17:13
|
mobilty calling search space.
|
|
0:17:15
|
OK, that would only be for device mobility
|
|
0:17:18
|
notice the heading Device Mobility Calling Search Space
|
|
0:17:23
|
eventhough it´s under the sub section of device mobility
|
|
0:17:25
|
related information, if it didn´t say device mobility
|
|
0:17:29
|
calling search space, then it would be a calling search space
|
|
0:17:31
|
for all devices that do not happen to have one configured.
|
|
0:17:38
|
but it says device mobility it´s specific to
|
|
0:17:41
|
just device mobility where as the others.
|
|
0:17:44
|
Don´t say device mobility AAR CSS and AAR group
|
|
0:17:49
|
and calling and called party transformation this is because
|
|
0:17:54
|
truly any device that needs these settings which could be
|
|
0:18:01
|
phones or gateways
|
|
0:18:04
|
and have them set at the device pool level.
|
|
0:18:17
|
OK? Also we have incoming calling part settings
|
|
0:18:21
|
though if the administartor sets the prefix to default,
|
|
0:18:24
|
well actually that´s just saying what will override in terms of
|
|
0:18:28
|
device pool service parameter eventhough we are at the device pool .
|
|
0:18:31
|
Again this is something related to dial plan
|
|
0:18:34
|
something specifically related to something called globalization
|
|
0:18:37
|
which is new in 7.0, something we will be covering Ad nauseum.
|
|
0:18:42
|
Very very in depth probably as one of the most important
|
|
0:18:47
|
of any CCIE voice lab and certainly of the new
|
|
0:18:52
|
version 3 CCIE voice lab will be all of the advance
|
|
0:18:57
|
dial plan settings, globalization, localization,
|
|
0:19:00
|
mapping the global number to the local variant
|
|
0:19:05
|
standard local route group, all of those pieces,
|
|
0:19:09
|
plus styling, all of those will be covered. Great.
|
|
0:19:16
|
Do you want me to do anything with
|
|
0:19:17
|
those or talk about those now?
|
|
0:19:21
|
OK, so we´ve set everything for headquarters
|
|
0:19:24
|
really there´s not much here that we need to keep
|
|
0:19:27
|
for the next section, we need change evrything
|
|
0:19:30
|
except for the CUCM groups, so I´m just going to add a new one.
|
|
0:19:43
|
OK? So device pool_Branch1 choose the group
|
|
0:19:48
|
we´re not going to do anything with those, we´ve already mention
|
|
0:19:52
|
Date/Time for Branch1, Region Branch1
|
|
0:19:58
|
and Location Branch1 and SRST Branch1,
|
|
0:20:03
|
we´re told to set and we could copy if we wanted, sure copy
|
|
0:20:09
|
to and we´ll choose Date/Time Branch2, Region Branch2
|
|
0:20:15
|
Location Branch2, SRST Branch2.
|
|
0:20:20
|
Add successful.
|
|
0:20:23
|
And everything should be set properly, have to do a quick
|
|
0:20:27
|
verification of the columns that show up here
|
|
0:20:31
|
OK? So our device pools are set. Any questions?
|
|
0:20:38
|
Looking at the next task 1.9 CUCM System Enterprise Parameter
|
|
0:20:43
|
change any, we´re actually giving you again some helpful information
|
|
0:20:48
|
the lab would not say change any, well in this case it would
|
|
0:20:53
|
some of the service parameters.
|
|
0:20:55
|
We wouldn´t say, hey this is going to be found under
|
|
0:20:57
|
service parameters, that´s a little too helpful, but again
|
|
0:21:01
|
this being volume 1, task by task, technology by technology or
|
|
0:21:07
|
youw know helping you learn in a deep dive section.
|
|
0:21:11
|
The idea is to help you rather than
|
|
0:21:14
|
test, fully test and fully challenge you,
|
|
0:21:16
|
that´s more of what our mock labs all about
|
|
0:21:20
|
OK, just wanted to note that so that you don´t think
|
|
0:21:22
|
it´s going to be quite that easy on the exam.
|
|
0:21:25
|
So Enterprise Parameters change any reference in any URL
|
|
0:21:28
|
from host name to IP address format, that should be rather simple.
|
|
0:21:33
|
So let´s go down to System Enterprise Parameters,
|
|
0:21:38
|
and we can scroll down, me may already know
|
|
0:21:42
|
where those host names are and of course
|
|
0:21:44
|
they´re under the phone URL parameters.
|
|
0:21:53
|
Now, this is a place where DNS actually can benefit you,
|
|
0:21:56
|
right now if I need to do authentication or
|
|
0:22:00
|
look up directory information, information about
|
|
0:22:05
|
various features on my phones, the question mark,
|
|
0:22:07
|
the URL, information that or services.
|
|
0:22:11
|
Maybe I have those services replicated on
|
|
0:22:13
|
from multiple servers or I want to
|
|
0:22:19
|
be able to look up directories or authenticate your
|
|
0:22:23
|
multiple servers or anything of that nature.
|
|
0:22:26
|
It might be helpful to have DNS
|
|
0:22:29
|
because then from the DNS server, we can either
|
|
0:22:31
|
round robin and load balance, well actually
|
|
0:22:34
|
round robin or load balance or we can use
|
|
0:22:36
|
SRV service records to have priority and redundancy, resiliency.
|
|
0:22:48
|
OK? So click save here.
|
|
0:22:54
|
Revil ask, is it true that gen3 phones,
|
|
0:22:57
|
no longer use this phone URL parameters.
|
|
0:23:01
|
Gen3 and Gen4 phones, when I speak of Gen3
|
|
0:23:05
|
I´m speaking of 61s, 41s, 65s, 45s, that nature.
|
|
0:23:10
|
and then the Gen4 phones are the newer
|
|
0:23:13
|
like 97, 80 phones I believe is the.
|
|
0:23:19
|
I don't have any, I played with them, but I don't
|
|
0:23:22
|
use them enough to remember the exact
|
|
0:23:24
|
model number, but the new ones with video
|
|
0:23:26
|
and usb ports and things of that nature
|
|
0:23:29
|
I will just show you what it is that they do use
|
|
0:23:34
|
So under device, device settings and phone services,
|
|
0:23:38
|
I'll open this in a new tab.
|
|
0:23:42
|
when close are help here, I probably should have let that open
|
|
0:23:47
|
We find a number of services existing like Corporate directory
|
|
0:23:51
|
intercom calls, missed calls, place calls
|
|
0:23:55
|
keep calls, personal directory and voice mail.
|
|
0:23:58
|
OK? So we do have a voicemail URL possible deployed
|
|
0:24:06
|
URL to phones, but we typically leave that blank because
|
|
0:24:10
|
or even Gen2 and Gen1 phones, what we typically use
|
|
0:24:13
|
is the voicemail pilot at the speed dial, but we
|
|
0:24:16
|
could replace that with something completely different.
|
|
0:24:21
|
We have directories as a URL that we
|
|
0:24:25
|
hand out to Gen2 and Gen1 phones
|
|
0:24:30
|
but in terms of the newer Gen3 and Gen4 phones.
|
|
0:24:34
|
For Corporate directory they use a service
|
|
0:24:38
|
an actual application that's built in and there's really no
|
|
0:24:42
|
place where you, like dive in here, it just shows new
|
|
0:24:44
|
the application is called, notice that this used to be called
|
|
0:24:49
|
xml services or IP phone services.
|
|
0:24:52
|
You could create XML based services which you still can
|
|
0:24:56
|
and you could also create java based services.
|
|
0:25:02
|
7970s are grandfather in to that older
|
|
0:25:07
|
I should say to the newer generation, so 7970 phones actually
|
|
0:25:11
|
of 8 mega flash memory so their firmware allows them to use
|
|
0:25:14
|
newer features like all these new services versus the old URLs.
|
|
0:25:20
|
The 60, 7960, 7940 older phones
|
|
0:25:24
|
they only have two meg of memory that's on their flash bank.
|
|
0:25:28
|
Actually, there two separate 1 meg flash banks.
|
|
0:25:33
|
The reason they cannot support any of the newer features,
|
|
0:25:38
|
they don't support globalization
|
|
0:25:42
|
which as we'll talk about in that separate module
|
|
0:25:46
|
one of the things that it means is basically that for
|
|
0:25:48
|
missed place and received calls those phones
|
|
0:25:51
|
don't store missed placed and receiced calls in their local
|
|
0:25:55
|
running memory any longer, the newer Gen3 and
|
|
0:26:01
|
as I mentioned back, grandfather DN
|
|
0:26:04
|
studying with this phone would be acceptable to getting
|
|
0:26:08
|
most of, maybe all the new features except for g722 maybe.
|
|
0:26:13
|
Is the 7970 phone that one actually is a Gen2 phone that can
|
|
0:26:17
|
be grandfathered in the supporting all these new features.
|
|
0:26:20
|
But what they do is instead of storing those numbers
|
|
0:26:24
|
locally and looking locally, they actually
|
|
0:26:27
|
place a skinny based programatic call back to CUCM
|
|
0:26:30
|
for the missed place and received calls application.
|
|
0:26:35
|
And look to where those are stored on the CUCM for
|
|
0:26:39
|
their respective call history. OK? So in essence
|
|
0:26:46
|
the answer is to most things yes, but not everything
|
|
0:26:50
|
another words idle and idle time still
|
|
0:26:54
|
take effect authentication still takes effect of Gen3,
|
|
0:26:59
|
phone proxy address, meesages doesn't
|
|
0:27:04
|
messages takes the voice mail application,
|
|
0:27:08
|
services though, services still do.
|
|
0:27:14
|
So we do have some things for the newer phones
|
|
0:27:17
|
that still use the URLs, but Corporate directory
|
|
0:27:25
|
this place received calls within the directories, but
|
|
0:27:31
|
voice mail, those don't use the URLs. So good question,
|
|
0:27:37
|
like I'm really glad you asked that, by the way also
|
|
0:27:42
|
started to mention, but was it phone services, here we go.
|
|
0:27:47
|
Failed to finish, all of these are built in applications
|
|
0:27:52
|
and as you note all of the URLs that I started to say
|
|
0:27:56
|
you can create, if I create and add new.
|
|
0:27:59
|
I can actually place something like you know
|
|
0:28:02
|
http://myserverip/mypage or myapp.asp or .php or
|
|
0:28:19
|
really anything that after its query returns xml
|
|
0:28:25
|
to the phone or return made of java for the phone
|
|
0:28:31
|
in following the IP phone services
|
|
0:28:36
|
developer guide or SDK, Softward Development Kit
|
|
0:28:41
|
and I can choose is it an xml service or a java midway.
|
|
0:28:45
|
OK, those still work perfectly fine however, note these are
|
|
0:28:51
|
they are xml services but they are specific to the
|
|
0:28:57
|
CUCM and that's why they're found in their application
|
|
0:29:00
|
colon which is basically a special or modify
|
|
0:29:02
|
or telling the phone, the phone already has program
|
|
0:29:04
|
in to its memory the Gen3 and Gen4 and 7970
|
|
0:29:08
|
grandfather in where that application URL is
|
|
0:29:12
|
and then in the directory of Cisco and
|
|
0:29:14
|
then the application called Missed calls.
|
|
0:29:18
|
No place that we actually assign this services
|
|
0:29:22
|
to the phones, they just, part of their default
|
|
0:29:26
|
programming as they know to access
|
|
0:29:30
|
Gen3 and 7970, these applications rather
|
|
0:29:35
|
than these URLs, so great question.
|
|
0:29:39
|
OK? So we've change our host name to IP address
|
|
0:29:43
|
and update successful.
|
|
0:29:47
|
OK? Looking still at enterprise parameters,
|
|
0:29:50
|
allow an IP phone user to customize the appearance
|
|
0:29:53
|
of line label from their CUCM user webpage.
|
|
0:29:57
|
Also allow IP phone users to change their call forward
|
|
0:30:00
|
all phone number however, do not allow them
|
|
0:30:03
|
to change any other type of call forward number.
|
|
0:30:06
|
So call forward all, not call forward busy or no answer
|
|
0:30:11
|
or no coverage or things of that nature.
|
|
0:30:14
|
And later after you auto register your phone
|
|
0:30:17
|
creating user and assign it to any phone
|
|
0:30:19
|
device, so do device association
|
|
0:30:22
|
and then log in to the CUCM
|
|
0:30:24
|
user webpage to verify the task works properly.
|
|
0:30:28
|
Alright, so they're still in Enterprise parameters
|
|
0:30:31
|
and we show the sub section of CUCM user parameter
|
|
0:30:35
|
there's a bunch of various ones here.
|
|
0:30:38
|
You can customize all of them and see all of
|
|
0:30:40
|
the default settings here to the right column
|
|
0:30:44
|
and we were told for call forwarding
|
|
0:30:47
|
not to show all setting, not to hide all settings,
|
|
0:30:50
|
but only show forward all.
|
|
0:30:53
|
OK? And notice that this will take effect on the next
|
|
0:30:56
|
refresh of the line settings configuration window
|
|
0:31:00
|
in the CUCM user option, another words if they're
|
|
0:31:02
|
already on the page and somebody's viewing at this moment
|
|
0:31:05
|
is not going to dynamically refresh their page.
|
|
0:31:10
|
And then what was the other thing we were told?
|
|
0:31:13
|
Allow them to customize the appearance of their line label,
|
|
0:31:16
|
so let's just do a search for label. Here we go, line text label.
|
|
0:31:21
|
I could have just look down there, but so in search feature.
|
|
0:31:25
|
Show line text label settings.
|
|
0:31:27
|
False. Also note for any, I mentioned this,
|
|
0:31:31
|
I believed yesterday, very important for any service parameters
|
|
0:31:37
|
there's many different services that have those parameters
|
|
0:31:40
|
and or for any Enterprise parameters.
|
|
0:31:44
|
The actual name of the field is phenomenal
|
|
0:31:48
|
context sensitive help, it pops out right there.
|
|
0:31:51
|
The help engine is just human readbale, very easy to follow
|
|
0:31:57
|
tells you any notes about i, tells you what are required
|
|
0:32:00
|
field, tells you what the default is although, you do see
|
|
0:32:03
|
that on the main page and gives you great description.
|
|
0:32:07
|
This parameter determines whether not the options you configure
|
|
0:32:09
|
the lines Line Text Label for a phone, appears on the Cisco
|
|
0:32:12
|
call manager users options CCM user window.
|
|
0:32:16
|
The users current device has lines configured, the user can view
|
|
0:32:19
|
and change the line text label for each phone, unless
|
|
0:32:23
|
the line is a primary line. Default is false.
|
|
0:32:28
|
We're told to show it, true.
|
|
0:32:32
|
OK? So always keep in mind the context sensitive help.
|
|
0:32:38
|
Also, if I do, this is another really really
|
|
0:32:42
|
great speed tip that you should take note of.
|
|
0:32:46
|
If I'm on any system service parameter or as I'm here
|
|
0:32:51
|
Enterprise parameter and I've been showing you hitting Ctrl left
|
|
0:32:54
|
mine shows up at the bottom and doing a search on let's say label.
|
|
0:32:59
|
OK? Or maybe I want to search on CCM user
|
|
0:33:03
|
and spell it correctly, now maybe that shows up, fine.
|
|
0:33:09
|
Maybe I wanted to search on forward all, OK?
|
|
0:33:14
|
Because I was told specifically, hey allow forward all.
|
|
0:33:17
|
Now, I could just search on forward, but that would be no fun.
|
|
0:33:21
|
I want to search on forward all, notice my Firefox window
|
|
0:33:26
|
search feature, find feature shows up as red,
|
|
0:33:30
|
it couldn't find, phrase was not found.
|
|
0:33:34
|
If you can't find what you're looking for in terms of a keyword
|
|
0:33:36
|
or a buzzword, to help you solve a task, which by the way
|
|
0:33:40
|
the proctors and the test writers, many times look in
|
|
0:33:44
|
surprise, surprise, the documentation or context sensitive
|
|
0:33:49
|
help which is many times taken from the documentation.
|
|
0:33:53
|
Or the buzzwords and keywords that don't show up
|
|
0:33:57
|
in the main interface with which to create questions and tasks and
|
|
0:34:04
|
things that aren't tricky, they're just or fundamental knowlege
|
|
0:34:08
|
or maybe anciliary knowledge maybe they deal with the feature that's
|
|
0:34:11
|
maybe not fundamental, but certainly deals with being an expert.
|
|
0:34:15
|
But that's the way to search, especially if you can't find
|
|
0:34:18
|
quickly what you're looking for with the Ctrl F
|
|
0:34:22
|
or you search through all of the options that do show up
|
|
0:34:26
|
with some results returned by a Ctrl F. Best thing you
|
|
0:34:30
|
can do even before you start searching
|
|
0:34:34
|
click on anyone of the context sensitive help bits
|
|
0:34:37
|
which if you'll notice doesn't just show you that, but also shows you
|
|
0:34:40
|
the next setting and the next setting and all the settings before it.
|
|
0:34:44
|
So scroll to the top, put your curser somewhere
|
|
0:34:47
|
and do a Ctrl F for forward all.
|
|
0:34:53
|
Guess what didn't show up on the main page, but did show up
|
|
0:34:57
|
on the context sensitive help page, that's great.
|
|
0:35:02
|
and guess what, it took me to the exactly the right one, now
|
|
0:35:05
|
so did click on forward on that page, I think so, actually
|
|
0:35:09
|
just search here, put my mouse up to the top.
|
|
0:35:14
|
OK, it did actually take me to the right on first time
|
|
0:35:18
|
however, they're going to be especially with service parameter
|
|
0:35:21
|
enterprise matters, you can see our scrolled
|
|
0:35:26
|
you know by going and scrolling top to bottom and
|
|
0:35:29
|
also the size of our scroll button, they aren't very many.
|
|
0:35:33
|
OK? So it's maybe a little less important here
|
|
0:35:37
|
there's still quite a bit to read then it is in service parameters,
|
|
0:35:40
|
but within service paramaters especially once you click on advance
|
|
0:35:44
|
and you always should. Click on service parameters, click on
|
|
0:35:48
|
for call manager advance, then click on, unless
|
|
0:35:52
|
you know exactly where to navigate to the first time and
|
|
0:35:54
|
even then I can probably take you there faster
|
|
0:35:56
|
than manually visually searching for it, click on the first field name
|
|
0:36:03
|
and then just do a Ctrl F or your search phrase
|
|
0:36:08
|
and it will 9 times out of 10, take you exaclty whre you want to go.
|
|
0:36:17
|
OK? We'll click save
|
|
0:36:23
|
Good, glad you think those are good steps, I think that will
|
|
0:36:27
|
well, I know for a fact that if you choose to use it, it will save you
|
|
0:36:31
|
a lot of times trying to search for either something that you have
|
|
0:36:35
|
no idea what they're asking, you just basically know a buzzword
|
|
0:36:39
|
in part of the task and they will put the buzzword in there, they just
|
|
0:36:43
|
tell you exaclty what to do, but a lot of times those buzzwords
|
|
0:36:47
|
copied and pasted or looked at and then keyed in to either
|
|
0:36:52
|
a context sensitive help query, find or the documentation itself
|
|
0:36:58
|
which remember I mentioned when and I'll keep saying this
|
|
0:37:03
|
over and over when going to the Cisco documentation website
|
|
0:37:06
|
and looking at any one of the guide, administration, system
|
|
0:37:10
|
it's probably just a good idea to begin with.
|
|
0:37:13
|
So just go download all the pdf's, maybe not right off the bat
|
|
0:37:16
|
but as you need them download the pdf in the actual lab exam
|
|
0:37:20
|
or practical exam and because you do have a pdf reader
|
|
0:37:25
|
and then press Ctrl F there because otherwise you'll be searching
|
|
0:37:28
|
page by page by page by clicking on the left bookmark.
|
|
0:37:34
|
So we've done bullet 1 and 2, we'll verify after we auto register phone.
|
|
0:37:40
|
More service paramaters, ensure that when any and again this
|
|
0:37:43
|
would be something where we wouldn't tell you service parameters.
|
|
0:37:46
|
And we also wouldn't have told you
|
|
0:37:49
|
Enterprise parameters for these tasks if this were a real
|
|
0:37:54
|
lab, mock lab or if it was in a real lab.
|
|
0:37:59
|
We also wouldn't tell you how to verify, we would hopefully
|
|
0:38:04
|
If you are ready to pass the exam, then I can
|
|
0:38:06
|
Emphatically say you would already know where to verify.
|
|
0:38:11
|
So ensure that when any IP phone goes to transfer
|
|
0:38:13
|
a call to another party that they have the ability to simply press
|
|
0:38:17
|
the softkey for transfer, then dial the number that you wish
|
|
0:38:20
|
to transfer to and then hang up without any further button presses.
|
|
0:38:27
|
OK? Now again I'm telling you system parameters, but
|
|
0:38:30
|
and I just have to again reemphasize they wouldn't tell you
|
|
0:38:35
|
where to find those so we will go where we know.
|
|
0:38:39
|
to system service parameters and we already have the right
|
|
0:38:44
|
all this fine because it's cluster wide parameter
|
|
0:38:47
|
so it doesn't matter which server and Cisco call manager
|
|
0:38:50
|
is the right subsection of service
|
|
0:38:55
|
and we know that it's transfer so let's juts go ahead and take our
|
|
0:39:01
|
advice and just open up help and do a search for transfer.
|
|
0:39:09
|
OK, show something in a cdr field, no that's not it
|
|
0:39:14
|
Let's look back at our task and see if there's
|
|
0:39:16
|
anything else that might have a clue in it.
|
|
0:39:19
|
Hanging up. OK, let's see if that shows up here
|
|
0:39:25
|
Find hang up.
|
|
0:39:27
|
OK, drop Ad Hoc Conference well the word hang up is there but
|
|
0:39:32
|
that's for Ad Hoc Conference SIP Dual Mode Alert Timer, No.
|
|
0:39:40
|
What's this one? Ad Hoc Conference, so we're back there
|
|
0:39:43
|
so that isn't going to be enough of one.
|
|
0:39:46
|
So we are going to probably need to rely on the transfer.
|
|
0:39:50
|
OK, keep clicking okay, until we find what it is.
|
|
0:39:58
|
Now this may not be the fastest one, sometimes your search
|
|
0:40:03
|
is, and I guess I would actually say your search is
|
|
0:40:07
|
going to be something you'll use either when you know
|
|
0:40:10
|
exactly where you want to go and in your self study
|
|
0:40:13
|
time you found the fastest keyword to search on,
|
|
0:40:17
|
which I could tell you what that keyword was.
|
|
0:40:19
|
In fact now already shows on the page, but
|
|
0:40:24
|
that's only if you knew from your self study time,
|
|
0:40:28
|
what it is you're looking for exaclty and you found they
|
|
0:40:32
|
nonambiguous or unique search term or buzzword.
|
|
0:40:37
|
The other option is that you don't know what to search for
|
|
0:40:42
|
except for a basic term like forward or hang up, we tried hang up
|
|
0:40:47
|
deal much so we can search for transfer and eventually
|
|
0:40:51
|
you might get to something like we did here.
|
|
0:40:53
|
This is in fact what we want, my resizing of the window
|
|
0:41:01
|
got rid of where were at and what I wanted
|
|
0:41:03
|
so I'm going to go ahead and search for the
|
|
0:41:05
|
buzzword or keyword that I know I want
|
|
0:41:08
|
because we had already found it once before
|
|
0:41:11
|
in our self city time which is on dash hook.
|
|
0:41:15
|
And that's not the one, on hook enabled
|
|
0:41:20
|
It doesn't show, there we go transfer on hook enabled,
|
|
0:41:23
|
so the second on hook was what I wanted this
|
|
0:41:26
|
parameter determines whether a call transfer complete as a result
|
|
0:41:29
|
of the user going on hook after initiating a transfer operation.
|
|
0:41:35
|
And then it even tells you valid value specify true which means
|
|
0:41:39
|
user presses the transfer softkey dials the number
|
|
0:41:43
|
and then presses the transfer sofkey again or
|
|
0:41:47
|
simply goes on hook to complete the transfer operation
|
|
0:41:52
|
OK? User dials the number, sorry, user presses
|
|
0:41:57
|
softkey for transfer, dials the number and then hangs up.
|
|
0:42:01
|
Now, this said user presses the softkey, dials the number
|
|
0:42:04
|
and then presses transfer softkey again or simply goes on hook.
|
|
0:42:10
|
That's exactly what we wanted, transfer on hook enable, so again
|
|
0:42:15
|
the context sensitive help verbose description
|
|
0:42:21
|
told us exactly what the functionality was
|
|
0:42:24
|
and exactly what we want so now we just search for on dash hook
|
|
0:42:28
|
in our main window, now that we already know
|
|
0:42:30
|
what it is we want based on the help window.
|
|
0:42:35
|
The searching for help window didn't you know
|
|
0:42:39
|
synchronize our help with our actual configuration value window.
|
|
0:42:45
|
The transfer on hook enabled, False. We set to True, done.
|
|
0:42:52
|
OK?
|
|
0:42:55
|
Next 1.12, we're told to change the default
|
|
0:42:59
|
interdigit time out from 15 seconds to 5 seconds.
|
|
0:43:05
|
OK?
|
|
0:43:06
|
Let's try that again, let's just click on any field
|
|
0:43:10
|
bring up context sensitive help
|
|
0:43:12
|
just roll to the beginning since we didn't necessarily
|
|
0:43:16
|
just go ahead and expand this to begin with.
|
|
0:43:20
|
Place our curser up here somehow and say
|
|
0:43:24
|
What was they keyword? Interdigit. Interdigit.
|
|
0:43:32
|
Parameters specifies an interdigit timer
|
|
0:43:35
|
for sending in the SET UP ACK or acknowledgement messages
|
|
0:43:39
|
The timer restarts each time call manager
|
|
0:43:41
|
receives a digit, the interdigit time out.
|
|
0:43:46
|
For exact time or definitions refer to the Q931 specification,
|
|
0:43:50
|
wait a minute, why is this a T302 timer and the Q931 specification
|
|
0:44:01
|
Why is this talking about Q931? What is Q931?
|
|
0:44:04
|
Let's make sure everyone's awake.
|
|
0:44:07
|
Ris, what is Q931 use for? What protocol? ISTN absolutely.
|
|
0:44:14
|
OK? I thought we were talking about
|
|
0:44:20
|
It says change the default interdigit time out
|
|
0:44:22
|
doesn't really say just for ISTN.
|
|
0:44:27
|
It is seemingly sounds like with default,
|
|
0:44:31
|
seemingly for all phones. Right? So that's the case,
|
|
0:44:38
|
what is it were talking about here for referring to Q93,
|
|
0:44:43
|
but that refers to as everyone is properly answered now ISTN.
|
|
0:44:52
|
Why would we be talking about ISTN in relation to regular
|
|
0:44:56
|
IP phones, skinny based IP phones.
|
|
0:45:03
|
Well, keep in mind that the ITUT
|
|
0:45:12
|
International Telecommunications Union
|
|
0:45:18
|
specifies or created the ISTN protocol or
|
|
0:45:27
|
What we would in the ITF or Internet call a request for comment or RFC.
|
|
0:45:36
|
They created their specs or specification is how they refer to them
|
|
0:45:40
|
for ISTN, then later in years, they came up with
|
|
0:45:47
|
a internet based modification of their existing and
|
|
0:45:52
|
really well working, so well that we still use quite prevalantly today
|
|
0:45:57
|
an internet modification of their ISTN protocol and they call it H.323.
|
|
0:46:07
|
Then before Cisco was around, well I shouldn't say
|
|
0:46:12
|
before they were aound rather, before they had purchased
|
|
0:46:14
|
the company called Celsius, Celsius creates this IP PBX.
|
|
0:46:19
|
and calls it call manager and they say, hey you know what
|
|
0:46:23
|
H323 is great, SIP is still kind of an infancy.
|
|
0:46:28
|
So it really doesn't do merely what we needed to, yet.
|
|
0:46:32
|
H323 is great however, there's a lot of things that it doesn't do,
|
|
0:46:37
|
that we would have to enhance or some things that
|
|
0:46:41
|
it doesn't do as well as we'd like it to do and it's a really loud
|
|
0:46:46
|
chatty protocol, I mean it just has a ton of messages
|
|
0:46:50
|
anyone ever done a debug H225 ASN1 on a router knows that.
|
|
0:46:57
|
So rather than using H323 on modified, we definitely need
|
|
0:47:01
|
to modify it for a number of things.
|
|
0:47:05
|
But we don't exactly just want to come up with our own
|
|
0:47:07
|
brand new protocol, so what we'll do is we'll take the
|
|
0:47:11
|
best of the H323 world and we'll condense it down to a lot of
|
|
0:47:17
|
coming from a networking background versus the ITUT
|
|
0:47:20
|
coming from a telefany background trying to internet modify things.
|
|
0:47:24
|
We'll make it skinny, we'll make it a skinnier version of the protocol
|
|
0:47:30
|
which is where we get the notation for SCCP, the skinny
|
|
0:47:36
|
the skinny control protocol. OK? So skinny is based or SCCP is
|
|
0:47:43
|
based on H323 which is based on ISTN, so that's the reason
|
|
0:47:48
|
telling you if you want exact time or definitions
|
|
0:47:51
|
Prefer to the Q939 spec because hey we didn't
|
|
0:47:53
|
really change the certain things such as timer.
|
|
0:47:59
|
Timer specifications or timer definition
|
|
0:48:02
|
OK, this T302 is for skinny based phone, so let's just
|
|
0:48:07
|
do a search on the main page for T302 and
|
|
0:48:14
|
we find H225, T302, wait a minute
|
|
0:48:20
|
Take a look the main section clusterwide parameters device H323
|
|
0:48:25
|
We did just mentioned that skinny based phones a re derivative
|
|
0:48:30
|
of H323, does that mean that they actually
|
|
0:48:35
|
are H323 devices can fall on this? No.
|
|
0:48:38
|
keep in mind the field name that we just saw was not
|
|
0:48:41
|
H225 T302 Timer it was simply T302 Timer.
|
|
0:48:47
|
Now the confusing thing is in previous versions of call manager
|
|
0:48:51
|
it actually or I should say both, there's a queue here,
|
|
0:48:54
|
both did actually happen to be called T302 Timer
|
|
0:48:57
|
but they were under separate settings, separate sub
|
|
0:49:02
|
Let's just say, previous, there we go, now under cluster
|
|
0:49:06
|
wide parameters device general, we have our T302 Timer.
|
|
0:49:14
|
Now both were T302, one is related to device general or
|
|
0:49:19
|
skinny based phones and gateways and devices.
|
|
0:49:22
|
the other is H225 T302 derived in the call set up of h323
|
|
0:49:29
|
only gateways and trunks, so there is a differentiation
|
|
0:49:33
|
as to, they both affect the same thing, interdigit time out
|
|
0:49:37
|
but for different sets of devices as it relates to Cisco call manager.
|
|
0:49:43
|
So 15,000 well we can probably assume or we can just
|
|
0:49:48
|
pull that back up and find out that the unit of measurement,
|
|
0:49:55
|
once it settles down is in milliseconds.
|
|
0:49:58
|
The minimum is 3 and the maximum is 75,000 or 75 seconds
|
|
0:50:05
|
There would be a long interdigit time. What were we told?
|
|
0:50:08
|
To put it to 5 seconds, so we have to say 5,000
|
|
0:50:13
|
milliseconds, since there a thousand of millliseconds in a second.
|
|
0:50:18
|
OK? So what I'm trying to teach you here
|
|
0:50:21
|
is by no means what every single service parameter can do,
|
|
0:50:26
|
we may have another module just on all service plus there are so many.
|
|
0:50:31
|
Even then we couldn't go over every single one and
|
|
0:50:34
|
I would probably bore you to death if I went to every single one.
|
|
0:50:38
|
But what we can say is that, what I'm trying to
|
|
0:50:44
|
teach now before we actually get to a separate module
|
|
0:50:47
|
just of service parameters is how to effectively
|
|
0:50:51
|
use service parameters. We'll cover a number of these
|
|
0:50:54
|
service parameters as we come to their relevancy in each modules,
|
|
0:50:57
|
so for instance QOS and RSVP, there's clusterwide parameters
|
|
0:51:03
|
just for those. So when we talk about QOS and RSVP
|
|
0:51:07
|
which we actually see like RSVP fails, RSVP fails for audio
|
|
0:51:13
|
and QOS settings we will talk about service parameters,
|
|
0:51:17
|
as we come to the four places that have
|
|
0:51:21
|
QOS service parameters set is by no means the only
|
|
0:51:24
|
one or other service parameters and even Enterprise parameters
|
|
0:51:28
|
that have QOS settings so as we come to a module that
|
|
0:51:31
|
necessitates or it becomes relevant, we'll talk about the relevant
|
|
0:51:36
|
service and Enterprise parameters, but again I'm trying to
|
|
0:51:43
|
do teach how to use and look through the service parameter.
|
|
0:51:48
|
It's also a good idea just simply to you know at some point
|
|
0:51:55
|
and maybe multiple points during your studies
|
|
0:51:57
|
just sit there and start from the top, scroll down and it might
|
|
0:52:01
|
take you days because it might be kind of so
|
|
0:52:05
|
so much of some degree, a mundane task to look
|
|
0:52:09
|
through each and everyone that you might get kind of bored reading
|
|
0:52:12
|
the basic ones like Code Yellow Entry Latency for instance
|
|
0:52:15
|
call through our line but keep in mind they're all valid
|
|
0:52:21
|
testable topics. This really where the meat of
|
|
0:52:25
|
CUCM call manager is here in the service parameters
|
|
0:52:30
|
but
|
|
0:52:33
|
it's probably a good idea to look through all of them
|
|
0:52:35
|
every single time a new release of call manager comes out
|
|
0:52:39
|
one of the first things that I always do.
|
|
0:52:41
|
Even if it's just like from let's say 71 to 72
|
|
0:52:46
|
certainly from version 6 to version 7 or version 7 to version 8
|
|
0:52:50
|
or 8 to 9 or whatever, I always look through the service parameters
|
|
0:52:54
|
and try to pick out ones that are new, that I haven't seen before
|
|
0:52:58
|
because as new features get introduced into call manager.
|
|
0:53:03
|
The very first place they show is globally
|
|
0:53:06
|
affecting all devices under service parameters
|
|
0:53:09
|
and then they end up making their way out to the
|
|
0:53:12
|
individual devices themselves for more granularity.
|
|
0:53:17
|
OK? You know one of the things that comes to mind is like
|
|
0:53:23
|
Let's see calling party
|
|
0:53:31
|
no that's not it, let's say let's use the keyword national then OK
|
|
0:53:40
|
subscriber?
|
|
0:53:45
|
Know that right? OK, here some place, I'll just click on the
|
|
0:53:51
|
context sensitive help and
|
|
0:53:55
|
bottom, but scroll over to the top.
|
|
0:54:01
|
Try to search for subscriber.
|
|
0:54:15
|
I think they did, they may have actually
|
|
0:54:20
|
let it out now, but I don't think they have
|
|
0:54:23
|
What was I getting to was, we were just on device pool.
|
|
0:54:27
|
and under device pool, we found incoming calling party settings
|
|
0:54:32
|
or national, international unknown subscriber
|
|
0:54:35
|
and again we're going to talk about those on another day
|
|
0:54:37
|
but we do see that if the administrator presents the prefix
|
|
0:54:40
|
to Default this indicates call processing we used
|
|
0:54:43
|
prefix at the next level or we're already at device pool so this was.
|
|
0:54:46
|
If you didn't set it up the gateway then it would use it
|
|
0:54:49
|
at the device pool level and then it would use it at the service
|
|
0:54:51
|
parameter level, so I just have to look and find, but it is in here
|
|
0:54:56
|
but without spending too much time trying to find it
|
|
0:55:02
|
the idea that I'm trying to get to is before they move this feature
|
|
0:55:06
|
incoming calling party settings out to the device pool
|
|
0:55:08
|
and also to the device which was in CUCM 7.0
|
|
0:55:13
|
as the beginning of announcing support for globalization
|
|
0:55:18
|
before they have it there, they've had it in service parameters
|
|
0:55:21
|
years, I mean back on call manager 33 it was there.
|
|
0:55:25
|
and you could try to make it work for you, unfortunately
|
|
0:55:27
|
it was so, so much of a global setting that it really didn't
|
|
0:55:31
|
yield many benefits, you know you could put a 9 in
|
|
0:55:35
|
depending on if you had multiple gateways in different locations.
|
|
0:55:38
|
It would prefix a 9 to everything, it just wasn't granular enough
|
|
0:55:42
|
but the idea was that the feature was there
|
|
0:55:45
|
long before it was granular enough to be used everywhere.
|
|
0:55:49
|
So again the focus of the idea being that if you,
|
|
0:55:57
|
if you look everytime and new version comes out
|
|
0:56:00
|
you' re definitely bound to find new features
|
|
0:56:04
|
here before anywhere else, before you'll find them on the
|
|
0:56:07
|
device gateway or device phone page. OK, so moving on,
|
|
0:56:14
|
Now, we're told finally to deal with some phones
|
|
0:56:18
|
so here we're told for phone button and softkey templates
|
|
0:56:22
|
create a new phone button template for 7961 type phone
|
|
0:56:25
|
both skinny and SIP that allows for in this order
|
|
0:56:30
|
two lines, two busy lamp field speed dials
|
|
0:56:34
|
one call park busy lamp field and one intercom DN.
|
|
0:56:39
|
Then we're told to create a new softkey template
|
|
0:56:42
|
Separate from a phone button template for 7961 type
|
|
0:56:45
|
type phones both skinny and SIP that allows for
|
|
0:56:49
|
an IP phone user to forward any incoming ringing calls
|
|
0:56:53
|
directly to voice mail eventhough we may not have
|
|
0:56:55
|
voicemail set up, we can use another number to
|
|
0:57:01
|
test it if we don't happen to have it set up or you
|
|
0:57:03
|
don't happen to have it set up, if you're watching this later.
|
|
0:57:07
|
Can perform a quality report on any calls that are already
|
|
0:57:10
|
in progress and connected, then we're told to ensure that
|
|
0:57:14
|
both of thses phones, both of these new template
|
|
0:57:18
|
are the default for any newly created or auto registered IP phones
|
|
0:57:23
|
and then also to ensure that any newly created or
|
|
0:57:25
|
auto registered IP phones have the default functionality
|
|
0:57:29
|
that when they select Do Not Disturb, the DND softkey
|
|
0:57:33
|
that all incoming calls forward automatically to voicemail
|
|
0:57:37
|
which as, seems to indicate and I can tell you
|
|
0:57:41
|
is not the defualt behavior. OK, so we've got a lot to do here
|
|
0:57:46
|
go ahead and go back to our interface
|
|
0:57:49
|
and device, device settings, phone button template
|
|
0:57:54
|
is the first place we want to be, let's actually scroll to the
|
|
0:57:56
|
top of our service parameters, make sure we did an update
|
|
0:57:59
|
successful, good. After we change the T302 interdigit time out.
|
|
0:58:07
|
OK, phone button template. Let's search for phone button templates
|
|
0:58:13
|
and we were told for 7961 phones for both skinny and SIP,
|
|
0:58:18
|
now note I keep searching for 7961,t here's actually four of them
|
|
0:58:24
|
because I have the 7961 skinny and SIP and then
|
|
0:58:27
|
the 61GE skinny and SIP. I all need to did it
|
|
0:58:31
|
for all four if I want to meet the criteria.
|
|
0:58:36
|
OK? So let's just open this
|
|
0:58:40
|
holding down my whatever key opens in a new tab for you.
|
|
0:58:46
|
and I'm going to make a copy of each one.
|
|
0:58:50
|
So I'll call this not standard but enhanced,
|
|
0:58:57
|
say module 3 enhanced.
|
|
0:59:05
|
Save.
|
|
0:59:07
|
Copy on this one.
|
|
0:59:10
|
For module 3 enhanced save for SIP
|
|
0:59:15
|
Make a copy on my GE skinny.
|
|
0:59:19
|
Module 3 enhanced.
|
|
0:59:22
|
and make a modification copy on my 61GE SIP phone or enhanced
|
|
0:59:30
|
OK? So what were we told? Two lines
|
|
0:59:34
|
Look likes we already have that line and line.
|
|
0:59:37
|
OK, so we're good there.
|
|
0:59:40
|
2 busy lamp fields speed dials, by the way in this order
|
|
0:59:46
|
So we've already got speed dials right? No,
|
|
0:59:49
|
that's just a speed dial, we need a speed dial BLF
|
|
0:59:52
|
or busy lamp field speed dial for each
|
|
0:59:58
|
Then what did we want?
|
|
1:00:00
|
Call 1, Call park busy lamp field, different from just call park
|
|
1:00:08
|
got call park and then call park BLF then we can change
|
|
1:00:11
|
the label if we want this is not what's going to show up
|
|
1:00:13
|
on the phone. This si what's going to show up in the
|
|
1:00:16
|
phone device web admin interface
|
|
1:00:21
|
and then we were told one intercom DN.
|
|
1:00:25
|
So let's choose intercom DN and we'll click save.
|
|
1:00:32
|
see was update successful, actually at the bottom
|
|
1:00:38
|
has done and nothing is there, this is possibly because I
|
|
1:00:45
|
that's the idea of module 3 enhanced 7961 skinny,
|
|
1:00:50
|
but it didn't save any things, dial BLF, dial BLF
|
|
1:00:59
|
or is it call park, intercom, call park BLF rather and then intercom
|
|
1:01:06
|
Let's see if it does this again, there we go update successful, close that one
|
|
1:01:13
|
dial BLF, speed dial BLF, call park BLF and intercom.
|
|
1:01:24
|
and we got nothing again
|
|
1:01:28
|
Awesome, I'll just close this window and will come back to it.
|
|
1:01:30
|
it could be because I open multiple windows and just because
|
|
1:01:38
|
internet explorer is still the best browser to configure
|
|
1:01:45
|
CUCM on evethough Firefox is supposed to be supportive
|
|
1:01:53
|
Click on our skinny just to make sure all those settings took, they did
|
|
1:01:59
|
SIP, enhanced, none did Alright, let's do it agagin real quick
|
|
1:02:04
|
speed dial BLF, Call Park BLF
|
|
1:02:08
|
intersom save, crosse our fingers, update successful.
|
|
1:02:16
|
Any GE, speed dial BLF, speed dial BLF, Call PArk BLF, Intercom
|
|
1:02:24
|
OK. Update Successful.
|
|
1:02:31
|
SIP good and our last one our GE SIP.
|
|
1:02:37
|
Speed dail BLF, speed dial BLF, call park BLF and then intercom
|
|
1:02:42
|
OK, hopefully update successful. Great.
|
|
1:02:48
|
First bullet and some bullets done. Now create a new softkey
|
|
1:02:52
|
template for 7961 type phones both skinny and SIP
|
|
1:02:56
|
it allows for these features, right.
|
|
1:02:59
|
Go to device settings, softkey template
|
|
1:03:07
|
Now wait a minute, I don't see them per device
|
|
1:03:10
|
now they aren't per device, they're just softkey templates
|
|
1:03:13
|
so this is kind of a relevant information, just this bit here
|
|
1:03:18
|
we are going to in fact create a softkey template
|
|
1:03:21
|
for 61 skinny and SIP, it just so happens they're not uniquely
|
|
1:03:28
|
uniquely set to those. OK, so we can allow them for
|
|
1:03:34
|
there able to be used for any phones that will support
|
|
1:03:36
|
the softkey templates or softkey templates in general.
|
|
1:03:39
|
So let's just take standard user, have to copy it.
|
|
1:03:45
|
Copy and call it, again just like we did
|
|
1:03:56
|
by the name. Note what we can do here this did say that
|
|
1:04:01
|
ensure any newly created or auto registered IP phones
|
|
1:04:04
|
have the default function, sorry that's the wrong one.
|
|
1:04:07
|
Ensure that both of these new templates are the default
|
|
1:04:10
|
for any newly created or auto registered phone.
|
|
1:04:12
|
Now we didn't see anything like this, default softkey template
|
|
1:04:16
|
which says this will remove the previously assigned default template.
|
|
1:04:23
|
OK? We didn't have anything like that for
|
|
1:04:28
|
our phone button templates, but we're going
|
|
1:04:32
|
to explore for how they do that in another way.
|
|
1:04:35
|
We could have done the another way for softkeys as well, but
|
|
1:04:40
|
showing you another option, there are typically multiple ways
|
|
1:04:43
|
to accomplish your task and as long as it needs the
|
|
1:04:47
|
requirements and it doesn't violate any restrictions
|
|
1:04:50
|
within the task or even in other tasks because there are
|
|
1:04:54
|
interactions or surprise surprise internet working
|
|
1:04:59
|
INCCIE between tasks so, tasks can post restrictions
|
|
1:05:06
|
on one another, but as long as we didn't violate any
|
|
1:05:11
|
restrictions and we met the requirements, we can configure
|
|
1:05:15
|
in whatever fashion we want, we can do this here and the
|
|
1:05:20
|
phone button template assigned to a default
|
|
1:05:22
|
something else that we do that later in another way.
|
|
1:05:28
|
OK? So related task Configure Softkey Layout,
|
|
1:05:30
|
that's where we going to go to next. Now notice that we
|
|
1:05:33
|
have a number of calls states with which we can configure
|
|
1:05:38
|
unselected softkeys to the selected or
|
|
1:05:43
|
assigned softkeys to that particular call state
|
|
1:05:46
|
we've got on hook, so the, we either
|
|
1:05:51
|
speaker phone is not activated, headset is not activated
|
|
1:05:54
|
where the actual headset is on the hook connected.
|
|
1:05:57
|
So we've already gone off hook place the call or
|
|
1:06:01
|
received the call and we are in connected state
|
|
1:06:04
|
on hold speaks for itself, ring in. There's a call coming
|
|
1:06:07
|
into us, but it's not yet answered or else it would be connected
|
|
1:06:11
|
off hook, that is we press speaker phone
|
|
1:06:14
|
or press headset or lifeted the handset from the hook
|
|
1:06:21
|
gone off hook, but we haven't yet dialed to be
|
|
1:06:25
|
in a ring out state, which is another state.
|
|
1:06:29
|
OK?
|
|
1:06:31
|
Off hook with feature connected conference,
|
|
1:06:34
|
we're connected into a conference, we are connected in
|
|
1:06:36
|
to a transfer any digits after the first digit
|
|
1:06:40
|
so that is we've gone off hook or not in a ring out
|
|
1:06:43
|
or a connected state yet but we press at least the
|
|
1:06:47
|
first digit, so anytime after there, then we can do something.
|
|
1:06:51
|
Remote in use, if it's a shared line. OK? So
|
|
1:06:57
|
there's various states, so what states were we told?
|
|
1:07:01
|
IP phone should be able to forward any incoming ringing calls
|
|
1:07:05
|
directly to voice mail so that would be the ring in state.
|
|
1:07:11
|
and we only have 3, so it's undefine,undefine.
|
|
1:07:15
|
You're not disturb? No, immediate divert
|
|
1:07:18
|
sure sounds we're diverting a call somewhere.
|
|
1:07:22
|
and we're diverting it to our call forward
|
|
1:07:25
|
no answer state or call forward busy state.
|
|
1:07:31
|
Save.
|
|
1:07:33
|
Rest would reset any phones that happened to be using
|
|
1:07:36
|
the softkey template, right now there no phones registered.
|
|
1:07:40
|
What was the next one? Allow the phones to
|
|
1:07:44
|
perform a quality report on any calls that are already in
|
|
1:07:47
|
progress and I would only have to say already in progress
|
|
1:07:52
|
But I want ahead and it's nice and said connected.
|
|
1:07:54
|
In progress call is going to be a connected call
|
|
1:07:58
|
I can add the quality report tool which is something
|
|
1:08:01
|
built in to CUCM assuming that under serviceability
|
|
1:08:04
|
the service has been started, but we started all services.
|
|
1:08:08
|
So that's good.
|
|
1:08:11
|
Didn;t say at what place it has to be. OK, so
|
|
1:08:15
|
on a phone with 4 softkeys, you would have hold, end call,
|
|
1:08:18
|
transfer and then the fourth key would be more
|
|
1:08:23
|
park conference, conference list more, but if this softkey
|
|
1:08:26
|
template were on let's say a 7970, 75 or something with 5 button
|
|
1:08:32
|
then we would have hold, end call, transfer, park and then more
|
|
1:08:36
|
order which these buttons are going to show up, well actually
|
|
1:08:39
|
I'll be the same but how many buttons show up per screen.
|
|
1:08:44
|
Save.
|
|
1:08:48
|
OK?
|
|
1:08:50
|
So now ensure that both these are the newly
|
|
1:08:54
|
sorry, or the default templatesfor newly
|
|
1:08:56
|
created or auto registered phones, well we
|
|
1:08:59
|
going back to the softkey template configuration already
|
|
1:09:02
|
did that for softkeys, but if we look back at device
|
|
1:09:07
|
settings phone button template and we choose any
|
|
1:09:09
|
one of our new phone button templates
|
|
1:09:13
|
We didn't see default anywhere, OK?
|
|
1:09:18
|
So that's not something we can do here.
|
|
1:09:21
|
|
