|
0:00:12
|
Ok, so now let's take a look at a demonstration of our
|
|
0:00:15
|
Unified Mobility and Mobile Connect
|
|
0:00:17
|
and Mobile Voice Access.
|
|
0:00:20
|
So to begin with, let's choose a phone.
|
|
0:00:25
|
Let's choose the Branch 1 Phone 1
|
|
0:00:29
|
We haven't picked on him much.
|
|
0:00:31
|
So we'll grab Branch 1 Phone 1 and we're going to go up to
|
|
0:00:35
|
related links and say copy to remote destination profile.
|
|
0:00:39
|
And we can see our remote destination profile configuration
|
|
0:00:42
|
here is based on our existing name. I'm not going to call
|
|
0:00:47
|
this, this particular name. I'll call it maybe instead of SEP,
|
|
0:00:51
|
I'll call it RDP and that Mac address.
|
|
0:00:54
|
And description will be Branch 1 Phone 1 RDP.
|
|
0:00:59
|
User ID is associated. It just so happens that's actually
|
|
0:01:03
|
the proper user for this was just the first one, so we do need
|
|
0:01:07
|
to have a user set up that we're going to associate before
|
|
0:01:11
|
we begin our RDP configuration.
|
|
0:01:14
|
Device pool, that's going to be the proper device pool.
|
|
0:01:17
|
Well, at least we would assume so.
|
|
0:01:20
|
Branch 1 Phone 1 is obviously at Branch 1, so unless we wanted
|
|
0:01:23
|
this RDP to use some sort of different set of media resources
|
|
0:01:30
|
or something of that nature, region, then it's probably going
|
|
0:01:36
|
to be the same one.
|
|
0:01:38
|
Calling search space, now this calling search space just deals
|
|
0:01:42
|
with a device. There actually is a line calling search space as well
|
|
0:01:47
|
if we're using line/device approach and that's going to be on the shared
|
|
0:01:50
|
line of 2001
|
|
0:01:52
|
User and hold network audio source if we want those any
|
|
0:01:55
|
different, privacy if we want that on or off.
|
|
0:02:00
|
Ok, it was on, on 2001 so that's why it's copied
|
|
0:02:05
|
over as on, but we can make it default.
|
|
0:02:08
|
Rerouting and actually phone 2001 has a privacy button that just
|
|
0:02:14
|
happens to be turned on. They have the ability to
|
|
0:02:16
|
turn it on and off and that's why because it was on
|
|
0:02:19
|
it was then on, on the administrative page, so it copied over as such.
|
|
0:02:24
|
I'll make it default which is off.
|
|
0:02:27
|
Rerouting calling search space, so this is how we're going to
|
|
0:02:30
|
find the DN which is the remote destination, so we need to make
|
|
0:02:35
|
sure that this can see those phones, so CSS US phones will
|
|
0:02:39
|
work just fine. Calling party transformation CSS.
|
|
0:02:44
|
Now Unified Mobility is one of the exceptions to outbound
|
|
0:02:50
|
PSTN calling party manipulation.
|
|
0:02:54
|
It essentially if a call goes out to the PSTN because
|
|
0:03:01
|
it was first extended to the shared line for the remote
|
|
0:03:06
|
destination profile and desk phone, its egress point --
|
|
0:03:12
|
if we were egressing to the actual IP desk phone, then it's
|
|
0:03:18
|
going out to an IP phone which is on cluster or on net.
|
|
0:03:23
|
But if it's going out as the egress point to a virtual phone
|
|
0:03:28
|
for the remote destination, then it's -- or the remote
|
|
0:03:31
|
destination profile, it's ultimately going to bring a remote destination
|
|
0:03:34
|
which is out on the PSTN somewhere.
|
|
0:03:38
|
And if it's going to -- and it doesn't have to be on the
|
|
0:03:42
|
PSTN, but nine times out of ten, that's what we're trying to accomplish.
|
|
0:03:45
|
So if it's going out to a mobile phone, it's going out on the PSTN
|
|
0:03:49
|
and in that specific instance, this CSS will override whatever
|
|
0:03:58
|
the standard calling party transformation pattern would be
|
|
0:04:03
|
on either a translation pattern or a route pattern or a route list
|
|
0:04:09
|
details or the gateway's egress calling party transformation pattern.
|
|
0:04:14
|
Ok, so in this one exception when we're using single-number
|
|
0:04:18
|
reach or mobile connect, this overrides that, so it takes the
|
|
0:04:24
|
globalized. The number that had come in from the PSTN
|
|
0:04:28
|
to dial the desk phone had come in from a particular gateway
|
|
0:04:32
|
and was globalized either in IOS or in CUCM.
|
|
0:04:36
|
That much has already still happened.
|
|
0:04:38
|
But then as it would normally go out to a phone and be
|
|
0:04:42
|
localized, that is calling party, here this is what we will do
|
|
0:04:47
|
to localize that previously globalized calling number
|
|
0:04:52
|
and that is what we'll display to the phone -- to the mobile phone.
|
|
0:05:00
|
And maybe we wanted to display in the exact same way, but maybe we don't.
|
|
0:05:05
|
We're going to take a look at it initially in the same way
|
|
0:05:08
|
and then we'll also take a look at a subset or something
|
|
0:05:12
|
a little bit different.
|
|
0:05:16
|
So we're not going to use device pool.
|
|
0:05:20
|
We don't want do not disturb turned on.
|
|
0:05:23
|
The DND option copied for call reject.
|
|
0:05:28
|
So let's say save.
|
|
0:05:31
|
Add failed. Phone cannot have the same intercom line more than once.
|
|
0:05:35
|
Ok, so as it added, it attempted to add and copy over all of the lines
|
|
0:05:42
|
and you don't see that yet, but it attempted to copy over the same
|
|
0:05:46
|
lines that phone Branch 1 Phone 1 had
|
|
0:05:54
|
which was the primary line of 2001, but also
|
|
0:05:57
|
the intercom line of star 2001
|
|
0:05:59
|
and you can't use that as a shared line, so that's the reason
|
|
0:06:03
|
this says add failed. It didn't actually fail to add the RDP
|
|
0:06:09
|
or to even add the one line 2001
|
|
0:06:11
|
It only failed to add one of the lines which was the intercom line.
|
|
0:06:16
|
So if we go out to back to find list
|
|
0:06:21
|
and do a find
|
|
0:06:24
|
we're going to see that it created the RDP and it's even
|
|
0:06:28
|
got the one shared line. It just couldn't copy the intercom line.
|
|
0:06:31
|
So that's not a problem.
|
|
0:06:33
|
And it just logged me out.
|
|
0:06:35
|
I'm not really sure why that keeps happening.
|
|
0:06:37
|
I'm going to have to try to figure that out.
|
|
0:06:42
|
So we'll go back to Device> Device Settings and
|
|
0:06:45
|
Remote Destination Profile
|
|
0:06:51
|
under device, we saw remote destination
|
|
0:06:55
|
but the profile which is the virtual device that sums up
|
|
0:07:00
|
all of the aggregate remote destinations is what we're
|
|
0:07:03
|
focusing on right now.
|
|
0:07:05
|
Ok, so we see this. We click on the
|
|
0:07:12
|
associated shared line and we see that it's now shared between
|
|
0:07:18
|
two devices of the same Mac address. Of course the remote
|
|
0:07:22
|
destination is just a virtual. I just happen to keep the
|
|
0:07:25
|
Mac address
|
|
0:07:26
|
so that it would be easy to see and the associated devices are
|
|
0:07:30
|
SEP Mac and RDP Mac.
|
|
0:07:33
|
Certainly don't need to be RDP Mac.
|
|
0:07:35
|
Ok, if I want anything that is specific to the line
|
|
0:07:40
|
like caller ID so that when I call in from my mobile, I wanted
|
|
0:07:45
|
to display my proper caller ID, I need to -- currently I can see
|
|
0:07:50
|
that I'm on the line or on the DN as it appears as a line
|
|
0:07:55
|
on my RDP. I want to click on SEP, my desk phone, and
|
|
0:07:59
|
say, 'Edit line appearance'
|
|
0:08:02
|
Scroll down.
|
|
0:08:04
|
And I see that I don't even have display here, so if I
|
|
0:08:08
|
had let's say Ben Linus
|
|
0:08:11
|
and line text label maybe Ben Linus X2001
|
|
0:08:20
|
and then if I wanted to -- first of all save
|
|
0:08:26
|
but then after I saved, grab these settings and propagate
|
|
0:08:31
|
them out. I'm going to propagate display internal caller ID and
|
|
0:08:35
|
external phone number mask. I'm not going to propagate
|
|
0:08:39
|
line text label because there is no line text label. It's a virtual
|
|
0:08:43
|
device and actually if I do it, it'll give me an error in this version.
|
|
0:08:50
|
Ok, so now I can see that I'm on this line as it pertains to
|
|
0:08:53
|
the hardware phone I'm going to go back to the line appearance for the RDP.
|
|
0:08:58
|
Same DN, different line appearance.
|
|
0:09:00
|
And I see that those have been propagated.
|
|
0:09:05
|
And now I'm going to go back to the RDP itself.
|
|
0:09:11
|
Ok, so I've set up all that. Now I need to add my remote destination.
|
|
0:09:17
|
And actually before this, let me go ahead and go over to my user
|
|
0:09:29
|
for Ben Linus.
|
|
0:09:34
|
And let me scroll down
|
|
0:09:38
|
and here's my mobility information.
|
|
0:09:42
|
I want to enable mobility.
|
|
0:09:45
|
Choose my primary user device. I believe -- let me look at my
|
|
0:09:51
|
associated. I don't even have any associated devices, let me do that first.
|
|
0:10:02
|
Let's do directory number begins with 2001, let's just make it
|
|
0:10:06
|
simple on ourselves.
|
|
0:10:09
|
Click save selected changes.
|
|
0:10:13
|
Back to the user.
|
|
0:10:17
|
Scroll down. I've got my control device BAAE
|
|
0:10:23
|
and click enable mobility
|
|
0:10:26
|
BAAE
|
|
0:10:29
|
Now I've enabled mobility. I've go an RDP associated. I've got a
|
|
0:10:36
|
limit of four remote destinations. I can bump that as high as ten
|
|
0:10:40
|
or I could bump it as low as one or I could just leave it at the default
|
|
0:10:45
|
of four. I'm going to put it at two and then I've got
|
|
0:10:50
|
maximum wait time for desk pickup. This is when I go to hang up my
|
|
0:10:53
|
mobile phone, how many milliseconds, so by default ten seconds or ten thousand
|
|
0:10:59
|
milliseconds will be wait or used to wait -- basically place the call on
|
|
0:11:04
|
hold for ten seconds and use to wait to allow me to pick it up
|
|
0:11:07
|
at my desk. I typically like to change this to about 30 seconds,
|
|
0:11:13
|
but again whatever the lab tells you or if they don't tell you
|
|
0:11:16
|
whatever's easiest for your testing, so now back to RDP
|
|
0:11:23
|
and let's click on this link.
|
|
0:11:26
|
And I'm going to go to add new remote destination.
|
|
0:11:32
|
And now I'm going to give this a name, so let's call it
|
|
0:11:35
|
Ben's mobile.
|
|
0:11:39
|
Destination number -- well let's take a look and see
|
|
0:11:47
|
in this PSTN example.
|
|
0:11:57
|
That's the reason that kept doing that. I thought I had changed that around, but
|
|
0:12:00
|
apparently I hadn't
|
|
0:12:13
|
and that's the reason it wasn't matching the...
|
|
0:12:20
|
the outbound voice translation profile either that was marking it as
|
|
0:12:24
|
subscriber or international.
|
|
0:12:27
|
But I have a mobile number defined for Jack, so let's just
|
|
0:12:33
|
go ahead and create ephone DN let's say 7
|
|
0:12:41
|
and let's call it
|
|
0:12:46
|
number 15126026666
|
|
0:12:58
|
secondary is the same number with a plus just in case
|
|
0:13:08
|
and label is Blinus Mobile +1 512 602
|
|
0:13:37
|
and let's go to our ephone 1 and say
|
|
0:13:49
|
copy our button command
|
|
0:13:53
|
and make button 5 map to 7
|
|
0:13:56
|
and restart.
|
|
0:14:01
|
There we go.
|
|
0:14:03
|
We'll save that route config and back out of it
|
|
0:14:10
|
so that now we have...
|
|
0:14:16
|
now we've got Ben Linus's mobile as well.
|
|
0:14:19
|
Ok, so
|
|
0:14:24
|
the number is +1
|
|
0:14:28
|
whoops
|
|
0:14:34
|
just follows the format of all the others.
|
|
0:14:36
|
I've got the answer too soon timer. This means that this is typically if a
|
|
0:14:41
|
call's answered within 1.5 seconds, that's faster than most humans would
|
|
0:14:46
|
generally answer a phone, it probably means -- and I could lower this
|
|
0:14:49
|
to 1000, you know one second if I wanted.
|
|
0:14:52
|
But it probably means that the phone has been switched off and it's going
|
|
0:14:56
|
straight to Voice mail or something like that
|
|
0:14:58
|
and we don't want a call actually extended to a
|
|
0:15:03
|
mobile or any remote destination's Voice mail. The whole idea of a
|
|
0:15:08
|
single enterprise voice mobility or sorry, single enterprise Voice mail
|
|
0:15:14
|
box means that even if I have mobile connect whether it's
|
|
0:15:19
|
answered too quickly, whether I have multiple maybe three or four
|
|
0:15:24
|
remote destinations or even if it's answered too late
|
|
0:15:30
|
so whatever the call forward no answer timer is of that particular
|
|
0:15:35
|
DN and I think I actually had -- I don't know if it's in this
|
|
0:15:40
|
particular PSTN setup, I can certainly add it a BACD script
|
|
0:15:44
|
that essentially answers -- it forwards -- call forwards no answer
|
|
0:15:48
|
to a script that goes off hook and just plays a recording that
|
|
0:15:53
|
I recorded saying that this is Ben's mobile voice mail and
|
|
0:15:57
|
if you're received this, then it's too late, in other words
|
|
0:16:01
|
the answer too late timer -- well it's too late and it rang to
|
|
0:16:05
|
call forward no answer, but it shouldn't have.
|
|
0:16:07
|
So whatever the call forward no answer timer is.
|
|
0:16:10
|
First of all it takes on average in a real production network
|
|
0:16:14
|
about four seconds or about a single ring cycle to actually
|
|
0:16:20
|
set up the call for the cell towers to triangulate the mobile
|
|
0:16:24
|
and to actually get the call out.
|
|
0:16:26
|
So answer too late timer has to take that into account.
|
|
0:16:33
|
Answer too soon timer should take that into account
|
|
0:16:35
|
as well, so in other words, if it actually takes about
|
|
0:16:38
|
four seconds to set up the call and then it automatically
|
|
0:16:42
|
answers because the phone was switched off, then
|
|
0:16:46
|
15 hundred milliseconds might not nearly be long enough to
|
|
0:16:49
|
catch a switched off phone. It might need to be something
|
|
0:16:52
|
more like 45 hundred milliseconds.
|
|
0:16:55
|
Be careful when you're testing in the real lab
|
|
0:17:00
|
because if you see mobile connect and you know -- you're anticipating
|
|
0:17:07
|
it ringing on the PSTN phone and you go to answer it really
|
|
0:17:11
|
quickly and it hangs up on you and you can't figure out why
|
|
0:17:15
|
it did, it's probably because you violated the answer too soon
|
|
0:17:19
|
so you might even want to go down to something like 500 milliseconds.
|
|
0:17:22
|
For a lab environment, where in a lab environment it's going to ring
|
|
0:17:25
|
immediately same exact time as it's going to -- in fact
|
|
0:17:31
|
same exact time it's going to ring if you set up your remote destination
|
|
0:17:35
|
as an actual ISDN remote destination.
|
|
0:17:38
|
So if it's not a mobile phone, but it's actually a LAN line
|
|
0:17:41
|
and it's not even FXO, but it's actually ISDN on your side
|
|
0:17:45
|
the setup and ISDN on the terminating side where the phone is
|
|
0:17:51
|
reaching to, then it's entirely possible that it will set up almost
|
|
0:17:58
|
instantaneously, it's with a mobile cellular network that it
|
|
0:18:01
|
will take a little bit of time in real life to set up.
|
|
0:18:04
|
But probably not in the lab environment.
|
|
0:18:08
|
Ok, so the answer too late timer let's make this -- maybe they go to
|
|
0:18:17
|
ring after four seconds, I'm sorry let's say five rings, so four seconds
|
|
0:18:25
|
each, so 20 seconds -- no let's say four rings.
|
|
0:18:29
|
So we're only going to let it ring if 16 hundred milliseconds
|
|
0:18:33
|
or 16 seconds would be four rings, let's make it 15
|
|
0:18:39
|
and this is the delay before ringing.
|
|
0:18:41
|
So on a cell network, a mobile network, this might actually
|
|
0:18:46
|
make it -- take almost the equivalent of two rings or two ring backs
|
|
0:18:52
|
to the calling party before it actually rings once at the
|
|
0:18:57
|
called party, the mobile phone. So on a mobile network, a real
|
|
0:19:00
|
production network, I would almost always set this to zero
|
|
0:19:02
|
if this remote destination were a mobile phone. If it were a
|
|
0:19:08
|
ISDN link, maybe I'd also want it to ring immediately. The whole
|
|
0:19:12
|
idea of the delay before ringing is that if it's ringing both your
|
|
0:19:18
|
desk phone and your mobile phone at the same time
|
|
0:19:21
|
and you generally are at your desk and generally have your
|
|
0:19:24
|
mobile with you, every time your desk phone rings,
|
|
0:19:29
|
assuming it's an instantaneous setup, your mobile phone rings
|
|
0:19:31
|
or even if I have it left to zero every time my desk phone
|
|
0:19:35
|
rings and I don't answer within one second, one second later
|
|
0:19:40
|
my mobile phone rings and that might not be desirable.
|
|
0:19:43
|
So if you're generally at your desk, maybe you want to leave it
|
|
0:19:46
|
at 4 thousand, if you are generally away from your desk
|
|
0:19:52
|
then you probably want it at zero, ring as soon as possible.
|
|
0:19:56
|
Ok, mobile phone. There's a tick box for this and I can have
|
|
0:20:01
|
multiple remote destinations, but only one can be labeled a mobile.
|
|
0:20:05
|
And the reason for that is my mobility soft key button
|
|
0:20:09
|
when I press 'send call to mobile', that generally means I'm at my desk
|
|
0:20:14
|
phone, I'm pressing the soft key and I want it to go to my
|
|
0:20:17
|
cellular mobile phone which is right next to me so that I can
|
|
0:20:21
|
take the call immediately.
|
|
0:20:22
|
Not I want it to transfer out to somewhere else, some other
|
|
0:20:26
|
LAN line somewhere that I might have as another remote destination.
|
|
0:20:29
|
So that's why only one phone can be mobile and if you have
|
|
0:20:31
|
multiple remote destinations and you already had one selected as mobile
|
|
0:20:35
|
and the next one you set up you also select as mobile
|
|
0:20:38
|
it will unselect your first one for you.
|
|
0:20:42
|
Yes, we want to enable mobile connect and we can choose
|
|
0:20:45
|
ring schedules, so whatever your particular lab or instructions
|
|
0:20:49
|
or policy tells you and then we also have ring the destination
|
|
0:20:54
|
only if the caller is in what's called an allow ACL which
|
|
0:20:58
|
is configured up here under dial rule -- I'm sorry not dial rules,
|
|
0:21:02
|
under class of control access list
|
|
0:21:05
|
or do not ring this caller if it's in one of the class of control
|
|
0:21:10
|
blocked access lists. They're both under access list, you just configure
|
|
0:21:13
|
whether they are an allow or a block.
|
|
0:21:16
|
Ok, please assure the associated phone has the mobility soft key
|
|
0:21:20
|
configured. We haven't, but we will.
|
|
0:21:23
|
And then we see the line that was brought over from the RDP
|
|
0:21:28
|
but it hasn't been associated, we have to press associate and
|
|
0:21:31
|
save and the reason is that there might an RDP that has multiple lines
|
|
0:21:36
|
associated and different remote destinations for different lines
|
|
0:21:40
|
on that virtual device.
|
|
0:21:44
|
Ok, at this point
|
|
0:21:46
|
I have enough information to try to extend a call out to
|
|
0:21:50
|
this remote destination.
|
|
0:21:52
|
So from the PSTN phone let's dial 51260262001
|
|
0:22:04
|
so the end user's desk phone.
|
|
0:22:07
|
And let's go off hook on the corporate headquarter phone.
|
|
0:22:13
|
And let me actually bring up
|
|
0:22:20
|
let me just hang up here real briefly and let me get my
|
|
0:22:23
|
phones situated the way I want.
|
|
0:22:28
|
There we go.
|
|
0:22:32
|
There's 2001
|
|
0:22:34
|
Ok, and I've only got the PSTN and 2001, ok.
|
|
0:22:38
|
So let's go off hook, let's dial the digits.
|
|
0:22:46
|
And we can see the call ringing over here.
|
|
0:22:50
|
Well, once this updates you also can maybe see
|
|
0:22:57
|
hopefully this line here which is my Ben's mobile line.
|
|
0:23:03
|
It's also ringing in from 12065015111
|
|
0:23:12
|
Now, it's now stopped ringing.
|
|
0:23:18
|
Whoops
|
|
0:23:22
|
Ok, so now take a look at this. It stopped ringing
|
|
0:23:26
|
and that's because the answer too late timer was triggered.
|
|
0:23:29
|
However, I don't yet have any Voice mail setup on here
|
|
0:23:34
|
so it's just going to continue to ring over here.
|
|
0:23:40
|
I can't answer the phone and go to mute
|
|
0:23:46
|
and let's try to -- I don't think I had ever configured the
|
|
0:23:51
|
mobility soft key, but we'll take a look here.
|
|
0:23:56
|
Nope, I have not configured the mobility soft key yet.
|
|
0:23:59
|
So we'll come back and do that, but let's go ahead and end this call.
|
|
0:24:07
|
And try this call again.
|
|
0:24:13
|
And I probably -- we can see the call ringing here again
|
|
0:24:21
|
and I probably can't answer the call here because it's the same
|
|
0:24:24
|
phone. It just hangs up the call.
|
|
0:24:27
|
So really to be able to test this, you actually need a second PSTN phone.
|
|
0:24:32
|
You can still see it ringing, but in order to answer it and then
|
|
0:24:35
|
hang up and allow it pick back up at the desk phone and we do
|
|
0:24:40
|
actually have a secondary PSTN phone for the deep dives where
|
|
0:24:43
|
we do just that, but you did see it answer if it did, it was able to answer
|
|
0:24:49
|
then you could hang up and you'd be able to see it here as a held
|
|
0:24:55
|
call for 30 seconds.
|
|
0:25:01
|
Let's go and give
|
|
0:25:05
|
this phone
|
|
0:25:12
|
the mobility soft key.
|
|
0:25:26
|
And so for a call that is the state of connected.
|
|
0:25:33
|
We can also do on hook as well
|
|
0:25:37
|
in order to check what the status of mobility is
|
|
0:25:40
|
and I'm going to bump this up so that we don't have to hit more.
|
|
0:25:45
|
So I can do it for connected
|
|
0:25:48
|
I could also do it for on hook or idle
|
|
0:25:53
|
to see what the status of mobility is.
|
|
0:26:00
|
And let's reset and then restart any phones that have this associated
|
|
0:26:08
|
soft key layout.
|
|
0:26:11
|
Ok, so now that we're back, I can click mobility.
|
|
0:26:16
|
And I can see that you are not a valid mobile phone user.
|
|
0:26:23
|
Ha Ha, Ok!
|
|
0:26:25
|
So let's go back to Device> Phone.
|
|
0:26:30
|
And let's grab our phone.
|
|
0:26:34
|
And Branch 1 Phone 1
|
|
0:26:39
|
What we do need to do is go onto the line and associate
|
|
0:26:44
|
the line for each device, so right now we're editing the line
|
|
0:26:51
|
appearance as it appears to SEP.
|
|
0:26:55
|
Associate the user Blinus
|
|
0:27:00
|
with the line.
|
|
0:27:05
|
So scroll down and we can see Benjamin Linus is now
|
|
0:27:08
|
associated.
|
|
0:27:11
|
Let's edit the line appearance of the RDP.
|
|
0:27:16
|
And do the same thing.
|
|
0:27:20
|
Now actually if we edit the line appearance of the
|
|
0:27:25
|
RDP and associate it to the user, then this means that it will also
|
|
0:27:32
|
apply to presence information.
|
|
0:27:35
|
And this might not be what we want. We do have to have
|
|
0:27:39
|
it associated for the SEP in order to be a valid mobility user.
|
|
0:27:47
|
But we may not want it associated to the RDP for
|
|
0:27:50
|
presence information. We may not want any time that
|
|
0:27:56
|
that we're on the phone through mobile to appear busy
|
|
0:28:01
|
or even to appear anything, so let's at this point reset
|
|
0:28:09
|
or restart the phone so that it takes a hold of that information.
|
|
0:28:14
|
And we probably could have done the user ID on the actual
|
|
0:28:18
|
device as well, the owner user ID. That's actually grayed
|
|
0:28:22
|
out right now and that's typically because that relates
|
|
0:28:24
|
to device mobility.
|
|
0:28:27
|
Whoops
|
|
0:28:37
|
Ok, so this phone should be restarted.
|
|
0:28:42
|
And it still says we're not a valid mobile user.
|
|
0:28:45
|
So let's go over to end user.
|
|
0:28:56
|
We've got mobility enabled. We don't have enabled mobile
|
|
0:29:00
|
voice access, but we shouldn't need that.
|
|
0:29:23
|
Let's try
|
|
0:29:25
|
calling the number.
|
|
0:29:38
|
And hitting mute and answering the call.
|
|
0:29:44
|
And doing mute and extending it to mobility.
|
|
0:29:47
|
Let's see if this one works.
|
|
0:29:50
|
Nope, same thing. You are not a valid mobile phone user.
|
|
0:30:07
|
So if we add the line from here
|
|
0:30:19
|
Alright.
|
|
0:30:20
|
Now let's reset
|
|
0:30:25
|
and restart and it'll restart both phones.
|
|
0:30:29
|
This one's actually restarting right now.
|
|
0:30:36
|
Both the virtual -- now does it say mobility?
|
|
0:30:41
|
Nope.
|
|
0:30:44
|
It still doesn't like us, so...
|
|
0:30:47
|
Alright, so what have we done wrong? What have I missed?
|
|
0:30:53
|
Can anyone see what I've missed?
|
|
0:31:04
|
Primary extension. That might do it.
|
|
0:31:13
|
I might have to restart the phone actually even if I did that.
|
|
0:31:16
|
Did I press save?
|
|
0:31:19
|
Yes.
|
|
0:31:25
|
And I think...
|
|
0:31:31
|
Did I accidentally close the wrong thing?
|
|
0:31:33
|
Which closed all my phones, didn't it?
|
|
0:31:35
|
Perfect.
|
|
0:32:30
|
Ok, here it shows my associated remote destinations.
|
|
0:32:38
|
Owner Blinus
|
|
0:32:43
|
The associated end user
|
|
0:33:09
|
User ID Ben Linus or Blinus
|
|
0:33:56
|
Ok, I thought that I had some end user permissions.
|
|
0:34:09
|
Aha! I don't have CTI, do I?
|
|
0:34:13
|
And I do need standard CTI enabled.
|
|
0:34:19
|
That could have been it.
|
|
0:34:23
|
Ok, so let's go back to the device
|
|
0:34:31
|
and reset or restart Branch 1 Phone 1
|
|
0:34:38
|
and in the meantime I will open those phones back up.
|
|
0:35:45
|
Ok,
|
|
0:35:48
|
so
|
|
0:35:54
|
now let's take a look at
|
|
0:36:00
|
the outbound calling party transformation.
|
|
0:36:10
|
So the outbound calling party transformation CSS
|
|
0:36:14
|
whoops
|
|
0:36:15
|
remote destination profile
|
|
0:36:20
|
was previously set to the same as the actual phone.
|
|
0:36:29
|
But what happens if a...
|
|
0:36:34
|
Let's say what happens if a regular end point dials this number?
|
|
0:36:38
|
So let's actually bring up another phone here,
|
|
0:36:42
|
say corporate headquarter phone 2
|
|
0:36:46
|
If it goes to dial
|
|
0:36:58
|
let's say 2001
|
|
0:37:06
|
it's going to ring at both locations
|
|
0:37:14
|
maybe you can hear the dual ring
|
|
0:37:20
|
and I actually can't probably answer it fast enough, so it's
|
|
0:37:23
|
now stopped ringing at the PSTN
|
|
0:37:26
|
let's do end call again real quick
|
|
0:37:30
|
and let's do the redial portion
|
|
0:37:36
|
but this time I'm going to go mute.
|
|
0:37:39
|
And this time I'll answer it over on the PSTN.
|
|
0:37:48
|
And so it still shows as from 1002 and if I had a
|
|
0:37:52
|
caller ID display on 1002, then it would also show
|
|
0:37:55
|
that as well just as a normal PSTN call would.
|
|
0:37:58
|
Now note Ben Linus shows that, that call is currently on.
|
|
0:38:04
|
Now he's got privacy turned on. If he didn't have privacy turned on
|
|
0:38:08
|
if we press this button, then he'll also show who the call
|
|
0:38:13
|
is connected to if we call back in.
|
|
0:38:19
|
And if I go ahead and end the call on my mobile phone
|
|
0:38:26
|
then corporate headquarter is held and we see that this
|
|
0:38:30
|
is the held call.
|
|
0:38:33
|
Let me go ahead and press mute over here.
|
|
0:38:37
|
And I've got 30 seconds to answer the call or
|
|
0:38:47
|
Sorry, I'm hitting mute on the wrong one.
|
|
0:38:50
|
And I've got 30 seconds to resume the call essentially.
|
|
0:38:53
|
But the call is being displayed in the same manner. Now
|
|
0:38:56
|
maybe that's what we want is for it to be displayed in the
|
|
0:38:59
|
same manner, maybe we want it to show up as 1002
|
|
0:39:02
|
I don't know, maybe we don't.
|
|
0:39:04
|
What if we want it to show up as something else such as...
|
|
0:39:10
|
I want it to show up -- so I'm going to create a new partition
|
|
0:39:14
|
in calling search space.
|
|
0:39:19
|
Let's just grab
|
|
0:39:22
|
one of the existing partitions
|
|
0:39:25
|
and instead of phones, say mobility.
|
|
0:39:33
|
And create a CSS of similar name
|
|
0:39:39
|
containing only that partition.
|
|
0:39:47
|
I want 1001 to show up maybe as let's say -- or
|
|
0:39:55
|
any number's internal. I want those patterns to
|
|
0:39:58
|
show up as -- and again I'm going to do 1 through 8
|
|
0:40:02
|
otherwise I could risk getting rid of my secondary dial tone
|
|
0:40:07
|
for nine or zero.
|
|
0:40:09
|
Of course if they're in the partition where they won't be seen by or dialed
|
|
0:40:13
|
by other numbers, then it shouldn't have any problem.
|
|
0:40:15
|
Actually it won't as long as they can't be seen.
|
|
0:40:18
|
So I'm going to put it in my partition for calling party transformation pattern for
|
|
0:40:21
|
Branch 1 mobility and I'm going to say maybe use calling party's
|
|
0:40:27
|
external phone number mask.
|
|
0:40:30
|
Ok, or maybe I'd do that for one and two
|
|
0:40:39
|
but I'm going to copy that
|
|
0:40:42
|
and say that if it's used by 3000 series extensions
|
|
0:40:50
|
I want it to show up as 1, 2, 3, 1, 2, 3, 1, 2, 3,
|
|
0:40:55
|
prefix 31, so drop the zero and prefix 31
|
|
0:41:01
|
and then I'm going to go back
|
|
0:41:06
|
and I've got those two in my mobility, but I've also got
|
|
0:41:08
|
some in Branch 1 and I want to use all of these
|
|
0:41:11
|
whoops, I went to the partition instead.
|
|
0:41:13
|
I want to use all of these that are in the Branch 1
|
|
0:41:17
|
standard Branch 1 phone's partition and I want to copy
|
|
0:41:22
|
those so that they exist in my mobility partition as well
|
|
0:41:28
|
so that all the calls from the external PSTN look the same
|
|
0:41:39
|
when they're on my mobility, but that I also have the
|
|
0:41:46
|
added -- and another thing I could have done is simply
|
|
0:41:48
|
gone back to that -- you what would even be easier, I'm actually
|
|
0:41:51
|
going to delete these, the mobility ones I just created.
|
|
0:41:55
|
I have two that are specific to mobility, but I'm going to go back
|
|
0:41:59
|
to my calling search space that I created that contains mobility.
|
|
0:42:08
|
And I'm simply going to add the Branch 1 phone's
|
|
0:42:12
|
calling party transformation as well, so it will see both of
|
|
0:42:17
|
those types of patterns.
|
|
0:42:19
|
Then I'm going to go back to my remote destination profile
|
|
0:42:23
|
and I'm going to change my calling party to calling party
|
|
0:42:28
|
Branch 1 mobility and save.
|
|
0:42:32
|
So now if a call comes in from the PSTN
|
|
0:42:43
|
it should still dial and show up. Underneath I see it as
|
|
0:42:48
|
from 12065015111
|
|
0:42:54
|
so that works.
|
|
0:42:59
|
But then if the call comes from let's say 1002
|
|
0:43:06
|
then it appears on one phone as 1002 on the PSTN phone
|
|
0:43:11
|
once it refreshes, it appears as 2065011002,
|
|
0:43:16
|
exactly what we told it to.
|
|
0:43:20
|
Ok, so that's something that we can do in terms of different
|
|
0:43:23
|
calling party -- and of course adjust that to however you might
|
|
0:43:29
|
be given a particular requirement in the exam.
|
|
0:43:34
|
But how we can adjust it for mobile connect.
|
|
0:43:37
|
Also for mobile connect if we go down to service parameters
|
|
0:43:45
|
for CCM
|
|
0:44:01
|
if we go almost all the way to the bottom, actually go all the way
|
|
0:44:04
|
to the bottom and just scroll up ever so slightly
|
|
0:44:07
|
we see a whole subsection for mobility and we have a lot of
|
|
0:44:12
|
enterprise feature access codes for mid-call features.
|
|
0:44:17
|
We have the inbound calling search space for remote destination. By default
|
|
0:44:20
|
it uses the inbound gateway or trunk that the call came in
|
|
0:44:23
|
from the PSTN on. We can switch that to remote destination
|
|
0:44:27
|
profile plus line.
|
|
0:44:29
|
So the line/device approach.
|
|
0:44:34
|
We can enable mobile voice access or enterprise feature access
|
|
0:44:37
|
which by default are both set to off, we haven't
|
|
0:44:41
|
dealt with mobile voice access yet, just mobile
|
|
0:44:43
|
connect, but when we do, we'll put in the DID number
|
|
0:44:49
|
for MVA there.
|
|
0:44:51
|
Match caller ID with remote destination.
|
|
0:44:55
|
So by default, it's set to a complete match, but
|
|
0:44:58
|
we can do a partial match and it says if we choose a
|
|
0:45:01
|
partial match, enter in the next field the number of
|
|
0:45:04
|
digits that we wish to match.
|
|
0:45:06
|
This useful because I haven't pressed saved yet.
|
|
0:45:09
|
So if I dialed in from -- let's go ahead and blow this phone up a little bit.
|
|
0:45:16
|
If I dialed in from my proxy line,
|
|
0:45:20
|
and I dial let's say 2065011002
|
|
0:45:28
|
which I have over here on my left
|
|
0:45:32
|
then we see this phone shows up right now as
|
|
0:45:36
|
from Ben Linus.
|
|
0:45:39
|
And so why does it show up as from Ben Linus.
|
|
0:45:46
|
Any idea?
|
|
0:45:53
|
We know that our remote destination begins with a
|
|
0:45:56
|
+1 512, but if we take a look at our inbound call where the call
|
|
0:46:04
|
came in -- let's just clear all these gateways and
|
|
0:46:07
|
send the call in again.
|
|
0:46:09
|
I'll just hit redial on the phone. Selecting line 5, Ben Linus's phone.
|
|
0:46:17
|
Ok, the call came in from 1512
|
|
0:46:24
|
So how did it actually get into and able to be seen
|
|
0:46:32
|
as +1 -- I'm sorry -- yeah, as the called party
|
|
0:46:43
|
+1206 -- I'm sorry, the calling party +1512602
|
|
0:46:50
|
Well, we already have globalized the number, right?
|
|
0:46:53
|
That's what you might say.
|
|
0:46:55
|
Ok, that's a fair enough assumption or understanding.
|
|
0:46:58
|
Let's try a different situation just to exercise that idea.
|
|
0:47:02
|
Clear off all the gateways and let's try a call again.
|
|
0:47:09
|
This time I'm going to call in again from the same line, but I'm
|
|
0:47:14
|
going to call into let's say into Branch 2
|
|
0:47:22
|
so let's call into 703 -- of course coming from the US it would be
|
|
0:47:36
|
Nope, I think I've got one too many threes there.
|
|
0:47:38
|
011207037333, yep, ok let's call in from Ben's mobile line.
|
|
0:47:52
|
Ok, it doesn't like dialing from there. I think I know why.
|
|
0:48:05
|
It's because I haven't set that particular number up this 512
|
|
0:48:20
|
Oh, no. It's because I'm trying it out of the PSTN.
|
|
0:48:22
|
Alright.
|
|
0:48:24
|
So I'm sorry. I'm still wanting to call let's say
|
|
0:48:27
|
7033001, there we go.
|
|
0:48:33
|
Let me pull up 3001
|
|
0:48:44
|
Ok, so let's go off hook on Ben's mobile line.
|
|
0:48:55
|
and here it's coming in from Ben Linus mobile 1512
|
|
0:49:02
|
So we did essentially the same call -- well we did
|
|
0:49:06
|
from the same line, but it's coming in a different gateway. It's coming in
|
|
0:49:10
|
the Branch 2 gateway. Aren't they both globalizing?
|
|
0:49:16
|
And the answer is, "Yes, they're both globalizing if we take a look
|
|
0:49:20
|
back at CUCM,
|
|
0:49:24
|
but if we take a look at the gateway for Branch 2
|
|
0:49:32
|
it's globalizing here on the actual gateway in CUCM.
|
|
0:49:39
|
Ok, it's globalizing...
|
|
0:49:43
|
I got logged out
|
|
0:49:44
|
it's globalizing in CUCM whereas the corporate headquarter
|
|
0:49:50
|
is a SIP trunk and so we weren't doing any globalizing here in CUCM.
|
|
0:49:54
|
We had done it in IOS.
|
|
0:49:58
|
So that's the major difference is that if the phone, the calling
|
|
0:50:03
|
number is globalized in CUCM, the remote destination is matched
|
|
0:50:09
|
prior to the gateway's globalization if it's done in CUCM.
|
|
0:50:14
|
However, remember we talked about digit manipulation in IOS
|
|
0:50:20
|
CUCM is unaware of any digit manipulation in IOS. It's simply being
|
|
0:50:24
|
passed digits, so in the case of the corporate headquarter
|
|
0:50:27
|
is a SIP trunk and SIP passes a plus, we had already added the
|
|
0:50:33
|
plus to the number before it had been handed on to the CUCM
|
|
0:50:43
|
server, so as far as CUCM saw, when it came in
|
|
0:50:49
|
it didn't do any globalization, it matched whatever it was
|
|
0:50:52
|
when it came in which already included the plus.
|
|
0:50:55
|
So this where things like partial match
|
|
0:51:02
|
for remote profiles can be really or remote destinations
|
|
0:51:13
|
can be really useful, so partial match let's say
|
|
0:51:16
|
ten digits or possibly even in the case of -- actually
|
|
0:51:23
|
there's a unique case for European gateways and
|
|
0:51:26
|
European numbers where if for some reason a --
|
|
0:51:34
|
let's go ahead and do this first and then I'll actually bring
|
|
0:51:36
|
up a whiteboard and show you this real quick and then we'll
|
|
0:51:42
|
cut for today.
|
|
0:51:45
|
So I go to partial match for ten digits
|
|
0:51:48
|
so now when the call comes in, same call,
|
|
0:51:53
|
from Ben Linus's mobile
|
|
0:52:01
|
because I'm only matching a partial match now
|
|
0:52:04
|
it now shows -- it doesn't show from Ben Linus mobile
|
|
0:52:07
|
which is the PSTN caller ID, it shows his corporate caller ID
|
|
0:52:12
|
which is Ben Linus and his corporate 4-digit extension.
|
|
0:52:18
|
Ok, so that's important.
|
|
0:52:22
|
So one last thing for today
|
|
0:52:26
|
is that if I'm actually trying to match a remote destination
|
|
0:52:32
|
for a European gateway or European phone where
|
|
0:52:37
|
I would have a gateway sending in the digits of maybe let's say
|
|
0:52:44
|
0207037, I'm sorry, not 7
|
|
0:52:50
|
but 3001
|
|
0:52:57
|
and my remote destination is...
|
|
0:53:03
|
Oh, no actually it would be -- calling number would actually
|
|
0:53:07
|
be the remote phone, so let's say 7555
|
|
0:53:14
|
that's maybe the 3001 mobile number.
|
|
0:53:26
|
So the gateway sends in
|
|
0:53:35
|
this number
|
|
0:53:38
|
but the remote destination
|
|
0:53:42
|
is this number, +31 207037555
|
|
0:53:50
|
The difference between a US and most other countries'
|
|
0:53:54
|
remote destination numbers is this particular digit right here
|
|
0:53:59
|
does not match.
|
|
0:54:03
|
That was a 1 back there.
|
|
0:54:08
|
Ok, so this digit doesn't match.
|
|
0:54:12
|
And when it says it has to be a partial match, we obviously
|
|
0:54:15
|
could say partial match and 1, 2, 3, 4, 5, 6, 7, 8, 9 digits
|
|
0:54:22
|
but even if we said partial match nine digits, it's actually
|
|
0:54:26
|
critically important that what the gateway is sending in
|
|
0:54:32
|
is equal to or a subset of the remote destination
|
|
0:54:37
|
and then partial match the number of digits will apply properly.
|
|
0:54:43
|
But if what the gateway is sending in is different than
|
|
0:54:48
|
completely different, doesn't match up
|
|
0:54:50
|
then it doesn't matter how many partial digits I tell it to match
|
|
0:54:53
|
it won't match, so this is important if you wanted to use
|
|
0:54:56
|
mobile connect or more specifically mobile voice
|
|
0:54:59
|
access in the sense of calling inbound and matching the
|
|
0:55:02
|
remote destination with a plus number, you would need to
|
|
0:55:06
|
make sure that this gateway in whatever city or country
|
|
0:55:13
|
you had it where zero was sent inbound was either H.323
|
|
0:55:20
|
back to CUCM or SIP -- not SAP, but SIP
|
|
0:55:26
|
and that you did digit manipulation there on the actual gateway
|
|
0:55:31
|
to remove this zero and prefix +31
|
|
0:55:35
|
or at least normalize it to remove that zero, but
|
|
0:55:39
|
hopefully at that point, you just go ahead and prefix +31
|
|
0:55:42
|
I suppose if it was H.323, you would only be able to prefix 31
|
|
0:55:45
|
because the plus would be lost and then you could add that plus back to all
|
|
0:55:49
|
unknown numbers which is what you would send them all into CUCM as
|
|
0:55:52
|
or if it were SIP which is a good idea these days
|
|
0:55:58
|
you would just prefix the +31
|
|
0:56:01
|
but that is necessary in order for the remote destination
|
|
0:56:05
|
profile to match even a partial match with that zero issue.
|
