|
0:00:15
|
So, let’s begin and let’s take a look at what the situation looks like
|
|
0:00:21
|
if we want to take and pick up our phone
|
|
0:00:24
|
and move to a different site without device mobility.
|
|
0:00:29
|
So, here, we got an example of a guy holding a
|
|
0:00:32
|
7921 wireless phone 8211, EGN, whatever wireless phone
|
|
0:00:40
|
and in the module we’re gonna use today
|
|
0:00:42
|
we'll be physically moving our 7961 hardware phone
|
|
0:00:48
|
which wouldn’t be what you would typically do in the real world.
|
|
0:00:53
|
You would have either a Nokia dual mode GSM in 8211 phone
|
|
0:00:58
|
or you’d have something like this 7921 phone
|
|
0:01:03
|
and these are by far the two biggest reasons
|
|
0:01:06
|
that device mobility was incorporated.
|
|
0:01:09
|
But the truth is it could be anything.
|
|
0:01:11
|
It could be CIPC cell phone.
|
|
0:01:13
|
It could be CUPC.
|
|
0:01:16
|
You could be moving your hardware 7961
|
|
0:01:20
|
and/or an 89100 series phone what have you.
|
|
0:01:24
|
So, we’ll take a look at it
|
|
0:01:25
|
but there you see that this guy wants to,
|
|
0:01:29
|
looks like he’s running out the door
|
|
0:01:31
|
from the Corporate Headquarters Seattle, Washington Site in the US,
|
|
0:01:36
|
over to the Branch 1 Austin, Texas site in the US.
|
|
0:01:39
|
So, let’s take a look here.
|
|
0:01:43
|
Car comes and gets him and picks him up
|
|
0:01:45
|
and takes him to the Branch 1 site
|
|
0:01:47
|
and then he wants to go and dial a number
|
|
0:01:52
|
like he would have dialled from his Corporate Headquarter site.
|
|
0:01:57
|
So, from his Corporate Headquarter site,
|
|
0:01:59
|
in order to get to this PSTN phone that we see,
|
|
0:02:03
|
up to the top right here +31
|
|
0:02:07
|
just our Branch 2 site in the Netherlands
|
|
0:02:10
|
and then 20, so the city code of Amsterdam, and then 7037333.
|
|
0:02:17
|
This is the phone out on the PSTN.
|
|
0:02:19
|
He goes and he’s gonna dial 9-011-31-703-7333
|
|
0:02:29
|
but without device mobility, the call gets sent over the WAN
|
|
0:02:35
|
and because his device pull for his 7921 was Corporate Headquarters
|
|
0:02:44
|
and so is the gateway at the Corporate Headquarters
|
|
0:02:46
|
where his call would go out because of his device calling search space.
|
|
0:02:51
|
Line Calling Search Space.
|
|
0:02:53
|
Remember line typically defines the class of restriction
|
|
0:02:56
|
and device typically defined by selection
|
|
0:03:02
|
or site specific gateway that will be used out,
|
|
0:03:06
|
looking at local route groups or anything like that
|
|
0:03:09
|
or even just looking at the calling party being himself.
|
|
0:03:12
|
Local route group without device mobility
|
|
0:03:14
|
would be as Corporate Headquarter gateway.
|
|
0:03:17
|
So, because the region in his 7921 Corporate Headquarter device full
|
|
0:03:24
|
and the region for the Corporate Headquarter gateway where
|
|
0:03:28
|
his calls going to go out are the same region
|
|
0:03:31
|
we typically and by default have G.711
|
|
0:03:35
|
or G.722 if negotiated, but G.711 within a region.
|
|
0:03:40
|
So, his call goes across the WAN.
|
|
0:03:42
|
G.711 uses a lot more bandwidth than WAN calls are
|
|
0:03:46
|
traditionally expected to use and goes out the Corporate Headquarter gateway
|
|
0:03:52
|
while he could have just sent the call
|
|
0:03:54
|
directly out his Branch 1 gateway where he’s now visiting.
|
|
0:03:59
|
So, without device mobility, the PSTN call uses the home gateway.
|
|
0:04:04
|
The location base CAC or call admission control is unaware of the call.
|
|
0:04:09
|
Now we might pause and say that if we were using RSVP based locations
|
|
0:04:15
|
rather than just traditional locations CAC in CUCM.
|
|
0:04:19
|
If we are using RSVP based locations,
|
|
0:04:21
|
this would take care of the problem in the sense that
|
|
0:04:26
|
RSVP call admission control would be path-specific.
|
|
0:04:32
|
It's in-band essentially or in-line call admission control.
|
|
0:04:36
|
So, it would be aware first that it was a G.711 call and then also that,
|
|
0:04:41
|
to reserve the proper bandwidth if there was bandwidth available,
|
|
0:04:46
|
but traditional locations based CAC won’t take care of it.
|
|
0:04:51
|
G.711 Codec as we already mentioned uses more WAN bandwidth.
|
|
0:04:55
|
The home site, something else we haven’t mentioned,
|
|
0:04:59
|
home site's media resources are going to be selected
|
|
0:05:02
|
if he wants to set up a conference between himself
|
|
0:05:06
|
and let’s say someone out at the Branch 1 site,
|
|
0:05:09
|
not only is he going up Corporate Headquarter gateway
|
|
0:05:12
|
but he is going to be using conference bridge resources across the WAN again.
|
|
0:05:17
|
So, possibly more bandwidth used for multi party conferences
|
|
0:05:26
|
back at the Corporate Headquarter gateway.
|
|
0:05:30
|
Then AAR, if needed to be invoked, would be anchored on the home gateway.
|
|
0:05:37
|
Again, RSVP would allow call admission control
|
|
0:05:41
|
to properly know the status of the call
|
|
0:05:45
|
and therefore AAR possibly could work
|
|
0:05:48
|
but its gonna be anchored on the home gateway
|
|
0:05:50
|
and if he is trying to call out a local gateway
|
|
0:05:53
|
because there's not enough bandwidth across the WAN,
|
|
0:05:55
|
well then that's just gonna fail.
|
|
0:05:59
|
Well, let’s take a look at the same scenario but with device mobility.
|
|
0:06:04
|
So, with device mobility, car comes and picks him up and takes him over
|
|
0:06:09
|
and he dials the same number, 9-011-31-20-703-7333.
|
|
0:06:18
|
This time, it goes out the local gateway.
|
|
0:06:22
|
This is because the PSTN call uses the roaming gateway.
|
|
0:06:26
|
He basically adapts much of the parameters of the visiting device pool
|
|
0:06:35
|
location based CAC, traditional location based CAC is aware of the call.
|
|
0:06:40
|
Obviously, RSVP still will be as well either wouldn’t be any RSVP
|
|
0:06:46
|
because we’re not ever traversing a WAN link,
|
|
0:06:49
|
but traditional locations would still work properly.
|
|
0:06:55
|
WAN bandwidth is not consumed in anyway, not in this scenario.
|
|
0:07:00
|
The proper media resources are selected.
|
|
0:07:03
|
So, we again inherit much of the characteristics
|
|
0:07:06
|
or parameters of the visiting device pool.
|
|
0:07:10
|
We’ll take a look at this, specific in a moment with our task.
|
|
0:07:16
|
In AAR, since he’s going to adapt new parameters.
|
|
0:07:21
|
AAR is going to allow outgoing calls would be sourced on the new site's gateways.
|
|
0:07:28
|
Incoming AAR calls would fail.
|
|
0:07:31
|
So, keep in mind that if an incoming call were to be routed via AAR.
|
|
0:07:38
|
Now, this is not necessarily saying that
|
|
0:07:43
|
a regular inbound call to his directed or dialled number would fail.
|
|
0:07:49
|
But just if an incoming call happened to be routed because of AAR.
|
|
0:07:54
|
There wasn’t enough bandwidth between the Corporate Headquarter
|
|
0:07:58
|
TDM PSTN gateway where the calls coming into his DID
|
|
0:08:03
|
and always will because that’s where the carrier will route it.
|
|
0:08:06
|
and there’s not enough bandwidth between that gateway
|
|
0:08:10
|
and the remote site that he is visiting.
|
|
0:08:15
|
If that’s the case, locations or RSVP based locations
|
|
0:08:21
|
cause the call to fail and the incoming AAR call would fail because,
|
|
0:08:26
|
well, the call would be coming in the PSTN home gateway
|
|
0:08:29
|
but there is not enough WAN bandwidth over to his branch site.
|
|
0:08:33
|
But, if there is enough bandwidth, then the incoming call would set up properly.
|
|
0:08:44
|
So, device mobility is gonna determine that a device is moved
|
|
0:08:48
|
to a new location based on the device’s IP subnet,
|
|
0:08:53
|
its home subnet and any new possible subnet that it knows about.
|
|
0:09:01
|
We’ll get into some of the specifics about how it knows about subnets
|
|
0:09:05
|
and what we can do to make sure that it always knows about
|
|
0:09:08
|
where a phone’s location is for a default location for all phones.
|
|
0:09:15
|
It dynamically associates roaming device pool
|
|
0:09:20
|
to the devices and that moved to a different location.
|
|
0:09:27
|
Termination to extend certain features are based on the following parameters:
|
|
0:09:33
|
The question is asked, is the device roaming outside of its physical location?
|
|
0:09:39
|
If the answer to that is No,
|
|
0:09:41
|
then no updates are going to be sent to the IP phone's settings.
|
|
0:09:48
|
So, no IP phone device settings will be updated.
|
|
0:09:52
|
So, in other words, it might be roaming to a new subnet
|
|
0:09:58
|
that new subnet might be even tied to a different device pool
|
|
0:10:04
|
but if the physical location is the same.
|
|
0:10:10
|
We’ll see where we associate this.
|
|
0:10:12
|
The No settings will be updated. We’ll use all of our home settings.
|
|
0:10:17
|
If yes, if a subnet shows that we’ve not only moved to a new device pool
|
|
0:10:24
|
but the device pool also has a different physical location than its home physical location,
|
|
0:10:32
|
then we ask a few, one additional question.
|
|
0:10:38
|
Is the device roaming within its device mobility group?
|
|
0:10:44
|
If it is roaming within its device mobility group,
|
|
0:10:48
|
then all of the parameters of the visited device pool
|
|
0:10:51
|
get passed to the IP phone.
|
|
0:10:53
|
If it’s not roaming within its device mobility group, its home device mobility group,
|
|
0:10:59
|
then only some of the parameters of the visited device pool
|
|
0:11:03
|
get passed to the IP phone.
|
|
0:11:05
|
There’s a real good reason and explanation for this
|
|
0:11:08
|
and after we take a look at the next couple of slides,
|
|
0:11:10
|
hopefully, this will help clear some of this up.
|
|
0:11:13
|
So, first of all, before we go on to the next slide,
|
|
0:11:16
|
let’s just reiterate if the device mobility,
|
|
0:11:22
|
first of all, device mobility mode has to be on for a given phone.
|
|
0:11:25
|
Otherwise, not all phones by default and we can turn this on in service parameters
|
|
0:11:30
|
but it’s not advised to do so.
|
|
0:11:33
|
It’s not advised to make the default device mobility mode set on
|
|
0:11:39
|
because then every single time, every phone boots up on the system.
|
|
0:11:44
|
It has to go through checking subnets
|
|
0:11:46
|
and it basically adds load to the CPU, of all processing engines.
|
|
0:11:52
|
It’s advised that you only turn it on
|
|
0:11:55
|
for the phones that are going to the roaming.
|
|
0:11:58
|
So, this would most likely be your stock clients,
|
|
0:12:04
|
your 7920 or 7921 phones and any wireless phone whether a dual mode.
|
|
0:12:11
|
So any wireless or soft client phone.
|
|
0:12:13
|
To sum it up, you could go through bulk administration tool.
|
|
0:12:18
|
You will custom query that checked for soft clients CUPC, CIPC
|
|
0:12:25
|
wireless phones and turn device mobility on.
|
|
0:12:29
|
But if it’s on, if it’s identified as a different subnet than its home subnet.
|
|
0:12:38
|
However, at the device pool level, it’s tide to the same physical location.
|
|
0:12:44
|
So, in another words, maybe and what might be a good example of this.
|
|
0:12:47
|
Well, I’m looking out my window and I see another building here
|
|
0:12:51
|
the parking lot in my same office complex campus.
|
|
0:12:56
|
If I were to head down the lift, head down the elevator,
|
|
0:13:02
|
and go out my building and take my 7921 wireless phone
|
|
0:13:06
|
over to the other building over here.
|
|
0:13:08
|
And once I associate with a thin AP,
|
|
0:13:13
|
then there’s going to be a subnet.
|
|
0:13:16
|
Maybe I got one subnet for floor of its rather large building.
|
|
0:13:20
|
I get up to the third floor of the other building,
|
|
0:13:23
|
I finally associate it with the wireless AP that I’m to be at for a while,
|
|
0:13:29
|
visiting for maybe an hour or two from meeting and CUCM sees my new subnet.
|
|
0:13:36
|
It sees that its tied to another device pool building 2.
|
|
0:13:41
|
But it’s the same campus, the Headquarter Corporate campus or Columbus campus.
|
|
0:13:47
|
and so maybe just depending on how I've got my system set up.
|
|
0:13:51
|
Maybe I've got it set up so that,
|
|
0:13:53
|
I got bonded 10gig fiber links between buildings.
|
|
0:13:57
|
So, I’m gonna consider all three of these buildings within this parking lot,
|
|
0:14:04
|
within this campus to be on the same physical location
|
|
0:14:08
|
even though they have different device pools.
|
|
0:14:10
|
I get to my roaming, I guess I shouldn’t call it roaming.
|
|
0:14:13
|
I get to my, for lack of a better term, roaming subnet.
|
|
0:14:19
|
Certainly not my home subnet.
|
|
0:14:21
|
A new device pool is associated with this subnet.
|
|
0:14:26
|
However, it’s tied to the same physical location.
|
|
0:14:31
|
So, because of this, I essentially see that my physical location has not changed
|
|
0:14:40
|
and the reason I set up that way is I had tons of bandwidth between buildings
|
|
0:14:44
|
and maybe all my TBN gateways are in one building, anyhow.
|
|
0:14:48
|
And so no new parameters from my device pool, the visiting device pool get passed.
|
|
0:14:54
|
Why? Because I can afford to have all calls go across the IP infrastructure
|
|
0:15:02
|
back to my home building and out my home gateway
|
|
0:15:05
|
This is not even really a WAN. It’s an extremely high speed LAN.
|
|
0:15:08
|
That might be a one reason that you might want to design it that way.
|
|
0:15:11
|
But again, you can design it however you want.
|
|
0:15:13
|
So, if it’s inside of its physical location, no parameters get passed.
|
|
0:15:18
|
If it’s outside of its physical location, then we’ll look at the next slide.
|
|
0:15:23
|
Does it roam within or outside of its device mobility group?
|
|
0:15:28
|
So, if the device roaming within its device mobility group
|
|
0:15:32
|
and really if we’re going according to the way
|
|
0:15:36
|
that Cisco has a designed parameter set up.
|
|
0:15:40
|
We’ll go ahead and make the connection or association
|
|
0:15:46
|
between the nomenclature of device mobility group
|
|
0:15:52
|
as what Cisco CUCM calls it.
|
|
0:15:55
|
And just the idea of a country, of a nationality and for country code of 1,
|
|
0:16:03
|
really numbering plan code of 1.
|
|
0:16:05
|
This would actually be the US and Canada together.
|
|
0:16:08
|
Even though they are separate countries, we use the same numbering plan.
|
|
0:16:12
|
We use the same fashion to dial.
|
|
0:16:17
|
But let’s we’re going from the US to the UK
|
|
0:16:22
|
or from the UK to Australia, or from Australia to India,
|
|
0:16:29
|
or from India to the Netherlands or from Netherlands to Germany.
|
|
0:16:33
|
Between these, we all have very different ways of dialling.
|
|
0:16:36
|
So, because of this, we’re gonna consider each of these separate countries
|
|
0:16:41
|
and separate device mobility groups.
|
|
0:16:43
|
So, we’ll create one device mobility group per country or per numbering plan.
|
|
0:16:49
|
Now, this isn’t a rule that you have to follow
|
|
0:16:52
|
but once you understand why it’s set up like this,
|
|
0:16:55
|
I think it will make a lot more sense,
|
|
0:16:57
|
and also once you understand what all we can do
|
|
0:17:00
|
when we get through our tasks today.
|
|
0:17:03
|
I think you’ll understand that this will still be
|
|
0:17:06
|
very flexible with our ideas of globalization.
|
|
0:17:11
|
So, for roaming within our same device mobility group
|
|
0:17:14
|
or we’re roaming within the country or between physical sites.
|
|
0:17:17
|
Maybe between cities even,
|
|
0:17:19
|
but within the same country or device mobility group,
|
|
0:17:25
|
then all of these visited device pool parameters get updated.
|
|
0:17:28
|
Local route group gets passed, date time group, region.
|
|
0:17:34
|
So we get a new date time group.
|
|
0:17:37
|
They’re likely in a new time zone or very possibly,
|
|
0:17:41
|
depends on how big the country is.
|
|
0:17:44
|
New region so that Codecs can be treated differently.
|
|
0:17:50
|
WAN calls. I should say calls between
|
|
0:17:53
|
a phone that used to be in the same home subnet.
|
|
0:17:57
|
Maybe I’m moving from Corporate Headquarters to Branch 1
|
|
0:17:59
|
and a call from Corporate Headquarter Phone 1
|
|
0:18:03
|
which is now roaming over a Branch 1
|
|
0:18:05
|
and Corporate Headquarter phone2 used to be G.711.
|
|
0:18:09
|
But now because I have taken new codec on new regions,
|
|
0:18:13
|
on my Corporate Headquarter visiting Phone 1,
|
|
0:18:17
|
I’ll use a new region and then I call back to the Corporate Headquarter Phone 2
|
|
0:18:22
|
will be G.729 because it’s actually going to be a WAN based call.
|
|
0:18:26
|
So, I get new regions, I get new media resources hopefully that are local to me,
|
|
0:18:32
|
new location for location based CAC or even RSVP based locations
|
|
0:18:38
|
and know which RSVP agent or MTP RSVP based
|
|
0:18:45
|
enabled MTP on an IOS router to trigger first.
|
|
0:18:49
|
New SRST reference, new physical location.
|
|
0:18:56
|
Actually, the physical location is the differentiating factor.
|
|
0:19:00
|
The device mobility group.
|
|
0:19:02
|
So, the physical location device mobility group don’t really get updated.
|
|
0:19:05
|
Those were really the determining factors that we’ll take a look at here.
|
|
0:19:13
|
Then we've got our device mobility calling search space.
|
|
0:19:18
|
So, this is the calling search space that will be replacing
|
|
0:19:21
|
the CSS that’s on the device.
|
|
0:19:24
|
So as I move my physical device,
|
|
0:19:26
|
I’ll actually get a new CSS at my device level
|
|
0:19:30
|
and this is what will allow site-specific call routing.
|
|
0:19:35
|
My AAR calling search space again if my moving my physical site
|
|
0:19:40
|
and I don’t want to use or possibly don’t wanna use.
|
|
0:19:43
|
In this case, that’ll work just fine.
|
|
0:19:45
|
Possibly, I don’t want to use the same AAR CSS as I had before
|
|
0:19:49
|
because I wanted to go out a site-specific gateway.
|
|
0:19:51
|
Again, with globalization, we can still have just one AAR CSS
|
|
0:19:56
|
and one AAR group just as we look at back in Module 11
|
|
0:20:02
|
for unlocking the potential of globalization and localization.
|
|
0:20:06
|
This will still work just fine
|
|
0:20:14
|
But a calling party transformation CSS,
|
|
0:20:17
|
it’s very possible that I, as the Headquarter phone,
|
|
0:20:19
|
want the new Branch 1 phone calling party transformation pattern mask
|
|
0:20:26
|
or CSS to match patterns because I want numbers
|
|
0:20:30
|
to show up to me in a way that’s local to my new location.
|
|
0:20:35
|
Called party don’t really matter for phones, they only matter for gateways.
|
|
0:20:41
|
Call has actually been extended to a phone.
|
|
0:20:43
|
We never needed to transform the DNs because it has already reached its destination.
|
|
0:20:47
|
We only possibly need to transform the NI.
|
|
0:20:50
|
This is within a country.
|
|
0:20:54
|
Now, let’s look at if we’re between countries
|
|
0:20:57
|
and this red line should have actually been extended up just a little bit.
|
|
0:21:01
|
If we are roaming to a new subnet, a new physical location,
|
|
0:21:07
|
but outside of our home device mobility group, so outside of our home country.
|
|
0:21:14
|
Then we still want, first of all local route group,
|
|
0:21:17
|
I should’ve have extended that red box up just a little bit.
|
|
0:21:20
|
The local route group will be passed or inherited or updated its settings.
|
|
0:21:27
|
Obviously, our date time group,
|
|
0:21:30
|
our region media resources,
|
|
0:21:34
|
locations for CAC, SRST.
|
|
0:21:37
|
However, if we look down that device mobility-related information
|
|
0:21:41
|
that was in the red-highlighted area earlier
|
|
0:21:45
|
within a country or within a device mobility group.
|
|
0:21:49
|
Why would we not want these parameters to be passed?
|
|
0:21:53
|
Well, think about it.
|
|
0:21:55
|
If I’m in another country and I take my mobile phone with me
|
|
0:22:02
|
and let’s say I've got a GSM SIM card
|
|
0:22:06
|
but it’s not a GSM SIM card of the visiting country,
|
|
0:22:10
|
I just take my existing GSM phone to another country
|
|
0:22:16
|
and power it up using my home SIM car.
|
|
0:22:19
|
Then, what’s gonna happen?
|
|
0:22:22
|
Well, my date and my time are gonna show up properly
|
|
0:22:27
|
because that’s going to be associated to the roaming mobile cell tower.
|
|
0:22:33
|
My calls will use whatever there’s cellular network
|
|
0:22:36
|
tells me in terms of a Codec sort of regions.
|
|
0:22:40
|
But when I actually come to my dialling habits,
|
|
0:22:45
|
if I am used to dialling,
|
|
0:22:50
|
let’s say 01144 to get a call out to the UK on my mobile
|
|
0:23:00
|
or maybe I’ll just do +44, maybe I do + dialling, but I’m in the UK.
|
|
0:23:06
|
I still should be able to dial in the exact same format
|
|
0:23:09
|
and this becomes much more so important with
|
|
0:23:13
|
users that, and you have to take yourself outside of the engineer mindset
|
|
0:23:19
|
that you are more than even just a power user with an IP phone
|
|
0:23:24
|
or with a phone system that you happen to know other countries' dialling plan.
|
|
0:23:31
|
But put yourself in the position of an average user
|
|
0:23:34
|
that just was given a 7921 phone and told,
|
|
0:23:36
|
“When you get to our London office or Amsterdam office
|
|
0:23:41
|
or our Paris office or whatever,
|
|
0:23:45
|
fire this up and then use it as normal.”
|
|
0:23:48
|
So, you get to those other three offices
|
|
0:23:51
|
because you’re actually visiting all three cities.
|
|
0:23:53
|
And without having to know how each country dials
|
|
0:23:57
|
because maybe it’s your first time there.
|
|
0:23:59
|
You don’t know how the local dialling plan works,
|
|
0:24:02
|
you just use your phone as you always have.
|
|
0:24:05
|
Educated about dialling plans or phone systems,
|
|
0:24:09
|
it’s your first trip outside of wherever your home country is.
|
|
0:24:12
|
So you don’t or shouldn’t need to know about the new dialling plans,
|
|
0:24:17
|
you should be able to retain all of your dialling habits.
|
|
0:24:20
|
And if you do this, you’re going to need to keep
|
|
0:24:25
|
your same device calling search space.
|
|
0:24:27
|
Because if you inherit a new device calling search space,
|
|
0:24:30
|
well, then there’s gonna be a problem because you’re going to have to dial
|
|
0:24:35
|
in the fashion of your visiting sites, PSTN codes.
|
|
0:24:40
|
So, maybe they dial 0 for second dial tone and then outside line
|
|
0:24:44
|
and you’re used to dialling 9.
|
|
0:24:46
|
And you’re from the UK and you’re visiting over to Australia
|
|
0:24:51
|
and you’ve never been there before and they dial 0 for outside dial tone
|
|
0:25:00
|
And you’re used to dialling just 00 for international.
|
|
0:25:03
|
So you would dial 000 and they actually dial,
|
|
0:25:07
|
maybe you dial 000 and then a 1 to dial internationally to the US
|
|
0:25:13
|
but they dial 000 and 111 to reach the US.
|
|
0:25:18
|
So, without having to know those new dialling habits or having to ask someone
|
|
0:25:25
|
or repeatedly have to ask someone if you have to make multiple calls,
|
|
0:25:27
|
you should be able to retain all your same dialling habits.
|
|
0:25:30
|
So, this is the reason that if we’d stick with the design that Cisco recommends
|
|
0:25:36
|
that device mobility groups equal countries,
|
|
0:25:38
|
then our device mobility calling search space or the CSS
|
|
0:25:43
|
that would otherwise replace the CSS on our device,
|
|
0:25:48
|
it does not replace anything neither does our AAR CSS ,
|
|
0:25:53
|
nor our AAR group, nor our calling party transformation CSS.
|
|
0:26:01
|
So, phones would still go out your primary home gateway for phone calls.
|
|
0:26:05
|
Your dialling habits would be retained.
|
|
0:26:08
|
Now, of course we can manipulate the design
|
|
0:26:13
|
knowing what the individual pieces of a puzzle,
|
|
0:26:17
|
knowing what the tools do,
|
|
0:26:18
|
we can manipulate the design anyhow we want.
|
|
0:26:21
|
So, if all of our users are very educated users
|
|
0:26:25
|
of every remote country that they’re going to visit,
|
|
0:26:30
|
well then we could just simply create one device mobility group
|
|
0:26:34
|
for our entire CUCM system regardless of what country they we’re visiting,
|
|
0:26:45
|
regardless of how many countries we have CUCM cluster branch sites,
|
|
0:26:51
|
and for branch sites off of our main cluster.
|
|
0:26:54
|
And then we would always get the new CSS, AAR CSS, AAR group,
|
|
0:26:59
|
and calling party transformation CSS.
|
|
0:27:03
|
So, we do have that ability.
|
|
0:27:06
|
Does anyone have any questions or does that make sense to everyone?
|
|
0:27:10
|
How device mobility groups equal country? And the reason
|
|
0:27:13
|
is so that we can maintain our traditional dialling habits.
|
