|
0:00:13
|
Now we're ready to move on to Cisco Unified CM Group,
|
|
0:00:18
|
buolt to modify the default CUCM group.
|
|
0:00:21
|
The group we're instructed should prioritize the subscriber
|
|
0:00:25
|
call processing engine over the publisher
|
|
0:00:29
|
CPE or Call Processing Engine.
|
|
0:00:32
|
Or else we're told to rename the group to something intuitive
|
|
0:00:34
|
that will allow for later CUCM
|
|
0:00:37
|
web user interface, easy recognition of the orders
|
|
0:00:41
|
of the servers they're in.
|
|
0:00:45
|
OK? So let's go up to our next item, Cisco Unified CM.
|
|
0:00:50
|
We will find two CMs here,
|
|
0:00:52
|
actually we're told to go to the group first.
|
|
0:00:55
|
And there's a reason we're going to the group
|
|
0:00:57
|
and modifying the order here first.
|
|
0:01:02
|
So we're told to name it something intuitive, so let's say
|
|
0:01:06
|
CUCM, maybe Group 1.
|
|
0:01:11
|
Or let's call it group with sub then pub.
|
|
0:01:19
|
OK.
|
|
0:01:21
|
And note that these are not the names of the servers,
|
|
0:01:24
|
they're the names of the CISCO Unified CM.
|
|
0:01:28
|
OK? Note the difference between the server and the CM
|
|
0:01:32
|
in terms of namin. The server itself
|
|
0:01:37
|
is of course the host or IP address name.
|
|
0:01:40
|
And the CUCM server is the way that the rest of the system
|
|
0:01:44
|
interfaces. So we've prioritized the sub above the pub.
|
|
0:01:48
|
We'll change the naming of these later, actually the next task
|
|
0:01:52
|
under Cisco Unified CM and that will naturally change it here.
|
|
0:01:54
|
We don't have to come back to do anything.
|
|
0:01:58
|
OK? So update was successful. You should see the new group.
|
|
0:02:02
|
Drop down into it, just make sure our change is saved,
|
|
0:02:05
|
they did and we're good.
|
|
0:02:08
|
So now we move, Task 1.3, Cisco Unified CMs.
|
|
0:02:13
|
Enable auto-registration for only the proper
|
|
0:02:16
|
Cisco Unified Communications Manager.
|
|
0:02:20
|
So what does this mean for only the proper Unified CM?
|
|
0:02:24
|
Well this was the reason that we did Task 1.2 first.
|
|
0:02:28
|
Or that it was given to us first, we were told
|
|
0:02:31
|
that the group should prioritize the subscriber,
|
|
0:02:33
|
CPE over the publisher CPE. So that means that the only
|
|
0:02:38
|
Cisco Unified CM that needs auto-registration,
|
|
0:02:42
|
assuming that both sub and pub are alive on the system,
|
|
0:02:47
|
on the network and that they're call manager services are both running.
|
|
0:02:53
|
Then the only one we should enable auto registration on is the subscriber.
|
|
0:02:58
|
In fact, if both are running, the only
|
|
0:03:01
|
server that will process autoregistration is the subscriber.
|
|
0:03:04
|
We could enable it on the publisher as well,
|
|
0:03:07
|
in the event that the subscriber should loose connectivity or the
|
|
0:03:11
|
call manager service should fail or something of that nature,
|
|
0:03:14
|
but in this task, we're instructed not to.
|
|
0:03:17
|
We're instructed to assign the auto-registration range of DNs
|
|
0:03:20
|
to be 5000 to 5999 so a thousand DN range.
|
|
0:03:26
|
And then to erase these DNs from the system once auto-registration
|
|
0:03:29
|
has been completed after a later task.
|
|
0:03:32
|
We're kind of told ahead of time that we're going to be
|
|
0:03:36
|
instructed to do auto-registration later and once
|
|
0:03:39
|
that's done to erase the DN.
|
|
0:03:41
|
Also to note the port numbers that are here for easy later reference.
|
|
0:03:45
|
We'll go over other places that port numbers available.
|
|
0:03:48
|
Most specifically probably on Friday
|
|
0:03:51
|
when we discuss the quality of service module.
|
|
0:03:57
|
So here we'll go up to system,
|
|
0:04:00
|
Cisco Unified CM and is everyone able to
|
|
0:04:06
|
keep up with the screen refreshes? I want to make sure that
|
|
0:04:10
|
nobody is seeing a blank or black page.
|
|
0:04:16
|
So next we'll go into the subscriber server.
|
|
0:04:23
|
And we could go ahead and rename it if we'd like,
|
|
0:04:26
|
we could rename it to CM_subscriber
|
|
0:04:34
|
and the description,
|
|
0:04:39
|
we'll call it CUCM subscriber
|
|
0:04:44
|
CPE, the starting number.
|
|
0:04:48
|
Now note, don't uncheck auto-registraiton disabled
|
|
0:04:52
|
before defining your range. First off, as we mentioned
|
|
0:04:55
|
in another module yesterday, that the auto-registration
|
|
0:04:59
|
will automatically uncheck as soon as define range, but if we uncheck this
|
|
0:05:03
|
we'll get the error that to enable auto-registration
|
|
0:05:06
|
to starting directory and ending directory number must
|
|
0:05:09
|
have a valid directory number and currently they don't.
|
|
0:05:11
|
They allow exactly one phone in the DN of 1000.
|
|
0:05:14
|
So that's not a valid range, so we were instructed 5000.
|
|
0:05:19
|
All that the range starting number currently is lower
|
|
0:05:23
|
or equal to the ending number.
|
|
0:05:25
|
Now 5999 and as soon as I go,
|
|
0:05:28
|
tab off of this, now auto-registration automatically.
|
|
0:05:37
|
We see that it automatically gets unchecked.
|
|
0:05:43
|
OK? Currently for the partition, we don't have any partitions or
|
|
0:05:47
|
calling search spaces, no class of restriction,
|
|
0:05:50
|
We're going to be discussing that
|
|
0:05:52
|
in the dial plan module in a few weeks so
|
|
0:05:55
|
that is not something that we need to
|
|
0:05:58
|
be concerned about at this moment.
|
|
0:06:00
|
We we're instructed to note the ports.
|
|
0:06:03
|
OK? So these are the default ports. We can change these ports.
|
|
0:06:07
|
So ethernet phone port, MGCP listen port, ethernet
|
|
0:06:11
|
phone is 2000. We're always instructed or told to use 2000
|
|
0:06:18
|
through 2002. Anyone know what 2001 and 2002 TCP ports are used for?
|
|
0:06:27
|
Trivia here.
|
|
0:06:32
|
Make sure everyone's paying attention.
|
|
0:06:35
|
Anyone else care to join in on the question and answer
|
|
0:06:38
|
for port 2001 or 2002?
|
|
0:06:48
|
OK? So one person answered correctly, 2001
|
|
0:06:54
|
is used for the older analogue Skinny devices
|
|
0:06:58
|
and 2002 was used for the digital Skinny devices.
|
|
0:07:01
|
So these are the older
|
|
0:07:05
|
blades that's used to go in. Let's say for instance the
|
|
0:07:08
|
6500 CAT OS switches that had a number of,
|
|
0:07:14
|
some people I suppose use this, analogue or digital
|
|
0:07:20
|
FXS and various ports like that. The digital we're actually
|
|
0:07:24
|
the old SEP, actually were called like the VIP 30 phones.
|
|
0:07:29
|
The VIP 30 phones, some of the original
|
|
0:07:32
|
Skinny devices, but 2000 is what we use for all modern
|
|
0:07:36
|
Skinny.
|
|
0:07:38
|
2427 UDP is MGCP listen,
|
|
0:07:42
|
and 2428 TCP is keep alive also
|
|
0:07:47
|
Q931 back haul for BRI and PRIs.
|
|
0:07:51
|
SIP phones are 5060 and secure are 5061. This doesn't deal with
|
|
0:07:56
|
secure Skinny which is actually 2443 2000 plus 443.
|
|
0:08:03
|
OK? And actually this is a TCP for MGCP keep alive.
|
|
0:08:08
|
There is also 24 27 UDP,
|
|
0:08:15
|
24 28 TCP for MGCP communications as well.
|
|
0:08:20
|
We'll look at more information on that
|
|
0:08:22
|
when we discuss QOS and we'll actually look at the Cisco
|
|
0:08:27
|
Unified Communications manager security guide
|
|
0:08:31
|
and port number guide.
|
|
0:08:36
|
OK? So we've saved this, so subscriber has the proper
|
|
0:08:42
|
auto-registration defined. We'll go ahead and rename this just to follow suit.
|
|
0:08:57
|
Leave auto-registration off.
|
|
0:09:03
|
OK? So it should still be enabled on the subscriber, it is.
|
|
0:09:07
|
And we should be good to go there.
|
|
0:09:17
|
So the next task 1.4 asks us to
|
|
0:09:21
|
look at date and time group to create three date time groups.
|
|
0:09:25
|
One group is going to be used for our Corporate Headquarter devices
|
|
0:09:28
|
and should be in the Pacific Standard Timezone
|
|
0:09:30
|
and allow for daylight savings. One group is for Branch1 devices
|
|
0:09:35
|
and should be in the Central Standard Timezone and allow for daylight savings.
|
|
0:09:40
|
And one group is for all Branch2 devices
|
|
0:09:42
|
and should be in the central Standard European Timezone
|
|
0:09:45
|
and also allow for daylight savings.
|
|
0:09:48
|
However as a subset to this CEST,
|
|
0:09:54
|
we're instructed to change the daytime to allow for a format
|
|
0:09:57
|
or the day comes before the month, and a dot
|
|
0:10:01
|
is in between section of numbers.
|
|
0:10:04
|
Also do not allow an A or a P to display
|
|
0:10:07
|
after the time on the IP phones.
|
|
0:10:10
|
So we're not being as straight forward as we could with the wording,
|
|
0:10:14
|
OK, we're not just in a similar fashion to the CCIE
|
|
0:10:19
|
labs, CCIE Practical Exam or some call it.
|
|
0:10:25
|
We are being a bit ambiguous, we're not just giving a straight
|
|
0:10:30
|
forward taks of what to configure, however
|
|
0:10:33
|
we're not, we are giving plenty enough information
|
|
0:10:36
|
that you can figure out what to do
|
|
0:10:38
|
and the truth be told, we're actually not being very
|
|
0:10:44
|
what's the right word, we're not being too concealing with the wording
|
|
0:10:48
|
at this point. We're not concealing what we want done, we're actually
|
|
0:10:51
|
pretty fairly straight forward. We could be a lot more
|
|
0:10:59
|
could be a lot more concealing with the wording.
|
|
0:11:01
|
So let's take a look at our interface
|
|
0:11:05
|
or we alreadr talked about NTP phone reference the other day.
|
|
0:11:11
|
We already talked about what IP address to give,
|
|
0:11:15
|
unicast, multicast, any cast. We normally do unicast but
|
|
0:11:19
|
we could, if we had a properly set up network to a
|
|
0:11:22
|
multicast or if the NTP server was local
|
|
0:11:28
|
to the subnet, we can do a directed broadcast.
|
|
0:11:32
|
OK this is for SIP based phones to get their time.
|
|
0:11:35
|
Let's go ahead and just set this because we actually
|
|
0:11:37
|
will have a SIP based phone. Even though we weren't instructed to
|
|
0:11:41
|
let's go ahead and set this to our headquarter router
|
|
0:11:45
|
and the loopback interface, so 177.1.254.1 and we could refer to the
|
|
0:11:55
|
we could refer to the topology, if we need to remember what those
|
|
0:12:01
|
IP addresses were or where they were. Let's send a unicast.
|
|
0:12:06
|
OK, that's save, create a date time group.
|
|
0:12:11
|
We'll note that we already have one called CM Local.
|
|
0:12:14
|
We're not going to use that one, we were instructed to create three.
|
|
0:12:18
|
And we're we given the format for them?
|
|
0:12:21
|
We weren't given the format for the names.
|
|
0:12:22
|
We should create them as intuitive naming convention.
|
|
0:12:26
|
So the naming convention I preferred for,
|
|
0:12:31
|
going on probably 10 years now is simply,
|
|
0:12:36
|
something that's unambiguous as a prefix that is a
|
|
0:12:41
|
certain abbreviation of the type of entity that I am creating.
|
|
0:12:45
|
So for instance a media resource group would be an MRG.
|
|
0:12:50
|
OK? So daytime group, I'll call DT_CorpHQ.
|
|
0:12:56
|
We we're instructed that this is in Pacific Timezone.
|
|
0:13:02
|
If I can find it here, there it is Pacific Standard with daylight time.
|
|
0:13:09
|
Everything else looks fine because we weren't instructed to change anything.
|
|
0:13:14
|
Now we don't know yet, we will
|
|
0:13:18
|
soon enough, but we don't know yet where our
|
|
0:13:22
|
SIP phones will be in this infrastructure, but let's just go ahead and
|
|
0:13:26
|
add a selected NTP reference for every date timegroup that we create.
|
|
0:13:32
|
In that way, even though they'll all have to come back to the headquarter
|
|
0:13:36
|
loop back router or interface, really a small
|
|
0:13:41
|
packet of information, a few packets, so it won't be that big of a problem.
|
|
0:13:45
|
So add that selected NTP phone reference to every date timegroup,
|
|
0:13:51
|
for any SIP phones.
|
|
0:13:55
|
OK, add successful, we'll go ahead and copy.
|
|
0:13:58
|
It's normally the fastest way to do things
|
|
0:14:01
|
and especially if we need to re-use any information like
|
|
0:14:06
|
the date timegroup or selected phone NTP reference.
|
|
0:14:09
|
So we'll name this DT_Branch1, we we're told
|
|
0:14:15
|
I believe that this is in, that's correct, Central Standard Timezone
|
|
0:14:19
|
and to allow for daylight savings.
|
|
0:14:25
|
Here's, that's the Central America standard time, but it doesn't say
|
|
0:14:30
|
daylight savings, so here's central standard with daylight time.
|
|
0:14:35
|
OK? So that's good enough for there and finally we'll copy this again,
|
|
0:14:42
|
and replace the 1 with a 2,
|
|
0:14:45
|
DT_Branch2, we we're instructed that this one should be
|
|
0:14:49
|
Central European Standard Time with daylight savings.
|
|
0:14:56
|
OK, so let's take a scroll down, this is going to be GMT +1.
|
|
0:15:08
|
If I can find it here, here we are.
|
|
0:15:11
|
Central European Standard Time with Daylight Savings Time.
|
|
0:15:18
|
OK, now note that we weren't given the GMT offsets for this.
|
|
0:15:22
|
We were only given the naming convention.
|
|
0:15:24
|
Sometimes you might be given the GMT off or UTC offset,
|
|
0:15:29
|
sometimes you might be given the name, sometimes you might be given both.
|
|
0:15:34
|
Either way, we can always figure out what needs to be done
|
|
0:15:38
|
even if we were just told offset.
|
|
0:15:41
|
Even if we were just told a name like we are here,
|
|
0:15:44
|
but it was in IOS router. OK?
|
|
0:15:48
|
And I'm trying to set up clock timezone. Well there's no,
|
|
0:15:53
|
there's no reference in that IOS router under the clock timezone
|
|
0:15:58
|
command or what name equals what UTC or GMT offset,
|
|
0:16:04
|
negative or plus, however I have other things available.
|
|
0:16:10
|
One of them in IOS, if I don't want to leave IOS,
|
|
0:16:13
|
is I could actually set up STST or CME
|
|
0:16:18
|
and jump in there and set up the date time group there because,
|
|
0:16:22
|
actually if I walk through the wizard, it won't give me a list of them.
|
|
0:16:25
|
But then also, I have CUCM server, so I could navigate over to the webpage,
|
|
0:16:31
|
for CUCM server and find my time in that fashion.
|
|
0:16:36
|
Don't necessarily have to just remain in IOS,
|
|
0:16:38
|
even if that's where the task was pertaining to.
|
|
0:16:41
|
Use all the tools that are available to you.
|
|
0:16:44
|
OK, we were also told to change the date time group for a format
|
|
0:16:46
|
where the day comes before the month.
|
|
0:16:49
|
OK, so date time format, day-month,
|
|
0:16:54
|
and the separator, you're instructed to be a dot
|
|
0:17:00
|
to move sections of numbers. OK?
|
|
0:17:05
|
There we go, day.month.year and then not to allow an A or a P
|
|
0:17:11
|
to display after the time, A or P would be for AM or PM.
|
|
0:17:16
|
So a way to do that is to switch it to 24 hour time.
|
|
0:17:22
|
Save.
|
|
0:17:25
|
OK? So that's through that Task 1.4.
|
|
0:17:33
|
OK, Roy had the question renaming the default date and time group,
|
|
0:17:37
|
gotten the point, so in reference to CCIE lab,
|
|
0:17:40
|
let's just go back and look at that taks real quickly.
|
|
0:17:44
|
It does say to create three date time groups,
|
|
0:17:50
|
you probably would not have been.
|
|
0:17:55
|
In fact, it is specific to create versus rename but
|
|
0:17:58
|
you probably would not have any issues with that.
|
|
0:18:03
|
It's one of those things where you can always ask the proctor
|
|
0:18:05
|
if you have any discrepancies in the wordings,
|
|
0:18:08
|
you know that's a perfect type question for a proctor which is,
|
|
0:18:13
|
you can always ask the proctor if you have any discrepancy in wording,
|
|
0:18:16
|
that would be a great question, would be,
|
|
0:18:18
|
you say to create, am I just allowed to rename or anything like that.
|
|
0:18:23
|
However some questions such as that are so insignificantly
|
|
0:18:28
|
small that it would take longer to ask the question
|
|
0:18:31
|
than it would just to go ahead and by default.
|
|
0:18:37
|
Make the change you know, actually do the creation versus
|
|
0:18:40
|
down here we see another task that says modify the default region.
|
|
0:18:44
|
So something to keep in mind, some questions are so small that they're
|
|
0:18:48
|
actaully not worth asking and they become an impediment versus a benefit.
|
|
0:18:55
|
Also regarding questions in the CCIE lab,
|
|
0:18:59
|
one other note is that if you have some smaller
|
|
0:19:02
|
or less important questions or less urgent and immediate.
|
|
0:19:07
|
A good idea might be to accumulate a few sets of questions, you know maybe
|
|
0:19:12
|
three or four, five questions, probably not more than four or five at once.
|
|
0:19:16
|
It might frustrate the proctor with 20 questions all at once.
|
|
0:19:20
|
But write them down and then go ask a bulk set of you know
|
|
0:19:24
|
three to five questions, versus just going up
|
|
0:19:28
|
every two minutes with a new question.
|
|
0:19:32
|
OK, so looking at CUCM system regions and we obviosuly have a lot of
|
|
0:19:38
|
configuration to do or maybe not configuration but
|
|
0:19:41
|
reading and understanding to do, and we certainly want to talk about
|
|
0:19:45
|
the concepts of regions here as we go along after we read our task.
|
|
0:19:50
|
So we're instructed to begin with, to modify the default region
|
|
0:19:54
|
and rename it R_CorpHQ.
|
|
0:19:58
|
Configure two additional regions to be later assigned
|
|
0:20:01
|
all Branch1 and Branch2 devices respectively.
|
|
0:20:04
|
And name them intuitively, following the format
|
|
0:20:06
|
of the Corporate Headquarter region.
|
|
0:20:09
|
We're now instructed to ensure that all voice codec negotiation,
|
|
0:20:14
|
within each site, utilizes the G711 Mu-Law format
|
|
0:20:20
|
as a maximum.
|
|
0:20:23
|
OK? So one thing to keep in mind about regions,
|
|
0:20:27
|
specifying a codec does not,
|
|
0:20:31
|
ensure that that codec will be chosen.
|
|
0:20:35
|
It states simply to the CUCM server that whatever bandwidth is
|
|
0:20:43
|
assumed or is the default,
|
|
0:20:48
|
inside the CUCM server programming as a maximum rate
|
|
0:20:53
|
or default rate for that codec,
|
|
0:20:57
|
then that is to be considered a maximum bandwidth
|
|
0:21:01
|
that is allowed to be negotiated in any, in all codecs that are equal
|
|
0:21:07
|
to that bandwidth or lesser than that codec default rate bandwidth.
|
|
0:21:13
|
are allowed to be used and therefore lower rate or equal rate codec
|
|
0:21:17
|
are able to be negotiated.
|
|
0:21:20
|
OK, so for instance, if I configure the G711 Mu-Law codec,
|
|
0:21:25
|
that is a default codec rate of what? We're not including any
|
|
0:21:29
|
we're not talking about layer 2 or layer 3 or anything like that,
|
|
0:21:32
|
it's just the default codec rate.
|
|
0:21:36
|
We're gonna actually look this up inside CUCM,
|
|
0:21:38
|
in fact let's just go ahead and do that very quickly.
|
|
0:21:44
|
We go over to system region,
|
|
0:21:50
|
do a find or default region,
|
|
0:21:53
|
and now that we're on this page, let's go up to help for this page.
|
|
0:22:02
|
By the way, we can see from the left hand table of content,
|
|
0:22:05
|
is a bookmark side, once it displays,
|
|
0:22:10
|
that we are at region configuration settings under region,
|
|
0:22:15
|
under system which is a subset of the administration guide.
|
|
0:22:19
|
In fact if we scroll down, we see that we have the system guide
|
|
0:22:22
|
features and services, bulk admin, and security guide.
|
|
0:22:26
|
We've got all those right here. Now all of that documentation
|
|
0:22:29
|
is of course available online, both in regular
|
|
0:22:34
|
day to day life and the in the CCIE voice lab.
|
|
0:22:38
|
However it's also right here, so depending on
|
|
0:22:42
|
which one happens to be faster, you've got all that information.
|
|
0:22:45
|
It's the same information, the only difference is that the online,
|
|
0:22:49
|
documentation is updated obviously with the content but
|
|
0:22:54
|
probably hasn't been updated once it's published
|
|
0:22:57
|
until the newere version of CUCM comes out.
|
|
0:23:01
|
7.0.1, this is the same admin guide that you find online.
|
|
0:23:06
|
So
|
|
0:23:10
|
looking here, we see that if we scroll down
|
|
0:23:15
|
we've got default bandwidths used for call and this one,
|
|
0:23:20
|
you include IP headers with 30 millisecond data packets,
|
|
0:23:24
|
So for G711, they're assuming 80K. So any codec that uses
|
|
0:23:30
|
80K or below is able to be negotiated. What else do we see
|
|
0:23:36
|
that can use, if G711 was selected as the codec,
|
|
0:23:42
|
what other codecs could be negotiated?
|
|
0:23:49
|
OK? G722, that's correct.
|
|
0:23:53
|
G722 is equal, so that could be selected, even if it's not chosen.
|
|
0:23:59
|
OK, so if I go down here and say, I can either say G711
|
|
0:24:04
|
which is the current between default and default,
|
|
0:24:07
|
or in other words within the region.
|
|
0:24:10
|
Or I could say G722, really it makes no difference.
|
|
0:24:14
|
Because they have the same bandwidth, either are able to be negotiated.
|
|
0:24:19
|
By the way, this also states this down here,
|
|
0:24:23
|
the audio codec selection determines the bandwidth only.
|
|
0:24:28
|
The G711 and G722 codecs both result in a maximum of 64K
|
|
0:24:34
|
even though it tells you 80K, it's actually
|
|
0:24:37
|
referring a little bit more to regions, but that's OK.
|
|
0:24:39
|
Whether it's 80 or whether it's 64, that's not really the important bit.
|
|
0:24:43
|
The default codec rate of 64 is the default of
|
|
0:24:49
|
G711 and G722, but whichever we're looking at,
|
|
0:24:55
|
the idea is that, whatever bandwidth is used for that codec,
|
|
0:25:00
|
the maximum is what we're looking at here, maximum bandwidth
|
|
0:25:06
|
and so these can be used interchangeably.
|
|
0:25:12
|
OK? So that's the important bit there.
|
|
0:25:16
|
So also we can pretty much note that, because of that we could have,
|
|
0:25:22
|
we selected G711, we could have G722,
|
|
0:25:26
|
lines, we could have G723, G728 or
|
|
0:25:33
|
the ILBC, G729 or GSM. The only one that's too high
|
|
0:25:39
|
is the wide band AAC, so that codec could not be chosen.
|
|
0:25:52
|
OK.
|
|
0:25:58
|
Let's look back at our task.
|
|
0:26:06
|
We're told to ensure that all voice codec negotiation within
|
|
0:26:10
|
each site utilizes G711 as a maximum.
|
|
0:26:14
|
Do not configure any settings on any region's page
|
|
0:26:18
|
to accomplish this task. OK, that's a bit of a difficulty.
|
|
0:26:24
|
We're told to ensure that all voice product negotiations between
|
|
0:26:28
|
any site and headquarter, as well as between any site and Branch1,
|
|
0:26:33
|
utilize the G729 codec as a maximum,
|
|
0:26:36
|
again not to configure any settings on either corporate headquarter or
|
|
0:26:41
|
Branch1 regions page to accomplish this task.
|
|
0:26:45
|
Again a little bit of an interesting situation.
|
|
0:26:50
|
We're told to ensure that all voice codec negotiation between
|
|
0:26:53
|
any site and Branch2 utilize a codec
|
|
0:26:56
|
that's best suited for internet communications.
|
|
0:27:00
|
OK, so this means that we would have to have understanding
|
|
0:27:04
|
of the codec, have understanding of the possibly probably the CUCM,
|
|
0:27:11
|
SRND or Solution Reference Network Design Guide.
|
|
0:27:16
|
We'll take a look at that. We're told to ensure that the G.722
|
|
0:27:20
|
voice codec is never able to be negotiated
|
|
0:27:23
|
for the reason, not that they would need to give it to you,
|
|
0:27:27
|
but for the reason so that newer Cisco generation
|
|
0:27:30
|
3 and 4 type IP phones, G3 and G4 in the future
|
|
0:27:35
|
will not suffer a lower codec negotiation to G711,
|
|
0:27:39
|
when making a call to a G2, Gen2 or a Gen1 phone.
|
|
0:27:44
|
But we'll instead always use the lesser G711 codecs. So the idea is
|
|
0:27:49
|
many organizations that have had IP phones for a while,
|
|
0:27:53
|
and still have the older Gen1 and Gen2 phones, which is 7960s and 40s
|
|
0:27:58
|
are predominant Gen2 phones that are deployed.
|
|
0:28:01
|
And they add new phones and upgrade to newer features or CCIE versions,
|
|
0:28:07
|
but they maintain their older phone inventory deployed in the field.
|
|
0:28:12
|
When a newer phone does support the G722
|
|
0:28:16
|
codec like a, let's say a Gen3 7961 or 65 or something like that,
|
|
0:28:22
|
goes to call another Gen3 newer 61 phone,
|
|
0:28:26
|
they negotiate G722 and that sounds great.
|
|
0:28:30
|
The problem is that very same person on Gen3 7961 phone,
|
|
0:28:35
|
then goes to say, maybe they call Joe in the warehouse,
|
|
0:28:39
|
and he has an older Gen2 7960 phone,
|
|
0:28:45
|
and all of the sudden G711 is the maximum codec that can be negotiated,
|
|
0:28:49
|
because of what the endpoint 7960 supports.
|
|
0:28:53
|
And so the person, let's say in accounts
|
|
0:28:57
|
receivable that was in the newer 7961 phone,
|
|
0:29:00
|
complains that whenever they call the warehouse, it sounds terrible.
|
|
0:29:03
|
Or whenever they call shipping, it sounds terrible,
|
|
0:29:07
|
not to pick on those guys but, maybe they just don't
|
|
0:29:09
|
have as much of a priority to upgrade to new phones.
|
|
0:29:12
|
OK? So when they call some phone, it sounds terrible.
|
|
0:29:16
|
When they call other phones, it sounds amazing,
|
|
0:29:19
|
like the person is in the room, the same room with them.
|
|
0:29:23
|
So that's the idea here of why we might want to
|
|
0:29:27
|
although the lab probably wouldn't necessary give you all that information.
|
|
0:29:31
|
I did want to point out why we might want to disable G722,
|
|
0:29:35
|
in an environment that has both type 3 or 4
|
|
0:29:39
|
and older type Gen1 or Gen2 phones.
|
|
0:29:43
|
OK. In an environment that has all newer Gen3 and better phones,
|
|
0:29:47
|
we typically don't want to disable G722. In fact we want to
|
|
0:29:51
|
very much use it. OK? So we're told to make sure
|
|
0:29:56
|
it's never able to be negotiated,
|
|
0:29:58
|
but we just got them saying, that if G711
|
|
0:30:02
|
was told to be selected as a maximum, it's codec default bit rate,
|
|
0:30:08
|
64K or 80K depending on how we're looking at it,
|
|
0:30:11
|
is the same as G722. How can we ensure that it's never used?
|
|
0:30:19
|
And Rivel also noted that disable G722 once
|
|
0:30:23
|
because call recording servers didn't support it.
|
|
0:30:26
|
That's another good reason, although I would imagine that if
|
|
0:30:29
|
they didn't support it as part of, that they're Skinny, probably SIP
|
|
0:30:36
|
or CTI that they would deal with a negotiatin process and
|
|
0:30:40
|
negotiate well, but very possibly not or maybe the negotiations
|
|
0:30:45
|
already happened between two phones, so 722 has already been set-up
|
|
0:30:49
|
and then recording gets invoked and it does not degrade
|
|
0:30:53
|
the codec that's already being used between the two phones in session.
|
|
0:30:57
|
And therefore can't be negotiated and used, so that's a really good point.
|
|
0:31:05
|
OK? Also we're instructed to assign the ability
|
|
0:31:09
|
between any site and Corporate Headquarter, as well as
|
|
0:31:13
|
between any site and Branch1, to have a maximum
|
|
0:31:16
|
video channel based call negotiated equal to the speed of 6 bonded
|
|
0:31:22
|
ISDN B channels. Now why are we referring to ISDN?
|
|
0:31:28
|
Really it has nothing to do with ISDN, well we're just bringing up
|
|
0:31:32
|
trying to learn information and knowledge
|
|
0:31:37
|
from you to, as to, do you know what is speed
|
|
0:31:41
|
of an ISDN B channel is and if so multiply that times six.
|
|
0:31:47
|
And then use that as the Corporate Headquarter and Branch1 speed
|
|
0:31:53
|
for video, maximum speed or lower rated speed can be negotiated.
|
|
0:31:59
|
OK, then we're told to assign the ability between any site and Branch2,
|
|
0:32:03
|
to have a maximum video channel based call negotiated equal
|
|
0:32:07
|
equal to the speed of 18 bonded ISDN B channels.
|
|
0:32:11
|
OK? Maybe because they're over the internet and we
|
|
0:32:16
|
assumed that they have more bandwidth available and we just don't really care.
|
|
0:32:21
|
They use more bandwidth. OK?
|
|
0:32:26
|
So let's first go modify the default region,
|
|
0:32:28
|
rename it and create two additional regions.
|
|
0:32:32
|
We we're told to call it R_CorpHQ
|
|
0:32:38
|
We'll go ahead and save that.
|
|
0:32:42
|
And we're told, I did select G722 there
|
|
0:32:46
|
I was told not to change anything which was by default.
|
|
0:32:55
|
By the default, it will set a G711.
|
|
0:32:58
|
So ensure that all voice codec negotiations within each site utilize
|
|
0:33:02
|
G711 is a maximum, do not configure any site on any region page.
|
|
0:33:06
|
OK, well I only configured this just because I had accidentally bumped it
|
|
0:33:12
|
from the beginning, but this is what the page looked like when we got here.
|
|
0:33:15
|
which is keep current setting. Alright?
|
|
0:33:19
|
So
|
|
0:33:21
|
as far as codec, we've met that requirement.
|
|
0:33:26
|
In terms of Corporate Headquarters between itself and any site,
|
|
0:33:32
|
have a maximum video channel based call equal to the speed of six bonded
|
|
0:33:37
|
ISDN B channels.
|
|
0:33:39
|
So and actually this is a matrix, so we should probably
|
|
0:33:42
|
say a region relationship between Corporate Headquarters
|
|
0:33:44
|
and Branch1, let's say for instance.
|
|
0:33:48
|
We have to define each region individually so
|
|
0:33:52
|
between any site and Corporate Headquarters, but we already know
|
|
0:33:56
|
any site and Branch2 is going to have a different speed,
|
|
0:33:58
|
so this is going to be within Corporate Headquarters and
|
|
0:34:02
|
Branch1 Corporate Headquarters.
|
|
0:34:05
|
So what is the default codec rate of an ISDN B channel?
|
|
0:34:16
|
64K, so 64 times six is, hey what do you know, 384.
|
|
0:34:21
|
It's already set, we're good to go there.
|
|
0:34:27
|
So that's within, that's between Corporate Headquarter
|
|
0:34:32
|
and Corporate Headquarter or in other words within the site.
|
|
0:34:35
|
It's going to be G711 and 384.
|
|
0:34:39
|
And so we now need to add some more sites before we can
|
|
0:34:42
|
make any sort of relationships or matrix.
|
|
0:34:47
|
Let's add a new site and call it Region_Branch1
|
|
0:34:55
|
OK? And now note that were not told,
|
|
0:35:00
|
we were told not to, let's go back here.
|
|
0:35:05
|
In terms of voice codec, within each site fo G711,
|
|
0:35:09
|
do not configure any settings on any region pages to accomplish
|
|
0:35:12
|
this task, this is just for voice codec.
|
|
0:35:15
|
I'm not talking about per video codec that were given
|
|
0:35:18
|
separate information as to how much bandwidth
|
|
0:35:22
|
and we weren't told to not configure anything, so we can.
|
|
0:35:30
|
And then also between any site in Corporate Headquarters,
|
|
0:35:33
|
as well as Branch1 utilize G729.
|
|
0:35:38
|
OK? So for these
|
|
0:35:42
|
we have to keep the current setting, can't do anything.
|
|
0:35:46
|
That's were instructed to do. Alright, somehow we have to accomplish
|
|
0:35:51
|
G711 and G729 within and between each site.
|
|
0:35:56
|
Alright, we'll take a look at that. For video, we weren't told we
|
|
0:35:59
|
could do nothing, so we can change it to
|
|
0:36:03
|
what we were instructed, which is 384.
|
|
0:36:06
|
We'll come back and look at this column in a moment.
|
|
0:36:12
|
Now, wait a minute, if we said just keep current setting,
|
|
0:36:16
|
how did it take G711? How is that possible?
|
|
0:36:22
|
And if I wouldn't have needed to do any video bandwidth,
|
|
0:36:26
|
what's interesting is that, now actually this is
|
|
0:36:30
|
looks like a bit of a bug, because this looks like
|
|
0:36:32
|
between Branch1 and Corporate Headquarter.
|
|
0:36:34
|
G711 was automatically selected, so that's a little bit of a problem,
|
|
0:36:40
|
maybe,let me delete and just do one at a time,
|
|
0:36:43
|
see if that fixes it.
|
|
0:36:46
|
Fine, we should still have Corporate Headquarters, we do.
|
|
0:36:51
|
Just create Region_Branch1.
|
|
0:36:57
|
OK, and let's just say between Branch, use 384.
|
|
0:37:12
|
It chooses G711. OK, so here is the bug that I wanted to point out.
|
|
0:37:16
|
It shows itself up here as well as being the default so
|
|
0:37:22
|
what we were getting at with the task of do not
|
|
0:37:25
|
configure any settings on regions to accpmplish this task is
|
|
0:37:31
|
we need to go into service parameters and we'll be talking
|
|
0:37:33
|
about service parameters in a moment.
|
|
0:37:36
|
But let's just choose the pub to begin with, this will be a cluster wide,
|
|
0:37:40
|
so it doesn't matter which we choose pub or sub,
|
|
0:37:42
|
and the Cisco Call Manager service,
|
|
0:37:53
|
loading, going to do a search.
|
|
0:37:57
|
so Ctrl F for codec.
|
|
0:38:07
|
Scroll, let me try that again. OK.
|
|
0:38:12
|
So first of all, codec G.722 enabled. Wait a minute,
|
|
0:38:19
|
I do remember seeing a task,
|
|
0:38:21
|
ensure that this codec is never able to be negotiated.
|
|
0:38:25
|
Alright, so we already found the ability
|
|
0:38:32
|
and by the way, I believe it was variable that mentioned.
|
|
0:38:37
|
Here is a way that we can
|
|
0:38:43
|
bounce back on the right place. Enable it for all devices
|
|
0:38:48
|
except for recording enabled devices, however
|
|
0:38:52
|
one thing to keep in mind here, or we can switch it to disable
|
|
0:38:54
|
because we're going to do here because of our instruction.
|
|
0:38:58
|
However one thing to keep in mind with that is that,
|
|
0:39:03
|
if it says enable for all devices except recording enabled devices,
|
|
0:39:06
|
it's assuming that you're using the CUCM,
|
|
0:39:09
|
recording infrastructure, which is device, device settings,
|
|
0:39:13
|
recording profile and some systems used that. For instance nice
|
|
0:39:19
|
uses the CUCM recording API as it were,
|
|
0:39:25
|
It's built in to Call Manager but many devices are simply
|
|
0:39:30
|
set up as CTI enabled, yes. And yours was a span based recording.
|
|
0:39:35
|
So yes, if CUCM doesn't recognize it as a recording
|
|
0:39:39
|
device under recording profile, then that would not,
|
|
0:39:43
|
take effect. So span based or CTI,
|
|
0:39:47
|
exactly that will not take effect.
|
|
0:39:52
|
Or it would not disable it for those devices because it doesn't recognize.
|
|
0:39:57
|
So disable, so we've met that one, great.
|
|
0:40:01
|
Slowly scroll down here, again these are clusterwide parameters
|
|
0:40:05
|
for system location and region.
|
|
0:40:08
|
OK? So here's what I wanted to point out,
|
|
0:40:10
|
the inner region audio codec default, intra-region and inter-region,
|
|
0:40:17
|
then also the viedo call bandwidth default.
|
|
0:40:20
|
Note the defaults are G711/G722 because
|
|
0:40:25
|
the same bit rate or intra or within a region.
|
|
0:40:30
|
And inter or between regions for the audio codec, the default is G729.
|
|
0:40:36
|
We go back up here to our other tab. Basically, what this is saying,
|
|
0:40:40
|
let me just go ahead and do system default,
|
|
0:40:47
|
There we go, this is what we need to accomplish.
|
|
0:40:50
|
Screen didn't refresh properly, let me go back out.
|
|
0:40:57
|
Go back and delete this Branch1,
|
|
0:41:01
|
and we'll know recreate it with what we need to use.
|
|
0:41:04
|
So we've got out Corporate Headquarters, we're going to add our new
|
|
0:41:08
|
R_Branch1
|
|
0:41:12
|
Page wasn't cooperating with me.
|
|
0:41:15
|
And I'll simply, for both of these, say 384 but instead
|
|
0:41:20
|
of saying keep current setting, I'll say use system default.
|
|
0:41:27
|
OK? So now, the audio codecs
|
|
0:41:31
|
and the truth is, I actually didn't even need to do anything
|
|
0:41:35
|
for video call bandwidth. What I could have done,
|
|
0:41:38
|
I'll do this one last time, actually let me copy my name,
|
|
0:41:41
|
so I don't have to type it out again.
|
|
0:41:45
|
What I could have done,
|
|
0:41:50
|
is nothing.
|
|
0:41:53
|
Because note, regions not displayed
|
|
0:41:57
|
use, I'll bring up my marker here, regions not displayed,
|
|
0:42:03
|
use the system default for audio and the system default for video,
|
|
0:42:08
|
and the system default for link loss type,
|
|
0:42:11
|
which we're gonna talk about in a moment.
|
|
0:42:13
|
OK, so again system default,
|
|
0:42:20
|
Cluster wide parameters, locations and regions,
|
|
0:42:26
|
intra-region, within is G711
|
|
0:42:32
|
inter between is G729
|
|
0:42:35
|
and within and between,
|
|
0:42:39
|
for video is 384 and the default link loss type is low loss,
|
|
0:42:47
|
as opposed to lossy, low loss meaning very little or no loss.
|
|
0:42:59
|
So using the system default, for the regions not displayed,
|
|
0:43:03
|
will be just fine for what I need.
|
|
0:43:12
|
So I actually don't have to do anything there, what I will say is save,
|
|
0:43:17
|
and I will add a new one and I'll call this one Region_Branch2
|
|
0:43:24
|
and this I will need to
|
|
0:43:30
|
modify, not necessariyly within, but between
|
|
0:43:38
|
the audio codec, now note
|
|
0:43:46
|
all voice codec negotiations between any site and Branch2,
|
|
0:43:49
|
utilize a codec best suited for the internet. I wasn't instructed
|
|
0:43:53
|
not to configure settings on these pages.
|
|
0:43:59
|
So I can go ahead and configure settings and I can say that
|
|
0:44:05
|
I will use the audio codec of, now
|
|
0:44:10
|
best suited for the internet. Let's take a look at help for this page.
|
|
0:44:23
|
Let's just search for the word internet.
|
|
0:44:27
|
The internet low bitrate codec.
|
|
0:44:35
|
ILBC enables graceful speech quality degradation in the case of loss
|
|
0:44:41
|
frames, being a keyword here,
|
|
0:44:44
|
and is suitable for real time communications over the internet.
|
|
0:44:49
|
OK, so the ILBC, however note the audio codec to be chosen
|
|
0:44:54
|
B728 for ILBC.
|
|
0:44:58
|
Well how do we know which one will be chosen?
|
|
0:45:01
|
They're actually not the same codec rate.
|
|
0:45:05
|
We note.
|
|
0:45:08
|
How do we know which one will be chosen?
|
|
0:45:11
|
So we'll choose G728 ILBC,
|
|
0:45:19
|
Press to that.
|
|
0:45:21
|
But how do we know what else will be chosen or
|
|
0:45:23
|
which one of those two will be chosen since they're not the same rate?
|
|
0:45:27
|
It's based on the link loss type,
|
|
0:45:31
|
which in this case, we need to be lossy.
|
|
0:45:35
|
If we say low loss D728 will try to be negotiated.
|
|
0:45:41
|
If we say lossy, then ILBC will attempt to be negotiated,
|
|
0:45:46
|
if both devices support it, if they don't, then I'll go back to G728.
|
|
0:45:54
|
OK?
|
|
0:45:57
|
So we'll say save there. We didn't do the video bandwidth yet.
|
|
0:46:01
|
So because the link type is lossy and G728/ILBC
|
|
0:46:06
|
ILBC will attempt to be negotiated. The video call bandwidth,
|
|
0:46:10
|
we still have the modify that, so we'll select those again.
|
|
0:46:14
|
And let's choose the bandwidth of, let's go back and take a look at
|
|
0:46:18
|
what we were told. Assign the ability between any site and Branch2
|
|
0:46:23
|
to have a maximum video channel call or base call negotiator
|
|
0:46:27
|
equal to the speed of 18. If we're worried about loss, why are we
|
|
0:46:32
|
assigning more channels? Well just because we can.
|
|
0:46:35
|
So the internet has more bandwidth, I will link to the internet,
|
|
0:46:38
|
their link or DSL or cable modem provider has more bandwidth,
|
|
0:46:42
|
really just because, in the case of a task
|
|
0:46:45
|
being assigned to us on a test, it doesn't really have to make sense.
|
|
0:46:49
|
One of the things that you definitely want to get through your,
|
|
0:46:52
|
definitely let sink in and believe it and follow it.
|
|
0:46:57
|
I should say accept it whether you understand why or not
|
|
0:47:03
|
as is pertains to the CCIE voice lab or any CCIE lab,
|
|
0:47:09
|
not necessarily best practice, or something
|
|
0:47:12
|
you would do in the real world. In fact, there are going to be quite
|
|
0:47:15
|
a few many things that are not going to be best pratice or,
|
|
0:47:21
|
this is not the CCDE or design exam and it's not meant to be.
|
|
0:47:28
|
This is based on, if that's the reason you're watching.
|
|
0:47:32
|
CCIE is about inter network expert,
|
|
0:47:36
|
inter-networking and so how can we make technologies work,
|
|
0:47:40
|
how we can use the tools in our tool kit
|
|
0:47:44
|
to make whatever we're being given as a task work for us.
|
|
0:47:47
|
They don't necessarily have to make sense.
|
|
0:47:49
|
They'll be logical, they just might not be, or I should say they'll be
|
|
0:47:54
|
syntactically logical or be able to be configured.
|
|
0:47:57
|
They just might not necessarily be
|
|
0:48:01
|
logical in the sense of why we want to do something.
|
|
0:48:04
|
So 18 channels, alright if we already mentioned that
|
|
0:48:08
|
64 was the base for 1, times 18,
|
|
0:48:13
|
we're going to have 1152 as our bandwidht.
|
|
0:48:19
|
And we'll go ahead and say save.
|
|
0:48:22
|
Now maybe, because we weren't given anything in regards to
|
|
0:48:28
|
within, we did say that all product negotiation between
|
|
0:48:32
|
any site and Branch2. We didn't say anything about within,
|
|
0:48:36
|
but we did say any site and Branch2.
|
|
0:48:40
|
So this probably means itself as well, because if you think about it,
|
|
0:48:44
|
if we have Branch2 users as internet based users,
|
|
0:48:52
|
then if we have internet based users as the Branch2 region,
|
|
0:48:58
|
they're probably across the internet from one another as well.
|
|
0:49:03
|
They're probably not all sitting in a single office that's connected
|
|
0:49:07
|
through the internet, but then again they very well may be.
|
|
0:49:10
|
So it's completely up to the,
|
|
0:49:15
|
possibilty in terms you know the wording, the proctor may
|
|
0:49:20
|
help clarify the wording if you have any confusion, they probably would.
|
|
0:49:24
|
Again given the assumption that you would ask the proctor properly,
|
|
0:49:30
|
give them a lot of information, say listen I understand
|
|
0:49:33
|
what this is asking and kind of explain a little bit of what it's asking,
|
|
0:49:36
|
but then say, the only thing I'm confused on is this between word,
|
|
0:49:40
|
between any site in Branch2, you don't talk about within
|
|
0:49:43
|
the Branch2 site and in this case, the proctor would say,
|
|
0:49:48
|
well because we don't talk about that, then between any site
|
|
0:49:51
|
and Branch2 also is between Branch2 and Branch2.
|
|
0:49:56
|
OK. So all of these users are desperate users
|
|
0:49:59
|
and they're just using one region, so we're actually gonna say
|
|
0:50:02
|
between itself, it's gonna be the same thing and we'll add that.
|
|
0:50:07
|
So now we have the matrix complete,
|
|
0:50:11
|
but let's just go ahead and go back and check each one
|
|
0:50:16
|
and I'll just hit alt to open each one,
|
|
0:50:20
|
so here we've got headquarters, we don't define Branch1 yet,
|
|
0:50:24
|
but remember regions not displayed, use system default which is
|
|
0:50:29
|
G711 within, so from Corporate Headquarters to Corporate Headquarters
|
|
0:50:34
|
although that was already the default and G729 between,
|
|
0:50:41
|
and then Branch2, we had explicitly configured as instructed.
|
|
0:50:47
|
And then here Branch2, this is the one we just got done explicitly configuring
|
|
0:50:52
|
and then Branch1 only talks about between itself and Branch2
|
|
0:50:57
|
because within itself is going to be G711,
|
|
0:51:01
|
and between itself and headquarters is going to be
|
|
0:51:06
|
G729 as we just got done mentioning for the service parameters.
|
|
0:51:16
|
OK?
|
|
0:51:18
|
So we of course have to, actually let me go back down, I think I
|
|
0:51:24
|
accidentally left that.
|
|
0:51:28
|
Low loss, that was the default, that's fine.
|
|
0:51:33
|
I haven't changed it, just wanted to make sure I hadn't change it.
|
|
0:51:35
|
G722, I had disabled, good.
|
|
0:51:39
|
All the others are the default, so now I need to save it.
|
|
0:51:45
|
Go to help page and we'll go ahead and move on.
|
|
0:51:51
|
Task is in the service parameter page, good. Back to update successfully.
|
|
0:52:01
|
So now we've taking care of the regions, everyone understands that region define,
|
|
0:52:07
|
the maximum bandwidth per call. I want to make that very clear distinction.
|
|
0:52:13
|
Regions define the maximum bandwidth per call.
|
|
0:52:17
|
OK? The maximum bandwidth for aggregate calls,
|
|
0:52:22
|
is at the locations or call admission control.
|
|
0:52:25
|
Agrregate being all of the calls, so how do we make sure
|
|
0:52:31
|
that let's say we want to allow, let's say
|
|
0:52:37
|
then bring up a calculator and we'll take a look in a moment
|
|
0:52:40
|
at locations but just for the moment time being, this interesting.
|
|
0:52:47
|
And then you respond.
|
|
0:52:49
|
For the time being we'll just go ahead and mention that 24K
|
|
0:52:52
|
as we saw on the regions page, 24K even though the default
|
|
0:52:57
|
codec bitrate for G729 is 16K.
|
|
0:53:06
|
8K, I'm not sure, I'm thinking of gatekeeper based
|
|
0:53:10
|
CAC, but the 8K is the default bitrate,
|
|
0:53:15
|
per call for G729 or G729 locations as we'll see in a moment.
|
|
0:53:24
|
I'll just go ahead and bring it up.
|
|
0:53:29
|
Click on the default location and go ahead and click help for this page.
|
|
0:53:38
|
Here we see that for the purposes of location bandwidth
|
|
0:53:40
|
calculations only and when we talked about or will talk about QOS,
|
|
0:53:46
|
depending on you're watching this later and you've already watched that module.
|
|
0:53:52
|
In terms of QOS, we will make the very clear distinction
|
|
0:53:57
|
that what we are configuring regarding bandwidth,
|
|
0:54:02
|
for aggregate calls or per call for the purpose of aggregate calls
|
|
0:54:07
|
and call admission control, whether we're talking about gatekeeper,
|
|
0:54:12
|
whether we're talking about standard locations based CAC,
|
|
0:54:16
|
or whether we're talking about RSVP call admission control.
|
|
0:54:21
|
The amount of bandwidth that we decide per call
|
|
0:54:25
|
has absolutely nothing to do, it's completely other than
|
|
0:54:31
|
completely dissociated with the amount of actual bandwidth,
|
|
0:54:36
|
that any given G729 call will actually use
|
|
0:54:43
|
over a given medium and the reason is, the given medium
|
|
0:54:48
|
is going to be what defined the amount of bandwidth based on
|
|
0:54:50
|
layer 2 header, going to talk about that or again if you've already
|
|
0:54:54
|
watched it talk about the in QOS module.
|
|
0:54:58
|
But G729 uses 24 kilobits per second
|
|
0:55:08
|
for a G729 call per call for location based CAC only.
|
|
0:55:14
|
But in terms of quality service and in terms of reserving
|
|
0:55:18
|
per G729 call for a priority queue, the amount of actual
|
|
0:55:24
|
bandwidth that we will calculate has nothing to do with that.
|
|
0:55:27
|
So then why, not only in the blueprint,
|
|
0:55:32
|
or the CCIE voice, in fact let me just open that real quickly,
|
|
0:55:38
|
illustrate the point.
|
|
0:55:42
|
Why in the blueprint CCIE voice, under section 10
|
|
0:55:50
|
implement and troubleshoot QOS and CAC, Call Admission Control.
|
|
0:55:54
|
Why did they put traffic classification qeueing mechanisms,
|
|
0:55:59
|
and RSVP and Call Admission Control all in one section.
|
|
0:56:04
|
If they really, if the bandwidths don't have to do anything with each other,
|
|
0:56:08
|
Well because there is something that's relevant to each other.
|
|
0:56:16
|
OK? And that is
|
|
0:56:21
|
going here, what's relevant is the type of call,
|
|
0:56:27
|
and the number of calls, but if we were to say five calls,
|
|
0:56:32
|
at G729 or we would you know, kind of sort of say,
|
|
0:56:41
|
for CAC, that's going to equal five times 24K.
|
|
0:56:48
|
OK so we will use a calculator, say 24K times five,
|
|
0:56:54
|
we have 120K of bandwidth.
|
|
0:57:02
|
But in terms of quality of service, priority queue,
|
|
0:57:10
|
what's that going to equal? Well we've already or will look
|
|
0:57:15
|
at that quality of service calculations,
|
|
0:57:20
|
again depending on if you've already watched it, if not on Friday,
|
|
0:57:23
|
for those that are live and the only information is again
|
|
0:57:29
|
type of call and number of calls, that's relevant between the two.
|
|
0:57:33
|
OK, this 24K was only specific, in fact
|
|
0:57:37
|
probably be better if I use another caller.
|
|
0:57:47
|
24K here is only specific to CAC and the other number,
|
|
0:57:53
|
that we don't see, I just don't have another place to write it,
|
|
0:57:56
|
question, question, question, this other number,
|
|
0:58:09
|
this number here is going to be multiplied times five,
|
|
0:58:15
|
based on the codec to determine what the actual
|
|
0:58:19
|
priority queue value will be. OK? So the type of call
|
|
0:58:23
|
again and the number of calls, that's what's relevant to both
|
|
0:58:27
|
CAC and quality of service, this bandwidth here 24K,
|
|
0:58:31
|
that's only used for call admission control if we're looking at location.
|
|
0:58:36
|
We're also going to see that depending on what type of
|
|
0:58:41
|
call admission control, the bandwidth may actually be a little bit different.
|
|
0:58:46
|
OK? This is based on what it is we're using in terms of like RSDP
|
|
0:58:52
|
or standard location based CAC.
|
|
0:58:58
|
OK, so again, location based CAC just to summarize
|
|
0:59:03
|
once again locations is the aggregate bandwidth,
|
|
0:59:08
|
for all calls based on the codec
|
|
0:59:13
|
and regions is the per call bandwidth.
|
|
0:59:22
|
The per call bandwidth to determine which codec can be negotiated.
|
|
0:59:28
|
So also again if we did have 24K for a G729 times five calls, 120K.
|
|
0:59:37
|
How can we make sure that each call will only be 24K?
|
|
0:59:42
|
Well, we actually, the truth of the matter is we can't, we cannot
|
|
0:59:47
|
ensure that each call will be only 24K, what we can do,
|
|
0:59:53
|
is ensure that each call or what we cannot do
|
|
0:59:56
|
is ensure that each call will be G729.
|
|
1:00:00
|
We can ensure that each call will be either G729 or a lesser codec.
|
|
1:00:07
|
A lesser bandwidth, but we can't stop lower bandwidth calls from taking up
|
|
1:00:12
|
the overall aggregate bandwidth based on call admission control.
|
|
1:00:16
|
But we can ensure that they are at least a maximum of, for instance G729,
|
|
1:00:25
|
8K is the default, bitrate but then obviously depending on layer 2 headers.
|
|
1:00:36
|
OK, so I hope that makes sense. Does anyone have any questions?
|
|
1:00:40
|
This will be a great place for any questions.
|
|
1:00:43
|
Or confusion relating to her call maximum bandwidth as defining regions
|
|
1:00:50
|
or aggregate calls within or between sites doing the location based CAC.
|
|
1:01:00
|
OK? So we've taken care of the regions,
|
|
1:01:03
|
next we are on to locations which we've already began talking about.
|
|
1:01:07
|
The task is explore the default settings of hub on location but
|
|
1:01:11
|
do not modify anything. This location will be used for the
|
|
1:01:13
|
Corporate Headquarter site. We'll talk about why.
|
|
1:01:17
|
We're also told to create two additional locations to be used later,
|
|
1:01:21
|
Assigned to all Branch1 and Branch2 devices respectively.
|
|
1:01:25
|
Name them intuitively, following the format L_Branch1 and L_Branch2.
|
|
1:01:31
|
Allow for a maximum total of G725 calls,
|
|
1:01:35
|
in the Corporate Headquarter which is Hub_None default
|
|
1:01:40
|
and Branch1 sites and allow for a maximum total of three ILBC calls
|
|
1:01:46
|
between the Corporate Headquarter Hub_None and Branch1,
|
|
1:01:49
|
actually this was meant to say Branch2, small type error there.
|
|
1:01:55
|
OK? So
|
|
1:01:58
|
gonna go to location nxt and we find the Hub_None
|
|
1:02:03
|
and the audio and video bandwidth is unlimited.
|
|
1:02:07
|
OK? Now by default within a location is typically unlimited
|
|
1:02:16
|
by default. So for video we could modify this
|
|
1:02:21
|
if we wanted to ensure that there were, we were already instructed
|
|
1:02:26
|
to make sure that six ISDN B channels were used,
|
|
1:02:30
|
in terms of region, that's per call. OK? That's per video call.
|
|
1:02:34
|
But that doesn't define the amount of video calls, however here
|
|
1:02:38
|
we weren't given any instructions regarding maximum number of video calls.
|
|
1:02:43
|
Now I realized that this would allow between locations
|
|
1:02:47
|
between geographical sites that unlimited for video call.
|
|
1:02:53
|
Virtually some, but virtually noone, technically noone has unlimited bandwidth.
|
|
1:02:59
|
Unless you happen to own all of the, be a manufaturer of the equipment,
|
|
1:03:03
|
and own all the fiber in the world and you can just keep upgrading.
|
|
1:03:06
|
Other than that, nobody has unlimited bandwidth.
|
|
1:03:10
|
So although this doesn't make sense, we wouldn't in real life leave
|
|
1:03:14
|
the video bandwidth between locations set to unlimited.
|
|
1:03:18
|
Here we're going to just because we weren't given any other instruction.
|
|
1:03:23
|
OK? In terms of the CCIE lab, it's about following instructions.
|
|
1:03:27
|
So we're also instructed to do nothing with Hub_None, use it for headquarters.
|
|
1:03:34
|
OK? So we will add a new, follow the naming convention L_Branch1
|
|
1:03:43
|
as we we're instructed, the audio bandwidth, we were told to
|
|
1:03:48
|
have, now we we're told in between,
|
|
1:03:55
|
Corporate Headquarter and Branch1 sites, how do we really keep it
|
|
1:03:59
|
just between the Corporate Headquarter and Branch1 sites?
|
|
1:04:04
|
We don't, if we, I'll just get to that question in just a monent, if we
|
|
1:04:12
|
if we recall from the web user interface and command line guide,
|
|
1:04:15
|
we looked at performance monitor statistics,
|
|
1:04:18
|
anytime we make a call between two sites, the calling and called
|
|
1:04:23
|
or the originating and terminating sites,
|
|
1:04:26
|
are going to subtract or degraded bandwidthfrom both sites.
|
|
1:04:34
|
Regions, we do have a matresy between sites,
|
|
1:04:40
|
one specific site and other site. Locations however
|
|
1:04:44
|
we do not, we simply specify the maximum bandwidth for that site,
|
|
1:04:50
|
and so although we were instructed between Corporate Headquarters
|
|
1:04:52
|
and Branch1, the best we can do is just configure Branch1.
|
|
1:04:56
|
So we can configure this to 5, which we've already done the Math,
|
|
1:05:01
|
five times 24K, since we had already looked at helped for this page,
|
|
1:05:05
|
to see the 24K per G729 call is what's assumed,
|
|
1:05:09
|
and we have the value of a 120K.
|
|
1:05:15
|
Now videos automatically set to 384. We can leave that
|
|
1:05:21
|
or we can change it to unlimited or not, obviously wouldn't allow any
|
|
1:05:27
|
to violate our previous, but we'll just leave it at the default.
|
|
1:05:36
|
OK? So there's our setting.
|
|
1:05:39
|
Now here is modified settings to other locations
|
|
1:05:44
|
we do see something regarding,
|
|
1:05:54
|
we do see something regarding
|
|
1:05:57
|
settings to other locations but this deals with RSVP.
|
|
1:06:01
|
OK? And again depending on if you're watching recorded,
|
|
1:06:04
|
we've already look at or if you are not, you're here live, then you are
|
|
1:06:09
|
we're going to look at RSVP very specifically
|
|
1:06:12
|
on Friday. So we're not gonna talk about that right now
|
|
1:06:15
|
because we could spend a long time just on the subject of RSVP
|
|
1:06:20
|
and location based CAC. We will cover that on the QOS CAC.
|
|
1:06:27
|
But other than that, we have a 120K.
|
|
1:06:30
|
Let's go back and if there were ready devices, I would have clicked on
|
|
1:06:34
|
resync bandwidht, so the question was asked, what does
|
|
1:06:38
|
resync bandwidth do? I beieve that's what you were asking Yesar?
|
|
1:06:43
|
The resync bandwidth button, if we already have
|
|
1:06:48
|
devices that are using these locations which we haven't got into yet
|
|
1:06:52
|
then those devices may already be inside calls,
|
|
1:06:59
|
the system, there's really no reset
|
|
1:07:02
|
or restart as there are for many other entities in CUCM.
|
|
1:07:06
|
There's really no reset or restart for locations.
|
|
1:07:09
|
Instead it's a resync bandwidth, it's basically resyncing it with the CUCM
|
|
1:07:13
|
or call manager process in terms of, if we made a change,
|
|
1:07:18
|
we just add a bandwidth with five calls going on, not necessarily.
|
|
1:07:25
|
If we were and or even if there weren't any live calls
|
|
1:07:30
|
and we do change the bandwidth, we double it to 240 or something.
|
|
1:07:33
|
Then we need to say resync bandwidth unless we want to go in
|
|
1:07:37
|
and restart every device in the system which is just not necessary.
|
|
1:07:41
|
But just resyncs the set bandwidth, it sort of like saying
|
|
1:07:48
|
Save is like committing it to disk and then
|
|
1:07:53
|
resync is sort of like is committing it to running memory in terms of who is
|
|
1:08:02
|
what is actually taking effect at this moment. So let's add a new
|
|
1:08:08
|
in location_Branch2.
|
|
1:08:13
|
And how much bandwidth were we instructed to give?
|
|
1:08:17
|
OK, a maximum of three ILBC calls. Alright? So let's look at
|
|
1:08:23
|
if we don't remember, help for this page, location configuration,
|
|
1:08:28
|
now we don't see ILBC as a codec here, But we do so G728.
|
|
1:08:37
|
OK? So G728 is a higher codec than ILBC and remember that
|
|
1:08:43
|
G728 or ILBC could be negotiated based on the lossy type
|
|
1:08:51
|
link loss type that we set and based on the regions
|
|
1:09:00
|
for that partcular site, so for Branch2 we use G728/ILBC.
|
|
1:09:09
|
So 16K is the multiplier that we will use,
|
|
1:09:13
|
so we'll just bring up our handy calculator for everyone to see,
|
|
1:09:16
|
16 times 3 would be 48K.
|
|
1:09:20
|
Now note that that's also the same as to G729 calls.
|
|
1:09:23
|
Alright? So how do we make sure G729
|
|
1:09:26
|
calls are not going to go through?
|
|
1:09:28
|
Because G729 calls, and I'll open this on a new window,
|
|
1:09:35
|
G729 calls are a higher bitrate value,
|
|
1:09:42
|
than G728 or ILBC. OK? Once 16,
|
|
1:09:48
|
so how did I go to this website, is that what you're asking Joe?
|
|
1:09:54
|
OK, yes this is just a help page, so I'll go ahead and bring it up
|
|
1:09:57
|
again, help for this page, this is the call manager administration guide.
|
|
1:10:04
|
Let me scroll down, G728 uses, now this says
|
|
1:10:10
|
26K or G728. Right? But this is bandwidth
|
|
1:10:16
|
including the IP headers, 30 millisecond data pack 24K for ILBC.
|
|
1:10:22
|
This is as it relates to regions so
|
|
1:10:27
|
region we need to know what codec we're using, G728 being the higher
|
|
1:10:32
|
and then for locations we do help for this page
|
|
1:10:34
|
and according to the locations page,
|
|
1:10:39
|
this says that G728 is 16K.
|
|
1:10:43
|
OK? So again it's not that important that we care about why the discrepancy,
|
|
1:10:50
|
that's not the important piece at this monent.
|
|
1:10:52
|
The important piece is, what do I configure for locations
|
|
1:10:57
|
if I want a multiplier of G728 or ILBC?
|
|
1:11:03
|
I need to use whatever help for this page,
|
|
1:11:05
|
what call manager considers the G728 call to be
|
|
1:11:09
|
as it relates to locations which is 16K,
|
|
1:11:13
|
so that's my multiplier times three for 48K.
|
|
1:11:18
|
Not including all over head Joe, it's including some.
|
|
1:11:21
|
And so we just mentioned that we will talk about
|
|
1:11:24
|
all the layer 2 over head as well as layer 3
|
|
1:11:29
|
headers, packets per second, sampling rates and everything, QOS module.
|
|
1:11:40
|
OK? Notice I mentioned, if you're browser does not
|
|
1:11:48
|
kind of see the sandwiched the save button and the location or whatever
|
|
1:11:52
|
you're on, sandwiched and we don't see any information regarding
|
|
1:12:00
|
update successful, we need to make sure that we don't
|
|
1:12:02
|
run into a browser issue, add successful, there we go, save again
|
|
1:12:06
|
and everything is good. So Hub_None is still set to unlimited.
|
|
1:12:09
|
That's OK because if we think about it we've got
|
|
1:12:15
|
let's say our hub site, let's just use a circle as router
|
|
1:12:21
|
indicating the hub site and let's say as in our setting,
|
|
1:12:27
|
we've got out Branch1 site and our Branch2 site,
|
|
1:12:35
|
and if the hub has unlimited bandwidth,
|
|
1:12:39
|
dead spot on the screen.
|
|
1:12:45
|
Unlimited bandwidth and Branch1 only has a 120K,
|
|
1:12:54
|
for audio and Branch2 has 48K,
|
|
1:12:58
|
for audio with a maximum, this is for locations.
|
|
1:13:08
|
locations
|
|
1:13:13
|
Locations over regions
|
|
1:13:18
|
and the region specify for Branch1 G729,
|
|
1:13:26
|
and so 24K per call or equal to five G729 calls.
|
|
1:13:40
|
OK? So 48K over here over the region specifying G728
|
|
1:13:50
|
which as for locations, that's considered to be 16K
|
|
1:13:57
|
so 48 over 60 is gonna give us the equal of,
|
|
1:14:00
|
not 5, I was looking at above of, of 3
|
|
1:14:06
|
G.728 or as what we are going to hopefully negotiate
|
|
1:14:11
|
because of link type ILBC, Internet Low Bitrate Codec.
|
|
1:14:17
|
OK? So headquarters has unlimited, is that a problem?
|
|
1:14:23
|
It's really not a problem because if a call comes from here,
|
|
1:14:29
|
from Branch1 over the headquarters,
|
|
1:14:33
|
bandwidth will be degraded from both unlimited
|
|
1:14:36
|
which still equals unlimited and from a 120K so minus 24K,
|
|
1:14:44
|
that might be kind of hard to see because of the color.
|
|
1:14:48
|
So once side is actually taking care of the bandwidth
|
|
1:14:52
|
and that's fine in a hub and spoke model,
|
|
1:14:55
|
that's going to be just fine. Now we could create
|
|
1:14:59
|
a location for headquarters, however centralized call processing
|
|
1:15:03
|
hub and spoke model like we have, we would need to make sure that
|
|
1:15:06
|
the bandwidth for Hub_None has at least 120 plus 48K.
|
|
1:15:12
|
Otherwise, let's just say we chose the higher of the value,
|
|
1:15:17
|
120 well then if there are actually five G729 calls,
|
|
1:15:21
|
going on between Branch1 and Headquarters,
|
|
1:15:24
|
then no calls can go between Branch2 and headquarters.
|
|
1:15:27
|
So that's a problem.
|
|
1:15:30
|
So we would need, if we created a new location for Hub_None,
|
|
1:15:34
|
we need to make sure that it was at least 168K,
|
|
1:15:40
|
but it's easier if the two is just to leave it
|
|
1:15:46
|
as unlimited.
|
|
1:15:52
|
OK?
|
|
1:15:54
|
So the same for Branch2 if we leave it as unlimited at headquarters,
|
|
1:15:59
|
then even if there's five calls going on and we've exhausted all 128K,
|
|
1:16:05
|
five calls going on between Branch1 and headqurters,
|
|
1:16:08
|
then there's still unlimited bandwidth to allow up to 48K
|
|
1:16:14
|
both sides are degraded from, then the calling or I suppose
|
|
1:16:18
|
it could be the called, just depending on who started the call,
|
|
1:16:21
|
whether a headquarter phone or a Branch2 phone started the call.
|
|
1:16:25
|
But between the two sites, only 48K can be used or three ILBC calls.
|
|
1:16:33
|
because the maximum of 48 calls is defined for any and all Branch2
|
|
1:16:38
|
devices and this would also include the gateway itself.
|
|
1:16:42
|
The Branch2 gateway would need to be a part of a Branch2 location,
|
|
1:16:46
|
Branch1 gateway a part of the Branch1 location.
|
|
1:16:51
|
Yes, on like I said I know we did cover this on QOS things but
|
|
1:16:58
|
within call manager defining x amount of value on gatekeeper,
|
|
1:17:02
|
it's a little different, as well as on the when you set up actual bandwidth
|
|
1:17:07
|
on the 0 link when you're doing,
|
|
1:17:11
|
your you know, if you're saying a QOS within the actual router.
|
|
1:17:15
|
So the difference in correlation in regards to
|
|
1:17:21
|
amount of bandwidth on the COM as fast as what you can configure inside,
|
|
1:17:25
|
inside the
|
|
1:17:28
|
the locations and all regions,what they're using but,
|
|
1:17:34
|
Also a question, it's just that,
|
|
1:17:37
|
when you're configuring the gatekeepr side, it's different values you're using.
|
|
1:17:41
|
Is that correct?
|
|
1:17:47
|
That's correct. If I was going to configure
|
|
1:17:55
|
first all, calling under the heading, let me use a different color.
|
|
1:18:06
|
If we're talking about call admisssion control,
|
|
1:18:11
|
deadspot on the
|
|
1:18:14
|
talking about Call Admission Control,
|
|
1:18:18
|
then I've got three types, three primary types we have to be concerned with.
|
|
1:18:24
|
First is standard locations.
|
|
1:18:30
|
Second is RSVP based locations.
|
|
1:18:44
|
And the third, as you mentioned David is gatekeeper.
|
|
1:18:56
|
OK? So those are three different types of CAC.
|
|
1:19:01
|
Then I've got my quality of service priority queue
|
|
1:19:07
|
for a priority queue that I want to set up.
|
|
1:19:13
|
And that's going to be a different value altogether.
|
|
1:19:25
|
OK. So the important correlation
|
|
1:19:30
|
between these and I will get to what the gatekeeper is here in a moment.
|
|
1:19:35
|
The important correlation between these
|
|
1:19:42
|
first of all, I'm only going to be using one sort of CAC.
|
|
1:19:46
|
So within CUCM,
|
|
1:19:54
|
within CUCM,
|
|
1:19:57
|
I'm going to be using one of these two, location or RSVP based locations.
|
|
1:20:01
|
The standard or RCP based and then possibly between,
|
|
1:20:09
|
between clusters
|
|
1:20:13
|
or between gateways or whatever, maybe between
|
|
1:20:18
|
you know internet service provider most use SIP,
|
|
1:20:21
|
but you know could be just about anything.
|
|
1:20:24
|
Between clusters, between autonomous systems,
|
|
1:20:26
|
that's where I might very well use the gatekeeper.
|
|
1:20:30
|
So even if I'm using gatekeeper, I still have to have it
|
|
1:20:34
|
registered as a gatekeeper based reference and trunk
|
|
1:20:39
|
within CUCM, so on that gatekeeper based trunk,
|
|
1:20:43
|
even if I'm using locations or RSVP locations for the rest of my CUCM cluster,
|
|
1:20:48
|
I would not put a location or I would probably put the Hub_None
|
|
1:20:53
|
location for unlimited on the trunk out to my gatekeeper.
|
|
1:21:02
|
So
|
|
1:21:06
|
within CUCM, I'm either gonna be using traditional or RSVP locations,
|
|
1:21:10
|
the only correlation between
|
|
1:21:14
|
the x value that we haven't talked about yet and will,
|
|
1:21:18
|
on Friday, for QOS priority queue and I'm not going into calculations
|
|
1:21:21
|
for that right now, because tha will go on for a little while.
|
|
1:21:25
|
The only correlation between CAC value and priority queue value is codec
|
|
1:21:34
|
and number of calls.
|
|
1:21:44
|
That's going to be the correlation between these two entities,
|
|
1:21:49
|
CAC and QOS priority queue.
|
|
1:21:53
|
To answer your question about gatekeeper, so within CUCM
|
|
1:21:59
|
location uses 80K or a G711 call.
|
|
1:22:04
|
711 and 24K for a G729 call as we've already mentioned.
|
|
1:22:13
|
And gatekeeper uses 128K,
|
|
1:22:20
|
for G711 and 16K for a G729.
|
|
1:22:24
|
The easy way to remember gatekeeper is, it takes the default codec bitrate,
|
|
1:22:29
|
which is 64 for 711 or 722 and 8K is the default bitrate for G729
|
|
1:22:38
|
and it multiplies that value times two, because the thinking was
|
|
1:22:43
|
there's two transmit paths, one in either direction.
|
|
1:22:47
|
So that's what gatekeeper uses for CAC and sorry this is a little bit messy.
|
|
1:22:51
|
I'm kind of running against my deadzone there.
|
|
1:22:58
|
Gatekeeper uses 128K for G711
|
|
1:23:04
|
and 16K for G729.
|
|
1:23:11
|
This value,
|
|
1:23:15
|
we'll talk about in the QOS section.
|
|
1:23:19
|
Does that answer the question David or did I not fully answer it?
|
|
1:23:24
|
I'm want to make sure that you're,
|
|
1:23:26
|
That's it, that's good.
|
|
1:23:27
|
Alright, that's great. I think once we get to QOS, another thing is that,
|
|
1:23:31
|
when you configure them with command on
|
|
1:23:35
|
the interface, are you referencing the same thing as what you
|
|
1:23:39
|
put inside the core manager side, I'm sure you partition that in QOS so
|
|
1:23:48
|
Yes the short answer is, never. The short answer is when you're putting
|
|
1:23:52
|
anything either in terms of the bandwidth command,
|
|
1:23:57
|
directly on the interface, just that command bandwidth
|
|
1:24:03
|
and the value for whenever we're talking about RSVP and we say
|
|
1:24:07
|
IP RSVP bandwidth and the net value or, and actually all of these
|
|
1:24:15
|
or what we put in as the bandwidth or priority command
|
|
1:24:20
|
for the prioriy queue for low latency queueing, none of those values
|
|
1:24:24
|
are equal to one another or equal to what we put in
|
|
1:24:29
|
inside of Cisco Call Manager. First of all bandwidth value in the interface
|
|
1:24:34
|
itslef has to do with how much actual bandwidth there is
|
|
1:24:38
|
on that link for that PVC if we're using frame relay or for that
|
|
1:24:43
|
link type if it's something else. Well mainly will be sticking with
|
|
1:24:46
|
frame relay, but touch on some other layer 2 types as well.
|
|
1:24:50
|
OK, that's the value just for the link itself.
|
|
1:24:54
|
But in terms of IP RSVP bandwidth,
|
|
1:24:59
|
for locations based bandwidth, as we see in anyone of these,
|
|
1:25:04
|
we will discuss why those values on Friday, will be actually
|
|
1:25:10
|
a little bit different from each other, this is multiples of 24,
|
|
1:25:14
|
for Branch1 and IP RSVP is multiples of 24 with a little bit of
|
|
1:25:20
|
overhead that we'll talk about, something called worst case scenario.
|
|
1:25:24
|
I'll show the documentation in where everything is pertaining to that,
|
|
1:25:28
|
but then the big thing that I wanted to point out was
|
|
1:25:32
|
in terms of locations,
|
|
1:25:38
|
in terms of locations,
|
|
1:25:43
|
versus
|
|
1:25:47
|
QOS priority queue
|
|
1:25:51
|
only correspondence between the two.
|
|
1:25:56
|
The only thing relevant, the only correlation between the two
|
|
1:26:00
|
has nothing to do with the bandwidth value at all.
|
|
1:26:03
|
Nothing to do with it, it has just to do with what is the codec,
|
|
1:26:13
|
and
|
|
1:26:18
|
how many calls.
|
|
1:26:21
|
That's the two only relevant factors between the two.
|
|
1:26:27
|
Actual value here, location and the actual value here,
|
|
1:26:32
|
will be derived from these two, but will have nothing to do with one another.
|
|
1:26:39
|
The actual value for location and QOS will have nothing to do.
|
|
1:26:44
|
Simply be based on what's the codec and what's the number of calls.
|
|
1:26:47
|
But we will go over all the actual calculations
|
|
1:26:49
|
and reshow the calculations per location.
|
|
1:26:53
|
Regular traditonal locations and then also RSVP locations
|
|
1:26:58
|
and then quality of service priority queue, we'll go over all of those
|
|
1:27:02
|
calculations the column algorithms but the
|
|
1:27:07
|
equations that will be used to derive those, we'll go over all of that.
|
|
1:27:15
|
OK? Great, any other questions?
|
|
1:27:19
|
Sure Joe, I can repeat the value for gatekeeper.
|
|
1:27:22
|
Gatekeeper is going to use
|
|
1:27:25
|
essentially it's default
|
|
1:27:31
|
default codec bitrate,
|
|
1:27:38
|
times two because there's a transmit path
|
|
1:27:44
|
ongoing on this direction and another transmit path going in this direction.
|
|
1:27:49
|
so the two transmit path is where it comes up with the times two.
|
|
1:27:53
|
So the default bitrate for G729,
|
|
1:27:58
|
G729 is 8, then multiplied by 2 is going to be 16
|
|
1:28:07
|
kilobits per second for gatekepeer.
|
|
1:28:12
|
And G711 equals 64 so times two,
|
|
1:28:19
|
equals 128 kilobits per second as far as gatekeeper is concerned.
|
|
1:28:30
|
Any other codec, you would just take again the default bit rate,
|
|
1:28:34
|
and multiply that times two and that is the ITUT spec
|
|
1:28:38
|
or what is considered per call in terms of call admission control.
|
|
1:28:45
|
Now there's one exception to that with gatekeeper
|
|
1:28:50
|
and it's really not an exception, it's just something to keep in mind.
|
|
1:28:53
|
And we'll go into a lot of detail on it when we talk about gatekeeper
|
|
1:28:57
|
and or when we talk about gatekeeper or as it relates to the cube,
|
|
1:29:03
|
the Cisco Unified Border Element.
|
|
1:29:04
|
But if gatekeeper is integrated with a unified border element,
|
|
1:29:08
|
or a CUBE module then
|
|
1:29:12
|
we effectively have twice the amount of bandwidth needed
|
|
1:29:16
|
because we have two call legs for every call since we're actually
|
|
1:29:21
|
looping it through a CUBE or a Cisco Unified Border Element module.
|
|
1:29:26
|
So again we'll talk a lot more in depth about that
|
|
1:29:29
|
on the gatekeeper and CUBE modules,
|
|
1:29:32
|
plus the modules for deep dives, but just one thing to keep in mind now,
|
|
1:29:36
|
gatekeeper with CUBE does effectively double the amount of bandwidth
|
|
1:29:40
|
needed per call based on the fact that we're looping it through another device
|
|
1:29:48
|
in most situations.
|
|
1:29:51
|
OK. So
|
|
1:29:56
|
there's no other questions, I'll certainly answer any that happen to pop up here.
|
|
1:30:01
|
But if there's not others,
|
|
1:30:03
|
then let's look at SRST references and as soon as we do SRST references,
|
|
1:30:07
|
we'll take a quick break. So CUCM SRST references under system,
|
|
1:30:12
|
we're told to create two SRST or Survivable Remote Site Telephony References.
|
|
1:30:18
|
To later be used by all Branch1 and Branch2 devices respectively.
|
|
1:30:21
|
Name them intuitively following the format of SRST_Branch1 and Branch2,
|
|
1:30:26
|
and then assign the SRST Branch1 reference, the IP address
|
|
1:30:32
|
of the loop back 0 interface of the Branch1 R2 router,
|
|
1:30:35
|
for both Skinny and SIP endpoints and then assign
|
|
1:30:40
|
the SRST Branch2 reference, the IP address of the loopback
|
|
1:30:45
|
0 interface on the Branch2 Router 3, again for Skinny and SIP endpoints.
|
|
1:30:52
|
OK? There's a reason we're skipping some things
|
|
1:30:56
|
so if you've noticed, we've skipped presence group, that's because
|
|
1:30:59
|
we're going to spend an entire module talking about presence.
|
|
1:31:04
|
And so there's really no reason to cover it now, I mean they're just groups.
|
|
1:31:07
|
You just create groups and modify relationships to one another
|
|
1:31:11
|
but there's really no reason to talk about that now,
|
|
1:31:13
|
since we're not gonna be using it now.u
|
|
1:31:15
|
Also device mobility and physical location, this physical location has to
|
|
1:31:21
|
do with device mobility, these are the things that we create,
|
|
1:31:24
|
device mobility groups, device mobility info, physical location
|
|
1:31:28
|
and how we link those together into device pools.
|
|
1:31:31
|
That's going to be specifically for device mobility and we again, we'll have
|
|
1:31:35
|
a whole module just for device mobility.
|
|
1:31:38
|
Just like we'll have another module for unified mobility,
|
|
1:31:41
|
mobile connect, and mobile voice access.
|
|
1:31:43
|
There's really no reason to talk about those now
|
|
1:31:45
|
if we're not going to go into why we created them.
|
|
1:31:49
|
OK, DHCP we've already talked about,
|
|
1:31:53
|
LDAP in a previous module, LDAP we're talking about tomorrow actually
|
|
1:32:00
|
or users enrolls, so we won't cover that today.
|
|
1:32:04
|
Locations we just talked about. Multi-link priority and presidence,
|
|
1:32:10
|
that's an entire module all into itself, easily so certainly won't talk about that.
|
|
1:32:17
|
We haven't talked about calling search spaces or partitions or anyting
|
|
1:32:20
|
that are necessary to understand multilevel priority and presidence.
|
|
1:32:26
|
Enterprise and service parameters we're going to hit on,
|
|
1:32:29
|
and moving on down some of the things we're gonna hit on, but SRST
|
|
1:32:33
|
we're hitting on this and location and region
|
|
1:32:36
|
before we come back to device pool that way,
|
|
1:32:39
|
when we cometo device pool, which I believe is a very nice task.
|
|
1:32:44
|
Great, yes it is.
|
|
1:32:47
|
We'll have everything necessary to populate those device pools.
|
|
1:32:51
|
OK? So let's go to SRST and perform the functions we were instructed.
|
|
1:32:57
|
Zero references by default, we'll create one,
|
|
1:33:01
|
the name convention that we were instructed, notice we're not creating
|
|
1:33:05
|
one of these for Corporate Headquarter, that's because it's got two
|
|
1:33:09
|
CUCM servers or just because we weren't instructed to.
|
|
1:33:12
|
You could have SRST at your main site, but most do 't.
|
|
1:33:16
|
So we were told to use the loopback of Branch1 Router 2,
|
|
1:33:23
|
let's take a look at our topology.
|
|
1:33:28
|
OK? So here we see the loop back is 177.1, that's headquarter Router1
|
|
1:33:34
|
and we want 2, so 177.1.254.2
|
|
1:33:44
|
and that's for the IP address and SIP network or IP address.
|
|
1:33:50
|
OK? So it's going to be the same for both.
|
|
1:33:54
|
For Skinny and for SIP, this is not secure, again security is something
|
|
1:33:58
|
we will spend an entire another module talking about.
|
|
1:34:02
|
And we'll copy this for Branch2 and if we look back
|
|
1:34:05
|
our loopback is the same except for the last octet which is .3.
|
|
1:34:09
|
The reason we can use different octets is because these are actually full
|
|
1:34:14
|
slash 32 or all bits set to one or 255255255.255,
|
|
1:34:21
|
so each network only has one host.
|
|
1:34:26
|
Three and click save.
|
|
1:34:30
|
And as long as add successful, which is was,
|
|
1:34:34
|
then we've got our two SRST references created.
|
|
1:34:39
|
OK? So we have met the requirements for 1.7.
|
|
1:34:43
|
|
