|
0:00:13
|
So we're back and let's take a look at our tasks for today.
|
|
0:00:22
|
To begin with,
|
|
0:00:25
|
make sure that when you're looking at and
|
|
0:00:28
|
performing these labs that you can download,
|
|
0:00:32
|
later after each deep dive that you are following the notes in the beginning,
|
|
0:00:36
|
most of these deep dive lab scenarios require existing configuration
|
|
0:00:40
|
befire they can begin to be configured, also most lab scenarios use
|
|
0:00:44
|
different preconfiguration from other deep dive labs
|
|
0:00:47
|
therefore it's necessary to load the start up configs
|
|
0:00:50
|
prior to the beginning of any of these lab scenarios.
|
|
0:00:53
|
If you're renting from ine of voice rental rack,
|
|
0:00:56
|
then you can use the start up configs for this deep dive,
|
|
0:01:00
|
by logging into your member's account, navigating to the rack rental tab
|
|
0:01:04
|
and clicking on control panel,
|
|
0:01:06
|
click here to choose a configuration to be loaded on you voice rack,
|
|
0:01:10
|
and then choosing the appropriately named selection for this module.
|
|
0:01:14
|
Now do note this will only load you router and switch
|
|
0:01:16
|
config so PSTN routers 2 and 3,
|
|
0:01:20
|
so corporate headquarter branch1 and branch2 respectively,
|
|
0:01:23
|
and then switch1 at headquarters and switch2 at branch2.
|
|
0:01:28
|
Branch1 has a ethernet switch module
|
|
0:01:31
|
however it does not load your CUCM configs at this time.
|
|
0:01:34
|
So for CUCM configs, you're gonna log on
|
|
0:01:37
|
to the Cisco Unified communication administration page,
|
|
0:01:42
|
change the host name or the pub to
|
|
0:01:45
|
177.1.10.10 if it's not already done.
|
|
0:01:48
|
And then activate all of your services on both the pub and sub,
|
|
0:01:52
|
and then finally you're gonna upload import the
|
|
0:01:56
|
CUCM start up .tar file that we provide for you,
|
|
0:02:00
|
as a part of every deep dive module.
|
|
0:02:03
|
We also provide all of the final configurations for CUCM,
|
|
0:02:06
|
and all of the routers as well of course.
|
|
0:02:09
|
And we give you a demo, a video on how to do that
|
|
0:02:12
|
if you happen to have never done that import before.
|
|
0:02:15
|
And we mentioned that a couple things happen on import that we
|
|
0:02:20
|
almost always just have to fix, they're just bugs with 7.0
|
|
0:02:24
|
One of the things that you should always
|
|
0:02:26
|
import all of your configuration except
|
|
0:02:29
|
for called and calling party transformations.
|
|
0:02:32
|
And when you do import everything, you should do click the override,
|
|
0:02:36
|
override existing configuration button.
|
|
0:02:39
|
Then you should go back in one at a time
|
|
0:02:41
|
and import your called and calling configuration
|
|
0:02:46
|
there's two more imports, but just of each one
|
|
0:02:50
|
of those checkboxes at a time and do not click override,
|
|
0:02:53
|
this is just due to a bug where they happen to
|
|
0:02:56
|
if imported together with the override configuration button,
|
|
0:03:00
|
it happen to normally, one overrides the other
|
|
0:03:06
|
and called party transformation patterns end up in calling party,
|
|
0:03:10
|
calling party end up in the called party,
|
|
0:03:12
|
so it's just a little bit of a mess, a little bit of a bug,
|
|
0:03:15
|
but you can avoid it by using the method I just mentioned.
|
|
0:03:19
|
Also another thing, any SIP trunks almost always
|
|
0:03:24
|
it imported with their significant digits
|
|
0:03:28
|
for inbound call routing set to all
|
|
0:03:30
|
rather than whatever else you would set them
|
|
0:03:33
|
H323 and MGCP gateways get imported with the proper
|
|
0:03:38
|
significant number of digits but
|
|
0:03:41
|
it's not that we exported them improperly, it's just that another bug
|
|
0:03:44
|
you just need to go back to your SIP trunk and
|
|
0:03:47
|
change your sig digits to four.
|
|
0:03:49
|
You also need to reset every gateway
|
|
0:03:52
|
every time you do this, every time you do an import.
|
|
0:03:56
|
Also one other thing we note in the video is that sometimes calling
|
|
0:03:59
|
search spaces don't have partitions imported with
|
|
0:04:03
|
their, calling search spaces don't have the partitions imported properly.
|
|
0:04:08
|
This is just due to the order in which they import, they almost always
|
|
0:04:12
|
do work properly, but if they don't, you may just need to do
|
|
0:04:16
|
another import or on top of each other.
|
|
0:04:19
|
These things really don't take a lot of time,
|
|
0:04:21
|
there are just some considerations to find and really the
|
|
0:04:24
|
only way that we can provide with the full configuration
|
|
0:04:30
|
either start up or final with the working configs
|
|
0:04:35
|
of the CUCM server without doing something like
|
|
0:04:38
|
taking of the ware VM snapshot and handing it out to you which
|
|
0:04:41
|
first of all the VM ware snapshot would probably be anywhere
|
|
0:04:44
|
they tend to be anywhere from two to five gigs for just the snapshot
|
|
0:04:49
|
not to mention the rest of the virtual server, so we're talking
|
|
0:04:54
|
we'd have to hand out 30 gig files and obviously that's not
|
|
0:04:59
|
very feasible for download to have a 30 gig file
|
|
0:05:05
|
for publisher and then another one for subscriber for every single
|
|
0:05:09
|
and then the snapshots, so another maybe two to five gig
|
|
0:05:13
|
per snapshots, so initial and final of pub and sub, so now we're talking
|
|
0:05:18
|
32, 34, 68, to 70 gig just for your CUCM pub and sub.
|
|
0:05:27
|
And do that for every single deep dive,
|
|
0:05:29
|
it's obviously not practical in any way.
|
|
0:05:32
|
And if we don't hand these out to you,
|
|
0:05:36
|
well then how are you gonna practice on your own racks if you
|
|
0:05:39
|
a lot of students, a lot of you guys do have your own rack of equipment.
|
|
0:05:44
|
OK? So this is the reason that we do the exported CSV file,
|
|
0:05:48
|
very lightweight, typically under 300K,
|
|
0:05:51
|
and the few little things that we have to go
|
|
0:05:53
|
through to make it work properly really are worth
|
|
0:05:58
|
if you ask me, they are worth even my own doing
|
|
0:06:01
|
in fact it's the way I do it, I don't use any VM ware snapshots
|
|
0:06:05
|
liable and they are much quicker to import and deal with so
|
|
0:06:15
|
the VM or snapshots that I've used in the past.
|
|
0:06:19
|
One other thing is that the LDAP does not import properly
|
|
0:06:24
|
whenever we import the LDAP settings
|
|
0:06:27
|
it almost never imports properly, so we actually don't include
|
|
0:06:31
|
the end user LDAP directory or LDAP authentication
|
|
0:06:36
|
imports or any of the end users because those are not
|
|
0:06:39
|
create it, they are imported from the
|
|
0:06:44
|
Microsoft active directory LDAP. So actually that's one of the
|
|
0:06:47
|
things I save for this particular lab
|
|
0:06:50
|
we're gonna go through and reimport those users, we haven't do
|
|
0:06:53
|
we haven't done that in most of the previous labs
|
|
0:06:56
|
and one of the reasons we will do it today and on any deep dive,
|
|
0:07:00
|
is to remind you that you need to do it
|
|
0:07:02
|
but I should say on any deep dive that specifically
|
|
0:07:06
|
the components that technologies in the deep dive rely
|
|
0:07:11
|
on end user configuration.
|
|
0:07:16
|
That's where the readme LDAP is important.
|
|
0:07:21
|
OK?
|
|
0:07:23
|
Also in the last deep dive module, we changed our SIP trunk
|
|
0:07:28
|
to point to DNSS RV records rather than IP addresses
|
|
0:07:31
|
this means that you'll need to SSH into your pub
|
|
0:07:33
|
and sub and re-issue this command and reboot both of them.
|
|
0:07:37
|
It is good to reboot both of them after you do your
|
|
0:07:40
|
import anyhow, but I've actually gone ahead and taken out
|
|
0:07:44
|
this taks and I've just put in IP addresses back
|
|
0:07:47
|
in our SIP trunks rather than relying on domain names
|
|
0:07:51
|
that way you don't have to do this set DNS primary command,
|
|
0:07:54
|
however this is certainly something you could have to do in the real lab.
|
|
0:07:58
|
They may have a SIP trunk set up for you with DNS
|
|
0:08:03
|
or even just a host name in a MGCP gateway
|
|
0:08:07
|
or they could tell you that you need to configure an MGCP,
|
|
0:08:11
|
or H323 gateway or a SIP trunk using host names, using domain names
|
|
0:08:18
|
and they might give you the IP address of the DNS server
|
|
0:08:22
|
or have you set the DNS server up yourself,
|
|
0:08:26
|
and the only one that you would have available to you is on the
|
|
0:08:28
|
UCCX windows platforms still in version 7
|
|
0:08:33
|
dns server there, but you do have one available to you
|
|
0:08:36
|
and you could set it up and they very well may not have
|
|
0:08:40
|
as part of your expert level task that they expect you
|
|
0:08:43
|
to demonstrate to them your expertise, they may not have set anything up
|
|
0:08:48
|
in the set network DNS primary or set up the CUCM pub
|
|
0:08:52
|
and sub to actually point to the
|
|
0:08:58
|
so this is a very real world task, something you could be
|
|
0:09:02
|
asked to do as well, so keep that in mind.
|
|
0:09:06
|
OK?
|
|
0:09:07
|
And if you're not using our racks, then be sure to
|
|
0:09:09
|
apply these router in CUCM start up configs
|
|
0:09:12
|
for your own lab hardware before beginning, so let's go ahead and do that
|
|
0:09:15
|
let's go ahead and bring up our CUCM cluster.
|
|
0:09:19
|
Let's log in and then let's bring up the LDAP
|
|
0:09:22
|
readme file that we include
|
|
0:09:28
|
with each deep dive
|
|
0:09:33
|
We mentioned everything that we just talked about
|
|
0:09:37
|
and we give you the four LDAP directories
|
|
0:09:40
|
that we had created and how to do the LDAP authentication,
|
|
0:09:46
|
what we had done, I believe it was back in deep dive module 4
|
|
0:09:50
|
when we discussed users groups and LDAP.
|
|
0:09:54
|
Well let's just do that real quick
|
|
0:09:56
|
let's go over to system, first of all let's check our users, end users
|
|
0:10:03
|
click find, there are none, but we also don't see anywhere up here
|
|
0:10:07
|
the ability to add user, that's because
|
|
0:10:12
|
over on system LDAP, LDAP system, so system column
|
|
0:10:15
|
and then LDAP, and then the LDAP system.
|
|
0:10:19
|
It is already checked to enable synchronization.
|
|
0:10:22
|
OK. So this does import properly however
|
|
0:10:26
|
so as soon as we enable synchronization, we disable our ability
|
|
0:10:30
|
to add new user, if I uncheck this and click save,
|
|
0:10:35
|
now I would be able to go back to end user and add a new user.
|
|
0:10:45
|
Save and this is when longer add a new user. OK?
|
|
0:10:52
|
So we'll go to LDAP directory, do a find
|
|
0:10:55
|
there are none because we didn't import any,
|
|
0:10:58
|
users not found in the corporate directory
|
|
0:11:00
|
will be deleted, that's OK, because we don't have any.
|
|
0:11:03
|
But a correct integration with LDAP users, it's necessary
|
|
0:11:06
|
that the user ID attribute is unique. OK?
|
|
0:11:10
|
We already know that from module 4.
|
|
0:11:12
|
And we give you all the information to use, so we'll just copy
|
|
0:11:20
|
operator at ine.com, the LDAP password is ccie cisco.
|
|
0:11:26
|
Place that in twice to confirm and then we give you the user search space.
|
|
0:11:33
|
OK? We alse tell you that IP phones should be synchronized
|
|
0:11:38
|
for phone number, so let's change that and the LDAP
|
|
0:11:41
|
server information, now note from the original LDAP
|
|
0:11:45
|
module 4, this IP changed and I've
|
|
0:11:48
|
recorded an intro that should be at the beginning of this
|
|
0:11:53
|
recorded module once it is recorded and available as a curriculum.
|
|
0:11:59
|
OK? We leave the port 389 and use SSL unchecked
|
|
0:12:03
|
and we click save, now this will not show add succesful
|
|
0:12:07
|
if it could not log in with this user name and password,
|
|
0:12:10
|
to this search base, so this means that it was
|
|
0:12:14
|
truly succesful in going out and verifying this exists.
|
|
0:12:18
|
Now no users, open this in a new window, no users exist yet
|
|
0:12:24
|
that's just because we need to perform a full sync now
|
|
0:12:29
|
we're going to go ahead and copy this
|
|
0:12:33
|
while we wait for this to be synced, they should probably
|
|
0:12:35
|
be done by about now and there we've got some records.
|
|
0:12:39
|
OK? So we're gonna copy this and the next one was ine
|
|
0:12:47
|
so we will change
|
|
0:12:51
|
search base, user name and password, and IP phone and server
|
|
0:12:56
|
that populated for us with a copy, so that was nice,
|
|
0:12:59
|
we'll perform a full sync, OK. We'll do another copy
|
|
0:13:04
|
this third one was security.
|
|
0:13:10
|
Add the user search base.
|
|
0:13:14
|
Save, perform full sync. OK.
|
|
0:13:19
|
We'll copy and do the
|
|
0:13:25
|
I skipped over one did I?
|
|
0:13:29
|
IT sales and security, yes I skipped over the first one which was executive.
|
|
0:13:35
|
OK?
|
|
0:13:39
|
Back, let's just verify IT.
|
|
0:13:43
|
Sales is sales, security is secure.
|
|
0:13:49
|
Copy it, paste it , grab the new search space
|
|
0:13:57
|
first ou really changes, save, perfom full.
|
|
0:14:03
|
Now if we do a find of our users, we should have a lot more.
|
|
0:14:07
|
Yes, 22 records, excellent.
|
|
0:14:10
|
We're only going to need two of them today, but we will need them.
|
|
0:14:13
|
And then although we probably won't need
|
|
0:14:16
|
actually we will not need this today, actually we will so
|
|
0:14:21
|
use LDAP for authentication for end users.
|
|
0:14:27
|
bottom
|
|
0:14:31
|
text file that we include for all of the specifics
|
|
0:14:35
|
and note for our search space as we mentioned back in module 4,
|
|
0:14:39
|
we're only searching the OU of Island Natural Exports
|
|
0:14:43
|
we're not searching any of the sub OUs of IT, security, sales
|
|
0:14:47
|
RND, executive, or any of the others that we have,
|
|
0:14:51
|
this way we're including all of those sub organizational units.
|
|
0:14:59
|
Save and now we should be good for LDAP authentication.
|
|
0:15:03
|
As soon as we turn on LDAP authentication,
|
|
0:15:06
|
what happened was the users ability to save a password,
|
|
0:15:10
|
became unavailable from our DC directory here in our CUCM server,
|
|
0:15:17
|
although we still can do pin and control devices and things of that nature.
|
|
0:15:23
|
OK?
|
|
0:15:25
|
So we'll go back to the beginning.
|
|
0:15:28
|
Set up our LDAP and we're ready to begin.
|
|
0:15:33
|
So now let's take a look at our first task, 12.1
|
|
0:15:37
|
Mobile Connect Basics.
|
|
0:15:39
|
We're told to configure CUCM, such that when either Hugo
|
|
0:15:43
|
known as Hurley Reyes,
|
|
0:15:47
|
his corporate directory phone2, at the dn of 1002,
|
|
0:15:52
|
or when James, also known as Sawyer Fords
|
|
0:15:56
|
branch2 phone2 at the dn of 3002 are called,
|
|
0:16:01
|
that their corresponding mobiles, mobile phones are rung
|
|
0:16:05
|
but only after their desk phone rings fully once.
|
|
0:16:11
|
Also we're told when Hurley's Corporate Headquarter phone2 is rung,
|
|
0:16:14
|
we're told to ring his home phone as well.
|
|
0:16:18
|
We're given this information here
|
|
0:16:20
|
and we're told from the information below, calculate the time that it
|
|
0:16:23
|
takes those mobile phones and home phones to ring to voicemail.
|
|
0:16:28
|
And prevent this mechanism from ringing into any of their
|
|
0:16:31
|
respective voicemail boxes, so it sounds like their mobile phones,
|
|
0:16:35
|
and home phones have voicemail set up on them.
|
|
0:16:39
|
Let's just test that out briefly.
|
|
0:16:43
|
Go over to our
|
|
0:16:47
|
remote phones and let's have Jame Ford call out
|
|
0:16:52
|
and we'll also bring out our routers where we've got
|
|
0:16:58
|
rug ISDN and termon turned on to all of them.
|
|
0:17:03
|
So we'll have James Ford whose in Amsterdam, the Netherlands,
|
|
0:17:08
|
we'll have him call out his local gateway to his mobile phone
|
|
0:17:13
|
So his mobile phone is, it's actually a long distance number
|
|
0:17:18
|
0 for long distance, 0 for secondary dial tone.
|
|
0:17:22
|
If you remember from previous modules and then 670 3575
|
|
0:17:30
|
and we see that it appears here on line 6 of our PSTN phone,
|
|
0:17:35
|
so we have Hurley's mobile and Hurley's home phone corresponding.
|
|
0:17:42
|
OK? So let's have James call out to that number.
|
|
0:17:49
|
OK? We're off hook, dial 0
|
|
0:17:56
|
0 and we'll have him dial 670357575
|
|
0:18:17
|
It took too long for this to enter, so let's try this again,
|
|
0:18:22
|
there's a slight delay, so let's dial 00670357575
|
|
0:18:34
|
OK? It's not able to dial right now, let's see if he can dial 112.
|
|
0:18:40
|
OK. He can dial out to, it might be that this user
|
|
0:18:44
|
doesn't have rights to dial out there, let's try it from
|
|
0:18:48
|
Desmond's phone at 3001, 00
|
|
0:18:54
|
670357575, there we go.
|
|
0:19:01
|
So we're ringing to mobile.
|
|
0:19:11
|
Voicemail.
|
|
0:19:18
|
OK. So we heard his voicemail recording
|
|
0:19:21
|
saying that you've reached either Sawyer or Hurley's
|
|
0:19:25
|
voicemail and if you're hearing this, it's too late.
|
|
0:19:27
|
So it forwarded after three rings, well let's just make sure
|
|
0:19:33
|
it was three rings proper, so let's do redial.
|
|
0:19:38
|
Really we have to listen for
|
|
0:19:50
|
that was actually me hitting the up and down volume button
|
|
0:19:53
|
that you might have heard somewhat of a fourth ring.
|
|
0:19:56
|
So apologize for doing that, it's just the wrong time,
|
|
0:19:58
|
but it did ring after three rings, let's test out Hurley's home phone as well.
|
|
0:20:05
|
OK? So let's
|
|
0:20:08
|
up to
|
|
0:20:11
|
Jack's phone at corporate headquarters 1001 and we'll dial
|
|
0:20:17
|
9 the local number 206 501 5151
|
|
0:20:27
|
get ringin on Hurley's mobile line,
|
|
0:20:31
|
so there's two, then go to voicemail after three rings.
|
|
0:20:44
|
OK? So it went after three rings, so now let's try Hurley's mobile.
|
|
0:20:58
|
That's one, that's two, three.
|
|
0:21:08
|
That's four.
|
|
0:21:19
|
OK.
|
|
0:21:22
|
We've got the calls, it does ring
|
|
0:21:25
|
to Hurley's mobile voicemail after four rings
|
|
0:21:29
|
to Hurley's home after three and to Sawyer's home after three.
|
|
0:21:34
|
So we can calculate the time
|
|
0:21:39
|
we pretty much know that a ring is just about,
|
|
0:21:42
|
depends of course on the ring cadence,
|
|
0:21:44
|
but it's just about with the standard default ring cadence that
|
|
0:21:48
|
CUCM or actually CME because the PSTN phone is on CME,
|
|
0:21:53
|
has is about four seconds per ring.
|
|
0:21:57
|
So we know that this is about 16 seconds and these are about 12.
|
|
0:22:02
|
And we make variations and adjustments if we need to
|
|
0:22:05
|
but we'll go on that premise.
|
|
0:22:09
|
OK? So we're told to prevent this mechanism
|
|
0:22:12
|
the mobile connect mechanism from ringing into any of their
|
|
0:22:15
|
respective voicemail boxes at their mobiles.
|
|
0:22:18
|
This is what's known as single enterprise voicemail box.
|
|
0:22:22
|
Now we mentioned that in our CUCM cluster
|
|
0:22:27
|
at our desk phones, we don't have actually
|
|
0:22:29
|
Unity Connection set up for this particular
|
|
0:22:32
|
deep dive module, that being said
|
|
0:22:35
|
we would have forward call to voicemail on busy
|
|
0:22:40
|
or no answer set on our line, our line of our standard
|
|
0:22:46
|
phone or IP desk phone and then also
|
|
0:22:49
|
the line that is associated as a shared line
|
|
0:22:54
|
to our remote destination profile, our virtual phone
|
|
0:22:57
|
we showed from the slides and the concepts.
|
|
0:23:00
|
So the idea is we don't want the call to go to our
|
|
0:23:06
|
mobile voicemail when one call comes in
|
|
0:23:10
|
and then another call comes in at a different
|
|
0:23:12
|
time based on our ring schedule, we'll look at next
|
|
0:23:15
|
and it goes to our home phone, gets left on that voicemail,
|
|
0:23:19
|
and then at another time all the ring destinations are turned off,
|
|
0:23:24
|
via a ring schedule and so then the third voicemail gets left at our
|
|
0:23:29
|
enterprise desk phone voicemail. We've got three different calls
|
|
0:23:33
|
that's possibly from different callers left at three
|
|
0:23:35
|
different voicemail boxes. This can be, not only rather confusing
|
|
0:23:40
|
but let's say if a voicemail get's left or too many
|
|
0:23:43
|
get left at our home, it's gonna perturb other people that happen
|
|
0:23:46
|
to live in our home and have to go through the voicemail
|
|
0:23:49
|
and don't want to listen to work calls.
|
|
0:23:52
|
OK? So the idea is that we want everything to ring
|
|
0:23:55
|
to our single enterprise voicemail box
|
|
0:23:59
|
that is attached or associated with our desk phone
|
|
0:24:02
|
or Unity Connection or Unity, whatever voicemail
|
|
0:24:06
|
system we happen to be using to that enterprise voicemail.
|
|
0:24:09
|
And the way that we have the single enterprise voicemail,
|
|
0:24:12
|
is to prevent the unified or mobile connect mechanism
|
|
0:24:18
|
from ringing any of these mobile or remote destination numbers
|
|
0:24:23
|
long enough so that the call is answered by
|
|
0:24:27
|
the voicemail, because if the call is answered by their mobile voicemail,
|
|
0:24:30
|
mobile connect just knows, hey we connected.
|
|
0:24:34
|
We were told to ring a remote destination and the desk phone,
|
|
0:24:37
|
maybe multiple remote destinations and the desk phone,
|
|
0:24:40
|
all concurrently and someone connected
|
|
0:24:45
|
so we're good, it doesn't distinguish between a voicemail
|
|
0:24:49
|
system connecting, and a human connecting.
|
|
0:24:54
|
Now, so that's all find and good, we can tell it not to ring
|
|
0:24:58
|
long enough, so one of those remote destinations
|
|
0:25:01
|
in order to ring into that particular,
|
|
0:25:05
|
that associated remote destination device voicemail.
|
|
0:25:08
|
So we have single enterprise unified voicemail box
|
|
0:25:12
|
that's all find and good, but what about the times when we
|
|
0:25:16
|
jump on a flight or we're underground on the
|
|
0:25:20
|
tube or a train or we're out of touch, out of reach
|
|
0:25:26
|
or we just happen to turn off our mobile phone.
|
|
0:25:29
|
And mobile connect was set to extend the call
|
|
0:25:33
|
to our mobile phone during that particular time
|
|
0:25:36
|
and from that particular caller.
|
|
0:25:39
|
So our mobile phone is turned off.
|
|
0:25:41
|
What happens when your mobile phone is turned off and someone calls it?
|
|
0:25:46
|
That's right, that's ecactly right, your response is exactly right.
|
|
0:25:49
|
It rings directly to voicemail. So when it rings directly to voicemail,
|
|
0:25:54
|
it's answered almost immediately. How do we prevent this?
|
|
0:26:00
|
Well
|
|
0:26:03
|
forwarding it to voicemail after four rings
|
|
0:26:05
|
we said we were going to put in a timer that was less
|
|
0:26:08
|
than four rings, so less than 16 seconds, so we'll do
|
|
0:26:11
|
maybe something like 15 or 14 seconds.
|
|
0:26:14
|
Maybe 15 seconds, just to give it just enough time to ring
|
|
0:26:19
|
and enough time that they can pick it up or as much time
|
|
0:26:21
|
as we can possibly give the remote destination time to pick it up
|
|
0:26:24
|
without going into their voicemail.
|
|
0:26:27
|
But
|
|
0:26:29
|
we don't want any call that's answered immediately
|
|
0:26:33
|
to be allowed to continue, so the first one was known as the
|
|
0:26:37
|
aswer to late timer, if they answered too late
|
|
0:26:41
|
we're not going to allow them to
|
|
0:26:45
|
we're not gonna allow that mobile connect call to be connected.
|
|
0:26:47
|
We'll stop it. We'll stop it ringing, stop it alerting
|
|
0:26:51
|
before it's too late, that's the answer to late timer.
|
|
0:26:54
|
If we had our phones off, mobile phone or
|
|
0:26:58
|
home phone was set to forward directly to voicemail
|
|
0:27:01
|
because we wanted a quiet morning whatever
|
|
0:27:04
|
then it would be answered too early so there's also a
|
|
0:27:06
|
default answer to early timer.
|
|
0:27:09
|
If the calls answered too early, we'll take a look at this
|
|
0:27:12
|
with the RTMT the
|
|
0:27:19
|
with our RTMT performance monitors statistics
|
|
0:27:22
|
as we have with many other things.
|
|
0:27:26
|
If that happens, then we also want the call
|
|
0:27:29
|
to be immediately disconnected from that remote destination
|
|
0:27:33
|
not allow the calling party
|
|
0:27:37
|
to ultimately be connected to that remote destination,
|
|
0:27:42
|
because we know that the human couldn't have answered
|
|
0:27:44
|
in that amount of time.
|
|
0:27:49
|
OK?
|
|
0:27:51
|
So looking on, we're also told to allow either Hurley
|
|
0:27:55
|
or Sawyer to be able to transfer calls
|
|
0:27:58
|
from their mobile phones back to their desk phones
|
|
0:28:01
|
so we mentioned earlier that was simply hanging up
|
|
0:28:05
|
at their mobile phone and it would be on hold at their
|
|
0:28:08
|
desk phone for a period of time, but then also
|
|
0:28:11
|
to be allowed from their desk phones
|
|
0:28:14
|
to transfer calls back to their mobile phones
|
|
0:28:16
|
with a single button, so this is the soft key
|
|
0:28:20
|
send call to mobile, that we're going to be able to
|
|
0:28:23
|
enter but of course we have to configure that softkey.
|
|
0:28:29
|
Then we're also told to allow either user to give a log in
|
|
0:28:31
|
to their CUCM user page and set up or change
|
|
0:28:35
|
any of their mobile connect remote phones.
|
|
0:28:37
|
That's right we can give users the ability
|
|
0:28:39
|
to set up their own mobile phones.
|
|
0:28:42
|
However we're told to only allow Sawyer
|
|
0:28:47
|
to be able to have a maximum of one remote phone so he could
|
|
0:28:50
|
change the number that he has existing that we set up as administrator.
|
|
0:28:54
|
Maybe he changed his mobile phone, different plan,
|
|
0:28:57
|
different carrier, different sim, but he can't add multiple remote phones.
|
|
0:29:04
|
No such restriction for Hurley. OK. So let's get in to the configuration of it.
|
|
0:29:10
|
So we're gonna bring up CUCM and one of the first things we're gonna do
|
|
0:29:14
|
is we're going to take a look at our users
|
|
0:29:19
|
we're gonna be using use HReyes, Hugo Reyes, also known as Hurley
|
|
0:29:26
|
and James Ford, also known as Sawyer.
|
|
0:29:32
|
But let's go ahead and associate them with their primary desk phones.
|
|
0:29:39
|
And we know that HReyes, he was on, I believe so
|
|
0:29:46
|
is headquarter phone, phone number 2, so dn 1002.
|
|
0:29:55
|
Primary desk phone user device, we'll go ahead and associate him as
|
|
0:30:05
|
scroll down, we're going to enable mobility
|
|
0:30:10
|
now our primary end user device was ending in
|
|
0:30:14
|
foxtrot one delta echo, here we go
|
|
0:30:19
|
and we'll probably want to enable mobile voice access
|
|
0:30:23
|
but that's something separate, so we'll wait until we get to that task.
|
|
0:30:28
|
Here's the maximum wait time for desk phone pick-up
|
|
0:30:31
|
so here when we mentioned that we want to allow Hurley or
|
|
0:30:36
|
Sawyer to be able to transfer their calls from their mobile phones back
|
|
0:30:39
|
to their desk phones and we mentioned that this was simply hanging up
|
|
0:30:43
|
that remote mobile phone and it would be allowed
|
|
0:30:45
|
to ring at their desk phone, this is the maximum wait time for
|
|
0:30:50
|
to be held at their desk phone.
|
|
0:30:55
|
Most everything in this module is gonna be in milliseconds.
|
|
0:30:59
|
So if we put a comma there or
|
|
0:31:06
|
then we see that this is 10,000 milliseconds, so this is actually 10 seconds.
|
|
0:31:10
|
So if we want to be available for 30 seconds
|
|
0:31:12
|
I think I said 30 was the default, I was wrong, it's 10.
|
|
0:31:16
|
We change this to 30,000 milliseconds, but we'll leave it at 10,
|
|
0:31:19
|
that's gonna be fine for now.
|
|
0:31:22
|
And here is the remote destination limit
|
|
0:31:25
|
so how many remote destinations is each user allowed to have
|
|
0:31:32
|
associated to them? Now
|
|
0:31:35
|
we didn't say there was any restriction for Hugo so
|
|
0:31:40
|
we're just gonna leave it at four. For Sawyer, we were told
|
|
0:31:43
|
only to allow a maximum of one remote phone.
|
|
0:31:46
|
So that's where we will change this value to one or Sawyer.
|
|
0:31:51
|
And we also need to add Hurley to a group
|
|
0:31:55
|
that group contains end users
|
|
0:31:59
|
standard CCM end user and the reason for this, we'll click save
|
|
0:32:07
|
those with his primary device, let's give him a primary extension 1002,
|
|
0:32:12
|
although probably not necessary for this task,
|
|
0:32:18
|
got the remote wait time for hold, remote destination limit of
|
|
0:32:22
|
four which is fine and standard CCM end users
|
|
0:32:25
|
so that he's got CCM user administration so that he can log in
|
|
0:32:30
|
to his user page and change his remote destinations.
|
|
0:32:33
|
And we'll look at that later after we've set up some remote destination.
|
|
0:32:37
|
OK? So now let's go ahead and go back to our users and grab
|
|
0:32:42
|
JFord, James Ford, also known as Sawyer
|
|
0:32:46
|
and we'll do the same thing, device association.
|
|
0:32:49
|
He's at branch2 phone2, so 3002.
|
|
0:32:57
|
Save his primary device, go back to the user
|
|
0:33:02
|
his device ends in 1A93
|
|
0:33:06
|
give him a primary extension, enable mobility
|
|
0:33:13
|
E1A93, primary user device, change his remote destination
|
|
0:33:18
|
limit to one and then add him to the group
|
|
0:33:22
|
standard CCM end users, click save, I'll just go back and verify everything.
|
|
0:33:29
|
OK. 1A93
|
|
0:33:33
|
got our primary extension, enable mobility with 1A93 as the
|
|
0:33:37
|
primary user device, standard CCM and end users.
|
|
0:33:43
|
OK.
|
|
0:33:45
|
So if we've taken care of the user, we've taken care of
|
|
0:33:49
|
allowing them to log in and Sawyer being able to only have one.
|
|
0:33:55
|
Let's add a softkey, so we really had to do the user
|
|
0:33:59
|
before we can create some of the other things.
|
|
0:34:02
|
So let's go to device, device settings, and softkey template
|
|
0:34:10
|
and let's actually check out before, open a new window here or new tab
|
|
0:34:16
|
before we actually modify, I believe they all have the module
|
|
0:34:19
|
three enhanced user softkey template.
|
|
0:34:22
|
Let's just verify, let's just open each of these
|
|
0:34:25
|
I'm just holding down control or and on a Mac
|
|
0:34:31
|
phone configuration, yes module 3
|
|
0:34:35
|
on module 3 softkey, next one module 3, module 3 enhanced
|
|
0:34:41
|
module 3 enhanced user, yes so their all using module 3 enhanced user.
|
|
0:34:46
|
Jump in to this one, they all are already using
|
|
0:34:51
|
they will configure the softkey layout for the application cisco call manager.
|
|
0:35:02
|
OK?
|
|
0:35:05
|
OK, so let's grab the mobility softkey
|
|
0:35:08
|
and we'll bring that over, we want to keep it on the first page,
|
|
0:35:13
|
they will have to actually press services before they can press their softkey.
|
|
0:35:19
|
So technically, I suppose it's two buttons but it would be very likely
|
|
0:35:25
|
I accidentally went back without saving.
|
|
0:35:29
|
This could be something that the lab may refer to as one button.
|
|
0:35:33
|
Send to mobile phone, even if you do technically have to press services.
|
|
0:35:37
|
And then the mobility softkey, so when in doubt ask the
|
|
0:35:41
|
proctor for clarification, that's what thy're there for.
|
|
0:35:45
|
Here with one button, this is what we mean.
|
|
0:35:49
|
Save.
|
|
0:35:51
|
And we'll look at each one of these to see where is mobility an option
|
|
0:35:55
|
connected it obviousy is and we want to put it right after transfer
|
|
0:36:01
|
actually no, we're gonna want to bump it up even one more
|
|
0:36:04
|
because on most phones, except for the larger display phones
|
|
0:36:08
|
they only have four softkeys, so you're gonna 1, 2, 3 and then more
|
|
0:36:13
|
and then 1, 2, 3 and then more, 1, 2, 3, so if we actually had this
|
|
0:36:18
|
down here, it would show up on the first button of the second page.
|
|
0:36:24
|
OK? We'll click save.
|
|
0:36:26
|
And we'll just look through all of these
|
|
0:36:29
|
there shouldn't really be any others that have mobility
|
|
0:36:32
|
but we'll look through all the states just to make sure
|
|
0:36:36
|
we're not missing anything, it doesn't take us that long to go through them
|
|
0:36:42
|
after first connected conference
|
|
0:36:45
|
I'm just looking over here on the unselected softkeys for mobility ring out
|
|
0:36:50
|
off hook with feature, it's in your remote in use,
|
|
0:36:55
|
and connected no feature, I believe yes, on hook
|
|
0:37:00
|
and then also connected are then only two that now have
|
|
0:37:05
|
and by the way, on hook it's the fourth softkey,
|
|
0:37:08
|
but unless we have more than four then more doesn't show up.
|
|
0:37:12
|
It only shows up when we have more than that position.
|
|
0:37:15
|
OK? Now we're going to go ahead and reset all of the deives and
|
|
0:37:20
|
restart all of the devices that had that softkey associated with them
|
|
0:37:26
|
and we see our devices beginning to be reset.
|
|
0:37:38
|
OK. So we'll let those restart.
|
|
0:37:42
|
So now we've taken care of the last two bullets, kind of first, alright.
|
|
0:37:47
|
So now we need to go and set up our actual
|
|
0:37:50
|
remote destination profile.
|
|
0:37:54
|
Now we're going to go to device, device settings
|
|
0:37:59
|
remote destination profile and we shoudn't have any to begin with.
|
|
0:38:04
|
So we'll add a new one and we'll call this one
|
|
0:38:10
|
RDP for Remote Destination Profile _hurley
|
|
0:38:20
|
Let's just call it Hurley's RDs
|
|
0:38:27
|
No, let's just call it remote destination Hurley
|
|
0:38:33
|
corporate headquarter phone2.
|
|
0:38:42
|
Looks good. OK, description, this is an RDP for Hurley's remote phone.
|
|
0:38:52
|
User ID is Hreyes, device pool
|
|
0:38:58
|
we're gonna have this the same as the device pool for our desk
|
|
0:39:02
|
phone now again we don't have to
|
|
0:39:04
|
but we're gonna choose to, this is where our MRGL will be chosen
|
|
0:39:07
|
the media resource group list, to look for media resources such as
|
|
0:39:11
|
conference bridge when we go to do that later or a music on hold server
|
|
0:39:16
|
and really we don't have to specify these user and network
|
|
0:39:19
|
called sources if they've been specified at the device pool level.
|
|
0:39:42
|
Or if probably just a good idea to go ahead and do it.
|
|
0:39:45
|
They are by default in the system service parameters
|
|
0:39:49
|
set to the index of one, but if there were multiple
|
|
0:39:51
|
then we would have to do it so just a
|
|
0:39:54
|
good idea to go ahead and do it, we can also set it the line
|
|
0:39:57
|
and because I opened that in a new windown, this isn't gonna save properly.
|
|
0:40:00
|
We also have privacy which we're just gonna leave
|
|
0:40:05
|
to off or we can just you know
|
|
0:40:09
|
leave it to off or default or whatever,
|
|
0:40:11
|
for the time being, we'll take a look at that a little bit mre
|
|
0:40:15
|
a little bit later.
|
|
0:40:17
|
Calling party transformation, we're gonna take a look
|
|
0:40:19
|
at that in a future task for localization.
|
|
0:40:23
|
Uncheck use device pool for right now.
|
|
0:40:26
|
And then we've got two calling search spaces here
|
|
0:40:29
|
our calling search space and our rerouting calling search space.
|
|
0:40:34
|
Now our calling search space is typically used
|
|
0:40:40
|
I shouldn't say typically, whenever we see calling search space on a
|
|
0:40:43
|
device, whether it's a gateway or a phone.
|
|
0:40:47
|
If you remember back to module 9, calling search spaces are only invoked
|
|
0:40:52
|
when a call is ingress in that device.
|
|
0:40:56
|
OK? So if it's on a phone, then it's only when the call is coming in
|
|
0:41:01
|
from the phone and then out to either another phone or
|
|
0:41:05
|
our to a PSTN number, but it;s when the call is coming in
|
|
0:41:09
|
into call manager from the phone that we look at the calling search space.
|
|
0:41:16
|
When a call is being presented out or egress to a phone,
|
|
0:41:21
|
we don't look at it's calling search space, we look at the partition
|
|
0:41:24
|
that the dn is a part of.
|
|
0:41:29
|
We match that we the calling search space of the
|
|
0:41:31
|
calling party's device, maybe inbound from a gateway
|
|
0:41:35
|
or ingress to another IP phone.
|
|
0:41:39
|
Calling search space here with remote destination profile is no different
|
|
0:41:43
|
so this is not used when we are trying to
|
|
0:41:48
|
reroute a call that's also ringing at our desk phone
|
|
0:41:52
|
reroute it out to a PSTN remote destination
|
|
0:41:55
|
that is what the rerouting calling search space is used for.
|
|
0:42:01
|
The calling search space is used when we are placing a call
|
|
0:42:05
|
in through a remote destination profile.
|
|
0:42:09
|
When is that? That's when we're calling in through mobile voice access
|
|
0:42:14
|
or but we're not gonna use today enterprise feature access for smart phone.
|
|
0:42:20
|
When we're calling in through mobile voice access and doing
|
|
0:42:22
|
two stage dialing, calling back to another location,
|
|
0:42:26
|
that's when this calling search space can be looked at.
|
|
0:42:31
|
So we'll take a look at that later, we're not gonna
|
|
0:42:33
|
configure anything for calling search space.
|
|
0:42:36
|
We're gonna be very specific on what we do and do not configure
|
|
0:42:39
|
and only do what we nned to, at the time that we need to
|
|
0:42:43
|
such as not enabling mobile voice access checkbox
|
|
0:42:46
|
on any of the users so that we can distinguish
|
|
0:42:50
|
and truly be experts and know what exactly
|
|
0:42:55
|
functions for what phase of our
|
|
0:43:01
|
needed configuration or needed results.
|
|
0:43:04
|
We will however configure the rerouting search space otherwise
|
|
0:43:09
|
we'll use the null or non calling search space
|
|
0:43:11
|
which will only have the none partition to try to find dns
|
|
0:43:15
|
or try to find patterns to match with our remote
|
|
0:43:18
|
destinations and of course we won't find any.
|
|
0:43:21
|
So let's go take a look at our translation patterns or PSTN patterns
|
|
0:43:30
|
now we note that if we look at the ones that begin with 0,
|
|
0:43:35
|
from calling from the Netherlands
|
|
0:43:37
|
or the ones that begin with 9 from calling anywhere in the US,
|
|
0:43:43
|
those are all fine and good, we could look at the partitions there
|
|
0:43:46
|
and try to find a calling search space that has those partitions already
|
|
0:43:50
|
but remember that our remote destinations we're going to
|
|
0:43:53
|
want to configure as we learned in module 11,
|
|
0:43:58
|
and 10 for globalization and localization, we're going to want
|
|
0:44:01
|
to configure those with full plus, full E164 numbers.
|
|
0:44:07
|
So we're gonna look at translation patterns that begin with \+
|
|
0:44:11
|
and we see that
|
|
0:44:16
|
the ones that we're going to want to dial
|
|
0:44:20
|
primarily either plus patterns plus 120615121312
|
|
0:44:28
|
those all belong in the partition for dial device either US
|
|
0:44:35
|
or dial device Netherlands, now there's internal directory,
|
|
0:44:39
|
we had used those to look at globalizing
|
|
0:44:45
|
numbers for directory numbers and then there's also restricted ones.
|
|
0:44:50
|
But again, we're gonna want to dial things from a device level
|
|
0:44:55
|
to the ones that actually ring.
|
|
0:44:59
|
OK. The ones that actually route I should say, so if I looked at the same
|
|
0:45:02
|
plus pattern one is in dial device Netherlands,
|
|
0:45:06
|
route this pattern, the other is in block line Netherlands, block this pattern.
|
|
0:45:12
|
So I'm gonna want the dial, but I'm not gonna want Netherlands
|
|
0:45:14
|
I'm gonna want the one for the US, because this remote destination
|
|
0:45:18
|
profile is for Hurley which is at corporate headquarter phone2,
|
|
0:45:23
|
he's in the US, so we want the calling search space for
|
|
0:45:29
|
dial device US and let's just go check to make sure that
|
|
0:45:32
|
calling search space open a new tab has the proper
|
|
0:45:37
|
it's just CSS contains US.
|
|
0:45:42
|
Dial device US has the partition for dial device US
|
|
0:45:47
|
which is what the translation pattern is.
|
|
0:45:49
|
So we're good there and we've got the proper CSS.
|
|
0:45:52
|
Now remember the remote destination profile is the virtual device.
|
|
0:45:57
|
Not the line, the virtual device.
|
|
0:46:00
|
So when we look back to module 9, line device approach
|
|
0:46:04
|
this is the device level CSS that allows everything
|
|
0:46:11
|
and no one had any restrictions yet but
|
|
0:46:17
|
when we look at restrictions in a little bit,
|
|
0:46:19
|
and Sawyer's gonna have a restriction we'll just make sure that his line,
|
|
0:46:25
|
has the restriction on it, but his device will still allow
|
|
0:46:29
|
calls it'll just allow them to the Netherlands because he's at branch2.
|
|
0:46:33
|
But for Hurley, at headquarers we'll allow device US.
|
|
0:46:37
|
We'll go ahead and click save and it won't work
|
|
0:46:38
|
properly, but we'll click save again.
|
|
0:46:41
|
It should add successful and now we see that we've got a new
|
|
0:46:46
|
field associate remote destination and add a dn.
|
|
0:46:49
|
We've also got this do not disturb option,
|
|
0:46:52
|
OK so we can actually turn on do no disturb for
|
|
0:46:57
|
an entire remote destination profile.
|
|
0:47:00
|
Now this is not the same as turning off or disabling one
|
|
0:47:07
|
or all of your
|
|
0:47:11
|
remote destinations, this is disabling essentially
|
|
0:47:16
|
the entire remote destination profile or virtual device
|
|
0:47:19
|
and if you give it a DND option of call reject, if you remember back
|
|
0:47:23
|
to I think it was module 5 for call features,
|
|
0:47:27
|
call reject as opposed to the standard device,
|
|
0:47:33
|
option of what was it, we'll get a standard phone
|
|
0:47:38
|
grab corporate headquarter phone2,
|
|
0:47:43
|
take a look at the do no disturb the
|
|
0:47:49
|
traditional option is ringer off, that's the default.
|
|
0:47:54
|
When we have a change to call reject and we have
|
|
0:47:57
|
do not disturb enabled, then the call goes to voicemail.
|
|
0:48:01
|
Well if we're rejecting the call from one of the shared lines,
|
|
0:48:05
|
or one of the shared line devices then the call should just go right
|
|
0:48:09
|
to voicemail, I'm actually gonna go back out to the list
|
|
0:48:11
|
and jump back into this, otherwise we'll have a problem with saving this.
|
|
0:48:15
|
OK? So now we'll add our new dn and our dn is 1002,
|
|
0:48:24
|
refresh we'll choose our partition, we want the same partition
|
|
0:48:28
|
as our primary phone dn is in, this way this will show up
|
|
0:48:33
|
a device association and a shared line.
|
|
0:48:36
|
So here we see that this is already associated with one of these devices.
|
|
0:48:42
|
So let's go ahead and click save
|
|
0:48:48
|
as soon as we click save, now we'll see that it's associated with
|
|
0:48:50
|
two devices, Hurley's RDP, Remote Destination Profile virtual device,
|
|
0:48:57
|
and also the primary deskphone device.
|
|
0:49:01
|
Now if we scroll down, we see that our line 1
|
|
0:49:06
|
so that dn of 1002 as it pertains to the device RDP,
|
|
0:49:11
|
is known as line 1 as on this RDP and it doesn't currently have any caller ID
|
|
0:49:15
|
or external phone number mask, now we could go fill this in
|
|
0:49:19
|
or we see this update shared device settings
|
|
0:49:22
|
we don't want to click this and click propagate
|
|
0:49:24
|
because we'll propagate what we have which is nothing over to the
|
|
0:49:29
|
desk phone which does have something, instead we'll scroll back up
|
|
0:49:33
|
click on the deskphone, click on edit line appearance
|
|
0:49:36
|
for that particular device, scroll down and now we do have all of these.
|
|
0:49:43
|
Now the line text label doesn't matter because
|
|
0:49:46
|
it doesn't show up on the other because there is no
|
|
0:49:48
|
line text because it's a virtual device.
|
|
0:49:50
|
But we will at least and we could just
|
|
0:49:52
|
go ahead and do all of them. No problem.
|
|
0:49:55
|
We'll click all of these checkboxes and say propagate selected.
|
|
0:50:04
|
They failed for some devices, see the log for list of fail devices
|
|
0:50:11
|
Right? Let's figure out why.
|
|
0:50:14
|
Let's go back into the line, because we had been modifying it for the
|
|
0:50:18
|
desk phone, we're currently on that device.
|
|
0:50:21
|
Let's scroll down, let's actually go back and click RDP, edit line appearance.
|
|
0:50:28
|
Scroll down and it didn't take effect. Alright let's go ahead and go
|
|
0:50:31
|
back out to configured device RDP
|
|
0:50:35
|
not sure why it didn't, let's try it again.
|
|
0:50:39
|
Click on the desk phone, edit line appearance
|
|
0:50:46
|
correct the three that we know exist
|
|
0:50:50
|
propagate the selected,
|
|
0:50:54
|
there we go, now we didn't have an issue. We're still on the
|
|
0:50:58
|
foxtrot one delta echo hardware deskphone, we'll go over
|
|
0:51:01
|
to RDP edit line appearance.
|
|
0:51:05
|
OK. Now evertyhing propagated properly, so I'm not sure why the error
|
|
0:51:09
|
the first time, but it worked when we did it the second time.
|
|
0:51:12
|
OK? So we've got all that set up, we've got our AAR destination mask
|
|
0:51:16
|
everything else is or call pick up group, everything else is proper.
|
|
0:51:21
|
OK? So now we're gonna go back out to our RDP device,
|
|
0:51:26
|
and we've now got enough for our virtual
|
|
0:51:29
|
device that we can go ahead and add a
|
|
0:51:32
|
our rerouting calling search space didn't stick.
|
|
0:51:36
|
Add again and click save.
|
|
0:51:40
|
Sorry that was calling party transformation.
|
|
0:51:44
|
There we go, certainly don't want that to get mixed up. OK.
|
|
0:51:50
|
So we'll come back to these when we do mobile voice access
|
|
0:51:52
|
and come back to this when we do localization.
|
|
0:51:54
|
For now, we're done with our virtual device
|
|
0:51:57
|
and we need to add a remote destination.
|
|
0:52:01
|
The name of this remote destination is going to be Hurley's mobile.
|
|
0:52:08
|
Destination number as we saw is going to be
|
|
0:52:16
|
+12065015555, here we've got our answer to soon timer
|
|
0:52:24
|
so 1500 milliseconds or 1.5 seconds. If someone answers the
|
|
0:52:29
|
call within 1.5 seconds, probably a machine
|
|
0:52:33
|
probably went to voicemail, mobile's probably off, don't let it extend the call.
|
|
0:52:40
|
Because we want single unified enterprise voicemail box
|
|
0:52:45
|
to answer to late, so this is kind of like a
|
|
0:52:51
|
don't let it forward no answer
|
|
0:52:54
|
too long, same thing as we would do with, when we're setting up UCCX agents
|
|
0:52:59
|
how we would not want the UCCX
|
|
0:53:05
|
RMCM System, or ICD system rather to extend a call
|
|
0:53:11
|
out to an agent long enough to get to their voicemail box
|
|
0:53:14
|
we would want to put the calling party back in queue,
|
|
0:53:18
|
much to their dismay, this is the same concept.
|
|
0:53:22
|
So we saw that for Hurley's mobile, it rang after four rings
|
|
0:53:27
|
or 16 seconds to voicemail, so we want to change this default
|
|
0:53:31
|
19 seconds down to 14, now let's just discuss
|
|
0:53:37
|
why it is actually 19 seconds or 19,000 milliseconds, why default.
|
|
0:53:44
|
If we think that four seconds is roughly one ring then
|
|
0:53:51
|
four times five would be 20,000, right? So 20,000 seconds
|
|
0:53:56
|
would be five rings, most mobile phones, either go to voicemail within
|
|
0:54:03
|
three or four rings, so either 12,000 or 16,000.
|
|
0:54:08
|
So why 20 or rather why one second below five rings?
|
|
0:54:14
|
This is because when we're dealing with a proper
|
|
0:54:17
|
mobule cellular network, GSM or CDMA,
|
|
0:54:23
|
we have to actually allow the cellular network
|
|
0:54:27
|
to establish the call and that typically takes about a full ring
|
|
0:54:32
|
to just get the call established to the point where
|
|
0:54:35
|
the cell company has triangulated the mobile phone
|
|
0:54:39
|
and it's now begun to ring the phone, so it's already been ringing
|
|
0:54:42
|
at the deskphone typically for about a full second before
|
|
0:54:48
|
it rings in to the mobile phone.
|
|
0:54:51
|
Also on top of that, we've got this delay before ringing timer
|
|
0:54:56
|
now this is set to 4000 seconds or one ring
|
|
0:55:01
|
this is actually meeting the requirement where we said
|
|
0:55:07
|
here that their corresponding mobile phones are rung
|
|
0:55:11
|
but only after their desk phone rings fully once.
|
|
0:55:14
|
But this is already the default, ringing fully once
|
|
0:55:18
|
and then we're going to try to ring this remote destination.
|
|
0:55:23
|
OK? Now we could change this to 0 and it would ring immediately.
|
|
0:55:29
|
And for testing, maybe you'd want to do that
|
|
0:55:31
|
as long as you remember to come back and change it back.
|
|
0:55:35
|
Maybe they would have you do something else, the default is that
|
|
0:55:38
|
actually we're asking you to have it do by default.
|
|
0:55:44
|
But in our lab, we don't actually have a real
|
|
0:55:48
|
GSM network and you wouldn't in the real lab as well so
|
|
0:55:52
|
because it's all local, we have ISTN really back to back,
|
|
0:55:58
|
there is no cellular network trying to establish a call
|
|
0:56:02
|
through GSM, then it's gonna ring immediately
|
|
0:56:06
|
whenever we tell it to, now it's gonna wait a full ring
|
|
0:56:09
|
at the desk phone, but once it does that, when it actually
|
|
0:56:12
|
begins extending the call to this remote destination
|
|
0:56:15
|
it's going to begin ringing immediately.
|
|
0:56:18
|
Because of that, we're not gonna want the answer to late timer
|
|
0:56:21
|
to include the time it takes the cell company or mobile company
|
|
0:56:26
|
or carrier to set up the call to that mobile phone.
|
|
0:56:30
|
So we're gonna reduce this as we had said four rings
|
|
0:56:34
|
when it goes to voicemail, 16 seconds, we're gonna reduce
|
|
0:56:37
|
to 1 second below that or 15 seconds, 15,000 milliseconds.
|
|
0:56:43
|
OK? So that's the rational behind that.
|
|
0:56:46
|
The RDP that we're tied to, this is our mobile phone
|
|
0:56:50
|
so we're gonna click mobile phone and we want to enable mobile connect.
|
|
0:56:54
|
And we'll get to the rest of this later, go ahead and press save,
|
|
0:56:58
|
And it says enable mobile connect checkbox
|
|
0:57:02
|
is selected please check that the phone associated with this user
|
|
0:57:07
|
has the mobile softkey configured which of course
|
|
0:57:10
|
we already did, we jsut have tosay OK to this
|
|
0:57:12
|
every time we press save on our remote destination.
|
|
0:57:15
|
So now we see all of this information is the same
|
|
0:57:18
|
but we also have the dn that we're associated with
|
|
0:57:21
|
we have to click line association save.
|
|
0:57:25
|
And now we're done with this remote destination.
|
|
0:57:29
|
Now we'll go to copy and we'll change this so that we still have our
|
|
0:57:34
|
line association, we'll change this Hurley's own phone.
|
|
0:57:40
|
Destination here
|
|
0:57:45
|
is +12065015151.
|
|
0:57:56
|
Three rings at the home phone.
|
|
0:57:59
|
So we're gonna want this, not 12 seconds, but 11 seconds.
|
|
0:58:06
|
One second under when it should ring to voicemail.
|
|
0:58:10
|
Now if I leave mobile phone checked
|
|
0:58:13
|
and enable mobile connect, watch what happens, gonna click save.
|
|
0:58:19
|
OK. So let's go back out to find list of remote
|
|
0:58:22
|
destinations so we can see this mobile phone, we'll click find.
|
|
0:58:27
|
We've got Hurley's home and Hurley's mobile, let's jump into Hurley's
|
|
0:58:30
|
home the one we just configured, mobile phone is checked.
|
|
0:58:34
|
OK? Let's go back to find and click Hurley's mobile
|
|
0:58:39
|
mobile phone is also checked. This is interesting.
|
|
0:58:44
|
We shouldn't actually allow this to stay checked
|
|
0:58:47
|
so let's go back to Hurley's home
|
|
0:58:51
|
phone. OK. Go back to Hurley's mobile.
|
|
0:58:57
|
Save, this should unchecked Hurley's home.
|
|
0:59:04
|
OK. They've updated it so you can have multiple mobile phones.
|
|
0:59:08
|
Again we don't want this checked unless it's actually the person's
|
|
0:59:13
|
mobile because whenever I click the softkey send to mobile,
|
|
0:59:17
|
it will send it to or it will actually go and attempt to ring
|
|
0:59:22
|
I guess now all of the phones that are marked as mobiles.
|
|
0:59:30
|
OK? So Hurley's home is not a mobile phone
|
|
0:59:35
|
and when we did this, it unassociated the line
|
|
0:59:38
|
reassociate the line, that's a lot of saving, going back and forth.
|
|
0:59:44
|
Let's make sure number is still proper 5151 11 seconds no mobile phone
|
|
0:59:49
|
line association, update successful, good. Go back to Hurley's mobile
|
|
0:59:55
|
mobile phone, line association, RDP, 15 seconds versus 16
|
|
1:00:03
|
5555, we're good. OK. So now everything is proper.
|
|
1:00:09
|
So at this point
|
|
1:00:13
|
we need to set up Sawyer's RDP and remote destination but
|
|
1:00:18
|
we should be able to test Hurley's immediately. We'll go ahead and set up
|
|
1:00:23
|
Sawyer's and we'll do all of our testing.
|
|
1:00:25
|
So right now, we're here at device remote destination.
|
|
1:00:28
|
Now we originally went to device settings, remote destination profile
|
|
1:00:34
|
and it was when we set up this that
|
|
1:00:39
|
we were able to click in, add a remote destination from there,
|
|
1:00:43
|
so that's how we jumped over.
|
|
1:00:47
|
We want to do an RDP or
|
|
1:00:53
|
format right? So it's actually branch2
|
|
1:01:00
|
Sawyer branch2 phone2, description, this is Sawyer's
|
|
1:01:09
|
phone let's say, the user ID is JFord,
|
|
1:01:16
|
device pool is branch2.
|
|
1:01:20
|
We want that checked for MRGLs for conferencing and whatever else.
|
|
1:01:26
|
Calling searh space, we'll do later at mobile voice access.
|
|
1:01:29
|
Choose the sample audio source for user and network,
|
|
1:01:33
|
privacy will leave off rerouting calling search space
|
|
1:01:36
|
we want to be dial Netherland PSTN.
|
|
1:01:40
|
And no calling party transformation CSS right now.
|
|
1:01:47
|
Add a new dn 3002
|
|
1:01:54
|
Proper internal dn partitions, so it shows up as a shared device.
|
|
1:02:00
|
We see the 1A93 desk phone, we'll go ahead and click save.
|
|
1:02:07
|
Now we see that it's a shared line.
|
|
1:02:09
|
We'll edit the line appearance on the desk phone, scroll to the bottom
|
|
1:02:18
|
paired device setthings that we wish to propagate,
|
|
1:02:25
|
go back to the line appearance on our RDP,
|
|
1:02:29
|
now that we're on our RDP device line,
|
|
1:02:33
|
we should have the display for caller ID and the external phone number mask.
|
|
1:02:39
|
These are gonna be important because when we make
|
|
1:02:42
|
calls into mobile voice access later
|
|
1:02:45
|
and we wish for them to be seen coming from
|
|
1:02:49
|
the proper person, if we don't have this external phone number mask
|
|
1:02:54
|
and the translation pattern that we dial through says to use it,
|
|
1:02:57
|
well then there's nothing there and we'll simply
|
|
1:03:00
|
have a calling number that comes from 3002.
|
|
1:03:03
|
And that will very likely not be reachable by anyone on the PSTN.
|
|
1:03:09
|
Or most certainly not reachable so, and depending on what
|
|
1:03:13
|
gateway we pull out, it could be different for every single one.
|
|
1:03:17
|
So we want that external phone number mask set properly.
|
|
1:03:21
|
OK? And also our CNAM or calling ID display.
|
|
1:03:26
|
So now we've got our partition, our shared line
|
|
1:03:30
|
in the proper partition, shared device, proper calling
|
|
1:03:36
|
party ID and name and now we need to add a new remote destination.
|
|
1:03:43
|
So we'll say that this one is Hurley's
|
|
1:03:46
|
not Hurley's, Sawyer's mobile.
|
|
1:03:52
|
The destination number we'll copy
|
|
1:03:54
|
and we're gonna want to use globalized format,
|
|
1:03:58
|
it is greatly going to simplify your life in many ways,
|
|
1:04:03
|
and Sawyer's phone rang after three rings to voicemail
|
|
1:04:07
|
so we'll take this not to 12, which is three rings, but to 11 seconds,
|
|
1:04:14
|
ring at his desk a full ring before going to his remote destination,
|
|
1:04:18
|
mobile phone this is and enable mobile connect.
|
|
1:04:24
|
Click line association and save.
|
|
1:04:29
|
We've completed setting up the basics of mobile connect for
|
|
1:04:35
|
both Hurley and Sawyer, so they've got their remote destinations,
|
|
1:04:41
|
and the remote destination profiles.
|
|
1:04:43
|
Now these are the ones that are associated with the users
|
|
1:04:48
|
still actually need to go to the device
|
|
1:04:57
|
and associate their ownder user ID
|
|
1:05:02
|
so this is for corporate headquarter phone2, so HReyes
|
|
1:05:10
|
else on here that we're missing.
|
|
1:05:14
|
Device mobility mode, that's for the next module.
|
|
1:05:24
|
Everything else looks good, let's save this, phone
|
|
1:05:31
|
Start it.
|
|
1:05:41
|
Go back to branch2 phone2
|
|
1:05:47
|
ID of JFord
|
|
1:05:53
|
save it.
|
|
1:05:59
|
Restart.
|
|
1:06:05
|
Go back to our end users,
|
|
1:06:15
|
James
|
|
1:06:18
|
that he, we need to go back and do device association
|
|
1:06:22
|
we don't do that to RDPs,
|
|
1:06:26
|
default
|
|
1:06:28
|
there we go, we see that his remote destination profile is linked now.
|
|
1:06:34
|
And then let's also go check
|
|
1:06:38
|
Hugo Hurley Reyes
|
|
1:06:42
|
check that his remote destination profile is automatically linked.
|
|
1:06:47
|
OK? We did that when we went to the remote destination profile
|
|
1:06:52
|
and associated to the user.
|
|
1:06:55
|
So now, before we test anything
|
|
1:07:00
|
let's go and see if we can actually log in
|
|
1:07:04
|
log out and we'll log back in to CCM user
|
|
1:07:14
|
unified CM user options, we'll log in as HReyes
|
|
1:07:20
|
password is cisco of course.
|
|
1:07:26
|
We're gonna log in and look at mobility settings remote destinations
|
|
1:07:32
|
and see that Hurley has two, his home and his mobile
|
|
1:07:36
|
jump into it, we could change it if we want.
|
|
1:07:39
|
Alright, let's just change it to six, we'll change it right back.
|
|
1:07:43
|
And show that we do have the rights, update was successful,
|
|
1:07:46
|
to be able to change it.
|
|
1:07:48
|
OK? And can add a new one if we want.
|
|
1:07:53
|
Name test 555
|
|
1:07:57
|
and click save, find a, save.
|
|
1:08:04
|
So now we have three, we're gonna go ahead and delete this one.
|
|
1:08:06
|
But we just want to show that we have the ability to be able to do it.
|
|
1:08:11
|
We'll click log out and that would show up in the admin
|
|
1:08:15
|
page as well of course. Now we're gonna log in as JFord,
|
|
1:08:21
|
Sawyer's log in,
|
|
1:08:24
|
now we're gonna go to mobility settings remote destinations,
|
|
1:08:29
|
that we have our one, we're gonna click add new, we'll do test
|
|
1:08:35
|
24 enable, save
|
|
1:08:41
|
RDP is required, had that on the last one, add failed
|
|
1:08:46
|
remote destination, we didn't because we copied it,
|
|
1:08:48
|
remote destination cannot be added because the remote destination limits
|
|
1:08:51
|
set by the administrator for this end user account has already been reached.
|
|
1:08:55
|
So that meets the requirements where Sawyer cannot add anymore
|
|
1:09:01
|
we could however change it, so let's change this last one to 9
|
|
1:09:06
|
click save, go ahead and log out,
|
|
1:09:10
|
we'll go back to our CCM admin log in,
|
|
1:09:14
|
log in, lok at our remote destinations
|
|
1:09:19
|
just to verify that Sawyer did have the ability to
|
|
1:09:22
|
change his number and sure enough the last digit is a 9.
|
|
1:09:27
|
Jump in and change it back to a 5, like it should have been
|
|
1:09:31
|
and click save, so we can modify his one
|
|
1:09:35
|
but he cannot add an additional one.
|
|
1:09:38
|
OK. I think it's time to change, time to test.
|
|
1:09:46
|
Alright so let's go ahead and minimize this
|
|
1:09:51
|
done a few resets.
|
|
1:10:05
|
Our
|
|
1:10:10
|
phone here, let's just go ahead and do all of them just to be sure.
|
|
1:10:26
|
We already got all their extensions in and they're already logged in,
|
|
1:10:29
|
thru AXL so I have to do a search again and then
|
|
1:10:31
|
control again once it comes back up.
|
|
1:10:37
|
OK.
|
|
1:10:40
|
Most of our phones are back,
|
|
1:10:43
|
one didn't configure properly, here we go.
|
|
1:10:50
|
The last one connects,
|
|
1:10:54
|
alright so now it's time to test.
|
|
1:10:59
|
So these are the phones that we're wishing to have, be called
|
|
1:11:08
|
that's Ford and Reyes.
|
|
1:11:19
|
PSTN phone and let's begin by calling from
|
|
1:11:24
|
Desmond's phone 3001, so we'll go off hook
|
|
1:11:30
|
and we're gonna dial 1002
|
|
1:11:35
|
here already ringing and see it ringing here at 1002,
|
|
1:11:39
|
and after one full ring, now the call comes in
|
|
1:11:43
|
on both Hurley's mobile and
|
|
1:11:47
|
his home phone, we can see both ringing.
|
|
1:11:52
|
Now let's see if it goes to voicemail.
|
|
1:11:56
|
OK. So it stopped ringing on the PSTN phone,
|
|
1:11:59
|
before it went to voicemail. This is good. Let's go ahead and hang up.
|
|
1:12:04
|
Let's just see what would have happened if at Hurley's home
|
|
1:12:11
|
we would have changed the answer to late timer
|
|
1:12:14
|
to let's say 15 seconds.
|
|
1:12:21
|
Alright? Let's try this call again.
|
|
1:12:31
|
Hopefully it catches up. OK, so it's ringing at his phone and mobile,
|
|
1:12:51
|
so the calls is no longer here
|
|
1:12:54
|
at his deskphone, it's no longer at his PSTN phone,
|
|
1:12:59
|
and this message will repeat
|
|
1:13:01
|
so, you have reached either Sawyer or Hurley's voicemail.
|
|
1:13:07
|
Original calling party did get connected
|
|
1:13:10
|
but they got connected to the mobile or
|
|
1:13:13
|
I think we changed the home phone
|
|
1:13:15
|
to their voicemail. Yes we changed his home phone,
|
|
1:13:18
|
so let's change it back to 11 seconds.
|
|
1:13:22
|
So again, these deep dives we want to
|
|
1:13:25
|
show the, you know contrast what's not working
|
|
1:13:29
|
from what is working. So we did it properly the first time and it worked.
|
|
1:13:33
|
And now we've just changed it back and we'll go ahead and try to dial again.
|
|
1:13:40
|
2
|
|
1:13:42
|
once at the desk and begins ringing at the PSTN,
|
|
1:13:51
|
Don't want it to go to voicemail, so it should stop ringing at both
|
|
1:13:54
|
PSTN phones here shortly, one stopped ringing
|
|
1:14:00
|
home and one his mobile had one additional ring,
|
|
1:14:04
|
now neither are ringing, but it is still ringing at his deskphone.
|
|
1:14:08
|
So if his deskphone had voicemail set up
|
|
1:14:11
|
then it would go to his deskphone voicemail.
|
|
1:14:14
|
A single enterprise voice mailbox and by the way this is the reason
|
|
1:14:18
|
that we did not set up voicemail, differentiate between hearing the mobile
|
|
1:14:24
|
and home voicemail out on the PSTN and not hearing our
|
|
1:14:31
|
get confusing in terms of the recorded prompt.
|
|
1:14:35
|
OK. So everything's set up properly.
|
|
1:14:40
|
Let's see where the call went out.
|
|
1:14:45
|
Now it looks like the call went out
|
|
1:14:50
|
looks like the call went out
|
|
1:14:56
|
to the headquarter gateway at one point
|
|
1:15:00
|
and also it went out internationally to the
|
|
1:15:05
|
for the Netherlands gateway that's 112 when we're testing a while ago.
|
|
1:15:09
|
Actually some of these could have been when we were just testing the
|
|
1:15:15
|
primary dialing, so let's actually go ahead and clear off our
|
|
1:15:17
|
scroll back buffer or all of our routers
|
|
1:15:21
|
and let's try this mobile connect again just to see what happens
|
|
1:15:25
|
when we call from Desmond's
|
|
1:15:31
|
1001, calls out to the PSTN and it goes out
|
|
1:15:36
|
router 3, it's making an international call, it's actually making two of them
|
|
1:15:42
|
so what we're to understand from this
|
|
1:15:46
|
is that when Desmond whose in the Netherlands goes to make
|
|
1:15:52
|
a standard call to another internal dn 1002
|
|
1:15:57
|
that single number reach or mobile connect is actually
|
|
1:16:01
|
placing two calls out to Hurley's mobile
|
|
1:16:05
|
and to his home phone just like we wanted him to
|
|
1:16:08
|
but that's actually going out Desmond's local Netherland
|
|
1:16:12
|
gateway and it's placing two international calls.
|
|
1:16:15
|
00 and then the country code 1
|
|
1:16:17
|
and then the rest of the digits, that's gonna be really expensive
|
|
1:16:21
|
every time Desmond goes to ring Hurley's phone.
|
|
1:16:27
|
OK? So that might not be the functionality that we desire
|
|
1:16:31
|
although we really haven't been told to do anything about it
|
|
1:16:33
|
we'e just kind of pointing out the way it's happening right now.
|
|
1:16:37
|
Just so that we know what's going on.
|
|
1:16:40
|
Also take a look at the calling party number.
|
|
1:16:43
|
It's 3001, let's do the call again real quick
|
|
1:16:45
|
just to see the PSTN phone.
|
|
1:16:51
|
So the PSTN phone sees 3001,
|
|
1:16:55
|
now 3001 to Hurley's mobile
|
|
1:17:01
|
maybe makes sense but what if
|
|
1:17:06
|
I don't know, but first of all not every
|
|
1:17:09
|
carrier would allow you to send out calling ID
|
|
1:17:15
|
COID, ANI, however you want to look at it, your calling number
|
|
1:17:18
|
to be anything other than DID range that you
|
|
1:17:20
|
actually own at that particular site.
|
|
1:17:24
|
And 3001 is not a valid DID number
|
|
1:17:29
|
0020703 3001 is a valid DID number at that gateway
|
|
1:17:34
|
but not just 3001,
|
|
1:17:37
|
3002 or whatever.
|
|
1:17:41
|
So because of that, we may need to change it
|
|
1:17:44
|
but also just so that the receiving party
|
|
1:17:47
|
do it properly, now maybe they do wanna see 3001.
|
|
1:17:50
|
It just depends on what your users requirements are
|
|
1:17:52
|
or in the lab, what the lab requirements are.
|
|
1:17:56
|
But for right now, we haven't been told to do anything about it,
|
|
1:17:59
|
again I'm just pointing it out.
|
|
1:18:01
|
Clear off this gateway
|
|
1:18:05
|
so that we can differentiate it from other
|
|
1:18:10
|
tasks so let's try the same thing to
|
|
1:18:16
|
the dn of 3002. OK, so let's call
|
|
1:18:26
|
call 3002
|
|
1:18:29
|
So we heard it ring once before the display catch up
|
|
1:18:32
|
and now the PSTN is calling and ringing
|
|
1:18:36
|
on his home line or mobile line
|
|
1:18:39
|
Sawyer's mobile and let's make sure it doesn't go to voicemail.
|
|
1:18:44
|
Stops ringing and it's still ringing at his desk phone
|
|
1:18:47
|
but it did not go to his mobile voicemail.
|
|
1:18:51
|
OK? So single number reach is working for both of our entities.
|
|
1:18:58
|
Which gateway did this go out of?
|
|
1:19:02
|
This went out of the Netherlands gateway. Now who is the calling party here?
|
|
1:19:08
|
Calling party was 3001 whose at branch2 Netherlands site.
|
|
1:19:13
|
Looks like it's going out his local gateway, let's clear it off.
|
|
1:19:17
|
All of our gateways are cleared and let's try that same call
|
|
1:19:21
|
from let's say Jack Shepherd, let's have him call 3002
|
|
1:19:31
|
It rings once to James' phone, now it's ringing the PSTN
|
|
1:19:39
|
which gateway is it going out?
|
|
1:19:42
|
Going out the corporate headquarter gateway 1001
|
|
1:19:45
|
for international 1316 for mobile phones in the Netherlands,
|
|
1:19:51
|
70357575.
|
|
1:19:55
|
Alright, so it went out the local gateway.
|
|
1:19:58
|
Alright, let's clear it off.
|
|
1:20:03
|
Go back buffer and try
|
|
1:20:07
|
Jack calling 1002, Hugo.
|
|
1:20:15
|
OK. So now we've got both lines of the PSTN phone ringing.
|
|
1:20:21
|
Calling party shows from Jack Shepherd 1001, so CNAM's working but
|
|
1:20:28
|
CLID is still showing 1001 and it's still going out
|
|
1:20:32
|
corporate headquarter gateway as a local call.
|
|
1:20:36
|
First of all, why is it working? Why is it dialing properly?
|
|
1:20:39
|
If our remote destination was for
|
|
1:20:44
|
Hurley's mobile was +12 and also for his phone +12065015555.
|
|
1:20:52
|
Why is it going out as a local number with only 10 digits?
|
|
1:20:55
|
Or why when we called Sawyer's phone,
|
|
1:20:59
|
and it needed to dial international, why did it go out properly?
|
|
1:21:02
|
So goes back to module 10 and 11 for globalization
|
|
1:21:05
|
and localization, we first globalize the number
|
|
1:21:09
|
that was the remote destination number we used, was the globalized format
|
|
1:21:15
|
but then it's localized at the egress gateway.
|
|
1:21:19
|
So each of these egress gateways whether it's a SIP trunk to headquarters
|
|
1:21:23
|
or an ISTN, so we'll just jump to any one of these
|
|
1:21:32
|
via ISTN MGCP gateway at branch2 site
|
|
1:21:42
|
OK? Has a outbound called party transformation CSS
|
|
1:21:49
|
that matches a partition or contains a partition,
|
|
1:21:52
|
and matches called party
|
|
1:22:03
|
transformation patterns when the page finally loads.
|
|
1:22:08
|
And the ones that are for the Netherlands gateway
|
|
1:22:12
|
or the branch2 gateway so
|
|
1:22:15
|
when it's going out as a local number
|
|
1:22:18
|
that's chopping off everything and if we take a look at it
|
|
1:22:22
|
probably just sending it as is to the local gate or to a
|
|
1:22:27
|
routelist really it's actually sending it on
|
|
1:22:30
|
to a route pattern because our transformation.
|
|
1:22:32
|
I'm sorry we're not looking at translation.
|
|
1:22:35
|
This is the called party transformation so it's chopping off the
|
|
1:22:38
|
called party number and sending the remaining digits out to the gateway
|
|
1:22:42
|
or when we have the Netherlands gateway for, not that one
|
|
1:22:44
|
31 so calls within the Netherlands
|
|
1:22:48
|
So like to our digit 6 for mobile numbers and 70357575
|
|
1:22:56
|
we've got, that doesn't match 3120 but it does match +31.
|
|
1:23:01
|
We discard the predot, the +31 and prefix a 0
|
|
1:23:06
|
and so it was going out with 0670357575.
|
|
1:23:13
|
So again it's all of the work that we've already done
|
|
1:23:17
|
to set up our system that's allowing all of our remote destinations
|
|
1:23:22
|
to have full E164 numbers including the plus
|
|
1:23:26
|
and everything to work perfectly no matter
|
|
1:23:28
|
which egress gateway it goes out.
|
|
1:23:32
|
The power behind the globalization and localization.
|
|
1:23:38
|
OK? Let's clear off this gateway,
|
|
1:23:44
|
at this point we're gonna state that we have met all the
|
|
1:23:47
|
requirements for task 1, everything works properly.
|
|
1:23:50
|
|
