|
0:00:14
|
So we're back and we'll take a look at our next task
|
|
0:00:16
|
14.3 for Extension Mobility
|
|
0:00:20
|
We're told to provision Eloise
|
|
0:00:23
|
the user but the ability to travel to either the Corporate Headquarter
|
|
0:00:27
|
or Branch 2 site, she is a Branch 1 user
|
|
0:00:31
|
and while there, log in to the Phone 2 at either of these sites.
|
|
0:00:37
|
To ensure that while Eloise is visiting,
|
|
0:00:39
|
either the Corporate Headquarter or Branch 2 sites
|
|
0:00:42
|
that all of the following work properly
|
|
0:00:45
|
To ensure that Eloise retains her class of restriction,
|
|
0:00:50
|
and that call show up as coming in
|
|
0:00:53
|
from 2001 and Eloise Hawking, respectively.
|
|
0:00:57
|
ensure that the phone Eloise has logged into reflects the proper date and time,
|
|
0:01:04
|
to ensure that the VIOP calls to any other site
|
|
0:01:08
|
other than the one that she is currently visiting, use the G.729 codec.
|
|
0:01:14
|
To ensure that multicast music on hold streams properly to our phone,
|
|
0:01:18
|
ensure that the Branch 2 site were to lose WAN connectivity,
|
|
0:01:22
|
the phone she has logged into at whatever site
|
|
0:01:24
|
would fall back to that respective,
|
|
0:01:26
|
in this case Branch 2 to the Branch 2 SRST router but either one
|
|
0:01:31
|
because Corporate Headquarter doesn’t have an SRST router
|
|
0:01:36
|
site for the main CUCM so both of them go down.
|
|
0:01:45
|
Ensure that Eloise dialing habits however must adjust to the
|
|
0:01:50
|
site that she is local to.
|
|
0:01:52
|
For example, to get secondary dial tone and an outside line while
|
|
0:01:56
|
the two US sites, Corporate Headquarter and Branch 1
|
|
0:01:59
|
but 0 when she is at the Netherlands Branch 2 site.
|
|
0:02:03
|
To dial nationally, she has to dial 91 while at
|
|
0:02:07
|
either of the two US or 0 at the Branch 2
|
|
0:02:09
|
and internationally, 011 from US
|
|
0:02:12
|
and 00 from Branch 2.
|
|
0:02:16
|
AAR must function properly while she’s logged into any of these sites.
|
|
0:02:21
|
Ensure that calls made to a display
|
|
0:02:23
|
would show exactly as they would as if she was back at,
|
|
0:02:26
|
actually she’d be at the Branch 1 site so that’s a typo.
|
|
0:02:30
|
We’re told on further
|
|
0:02:32
|
that since Eloise will be the only person travelling
|
|
0:02:34
|
to these two sites and logging into these two remote phones
|
|
0:02:38
|
we’re told to configure ways so that any phone she goes to log into,
|
|
0:02:41
|
she only has to press one button on the phone to log in.
|
|
0:02:46
|
that she has the ability to log out of any phone without any assistance
|
|
0:02:51
|
and that when she does that the phone that she was logged into goes back
|
|
0:02:54
|
to operations just as if she had never been there.
|
|
0:02:58
|
Also to ensure that when she returns home to her Branch 1,
|
|
0:03:01
|
she is able to log into that phone if someone else logged into it.
|
|
0:03:06
|
So if Eloise forgets to log out of a phone
|
|
0:03:09
|
that she visits, we should automatically log her out after 10 hours,
|
|
0:03:13
|
allow Eloise to log into multiple phones
|
|
0:03:16
|
if she logs into a phone while still being logged into another phone,
|
|
0:03:21
|
that she is automatically logged out of the previously logged in phone
|
|
0:03:26
|
and when she logs out of a phone, automatically clear
|
|
0:03:31
|
all of the call history records. First, let’s just
|
|
0:03:37
|
break down the main differences between
|
|
0:03:40
|
device mobility and extension mobility.
|
|
0:03:43
|
The first glaringly obvious difference is that
|
|
0:03:48
|
for device mobility, you take your physical phone with you
|
|
0:03:50
|
be it a Blackberry or Nokia or
|
|
0:03:53
|
7921 wireless or what have you
|
|
0:03:59
|
or maybe even a desk phone. With extension mobility,
|
|
0:04:03
|
you take nothing with you but use your name and password
|
|
0:04:05
|
and you log in to a service on another phone
|
|
0:04:08
|
and that phone becomes your phone.
|
|
0:04:10
|
First of all, there has to be a phone for you to log into, that’s taken.
|
|
0:04:15
|
And then you don’t have to carry any hardware with you.
|
|
0:04:21
|
The main difference though being, most of these things sound fairly similar.
|
|
0:04:27
|
Some of these are specific to the service
|
|
0:04:31
|
but most of this sound similar class of restrictions still applies and
|
|
0:04:36
|
for both of device mobility and extension mobility,
|
|
0:04:38
|
class of restriction will apply if, like we talked about module 9,
|
|
0:04:42
|
line device approach is used for calling search spaces and partitions.
|
|
0:04:47
|
If it is, then class of restriction will follow.
|
|
0:04:51
|
Calls coming from
|
|
0:04:54
|
her number and name or Jack’s number and name for device mobility,
|
|
0:04:57
|
all that has to do with the actual line and that follows you whether it’s
|
|
0:05:03
|
line device or traditional CSS
|
|
0:05:06
|
whether it’s device mobility or extension mobility so that’s always gonna be there.
|
|
0:05:10
|
date and time as long as extension mobility is logging into a
|
|
0:05:15
|
phone at that site that was set up properly, then that will always work
|
|
0:05:19
|
and with device mobility the same thing
|
|
0:05:22
|
G.729 between other sites, that’s the same at both
|
|
0:05:27
|
media resources were the same at both.
|
|
0:05:29
|
SRST references, those were the same with both device mobility and extension.
|
|
0:05:34
|
The big two are 1.) Do you take you device or technically use your name and pin
|
|
0:05:39
|
and 2.) What are, this is the big one, the dialling habits.
|
|
0:05:44
|
With device mobility, you retain your dialling habits always
|
|
0:05:51
|
unless we choose to kinda manipulate the system in a different
|
|
0:05:55
|
non-intent or not by designed, not by intent by Cisco
|
|
0:06:00
|
and only create one DMG even if we have multiple countries
|
|
0:06:05
|
But with extension mobility, we don’t really have a choice
|
|
0:06:08
|
and that’s because we’re taking the calling search space
|
|
0:06:12
|
of the device that we log into. I think we take with us is the line
|
|
0:06:16
|
our own line CSS to maintain our class of restriction.
|
|
0:06:21
|
So this works for emergency services, in fact,
|
|
0:06:24
|
emergency services even between countries would never
|
|
0:06:28
|
be routed back to our home gateway but then again 911 won’t work when we’re
|
|
0:06:33
|
at the Branch 2 Netherlands gateway. We have to dial 112
|
|
0:06:38
|
So our dialling habits must change with extension mobility.
|
|
0:06:41
|
So let’s set this up. So we've got our, for the user management and user,
|
|
0:06:50
|
log in, find Eloise Hawking
|
|
0:06:57
|
Note that we never had any user for Jack Shepherd
|
|
0:07:00
|
for device mobility to work in its entirety.
|
|
0:07:06
|
Eloise Hawking, let’s just be sure that the password
|
|
0:07:09
|
Cisco. Actually, we’re not gonna need the password at all
|
|
0:07:13
|
but the pin, importantly. Let’s key it back in as 12345, just to be sure.
|
|
0:07:21
|
He already has a control device for her BAAE device.
|
|
0:07:28
|
She doesn’t have for extension mobility any profiles yet but she will.
|
|
0:07:38
|
Notice one thing that we haven’t covered yet is any of the present’s topics.
|
|
0:07:42
|
We’ll certainly cover that in a deep dive and we’ll come back to device users
|
|
0:07:47
|
extension mobility with that present but that is
|
|
0:07:54
|
present as its specific to extension mobility so when you log in
|
|
0:07:59
|
with the user device profile of another device.
|
|
0:08:03
|
Notice the mobility information.
|
|
0:08:07
|
This is not device mobility or extension mobility.
|
|
0:08:10
|
This is unified mobility and it should say unified mobility information
|
|
0:08:14
|
but we don’t need to enable mobility for device we didn’t
|
|
0:08:17
|
because we never had user for Jack’s phone.
|
|
0:08:20
|
We don’t need to enable it for extension mobility. This is just unified.
|
|
0:08:26
|
So the first thing we need to do is go set up
|
|
0:08:30
|
a device profile and this used to be called in the database, they still are a UDP
|
|
0:08:38
|
rather than the ambiguous DP which could be device pool or device profile.
|
|
0:08:45
|
This is a UDP or user device profile
|
|
0:08:49
|
that is separate from an ADP which is an
|
|
0:08:51
|
auto-generated device profile, we’ll see where that comes into play in a moment.
|
|
0:08:56
|
So all of our phones are 7961s,
|
|
0:09:01
|
and is it Skinny or SIP? Well. Her phone is actually a Skinny phone.
|
|
0:09:08
|
Take a look at that in a bit.
|
|
0:09:11
|
So we could leave this because we got our device pool
|
|
0:09:15
|
or the device pool actually of whatever visiting device.
|
|
0:09:19
|
But let's just go ahead, maybe we haven’t configured it on the line.
|
|
0:09:22
|
et’s just go ahead and take user hold audio source
|
|
0:09:27
|
phone button template is module 3 enhanced Skinny
|
|
0:09:35
|
the one that we had previously been using, in fact,
|
|
0:09:37
|
it might not be a bad idea just to open
|
|
0:09:40
|
her phones specifically in a new tab so Branch 1 phone 1
|
|
0:09:51
|
E phone and really I need to try to but
|
|
0:10:08
|
window, Skinny, her phone was Skinny.
|
|
0:10:16
|
We’ll call it UDP to avoid ambiguity for Eloise Hawking,
|
|
0:10:28
|
audio source, English US as a locale.
|
|
0:10:31
|
Let’s just make sure that her phone button template was
|
|
0:10:35
|
module 3 enhanced 7961 Skinny, good
|
|
0:10:38
|
soft key template was module 3 enhanced user, good,
|
|
0:10:44
|
privacy what was she set to, it was off,
|
|
0:10:51
|
enter, single button barge and join across lines.
|
|
0:10:55
|
I think those were just left to default.
|
|
0:11:00
|
Nor presentation indicators, I know she didn’t have that on.
|
|
0:11:04
|
DND option and incoming calling alert
|
|
0:11:07
|
and log out user ID, sorry, log in user ID is gonna be E. Hawking,
|
|
0:11:15
|
add successful and no we need to create her shared line, she is 2001
|
|
0:11:23
|
partition or internal DNs partition.
|
|
0:11:27
|
Once we do this, we’ll see a saved line. We’ll see an existing device
|
|
0:11:31
|
and her user profile so go over to the
|
|
0:11:35
|
existing device because we wanna get this
|
|
0:11:37
|
Line 1 on her existing device
|
|
0:11:41
|
parameters so we don’t have to key them again at a line appearance,
|
|
0:11:45
|
scroll down and we’ll update the shared device settings,
|
|
0:11:52
|
propeagate selected, it worked.
|
|
0:11:56
|
Now, we’ll go back to UDP Eloise Hawking.
|
|
0:12:00
|
At the line appearance, we still got here calling search space
|
|
0:12:04
|
which is unrestricted, her AAR pattern and now we got her name and
|
|
0:12:12
|
line text label and external phone number mask.
|
|
0:12:16
|
Back to her device and looks like we’re done,
|
|
0:12:21
|
we’ll go and here’s our user device profile.
|
|
0:12:26
|
We've got this, now let’s go to her, back to her N user
|
|
0:12:33
|
and we see it as an available profile. We’re gonna
|
|
0:12:37
|
drop that down the controlled profile and she uses it as her default profile.
|
|
0:12:42
|
Press save. Now, we’ve set up her user device profile.
|
|
0:12:50
|
We still need to set up the service for her to be able to log into.
|
|
0:12:55
|
Let’s go out to Cisco.com
|
|
0:12:59
|
Cisco.com and we click on support,
|
|
0:13:07
|
click on voice unified communications,
|
|
0:13:11
|
IP telephony call control, scroll down to CUCM
|
|
0:13:20
|
and we’re gonna to maintain operate guides,
|
|
0:13:25
|
and really can go to just about any version but we’ll choose 7.0
|
|
0:13:28
|
features and services guide, that's what we want
|
|
0:13:32
|
and we’re gonna want extension mobility here and we can either
|
|
0:13:40
|
look over here on the right or what I typically do, here we go,
|
|
0:13:44
|
adding the Cisco extension mobility service,
|
|
0:13:47
|
I typically just do a search for http://
|
|
0:13:51
|
here we go, adding the service.
|
|
0:13:54
|
We’ve got our URL for new phone service that we need to create.
|
|
0:14:03
|
There we go. So we'll go to device, device settings and phone services.
|
|
0:14:12
|
In number of services already, we're gonna add a new one
|
|
0:14:16
|
and we’re gonna call it extension mobility
|
|
0:14:23
|
URL in, replace it with the IP address of,
|
|
0:14:28
|
let’s say the publisher for right now. We do a host name with
|
|
0:14:32
|
round robin http port 80 service record lookups if we
|
|
0:14:40
|
wanted to have that load balance or maybe a content series switch.
|
|
0:14:45
|
Now there's couple things one is in XML service or a Java midlet,
|
|
0:14:48
|
it is an XML service and it is the standard
|
|
0:14:51
|
phone service not a directory or type of messages.
|
|
0:14:54
|
Also, we’re gonna want to enable it but
|
|
0:14:57
|
we’re not going to want to press enterprise subscription
|
|
0:15:01
|
unless we’re sure that we want everyone in the entire
|
|
0:15:05
|
cluster to get this service and it’s one that they cannot
|
|
0:15:11
|
They won’t see that as an available subscribe or want to delete
|
|
0:15:16
|
and it’s not one that after we press save up here.
|
|
0:15:20
|
we can come back into it and we can add all of the parameters except
|
|
0:15:24
|
subscriptions. We can't essentially unsubscribe it from everyone.
|
|
0:15:29
|
Once you’ve done it, you’ve done it and this goes away, you don’t see it anymore,
|
|
0:15:33
|
you don’t see it under the individual users but it is there.
|
|
0:15:37
|
You do when you actually press services on their phone but not at their
|
|
0:15:42
|
evice phone and up to the top right subscribe or unsubscribe services,
|
|
0:15:47
|
you don’t see it just subscribe or unsubscribe. It’s automatically there
|
|
0:15:51
|
and it’s for that reason that we cannot do anything very specific, we can’t add
|
|
0:15:55
|
parameters to it either because parameters would
|
|
0:15:58
|
really only be specific to one user
|
|
0:16:03
|
what we’re going to want to do is add parameters for,
|
|
0:16:09
|
you take a look back at our task.
|
|
0:16:11
|
We we’re told that since Eloise will be the only
|
|
0:16:14
|
person travelling these sites and logging in,
|
|
0:16:16
|
we should configure ways so that when she goes to log in,
|
|
0:16:19
|
she only has to press one button on the phone to log in.
|
|
0:16:22
|
This called enterprise, sorry, extension mobility 1 button log in.
|
|
0:16:26
|
And we’ve also got one button log in for
|
|
0:16:28
|
IP phone agent with the UCCX system but we're only looking at
|
|
0:16:34
|
today. You’ll see that we’ll do, we’ll create the
|
|
0:16:40
|
UCCX IP phone agent service for one button log in
|
|
0:16:44
|
pretty much exactly the same fashion that we’re gonna do this.
|
|
0:16:47
|
Now, we could go back in the real lab and click on,
|
|
0:16:54
|
it clicked on, let's see.
|
|
0:16:59
|
clicked on maintain an operate guides,
|
|
0:17:01
|
we could’ve clicked on configuration tech notes
|
|
0:17:04
|
freed or maintain and operate or I think
|
|
0:17:06
|
configuration example tech notes would be what we would want actually
|
|
0:17:10
|
and we’ve clicked find, control F and button
|
|
0:17:16
|
There is one button log in for IP phone agents.
|
|
0:17:22
|
I actually don’t see one button log in for extension mobility so let’s go
|
|
0:17:27
|
back maybe it is under maintain and operate tech notes.
|
|
0:17:44
|
Maybe it’s not even here for
|
|
0:17:55
|
words, phone
|
|
0:18:08
|
Well, I don’t even see one button log in for extension mobility
|
|
0:18:11
|
but that’s okay because we really don’t have to have it
|
|
0:18:14
|
in the same manner that we can get all the information for IP
|
|
0:18:18
|
phone agent, we can get it for extension mobility. So we would grab
|
|
0:18:21
|
the URL that we were going to create
|
|
0:18:25
|
or actually gonna go ahead and create this.
|
|
0:18:27
|
We’re just not going to do enterprise subscription
|
|
0:18:31
|
and we’re gonna grab the URL. We’re gonna open a new
|
|
0:18:36
|
window although it does have to be Internet Explorer
|
|
0:18:43
|
not a problem for you in the lab and not even a problem for me
|
|
0:18:48
|
here, let me just open the window.
|
|
0:18:55
|
Bring it over and we’re gonna paste in the URL but we’re gonna replace
|
|
0:19:02
|
the variable for pound device name. Noticed that this is a
|
|
0:19:10
|
notice that this is a
|
|
0:19:17
|
our path through our URI has a question mark
|
|
0:19:22
|
and then more information so what we're doing is we’re passing a variable
|
|
0:19:28
|
on to this EMAppServlet here.
|
|
0:19:35
|
This tomcat service is what it really is
|
|
0:19:38
|
and we’re passing the value for that variable
|
|
0:19:42
|
as actually sort of another variable which is
|
|
0:19:45
|
the information from the phone that’s doing the request, the http request.
|
|
0:19:50
|
What we can do is manually replace this.
|
|
0:19:59
|
I can’t actually
|
|
0:20:05
|
If I were to go over to phone and grab
|
|
0:20:12
|
her SEP MAC address, that is her phone device name.
|
|
0:20:16
|
Device name so I would replace # device name #,
|
|
0:20:32
|
cooperate with me and it’s not really want to.
|
|
0:20:42
|
We replace it with her MAC address,
|
|
0:20:45
|
actually SEP MAC address or phone device name
|
|
0:20:48
|
and what we get back is the XML that would be displayed
|
|
0:20:52
|
to the IP phone. We get the prompt, please sign on,
|
|
0:20:57
|
the URL that’s going to be triggered which is actually the exact same URL
|
|
0:21:02
|
there are two parameters or
|
|
0:21:07
|
query string for EMS that we need to pass on that she would
|
|
0:21:11
|
fill in the information for user ID is alphanumeric
|
|
0:21:15
|
and SEQ is your display name pin number with
|
|
0:21:21
|
N and P, N is number and P is a password.
|
|
0:21:26
|
Anyhow, let’s go back over here to where we’re creating our service,
|
|
0:21:30
|
back to find list, click on extension mobility just in case it doesn’t update properly.
|
|
0:21:34
|
Grab new parameter and the parameter name,
|
|
0:21:41
|
there’s the display name and then the name. This follow
|
|
0:21:45
|
the fields we see here. The display name, it is gonna be user ID
|
|
0:21:54
|
as well if we want, we have to put a description.
|
|
0:21:58
|
Parameter is required
|
|
0:22:03
|
and then query string parameter that’s the actual parameter name.
|
|
0:22:07
|
That has to be case sensitive
|
|
0:22:10
|
properly copy and paste would be best. These two really don’t matter what they are.
|
|
0:22:15
|
The value is we want everyone to have. Now, we can
|
|
0:22:18
|
fill this in on an individual case by case basis
|
|
0:22:21
|
or since she is the only user, we can just go ahead and have the default
|
|
0:22:26
|
value of her user ID right here.
|
|
0:22:30
|
Save and close and user ID has been updated.
|
|
0:22:33
|
We’ll add a new parameter
|
|
0:22:36
|
and the new parameter display name will be pin.
|
|
0:22:42
|
Actual param name is SEQ,
|
|
0:22:46
|
sequence maybe. The default value 12345.
|
|
0:22:50
|
Numeric and P is the password, so mask the contents, we’ll save that.
|
|
0:22:59
|
We’ll save the whole thing.
|
|
0:23:05
|
We've now got this information in for one button log in.
|
|
0:23:11
|
Again, we found that out just by going to the
|
|
0:23:16
|
flood page for it and we could actually even
|
|
0:23:17
|
pass this information on from the web page
|
|
0:23:21
|
and by the way, this is doesn’t have to be her device,
|
|
0:23:24
|
this would really be the device that she wants to log in to
|
|
0:23:27
|
so like here, you can see that I've had F1DE
|
|
0:23:31
|
which is another and what we can do is put in
|
|
0:23:34
|
& in between each of the parameters
|
|
0:23:37
|
equals the value &, next parameter equals the value so after
|
|
0:23:44
|
question device equals the value, it would be &
|
|
0:23:48
|
user ID equals E Hawking &
|
|
0:23:52
|
SEQ equals 12345
|
|
0:23:55
|
nd this would be the device that we wanna log into.
|
|
0:23:58
|
Because we had all other information, we have the user ID and pin
|
|
0:24:01
|
and the device name, it would actually log as into that device
|
|
0:24:06
|
assuming it was set up properly right here from the web browser,
|
|
0:24:12
|
Couldn't close Internet Explorer
|
|
0:24:18
|
Now, we need to go associate phones with this
|
|
0:24:27
|
with this IP's phone service.
|
|
0:24:29
|
So we need Phone 2 at each site is what we are told to do.
|
|
0:24:36
|
Drive them to extension mobility
|
|
0:24:44
|
with all the parameters are already keyed in so that one button will work.
|
|
0:24:51
|
We don't have to restart a phone because when they actually press services,
|
|
0:24:55
|
it will actually goes out and restarts at anyhow but when they press services, it does
|
|
0:24:59
|
live http call to that page and would already find
|
|
0:25:05
|
that there. While I was in Corporate Headquarter Phone 2, I wanted to also but forgot,
|
|
0:25:13
|
go down and actually enable the ability
|
|
0:25:16
|
to log in to extension mobility.
|
|
0:25:19
|
So we'd log in to extension mobility
|
|
0:25:23
|
the ability to log in, start the phone again,
|
|
0:25:36
|
Branch 2 Phone 2,
|
|
0:25:40
|
the ability to enable extension mobility
|
|
0:25:43
|
the log out profile. Now, we can assign a specific log out profile
|
|
0:25:49
|
but, and the reason that we don’t see any in here is because the
|
|
0:25:56
|
only user device profile that we have already created,
|
|
0:25:58
|
we’ve already assigned to the user of E Hawking
|
|
0:26:02
|
but if we had others,
|
|
0:26:03
|
we could have a log out profile maybe we’d have a common log out profile for all phones.
|
|
0:26:08
|
But used current device settings means that when
|
|
0:26:10
|
tension mobility goes to log out, when Eloise logs out to go home,
|
|
0:26:14
|
it will actually log in
|
|
0:26:18
|
using extension mobility, the phone will automatically
|
|
0:26:21
|
log out and go to a user device profile. It's actually gonna be an
|
|
0:26:25
|
used current device settings is what creates the ADP (autogenerated device profile)
|
|
0:26:30
|
which we don’t see anywhere in here. It shows up in the database
|
|
0:26:34
|
and it’s basically a mirror image of everything that we already have here.
|
|
0:26:40
|
But it is still using device profiles and extension mobility.
|
|
0:26:45
|
So we need to subscribe to a service,
|
|
0:26:54
|
save,
|
|
0:27:01
|
reset, restart
|
|
0:27:08
|
and then also Branch 1 Phone 1, we told
|
|
0:27:12
|
we were told that we needed to allow
|
|
0:27:16
|
extension mobility to work for
|
|
0:27:21
|
her phone as well so maybe people would be logging in to her phone
|
|
0:27:26
|
for the ability to log in and out of her own home phone.
|
|
0:27:36
|
So we've got extension mobility enabled
|
|
0:27:38
|
for her phone and that two
|
|
0:27:40
|
other Headquarter and Branch 2 site phones.
|
|
0:27:46
|
We've got her user device profile created and linked to her user.
|
|
0:27:52
|
Now, here’s a problem,
|
|
0:27:57
|
go back and look at the task, we were told to ensure that
|
|
0:28:00
|
Eloise has the ability to log out of any phone without any assistance
|
|
0:28:04
|
and that when she does, the phone she was logged into goes back in normal operations.
|
|
0:28:10
|
Actually, let’s just not do anything with that
|
|
0:28:13
|
for the moment and let’s just go ahead and test what we have
|
|
0:28:16
|
and see what happens. We’re going to actually bring up another
|
|
0:28:23
|
remote phone or phone remote instance.
|
|
0:28:31
|
We’ll bring in 3002.
|
|
0:28:51
|
So James Ford phone, we’re gonna go ahead and press services
|
|
0:28:57
|
because there’s only one service there, extension mobility
|
|
0:29:02
|
automatically logged in and said that log in successful, resetting,
|
|
0:29:06
|
please wait. Had there been multiple services,
|
|
0:29:08
|
it would have asked us which service we wanted
|
|
0:29:11
|
Because there’s only one, it went ahead and automatically logged in.
|
|
0:29:18
|
in because we already had the user ID and pin or the credentials
|
|
0:29:23
|
set in the parameters. That was the one button log in.
|
|
0:29:28
|
, she is registered as Eloise Hawking if we go off hook
|
|
0:29:32
|
it’s gonna show that we’re off hook on her phone as well.
|
|
0:29:36
|
This doesn’t have refresh set on it. If I click refresh,
|
|
0:29:41
|
phone goes to busy. Let's go device
|
|
0:29:52
|
on, control, let’s refresh,
|
|
0:30:04
|
now we have the user device profile as well, I see, that was why.
|
|
0:30:16
|
So if we go off hook on the logged in phone, James’ phone,
|
|
0:30:22
|
noticed that her phone will show here in just a moment. There we go,.
|
|
0:30:25
|
the non-idle on the actual phone showing red
|
|
0:30:29
|
line. So if we do 911, we immediately, after I dial 9,
|
|
0:30:37
|
get reorder tone and the reason is that she’s at Branch 2, she can’t dial 9 anything.
|
|
0:30:48
|
2001 was dialling at local, let’s clear that buffer. Our other two buffers are cleared
|
|
0:30:53
|
so let’s see if she can dial from her own home phone, 911.
|
|
0:31:02
|
That’s from her home Branch 1 phone. She can dial just fine.
|
|
0:31:09
|
knows that she's on off hook and 911 so
|
|
0:31:14
|
she actually is, this is just operating just like a shared line,
|
|
0:31:22
|
remote log in phone. Let’s clear this buffer.
|
|
0:31:27
|
So she’s over at Branch 2 and she wants emergency services,
|
|
0:31:33
|
We'll go off hook here
|
|
0:31:37
|
and we’ll dial 112
|
|
0:31:40
|
for emergency services and then we’ll go out Branch 2 gateway.
|
|
0:31:51
|
dialing will work, let’s have her dial nationally,
|
|
0:32:01
|
00107047444
|
|
0:32:10
|
Now, she’s dialling out nationally out of Branch 2.
|
|
0:32:14
|
What if she calls back to 3001?
|
|
0:32:26
|
She goes off hook, we mute it and look at her stats and she is calling
|
|
0:32:39
|
177.3.11 is her local IP to 177.3.11,
|
|
0:32:44
|
she is 52, he’s 56. They’re using G.722
|
|
0:32:50
|
ecause they’re on the same subnet. She called the 3001.
|
|
0:32:54
|
2001 but she is logged in at a 3002
|
|
0:32:58
|
phone or a phone that’s physically at Branch 2. What about to 1001?
|
|
0:33:07
|
She is now back registered proper
|
|
0:33:11
|
at its Corporate Headquarter site and subnet, device mobility still on,
|
|
0:33:19
|
press here. She is 177.3.11 to 177.1.11.33
|
|
0:33:26
|
put that G.729, talking to of course, Jack Shepherd.
|
|
0:33:40
|
What about music on hold? Actually, redial that call, he’ll answer,
|
|
0:33:47
|
we’ll put her on hold, she is hearing music on hold, let’s look at the stats
|
|
0:33:53
|
for the stream, refresh it, she’s getting 239111 G.711,
|
|
0:34:00
|
the received codec, the transmit is just the last, and there’s no packets.
|
|
0:34:05
|
So she is 239111 is the
|
|
0:34:14
|
multicast music on hold for G.711
|
|
0:34:22
|
G.722 with the music on hold server doesn‘t speak to G.722.
|
|
0:34:36
|
That looks like it’s working properly.
|
|
0:34:41
|
Now, she wants to log out, she presses services
|
|
0:34:46
|
and it says no services configured.
|
|
0:34:50
|
No services configured, what do you mean?
|
|
0:34:54
|
Branch 2 Phone 2, subscribe unsubscribed services
|
|
0:35:03
|
intercom calls which doesn’t show up but it’s got extension mobility.
|
|
0:35:07
|
It had to, how else do we log in?
|
|
0:35:10
|
Wait a minute, we logged into the phone and now we’re logged in with our
|
|
0:35:14
|
user device profile. Let’s go under our user device profile
|
|
0:35:19
|
and see what services she has subscribed.
|
|
0:35:24
|
She has none. Now, we could give her extension mobility, the problem is
|
|
0:35:29
|
that extension mobility service
|
|
0:35:37
|
services, extension mobility already has two parameters that we gave default values.
|
|
0:35:45
|
and even if we hadn’t given them default values, the fact that we gave them parameters
|
|
0:35:50
|
and said that parameter was required,
|
|
0:35:56
|
that means that when we actually subscribed the user or actually a device
|
|
0:36:00
|
or user device profile to the service, we have to fill in that parameter with a value.
|
|
0:36:06
|
Since we have to fill in those variable parameters with values,
|
|
0:36:10
|
extension mobility will try to basically log her back in.
|
|
0:36:14
|
So this, we’re gonna call this extension mobility
|
|
0:36:18
|
Eloise Hawking because that’s really, let’s call it E Hawking.
|
|
0:36:28
|
Because that's really what this is. This is just extension mobility
|
|
0:36:32
|
just for Eloise Hawking
|
|
0:36:34
|
or technically when you subscribed the user, they could fill in
|
|
0:36:38
|
own or the administrator could overwrite whatever the default value was
|
|
0:36:43
|
but we don’t have anyone else so this is gonna be extension mobility for E Hawking.
|
|
0:36:47
|
Because of this, we actually have to create a new service that we’re gonna call
|
|
0:36:57
|
just extension mobility. Maybe we’ll call it extension mobility log out.
|
|
0:37:03
|
actually be logged out or logged back in.
|
|
0:37:08
|
Enable it but we’re not gonna give this one any parameters
|
|
0:37:12
|
are going to go to her user device profile
|
|
0:37:22
|
Subscribe, her user device profile
|
|
0:37:28
|
not extension mobility E Hawking but to the log out.
|
|
0:37:33
|
Subsribe it, now she’s subscribed but wait a minute, where’s the reset?
|
|
0:37:39
|
There’s no reset or restart.
|
|
0:37:42
|
So how is she gonna get out?
|
|
0:37:45
|
Well, we;re actually going to have to and I went to the wrong phone here.
|
|
0:37:49
|
We're gonna need to go into the phone, so Branch 2 Phone 2
|
|
0:37:52
|
is the one she is the one she’s currently logged into.
|
|
0:38:00
|
Actually when I'm up here
|
|
0:38:05
|
actually go to the actively logged in device report.
|
|
0:38:11
|
Find that there is one device that has a log in profile,
|
|
0:38:17
|
E Hawking 2001. So, everyone see where I was, I was at phone,
|
|
0:38:22
|
device phone and instead of just clicking find
|
|
0:38:25
|
which I already had devices over records populated from her previous find.
|
|
0:38:29
|
I went up to actively logged in device report, click go,
|
|
0:38:33
|
and there I see that the UDP Eloise Hawking,
|
|
0:38:36
|
her user ID E Hawking directory number 2001
|
|
0:38:39
|
is logged in to this device.
|
|
0:38:43
|
I can scroll down to extension mobility here.
|
|
0:38:46
|
I can log her out using her device configuration.
|
|
0:38:57
|
How it looks on her phone as it’s logged in to her extension mobility
|
|
0:39:04
|
or I can log her out. So this was the administrative assistance to log her out.
|
|
0:39:11
|
Where if I go back to the phone, it’s restarting
|
|
0:39:16
|
because she logged out even though it was through administrative help.
|
|
0:39:20
|
While that’s restarting, if we take a look,
|
|
0:39:22
|
ensure that Eloise has the ability to log out of a phone
|
|
0:39:25
|
without any assistance that was the assistance.
|
|
0:39:28
|
So we need to and we already did give her subscription to the
|
|
0:39:33
|
service of extension mobility log out
|
|
0:39:39
|
that restarts, here it is.
|
|
0:39:56
|
Now, James Ford is back.
|
|
0:39:58
|
We can press services.
|
|
0:40:03
|
He still has the service. He does not have extension mobility logged out.
|
|
0:40:08
|
He only has extension mobility
|
|
0:40:11
|
which is the, we rename to extension mobility E Hawking,
|
|
0:40:14
|
the one button log in, so it is still one button to log in.
|
|
0:40:19
|
She is the only user device profile or device for that matter
|
|
0:40:24
|
n the system that has two services, 1 extension mobility E Hawking and the other
|
|
0:40:29
|
extension mobility log out.
|
|
0:40:33
|
Now, she’s logged in as Eloise Hawking, she can click services,
|
|
0:40:38
|
ask do we wanna log out E Hawking?
|
|
0:40:43
|
Yes.
|
|
0:40:46
|
Now, it’s restarting again. Log out was successful.
|
|
0:40:52
|
We gonna restart as James’ phone.
|
|
0:40:55
|
She actually does have the ability to log out without any,
|
|
0:41:04
|
if Eloise forgets to log out of a phone that she visits,
|
|
0:41:08
|
utomatically logged her out after 10 hours.
|
|
0:41:10
|
We haven’t seen anything related to that yet.
|
|
0:41:13
|
Let’s go back to CUCM and there’s really no space in here for extension mobility.
|
|
0:41:20
|
There was device profile, user device profile.
|
|
0:41:22
|
There’s extension mobility specifics under each phone.
|
|
0:41:27
|
We created the extension mobility service or services.
|
|
0:41:33
|
There is a service parameter section dedicated just to extension mobility.
|
|
0:41:43
|
Under this extension mobility, we got some information such as,
|
|
0:41:47
|
is there a maximum log in time. Well by default, it’s no,
|
|
0:41:52
|
we’re gonna change it to yes and change the maximum time from 8 hours to 10 hours
|
|
0:41:58
|
because that’s what we’re instructed to do.
|
|
0:42:01
|
Eloise forgets to log out, automatically log her out after 10 hours.
|
|
0:42:05
|
Also, if Eloise logs into multiple phones, sorry, allow her to
|
|
0:42:09
|
however, if she does, while still being logged into another phone,
|
|
0:42:13
|
ensure that she is automatically log out of the previous phone.
|
|
0:42:18
|
Multiple log in behaviour, by default, multiple log ins are not allowed.
|
|
0:42:23
|
We can change it to just multiple log ins are allowed or
|
|
0:42:27
|
asically auto-log out which basically says
|
|
0:42:30
|
click this link for context sensitive help to tell us exactly
|
|
0:42:37
|
Log in's allowed. There we go, auto log out if the user ID
|
|
0:42:42
|
is logged in to extension mobility on one device
|
|
0:42:45
|
and the same user ID attempts to log in to extension mobility on a different device,
|
|
0:42:49
|
the first device automatically logs out. So it does allow
|
|
0:42:54
|
multiple logins, this right here,
|
|
0:42:58
|
you would simply meet with in fact, let’s actually just try it.
|
|
0:43:03
|
Have her log in to extension mobility on James’s phone
|
|
0:43:08
|
which this phone control over to 1002,
|
|
0:43:13
|
Headquarter that she’s going to be logging into.
|
|
0:43:28
|
The device is possibly not a phone.
|
|
0:43:34
|
Perk like a phone and control the phone, then I’d say it’s a phone
|
|
0:43:44
|
|
|
0:43:53
|
over it 3002, over the phone that was
|
|
0:43:57
|
3002, the hardware device.
|
|
0:44:00
|
at Branch 2, Eloise Hawking is logged in. However, Hurley
|
|
0:44:07
|
Hugo also wants to log in so he presses services
|
|
0:44:11
|
and log in unsuccessful, user logged in elsewhere, area code 25.
|
|
0:44:19
|
what you get by default with multiple logins not allowed.
|
|
0:44:23
|
If multiple log ins allowed, he would be able to log in and
|
|
0:44:29
|
Branch 2 Phone 2 would say logged in.
|
|
0:44:32
|
Auto log out, which is what we’re going to switch it to
|
|
0:44:36
|
will automatically log out Branch 2 Phone 2 once we do that
|
|
0:44:42
|
and we were also told when she logs
|
|
0:44:45
|
out of a phone, automatically clear the call history records,
|
|
0:44:49
|
so here’s the clear call log for privacy concerns, we’ll go ahead and press save.
|
|
0:44:56
|
There’s also some advanced parameters. We can validate IP addresses,
|
|
0:45:01
|
trusted list of IPs or extension mobility cash.
|
|
0:45:05
|
I remember the last user that logged in,
|
|
0:45:08
|
doesn’t remember their password but I remember their
|
|
0:45:10
|
user ID and that they have to put in their pin.
|
|
0:45:14
|
Password, I should’ve said pin
|
|
0:45:18
|
Keep those in mind. There is advanced parameters.
|
|
0:45:22
|
Now, I don’t remember if we have to restart CUCM for this or not.
|
|
0:45:27
|
Eloise is still logged in at Branch 2 Phone 2.
|
|
0:45:30
|
If I had to look in Hurley’s phone and it’s going to say, log in successful,
|
|
0:45:37
|
resetting, please wait. Apparently, we do not have to reset the CUCM service.
|
|
0:45:49
|
Automatically logged her out of Branch 2 Phone 2 and it’s restarting that phone.
|
|
0:46:03
|
Back to control, I’ll just update this.
|
|
0:46:09
|
it actually looks like it did update properly
|
|
0:46:20
|
that’s James Ford, logged back in as his own phone.
|
|
0:46:28
|
We’re gonna shut that done because we’re done with that one.
|
|
0:46:34
|
his Corporate Headquarter Phone 2 is now Eloise Hawking.
|
|
0:46:40
|
So if we were to dial out of this phone,
|
|
0:46:47
|
911 for instance, it’s gonna go out the Corporate Headquarter gateway.
|
|
0:46:59
|
If we dial, let’s say maybe 901131207037333#.
|
|
0:47:11
|
Again, it’s gonna out the Corporate Headquarter gateway as an international call.
|
|
0:47:19
|
So verything works in the same way that we were instructed,
|
|
0:47:25
|
he basically has to take on the dialling characteristics of whatever sites she’s at,
|
|
0:47:29
|
calls go out the local gateway. Fine, we’ve configured one button log in,
|
|
0:47:38
|
able to log out herself,
|
|
0:47:44
|
press services had logged out.
|
|
0:47:46
|
Again, we didn’t do anything
|
|
0:47:47
|
with Corporate Headquarter Phone 2 other than the initial
|
|
0:47:50
|
subscription to extension mobility. This is because
|
|
0:47:53
|
her user device profile has the extension mobility to log out app.
|
|
0:48:00
|
Keep in mind that there’s nothing unique about
|
|
0:48:03
|
the log out app, it’s also a log in app.
|
|
0:48:06
|
It just so happens that nobody has that extension at IP phone service
|
|
0:48:11
|
subscribed. All they have is the
|
|
0:48:15
|
one with the user and password or user and pin rather already filled in.
|
|
0:48:22
|
Log out of a phone and logs her out after 10 hours,
|
|
0:48:25
|
although we’re not gonna test that.
|
|
0:48:27
|
That would be a rather lengthy video.
|
|
0:48:29
|
If she logs into multiple phones, it automatically logs her out.
|
|
0:48:33
|
When she logs out, it clears the records.
|
|
0:48:35
|
Let’s check this. Go ahead and say services,
|
|
0:48:45
|
log out, yes, we wanna log her out.
|
|
0:48:49
|
That’s going to log out was successful. It’s gonna be
|
|
0:48:53
|
resetting the phone and
|
|
0:49:01
|
we didn’t test the Branch 2 SRST, we could’ve tested that.
|
|
0:49:07
|
Again, it’s the device. The device says the SRST references,
|
|
0:49:11
|
be it the device pool that wasn’t an option from the user device profile.
|
|
0:49:15
|
It shouldn’t be. It should follow whatever the device already has
|
|
0:49:19
|
already tested SRST
|
|
0:49:22
|
Now, Hugo then logged out. Let’s check directories,
|
|
0:49:30
|
calls, like that’s been cleared once this refreshes, there you go, no records,
|
|
0:49:39
|
what about missed calls.
|
|
0:49:44
|
missed calls has no records. So it cleared the phone,
|
|
0:49:51
|
actually cleared the CUCM database in reference to this phone name
|
|
0:49:57
|
and while that might not necessarily be good
|
|
0:50:02
|
if you just had an occasional user visiting
|
|
0:50:05
|
Obviously, it’s out to Corporate policy and if you’re using or relying
|
|
0:50:11
|
almost primarily or exclusively on extension mobility such as
|
|
0:50:15
|
a lot of companies do, Cisco does for instance, then
|
|
0:50:20
|
probably is a very good policy to enforce so that
|
|
0:50:24
|
all of your privacy is kept private.
|
|
0:50:33
|
Are there any questions?
|
|
0:50:37
|
We’ve pretty much covered the extension mobility.
|
|
0:50:40
|
The only thing we’re gonna cover when we come back
|
|
0:50:41
|
is device and extension mobility interaction with THO.
|
|
0:50:45
|
Right now, all of our calls, remember even our call to international
|
|
0:50:51
|
om the Corporate Headquarter site with
|
|
0:50:55
|
extension mobility log in or when we’re calling
|
|
0:51:02
|
international or even what we thought was that we’re using device mobility
|
|
0:51:07
|
and we were dialling a national number or actually even a subscriber number 9
|
|
0:51:11
|
and then only 10 digits but from the Branch 2 site with our device
|
|
0:51:16
|
carried over from the Corporate Headquarter site it went out
|
|
0:51:18
|
our local gateway because of local route group
|
|
0:51:21
|
as an international number so we’ll look next at tail and hop off
|
|
0:51:25
|
and how that can again, just like it has in so many other times
|
|
0:51:30
|
really be extremely beneficial.
|
|
0:51:33
|
|
