|
0:00:15
|
And now that we've talked about what happens with a
|
|
0:00:20
|
Line Calling Search Space and a Device Calling Search Space,
|
|
0:00:24
|
partitions are concatenated together to form a new resulting CSS
|
|
0:00:28
|
with line partitions being ordered first or hired.
|
|
0:00:32
|
Let's take a look at how that could possibly impact a dial plan
|
|
0:00:37
|
that we might want to configure or route pattern.
|
|
0:00:42
|
Let's look at Application.
|
|
0:00:45
|
The device CSS and first of all let me go back and just remind
|
|
0:00:49
|
The primary reasons that we are using Calling Search Spaces were
|
|
0:00:53
|
Path Selection or Site-Specific Call Routing, Number 1,
|
|
0:00:59
|
and then Number 2, is Class of Restriction.
|
|
0:01:01
|
But we were using the same CSS for both functions.
|
|
0:01:07
|
What we are going to seek to do now is to split those Calling Search Spaces
|
|
0:01:13
|
out into application of separate functions.
|
|
0:01:17
|
So we are gonna use the device CSS as we see here,
|
|
0:01:21
|
is going to allow access to all external routes,
|
|
0:01:27
|
even if the person shouldn't be able to dial anywhere but internal and 911.
|
|
0:01:32
|
We're going to give every device, every phone within any one location,
|
|
0:01:41
|
any one geographic area, one city or one cluster.
|
|
0:01:47
|
We're gonna give all devices access to a single Calling Search Space
|
|
0:01:55
|
that allows access to all routes.
|
|
0:02:03
|
And actually we're gonna give all devices, pretty much within a country,
|
|
0:02:09
|
anywhere that has, in the US case,
|
|
0:02:13
|
in Canada, the North America Numbering Plan, they share one.
|
|
0:02:16
|
The only place that has similar numbering plans,
|
|
0:02:19
|
we're gonna give them access to all of the numbers.
|
|
0:02:22
|
So, regardless of whether we have one site, a hundred sites, or 1000 sites,
|
|
0:02:29
|
We're gonna have one Calling Search Space
|
|
0:02:32
|
that's going to give, I'm sorry. It is still going to be based on site.
|
|
0:02:39
|
So, I had a little ahead of myself there.
|
|
0:02:42
|
So, per geographic area, we are going to have one CSS.
|
|
0:02:50
|
Then what we'll do is we will have another Calling Search Space at the line
|
|
0:02:58
|
This will actually define Class of Service.
|
|
0:03:01
|
So the Device Calling Search Space will define the path to the local gateway.
|
|
0:03:06
|
So for each site there will be one CSS.
|
|
0:03:10
|
By the thousand sites, I don't have one CSS just yet.
|
|
0:03:17
|
We'll get to that shortly, but one CSS just yet for all sites.
|
|
0:03:20
|
I have one CSS for each site.
|
|
0:03:22
|
So if I have a thousand sites, I have 1000 CSSs.
|
|
0:03:25
|
Remember before, if I had a thousand sites,
|
|
0:03:28
|
I had to have 4000 CSSs because I had one Calling Search Space
|
|
0:03:35
|
for each site and each class of service.
|
|
0:03:40
|
Now, I've got one CSS for each site that calls everywhere.
|
|
0:03:44
|
And then I'm going to have four additonal Calling Search Spaces
|
|
0:03:49
|
that will block undesired routes. Wait a minute,
|
|
0:03:53
|
What do you mean block? Did you mean allow?
|
|
0:03:56
|
Access to what they're allowed to dial?
|
|
0:03:59
|
Well, if the device allows them to dial anything,
|
|
0:04:06
|
and each of these route patterns are routed.
|
|
0:04:11
|
Route patterns do not block.
|
|
0:04:13
|
But they are routed too specific route list and route groups.
|
|
0:04:18
|
So therefore specific gateways that's giving us our site-specific call routing.
|
|
0:04:24
|
Then if we just allowed something at the line,
|
|
0:04:28
|
the concatenation would be allowing let's say local here,
|
|
0:04:33
|
and also allowing it at the device that were also allowing long distance and international
|
|
0:04:40
|
so we would be allowing them to call anywhere.
|
|
0:04:44
|
We can't just allow them to call somewhere at the line
|
|
0:04:47
|
and consider that Class or Restriction won't block them from anything,
|
|
0:04:51
|
as the device allows everything.
|
|
0:04:55
|
So what happens is, looking very similar to the last slide,
|
|
0:05:00
|
relying device partitions and Calling Search Spaces
|
|
0:05:04
|
result in a new concatenated Calling Search Space with new partitions.
|
|
0:05:11
|
What we've done is we've added the route patterns inside those partitions
|
|
0:05:14
|
and we can see that although there are more route patterns in this PSTN partition,
|
|
0:05:20
|
that does the ellipses, the dot dot dot.
|
|
0:05:23
|
We see that we do have a route to 9.011!
|
|
0:05:30
|
becasue we have all routes at the device level.
|
|
0:05:34
|
But then we've got a Block International Partition
|
|
0:05:39
|
and Blocked International Pattern. Now this happens to be a Translation Pattern.
|
|
0:05:44
|
It doesn't really matter whether it's a translation pattern, a route pattern.
|
|
0:05:48
|
You can block at a route pattern level but you have to point to route group or whatever.
|
|
0:05:54
|
It will just never get there, but you don't have to point to one,
|
|
0:06:01
|
but the idea is that we can use a translation pattern or route pattern, it doesn't matter,
|
|
0:06:09
|
to create our Blocked Patterns.
|
|
0:06:12
|
If it is an equal match 9.011!, is the exact equal match.
|
|
0:06:21
|
If this one's even slightly less specific than this one,
|
|
0:06:25
|
then what we're trying to do won't work. But if it's an equal match,
|
|
0:06:28
|
and it's blocked because it is ordered higher,
|
|
0:06:32
|
what we get is the result that this user cannot dial internationally.
|
|
0:06:37
|
But they can dial long distance. They can dial local,
|
|
0:06:43
|
There is probably 911 and internal numbers that are not pictured here.
|
|
0:06:48
|
but they are a part of this PSTN Partition.
|
|
0:06:52
|
And so they do have the ability to dial everywhere except internationally.
|
|
0:06:58
|
Now again, you might say wait a minute, maybe this makes sense.
|
|
0:07:03
|
Then if it doesn't, please speak up. Please mention anything, any questions at this point.
|
|
0:07:10
|
But you might say this makes sense, maybe why or maybe not why but that we can block,
|
|
0:07:18
|
at the line level because of the resulting higher ordered line partition
|
|
0:07:23
|
and the resulting concatenated CSS, mouthful to say,
|
|
0:07:29
|
But why would we wanna do this?
|
|
0:07:31
|
Well, because if I only have to create four blocking partitions,
|
|
0:07:37
|
and technically maybe only three, but four blocking partitions, four blocking patterns,
|
|
0:07:45
|
then I only have to create four blocking CSSs for the entire numbering plan.
|
|
0:07:53
|
So, for everyone within a country, or US North America Numbering Plan and Canada,
|
|
0:07:59
|
anyone within that numbering plan can use these four blocking partitions and CSSs.
|
|
0:08:08
|
And then I only have to create one calling seach base per site.
|
|
0:08:15
|
Let's take a look, first of all, example with configuration
|
|
0:08:18
|
and then the savings that one lead us.
|
|
0:08:20
|
Here's a translation pattern.
|
|
0:08:22
|
Here we've got the actual pattern of 9.011!
|
|
0:08:28
|
It's in a partition that is inside of a CSS that is applied to the line.
|
|
0:08:34
|
And its not a routing pattern, but it is a blocking pattern.
|
|
0:08:40
|
Then you can choose what enunciator message you want played if it's a Skinny device.
|
|
0:08:44
|
Remember, H.323 or Skinny devices will play enunciator.
|
|
0:08:50
|
Remember MGCP and more importantly if it's a phone dialling a SIP phone, it will not play the enunciator.
|
|
0:09:02
|
So let's take a look at this. David, to answer your question.
|
|
0:09:08
|
David commented, so going forward
|
|
0:09:11
|
this would be the best way to configure for all deployment types.
|
|
0:09:15
|
Yes, but, I would say the answer to that question is yes, if you are deploying
|
|
0:09:22
|
or maybe even reorganizing a 6.X cluster and a 4.
|
|
0:09:27
|
But we haven't got to other new features in 7 which
|
|
0:09:31
|
we'll very quickly see what it can do for us.
|
|
0:09:34
|
Give me just a bit to answer definitively on whether
|
|
0:09:38
|
the line devices approaches the best method.
|
|
0:09:40
|
I will go ahead and say the Line Device approach is the best method.
|
|
0:09:44
|
But there's something more we can add on to it
|
|
0:09:46
|
to give us even more savings and a lot more power and flexibility.
|
|
0:09:53
|
So taking a look at building classes of service, with wine device approach.
|
|
0:10:00
|
Remember before we had Seattle phones and Austin phones,
|
|
0:10:07
|
Now, we've got a separate section here above this grey line, this per lines,
|
|
0:10:12
|
for all lines within a country or within a dialling plan.
|
|
0:10:16
|
When you have multiple countries, you do still need multiple dialling plans.
|
|
0:10:20
|
That's not, you're not going to escape that.
|
|
0:10:24
|
But we also have then specific Seattle devices,
|
|
0:10:29
|
Seattle phones, even Seattle gateways for inbound calls maybe,
|
|
0:10:33
|
Austin devices and then any number of other sites we have, we'll have devices
|
|
0:10:39
|
for Calling Search Spaces and patterns.
|
|
0:10:43
|
Note that we still have to have the replication of the patterns.
|
|
0:10:47
|
So, here I’ve got the line
|
|
0:10:49
|
calling search space dictates class of service or class of restriction.
|
|
0:10:53
|
Here we’ve got two CSS's
|
|
0:10:56
|
or class of restriction picture, internal or non-restricted.
|
|
0:11:00
|
For internal, we’re blocking local calls,
|
|
0:11:03
|
long distance, and international.
|
|
0:11:07
|
Unrestricted is simply something that points to the internal DN.
|
|
0:11:12
|
Now, you could note that as long as the device
|
|
0:11:15
|
has a calling search space that points to internal,
|
|
0:11:17
|
You actually don't have to have this
|
|
0:11:20
|
CSS defined and applied to a line.
|
|
0:11:22
|
The reason that we do that is for our own
|
|
0:11:27
|
ID10 Tier, our own administrative
|
|
0:11:31
|
or actually possibly for designing, implementing and then turning it over to a customer.
|
|
0:11:36
|
Just any possible mistakes where someone sees
|
|
0:11:40
|
Wait a minute, I know that
|
|
0:11:43
|
these many fields or checkboxes or dropdowns
|
|
0:11:46
|
are supposed to be filled in with any given page.
|
|
0:11:50
|
and I'm on a line page for a phone and I know that it’s calling search space
|
|
0:11:55
|
because people that deployed it for us,
|
|
0:11:57
|
they’re gone, but they told us that every line and device should have
|
|
0:12:01
|
a CSS and a CSS as per device are named
|
|
0:12:05
|
Site-specific devices like Seattle devices, Austin devices.
|
|
0:12:10
|
And the ones for the lines are the class restriction.
|
|
0:12:13
|
They might just see
|
|
0:12:14
|
three classes of restrictions CSSs when they do a dropdown
|
|
0:12:17
|
And they see a number of devices that don't have a CSS configured,
|
|
0:12:21
|
although they would still work properly.
|
|
0:12:23
|
There were just a little bit of confusion and
|
|
0:12:25
|
possibly misconfiguration due to that, so that’s
|
|
0:12:28
|
the reason we go ahead and create the unrestricted class of restriction.
|
|
0:12:37
|
So, now we look at the device CSS dictates path selection.
|
|
0:12:42
|
This CSS points only,
|
|
0:12:45
|
other than internal, points only to the route patterns
|
|
0:12:48
|
that point only to the Seattle route list
|
|
0:12:50
|
and point only to the Seattle route groups and gateways.
|
|
0:12:54
|
And our Austin devices point only to the Austin route patterns,
|
|
0:12:59
|
the Austin route list and the Austin route groups and gateways.
|
|
0:13:04
|
So, now instead of N x 4 which what we had last time,
|
|
0:13:07
|
number of sites x number of class of restrictions.
|
|
0:13:11
|
We now have N + 4.
|
|
0:13:13
|
So instead of 1000 x 4 = 4000,
|
|
0:13:17
|
we’ve now got N + 4 or 1004. 1000 CSSs, one for each site
|
|
0:13:23
|
thousand sites but only four classes of restrictions
|
|
0:13:26
|
if were still all in the same country or dialling plan.
|
|
0:13:30
|
That’s the savings of almost all 3000 CSSs and
|
|
0:13:34
|
almost 3000 partitions, that’s a tremendous savings.
|
|
0:13:39
|
We’re now at 5992
|
|
0:13:45
|
savings of entity, CSSs and partitions combined that we have to create
|
|
0:13:50
|
in CUCM. That’s a lot less work.
|
|
0:14:00
|
We have some configurations to think of.
|
|
0:14:03
|
But before we go on to considerations
|
|
0:14:06
|
and then before we build on this to add one more
|
|
0:14:10
|
level of complexity, but then also
|
|
0:14:15
|
tremendous savings and when you see it,
|
|
0:14:18
|
ultimately, that complexity turns into
|
|
0:14:22
|
a tremendous ease of use, ease of troubleshooting,
|
|
0:14:26
|
ease of building, scalability, moving forward, design, administration.
|
|
0:14:33
|
Before we move on to that,
|
|
0:14:37
|
Then anyone have questions regarding
|
|
0:14:40
|
the basic line device approach,
|
|
0:14:43
|
the line blocks, whatever we don't want them to call,
|
|
0:14:47
|
the device allows everything to a specific route pattern
|
|
0:14:52
|
we still have, if we have a thousand sites,
|
|
0:14:55
|
and we’ve got 1, 2, 3, 4, 5, 6 route patterns,
|
|
0:15:00
|
we’ve still got 6 patterns times a thousand sites, 6000 patterns
|
|
0:15:06
|
1000, one for every site, 1000 route lists, 1000 route groups.
|
|
0:15:14
|
We still got a lot of stuff we have to configure.
|
|
0:15:17
|
But, we’ve saved ourselves tremendous, and even if we take this down to a hundred,
|
|
0:15:22
|
the savings are exponential, there are still tremendous savings here.
|
|
0:15:29
|
So I’ve got a question on this, you just got the internal
|
|
0:15:33
|
CSS that’s always has the blocked partitions.
|
|
0:15:36
|
So you would, if I said if I had local
|
|
0:15:38
|
CSS, I would have just blocked partitions for everything except local calling,
|
|
0:15:43
|
long distance and international, is that correct?
|
|
0:15:50
|
Yes, so if I had a, so right the CSS for internal
|
|
0:15:55
|
blocks everything except for internal.
|
|
0:15:58
|
And the reason internal is allowed has nothing to do with CSS on the line
|
|
0:16:02
|
but because the device plus the line,
|
|
0:16:06
|
the device points to the internal partitions, right.
|
|
0:16:09
|
So, for the local, if we wanted to have a local class of restriction,
|
|
0:16:13
|
local CSS would point to a partition,
|
|
0:16:18
|
That partition would have the patterns in it.
|
|
0:16:21
|
So in this case, we’d split up,
|
|
0:16:23
|
there wouldn’t be just partitions or blocked PSTN.
|
|
0:16:26
|
We'd have a partition for local
|
|
0:16:30
|
and a pattern, a translation pattern with a blocked
|
|
0:16:33
|
Actually, sorry, first of all, we’d have
|
|
0:16:38
|
blocked international as a partition,
|
|
0:16:42
|
blocked long distance as a partition,
|
|
0:16:44
|
blocked local as a partition and blocked
|
|
0:16:49
|
really that would be it because ultimately you can’t block
|
|
0:16:54
|
emergency calls or internal, or else if you don't relay
|
|
0:16:57
|
a phone system, you have a paperweight.
|
|
0:16:59
|
So the blocked long distance would have a pattern for long distance that was blocked.
|
|
0:17:06
|
Blocked international would have a pattern for international that was blocked.
|
|
0:17:10
|
Blocked local would have a pattern for a local that was blocked.
|
|
0:17:12
|
So, if I wanted a local class of restriction,
|
|
0:17:15
|
I’d create a local CSS for the line
|
|
0:17:18
|
and in it I will add the partitions which would inherently add the patterns.
|
|
0:17:23
|
I would add the partitions for blocked international
|
|
0:17:26
|
and blocked long distance and that’s it.
|
|
0:17:30
|
Local, internal would automatically be allowed because of the device allowing everything.
|
|
0:17:40
|
I just wanted to point out to, I mean, I
|
|
0:17:43
|
do this on a regular basis, like customer sites.
|
|
0:17:46
|
And everytime you got to do it,
|
|
0:17:48
|
it’s still something you got to kind of take a half step back
|
|
0:17:52
|
think through the logic on and
|
|
0:17:55
|
kind of mapped it out on paper before you start your program it
|
|
0:17:58
|
because it almost this counter or two when your blocking
|
|
0:18:01
|
calls with a calling search space.
|
|
0:18:04
|
So if it doesn’t make sense at first
|
|
0:18:06
|
it really is something you have to take a half step back
|
|
0:18:09
|
and rethink the way you, if all you do is the device calling search space all the time.
|
|
0:18:14
|
You got to rethink the way you do things a little bit because you're
|
|
0:18:17
|
not just allowing calls, you're not allowing, you're blocking.
|
|
0:18:26
|
That would be correct. Thanks for that Michael. It’s very true.
|
|
0:18:29
|
It is very countering to whatever against your
|
|
0:18:33
|
and what you’re thinking, you're thinking of allowing the user to
|
|
0:18:37
|
only call certain numbers, 911,
|
|
0:18:41
|
internal numbers and local numbers, let’s say. You're not actually
|
|
0:18:46
|
typically in the mindset of approaching it from the reversed direction and
|
|
0:18:50
|
blocking them from calling international and
|
|
0:18:54
|
and long distance or national numbers.
|
|
0:18:57
|
So, another way to think about this,
|
|
0:18:59
|
let’s start here with the whiteboard, is
|
|
0:19:03
|
almost that when you're looking at this kind of a way of deploying
|
|
0:19:11
|
systems in a moving forward or even
|
|
0:19:14
|
studying in your own lab time for the actual CCI voice lab.
|
|
0:19:18
|
Do it as if you're gonna go ahead and make the assumption
|
|
0:19:25
|
that every phone can call everywhere by default
|
|
0:19:29
|
and it’s your job to stop them from calling the places they shouldn’t call.
|
|
0:19:33
|
And thinking of that, you'll go ahead and you'll create your
|
|
0:19:37
|
allowed route patterns in a single partition or each site
|
|
0:19:44
|
not soon, but soon we’ll actually come up with a way here back
|
|
0:19:50
|
But for the time being with what we've slides and concepts we looked at so far,
|
|
0:19:54
|
You'll by default create one partition
|
|
0:19:56
|
and a set of patterns for each site that allow everything.
|
|
0:20:00
|
And then you'll just go about, you kind of thinking things
|
|
0:20:03
|
in reversed direction. Now that everyone has on their device
|
|
0:20:07
|
the ability to call everywhere and maybe even just test that not
|
|
0:20:10
|
every single phone, no 400 phones at a thousand sites but
|
|
0:20:14
|
maybe even juts one phone at each site
|
|
0:20:17
|
as we’re setting it up in the lab or even maybe going to play it live.
|
|
0:20:21
|
Make sure that they can dial all the patterns and all the phones have the
|
|
0:20:24
|
exact same CSS on the device because you would do it
|
|
0:20:27
|
through the BAT tool of course, Bulk Administration
|
|
0:20:30
|
And then we’ll go about blocking individual
|
|
0:20:34
|
lines and thinking about everyone can call everywhere.
|
|
0:20:38
|
Then what is it we have to restrict them
|
|
0:20:41
|
in order to build this class of restriction.
|
|
0:20:44
|
That’s one of the reasons I like to refer to instead of class of service.
|
|
0:20:47
|
Instead of what service do you have, look at it as a
|
|
0:20:50
|
class of restriction, so, what restrictions
|
|
0:20:53
|
do you have? Where is it that you're restricted from dialing?
|
|
0:20:57
|
And that helps at me even
|
|
0:21:00
|
in known designs to keep it straight in terms of,
|
|
0:21:04
|
that’s right, we’re restricting so we have to block
|
|
0:21:06
|
at the line, we have to actually restrict them from calling
|
|
0:21:09
|
where they are otherwise able to call.
|
|
0:21:13
|
So, let’s take a look here, we’ve got
|
|
0:21:18
|
So, this phone, and i'ts gonna be in Seattle.
|
|
0:21:26
|
And it should be allowed to have long distance rights only, LD or national.
|
|
0:21:32
|
And we've got another phone at Seattle, I'm only gonna draw one site
|
|
0:21:39
|
just for this sake of space that can call local
|
|
0:21:44
|
and other Seattle phones
|
|
0:21:55
|
Another Seattle phone that can dial restricted, internal and 911.
|
|
0:22:04
|
So I've got here a calling search space for international use
|
|
0:22:18
|
This phone has a calling search space
|
|
0:22:27
|
CSS for long distance.
|
|
0:22:40
|
Local phone has the calling search space for
|
|
0:22:56
|
So now I’ve got partitions, I’ll make those orange.
|
|
0:23:05
|
Partition that a
|
|
0:23:23
|
except local
|
|
0:23:32
|
emergency
|
|
0:23:41
|
internal
|
|
0:23:51
|
So the restricted calling, we’ll actually let’s draw our patterns first.
|
|
0:23:55
|
So, now we've got our and we’d probably do better to name this blocked,
|
|
0:24:02
|
international, blocked long distance, blocked
|
|
0:24:08
|
local. You never really wanna emergency or internal.
|
|
0:24:15
|
Those would be part of our allowed partitions
|
|
0:24:19
|
but not part of our block, so our blocked partitions are going to be
|
|
0:24:25
|
separate from our
|
|
0:24:31
|
So now we have our patterns.
|
|
0:24:36
|
So we are gonna have a 9.0 and we’re just going
|
|
0:24:38
|
according to North America Numbering Plan right now.
|
|
0:24:40
|
Again, you would have to have one of these for each country or numbering plan.
|
|
0:24:45
|
9.011, 9.011-1, I'm just gonna write 10 Xs.
|
|
0:25:01
|
North American Numbering Plan, that would be
|
|
0:25:12
|
And then we’re going to have a 9.10Xs
|
|
0:25:23
|
That’s gonna be a local number
|
|
0:25:25
|
depending on there in the USUR. You can dial 10 or 7 digits.
|
|
0:25:33
|
Differentiating factor is that first digit’s a 1. This cannot be a 1.
|
|
0:25:40
|
That was differentiated at least that.
|
|
0:25:53
|
And then I've got 911 in internal
|
|
0:25:58
|
patterns but again those wouldn’t be blocked.
|
|
0:26:00
|
So I don't wanna draw those necessarily in red.
|
|
0:26:03
|
So, my international blocked is going to point.
|
|
0:26:10
|
I actually draw it this way because the patterns are
|
|
0:26:14
|
We’ll draw it from the perspective of the call.
|
|
0:26:17
|
So I’ll draw the partitions pointing to the patterns.
|
|
0:26:22
|
The patterns are inside the partitions, but from the directive of the calling,
|
|
0:26:27
|
we call through the CSS to the partition
|
|
0:26:31
|
and eventually find patterns within that.
|
|
0:26:34
|
But our blocked long distance and we blocked local.
|
|
0:26:43
|
doesn't block anything, internal doesn’t block anything, so,
|
|
0:26:48
|
if I want my phones to have a
|
|
0:26:55
|
restricted calling search space as we see here
|
|
0:26:58
|
then I'm going the need to make sure that they are restricted CSS.
|
|
0:27:07
|
block local, block long distance, block international.
|
|
0:27:16
|
If they only should’ve local rights
|
|
0:27:20
|
then we only have to block long distance and national.
|
|
0:27:29
|
They should’ve long distance, then we only need to block international.
|
|
0:27:35
|
They have international, we don't need to block anything.
|
|
0:27:38
|
Everything’s pretty much open.
|
|
0:27:39
|
So that’s where you saw, we could either not assign any calling search space
|
|
0:27:44
|
or we would actually point them
|
|
0:27:48
|
to the allow internal partition and allow emergency partition
|
|
0:27:56
|
blocking partitions in any way.
|
|
0:27:57
|
And again the only reason we would do that, the only reason we would set up
|
|
0:28:01
|
and international CSS or unrestricted
|
|
0:28:04
|
was simply so that we could have something to apply
|
|
0:28:08
|
to the actual line so that
|
|
0:28:11
|
going back later ourselves or other administrators wouldn’t
|
|
0:28:14
|
possibly become confused as to why
|
|
0:28:17
|
that dropdown for CSS on the given phone’s line have been left blank.
|
|
0:28:26
|
We've only got actually a few more slides, I think about six more slides
|
|
0:28:32
|
Everyone understands the tremendous savings there.
|
|
0:28:37
|
As long as everyone’s clear on line device approach
|
|
0:28:41
|
1.) How to do it, 2.) Why we might
|
|
0:28:44
|
want it other than just Cisco best practice, recommended practice.
|
|
0:28:52
|
Let's move on to
|
|
0:28:54
|
Well first of all let’s take a look at some of the considerations with Line Device
|
|
0:28:57
|
and then we’ll take a look at the next building block.
|
|
0:29:00
|
So line device approach considerations
|
|
0:29:02
|
Some are the call forward all
|
|
0:29:04
|
calling search space activation policy.
|
|
0:29:08
|
So this actually came about in 6.X CUCM
|
|
0:29:16
|
in CUCM version 4 and version 5
|
|
0:29:21
|
We were still able to use the line device approach
|
|
0:29:25
|
and even back in certain version of 3
|
|
0:29:28
|
Although at some point there was actually a switch in the order
|
|
0:29:32
|
of the partition ordering,
|
|
0:29:34
|
although there has always been a resulting concatenated search space.
|
|
0:29:37
|
But back in 4 and 5, versions 4 and 5,
|
|
0:29:41
|
if we wanted to call forward all,
|
|
0:29:44
|
Now this isn’t getting in to call forward busy, no answer.
|
|
0:29:47
|
Each of those still only have one CSS
|
|
0:29:50
|
One CSS per call for busy internal.
|
|
0:29:53
|
One CSS per call busy external
|
|
0:29:55
|
One CSS per call for no answer
|
|
0:29:58
|
internal, external, no coverage, failure
|
|
0:30:01
|
on and registered is a number of different ones. But for call forward all,
|
|
0:30:06
|
we also always only had 1 CSS
|
|
0:30:09
|
Now, in previous versions actually,
|
|
0:30:12
|
you have to take a look at the release notes for each one.
|
|
0:30:15
|
In 4.X, it says that you should always configure it because
|
|
0:30:18
|
varying results may occur. In other words,
|
|
0:30:22
|
from release to release, maintenance release to maintenance release
|
|
0:30:24
|
within 4.x, you might actually have
|
|
0:30:28
|
differing results or your mileage may vary, as some say.
|
|
0:30:32
|
But largely, the way it was in 4 and 5 was that
|
|
0:30:37
|
whatever line CSS and device CSS you had,
|
|
0:30:43
|
that resulting concatenated CSS
|
|
0:30:46
|
would be the default CSS applied
|
|
0:30:49
|
to the forward all, that was in CUCM version 4 and 5.
|
|
0:30:54
|
In version 6, we now actually have and if you wanted
|
|
0:30:58
|
to change that, in other words, if you wanted to restrict someone
|
|
0:31:00
|
from pressing the call forward all soft key
|
|
0:31:03
|
and not being able to forward other calls internationally,
|
|
0:31:07
|
even though they are allowed to call during the day
|
|
0:31:09
|
internationally, maybe they are purchasing agent.
|
|
0:31:12
|
They purchase a lot of things from overseas.
|
|
0:31:16
|
We don't want them forwarding their calls because we could get in the
|
|
0:31:18
|
toll fraud options, right? If someone
|
|
0:31:23
|
you know, got a little intelligence and realized
|
|
0:31:26
|
that all they have to do
|
|
0:31:29
|
is forward their call to
|
|
0:31:33
|
a girl or a guy that they met while they were on one of their purchasing
|
|
0:31:37
|
business trips in another country.
|
|
0:31:42
|
They just forwarded their phone to that person, cellphone let’s say,
|
|
0:31:45
|
and then they went home and they called their DID or
|
|
0:31:48
|
called in to the auto-attendant and ran to their extension
|
|
0:31:51
|
and it forwarded all calls onto that person’s international cellphone or mobile.
|
|
0:31:57
|
Well, that’s toll fraud. You're using the company’s dime to sit and talk to your
|
|
0:32:02
|
boyfriend or girlfriend for hours
|
|
0:32:04
|
after work hours or whatever.
|
|
0:32:08
|
There’s a lot of potential there for toll fraud.
|
|
0:32:10
|
It was always and still is always a good idea to
|
|
0:32:13
|
specifically set the calling search space for call forward all
|
|
0:32:20
|
regardless of whether there's actually anything filled in in the destination.
|
|
0:32:23
|
Because then when someone goes to press the soft key
|
|
0:32:26
|
for call forward all on their phone,
|
|
0:32:29
|
the one call forward option that almost everyone primarily has control over,
|
|
0:32:33
|
or you could take that away as well.
|
|
0:32:36
|
Then as they fill in digits, if that doesn’t
|
|
0:32:40
|
match, in other words if a pattern or DN doesn’t match
|
|
0:32:44
|
based on not being found in a directory
|
|
0:32:48
|
in your filing cabinet or not being found in a
|
|
0:32:50
|
partition within your calling search space
|
|
0:32:52
|
already configured on your call forward all
|
|
0:32:56
|
line page or CSS, then
|
|
0:33:00
|
you won’t be able to actually get reordered tone as you're
|
|
0:33:03
|
putting in your call forward all destination on your
|
|
0:33:06
|
on your actual phone. So that's a good idea.
|
|
0:33:10
|
to limit call forward all to begin with.
|
|
0:33:12
|
The problem was line device approach, if I just limit line
|
|
0:33:17
|
by using the line CSS, then
|
|
0:33:22
|
that only restricts, it doesn’t allow
|
|
0:33:24
|
But the device CSS allows everything.
|
|
0:33:27
|
So neither a good approach is. So in 6.x that’s where we actually had a
|
|
0:33:31
|
primary and a secondary calling search space for call forward all.
|
|
0:33:35
|
That way we can fill in our line and our device.
|
|
0:33:40
|
Line calling search space up top, device calling search space here.
|
|
0:33:44
|
This allows all calls to go through and goes to the proper gateway.
|
|
0:33:48
|
This restricts which of those allowed calls should not be.
|
|
0:33:52
|
So maybe restrict international but allow long distance and everything else.
|
|
0:33:56
|
On top of that, we actually have the calling search space activation policy.
|
|
0:34:00
|
By the way, these are two of the same screen shots that you see and then you see here.
|
|
0:34:06
|
I only captured in twice that way you could see the dropdown from the
|
|
0:34:12
|
calling search space activation policy. Otherwise, it
|
|
0:34:14
|
covers those two forward all primary and secondary CSS.
|
|
0:34:21
|
So the calling search space activation policy
|
|
0:34:24
|
is by default use system default, or I can say with
|
|
0:34:29
|
call configured CSS which is whatever I put here
|
|
0:34:33
|
and here or just here.
|
|
0:34:35
|
I can either have just the primary CSS if I want
|
|
0:34:39
|
or I can put both. That's the policy with configured CSS.
|
|
0:34:45
|
With activating device line CSS that says
|
|
0:34:50
|
forget about putting anything here just go ahead and use whatever
|
|
0:34:54
|
passive restriction and local gateways that I normally use in my line device
|
|
0:34:59
|
Go ahead and use that for my call forward all as well.
|
|
0:35:02
|
So, here we’re showing the configured call forward all and secondary are used
|
|
0:35:11
|
retty much what I just said without necessarily having
|
|
0:35:14
|
deactivating line device call forward primary and secondary
|
|
0:35:18
|
automatically get populated from the directory number
|
|
0:35:23
|
and use system default with configured as obviously.
|
|
0:35:26
|
Whatever you configure, use system default
|
|
0:35:29
|
is the cluster-wide service parameter
|
|
0:35:31
|
which determines what that will be.
|
|
0:35:36
|
Some more considerations blocking translation patterns
|
|
0:35:43
|
configured within a line, must be at least as specific
|
|
0:35:46
|
as the route patterns within the device. We already said that
|
|
0:35:49
|
but it’s good to reiterate it. If they happen to be less specific,
|
|
0:35:54
|
then most specific match, matching patterns will take effect
|
|
0:35:58
|
even if the partitions are ordered lower.
|
|
0:36:04
|
Particularly, watch for the @ wildcard.
|
|
0:36:07
|
That might sound like a very broad wildcard but believe it or not its
|
|
0:36:11
|
patterns are very very specific because it only works with route filters.
|
|
0:36:17
|
So, watch out for that @ wildcard.
|
|
0:36:21
|
It can actually be very specific.
|
|
0:36:25
|
AAR uses a different calling search space for rerouted calls.
|
|
0:36:30
|
In most cases, the CSS can be the same as the unrestricted
|
|
0:36:35
|
site-specific device CSS.
|
|
0:36:38
|
But in some cases this might not be desirable.
|
|
0:36:41
|
Does the activation call affect call forward all or does it affect
|
|
0:36:44
|
all of the other options as well?
|
|
0:36:50
|
All of the other options, meaning all of the other call forward options?
|
|
0:36:55
|
Yes, that is just for the call forward all. It does not
|
|
0:36:59
|
taken in consideration call forward busy, call forward no answer.
|
|
0:37:03
|
And the reason is, while those options can be
|
|
0:37:06
|
given to users to configure on their CUCM user page.
|
|
0:37:10
|
Most typically, if we’re them to the users, then we
|
|
0:37:13
|
already have a good degree of trust in them, but maybe not.
|
|
0:37:17
|
There’s probably certainly arguments we made while we might not
|
|
0:37:21
|
but normally those are configured by administrators.
|
|
0:37:25
|
And so a single CSS for that typically is sufficient.
|
|
0:37:32
|
And then this is something
|
|
0:37:33
|
very important to keep in mind which is that the priority order,
|
|
0:37:37
|
the ordering of the partitions within the
|
|
0:37:39
|
resulting concatenated CSS
|
|
0:37:41
|
between line and device, is actually reversed
|
|
0:37:45
|
for CTI route points and ports.
|
|
0:37:47
|
This is actually the way they all were. So device
|
|
0:37:49
|
partitions are ordered higher than the line partitions.
|
|
0:37:52
|
This is the way all devices were before call manager 3.1 and 3.0.
|
|
0:37:57
|
After 3.1 line became first and then device.
|
|
0:38:01
|
But for CTI, this is still backwards,
|
|
0:38:07
|
it has never been changed. And because it was never changed,
|
|
0:38:11
|
they were probably pretty hesitant to do it now because as you upgrade,
|
|
0:38:16
|
it can break a lot of existing large configurations.
|
|
0:38:20
|
So, if they reversed the order on you, you reversed it on them.
|
|
0:38:25
|
So in other words, for CTI route points and ports,
|
|
0:38:29
|
configure a line calling search space on the CTI device
|
|
0:38:34
|
page and configure the device CSS on the CTI line page.
|
|
0:38:40
|
So if they reverse it on you, you reverse it on them
|
|
0:38:43
|
and then you can still use the line device approach even on CTI ports and route points.
|
|
0:38:52
|
So, now let’s take a look at a new
|
|
0:38:57
|
function within 7.0. this is not in 6.x.
|
|
0:39:02
|
Within 7.0, we have this new idea of a local route group.
|
|
0:39:07
|
A local route group is also referred to as
|
|
0:39:09
|
a standard local route group whether you hear local route group
|
|
0:39:13
|
or standard local route group,
|
|
0:39:15
|
LRG or SLRG, they are the same things.
|
|
0:39:20
|
This is a dynamic entity
|
|
0:39:23
|
that is always even before you created
|
|
0:39:26
|
remember we talked about the configuration order, we configure our gateways
|
|
0:39:30
|
then we configure route groups and place the gateways and trunks in them.
|
|
0:39:33
|
Then we configure route list and put our route groups within them.
|
|
0:39:37
|
And then we create our route patterns and put
|
|
0:39:40
|
our route lists inside of them or point our route patterns
|
|
0:39:43
|
to the route list. We have to configure in the opposite direction.
|
|
0:39:46
|
Before we have even configured any route groups,
|
|
0:39:50
|
we can now configure a route list
|
|
0:39:52
|
and point it to something that always exists
|
|
0:39:56
|
in CUCM 7, always exists in the route list and that is the
|
|
0:40:00
|
standard local route group.
|
|
0:40:05
|
This is a dynamic entity. What this does,
|
|
0:40:09
|
in anytime somebody triggers,
|
|
0:40:11
|
the local or standard local route group,
|
|
0:40:14
|
it goes back to the calling party
|
|
0:40:18
|
and says, “Hey, what was your device for?”
|
|
0:40:21
|
and your device pool contains some valuable information for me
|
|
0:40:24
|
called your local route group.
|
|
0:40:26
|
Your local route group points to a specific
|
|
0:40:31
|
not just dynamic entity, but a specific entity
|
|
0:40:34
|
that I’ll use to replace myself
|
|
0:40:36
|
and that’s gonna contain whatever route group
|
|
0:40:38
|
you actually have configured it, so we still have to configure our route groups.
|
|
0:40:42
|
So let’s take a look. We still got the line device approach.
|
|
0:40:46
|
We still got a restricted and unrestricted CSS.
|
|
0:40:49
|
Restricted still points to blocked partition
|
|
0:40:52
|
and blocked patterns. Unrestricted still points to internal only
|
|
0:40:57
|
allowing and if we had couple others he assesses we just looked at.
|
|
0:41:02
|
But now, take a look at this.
|
|
0:41:06
|
As this call and this is actually for Seattle
|
|
0:41:09
|
phone. I forgot to note that this was a Seattle phone.
|
|
0:41:11
|
As that call goes through the one calling search space,
|
|
0:41:18
|
goes through the one pattern.
|
|
0:41:21
|
I'm only gonna have one set of patterns.
|
|
0:41:22
|
Remember before we set up, we had a thousand sites, we still needed 1000
|
|
0:41:27
|
patterns times the number of, well, types of patterns
|
|
0:41:32
|
times the number of sites, so if I had
|
|
0:41:36
|
a thousand sites and I have 1, 2, 3, 4, 5, 6 patterns, I would still need
|
|
0:41:44
|
6 patterns per site or 6000 patterns. Why?
|
|
0:41:49
|
Because the pattern points to the route list.
|
|
0:41:52
|
And I still need or needed 6000 route list
|
|
0:41:57
|
to point to each individual route group.
|
|
0:42:00
|
What if I have this dynamic entity here
|
|
0:42:02
|
which says spaced on who’s calling,
|
|
0:42:05
|
that’s how I’ll determine which route group to pick.
|
|
0:42:08
|
Now I can have, instead of 1000 route list, 1 for each site,
|
|
0:42:12
|
I guess I just said 6000 but instead of having
|
|
0:42:14
|
1000 route list, 1 for each site,
|
|
0:42:16
|
I can now have 1 route list.
|
|
0:42:19
|
One at least for a given country or numbering plan.
|
|
0:42:24
|
Now I realized that it won’t
|
|
0:42:26
|
completely simplify things as I’m about to do. In other words,
|
|
0:42:29
|
there will still be exceptions. You still have customers. You still have needs.
|
|
0:42:32
|
On the CCI voice exam, you still have reasons why
|
|
0:42:37
|
you very well may need to create multiple route list.
|
|
0:42:40
|
That being said, if I had a thousand sites,
|
|
0:42:46
|
and I still need to create a few different back up ones,
|
|
0:42:49
|
it’s gonna be a lot less to create maybe
|
|
0:42:52
|
50 or even a hundred route list for all the various
|
|
0:42:55
|
exceptions than it is to create a thousand or even if I have a
|
|
0:42:58
|
a hundred, maybe not a thousand sites, but a hundred sites.
|
|
0:43:02
|
Instead of creating a hundred route list, maybe I need 10 or 15.
|
|
0:43:05
|
But still an 80, 85,
|
|
0:43:09
|
90 percent savings depending on how many you still need.
|
|
0:43:14
|
Entities that I need to create.
|
|
0:43:16
|
Where I have a thousand sites and I had six patterns and I needed to create
|
|
0:43:19
|
six patterns times a thousand sites,
|
|
0:43:21
|
6000 patterns. I now need to create six patterns
|
|
0:43:24
|
for the entire North America.
|
|
0:43:29
|
So I have a tremendous savings.
|
|
0:43:32
|
So what happens to that call, let’s just watch the call go through again.
|
|
0:43:35
|
Call goes through 911. Hits the one route list,
|
|
0:43:39
|
hits the one dynamic entity called local route group.
|
|
0:43:43
|
That goes back to the calling parties device pool,
|
|
0:43:47
|
finds the local route group, takes that at replaces
|
|
0:43:52
|
itself with that actual explicitly configured route group, the Seattle route group
|
|
0:43:59
|
and it routes the call on to Seattle gateways.
|
|
0:44:05
|
Likewise, when an Austin phone dials through to 911, same pattern
|
|
0:44:11
|
same partition, same route list,
|
|
0:44:15
|
same dynamic entity of local route group,
|
|
0:44:19
|
local route group goes back to the calling party says what your device pool.
|
|
0:44:24
|
Inside up there, what’s your explicit route group,
|
|
0:44:27
|
I found that it’s the Austin route group
|
|
0:44:30
|
I’ll replace myself with that route group
|
|
0:44:33
|
and the call is routed out to the Austin gateways via the Austin route group.
|
|
0:44:39
|
So, let’s remember, we started with
|
|
0:44:42
|
N x C or sites x classes.
|
|
0:44:46
|
So a thousand sites x 4 classes was 4000 CSS.
|
|
0:44:50
|
And we started out with 6000 patterns,
|
|
0:44:55
|
thousand partitions and a thousand route lists and a thousand route groups.
|
|
0:45:00
|
So now, actually with the line device approach, we changed
|
|
0:45:06
|
1000 x 4 to 1000 + 4
|
|
0:45:10
|
and we took 4000 CSSs down to 1004 CSSs.
|
|
0:45:15
|
We still had 6000 patterns, a thousand partitions,
|
|
0:45:20
|
a thousand site-specific CSSs
|
|
0:45:24
|
that was 1000, of the 1004. Four for the restricted block,
|
|
0:45:29
|
a thousand route list and a thousand route groups.
|
|
0:45:32
|
With line device approach,
|
|
0:45:35
|
it’s no longer sites x classes,
|
|
0:45:38
|
it’s country or dialling + classes.
|
|
0:45:44
|
So we have one here, we only have one country or one dialling plan
|
|
0:45:49
|
lus two classes of restrictions or actually
|
|
0:45:53
|
I forgot, I was using four as the example
|
|
0:45:56
|
this two still reflects here. So 1 + 2 does not equal 5
|
|
0:46:00
|
It's a typo. But with four classes
|
|
0:46:03
|
and one country, I know have five calling search spaces total.
|
|
0:46:09
|
Well actually you know I’d have four blocked partitions,
|
|
0:46:14
|
actually three blocked partitions plus my internal plus my
|
|
0:46:20
|
PSTN partitions. So I have 5 partitions.
|
|
0:46:23
|
Instead of 6000 patterns, I have 6 patterns.
|
|
0:46:26
|
Instead of a thousand route list, I have one route list.
|
|
0:46:29
|
But one thing I still do have to have is
|
|
0:46:32
|
at least one route group for earch site.
|
|
0:46:36
|
So if I have a thousand site, I still have 1000 route groups.
|
|
0:46:39
|
And those route groups I place inside the device pool.
|
|
0:46:42
|
I no longer give them directly to a route list, but I place them inside
|
|
0:46:48
|
of the device pool because the standard local route group dynamic entity
|
|
0:46:52
|
will go back to the calling parties device pool.
|
|
0:46:57
|
Whoever picked up the phone and placed the call
|
|
0:47:00
|
and looked to its local route group
|
|
0:47:04
|
so to try to find a replacement for itself
|
|
0:47:07
|
to know where to route the call.
|
|
0:47:10
|
So we’re just talking about 4000
|
|
0:47:12
|
CSSs, roughly 4000 CSSs that we’ve saved
|
|
0:47:17
|
but we didn’t add any yet 6000 patterns,
|
|
0:47:21
|
4000 partitions or 3099.
|
|
0:47:25
|
So that’s 10000 + 1000 route list
|
|
0:47:33
|
Sorry 1000 partitions, one for each site. So that’s 6, 7, 8000
|
|
0:47:39
|
ntities plus the 4000. We've now saved almost 12000 entities
|
|
0:47:44
|
on a thousand site cluster.
|
|
0:47:50
|
Tremendous amount of savings in terms of
|
|
0:47:54
|
configuration, troubleshooting, scalability.
|
|
0:47:58
|
If I wanna add more sites, all I do is create a route group,
|
|
0:48:02
|
and add it to the device pool. That’s it.
|
|
0:48:05
|
Everyone’s as long as it’s within the same country,
|
|
0:48:07
|
everyone still points to the same partition.
|
|
0:48:12
|
Now there are gonna be some exceptions, what if I wanna have back up gateways?
|
|
0:48:16
|
So let’s take a look at that. And this is actually our last slide.
|
|
0:48:21
|
And then we’re going to configuration. So, here,
|
|
0:48:24
|
I’ve got still my Seattle phone and my Austin phone.
|
|
0:48:28
|
And they're still going to point to the one calling search space
|
|
0:48:32
|
but certain patterns are pointing towards, let's say 911, 9911 and local.
|
|
0:48:41
|
We still want those to point to our local
|
|
0:48:44
|
route list which only points to standard local groups.
|
|
0:48:48
|
So maybe the first call goes through.
|
|
0:48:50
|
You know what, I didn’t have one for the first call.
|
|
0:48:52
|
The first call goes through from Seattle and dials 911 for emergency
|
|
0:48:58
|
routes out the local only route list which only routes the local route group,
|
|
0:49:02
|
goes back, looks at his device pool
|
|
0:49:04
|
finds up a local route group, replaces it with itself
|
|
0:49:08
|
and sends it to the Seattle gateway. That still happens normally.
|
|
0:49:12
|
But now the Austin phone, wants to send the call either
|
|
0:49:16
|
long distance or international. I think it’s long distance here.
|
|
0:49:20
|
I guess it’s the Seattle phone, sorry.
|
|
0:49:22
|
Seattle phone wants to send it to international.
|
|
0:49:27
|
So we have those patterns pointing to a different route list
|
|
0:49:32
|
and that route list has a first preference
|
|
0:49:35
|
of explicitly-configured headquarter gateways,
|
|
0:49:39
|
So there’s gonna be a need to be
|
|
0:49:40
|
some form of digit manipulation to make sure they route properly.
|
|
0:49:45
|
But they're going to always if those set of those set of gateways is available.
|
|
0:49:51
|
For long distance international calls,
|
|
0:49:54
|
they're always gonna route up to the headquarter gateways first.
|
|
0:49:57
|
Because maybe our headquarter is Seattle, who knows?
|
|
0:50:00
|
But our headquarter has, you know, we've got 12 PRI’s and we've got some
|
|
0:50:06
|
great rates and negotiate with the carrier.
|
|
0:50:10
|
So we want our calls to route across the WANout here first.
|
|
0:50:14
|
But then maybe the WAN’s down. So if the WAN’s down
|
|
0:50:19
|
then we’re going to choose our second option
|
|
0:50:22
|
which will route to standard local route group.
|
|
0:50:25
|
And then we still have site-specific local fail over
|
|
0:50:31
|
for each of the 1000 sites.
|
|
0:50:34
|
For all the 1000 sites, long distance and international,
|
|
0:50:36
|
always right across the WAN up to headquarters,
|
|
0:50:38
|
But in the case that the WAN’s down. I guess if the WAN's down then
|
|
0:50:42
|
maybe the call volume is full or one of the gateways is down
|
|
0:50:45
|
The WAN’s down on an SRST mode probably
|
|
0:50:48
|
unless we had a distributed cluster which is possible as well.
|
|
0:50:51
|
Maybe that route is isn’t available for whatever reason
|
|
0:50:55
|
trunks are full and so we all fail over to our site-specific
|
|
0:51:01
|
local route group based on this dynamic standard local route group entity.
|
|
0:51:08
|
So, you asked and stated earlier, was that the best
|
|
0:51:15
|
deployment going forward and you were referring to the line device approach.
|
|
0:51:19
|
And I would say that now if you were working on a 7.0 cluster or later
|
|
0:51:24
|
that the best deployment is line device approach with local route group
|
|
0:51:31
|
and some variations thereof. So, you're going to probably need
|
|
0:51:38
|
to have some different back up
|
|
0:51:43
|
We’ll definitely talk about T-Ho a little later.
|
|
0:51:48
|
David, you asked about T-Ho, you said for T-Ho, would we just
|
|
0:51:52
|
create route list for those area codes and gateways.
|
|
0:51:56
|
We’re actually not gonna talk about T-Ho today
|
|
0:51:59
|
or AAR or call forward unregister
|
|
0:52:03
|
or single number reach or
|
|
0:52:06
|
device mobility or extension mobility or SRST.
|
|
0:52:10
|
All things that are very potentially
|
|
0:52:14
|
impacting or very potentially impacted with local route group.
|
|
0:52:19
|
And the reason we’re not going to talk about them today
|
|
0:52:22
|
is because, we’re gonna get in to our configuration here next.
|
|
0:52:25
|
And make sure that everything’s solid on the fundamentals because
|
|
0:52:28
|
once we introduced globalization and localization tomorrow
|
|
0:52:33
|
If went ahead and talked about all of those things that I just mentioned
|
|
0:52:37
|
AAR, THO, all of that. I wouldn't talk about them today.
|
|
0:52:41
|
We will just basically have to forget everything that we look at
|
|
0:52:44
|
because there will be a lot of digit manipulation depending on
|
|
0:52:48
|
am I crossing, area code boundaries within a country.
|
|
0:52:52
|
So, city boundaries, am I crossing boundaries?
|
|
0:52:56
|
There’s a lot of different digit manipulations, things we’ll have to look at.
|
|
0:52:59
|
What we’ll see tomorrow is that globalization and localization is going too
|
|
0:53:04
|
so drastically simplified all of that that
|
|
0:53:09
|
it’s really not worth going in to today.
|
|
0:53:16
|
But you would, if you we’re looking at justice with local route group
|
|
0:53:21
|
which is a feature of 7, you’re using this
|
|
0:53:26
|
we'll also go ahead use the other features of 7 being globalization and localization.
|
|
0:53:29
|
But if you were just using this, you would create
|
|
0:53:33
|
specific route list that had particularly
|
|
0:53:37
|
the areas and the gateways that you wanted to
|
|
0:53:40
|
do the HAPA and you have to form that digit manipulation.
|
|
0:53:46
|
This is also one of the reasons
|
|
0:53:48
|
why before, I think this is the last slide, we get in to our
|
|
0:53:53
|
tasks for today. This is also the reason that
|
|
0:53:58
|
calling party and called party transformation CSS
|
|
0:54:03
|
out at the gateway level. So,
|
|
0:54:06
|
still in CUCM webpage but the gateway or trunk
|
|
0:54:10
|
for the, within CUCM, why we now have in 7.0
|
|
0:54:18
|
calling and calling party transformation in CSS there. Because think about it,
|
|
0:54:23
|
earlier when we were saying that we could do digit manipulation
|
|
0:54:26
|
at the route pattern level, right?
|
|
0:54:30
|
We could also do it at the route list details.
|
|
0:54:34
|
That was the route group within the route list.
|
|
0:54:36
|
That was the second place we could do it.
|
|
0:54:39
|
If we could just do in those two places, think about what will happen?
|
|
0:54:45
|
I might want certain, let’s say, calling party numbers.
|
|
0:54:51
|
Actually, let's even just look at called party numbers.
|
|
0:54:54
|
What if I wanted, here I only show lond distance and international
|
|
0:54:58
|
routing out this, route list that sends it up to
|
|
0:55:02
|
a specific headquarter
|
|
0:55:04
|
route group before going to local. Those might not have to be
|
|
0:55:08
|
changed too much in their digit manipulation, just drop pre-dot and you're fine.
|
|
0:55:13
|
What about local dialing and 7-digit local dialing?
|
|
0:55:18
|
If I send this seven digit local dialing
|
|
0:55:21
|
out a route list that first goes up to a route group
|
|
0:55:26
|
per headquarter gateways, I might have to do some
|
|
0:55:31
|
form of digit manipulation to prefix
|
|
0:55:35
|
whatever area code they were trying to dial out of
|
|
0:55:42
|
and also add on based on the route pattern
|
|
0:55:51
|
on for national access code, the area code they were trying to dial
|
|
0:55:56
|
things of that nature. Now we can fix this with 10-digit dialing.
|
|
0:56:00
|
or local calls, I realized that but there still might need to be some
|
|
0:56:04
|
variations of called party, also calling party.
|
|
0:56:08
|
Maybe I want my calling party number to look one way.
|
|
0:56:10
|
If I do it at the route pattern, and don't do it anywhere else,
|
|
0:56:14
|
and it's gonna take effect for not only Seattle phones but
|
|
0:56:17
|
all other site's phones. What about if I do it at the route list
|
|
0:56:22
|
details? Route group within a route list?
|
|
0:56:24
|
By the way you can do digit manipulation for standard local route group
|
|
0:56:29
|
as part of the route list so the route list details or standard local route group.
|
|
0:56:33
|
But again, this is going to take effect for
|
|
0:56:36
|
every sites calling party
|
|
0:56:40
|
that traverses through this single set of patterns and route list details.
|
|
0:56:47
|
We probably don't want to uniformly impact everyone on the same fashion.
|
|
0:56:51
|
We probably want to impact them based on where they come from.
|
|
0:56:56
|
So now, depending on where they're leaving, the egress point
|
|
0:57:02
|
out to the PSTN, the gateway, we can say, based on whoever you were
|
|
0:57:08
|
calling party, we'll match your calling party number
|
|
0:57:12
|
and once we match specific numbers then we'll only
|
|
0:57:16
|
transform those calling party numbers when they leave our gateway.
|
|
0:57:20
|
So not even, just everyone that leaves our gateway, but only maybe say
|
|
0:57:25
|
maybe this is a 2000 series set of DNs at Austin.
|
|
0:57:31
|
And a 1000 series set of DNs at Seattle.
|
|
0:57:35
|
So we would match, let's say we wanted to transform Austin but not Seattle,
|
|
0:57:40
|
if we did it at the route pattern, transforms everyone.
|
|
0:57:43
|
If we do it at the route list details, transforms everyone.
|
|
0:57:47
|
Why? Because we don't have patterns for each site anymore.
|
|
0:57:50
|
We don't have route list for each site anymore.
|
|
0:57:53
|
So instead of the gateways, I can say
|
|
0:57:57
|
Set up a new CSS that only has one partition in it
|
|
0:58:02
|
and we'll name it intuitively and that partition
|
|
0:58:06
|
should only be applied to a single pattern
|
|
0:58:11
|
that is a calling party transformation pattern
|
|
0:58:14
|
and that matches the 2000 series set of numbers.
|
|
0:58:19
|
Austin numbers. So the pattern would be 2XXX
|
|
0:58:23
|
in a partition for Seattle gateways calling or ANI
|
|
0:58:31
|
only visible by the Seattle gateways ANI CSS
|
|
0:58:36
|
And then we will only have our match, people that leave Seattle but come from Austin
|
|
0:58:43
|
and we'll manipulate their calling party number in a very specific way.
|
|
0:58:50
|
This is one of the complexities of having to think about
|
|
0:58:54
|
matchin the actual pattern for called or calling, again
|
|
0:59:02
|
but we also get a very fine granular
|
|
0:59:07
|
detailed level of control because we're so
|
|
0:59:11
|
we're muddying the waters. We're making the patterns
|
|
0:59:16
|
you pick with us, we're making them ambiguous.
|
|
0:59:19
|
We're making the route list ambiguous.
|
|
0:59:21
|
It doesn't really matter who accesses them anymore.
|
|
0:59:24
|
as long as they're from the same numbering plan,
|
|
0:59:27
|
the same dialing habits, the same country typically.
|
|
0:59:41
|
There was the route back from the second
|
|
0:59:44
|
choice, the local route group goes back
|
|
0:59:46
|
to the device pool and found the Seattle gateways.
|
|
0:59:49
|
We have more, one more quiz I put together. So,
|
|
0:59:54
|
with the advent of standard local route groups,
|
|
0:59:57
|
is the line device approach
|
|
0:59:59
|
the calling search space's assignment is still necessary.
|
|
1:00:02
|
Let's go back and look at this.
|
|
1:00:05
|
What was our reason for having
|
|
1:00:07
|
the line device approach restricted up here?
|
|
1:00:10
|
What was the reason for splitting out
|
|
1:00:13
|
lines CSSs which
|
|
1:00:16
|
denoted class of service or class of restriction
|
|
1:00:20
|
versus device calling search spaces which denoted the
|
|
1:00:24
|
half selection or site specific call routing
|
|
1:00:29
|
the reason was, we had a thousand sites, so we had a thousand CSSs
|
|
1:00:34
|
and we had four class of restrictions, right? But now,
|
|
1:00:40
|
we effectively only have one site
|
|
1:00:43
|
because local route group allows one CSS
|
|
1:00:46
|
to point to one partition with all the patterns
|
|
1:00:50
|
go out one route list and then it decides
|
|
1:00:53
|
where the call should go based on who was the calling party.
|
|
1:00:57
|
So we don't need a thousand CSSs here anymore.
|
|
1:01:00
|
So could we not just have four CSSs
|
|
1:01:05
|
kindly go back to the traditional approach and those 4 CSSs were
|
|
1:01:12
|
were class of restrtiction specific
|
|
1:01:14
|
So, or class of service specific if
|
|
1:01:17
|
wanna be inclusive versus exclusive
|
|
1:01:21
|
We had one for CSS allow long distance
|
|
1:01:24
|
One for CSS allow international
|
|
1:01:26
|
One for CSS allow local
|
|
1:01:29
|
One for CSS allow restricted.
|
|
1:01:32
|
Internal and emergency and then not do anything on the line.
|
|
1:01:37
|
Well, for this simple illustration that we have here
|
|
1:01:41
|
and believe or not this is very simple compared to
|
|
1:01:45
|
some of the things we can talk about and get into, technically,
|
|
1:01:50
|
we don't need it. See, it's still considered best practice
|
|
1:01:55
|
and some things don't use local route group.
|
|
1:01:57
|
There are definitely some things that were probably not going to want to
|
|
1:02:02
|
setup with local route group. What if we don't
|
|
1:02:04
|
you know, what if certain set certain phones that never use local route
|
|
1:02:08
|
you know, probably everyone should route to their own
|
|
1:02:12
|
call at some point but they're very well maybe
|
|
1:02:15
|
and as people are moving and
|
|
1:02:20
|
upgrading their clusters to 7.0
|
|
1:02:24
|
some people that I know are going from 6
|
|
1:02:28
|
whether upgrading through 7 or not, they're ultimately going to 8
|
|
1:02:33
|
but, they are certainly a lot of people that are not yet
|
|
1:02:37
|
if not most people that have not yet found or deploy the power of local route groups
|
|
1:02:42
|
and remember for those that do have a large number of clusters
|
|
1:02:47
|
What if we had one cluster with a large number of sites or a large number of sites
|
|
1:02:51
|
distributed across multiple clusters, you probably have
|
|
1:02:55
|
already move to the line device approach long long ago
|
|
1:03:00
|
and you've already got everything set up, local route group sounds great
|
|
1:03:04
|
but you're not yet ready to go and redesign everything just to have savings
|
|
1:03:09
|
that wouldn't be savings because you've already configured everything
|
|
1:03:12
|
moving forward, you might design with that in mind
|
|
1:03:15
|
but all of your existing will actually take a lot of work
|
|
1:03:18
|
to move away from. So,
|
|
1:03:21
|
you should definitely still use the line device approach
|
|
1:03:25
|
but as you begin new greenfield deployments, new designs
|
|
1:03:30
|
certainly thinking about it in terms of the CCIE voice lab practical exam
|
|
1:03:37
|
or even upgrading and adding on to your cluster
|
|
1:03:41
|
then begin factoring in the local route groups
|
|
1:03:45
|
but you should definitely still use the line device approach.
|
|
1:03:48
|
If you're only using local route groups and you have a very simple
|
|
1:03:52
|
deployment as we showed on the last
|
|
1:03:55
|
or very simple plan we showed on the last slide
|
|
1:03:59
|
It could potentially not be necessary
|
|
1:04:03
|
is still best practice.
|
