|
0:00:14
|
We’re back and we’re gonna take a look at our next task 14.2
|
|
0:00:18
|
Device Mobility Movement between sites and between countries.
|
|
0:00:23
|
We’re told to provision Jack’s phone to be able to
|
|
0:00:27
|
pick up and move his phone to the Branch 2 site
|
|
0:00:30
|
and to ensure that when he arrives
|
|
0:00:32
|
and attaches his phone to the Branch 2 subnet
|
|
0:00:34
|
then he takes on some of the characteristics of the Branch 2
|
|
0:00:37
|
device pool, phone device pool called DP Branch 2 phones.
|
|
0:00:42
|
Again for the recording, the Corporate Headquarter subnet hasn’t changed
|
|
0:00:46
|
ut the Branch 2 subnet will be 177.3.11.0/24
|
|
0:00:52
|
and for your self-study, we’ll create it as
|
|
0:00:55
|
192.168.10.170/32.
|
|
0:01:01
|
Let’s go ahead and we will create this new device mobility info.
|
|
0:01:09
|
Copy one of these
|
|
0:01:12
|
copy the branch1, we’ll call it Branch 2
|
|
0:01:16
|
with the second octet being .3/24
|
|
0:01:21
|
and we’ll associate it with a Branch 2 phones device pool
|
|
0:01:25
|
and then we’ll copy this one to call it self-study
|
|
0:01:32
|
Change the subnet mass first
|
|
0:01:35
|
to 192.168.10.170
|
|
0:01:43
|
good, Branch 2 phones, go back out and we should have
|
|
0:01:48
|
three of these now or three sets I should say
|
|
0:01:53
|
and we’re going to need to add a new device mobility group
|
|
0:01:59
|
called DMG_Netherlands
|
|
0:02:05
|
because that’s where the Branch 2 site is, it doesn’t really matter what we call it
|
|
0:02:09
|
It just needs to be that we have to device mobility groups
|
|
0:02:14
|
we’ll need to add of course a new physical location, so we copy this one
|
|
0:02:20
|
and call it PL Branch 2. Back to find list,
|
|
0:02:25
|
so now we got three physical locations as well. So all we need to do
|
|
0:02:30
|
is go to the device pool for Branch 2 phone
|
|
0:02:36
|
and modify the physical location to be PL Branch 2
|
|
0:02:39
|
and the device mobility group to be the Netherlands
|
|
0:02:43
|
Now, notice that we have all of this populated
|
|
0:02:48
|
he device mobility calling search space
|
|
0:02:51
|
and calling party transformation CSS most specifically
|
|
0:02:55
|
set to Branch 2 PSTN and Branch 2 phones respectively
|
|
0:02:59
|
so that we see that it does not take on these characteristics
|
|
0:03:03
|
because it’s moving between
|
|
0:03:05
|
device mobility groups or between countries really
|
|
0:03:09
|
I don’t wanna take on new calling search space because that would mean taking on
|
|
0:03:12
|
new PSTN dialling
|
|
0:03:17
|
test to this. We would have to dial in a different fashion.
|
|
0:03:23
|
We’re gonna go ahead and reset or restart,
|
|
0:03:26
|
actually there’s really no reason that we need to restart
|
|
0:03:29
|
this device mobility, sorry, this device pool.
|
|
0:03:32
|
Let’s gonna restart my two Branch 2 phones
|
|
0:03:35
|
But the only thing that’s really gonna need to take
|
|
0:03:38
|
these two settings that we just changed, the physical location
|
|
0:03:41
|
and device mobility group
|
|
0:03:43
|
is going to be the Corporate Headquarter phone,
|
|
0:03:48
|
branch1 177.2.11 subnet
|
|
0:03:56
|
So at this point, while we read the rest of the task,
|
|
0:04:01
|
probably figure out what it means or going to say already
|
|
0:04:07
|
from the last task, at least most of it. I’m gonna go ahead and
|
|
0:04:11
|
without making you watch disconnect Desmond Hume Branch 2 Phone 1
|
|
0:04:17
|
and connect the Corporate Headquarter
|
|
0:04:24
|
Corporate Headquarter Phone 1
|
|
0:04:26
|
over to the Branch 2 subnet
|
|
0:04:29
|
and then reconnect the branch1 phone that we had taken off
|
|
0:04:35
|
3001 Branch 2 phone 1 will be disconnected
|
|
0:04:39
|
on its place will Corporate Headquarter Phone 1 as a visiting phone
|
|
0:04:46
|
If we take a look at right now,
|
|
0:04:49
|
we see that branch1 Phone 1 is off.
|
|
0:04:53
|
It still says Corporate Headquarter Phone 1 is registered but
|
|
0:04:56
|
it’s not. If we click on that IP, it’ll not go anywhere.
|
|
0:05:00
|
It’s in the process of
|
|
0:05:05
|
powering up right now. It just hasn’t
|
|
0:05:07
|
exceeded its hello timer so CUCM doesn’t know that it’s dead.
|
|
0:05:13
|
It was 177.2.11.54
|
|
0:05:16
|
it’s unregistered. Let’s go back and take a look at with the rest of our task tells us.
|
|
0:05:21
|
Ensure that while Jack’s Corporate Headquarter Phone 1 is visiting
|
|
0:05:25
|
that all of these following work properly
|
|
0:05:28
|
Class restriction remains the same, needs to work,
|
|
0:05:31
|
proper date and time which is going to be CET+1
|
|
0:05:34
|
As a difference from
|
|
0:05:38
|
Corporate Headquarter phone2, it needs to be
|
|
0:05:43
|
GMT-8, this is GMT+1. It should be 9 hours ahead
|
|
0:05:49
|
VOIP calls to both Corporate Headquarter phone2
|
|
0:05:53
|
and branch1 Phone 1, use G.729
|
|
0:05:56
|
G.711 over to Branch 2 phone2.
|
|
0:06:00
|
By the way, that Corporate Headquarter Phone 1 just booted up
|
|
0:06:03
|
and then it’s now resetting again because
|
|
0:06:05
|
device mobility mode found the subnet it was on and it’s
|
|
0:06:08
|
now resetting with the new parameters that it was given.
|
|
0:06:12
|
Multicast media on hold or multicast music on hold needs to still work.
|
|
0:06:18
|
Branch2 where to lose connectivity, there should be SRST the dot router.
|
|
0:06:22
|
All calls that Jack attempts to make should
|
|
0:06:26
|
only go up to Branch 2 gateway primarily
|
|
0:06:28
|
except 911 call should only
|
|
0:06:31
|
go out the Corporate Headquarter gateway. Wait a minute,
|
|
0:06:34
|
what do you mean should go up the Branch 2 gateway primarily?
|
|
0:06:38
|
I thought you said that the CSS
|
|
0:06:41
|
doesn’t get passed. Go back and look at the device pool
|
|
0:06:47
|
open that with new window for Branch 2 phones.
|
|
0:06:56
|
Pull up our phone here.
|
|
0:07:02
|
It’s already gone. All devices are in the roaming location,
|
|
0:07:08
|
found at the bottom. I was too slow
|
|
0:07:12
|
You have to pull it up. I can do settings
|
|
0:07:16
|
to network1 for IPV4 and we can see that we are at
|
|
0:07:21
|
177.3.11.55
|
|
0:07:27
|
Back to what we’re saying, I thought you’d said, Mark,
|
|
0:07:30
|
that device mobility calling search space
|
|
0:07:32
|
would not be updated
|
|
0:07:35
|
That’s correct. If we are between
|
|
0:07:38
|
device mobility group or between countries
|
|
0:07:41
|
then none of this information is passed.
|
|
0:07:44
|
If that’s the case, then how can we possibly make the call
|
|
0:07:49
|
go out the Branch 2 gateway
|
|
0:07:51
|
however, 911 calls go up the Corporate Headquarter gateway
|
|
0:07:55
|
even if this is not totally the desired
|
|
0:07:57
|
functionality in other words in really life, you wouldn’t want
|
|
0:08:00
|
911 calls really to still work but
|
|
0:08:05
|
within 7.0.0, there’s no way that we
|
|
0:08:08
|
we can really handle that. Within 701
|
|
0:08:10
|
we could handle it the GEO location routing, we could block it
|
|
0:08:13
|
but in 700, there’s no way to stop
|
|
0:08:15
|
those 911 calls from still going out there
|
|
0:08:20
|
device mobility roaming phones home gateway.
|
|
0:08:24
|
So Jack’s styling habit, wait a minute
|
|
0:08:26
|
styling habit should not have to change
|
|
0:08:28
|
911 calls go out the home gateway
|
|
0:08:31
|
but the rest of the calls go out the Branch 2 gateway
|
|
0:08:36
|
If jack dials internationally to reach
|
|
0:08:40
|
PSTN phones that habit to be at the Branch 2
|
|
0:08:42
|
Branch 2 country code and geographic area code
|
|
0:08:44
|
such as 9.011.31.20.703.7333
|
|
0:08:50
|
such as 9.011.31.20.703.7333he should still be able to do so
|
|
0:08:53
|
but it goes out the Branch 2 gateway.
|
|
0:08:56
|
Let’s see how that’s gonna work
|
|
0:09:00
|
AAR does not need to function properly
|
|
0:09:03
|
ensure calls made into Jack’s phone display exactly as they would
|
|
0:09:07
|
as if you were back at the Corporate Headquarter site
|
|
0:09:10
|
Let’s try some basic things first.
|
|
0:09:14
|
First of all, let’s call back to 1002.
|
|
0:09:21
|
Just so it displays a lot faster. I’m not going to
|
|
0:09:25
|
pull up remote phone for both phone displays
|
|
0:09:29
|
Instead, I have G.729
|
|
0:09:31
|
My stats, my stream, refresh
|
|
0:09:35
|
show that I’m 177.3.11
|
|
0:09:38
|
to 177.1.11
|
|
0:09:41
|
Those are phone to phone G.729
|
|
0:09:46
|
What about if I were to call to branch1
|
|
0:09:50
|
2001
|
|
0:09:56
|
Let’s update this, refresh
|
|
0:10:00
|
So now I’m 177.3.11, myself
|
|
0:10:03
|
to 211 codec G.729
|
|
0:10:08
|
That’s good. What about calls to 3002
|
|
0:10:21
|
Now, I’m calling on local subnet here.
|
|
0:10:25
|
Let’s refresh this stream
|
|
0:10:27
|
177.3.11 to 3.11
|
|
0:10:31
|
and it looks like it’s G.729.
|
|
0:10:35
|
Take a look and see why that might be
|
|
0:10:42
|
Listen and let’s take a look at this time as well.
|
|
0:10:46
|
I’m gonna end this call and the time shows
|
|
0:10:49
|
19:57
|
|
0:10:51
|
and the Corporate Headquarter phone2 shows 10:57
|
|
0:10:56
|
basically, 11 o’clock
|
|
0:10:58
|
and this is basically 8 o’clock
|
|
0:11:01
|
so that’s exactly 9 hours ahead to the Corporate Headquarter phone
|
|
0:11:08
|
So the time is right. The date is proper.
|
|
0:11:15
|
Take a look at our settings. Here, I got region Branch 2.
|
|
0:11:27
|
Now, my Corporate Headquarter Phone 1 shows up as 177.3.11
|
|
0:11:32
|
in fact let’s just go and take a look at our
|
|
0:11:35
|
Switch 2 over here
|
|
0:11:42
|
Those CDP neighbor on branch1, we note that
|
|
0:11:45
|
BAAE
|
|
0:11:48
|
just the branch1 Phone 1 last for the MAC is back there.
|
|
0:11:53
|
Here, on Branch 2, shows,
|
|
0:11:58
|
was it A576?
|
|
0:12:01
|
Here we go, A576 is the visiting MAC address
|
|
0:12:05
|
so we all are properly over on Branch 2 gateway.
|
|
0:12:14
|
Branch 2 handed up the IP
|
|
0:12:20
|
to A576.
|
|
0:12:24
|
177.3.11.55,
|
|
0:12:27
|
looks like it did, that’s good, put that off.
|
|
0:12:33
|
So here’s our Branch 2 phone2
|
|
0:12:40
|
is using the device pool for Branch 2 phones
|
|
0:12:45
|
that has region Branch 2. Let’s go and take a look at that region.
|
|
0:12:55
|
For some reason, 2region Branch 2
|
|
0:12:58
|
2region Branch 2 is told to use G.728
|
|
0:13:01
|
so let’s just change that
|
|
0:13:07
|
711 or I supposed 722 if it got
|
|
0:13:10
|
negotiated properly and let’s do a restart.
|
|
0:13:20
|
Restarting Branch 2 phone2
|
|
0:13:31
|
it’s finally resetting Corporate Headquarter Phone 1
|
|
0:13:37
|
Vice on roaming location, let’s try that call again
|
|
0:13:46
|
over to 3002
|
|
0:13:56
|
and do a refresh
|
|
0:14:01
|
Here we got 177.3.11, 177.3.11
|
|
0:14:05
|
and we’re actually using the G.722 protocol
|
|
0:14:09
|
because it’s equal in bandwidth with 711
|
|
0:14:12
|
and this particular lab has not been disabled.
|
|
0:14:16
|
It was doing exactly what we told it to.
|
|
0:14:19
|
It was just that we happen to have
|
|
0:14:22
|
the region set to something different.
|
|
0:14:24
|
We’re good there.
|
|
0:14:27
|
We’ve already ensured G.729 back to the other two
|
|
0:14:33
|
Let’s do multicast music on hold
|
|
0:14:36
|
Let’s just call back over to 3002.
|
|
0:14:42
|
then put me on hold
|
|
0:14:52
|
Let’s do a refresh and it’s from 239.111
|
|
0:15:00
|
which to me looks like that 711
|
|
0:15:04
|
There’s no transmit code, that’s the last transmit code I received is
|
|
0:15:09
|
711. The sender code, I could not send any packets, zero packets.
|
|
0:15:13
|
It says 22 but that’s just because that was the last stream
|
|
0:15:17
|
It’s from the publisher and it’s G711
|
|
0:15:21
|
because if we take a look at
|
|
0:15:26
|
Branch 2 on music on hold servers
|
|
0:15:30
|
we have 711
|
|
0:15:32
|
Why ever it was configured like this, from our previous modules
|
|
0:15:36
|
don’t really remember exactly why we had it configured like
|
|
0:15:38
|
that maybe we were looking at streaming from the branch router
|
|
0:15:42
|
but the point is that it’s doing
|
|
0:15:44
|
exactly what we told it to do,
|
|
0:15:48
|
exactly how it’s configured for Branch 2
|
|
0:15:51
|
site and 239.111 we know that we’re listening to a multicast stream.
|
|
0:15:56
|
ut of course, go over to the Branch 2 router, do a show IP M route
|
|
0:16:01
|
and 239.111
|
|
0:16:06
|
is going out Fa00.11
|
|
0:16:11
|
and serial 001:0.1 so this is
|
|
0:16:17
|
back across the WAN as the incoming and the
|
|
0:16:20
|
outgoing is the voice VLAN over the switch2
|
|
0:16:25
|
By end of that call, do command again
|
|
0:16:33
|
Still going out, it will probably die off here in a little bit
|
|
0:16:39
|
There we go. Now, it’s coming in the serial
|
|
0:16:42
|
because it is being flooded dense mode but there is no outgoing interface list
|
|
0:16:46
|
because is no one is requesting that file any longer for that
|
|
0:16:54
|
Let’s make sure our gateways are cleared off and that they all have
|
|
0:16:58
|
debug ISTN Q931
|
|
0:17:00
|
so that we can see how calls are going to flow.
|
|
0:17:04
|
So now we’ll do the SRST last again.
|
|
0:17:07
|
All calls should go out the Branch 2 gateway
|
|
0:17:10
|
but 911 should go out Corporate Headquarter gateway
|
|
0:17:14
|
even if that wouldn’t really be what we wanted it in real life.
|
|
0:17:17
|
Let’s try this. Let’s try 911 first
|
|
0:17:23
|
We hide this stream information
|
|
0:17:27
|
bring this up here and let’s try
|
|
0:17:31
|
having Jack call 911
|
|
0:17:38
|
refreshing very fast. There he go, 911
|
|
0:17:43
|
nd going out to Corporate Headquarter gateway, Jack Shepherd.
|
|
0:17:49
|
That one works and that make sense
|
|
0:17:52
|
because we didn’t take our CSS with us
|
|
0:17:55
|
so in another words, we, now remember we had
|
|
0:17:59
|
the calling search space of the branch1
|
|
0:18:01
|
device pool last because that was the last site that we had visited.
|
|
0:18:06
|
but now we just got on a plane from Austin and flew over to Amsterdam and
|
|
0:18:12
|
we are stack to using our Corporate Headquarter device pool CSS.
|
|
0:18:18
|
Our existing device CSS if we have one configured on the device and we do.
|
|
0:18:24
|
That gateway was clearly used
|
|
0:18:28
|
for the 901 call. Let’s clear off that buffer
|
|
0:18:31
|
and let’s now make a call to, let’s say
|
|
0:18:35
|
a local number 9206
|
|
0:18:43
|
That call is not connected, I know that
|
|
0:18:47
|
certainly but it still shows connected
|
|
0:18:54
|
We’re back with that and here’s Jack’s phone.
|
|
0:18:59
|
We’re gonna call the first line here, 2065015111
|
|
0:19:03
|
So Jack will go off hook, now remember,
|
|
0:19:05
|
if Jack didn’t, if he had
|
|
0:19:09
|
and let’s just go and take a look at configuration just to be sure
|
|
0:19:13
|
if Jack had inherited the Branch 2 phones
|
|
0:19:19
|
device mobility calling search space which is
|
|
0:19:23
|
CSS dial device Branch 2 PSTN, let’s just go take a look at that,
|
|
0:19:27
|
calling search space
|
|
0:19:38
|
So here's the dial device Branch 2 PSTN
|
|
0:19:42
|
this contains the dial device Branch 2 only PSTN partition
|
|
0:19:47
|
the Netherlands partition, internal DNs and the directory.
|
|
0:19:51
|
If we take a look at translation patterns
|
|
0:19:55
|
that begin with 9, none of them are in the
|
|
0:19:59
|
partition dial device Netherlands
|
|
0:20:02
|
or Branch 2 only. What about the ones that starts with 0?
|
|
0:20:06
|
Sure, we got partition dial device Netherlands PSTN
|
|
0:20:11
|
and we also, if we go to our actual route patterns
|
|
0:20:19
|
got Branch 2 only which is 0112 and 112
|
|
0:20:25
|
Going back to our translation patterns, basically,
|
|
0:20:29
|
if we wanna look at partitions that contain NL
|
|
0:20:37
|
they either start with a 0
|
|
0:20:43
|
there’s a 0, 0, so this is 00 for National dialing
|
|
0:20:47
|
We 000 for International, 40 for secondary dial tone
|
|
0:20:51
|
and then we have 7 and 7 digits for local
|
|
0:20:54
|
or we got \+ or \+53120.
|
|
0:20:58
|
There’s nothing that begins with 9. So if Jack had inherited that
|
|
0:21:03
|
that calling search space which we
|
|
0:21:05
|
are pretty sure that he didn’t because of the 911
|
|
0:21:08
|
then he would only be able to dial
|
|
0:21:11
|
igits that begin with 0 for PSTN
|
|
0:21:13
|
and he would not be able to dial anything, in fact let’s just
|
|
0:21:17
|
be certain here real quick again
|
|
0:21:21
|
Route plan report where anything begins with a 9,
|
|
0:21:26
|
this thing in here has a partition that has a
|
|
0:21:29
|
NAL or NL or a Branch 2
|
|
0:21:35
|
Nothing that begins with 0
|
|
0:21:37
|
, nothing that begins with a 9 that has a NL
|
|
0:21:44
|
He shouldn’t be able to dial 9 if he has his own proper
|
|
0:21:48
|
I’m sorry, if he had the new calling search space but he has his own
|
|
0:21:51
|
home calling search space so he should be able to dial a 9
|
|
0:21:56
|
and do this real quick so we’ll go off hook. Jack will dial 9
|
|
0:22:02
|
and let’s say 2065015111
|
|
0:22:10
|
So Jack is dialling normal
|
|
0:22:13
|
but it got transformed to 00
|
|
0:22:17
|
is international. 0012065015111, end this call
|
|
0:22:24
|
and it went out the Branch 2 gateway.
|
|
0:22:27
|
Router1 Corporate Headquarter nope
|
|
0:22:30
|
router2 branch1 nope, router3 Branch 2
|
|
0:22:34
|
is where it went out. Jack Shepherd goes up with his country code first.
|
|
0:22:42
|
So how did this happen?
|
|
0:22:44
|
Well, it happen exactly as we told you
|
|
0:22:47
|
all calls that he attempts should
|
|
0:22:49
|
go out the Branch 2 gateways primarily. This is because
|
|
0:22:56
|
back to device pool for Branch 2 phones
|
|
0:22:58
|
that he inherited some of the
|
|
0:23:01
|
information about, he did not inherit any of these parameters
|
|
0:23:05
|
However, he did even though it doesn’t show up in a roaming
|
|
0:23:07
|
sensitive settings category or subcategory,
|
|
0:23:10
|
he did inherit local route group.
|
|
0:23:12
|
In fact, if I were to advise Cisco to kinda redesign this
|
|
0:23:15
|
just this one page, I would say, put
|
|
0:23:18
|
physical location and device mobility group
|
|
0:23:20
|
up and device pool settings
|
|
0:23:23
|
because that doesn’t get inherited, that’s just how we
|
|
0:23:27
|
make distinctions between
|
|
0:23:30
|
device mobility related settings
|
|
0:23:32
|
and then put local route group down in the roaming
|
|
0:23:35
|
sensitive settings because this is the area that all of this
|
|
0:23:38
|
except for the last two, always gets passed.
|
|
0:23:41
|
As long as we’re between physical, we
|
|
0:23:43
|
always get this information
|
|
0:23:46
|
here if we are between
|
|
0:23:54
|
pool locations, always take this information.
|
|
0:24:06
|
But if we are
|
|
0:24:19
|
between, I actually should’ve
|
|
0:24:22
|
set up there physical locations
|
|
0:24:30
|
rather within in device mobility group or within the country.
|
|
0:24:44
|
Then and only then, we will take
|
|
0:24:56
|
everything
|
|
0:25:02
|
We did still take a local route group
|
|
0:25:05
|
and that’s why the calls going out the local gateway.
|
|
0:25:09
|
If we did take a local route group
|
|
0:25:11
|
then let’s follow the path of what happened.
|
|
0:25:13
|
We already know what calling search space we have
|
|
0:25:16
|
we already know what we dialled because we dialled it,
|
|
0:25:19
|
we dialled pattern that began with a 9
|
|
0:25:22
|
and had 10 digits. This is the only
|
|
0:25:25
|
pattern that we could have taken,
|
|
0:25:29
|
it drops the 9. If we take a look at called
|
|
0:25:32
|
party transformation, we dropped pre dot
|
|
0:25:34
|
we prefix a +1 so this is now a globalized number +1
|
|
0:25:38
|
and we dial 2065015111
|
|
0:25:42
|
and it sends it on to be matched by the digit analysis engine again.
|
|
0:25:47
|
any partitions in the CSS
|
|
0:25:49
|
translation pattern to route pattern SLRG
|
|
0:25:52
|
PSTN CSS. The only one in there
|
|
0:25:56
|
is the partition of the same name
|
|
0:26:07
|
translation pattern. There’s no other translation patterns that could cause a reoccurring
|
|
0:26:13
|
or teclical routing loop
|
|
0:26:17
|
so how about partition contains this information here in route pattern
|
|
0:26:21
|
We only have one, so it matches this. This sends it off to SLRG,
|
|
0:26:28
|
SLRG goes to the local gateway
|
|
0:26:31
|
so the local gateway is Branch 2
|
|
0:26:37
|
MGCP gateway. Go down here to the Branch 2 MGCP gateway.
|
|
0:26:44
|
What happens? The called party transformation CSS
|
|
0:26:51
|
searched for a match for +12065015111 PSTN number.
|
|
0:27:03
|
Let’s go and look at this called
|
|
0:27:05
|
party transformation with a partition of the same name.
|
|
0:27:09
|
Really looking at partition contains 2
|
|
0:27:32
|
Really that CSS has the Branch 2 partition but then also
|
|
0:27:36
|
.NL. Partition contains either NL
|
|
0:27:43
|
or let’s add partition
|
|
0:27:50
|
contains gateway. It’s not liking that,
|
|
0:27:57
|
for some reason, it’s doesn’t like any of my filters.
|
|
0:28:01
|
It might just be a bug but we cannot see if I just sort these partitions.
|
|
0:28:06
|
Here, I got my ELS, there’s three of them
|
|
0:28:12
|
and then here’s my 1 Branch 2 gateway right here
|
|
0:28:15
|
So it’s not +31, it’s not +31 here, it’s not +112, it is +1
|
|
0:28:25
|
but it’s +1206. So it only matches this
|
|
0:28:33
|
called party transformation pattern right here
|
|
0:28:35
|
which says to strip the pre dot
|
|
0:28:37
|
and prefix a 00.
|
|
0:28:42
|
Because of that, the call goes up the local gateway
|
|
0:28:45
|
because we already had everything set up from globalization and localization
|
|
0:28:48
|
way back in module 10. It goes out the local gateway
|
|
0:28:54
|
routed properly. We still,
|
|
0:28:58
|
because of globalization and localization
|
|
0:29:00
|
combined with device mobility,
|
|
0:29:03
|
we still save WAN bandwidth
|
|
0:29:08
|
ot using our home gateway except for
|
|
0:29:12
|
that only match
|
|
0:29:14
|
and route out there which is our emergency services patterns
|
|
0:29:21
|
but the numbers transformed and therefore the carrier routes it in the proper fashion
|
|
0:29:27
|
Maybe we wanted it to go out the Corporate Headquarter gateway
|
|
0:29:31
|
That’s going to get back into tail and hop off.
|
|
0:29:34
|
We got a task with that coming up but for right now, it is doing what we want
|
|
0:29:38
|
Let’s try dialling internationally from the phone.
|
|
0:29:42
|
Let’s try going off hook on Jack’s phone
|
|
0:29:45
|
and dialling 901131207037333
|
|
0:29:56
|
this one I have to wait for interdigit time out. I’ll hit the #,
|
|
0:30:01
|
that it’s coming from
|
|
0:30:06
|
the international number of 12065011001
|
|
0:30:09
|
going out to Branch 2 gateway as a local call
|
|
0:30:21
|
Call is actually sent out as a local call.
|
|
0:30:23
|
Again, it’s the same exact things, standard local route group is what
|
|
0:30:27
|
routed it and then the called party transformation
|
|
0:30:30
|
matched this as the best match, +1
|
|
0:30:34
|
When the call went out, our translation pattern globalized it to a +31
|
|
0:30:40
|
+3120 matches, we drop pre dot
|
|
0:30:44
|
There’s only 7 digits left, we send it out to subscriber.
|
|
0:30:47
|
The call went out as called party subscriber local with 7 digits.
|
|
0:30:53
|
Globalization and localization once again saved the day.
|
|
0:30:57
|
So we've met that
|
|
0:31:00
|
AAR does not need to function properly and it’s not going to.
|
|
0:31:04
|
The reason is, again if we go to device pool,
|
|
0:31:09
|
Branch 2 we’re not taking on a new AAR group or CSS
|
|
0:31:16
|
and so it’s, actually we’re using the same CSS anyway
|
|
0:31:22
|
but AAR is not going to function necessarily properly
|
|
0:31:29
|
especially because of the fact that we have our own
|
|
0:31:35
|
our own primary local gateway.
|
|
0:31:39
|
AAR might function in some instances.
|
|
0:31:42
|
There are limitations. It does not have to function properly
|
|
0:31:46
|
hen you’re roaming to another country. The SRND tells us this, by the way.
|
|
0:31:52
|
Ensure that calls made into Jack’s
|
|
0:31:55
|
phone display as if he were in the Corporate Headquarter site
|
|
0:31:58
|
so let’s bring up this and the PSTN phone and let’s dial in
|
|
0:32:03
|
from this phone, 2065011001.
|
|
0:32:14
|
This actually is showing up with 001206,
|
|
0:32:18
|
so why is this showing up with the same
|
|
0:32:22
|
the same way that he would see it if he were
|
|
0:32:25
|
actually at the Branch 2 site. Again, this gets back to the phone
|
|
0:32:30
|
we told the phone Corporate Headquarter Phone 1 to use
|
|
0:32:34
|
device pool so it does have a new device pool
|
|
0:32:37
|
and it’s basically saying, “This is my new device pool.”
|
|
0:32:40
|
Now, these aren’t overriding what is on his phone, however,
|
|
0:32:47
|
so he can still dial his same fashion, he still dials with his
|
|
0:32:52
|
9 for the secondary dial tone and dial as if he was in the US
|
|
0:32:55
|
However, the calling party transformation, it was told to use
|
|
0:33:00
|
from the device pool and this is set to something else
|
|
0:33:04
|
so if he wanted to travel internationally and we didn’t want it to show up
|
|
0:33:07
|
in the same way that the other
|
|
0:33:11
|
international sites were showing up,
|
|
0:33:14
|
then we either create a whole separate device pool for him
|
|
0:33:17
|
that we’d put on physical location DMG
|
|
0:33:22
|
Netherlands and we’d associate that subnet
|
|
0:33:25
|
for Branch 2 to the new device pool
|
|
0:33:27
|
hat was just for him while he is travelling and have his own
|
|
0:33:32
|
Corporate Headquarter Phone 1, we could do that
|
|
0:33:35
|
In fact, let’s just go ahead and do that real quick.
|
|
0:33:38
|
Branch 2 phones actually, we call it Branch 2
|
|
0:33:45
|
Corporate Headquarter phone
|
|
0:33:56
|
device mobility and
|
|
0:34:06
|
get this to calling party for Corporate Headquarter phones
|
|
0:34:14
|
save, thus 0 numbers currently
|
|
0:34:19
|
We got this new device pool. How do we associate the phone to it
|
|
0:34:24
|
with device mobility info for Branch 2 phones?
|
|
0:34:28
|
We’re going to associate this, actually, let’s just leave it to the Branch 2 phones
|
|
0:34:36
|
That’s fine. The phone is already resetting.
|
|
0:34:51
|
Meantime, the only thing we have to do is check SRST.
|
|
0:34:56
|
As long as the SRST is set up properly, then it’s going to
|
|
0:35:00
|
fall back just as we told it to
|
|
0:35:07
|
properly to branch1. All we have to do
|
|
0:35:10
|
is shut down the serial interface to the Branch 2
|
|
0:35:13
|
Corporate Headquarter Branch 2 WAN link. The phone is already restarting.
|
|
0:35:29
|
Now, it’s resetting again
|
|
0:35:33
|
came back up, found device mobility
|
|
0:35:36
|
found a new subnet, found a new device
|
|
0:35:39
|
pool that it’s registered to, got the new settings
|
|
0:35:41
|
including calling party, new calling party transformation CSS
|
|
0:35:45
|
and now it’s resetting with those
|
|
0:35:50
|
parameters to have those parameters take effect.
|
|
0:35:59
|
Try these with the real labs so that you’re not bored just watching this happen
|
|
0:36:03
|
It these were the real labs, you would not be sitting here, doing what I’m doing which is
|
|
0:36:08
|
no talking or just waiting for this phone to come back up.
|
|
0:36:12
|
Maybe you’d written down some questions for the proctor, now would be a great time to go ask him
|
|
0:36:17
|
or her or maybe you had
|
|
0:36:21
|
something else to do but find something else to do, don’t just sit here
|
|
0:36:25
|
times of restarts and things like that
|
|
0:36:28
|
and wait. Here we go, device and roaming location
|
|
0:36:32
|
and just wait for your
|
|
0:36:35
|
update, restart or whatever to take effect.
|
|
0:36:38
|
Let’s dial back in.
|
|
0:36:44
|
Now, the call’s coming in how we would expect it to
|
|
0:36:47
|
206. If I had to called that same number from an international
|
|
0:36:53
|
line even though I’m at the Branch 2 site.
|
|
0:36:59
|
Now, the call’s coming in according to my
|
|
0:37:01
|
calling party transformation CSS, 01131.
|
|
0:37:06
|
Now I’m used to seeing it presented
|
|
0:37:08
|
however, let’s just make sure that I still have the proper
|
|
0:37:12
|
kill all of our scroll back buffers on all of our sites
|
|
0:37:21
|
dialling our from the phone. Let’s dial, go off hook and dial
|
|
0:37:26
|
901131207037333#
|
|
0:37:39
|
It’s still going out local gateway being formatted as a local call,
|
|
0:37:44
|
display updates and shows that
|
|
0:37:47
|
It’s still functioning as we would expect it to
|
|
0:37:53
|
with the new device pool that we just created
|
|
0:37:57
|
however, we created it specifically so that we could
|
|
0:38:04
|
have only our
|
|
0:38:07
|
traditional, what we’re used to as our
|
|
0:38:10
|
calling party transformation CSS.
|
|
0:38:14
|
Really looked at device mobility and
|
|
0:38:16
|
broken it down, I think it as far as we can.
|
|
0:38:20
|
Again, it’s really not that
|
|
0:38:23
|
much in terms of difficulty. It’s mainly conceptual.
|
|
0:38:26
|
Once you get over the concept and you have that nailed, got that down, then
|
|
0:38:33
|
the actual configuration for it, there really isn’t a lot there to have to do.
|
