|
0:00:13
|
Ok, so let's come back from break and if you will
|
|
0:00:15
|
recall, we had just previously globalized all the calling party
|
|
0:00:20
|
numbers inbound from PSTN calls and now we need to take
|
|
0:00:26
|
a look at localizing those calling party numbers as per the
|
|
0:00:31
|
requirements of in our case a CCIE Lab exam or even in
|
|
0:00:37
|
real life however the local users or really the company
|
|
0:00:40
|
policy dictated that they wanted to see those numbers
|
|
0:00:43
|
localized for each format for subscriber or local.
|
|
0:00:46
|
for national and for international calls.
|
|
0:00:51
|
And we had previously localized outbound PSTN called party
|
|
0:00:59
|
or dnis with called party transformation patterns
|
|
0:01:04
|
and we will likewise localize calling party numbers
|
|
0:01:10
|
for inbound PSTN calling, so ANI
|
|
0:01:19
|
So called and calling party transformation when it applies
|
|
0:01:23
|
to localization, always is at -- if you recall, always is at
|
|
0:01:26
|
the egress, so the called party transformation pattern
|
|
0:01:30
|
was at the egress which was the gateway and
|
|
0:01:34
|
the calling party transformation for localization is at the egress
|
|
0:01:41
|
in this case, so a call's coming in from the PSTN. It comes in
|
|
0:01:46
|
from a gateway and it goes out or egress to a phone.
|
|
0:01:50
|
So it's on these phones
|
|
0:01:56
|
that we need to apply and I'll just grab one phone
|
|
0:01:58
|
for right now
|
|
0:02:03
|
that we need to apply if we scroll down to the bottom
|
|
0:02:06
|
of this section, a calling party transformation CSS
|
|
0:02:11
|
and again we can use device pool.
|
|
0:02:13
|
No problem aggregating these variables or parameters
|
|
0:02:18
|
at the device pool; however, right now our device pools
|
|
0:02:22
|
we only have one per site except for MOH
|
|
0:02:25
|
and those device pools are shared between gateways
|
|
0:02:31
|
and phones. In a production network I wouldn't do that.
|
|
0:02:33
|
But for the simplicity of the lab, we do or at least you can.
|
|
0:02:38
|
And so I'm not going to do anything regarding calling or
|
|
0:02:41
|
called party transformation CSS at the device pool level
|
|
0:02:46
|
I'll instead just do it at the phone.
|
|
0:02:48
|
Now you might say, 'Will I have to go into every single phone and do that?'
|
|
0:02:51
|
But that's not necessarily the case because we have BAT
|
|
0:02:55
|
so I'm going to do Bulk update for phones
|
|
0:02:58
|
based on a query and all directory numbers that
|
|
0:03:02
|
begin with one. We're not updating lines, but we can
|
|
0:03:05
|
use directory number as a search criteria for the phones
|
|
0:03:07
|
that are contained therein and this is actually only two phones.
|
|
0:03:14
|
Restart them when they're done.
|
|
0:03:19
|
Look down not to calling search space or AAR, but
|
|
0:03:22
|
calling party transformation calling search space
|
|
0:03:25
|
and I'm going to -- or CSS is it's actually typically referred to now
|
|
0:03:30
|
because it's not necessarily the word calling in the calling
|
|
0:03:36
|
party -- I'm sorry, the word calling in calling search space
|
|
0:03:40
|
or CSS doesn't always refer to calling anymore, so
|
|
0:03:44
|
anyway, a lot of people just refer to it as CSS. I think at some point
|
|
0:03:48
|
it would make sense to change it to search space
|
|
0:03:50
|
like unity connection uses,
|
|
0:03:54
|
but for now -- so we will apply to the corporate headquarter
|
|
0:03:59
|
phones the CSS for CNG PTP corporate headquarter phones.
|
|
0:04:05
|
Scroll all the way down and run immediately.
|
|
0:04:09
|
And then for phones whose directory number begins with two.
|
|
0:04:19
|
I personally think it's faster to use BAT even to update one phone
|
|
0:04:22
|
because you can restart and everything
|
|
0:04:26
|
all within one page
|
|
0:04:34
|
faster than it is to go to the actual phone page.
|
|
0:04:36
|
And directory numbers that begin with three
|
|
0:04:40
|
so we'll see four phones, but it's really only two actual Mac
|
|
0:04:43
|
addresses, two physical phones.
|
|
0:04:47
|
Restart after application.
|
|
0:04:50
|
Change calling party transformation CSS
|
|
0:04:53
|
to Branch 2 CSS
|
|
0:04:55
|
CNG PTP Branch 2 phones run immediately.
|
|
0:05:00
|
So now we've applied to the egress
|
|
0:05:03
|
inbound from the PSTN, egress to the phones.
|
|
0:05:07
|
We've applied their calling party transformation CSS
|
|
0:05:11
|
so that they can find the patterns.
|
|
0:05:13
|
Now I went to called party a little bit earlier because I wanted to
|
|
0:05:17
|
show you that if you see -- if you take a look and see these
|
|
0:05:23
|
patterns, while we're not going to put them in the same partition
|
|
0:05:27
|
and you definitely don't want to because these called and calling
|
|
0:05:30
|
can actually overlap based on partition.
|
|
0:05:33
|
Remember anything with a pattern can be matched by
|
|
0:05:36
|
anything with a CSS, but the patterns themselves, not the digit
|
|
0:05:42
|
manipulation, not the partition, but the patterns themselves
|
|
0:05:45
|
other than the emergency services one
|
|
0:05:48
|
the international, national, so international one for each country
|
|
0:05:54
|
national one for each country
|
|
0:05:57
|
and potentially local if there's a difference. Again, certain countries'
|
|
0:06:03
|
national and local will be fairly similar if not maybe the same.
|
|
0:06:08
|
But actually -- yeah, no for even local we may want them
|
|
0:06:12
|
to be displayed in a similar fashion is all I'm saying
|
|
0:06:19
|
the national and local we may not, but either way all these patterns are
|
|
0:06:22
|
going to be almost the exact same patterns that we used in
|
|
0:06:25
|
our calling party.
|
|
0:06:27
|
Why? Because we've globalized the calling number. We've still
|
|
0:06:31
|
globalized it which means it's now in a plus country code format.
|
|
0:06:37
|
So let's just begin.
|
|
0:06:38
|
Let's create for the corporate headquarter site at first
|
|
0:06:43
|
an international pattern.
|
|
0:06:45
|
And remember, this is where if we were using an aggregate
|
|
0:06:48
|
partition for the entire country like instead of partition calling
|
|
0:06:56
|
PTP for corporate headquarter and Branch 1, we also had one
|
|
0:07:02
|
for partition calling PTP for US phones and then
|
|
0:07:06
|
those two patterns that went into those US phones
|
|
0:07:11
|
calling PTPs ended up being a part of the calling search space
|
|
0:07:16
|
for every phone within that site.
|
|
0:07:19
|
Ok, we kept it a little bit more simple
|
|
0:07:22
|
in terms of the CSS and the partitions that we're creating
|
|
0:07:26
|
and their structure. It's a one for one an so we do need to
|
|
0:07:29
|
create duplicate national and international patterns,
|
|
0:07:32
|
but in real life we wouldn't need to.
|
|
0:07:34
|
And in fact, if you want to see that other where we only create
|
|
0:07:38
|
the ones for national and international, the deep dives
|
|
0:07:42
|
reflect that tiny bit more advanced config.
|
|
0:07:46
|
Ok, so pattern plus. We know that we're going to be matching
|
|
0:07:50
|
plus. We have to escape it with a backslash.
|
|
0:07:53
|
And actually one other note, I mentioned that if you don't put
|
|
0:07:56
|
in a backslash, the web page yells at you, it gives you an error
|
|
0:08:00
|
and says, 'The first character cannot be a plus.'
|
|
0:08:02
|
There's actually a bug in 7.0.1
|
|
0:08:06
|
CUCM that one of the two, I can't remember whether it's calling
|
|
0:08:10
|
or called, if you omit the backslash it actually doesn't get you --
|
|
0:08:15
|
give you an error.
|
|
0:08:16
|
Let me just test to see if it's this one.
|
|
0:08:19
|
Nope, it is not this one.
|
|
0:08:22
|
It must be called.
|
|
0:08:24
|
So if I create a new called pattern and it is +! for instance
|
|
0:08:33
|
Yeah, it doesn't actually give you an error.
|
|
0:08:35
|
That's a bug that it doesn't give you the error
|
|
0:08:38
|
because that in fact will not match anything because
|
|
0:08:42
|
it's a regular expression.
|
|
0:08:45
|
Those are all still there. It's not really zero records found.
|
|
0:08:48
|
That's another bug.
|
|
0:08:50
|
Ok, so anyway let's create our calling party.
|
|
0:08:57
|
\+ and we're going to do all international calls
|
|
0:09:02
|
for the US, so let's do .! and we want them to be
|
|
0:09:08
|
in the corporate headquarter calling party transformation
|
|
0:09:12
|
pattern partition.
|
|
0:09:15
|
And there is no calling party external phone number mask
|
|
0:09:17
|
they're coming from the PSTN.
|
|
0:09:20
|
We want to let's say discard predot and maybe
|
|
0:09:24
|
we want them to show up with a 011
|
|
0:09:27
|
Ok, whatever you're instructions or lab exam requirements
|
|
0:09:33
|
or clients tell you.
|
|
0:09:37
|
Ok, before we go any further, let's just test that real quick.
|
|
0:09:40
|
So if we have a corporate headquarter phone
|
|
0:09:44
|
and a call comes in from the PSTN
|
|
0:09:47
|
from an international number
|
|
0:09:50
|
then it needs to display as 011 and then country code.
|
|
0:09:59
|
So try calling in from
|
|
0:10:03
|
whoops
|
|
0:10:04
|
not line 2, but line 3
|
|
0:10:07
|
so the Amsterdam line and let's dial the digits.
|
|
0:10:18
|
And we see that this call -- whoops
|
|
0:10:20
|
has not come in properly yet, ok.
|
|
0:10:24
|
So let's take a look. Add was successful, match is \+.!
|
|
0:10:32
|
drops predot.
|
|
0:10:34
|
Ok, let's just do a save.
|
|
0:10:37
|
And go back out and make sure that it is in the database.
|
|
0:10:42
|
Ok, let's just make sure our CSS has the PTP.
|
|
0:10:49
|
So the CSS for calling party transformation pattern
|
|
0:10:55
|
headquarter phones has the partition for calling party.
|
|
0:10:58
|
Good.
|
|
0:11:00
|
Let's go to our phone. Make sure that BAT did its job
|
|
0:11:04
|
by updating these phones properly.
|
|
0:11:11
|
Ah! In the Bulk Administration tool, I forgot to uncheck
|
|
0:11:17
|
use device pool calling party transformation CSS
|
|
0:11:20
|
and this is actually something that overrides this field.
|
|
0:11:23
|
So in all my phones I need to go back and do an update
|
|
0:11:27
|
query and this time I'm going to grab all phones.
|
|
0:11:30
|
They have their proper CSS, but I just need to tell all five of them
|
|
0:11:36
|
to restart once.
|
|
0:11:40
|
They change this field and the field is to untick that box.
|
|
0:11:46
|
Run immediately.
|
|
0:11:48
|
Go.
|
|
0:11:54
|
So we'll wait until this phone restarts.
|
|
0:11:58
|
Here it goes.
|
|
0:12:05
|
And the phone's restarted. The screen will update here.
|
|
0:12:09
|
So let's go ahead and dial that number back in.
|
|
0:12:17
|
And this time we should see the phone
|
|
0:12:22
|
Ah! We just see it as 011
|
|
0:12:24
|
Alright
|
|
0:12:26
|
so let's take a look at what we did
|
|
0:12:29
|
in the calling party transformation pattern.
|
|
0:12:32
|
Fairly certain I know what I did wrong.
|
|
0:12:36
|
And that was I put it in the mask field rather than the
|
|
0:12:40
|
prefix field, so I essentially said whatever it was
|
|
0:12:44
|
not only strip the plus, but replace everything else with
|
|
0:12:46
|
011 rather than saying prefix it.
|
|
0:12:49
|
So let's just click save.
|
|
0:12:54
|
And now if I
|
|
0:12:57
|
dial this number again
|
|
0:13:01
|
I should just hit redial from now on, so it doesn't pulse.
|
|
0:13:06
|
Yep, here we go.
|
|
0:13:11
|
Now we see 01131207037333
|
|
0:13:18
|
Ok,
|
|
0:13:22
|
so we stripped the plus and we prefixed a 011
|
|
0:13:26
|
We localized it to the phone for the calling number
|
|
0:13:29
|
however we were told or wanted to see it.
|
|
0:13:32
|
If I go to directory
|
|
0:13:36
|
and missed calls
|
|
0:13:42
|
then we will see that the number still came in all of these times
|
|
0:13:48
|
even when it was displayed in position two as just 011
|
|
0:13:52
|
displayed this last time position one as 01131
|
|
0:13:57
|
and the rest of the digits, it always shows in the globalized format.
|
|
0:14:00
|
But the localized is what shows on the display.
|
|
0:14:05
|
Ok, so let's go ahead and propagate this on out.
|
|
0:14:09
|
So let's create the same pattern for Branch 1
|
|
0:14:21
|
Whoops I did it under called party. I meant to do it under
|
|
0:14:23
|
Branch 1 calling party for phones.
|
|
0:14:27
|
And the reason it said there was a similar pattern
|
|
0:14:29
|
or same pattern actually is because there is a called party.
|
|
0:14:32
|
Remember patterns are just patterns. They might have a different interface
|
|
0:14:36
|
here in CUCM, but they're still just patterns.
|
|
0:14:41
|
Ok, so let's also copy that.
|
|
0:14:48
|
And make it for Branch 2 calling party.
|
|
0:14:52
|
But we're going to drop the predot and for Branch 2
|
|
0:14:59
|
maybe we're going to add a double zero.
|
|
0:15:05
|
Ok, so we've now got one international calling party
|
|
0:15:09
|
transformation pattern for each site.
|
|
0:15:12
|
So let's go back into our corporate headquarter one
|
|
0:15:15
|
and copy this and add in what we would need for US
|
|
0:15:21
|
So for US let's make it so that it shows -- let's leave the 1
|
|
0:15:28
|
so the dot is going to be in between the plus, we're still stripping the plus.
|
|
0:15:33
|
But we want it to show the 1 which actually -- yeah, that's
|
|
0:15:38
|
that's going to be what we want, but instead of the prefix
|
|
0:15:41
|
of 011, we don't want that. We just want it to drop the plus.
|
|
0:15:47
|
Now, again why would we include the 1?
|
|
0:15:51
|
Well, because if we didn't, it would actually be the same pattern as our international
|
|
0:15:54
|
and including the 1 is also more specific
|
|
0:15:59
|
because it has a different transformation.
|
|
0:16:02
|
Let's go ahead and copy this to our Branch 1
|
|
0:16:06
|
and leave that the same and again we could have both the
|
|
0:16:09
|
national +1 and the international plus patterns in a partition for the
|
|
0:16:16
|
whole country that was visible to both phones' CSSs
|
|
0:16:21
|
Ok, we'll also copy this.
|
|
0:16:24
|
And we'll change the country code to +31
|
|
0:16:27
|
for Branch 2 phones calling party transformation pattern
|
|
0:16:31
|
and we don't want to keep the 31, so I'm actually going to
|
|
0:16:37
|
move the dot over here and I want to prefix back
|
|
0:16:42
|
in the zero, so users are expecting to see let's see
|
|
0:16:45
|
let's say 020 or -- actually 020 would be local, so 010
|
|
0:16:53
|
So they're expecting to see that. It had been stripped because
|
|
0:16:57
|
the E.164 number doesn't contain it.
|
|
0:17:03
|
So let's go back and take a look.
|
|
0:17:05
|
So now I've got three patterns for international one for each site
|
|
0:17:09
|
three patterns for national one for each site.
|
|
0:17:12
|
And so let's go back into corporate headquarters.
|
|
0:17:15
|
Copy this.
|
|
0:17:18
|
And this time we're going to move the dot over and
|
|
0:17:21
|
make this more specific 206
|
|
0:17:24
|
and again we're just going to drop predot, so this time
|
|
0:17:27
|
we won't have a one displang, we'll only have a 206
|
|
0:17:30
|
Now, I can do anything I want. I could prefix a 9, I could show
|
|
0:17:36
|
everyone all globalized numbers, plus numbers. Whatever the
|
|
0:17:41
|
lab tells you or whatever your client says is their request
|
|
0:17:45
|
we can do it. It's not a problem.
|
|
0:17:48
|
I'm going to copy this and I'm going to change the
|
|
0:17:52
|
city code to 512
|
|
0:17:55
|
and change this to Branch 1
|
|
0:18:00
|
and then I'm going to copy this again.
|
|
0:18:06
|
And change this the country code 31 and the city code 20
|
|
0:18:12
|
and I'm going to change the position of the dot so that
|
|
0:18:15
|
Amsterdam phones only see seven digits when --
|
|
0:18:20
|
if I change the partition to the proper partition
|
|
0:18:22
|
when the call is coming from a calling number of 20
|
|
0:18:29
|
which is the city code for Amsterdam.
|
|
0:18:33
|
Ok, so add successful.
|
|
0:18:35
|
Make sure I did my copies
|
|
0:18:37
|
Ok, so I've got my national
|
|
0:18:43
|
and two nationals, there we go and then I've got my two
|
|
0:18:46
|
whoops
|
|
0:18:47
|
my two city codes for corporate headquarter and Branch 1
|
|
0:18:50
|
and city code for Branch 2
|
|
0:18:53
|
Ok, so that was easy. Let's go ahead and test a few things.
|
|
0:19:03
|
So let's test...
|
|
0:19:09
|
Let's just minimize that.
|
|
0:19:12
|
Let's test calling into let's say 0207033002
|
|
0:19:23
|
and we'll call in from the US
|
|
0:19:36
|
so the call should display as 1
|
|
0:19:39
|
Actually,
|
|
0:19:45
|
it might have been the way that I -- Oh, I went off
|
|
0:19:47
|
Yeah,
|
|
0:19:48
|
Oh, that was because the 1 sorry line 1 is actually still
|
|
0:19:52
|
portraying the plus.
|
|
0:19:54
|
I didn't have a chance to look at that
|
|
0:19:58
|
during the break yet.
|
|
0:20:00
|
So let's do from line 2
|
|
0:20:05
|
So from line 2 it does show up properly as 001512
|
|
0:20:12
|
Line 1 again was my PSTN problem, not any of the
|
|
0:20:17
|
configuration within our CUCM system.
|
|
0:20:20
|
And if I call from line 4 which is nationally.
|
|
0:20:34
|
Now the screen shows up as 010
|
|
0:20:38
|
so we dropped the +31 and prefixed that zero.
|
|
0:20:46
|
And if I make that same call from the Amsterdam line
|
|
0:20:52
|
it should show up as 7037333
|
|
0:20:58
|
and in fact...
|
|
0:21:02
|
in fact it does.
|
|
0:21:07
|
Ok,
|
|
0:21:10
|
excellent, so let's call into -- let's just say the corporate
|
|
0:21:15
|
headquarter from nationally.
|
|
0:21:36
|
And we should see that the line comes in with a prefix of 1
|
|
0:21:43
|
and actually let's go back to that 3002 phone and just take
|
|
0:21:47
|
a look at missed calls since we didn't answer any of those calls
|
|
0:21:50
|
they should all be missed, so even though they came in with
|
|
0:21:53
|
double zero for international or 010 for Rotterdam or just
|
|
0:22:00
|
7037333 from the Amsterdam local
|
|
0:22:03
|
they still all have the global format.
|
|
0:22:07
|
Ok, so everything is working in terms of our localization.
|
|
0:22:16
|
Now again, if this were the real lab and I was not
|
|
0:22:22
|
talking through everything I'm doing which certainly obviously
|
|
0:22:25
|
slows things down just a little bit and I were...
|
|
0:22:30
|
I had the phones in front of me which I do, but you can't
|
|
0:22:33
|
see unless we use the remote client and so therefore I could
|
|
0:22:37
|
dial and see the response a lot quicker.
|
|
0:22:41
|
I would definitely most definitely test every single
|
|
0:22:45
|
pattern on every single phone.
|
|
0:22:48
|
You want to make sure that you test everything in your
|
|
0:22:50
|
dial plan thoroughly. One of the biggest mistakes that
|
|
0:22:55
|
when a candidate doesn't pass and they come back and they're a little bummed
|
|
0:22:58
|
and they either e-mail me or chat with me online and talk with me
|
|
0:23:03
|
and I actually get to kind of do a postmortem with them and
|
|
0:23:05
|
break down maybe what they think they did wrong
|
|
0:23:08
|
not asking them any specifics about the questions, but
|
|
0:23:12
|
just in terms of technology or in terms of your strategy
|
|
0:23:16
|
what do you think you did wrong? One of the things that I almost
|
|
0:23:18
|
always get out of people is that they either didn't have enough time
|
|
0:23:22
|
and so they really need to improve their speed and also
|
|
0:23:25
|
accuracy, but that when they did have enough time or if they
|
|
0:23:31
|
didn't have enough time and so one of the things that they did
|
|
0:23:35
|
to try to make up for the lack of time that they had to test
|
|
0:23:41
|
was they only tested a few of their outbound or inbound
|
|
0:23:46
|
dial plan scenarios. Again, not revealing whatever
|
|
0:23:49
|
those scenarios were, but just talking in general about did you
|
|
0:23:53
|
test everything thoroughly? Did you shut down your primary gateway
|
|
0:23:56
|
and test out you backup? Make sure ANI and DNIS look properly?
|
|
0:24:00
|
Make sure type and plan are proper whatever you were told
|
|
0:24:03
|
to set them as? Did you test every single inbound call on
|
|
0:24:07
|
every phone? It takes a lot of time.
|
|
0:24:09
|
I realize that, but it's something that you need to plan for
|
|
0:24:13
|
because otherwise, even if one phone happens to fail
|
|
0:24:17
|
and maybe the proctor isn't going to test every single inbound call.
|
|
0:24:21
|
First of all they are creating these XML grading scripts that will
|
|
0:24:27
|
help them not only test things quicker so that you can get your
|
|
0:24:31
|
results back quicker, but also make sure that the results are
|
|
0:24:35
|
more accurate in the sense that eliminating any possible
|
|
0:24:39
|
human error. What if a proctor goes to dial a number and they
|
|
0:24:42
|
accidentally misdial a number? And then they're testing
|
|
0:24:45
|
they get reorder tone, but it's actually because they dialed
|
|
0:24:48
|
something wrong. Now they'll typically in their testing look back and
|
|
0:24:52
|
dial something twice, but they obviously -- it's going to take
|
|
0:24:55
|
quite a long time to dial every single number inbound and outbound
|
|
0:24:58
|
to and from every phone every permutation and
|
|
0:25:02
|
especially to ask them to do that twice, so anyway the scripting
|
|
0:25:06
|
can -- should be looked at and viewed as a good thing.
|
|
0:25:10
|
But as that comes along, it becomes very possible
|
|
0:25:14
|
for a very fast computer script to test absolutely
|
|
0:25:19
|
every permutation rather than a proctor who might only
|
|
0:25:25
|
test three or four, but the point of the
|
|
0:25:29
|
the point I'm trying to get to is that even if a proctor's
|
|
0:25:31
|
grading manually still and I don't whether they've implemented
|
|
0:25:35
|
the scripts yet or not. I know they were writing them back in
|
|
0:25:38
|
about a year ago when I last visited the RTP actual
|
|
0:25:44
|
testing center .... back one time since then, but I didn't
|
|
0:25:47
|
have a chance to talk to Kelly about the
|
|
0:25:50
|
script grading that she was creating
|
|
0:25:53
|
but when they were creating these I don't know if they haven't
|
|
0:25:57
|
implemented yet, but even if a proctor does go to test something
|
|
0:26:00
|
manually and they happen to test the one number that you
|
|
0:26:04
|
didn't test and there happens to be a problem with it
|
|
0:26:09
|
just coincidentally.
|
|
0:26:10
|
That's very unfortunate, but it's obviously going to cost you
|
|
0:26:14
|
probably in the neighborhood of somewhere between three to four
|
|
0:26:18
|
points, dial plan being a very big section of the exam, so
|
|
0:26:22
|
possibly more.
|
|
0:26:24
|
So again, you really want to go through and test everything
|
|
0:26:29
|
as thoroughly as you possibly can.
|
|
0:26:34
|
Ok, so we've localized all the calling numbers.
|
|
0:26:36
|
We now need to deal with the fact that these
|
|
0:26:39
|
calling numbers need to be returned. If I press dial
|
|
0:26:58
|
I get the annunciator message telling me the call can't be returned.
|
|
0:27:01
|
And that's because my calling search space here
|
|
0:27:05
|
on my line and device, line/device approach
|
|
0:27:10
|
does not have access to my plus route patterns.
|
|
0:27:18
|
And currently I only have plus as my route patterns.
|
|
0:27:21
|
If I take a look at route plan report and I see
|
|
0:27:24
|
all patterns that begin with \+
|
|
0:27:27
|
they are all either route patterns or calling or called
|
|
0:27:33
|
party transformation patterns.
|
|
0:27:36
|
Here's route pattern, route pattern, route pattern,
|
|
0:27:39
|
calling and called party transformation.
|
|
0:27:41
|
And again it's for this reason that I like to keep all
|
|
0:27:44
|
of my actual user dialable numbers as translation patterns.
|
|
0:27:50
|
My route patterns are for globalized -- the already
|
|
0:27:54
|
globalized format and yes, you might say, 'Well this...
|
|
0:27:58
|
whoops sorry
|
|
0:28:01
|
'The missed calls are in the already globalized format.'
|
|
0:28:05
|
Once this refreshes.
|
|
0:28:07
|
Yes, that's true, but it's still the user dialing them.
|
|
0:28:11
|
So when I say already globalized, I mean already globalized and the
|
|
0:28:14
|
system is using them.
|
|
0:28:16
|
Ok, so what I'm going to is we're going to go to a
|
|
0:28:20
|
translation pattern and -- well, let's just create some
|
|
0:28:26
|
patterns. Actually no, let me actually go back
|
|
0:28:29
|
and I was going to do a copy. I think I'm going to still do that.
|
|
0:28:33
|
So for the US users dial beginning with a 9
|
|
0:28:37
|
so show those patterns and then organize them.
|
|
0:28:40
|
I don't want to put them in a block although we could
|
|
0:28:44
|
consider those as well for our line/device approach and this is
|
|
0:28:46
|
I mentioned earlier that this is actually where it comes
|
|
0:28:48
|
to an issue where when you're using globalization and the
|
|
0:28:53
|
line/device approach, it becomes without creating and going back
|
|
0:28:58
|
and losing the savings that we talked about gaining
|
|
0:29:02
|
from the line/device without losing those savings and still
|
|
0:29:05
|
having to have a -- and actually it was the -- not the savings from
|
|
0:29:10
|
the line/device approach, but rather the -- well no, yeah
|
|
0:29:13
|
it was the savings from the line/device approach where we only had four
|
|
0:29:16
|
class of restrictions versus four class of restrictions times the number
|
|
0:29:21
|
of sites and I'm not sure why I just timed out.
|
|
0:29:26
|
But interesting.
|
|
0:29:34
|
So
|
|
0:29:37
|
without going back and losing those savings which we can do
|
|
0:29:41
|
do mitigate the problem I'm about to explain, but without
|
|
0:29:45
|
going back and losing those savings, it's going to become
|
|
0:29:48
|
fairly impossible for me to actually block or to differentiate
|
|
0:29:55
|
between already globalized numbers that are national and local
|
|
0:30:02
|
because they both begin with +1
|
|
0:30:05
|
in the US or if I'm in Netherlands, they both begin with +31
|
|
0:30:09
|
So if the number needs to be dialed in a already globalized format
|
|
0:30:17
|
if I'm at my Branch 2 phone here whether I'm dialing or
|
|
0:30:22
|
returning the call to Amsterdam which is subscriber or local
|
|
0:30:26
|
or whether I'm returning it to Rotterdam which is
|
|
0:30:29
|
national or long distance
|
|
0:30:33
|
they both begin with +31
|
|
0:30:36
|
Now, differentiating between national or even subscriber and
|
|
0:30:40
|
international is easy because they don't begin with +31
|
|
0:30:44
|
they just begin with plus and then anything else that's not 31
|
|
0:30:48
|
The 31 pattern being more specific.
|
|
0:30:51
|
So it's easy for me to differentiate the class of restriction there.
|
|
0:30:57
|
If I need to have class of restriction and I want to use
|
|
0:31:00
|
line/device approach which is a good idea
|
|
0:31:03
|
It's probably a good idea if you want to retain the savings
|
|
0:31:08
|
to allow all your users to dial local and national.
|
|
0:31:12
|
Now, that might not be your wish and if it's not, then
|
|
0:31:16
|
you pretty much have to go back to still using global dialing
|
|
0:31:20
|
so we're still going to create plus translation patterns
|
|
0:31:22
|
but you have to go back and lose the savings of only having
|
|
0:31:27
|
four or actually three class of restriction partitions or
|
|
0:31:34
|
patterns for every country
|
|
0:31:39
|
and instead you have to go back to having three or four
|
|
0:31:42
|
partitions or patterns for each site within each country.
|
|
0:31:50
|
So if I have a thousand sites within a country, I have a
|
|
0:31:53
|
thousand times four or actually I'd have probably
|
|
0:31:56
|
three partitions -- well, no I'd have my duplicate international
|
|
0:32:02
|
no, I wouldn't have duplicate because you're not going to have the
|
|
0:32:04
|
hash at the end of plus, so you'd have three. You'd have the
|
|
0:32:07
|
local, international and national and then you could be more specific
|
|
0:32:11
|
with +1 or +1206
|
|
0:32:14
|
you can still be more specific, but you might block legitimate
|
|
0:32:18
|
calls, so it's a little bit more difficult.
|
|
0:32:22
|
Or at least it's a little bit less of a savings.
|
|
0:32:26
|
But that's more for the real world because in the lab
|
|
0:32:29
|
we've only got three sites. It's going to be fairly straight
|
|
0:32:32
|
for whether we need to create three sites two countries
|
|
0:32:36
|
so we at least need create at least six of those partitions
|
|
0:32:39
|
and patterns. Whether we need to create six or nine partitions
|
|
0:32:43
|
and patterns is really insignificant.
|
|
0:32:46
|
But I'm just more speaking of for the real world.
|
|
0:32:50
|
Ok, so let's say I want to have my partition for dial
|
|
0:32:56
|
for local. I'm just going to go ahead and grab this.
|
|
0:33:01
|
And I'm going to use this to copy. Even though I don't
|
|
0:33:06
|
really want any of this pattern, my pattern is \+
|
|
0:33:12
|
oops sorry, this was my local, so \+1206!
|
|
0:33:19
|
and I don't really care to do any called party transformation
|
|
0:33:24
|
so I want to get rid of this predot 1 away because I don't
|
|
0:33:27
|
have a dot, but I did copy this so that whatever I had
|
|
0:33:30
|
for my calling party transformation is retained.
|
|
0:33:34
|
Ok, so I'm going to save this.
|
|
0:33:39
|
And I'm probably going to copy this.
|
|
0:33:44
|
Oh! Actually that's right. That's in for my US
|
|
0:33:48
|
so all phones in the US can dial that.
|
|
0:33:53
|
Now I'm going to grab my long distance
|
|
0:33:56
|
or national.
|
|
0:34:02
|
Oops that was block, sorry.
|
|
0:34:06
|
And say for my dialable national
|
|
0:34:10
|
does it have anything different for the calling party?
|
|
0:34:13
|
It doesn't. It doesn't have anything different.
|
|
0:34:17
|
The called party did, but we're not concerned with globalizing
|
|
0:34:21
|
because they're already in the globalized format.
|
|
0:34:23
|
So let me go back to my plus pattern
|
|
0:34:27
|
and say as long as there's nothing different between my
|
|
0:34:31
|
calling party transformation for local and national
|
|
0:34:37
|
then I can make that a simple +1 pattern that
|
|
0:34:43
|
does same thing for calling party use external phone number mask
|
|
0:34:46
|
does nothing for called party
|
|
0:34:48
|
and that will work for both sites national and both sites local.
|
|
0:34:55
|
Remember, at the device it just matters that they can dial
|
|
0:34:58
|
because at the device they're always able to dial everything.
|
|
0:35:01
|
Alright.
|
|
0:35:06
|
So then for my dialable international
|
|
0:35:11
|
pattern
|
|
0:35:12
|
I may have something different for the calling party.
|
|
0:35:16
|
For my pattern, it's just going to be \+!
|
|
0:35:23
|
and that's going to get rid of the predot there and I'm
|
|
0:35:26
|
going to get rid of the prefix because it already has the plus.
|
|
0:35:29
|
Now one thing I need to go do on my other national/subscriber
|
|
0:35:33
|
dial is the urgent priority. Remember, calls that are
|
|
0:35:38
|
dialing the plus aren't from the keypad.
|
|
0:35:43
|
So there’s never overlap sending. They're always from missed calls
|
|
0:35:47
|
or an application such as a call forward box or an AAR destination
|
|
0:35:53
|
box, so they're always going to be end block sending, so we
|
|
0:35:58
|
have to have urgent priority.
|
|
0:36:01
|
So I do need to go back
|
|
0:36:04
|
and grab my other \+ pattern.
|
|
0:36:12
|
And make sure it's urgent priority as well.
|
|
0:36:18
|
Ok, so now I've covered for the US national and international.
|
|
0:36:25
|
So let's go take a look at my dials from the Netherlands.
|
|
0:36:36
|
So let's see I've got my international dial.
|
|
0:36:41
|
Again, the reason I'm going to use this is
|
|
0:36:43
|
because of the calling party is already set up right
|
|
0:36:45
|
so I'm going to do a copy
|
|
0:36:49
|
change the pattern to \+!
|
|
0:36:53
|
so any country code urgent priority.
|
|
0:36:57
|
Calling party transformation stays the same.
|
|
0:37:00
|
The predot's already grayed out. I get rid of the prefix.
|
|
0:37:05
|
I'm good to go there.
|
|
0:37:09
|
Provide outside dial tone really doesn't matter.
|
|
0:37:12
|
And I also want to look at my national/local.
|
|
0:37:17
|
Actually we do have a separate one for that.
|
|
0:37:20
|
Let's look at this one first.
|
|
0:37:24
|
Calling party external phone number mask
|
|
0:37:26
|
is what's used there.
|
|
0:37:28
|
So I'm copying it for that plus the partition
|
|
0:37:31
|
say \+31!
|
|
0:37:36
|
urgent priority
|
|
0:37:38
|
Get rid of any called party transformation
|
|
0:37:41
|
because it's already in the globalized format.
|
|
0:37:44
|
Save that.
|
|
0:37:47
|
And then let's see.
|
|
0:37:50
|
Was there anything different for the 7-digit potential dial
|
|
0:37:56
|
that we had? No, it also used calling party transformation.
|
|
0:38:01
|
The only difference was the called party. Well, since we're not
|
|
0:38:03
|
doing any digit manipulation on called party, then our
|
|
0:38:09
|
\+31 will take care of national and subscriber.
|
|
0:38:14
|
Now these are for the all the for the dials.
|
|
0:38:17
|
We still need to potentially have blocks for the -- or sorry
|
|
0:38:23
|
equivalents for the blocks, so let's go take a look
|
|
0:38:26
|
at our 9 for our US
|
|
0:38:30
|
and I had a block for national.
|
|
0:38:34
|
Now remember all these have is the partition that is the block
|
|
0:38:39
|
partition and the fact that it blocks this pattern.
|
|
0:38:44
|
So if I were to copy this
|
|
0:38:48
|
so in other words, there's no calling or called party transformation.
|
|
0:38:51
|
If I were to copy this and say if this was a national number
|
|
0:38:54
|
then \+1! is the equivalent with urgent priority
|
|
0:39:04
|
but keep in mind if this blocks national, it also blocks local.
|
|
0:39:12
|
Well, maybe not. Let's see.
|
|
0:39:15
|
Let's do partition.
|
|
0:39:19
|
No, that's actually not going to...
|
|
0:39:20
|
I'll do an And.
|
|
0:39:23
|
So pattern begins with 9.1
|
|
0:39:31
|
and...
|
|
0:39:35
|
These aren't And Or
|
|
0:39:40
|
Ok, so anyhow
|
|
0:39:43
|
I'll just show them all.
|
|
0:39:49
|
So if I've got an allow for +1
|
|
0:39:53
|
whoops sorry, that's my block.
|
|
0:39:55
|
If I've got an allow for +1
|
|
0:39:58
|
and a block for +1
|
|
0:40:01
|
then those two are equal. Remember one shows up
|
|
0:40:04
|
at the device level, so it's ordered lower and one
|
|
0:40:08
|
shows up at the line level, so it's ordered higher.
|
|
0:40:11
|
But higher partitions only matter in the case of a
|
|
0:40:15
|
direct tie. Well, those two patterns are a direct tie.
|
|
0:40:19
|
So in this case, I might also want to create
|
|
0:40:28
|
a +1206
|
|
0:40:33
|
which is a more specific pattern.
|
|
0:40:39
|
So now, if I had block national on my line
|
|
0:40:44
|
and I had dot US PSTN dial
|
|
0:40:49
|
national on my device
|
|
0:40:51
|
this is ordered higher, so it blocks me from dialing anything
|
|
0:40:55
|
that begins with +1 unless at the device, I have something
|
|
0:40:59
|
that allows me something more specific, so if I dial +1206
|
|
0:41:05
|
Right, so this would work. Here's the problem.
|
|
0:41:09
|
Because this is also on the device level for the Branch 1
|
|
0:41:13
|
phone, because it's at the US PSTN dial partition rather than
|
|
0:41:19
|
a corporate headquarter PSTN dial.
|
|
0:41:24
|
It's at the US level, so all phones in the US or all phones within a given country
|
|
0:41:29
|
then Branch 1 phones also have the ability -- they might still
|
|
0:41:33
|
if they had the block at the national, so they've only got the local
|
|
0:41:38
|
allowable CSS, they're still not allowed to dial anywhere
|
|
0:41:41
|
else other than +1512 which we haven't created, but
|
|
0:41:45
|
we'll do so very quickly here.
|
|
0:41:48
|
But there also -- this is in the way, sorry
|
|
0:41:52
|
but they're also able to dial the +1206 and any other
|
|
0:41:59
|
site that I have a gateway. Now, if I have tail end hop-off
|
|
0:42:05
|
which you don't always want to do
|
|
0:42:09
|
it's really -- in the lab again it's whatever the lab says.
|
|
0:42:12
|
In real life, you don't always want to do because a lot of
|
|
0:42:16
|
times these days at least in the US, phone lines are far cheaper than the
|
|
0:42:22
|
WAN bandwidth and I think that's probably still true in
|
|
0:42:25
|
most places is that while long distance national and international
|
|
0:42:29
|
tolls can be expensive, they're typically less expensive than
|
|
0:42:33
|
the WAN bandwidth is. It depends on your company.
|
|
0:42:36
|
You might have loads of extra WAN bandwidth and so you don't care how many calls
|
|
0:42:40
|
route over the WAN or you don't care if up to whatever you have
|
|
0:42:45
|
defined for your call admission control in QoS priority queues
|
|
0:42:48
|
route over the WAN, so in other words all the tail end hop-off calls
|
|
0:42:52
|
that want to -- however you may care.
|
|
0:42:56
|
You may not want everything going tail end hop-off because
|
|
0:43:00
|
you could dial long distance and either incur a toll
|
|
0:43:06
|
that in the grand scheme of total cost of ownership is actually
|
|
0:43:09
|
less expensive than the WAN bandwidth that it occupied
|
|
0:43:12
|
for the hour that you happen to be on the phone to a buyer
|
|
0:43:16
|
or an agent or something like that.
|
|
0:43:21
|
Ok, so maybe you're on the phone with Microsoft tech support
|
|
0:43:24
|
so you're going to be on for good two hours. I'm just kidding.
|
|
0:43:26
|
Just joking.
|
|
0:43:29
|
But so anyway, in the real life it might depend.
|
|
0:43:33
|
But if you did have tail end hop-off, then you might not care about the
|
|
0:43:38
|
user's dialing nationally. I personally once you get to a lot of
|
|
0:43:44
|
large companies, they typically don't care to have a difference
|
|
0:43:48
|
between users that are allowed to dial local and nationally
|
|
0:43:52
|
except maybe in a few small areas like lobby areas and
|
|
0:43:56
|
waiting rooms and break rooms and things like that,
|
|
0:43:59
|
But at the desks, they really don't care that much.
|
|
0:44:01
|
In that case, it's great. It's easily scalable.
|
|
0:44:04
|
Ok, but there are possibly exceptions to what you might
|
|
0:44:08
|
want to do. In the lab, you want to do exactly what you're told.
|
|
0:44:18
|
Ok, so I've got my two patterns that are more
|
|
0:44:23
|
specific for cities just in case I happen to have block national.
|
|
0:44:26
|
Now, maybe I need to have a block local or block subscriber
|
|
0:44:32
|
as well, so I'm going to copy this. It doesn't really matter
|
|
0:44:36
|
if I leave or uncheck, untick, do anything with my calling or
|
|
0:44:40
|
called party because I'm about to make this in the partition
|
|
0:44:45
|
for US block local
|
|
0:44:49
|
and block this pattern.
|
|
0:44:53
|
So if you have restricted access on your phone, that is
|
|
0:44:57
|
you're told to block local, the you're not going to be
|
|
0:44:59
|
able to dial or return dial a +1206
|
|
0:45:05
|
You've also not going to be able to return dial a +1512
|
|
0:45:15
|
But only if you have restricted on your line.
|
|
0:45:18
|
And it doesn't matter what the CSS is.
|
|
0:45:20
|
In most of our blocks, the CSS is left to none. It's
|
|
0:45:24
|
fine, it really doesn't matter if it's left to something.
|
|
0:45:27
|
I'm not going to go and change my +1206 because
|
|
0:45:29
|
the pattern is going to be blocked. The CSS if effectively ignored.
|
|
0:45:36
|
Ok, do I have a block for my international? I do not yet.
|
|
0:45:40
|
So I'm going to create a block for my international.
|
|
0:45:44
|
Copy.
|
|
0:45:47
|
And block international CSS to none just because
|
|
0:45:52
|
block this pattern. I can get rid of this just so that
|
|
0:45:55
|
when I come back I'm not confused, but it really doesn't matter
|
|
0:45:58
|
because the pattern's blocked.
|
|
0:46:02
|
Ok, so now I have my blocks taken care of
|
|
0:46:04
|
for the line/device approach as well.
|
|
0:46:09
|
Well, at least for the US
|
|
0:46:10
|
and I need to block my Netherlands sites.
|
|
0:46:16
|
So I've got my Netherlands PSTN dial. Let's go ahead and grab this.
|
|
0:46:20
|
Well actually no. I think my blocks were for...
|
|
0:46:25
|
Yeah I did have Netherland specific blocks.
|
|
0:46:27
|
Ok, so Netherland block international.
|
|
0:46:29
|
oops sorry, I need to copy this first
|
|
0:46:32
|
would be a good idea.
|
|
0:46:35
|
So I don't overwrite.
|
|
0:46:37
|
That's a common mistake that I do and I've seen students do is
|
|
0:46:40
|
accidentally go in and modify, but you meant to copy first.
|
|
0:46:45
|
So be aware of that.
|
|
0:46:53
|
And again, I'm just getting rid of this for future reference
|
|
0:46:57
|
so block international Netherlands
|
|
0:47:01
|
copy, block national
|
|
0:47:07
|
whoops
|
|
0:47:08
|
I didn't change the partition to block
|
|
0:47:12
|
Netherlands national, there we go.
|
|
0:47:17
|
And then copy to block Netherlands local.
|
|
0:47:30
|
Ok, so if I go back and just look at my
|
|
0:47:34
|
plus patterns
|
|
0:47:37
|
and sort partition according to name.
|
|
0:47:42
|
I see that if I have a block national
|
|
0:47:48
|
on my line, but I'm allowed to dial local
|
|
0:47:52
|
I currently only have a +31 for dialing anything national or
|
|
0:47:56
|
local, so I need to also copy this
|
|
0:48:01
|
for regular dialing for +3120 for local
|
|
0:48:08
|
and calling party external phone number mask is
|
|
0:48:11
|
probably going to be still what I want
|
|
0:48:15
|
so now I should have everything I want.
|
|
0:48:23
|
Ok, so I've got my dial patterns for
|
|
0:48:30
|
Branch 1 local, then international, then corporate headquarter
|
|
0:48:34
|
local, then national.
|
|
0:48:36
|
And then I've got my block patterns for the US
|
|
0:48:40
|
for national, Branch 1, corporate and international
|
|
0:48:45
|
respectively top down.
|
|
0:48:47
|
Then I've got my PSTN dials for Netherlands
|
|
0:48:51
|
for international, local and national.
|
|
0:48:55
|
And then my block patterns for international, local and
|
|
0:49:01
|
I'm sorry national, local and international.
|
|
0:49:04
|
And again we note that the US will be able to dial
|
|
0:49:08
|
back and forth between the two sites even if you
|
|
0:49:11
|
don't have -- even if you're blocked at the national level.
|
|
0:49:17
|
Ok, unless we create further partitions and CSSs.
|
|
0:49:23
|
So is that clear so far before we go ahead and test this?
|
|
0:49:36
|
Ok, I don't see any questions yet.
|
|
0:49:38
|
I see a few people typing, so I'll take those as they come.
|
|
0:49:42
|
Someone said, "Wouldn't it be the same if we added the phones'
|
|
0:49:48
|
calling search spaces and given only the partitions that give access
|
|
0:49:53
|
to the desired patterns local, national, inter? This way we
|
|
0:49:58
|
won't we have to create blocked patterns?" Ok, so you're saying
|
|
0:50:01
|
wouldn't the situation work equally as well if instead of
|
|
0:50:06
|
creating any blocked patterns for anything whether it be for
|
|
0:50:10
|
these plus patterns or even for the -- let's just go to
|
|
0:50:16
|
partition contains block.
|
|
0:50:20
|
Whoops.
|
|
0:50:22
|
Not block L
|
|
0:50:25
|
but block.
|
|
0:50:27
|
So instead of creating any of these block patterns
|
|
0:50:32
|
wouldn't it be better to just create CSSs that were applied
|
|
0:50:38
|
to the lines that not only were site specific, but also
|
|
0:50:43
|
class of restriction specific?
|
|
0:50:45
|
So essentially we'd create the class of restrictions and only
|
|
0:50:48
|
put the partitions with patterns in that should be in those particular
|
|
0:50:53
|
lines and so we'd create instead of just creating a
|
|
0:50:56
|
general partition for US dial for all PSTN numbers
|
|
0:51:01
|
and partition for dial for all Netherlands numbers
|
|
0:51:07
|
we create partition for local and put those local dials in there.
|
|
0:51:11
|
Yes it would be the same except for the fact that
|
|
0:51:20
|
we would still have -- let me think about this
|
|
0:51:26
|
but local route groups is what takes away all the patterns
|
|
0:51:29
|
we would still have all of the calling search spaces. Now
|
|
0:51:32
|
again, in a 3-site lab environment
|
|
0:51:36
|
you really can't appreciate the savings
|
|
0:51:41
|
because for instance, we only have two sites within one country:
|
|
0:51:46
|
Corporate Headquarter and Branch 1
|
|
0:51:49
|
So the calling search space and partition savings by
|
|
0:51:53
|
using the line/device approach where the block calling search space
|
|
0:51:58
|
goes on the -- or the block patterns are effectively
|
|
0:52:01
|
go on the line and the allow patterns for everything
|
|
0:52:04
|
go on the device, the savings is only for CSSs and for partitions.
|
|
0:52:11
|
But again, if we were looking at even 100 sites which is
|
|
0:52:15
|
a much more reasonable -- although I certainly know
|
|
0:52:20
|
I know CUCM clusters personally that have easily 500 sites
|
|
0:52:29
|
and so if we had 500 sites even spread out within like
|
|
0:52:34
|
70 or 80 or a 100 cities all within one country
|
|
0:52:41
|
we are going to still effectively have without the line/device approach
|
|
0:52:45
|
we're going to have to have calling search spaces
|
|
0:52:51
|
for each of those sites and each of those patterns
|
|
0:52:56
|
because we need them to be -- let me think about this
|
|
0:53:05
|
with local route group if we're using local route group
|
|
0:53:10
|
that's going to shoo the need for all the patterns
|
|
0:53:14
|
and just have one set.
|
|
0:53:21
|
With local route group -- I'd have to put it down on paper
|
|
0:53:25
|
to be sure, but it may get us back to being able to do what
|
|
0:53:31
|
you're referring to is what's called the traditional CSS approach
|
|
0:53:34
|
and it was the first thing that we looked at before we
|
|
0:53:37
|
in the slides looked at the line/device approach.
|
|
0:53:42
|
It's very possible that that could get us back because
|
|
0:53:47
|
we wouldn't need CSS per site, but we would need
|
|
0:53:51
|
them for types of patterns.
|
|
0:53:54
|
Yeah, it's very possible that we could do it that way
|
|
0:53:56
|
as well.
|
|
0:53:59
|
Ok, so what I'll do is I will after we cut class for today
|
|
0:54:07
|
I'll actually take a look and since I still wanted to go into
|
|
0:54:12
|
the line/device approach just in case for some reason you were forced to use it in the lab
|
|
0:54:17
|
you were told to use it, it's very important that you know how to
|
|
0:54:20
|
with not only respect to user dialable patterns, but also
|
|
0:54:24
|
with respect to plus dial patterns
|
|
0:54:29
|
but I will also go back and modify this dial plan to not
|
|
0:54:32
|
include them and again while it's still a small lab environment
|
|
0:54:37
|
we should still see at least the savings of that between.
|
|
0:54:44
|
Even if we have that, we're still going to have the issue
|
|
0:54:50
|
with being able to dial the plus or return calls or
|
|
0:54:59
|
missed and received with the plus local to each other gateway
|
|
0:55:06
|
site unless we created a by site calling search space
|
|
0:55:13
|
break down.
|
|
0:55:14
|
But I can certainly modify it and show you what it looked like
|
|
0:55:18
|
the other way as well.
|
|
0:55:23
|
That's true, you could create the plus dial patterns per site
|
|
0:55:26
|
and create one additional partition and CSS for local only per site
|
|
0:55:30
|
leaving an international and a national CSS for the whole country
|
|
0:55:37
|
but then the local per city or per site.
|
|
0:55:41
|
That's a very good point.
|
|
0:55:44
|
Ok, so I will modify it so that you see what the
|
|
0:55:48
|
simplified possibilities are, but I did want to make sure that
|
|
0:55:53
|
you saw the other way as well. Like I said, just in case it's something
|
|
0:55:56
|
that you're instructed to do. I want to make sure we cover all the bases.
|
|
0:56:01
|
Ok, so next let's go ahead and test some things.
|
|
0:56:05
|
Ok, so let's test dialing back to -- and I believe
|
|
0:56:11
|
1002 had national dial rights if I recall properly.
|
|
0:56:15
|
1001 has international, so if I go to missed calls
|
|
0:56:22
|
I should be able to dial back to the Austin phone
|
|
0:56:28
|
And sure enough it's ringing the PSTN.
|
|
0:56:33
|
Whoops.
|
|
0:56:35
|
Here's the PSTN screen.
|
|
0:56:40
|
Let me try to find -- there we go.
|
|
0:56:43
|
So it's dialing 512602 and it's coming from 2065011002
|
|
0:56:54
|
Ok,
|
|
0:56:57
|
whereas if I go to dial for missed calls from that same
|
|
0:57:03
|
phone 1002
|
|
0:57:08
|
And let's see if I even have a call from an international.
|
|
0:57:12
|
I don't, so let's actually just dial in from international here.
|
|
0:57:27
|
Ok, they should see 011
|
|
0:57:30
|
it does.
|
|
0:57:33
|
Let's get rid of that call.
|
|
0:57:35
|
And bring up missed calls.
|
|
0:57:39
|
So if I try to dial back to an international number
|
|
0:57:48
|
it clears away. Instantly clears.
|
|
0:57:51
|
Remember I changed one of those patterns to
|
|
0:57:57
|
precedence level exceeded.
|
|
0:57:58
|
I didn't happen to change this particular or any of the blocked
|
|
0:58:02
|
patterns for the plus dials
|
|
0:58:07
|
or not even all of them for the rest to precedence
|
|
0:58:10
|
level exceeded or call rejected where I'd get reorder tone.
|
|
0:58:13
|
So right now, with no error the call just clears away because
|
|
0:58:18
|
they're not allowed to, so we've even -- we've retained
|
|
0:58:24
|
our class of restriction as well as...
|
|
0:58:29
|
We've retained our class of restriction for the block patterns
|
|
0:58:33
|
and we've retained our calling party transformation or calling
|
|
0:58:40
|
ID display as per the dialed digits even when we're doing
|
|
0:58:46
|
for both of those even when we're doing plus dial returns.
|
|
0:58:49
|
Ok, so if I go to the corporate headquarter
|
|
0:58:54
|
Oh, this is Branch 2 phone 2, let me go to corporate headquarter
|
|
0:58:57
|
phone 1 and they go to missed calls
|
|
0:59:04
|
then I should be able to return something like an Amsterdam
|
|
0:59:07
|
international line.
|
|
0:59:11
|
And sure enough, this seems to work just fine.
|
|
0:59:18
|
From Jack Shepherd
|
|
0:59:20
|
this must be going out the SIP corporate headquarter gateway
|
|
0:59:23
|
because I still see the 9 We never did the SIP profiles
|
|
0:59:26
|
to get rid of that.
|
|
0:59:30
|
Ok, so that looks like that works.
|
|
0:59:32
|
Let's look at a Branch 1 phone.
|
|
0:59:34
|
Oh, that's a Branch 2 phone, let's go ahead and do it since it's up.
|
|
0:59:38
|
So Branch 2 Phone 2
|
|
0:59:41
|
returning a local number +3120
|
|
0:59:45
|
looks like it fails.
|
|
0:59:48
|
Ok, let's see what the gateway said.
|
|
0:59:53
|
And the called party number
|
|
0:59:56
|
wait a minute, let's clear off these gateways because we're not
|
|
0:59:58
|
exactly sure
|
|
1:00:02
|
where that call came from
|
|
1:00:05
|
or actually what gateway it went out if it did.
|
|
1:00:08
|
So let's do missed calls.
|
|
1:00:15
|
And let's try to dial the number back.
|
|
1:00:19
|
And it clears, I don't see any output on any of these
|
|
1:00:23
|
gateways. Let's see if 3002
|
|
1:00:27
|
actually had the rights to dial local.
|
|
1:00:35
|
I know we gave one phone. I thought we gave one phone
|
|
1:00:39
|
restricted and it might have been that one.
|
|
1:00:42
|
Branch 2 Phone 2
|
|
1:00:45
|
the CSS of course on the line is for Netherlands phones
|
|
1:00:49
|
dial everything. The CSS on the -- I'm sorry, on device was dial everything.
|
|
1:00:53
|
The CSS on the line was restricted, so that worked properly.
|
|
1:00:58
|
It can't even dial a local number back. Good.
|
|
1:01:00
|
That's as expected.
|
|
1:01:03
|
Ok, so let's get rid of some of these phones
|
|
1:01:06
|
that we're not using.
|
|
1:01:08
|
Here's our Branch 2 Phone 1
|
|
1:01:11
|
I'm not sure if we have a call into it from -- Yep, there we go.
|
|
1:01:19
|
So here's a local call
|
|
1:01:21
|
+3120
|
|
1:01:24
|
It works just fine to dial out
|
|
1:01:29
|
except that it went out the corporate headquarter gateway
|
|
1:01:32
|
it looks like.
|
|
1:01:34
|
It looks like it tried to dial out with 020, but the...
|
|
1:01:43
|
We received a disconnect.
|
|
1:01:45
|
So I'm guessing that that's because I'm not allowing
|
|
1:01:49
|
020 to go out and instead I'm expecting seven digits only on the PSTN.
|
|
1:01:57
|
Let's see...
|
|
1:01:58
|
If that is the case,
|
|
1:02:01
|
then it wouldn't be hard to...
|
|
1:02:04
|
If I can find my configuration
|
|
1:02:08
|
to make it so that...
|
|
1:02:14
|
for called party transformation pattern
|
|
1:02:21
|
for Branch 2 -- let's just sort this by partition
|
|
1:02:27
|
that Branch 2 gateway +31
|
|
1:02:32
|
We actually do create a duplicate which says
|
|
1:02:38
|
+3120 gets stripped and we don't prefix
|
|
1:02:45
|
a zero so that it sends seven digits.
|
|
1:02:51
|
Ok,
|
|
1:02:52
|
again it just depends on the carrier and in this case, my particular
|
|
1:02:56
|
carrier. It doesn't really matter what the real world is if that's
|
|
1:02:59
|
not the way that the real world would accept it because
|
|
1:03:02
|
in this case, that's my carrier and what it's allowing and
|
|
1:03:06
|
again, same sort of idea for the lab whatever they tell you.
|
|
1:03:14
|
They will drop calls if you don't format the number
|
|
1:03:18
|
properly the way they tell you to
|
|
1:03:19
|
or the way they instruct you that your carrier simulator
|
|
1:03:23
|
will accept them. They may drop calls if type or plan
|
|
1:03:26
|
is other than what they expect to see.
|
|
1:03:28
|
Ok, so let's try that call again.
|
|
1:03:33
|
And actually, I didn't...
|
|
1:03:38
|
I didn't clear away anything.
|
|
1:03:42
|
So let's hit -- no, let's go back in through this method.
|
|
1:03:47
|
I don't want to accidentally
|
|
1:03:50
|
hit redial and it dials something else.
|
|
1:03:52
|
I just want to be sure, so missed calls call number two.
|
|
1:03:55
|
Let's dial again, look through our gateways.
|
|
1:03:59
|
It is not even coming through Branch 2
|
|
1:04:02
|
at all. It didn't even try it.
|
|
1:04:07
|
Ok, that's interesting.
|
|
1:04:13
|
I wonder why.
|
|
1:04:16
|
Let's take a look in Branch 2 and do a debug voip dial peer
|
|
1:04:22
|
and clear off
|
|
1:04:24
|
corporate headquarter.
|
|
1:04:27
|
Let's try the redial.
|
|
1:04:33
|
Yep, 703 -- Ah!
|
|
1:04:39
|
I know why.
|
|
1:04:40
|
Because it did come in, but it came in as seven digits
|
|
1:04:43
|
and if we take a look at our voice translation rules
|
|
1:04:47
|
that on the inbound
|
|
1:04:52
|
prefixed a zero it was only if they were coming in with
|
|
1:04:55
|
a zero first.
|
|
1:04:58
|
So ten is prefixed zero in from CUCM.
|
|
1:05:00
|
So here I need to config t and I just happen to copy that
|
|
1:05:06
|
it's just copying rule 1 over top of itself, but I'm going to create
|
|
1:05:09
|
rule 2 which says that if the number begins with a
|
|
1:05:15
|
let's say 703.... so seven digits
|
|
1:05:24
|
then do the same thing. Prefix a zero ampersand
|
|
1:05:32
|
Now this should work. Let's undebug voip dial peer
|
|
1:05:40
|
so that I still have ISDN on.
|
|
1:05:43
|
Let's clear this away just in case it does come back out
|
|
1:05:45
|
corporate headquarter. We can see it.
|
|
1:05:48
|
Let's go to missed calls.
|
|
1:05:55
|
And try call number two back to Seattle local
|
|
1:05:59
|
I'm sorry, not Seattle, Amsterdam
|
|
1:06:01
|
and dial.
|
|
1:06:04
|
Nope. It still didn't like it.
|
|
1:06:12
|
So let's debug voip dial peer again.
|
|
1:06:16
|
Try the call again.
|
|
1:06:20
|
See what's happening now.
|
|
1:06:22
|
Oh! I know what happened. I prefixed the zero, so it
|
|
1:06:26
|
first came in as 703, then we did the transformation, so now
|
|
1:06:30
|
it's -- I didn't actually mean to prefix a zero
|
|
1:06:33
|
I'm not sure why I did that.
|
|
1:06:36
|
What I did mean to do...
|
|
1:06:44
|
no rule 2
|
|
1:06:47
|
was to say that we don't have the proper dial peers.
|
|
1:06:50
|
begin dial-peer
|
|
1:06:53
|
for outgoing -- actually no, I did mean to prefix
|
|
1:06:58
|
a zero because of the secondary dial tone.
|
|
1:07:00
|
So I do want to prefix the zero for the secondary dial tone, but I still
|
|
1:07:03
|
don't have a dial peer that will allow for that. I only have
|
|
1:07:11
|
Ok, let me quit second guessing myself. I do want
|
|
1:07:13
|
that rule 2 that adds that second zero, but then I also
|
|
1:07:19
|
want...
|
|
1:07:26
|
I just entered those so that I could go back and
|
|
1:07:30
|
use the structure quickly
|
|
1:07:32
|
port I want and destination pattern.
|
|
1:07:39
|
I want without.
|
|
1:07:42
|
So yes,
|
|
1:07:46
|
this
|
|
1:07:50
|
and this are overlapping dial peers
|
|
1:07:54
|
Actually no they're not. This is just variable length, but they're
|
|
1:07:58
|
not overlapping because of that 1 through 9
|
|
1:08:01
|
And it will strip the zero before it sends it, so now it should work.
|
|
1:08:07
|
Let's clear off this gateway. Clear off this gateway.
|
|
1:08:11
|
And undebug voip dial peer unless we need it again.
|
|
1:08:17
|
Try this redial again.
|
|
1:08:20
|
This time it goes out properly.
|
|
1:08:24
|
Ok, so
|
|
1:08:30
|
we did promise you trouble shooting live in the class, right?
|
|
1:08:32
|
Even instructors break things. No problem.
|
|
1:08:36
|
The important thing is that you know how and which
|
|
1:08:38
|
debugs to run, how to read them and how to quickly
|
|
1:08:41
|
recover from your mistakes.
|
|
1:08:45
|
And you learn how to quickly recover from your mistakes when you
|
|
1:08:49
|
record yourself live in front of a live class.
|
|
1:08:53
|
That should get a few laughs, but it's true.
|
|
1:08:56
|
Put yourself under some pressure like that. Somehow
|
|
1:08:58
|
when you're preparing for the lab towards your last couple weeks
|
|
1:09:02
|
put yourself under a real timed test where if you don't
|
|
1:09:07
|
get it done in eight hours, you stop yourself.
|
|
1:09:11
|
You should really be doing that about a month before
|
|
1:09:14
|
your exam, but then maybe even put yourself under some
|
|
1:09:19
|
sort of pressure where you hold your own little self-study
|
|
1:09:23
|
group where you've got a few members in a study group
|
|
1:09:29
|
and -- I don't know if you want to necessarily do it live
|
|
1:09:34
|
or something, but some way to really force the pressure
|
|
1:09:38
|
of what you would expect to see in the real lab.
|
|
1:09:44
|
Ok, and likewise -- actually I don't know if I have a...
|
|
1:09:50
|
this screen should be refreshed.
|
|
1:09:51
|
Let's do a 7033001
|
|
1:10:02
|
in from a Austin site
|
|
1:10:09
|
just so that we have an international number appear here.
|
|
1:10:11
|
It'll appear as 001
|
|
1:10:16
|
We'll go ahead and hang up.
|
|
1:10:19
|
But then in their missed calls
|
|
1:10:24
|
they should see the +1512 and while Branch 2 Phone 2 couldn't return it
|
|
1:10:30
|
Branch 2 Phone 1 should be able to.
|
|
1:10:37
|
And what ANI is seeing
|
|
1:10:41
|
3120, so country code first
|
|
1:10:45
|
and the call...
|
|
1:10:51
|
The call actually went out my Branch 1 gateway.
|
|
1:10:56
|
Why did it go out my Branch 1 gateway?
|
|
1:10:58
|
Because we have tail end hop-off configured. If I didn't
|
|
1:11:01
|
have tail end hop-off, it would have gone out my local gateway.
|
|
1:11:06
|
Obviously there are other considerations in real production networks with tail end
|
|
1:11:10
|
hop-off such as some countries.
|
|
1:11:14
|
Sorry.
|
|
1:11:15
|
India being the one that comes to my mind quickest
|
|
1:11:20
|
Don't allow for certain types of tail end hop-off.
|
|
1:11:24
|
So especially if I'm going -- if I have a phone
|
|
1:11:28
|
let's say I have a gateway in Bangalore and I've got a
|
|
1:11:33
|
gateway in New York City and I've got a phone in Bangalore
|
|
1:11:36
|
and a phone in New York City. If I go to make a call and I try
|
|
1:11:41
|
to hop off to a gateway, I go to make a call from a New York
|
|
1:11:45
|
City phone, IP phone, and I try to hop off a Bangalore gateway
|
|
1:11:48
|
that's actually forbidden by law and even more so, if I'm let's say
|
|
1:11:55
|
IP phone from New York City to IP phone from Bangalore
|
|
1:11:58
|
that's allowed, but then I involve a third party conference
|
|
1:12:03
|
which hops off in Bangalore, that's effectively -- or even a
|
|
1:12:07
|
third party conference that hops off in the New York City PSTN
|
|
1:12:11
|
that's still effectively involving a tail end hop-off that is essentially
|
|
1:12:19
|
the way that it's viewed or that I understand from certain people
|
|
1:12:23
|
that it's viewed as it's essentially stealing from the
|
|
1:12:27
|
government-run Telco that could be harvesting those
|
|
1:12:32
|
dollars or currency for the toll that would otherwise be incurred
|
|
1:12:39
|
so in CUCM 7.1 and persisting into 8
|
|
1:12:45
|
there is something called GO localization and we actually
|
|
1:12:51
|
can put GO tags based on gateways and things like that.
|
|
1:12:55
|
That's not in the lab. Nice that it's one less thing that you have to worry about
|
|
1:12:59
|
for now until the lab blueprint changes probably in the
|
|
1:13:04
|
little over a year of July of 2012 most likely if it stays on historical
|
|
1:13:11
|
track, but just so you're aware in real life, tail end hop-off
|
|
1:13:16
|
most certainly isn't for everyone and in some cases it might not be
|
|
1:13:20
|
allowed. The nice thing is with CUCM and the flexibility of the way
|
|
1:13:24
|
that they create the modules, the entities within CUCM
|
|
1:13:28
|
you can still provision everything to do tail end hop-off if that's what
|
|
1:13:32
|
you desire, but in CUCM 7.1 and 8 and 8.5 and 9, you
|
|
1:13:37
|
can tag these entities with their GO location and then
|
|
1:13:43
|
if it should not involve one of those gateways because
|
|
1:13:46
|
it would otherwise be a violation of GO location...
|
|
1:13:51
|
GO location policy, then it will automatically not allow that
|
|
1:13:56
|
type of a tail end hop-off and automatically fail over.
|
|
1:13:59
|
So it doesn't mean that you have to change again your
|
|
1:14:02
|
whole dial plan to not do certain tail end hop-off for this
|
|
1:14:04
|
type of a -- this particular site or these particular sites in this
|
|
1:14:11
|
particular country, but you simply tag everything appropriately
|
|
1:14:15
|
and then it will make the intelligent decisions.
|
|
1:14:18
|
So again, that's actually just one of the reasons why
|
|
1:14:23
|
everything is so granular and abstracted from each other
|
|
1:14:28
|
and cut up is so that with granularity comes extreme
|
|
1:14:33
|
flexibility in our design and our programming.
|
|
1:14:36
|
It might also increase the complexity of things.
|
|
1:14:42
|
But then again, that's why you're here watching this
|
|
1:14:46
|
class on demand or live class and that's why you're
|
|
1:14:50
|
going after your CCIE is so that you can be the expert
|
|
1:14:53
|
at these complex things and not just have past an exam, but
|
|
1:14:59
|
truly be the expert. So anyhow
|
|
1:15:02
|
we've now dealt with all the forms of globalization and localization
|
|
1:15:07
|
including dealing with plus dial which should mean that anything
|
|
1:15:14
|
that we need to do in terms of -- if we log back in to CUCM
|
|
1:15:19
|
anything that we're about to do in terms of populating any
|
|
1:15:23
|
fields when it comes to let's say automated alternate routing
|
|
1:15:28
|
or when it comes to AAR
|
|
1:15:37
|
sorry, that is automated alternate routing. I meant to say CFUR
|
|
1:15:40
|
so Call Forward on Unregister for phones that have fallen back
|
|
1:15:44
|
into SRST mode and still have PSTN capability or connectivity
|
|
1:15:48
|
but they don't have WAN connectivity. All of those
|
|
1:15:51
|
fields, any and all of these fields can now and should now
|
|
1:15:57
|
be populated. If I can just go into one briefly.
|
|
1:16:04
|
As well as what we're going to talk about next: Unified Mobility
|
|
1:16:07
|
can now be populated with the...
|
|
1:16:16
|
And actually, this would just be the plus. The only time it's a
|
|
1:16:20
|
backslash plus is if it's actually a pattern, so directory number
|
|
1:16:25
|
or something that ends in the word pattern.
|
|
1:16:27
|
But if it's anything else like a destination or whatever
|
|
1:16:31
|
this isn't evaluating regular expressions.
|
|
1:16:36
|
So you just need to use the plus format, but at this point...
|
|
1:16:39
|
What phone are we on? 1001
|
|
1:16:42
|
So this can be +1206501XXXX
|
|
1:16:48
|
and I can use this for all my AAR destination masks at
|
|
1:16:52
|
corporate headquarters.
|
|
1:16:55
|
I can use this for my forward on unregistered
|
|
1:16:58
|
my call forward on unregistered
|
|
1:17:01
|
whoops, I didn't copy that.
|
|
1:17:07
|
Corporate headquarter probably wouldn't be unregistered
|
|
1:17:10
|
but why can I use that? So let's say for a Branch 1 phone
|
|
1:17:13
|
that might unregistered and fall back into SRST.
|
|
1:17:16
|
Well because if the corporate headquarter phone goes to
|
|
1:17:18
|
dial the Branch 1 phone at let's say +1512602XXXX or
|
|
1:17:26
|
2001, it will simply match a translation pattern
|
|
1:17:34
|
that is if the calling search space allows it to.
|
|
1:17:39
|
It will match a translation pattern. That translation pattern will apply
|
|
1:17:43
|
calling party transformation to make the ANI look proper.
|
|
1:17:48
|
Send it on to the route pattern, the route pattern will send it on
|
|
1:17:52
|
to the route list, route list will send it either to a specific
|
|
1:17:56
|
tail end hop-off gateway or to standard local route group
|
|
1:17:59
|
which will look back to the calling party corporate
|
|
1:18:01
|
headquarter phone, find the local route group, route out
|
|
1:18:04
|
to the gateway, the gateway will then have the egress called party
|
|
1:18:11
|
transformation and if I'm at corporate headquarter, but I'm
|
|
1:18:14
|
calling 512 because let's just say this was actually the Branch 1
|
|
1:18:19
|
phone, I'm realize I'm on a corporate headquarter phone, but
|
|
1:18:21
|
just imagine this was the Branch 1 phone, so it's calling
|
|
1:18:24
|
out to +1512, the egress called party transformation for +1206
|
|
1:18:34
|
would not apply, but +1 would apply and is more
|
|
1:18:37
|
specific than plus. That tells it to drop the plus, leave the 1
|
|
1:18:44
|
and send it out to the gateway
|
|
1:18:48
|
the gateway which is Branch 1, in this case MGCP, sends it out
|
|
1:18:52
|
as -- actually I'm sorry, it would send it out -- maybe
|
|
1:18:57
|
tail end hop-off tried, but the WAN is down, so it
|
|
1:19:00
|
couldn't reach that Branch 1 gateway, so it tries my backup
|
|
1:19:04
|
which is myself, my local
|
|
1:19:07
|
and it sends out -- it says ok, +1206 doesn't match
|
|
1:19:12
|
+1 does, strip the plus
|
|
1:19:16
|
send it out as 1512
|
|
1:19:21
|
It gets to the inbound VoIP dial peer
|
|
1:19:25
|
of the corporate headquarter gateway
|
|
1:19:28
|
that prefixes a 9, it then is able to match the outbound
|
|
1:19:32
|
dial peer of the POTS dial peer and route out as a national or
|
|
1:19:36
|
long distance number.
|
|
1:19:39
|
Ok, so again, anywhere I'm at in CUCM at this point
|
|
1:19:45
|
I will be using plus dial numbers
|
|
1:19:48
|
for anything, any speed dial, anything where a user is not
|
|
1:19:55
|
physically dialing the digits.
|
|
1:19:57
|
Ok,
|
|
1:20:03
|
ok, so are there any questions on anything that we've done
|
|
1:20:06
|
in globalization and localization and I might even open it up --
|
|
1:20:10
|
I will open it up even further to say are there any questions
|
|
1:20:14
|
at all on the dial plan in general because at this point
|
|
1:20:19
|
I'm going to take questions and then we're going to
|
|
1:20:22
|
pause for a break and then we're going to move on to
|
|
1:20:26
|
other things in CUCM which we only have a couple left
|
|
1:20:29
|
unified mobility and things like high availability and then
|
|
1:20:36
|
we're going to move on to our other components, our
|
|
1:20:42
|
CME, our UCCX obviously in many modules to come, but
|
|
1:20:50
|
I'm simply saying we're about to be using the dial plan rather
|
|
1:20:53
|
than discussing it so much anymore.
|
|
1:20:55
|
Ok, we have a question.
|
|
1:20:58
|
"Is there a chance that we have to use site codes in
|
|
1:21:00
|
the CCIE lab?" Can you be a bit more specific on what you mean
|
|
1:21:04
|
by site codes?
|
|
1:21:06
|
I could guess, but I want to make sure I'm answering your question
|
|
1:21:10
|
how you're envisioning it.
|
|
1:21:15
|
And you go on to say, "Like having a two or three-digit site
|
|
1:21:17
|
code for every site that users can use to dial between different
|
|
1:21:21
|
sites across the country or even worldwide."
|
|
1:21:25
|
That's what I thought you meant. I just wanted to make sure that
|
|
1:21:27
|
I could clarify.
|
|
1:21:29
|
Is there the possibility that they could ask you to do that?
|
|
1:21:32
|
Absolutely.
|
|
1:21:34
|
Not only is it very often used for companies that
|
|
1:21:42
|
have even multiple clusters and the two or three-digit
|
|
1:21:47
|
site code may actually be a part of their standard E.164
|
|
1:21:52
|
number, but a lot of times isn't. The two or three-digit
|
|
1:21:56
|
site code, three digit being a very common one that for instance...
|
|
1:22:02
|
actually yeah, very common one that Cisco uses, so maybe
|
|
1:22:08
|
4-digit extensions and a 3-digit site code for a 7-digit
|
|
1:22:11
|
number and the first three digits of the site code might
|
|
1:22:13
|
not even have anything to do or might not be a part of
|
|
1:22:17
|
your normal E.164 direct inward dial number
|
|
1:22:26
|
however is something that has arbitrarily been set up
|
|
1:22:30
|
with purpose and design, but essentially the numbers picked
|
|
1:22:34
|
arbitrarily for the sites maybe corresponds to other sort of
|
|
1:22:38
|
billing codes or something else within the organization for the
|
|
1:22:42
|
given site, but regardless, that's very much something
|
|
1:22:46
|
that you could expect to see, sure.
|
|
1:22:49
|
I don't see how it would complicate your situation
|
|
1:22:54
|
too very much. It certainly -- let's say if I had a 3-digit
|
|
1:23:00
|
extension -- let's get rid of this because
|
|
1:23:04
|
this is not proper for that particular number.
|
|
1:23:07
|
But let's say I had a 4-digit extension
|
|
1:23:12
|
I could either make my directory numbers, all directory numbers
|
|
1:23:17
|
for let's say site corporate headquarter is site 101
|
|
1:23:23
|
I could either add that to my directory number or
|
|
1:23:26
|
I could create translation patterns
|
|
1:23:31
|
that these translation patterns essentially said, 'If you dial 101
|
|
1:23:37
|
XXXX in a given partition...' -- and I'll discuss that in a minute.
|
|
1:23:44
|
'...then do something for the call party's external phone number mask
|
|
1:23:57
|
It's typically easiest if they become part of the DNs
|
|
1:24:01
|
and you use translation patterns to translate down
|
|
1:24:07
|
but it can actually be used where I'm using translation patterns
|
|
1:24:10
|
to translate up, in other words DNs themselves are only four digits
|
|
1:24:14
|
and I'm prefixing on a 101, but the called party actually
|
|
1:24:19
|
is just XXXX and the called party resides in the...
|
|
1:24:29
|
sorry, the mask XXXX
|
|
1:24:32
|
and the called party resides within a given partition that
|
|
1:24:38
|
can only be seen by the calling search space so that DNs can't see
|
|
1:24:42
|
each other or else -- again what I think is typically more
|
|
1:24:47
|
likely is that those -- all the extensions are actually
|
|
1:24:55
|
the 7-digit extensions so that things like calling party will
|
|
1:25:03
|
actually fill out with your site code whenever you go to dial
|
|
1:25:07
|
between and that instead I have -- I still have each site's
|
|
1:25:11
|
DNs in separate partitions, but then if I'm going to dial let's say
|
|
1:25:16
|
from a corporate headquarter phone to a corporate headquarter
|
|
1:25:20
|
phone and I don't want to dial the 3-digit extension before that
|
|
1:25:22
|
I only want to dial a 4-digit extension for instance
|
|
1:25:25
|
then I say, "If you're dialing XXXX..." And again, you probably wouldn't
|
|
1:25:32
|
do any X because that would eliminate the secondary dial tone
|
|
1:25:37
|
as we saw earlier from nine or zero initiated calls, so
|
|
1:25:42
|
maybe 1 through 9 XXX
|
|
1:25:45
|
I'm sorry
|
|
1:25:47
|
1 through 8, so not zero and not nine XXX
|
|
1:25:53
|
and you're dialing within or you have access to dial
|
|
1:25:58
|
to the corporate headquarter phone partition, then you go
|
|
1:26:04
|
through a given CSS and it prefixes 101 quadruple X
|
|
1:26:12
|
or like this prefix to the mask or you can even do
|
|
1:26:17
|
101 and then the mask. They both work the same.
|
|
1:26:19
|
Not a problem, but to answer your question in general
|
|
1:26:22
|
is there a possibility that you could have site codes? Yes.
|
|
1:26:26
|
There is the possibility. Someone else asked the question,
|
|
1:26:29
|
"What are the chances to be asked in the lab to create
|
|
1:26:32
|
intercluster trunks and combine this with globalized call routing
|
|
1:26:36
|
like the one that I had in deep dive 11?"
|
|
1:26:39
|
So as this person's mentioning, I did cover that in deep dive 11
|
|
1:26:48
|
I don't have another cluster setup at this moment. I actually
|
|
1:26:51
|
I don't have it spun up right now, so I can't show that
|
|
1:26:55
|
example, but if you are interested in seeing that example both with
|
|
1:27:00
|
SIP with and H.323 I think I covered both in the intercluster
|
|
1:27:04
|
linking and that's for 7, 8 obviously has a lot more
|
|
1:27:07
|
functionality with SIP and the preferred intercluster
|
|
1:27:11
|
method of linking in really in CUCM 7, but especially
|
|
1:27:16
|
in 8 where there's a lot of additional functionality.
|
|
1:27:18
|
In the lab, is that a possibility?
|
|
1:27:22
|
Well, you didn't ask is it a possibility. You asked
|
|
1:27:25
|
what are the chances. First I'll say it's a possibility, but I think
|
|
1:27:30
|
the chances are fairly slim or fairly low. It's not that it's
|
|
1:27:36
|
impossible for them to ask you to do that, but a couple things
|
|
1:27:40
|
if they have you -- first of all, if they have you linked
|
|
1:27:48
|
to another cluster, then it's additional work that you need
|
|
1:27:52
|
to do to set up that cluster or maybe they already have it
|
|
1:27:57
|
set up for you
|
|
1:27:59
|
and maybe it's not even in your administrative control.
|
|
1:28:01
|
It is an additional phone to set on your desk and let's be
|
|
1:28:06
|
honest just in terms of physical desks. There's only
|
|
1:28:09
|
so much desk space for so many phones, they can't just
|
|
1:28:12
|
keep adding phones infinitely unless they want the -- you're
|
|
1:28:16
|
testing facility to look like a call center -- your desk
|
|
1:28:21
|
I should say to look like a call center.
|
|
1:28:25
|
But one additional phone on the desk probably not that big
|
|
1:28:27
|
of a deal -- I guess it's possible, but the only way
|
|
1:28:33
|
that I could see that they would do it is if they made you
|
|
1:28:40
|
set up both sides of the trunk, either H.323 intercluster trunk or
|
|
1:28:45
|
SIP and then therefore you set up the -- not necessarily
|
|
1:28:53
|
the call routing, maybe they already had the trunk and
|
|
1:28:56
|
the services activated, the phone registered, the trunk
|
|
1:29:00
|
created, but they're having you do digit manipulation or just
|
|
1:29:03
|
test the plus dialing ... and things like that.
|
|
1:29:09
|
I don't think it's quite as likely.
|
|
1:29:12
|
I think there's definitely a possibility and a high probability
|
|
1:29:17
|
depending on when you go sit the exam that you could see
|
|
1:29:20
|
one or possibly even two, but probably one CME cluster
|
|
1:29:26
|
or CME site and a CUCM site, but then again it's also just as
|
|
1:29:31
|
likely that you go and sit the exam and all sites are or all
|
|
1:29:36
|
phones at all sites are registered to a primary cluster.
|
|
1:29:39
|
There's really -- there's pluses and minuses with everything.
|
|
1:29:43
|
If they only have three sites to test with unless they have this
|
|
1:29:47
|
sort of fourth pseudo site that's like your mentioning
|
|
1:29:50
|
maybe another cluster, another CUCM cluster that
|
|
1:29:54
|
is sort of outside your normal topology and normal control
|
|
1:29:58
|
but other than that, if they only have three sites to
|
|
1:30:01
|
deal with, then as soon as they begin taking away
|
|
1:30:08
|
from phones being registered to CUCM and then either being
|
|
1:30:13
|
registered to another cluster, another CUCM cluster or
|
|
1:30:16
|
secondary or a CME, they take away the complexity of how you
|
|
1:30:22
|
have to create your globalized and localized patterns, so
|
|
1:30:27
|
you could view that as a good thing, but then they potentially
|
|
1:30:30
|
increase your complexity of dealing with H.323 gatekeeper
|
|
1:30:37
|
in between. They really don't I don't think too very much increase
|
|
1:30:42
|
the complexity of any IOS digit manipulations as you would
|
|
1:30:46
|
have to do in CME because you're already going to have to do those
|
|
1:30:52
|
whether you have a SIP gateway, SIP trunk,
|
|
1:30:55
|
SIP gateway to a PRI or whether you have a H.323
|
|
1:30:59
|
gateway to a PRI, you're still going to have digit manipulation in IOS
|
|
1:31:04
|
so whether it's one of those two or whether it's CME
|
|
1:31:07
|
not too much complexity add there; however, it could be
|
|
1:31:13
|
asked to be routed through either a CUBE or an H.323
|
|
1:31:18
|
gatekeeper or both in which case you have that added complexity
|
|
1:31:22
|
but again, it's taking away from all of the globalized and localized
|
|
1:31:26
|
complexity if all the phones were registered to the same
|
|
1:31:30
|
CUCM cluster.
|
|
1:31:32
|
So if you look at it really you should study for everything and
|
|
1:31:37
|
understand everything well, but the truth of the matter is
|
|
1:31:40
|
I don't think that any one particular topology or setup
|
|
1:31:43
|
is any more difficult than another.
|
|
1:31:46
|
I just think that they happen to place the complexities
|
|
1:31:50
|
of what it is you have to do in different places
|
|
1:31:56
|
whether it's in the digit manipulation in CUCM for
|
|
1:31:59
|
globalization and localization and everything that we've shown
|
|
1:32:01
|
you can do there or whether it's in the gatekeeper and the
|
|
1:32:05
|
CUBE -- I couldn't answer the exact
|
|
1:32:10
|
question of what are the chances because --
|
|
1:32:14
|
in other words, I couldn't give you an actual percentage
|
|
1:32:16
|
breakdown for two reasons one: if I knew, it would be
|
|
1:32:20
|
breaking NDA to tell you, but even -- I don't know simply
|
|
1:32:27
|
because they change the lab about every three months anyhow
|
|
1:32:30
|
so even if any one person let's just say hopefully you're
|
|
1:32:35
|
-- no one is talking to their friends that have taken the lab
|
|
1:32:39
|
and asking them or even listening to information specific
|
|
1:32:42
|
about the questions on the exam, but hypothetically speaking
|
|
1:32:46
|
even if you had heard something specific that was on the exam
|
|
1:32:50
|
it's really not of you're used to try to memorize or study
|
|
1:32:54
|
to that particular scenario because it's very likely that
|
|
1:32:57
|
by the time you go sit the exam, you won't have the same
|
|
1:33:01
|
test, in fact -- of tests for the entire exam, for the entire Voice exam
|
|
1:33:10
|
that can be rearranged anyhow, so...
|
|
1:33:16
|
but I don't think that there is a high likelihood of that
|
|
1:33:20
|
it was part of the deep dive that we were going as deep as
|
|
1:33:23
|
we could, so I guess that's probably all I could say is I think it would
|
|
1:33:27
|
take away from desk real estate and take away from your --
|
|
1:33:31
|
take away from their ability to have you do other things that are
|
|
1:33:33
|
a little bit more complex.
|
