WEBVTT

00:00:00.000 --> 00:00:03.430 align:middle line:90%


00:00:03.430 --> 00:00:06.860 align:middle line:90%
[AUDIO LOGO]

00:00:06.860 --> 00:00:09.810 align:middle line:90%


00:00:09.810 --> 00:00:12.180 align:middle line:90%
Hello, and welcome to INE.

00:00:12.180 --> 00:00:14.820 align:middle line:84%
In this video, we would look
at section 2, dial plan.

00:00:14.820 --> 00:00:17.520 align:middle line:90%
Basically, task 2.1.

00:00:17.520 --> 00:00:18.990 align:middle line:90%
Now you're in this task.

00:00:18.990 --> 00:00:22.260 align:middle line:84%
It basically says that HQ
site and side B site need

00:00:22.260 --> 00:00:23.890 align:middle line:90%
to communicate with each other.

00:00:23.890 --> 00:00:25.770 align:middle line:84%
We need to provision
this request.

00:00:25.770 --> 00:00:28.930 align:middle line:84%
And the following information
has been given to us.

00:00:28.930 --> 00:00:31.440 align:middle line:84%
We need to configure
HQ cluster and side B

00:00:31.440 --> 00:00:33.480 align:middle line:84%
cluster to be able to
talk to each other.

00:00:33.480 --> 00:00:37.260 align:middle line:84%
All calls from HQ or from
side B towards each other

00:00:37.260 --> 00:00:39.630 align:middle line:90%
should route through the SME.

00:00:39.630 --> 00:00:43.120 align:middle line:84%
The HQ UCM must
send E164 number,

00:00:43.120 --> 00:00:48.360 align:middle line:84%
which is +14082022XXX as
the calling number to SME.

00:00:48.360 --> 00:00:55.710 align:middle line:84%
And side B must also send
E164, which is +19723033XXX.

00:00:55.710 --> 00:00:58.030 align:middle line:90%
as the calling number to SME.

00:00:58.030 --> 00:01:02.310 align:middle line:84%
SME must always send eight
digits as the calling number

00:01:02.310 --> 00:01:06.090 align:middle line:84%
to side B and eight digits
as the calling number

00:01:06.090 --> 00:01:09.310 align:middle line:90%
to HQ cluster.

00:01:09.310 --> 00:01:13.260 align:middle line:84%
SME must always send eight
digits as the called number

00:01:13.260 --> 00:01:17.400 align:middle line:84%
to side B and eight digits
as the called number

00:01:17.400 --> 00:01:19.500 align:middle line:90%
to HQ cluster.

00:01:19.500 --> 00:01:24.780 align:middle line:84%
The HQ cluster will dial eight
digits, which is 83033XXX

00:01:24.780 --> 00:01:28.230 align:middle line:84%
to call side B.
Similarly, side B

00:01:28.230 --> 00:01:33.630 align:middle line:84%
will dial eight digits, which
is 82022XXX as the called number

00:01:33.630 --> 00:01:35.430 align:middle line:90%
to call HQ side.

00:01:35.430 --> 00:01:40.980 align:middle line:84%
For example, when Tony
Stark dials 83033XXX,

00:01:40.980 --> 00:01:47.460 align:middle line:84%
Steve Rogers must see 82022003
as the calling number.

00:01:47.460 --> 00:01:50.640 align:middle line:84%
You are only allowed to
create one route pattern

00:01:50.640 --> 00:01:55.850 align:middle line:84%
on the HQ cluster and one route
pattern on the side B cluster.

00:01:55.850 --> 00:02:00.440 align:middle line:84%
We need to create a SIP trunk
between the HQ UCM and SME

00:02:00.440 --> 00:02:04.370 align:middle line:84%
and another SIP trunk between
the side B cluster and SME.

00:02:04.370 --> 00:02:07.340 align:middle line:84%
You must create a route
group, and the root group name

00:02:07.340 --> 00:02:12.110 align:middle line:84%
must be RG-SME on HQ
and side B cluster.

00:02:12.110 --> 00:02:19.970 align:middle line:84%
We must also create a route list
named as RL-SME on HQ cluster

00:02:19.970 --> 00:02:21.590 align:middle line:90%
and side B cluster.

00:02:21.590 --> 00:02:24.410 align:middle line:84%
Your task is complete
when Tony Stark can call

00:02:24.410 --> 00:02:26.850 align:middle line:90%
Steve Rogers and vice versa.

00:02:26.850 --> 00:02:29.300 align:middle line:84%
So before we actually
do this, let's, in fact,

00:02:29.300 --> 00:02:31.790 align:middle line:90%
see what the requirement is.

00:02:31.790 --> 00:02:33.500 align:middle line:84%
And let's, in fact,
do a whiteboarding

00:02:33.500 --> 00:02:36.270 align:middle line:84%
and see what the
exact requirement is.

00:02:36.270 --> 00:02:40.310 align:middle line:90%
So if I look back at--

00:02:40.310 --> 00:02:41.850 align:middle line:90%
let's, in fact, draw this.

00:02:41.850 --> 00:02:46.290 align:middle line:90%
So I have my HQ cluster.

00:02:46.290 --> 00:02:51.160 align:middle line:84%
So I have a phone here,
which is Tony Stark.

00:02:51.160 --> 00:02:57.880 align:middle line:84%
His extension is 2003 as per
our earlier configuration, which

00:02:57.880 --> 00:03:00.100 align:middle line:84%
we did, I believe,
in section 1 when

00:03:00.100 --> 00:03:03.550 align:middle line:84%
we had done Jabber
registration for Tony Stark.

00:03:03.550 --> 00:03:06.880 align:middle line:84%
So his extension is four
digits, which is 2003.

00:03:06.880 --> 00:03:12.010 align:middle line:84%
He connects to the HQ
cluster, which is the pub.

00:03:12.010 --> 00:03:15.070 align:middle line:90%
This would connect to SME.

00:03:15.070 --> 00:03:17.230 align:middle line:90%
So we have SME here.

00:03:17.230 --> 00:03:21.790 align:middle line:84%
This would have a SIP
trunk to the pub of side B.

00:03:21.790 --> 00:03:23.650 align:middle line:90%
So this is HQ.

00:03:23.650 --> 00:03:27.760 align:middle line:84%
This is side B. And on
the pub, the pub basically

00:03:27.760 --> 00:03:34.180 align:middle line:84%
has a phone connected, which
is Steve Rogers whose extension

00:03:34.180 --> 00:03:38.080 align:middle line:90%
is, again, four digits, 3003.

00:03:38.080 --> 00:03:39.940 align:middle line:84%
Now, the question
states that we need

00:03:39.940 --> 00:03:43.210 align:middle line:90%
to create a SIP trunk here.

00:03:43.210 --> 00:03:45.400 align:middle line:90%
And we need a SIP trunk here.

00:03:45.400 --> 00:03:50.710 align:middle line:84%
And what is the HQ user-- let's
say if HQ was calling side B,

00:03:50.710 --> 00:03:53.770 align:middle line:84%
all calls must route
through the SME, which

00:03:53.770 --> 00:03:57.160 align:middle line:84%
means there would not be any
SIP trunk direct between HQ

00:03:57.160 --> 00:03:58.780 align:middle line:90%
cluster and side B cluster.

00:03:58.780 --> 00:04:01.570 align:middle line:90%
It has to route through the SME.

00:04:01.570 --> 00:04:06.940 align:middle line:84%
Now, as for the question, the
HQ user, if he's dialing side B,

00:04:06.940 --> 00:04:09.020 align:middle line:90%
he would dial eight digits.

00:04:09.020 --> 00:04:20.089 align:middle line:84%
So the called number
would be 83033XXX,

00:04:20.089 --> 00:04:32.350 align:middle line:84%
and the calling number sent
to SME should be +14082022003.

00:04:32.350 --> 00:04:40.300 align:middle line:84%
So this is what should be
sent to SME by the HQ cluster.

00:04:40.300 --> 00:04:45.820 align:middle line:84%
When SME gets that, so SME would
see the calling number as E164

00:04:45.820 --> 00:04:51.340 align:middle line:90%
and called number as 83033XXX.

00:04:51.340 --> 00:04:56.050 align:middle line:84%
SME would forward
down to this pub.

00:04:56.050 --> 00:05:02.440 align:middle line:84%
The calling number should
change to 82022XXX,

00:05:02.440 --> 00:05:08.620 align:middle line:84%
and the called number would
still remain as 83033XXX.

00:05:08.620 --> 00:05:11.740 align:middle line:84%
The pub when he sends
it down to the phone,

00:05:11.740 --> 00:05:16.630 align:middle line:84%
because the phone
is four digits,

00:05:16.630 --> 00:05:18.850 align:middle line:84%
we would need to create a
translation pattern which

00:05:18.850 --> 00:05:23.170 align:middle line:84%
translates the called number
from eight digits to four

00:05:23.170 --> 00:05:23.840 align:middle line:90%
digits.

00:05:23.840 --> 00:05:27.000 align:middle line:84%
So we would need to send
down calling number.

00:05:27.000 --> 00:05:29.360 align:middle line:84%
So I'm going to
write this down here.

00:05:29.360 --> 00:05:35.272 align:middle line:90%
So calling and called.

00:05:35.272 --> 00:05:42.550 align:middle line:84%
Calling would be 82022XXX,
and called would be 3003.

00:05:42.550 --> 00:05:49.280 align:middle line:84%
This is what the pub should
send down to the phone.

00:05:49.280 --> 00:05:51.190 align:middle line:90%
So this is our requirement.

00:05:51.190 --> 00:05:54.130 align:middle line:84%
And this is, again,
going to be reverse also.

00:05:54.130 --> 00:05:57.250 align:middle line:84%
If the side B cluster
is dialing HQ,

00:05:57.250 --> 00:06:02.650 align:middle line:84%
he would send the calling number
as E164, called as eight digits

00:06:02.650 --> 00:06:04.720 align:middle line:90%
to the SME.

00:06:04.720 --> 00:06:07.150 align:middle line:84%
The SME would strip
the calling number

00:06:07.150 --> 00:06:10.510 align:middle line:84%
from E164 to eight
digits and forward

00:06:10.510 --> 00:06:13.480 align:middle line:84%
it to HQ cluster, which
means the HQ cluster is going

00:06:13.480 --> 00:06:15.460 align:middle line:84%
to get calling number
as eight digits

00:06:15.460 --> 00:06:18.280 align:middle line:84%
and called number
as eight digits.

00:06:18.280 --> 00:06:22.930 align:middle line:84%
The pub on the HQ side is going
to strip the called number

00:06:22.930 --> 00:06:25.840 align:middle line:84%
from eight digits to four
digits because my extensions are

00:06:25.840 --> 00:06:27.040 align:middle line:90%
four digits.

00:06:27.040 --> 00:06:29.230 align:middle line:84%
And this is what our
requirement states.

00:06:29.230 --> 00:06:31.090 align:middle line:84%
At the same time,
we are only allowed

00:06:31.090 --> 00:06:35.140 align:middle line:84%
to use one route pattern
on pub, which is going

00:06:35.140 --> 00:06:37.330 align:middle line:90%
to be backslash plus bang.

00:06:37.330 --> 00:06:39.280 align:middle line:90%
And same thing on this pub.

00:06:39.280 --> 00:06:42.730 align:middle line:84%
We are only supposed to use
backslash plus bang one route

00:06:42.730 --> 00:06:43.340 align:middle line:90%
pattern.

00:06:43.340 --> 00:06:47.180 align:middle line:84%
So we need to make it work
with a single route pattern.

00:06:47.180 --> 00:06:49.820 align:middle line:84%
So let's quickly
go and build this.

00:06:49.820 --> 00:06:55.210 align:middle line:84%
I am going to build
this by starting off

00:06:55.210 --> 00:06:57.070 align:middle line:90%
with the HQ cluster.

00:06:57.070 --> 00:06:58.990 align:middle line:84%
What I'm actually
going to do is I

00:06:58.990 --> 00:07:01.220 align:middle line:90%
will build both simultaneously.

00:07:01.220 --> 00:07:04.270 align:middle line:84%
So I will build the HQ
cluster and the side B cluster

00:07:04.270 --> 00:07:05.450 align:middle line:90%
together.

00:07:05.450 --> 00:07:09.490 align:middle line:84%
And once we build the HQ
cluster and the side B cluster,

00:07:09.490 --> 00:07:11.570 align:middle line:90%
I will go and configure the SME.

00:07:11.570 --> 00:07:15.610 align:middle line:84%
So let's go and
access my Jabber1 PC.

00:07:15.610 --> 00:07:18.230 align:middle line:90%
So I have my HQ cluster here.

00:07:18.230 --> 00:07:21.550 align:middle line:90%
Let's log in.

00:07:21.550 --> 00:07:27.885 align:middle line:84%
And let's also log into side
B and also log into SME.

00:07:27.885 --> 00:07:37.050 align:middle line:90%


00:07:37.050 --> 00:07:38.730 align:middle line:90%
So let's log in.

00:07:38.730 --> 00:07:40.620 align:middle line:90%
Administrator.

00:07:40.620 --> 00:07:49.080 align:middle line:90%
Password is C1sc0123!.

00:07:49.080 --> 00:07:51.240 align:middle line:90%
Administrator.

00:07:51.240 --> 00:07:55.590 align:middle line:90%
Password C1sc0123!.

00:07:55.590 --> 00:07:59.060 align:middle line:90%
And same thing here.

00:07:59.060 --> 00:08:00.320 align:middle line:90%
Administrator.

00:08:00.320 --> 00:08:04.040 align:middle line:90%
Password C1sc0123!.

00:08:04.040 --> 00:08:05.270 align:middle line:90%
C was uppercase.

00:08:05.270 --> 00:08:10.790 align:middle line:90%


00:08:10.790 --> 00:08:13.810 align:middle line:90%
Now what I'm going to do is--

00:08:13.810 --> 00:08:15.520 align:middle line:84%
the first thing
that I will do is

00:08:15.520 --> 00:08:20.355 align:middle line:84%
I will create some
partitions on my HQ cluster.

00:08:20.355 --> 00:08:22.480 align:middle line:84%
And at the same time, I
would create the same thing

00:08:22.480 --> 00:08:23.540 align:middle line:90%
on side B cluster.

00:08:23.540 --> 00:08:26.920 align:middle line:84%
Let's do it together side
by side so at the end of it,

00:08:26.920 --> 00:08:29.740 align:middle line:90%
we are able to test it out.

00:08:29.740 --> 00:08:40.100 align:middle line:90%


00:08:40.100 --> 00:08:42.138 align:middle line:84%
So first thing, we'll
go to HQ cluster.

00:08:42.138 --> 00:08:43.180 align:middle line:90%
Let's go to call routing.

00:08:43.180 --> 00:08:58.100 align:middle line:90%


00:08:58.100 --> 00:08:59.380 align:middle line:90%
It's taking a bit of time.

00:08:59.380 --> 00:09:02.790 align:middle line:90%


00:09:02.790 --> 00:09:04.440 align:middle line:84%
I think because they
just boot it up.

00:09:04.440 --> 00:09:06.810 align:middle line:90%
So it just takes a bit of time.

00:09:06.810 --> 00:09:08.865 align:middle line:84%
Once it comes up,
it's super fast.

00:09:08.865 --> 00:09:22.010 align:middle line:90%


00:09:22.010 --> 00:09:25.220 align:middle line:84%
Now, based on our
earlier configuration,

00:09:25.220 --> 00:09:27.500 align:middle line:84%
if you remember
from section 1, we

00:09:27.500 --> 00:09:29.270 align:middle line:90%
did not create any partitions.

00:09:29.270 --> 00:09:32.420 align:middle line:84%
We did not create any CSS,
which means my phones,

00:09:32.420 --> 00:09:35.120 align:middle line:84%
my lines are in
the none partition,

00:09:35.120 --> 00:09:40.340 align:middle line:84%
and my phone's device CSS,
again, it has access to none.

00:09:40.340 --> 00:09:42.950 align:middle line:90%
So he can only access PT-NONE.

00:09:42.950 --> 00:09:54.570 align:middle line:84%
So on side B, what I'm going to
do is go to Class of Control,

00:09:54.570 --> 00:09:56.310 align:middle line:90%
create four partitions.

00:09:56.310 --> 00:09:58.350 align:middle line:84%
So I'm going to create
four partitions.

00:09:58.350 --> 00:09:59.430 align:middle line:90%
I'll tell you why.

00:09:59.430 --> 00:10:01.410 align:middle line:84%
And once we've done
the configuration,

00:10:01.410 --> 00:10:05.200 align:middle line:84%
I'll explain the flow of it,
how the flow is happening,

00:10:05.200 --> 00:10:07.060 align:middle line:90%
how the call is going through.

00:10:07.060 --> 00:10:09.210 align:middle line:84%
So I'm going to go,
and let's do a Find.

00:10:09.210 --> 00:10:12.210 align:middle line:84%
So I don't have any partitions
besides the default ones.

00:10:12.210 --> 00:10:16.650 align:middle line:84%
Let's go and add
four partitions.

00:10:16.650 --> 00:10:18.530 align:middle line:90%
So this is going to be PT--

00:10:18.530 --> 00:10:22.550 align:middle line:90%
let's name this as intersite.

00:10:22.550 --> 00:10:24.020 align:middle line:90%
So PT-INTERSITE.

00:10:24.020 --> 00:10:26.630 align:middle line:84%
Let's make one more PT
single route pattern.

00:10:26.630 --> 00:10:36.950 align:middle line:84%
Let's make one more as
partition inbound from SME.

00:10:36.950 --> 00:10:41.570 align:middle line:84%
And one more, which is
going to be PT-CALLED-XFORM.

00:10:41.570 --> 00:10:50.600 align:middle line:90%


00:10:50.600 --> 00:10:52.250 align:middle line:84%
So four partitions,
I'm creating.

00:10:52.250 --> 00:10:55.790 align:middle line:84%
PT-INTERSITE would
be for outbound

00:10:55.790 --> 00:11:01.490 align:middle line:84%
so that my phones can dial
side B. The PT single route

00:11:01.490 --> 00:11:05.540 align:middle line:84%
pattern would be for my route
pattern, which the phones would

00:11:05.540 --> 00:11:07.310 align:middle line:90%
not have access to directly.

00:11:07.310 --> 00:11:09.320 align:middle line:84%
The translation pattern
would have access

00:11:09.320 --> 00:11:10.850 align:middle line:90%
to the single route pattern.

00:11:10.850 --> 00:11:15.200 align:middle line:84%
The inbound is for translating
the calls coming from SME

00:11:15.200 --> 00:11:19.820 align:middle line:84%
because if you remember in
that diagram that I drew,

00:11:19.820 --> 00:11:23.990 align:middle line:84%
when the call comes in to
the pub or even the sub,

00:11:23.990 --> 00:11:25.220 align:middle line:90%
it comes from the SME.

00:11:25.220 --> 00:11:27.200 align:middle line:84%
The called number
was eight digits.

00:11:27.200 --> 00:11:29.360 align:middle line:84%
I need to translate
that to four digits

00:11:29.360 --> 00:11:32.520 align:middle line:84%
because my phones have the
extension as four digits.

00:11:32.520 --> 00:11:36.740 align:middle line:84%
So I would go and
create one called xform.

00:11:36.740 --> 00:11:43.430 align:middle line:84%
The called xform is
going to be to translate

00:11:43.430 --> 00:11:48.410 align:middle line:84%
basically the eight
digits to four digits.

00:11:48.410 --> 00:11:54.740 align:middle line:84%
And the inbound from SME
would be for giving access

00:11:54.740 --> 00:11:57.538 align:middle line:90%
to the phone's partition.

00:11:57.538 --> 00:11:58.580 align:middle line:90%
We'll, in fact, see this.

00:11:58.580 --> 00:12:00.210 align:middle line:84%
We'll see where
all this fits in.

00:12:00.210 --> 00:12:03.990 align:middle line:84%
So I'm going to create
these four partitions.

00:12:03.990 --> 00:12:06.990 align:middle line:84%
And let's try and see
if we can copy this.

00:12:06.990 --> 00:12:09.710 align:middle line:90%


00:12:09.710 --> 00:12:11.255 align:middle line:90%
Copy and save.

00:12:11.255 --> 00:12:16.790 align:middle line:90%


00:12:16.790 --> 00:12:21.990 align:middle line:84%
Next, I will go and
create four calling search

00:12:21.990 --> 00:12:23.760 align:middle line:90%
spaces, one for each partition.

00:12:23.760 --> 00:12:28.290 align:middle line:90%


00:12:28.290 --> 00:12:32.852 align:middle line:84%
So CSS single route
pattern will contain

00:12:32.852 --> 00:12:34.310 align:middle line:84%
the partition single
route pattern.

00:12:34.310 --> 00:12:41.480 align:middle line:90%


00:12:41.480 --> 00:12:42.500 align:middle line:90%
Let's add one more.

00:12:42.500 --> 00:12:45.430 align:middle line:90%


00:12:45.430 --> 00:12:55.310 align:middle line:84%
CSS-INTERSITE will contain
the intersite partition.

00:12:55.310 --> 00:12:59.330 align:middle line:84%
Or, in fact, let's name
this as CSS-PHONES.

00:12:59.330 --> 00:13:01.880 align:middle line:84%
So CSS-PHONES will
contain the intersite.

00:13:01.880 --> 00:13:06.730 align:middle line:90%


00:13:06.730 --> 00:13:16.600 align:middle line:84%
Then I'll create one
more, CSS-CALLED-XFORM,

00:13:16.600 --> 00:13:20.640 align:middle line:84%
which will contain the
called xform partition.

00:13:20.640 --> 00:13:26.390 align:middle line:90%


00:13:26.390 --> 00:13:36.620 align:middle line:84%
And then one more, which
is going to be CSS--

00:13:36.620 --> 00:13:39.890 align:middle line:84%
I believe it is the last
one-- inbound from SME.

00:13:39.890 --> 00:13:49.450 align:middle line:84%
So inbound from SME, which
contains the inbound from SME.

00:13:49.450 --> 00:13:51.880 align:middle line:90%
So four, partitions, four CSS.

00:13:51.880 --> 00:13:56.690 align:middle line:84%
Let's do exactly the same
thing on the HQ cluster.

00:13:56.690 --> 00:13:59.020 align:middle line:84%
So on HQ cluster,
I would go back

00:13:59.020 --> 00:14:02.440 align:middle line:84%
and go to Class of Control,
create four partitions.

00:14:02.440 --> 00:14:05.390 align:middle line:90%


00:14:05.390 --> 00:14:06.320 align:middle line:90%
Let's do Add.

00:14:06.320 --> 00:14:09.130 align:middle line:90%


00:14:09.130 --> 00:14:12.520 align:middle line:90%
And let's paste that.

00:14:12.520 --> 00:14:14.070 align:middle line:90%
So these four partitions.

00:14:14.070 --> 00:14:18.530 align:middle line:90%


00:14:18.530 --> 00:14:21.710 align:middle line:84%
Let's now go and
create four CSS.

00:14:21.710 --> 00:14:23.870 align:middle line:90%
So Calling Search Space.

00:14:23.870 --> 00:14:24.710 align:middle line:90%
Add New.

00:14:24.710 --> 00:14:27.240 align:middle line:90%


00:14:27.240 --> 00:14:31.910 align:middle line:84%
So CSS single route pattern,
which contains a single route

00:14:31.910 --> 00:14:32.410 align:middle line:90%
pattern.

00:14:32.410 --> 00:14:41.170 align:middle line:90%


00:14:41.170 --> 00:14:47.460 align:middle line:84%
Then I have one more,
which is CSS-PHONES,

00:14:47.460 --> 00:14:50.080 align:middle line:90%
which contains the intersite.

00:14:50.080 --> 00:14:55.110 align:middle line:84%
So CSS-PHONES, which contains
the intersite partition.

00:14:55.110 --> 00:15:00.310 align:middle line:90%


00:15:00.310 --> 00:15:09.420 align:middle line:84%
Then I have the
CSS-CALLED-XFORM, which

00:15:09.420 --> 00:15:11.130 align:middle line:90%
will contain the called xform.

00:15:11.130 --> 00:15:20.490 align:middle line:90%


00:15:20.490 --> 00:15:27.520 align:middle line:84%
And lastly, I will have
CSS-INBOUND-FROM-SME,

00:15:27.520 --> 00:15:30.190 align:middle line:84%
which will contain
the inbound from SME.

00:15:30.190 --> 00:15:34.660 align:middle line:84%
So four partitions and four
CSS done on HQ and side B. I'm

00:15:34.660 --> 00:15:36.790 align:middle line:90%
not touching the SME right now.

00:15:36.790 --> 00:15:39.250 align:middle line:84%
Next thing what I'm
going to do is I

00:15:39.250 --> 00:15:41.980 align:middle line:84%
would go and attach
all my phones

00:15:41.980 --> 00:15:44.500 align:middle line:84%
device CSS with the
CSS phones, which

00:15:44.500 --> 00:15:49.220 align:middle line:84%
means my phones will now
have access to the partition

00:15:49.220 --> 00:15:51.970 align:middle line:90%
intersite and partition none.

00:15:51.970 --> 00:15:53.220 align:middle line:90%
So let's go to my phones.

00:15:53.220 --> 00:15:59.020 align:middle line:84%
So on HQ cluster, let's go to
Phones and say Update Phones.

00:15:59.020 --> 00:16:06.040 align:middle line:90%


00:16:06.040 --> 00:16:07.060 align:middle line:90%
Let's do a Find.

00:16:07.060 --> 00:16:09.800 align:middle line:84%
I think we have
three phones there.

00:16:09.800 --> 00:16:14.410 align:middle line:84%
So we have three phones
CSFONE, CSFTWO, and Tony Stark.

00:16:14.410 --> 00:16:23.620 align:middle line:84%
So on all three
phones, let's do Next

00:16:23.620 --> 00:16:28.000 align:middle line:90%
and let's apply the config.

00:16:28.000 --> 00:16:29.110 align:middle line:90%
Or maybe we can reset.

00:16:29.110 --> 00:16:33.763 align:middle line:90%


00:16:33.763 --> 00:16:35.180 align:middle line:84%
So either you can
apply the config

00:16:35.180 --> 00:16:36.347 align:middle line:90%
or you can reset the config.

00:16:36.347 --> 00:16:37.350 align:middle line:90%
That's really up to you.

00:16:37.350 --> 00:16:38.510 align:middle line:90%
So we can do Apply.

00:16:38.510 --> 00:16:40.850 align:middle line:84%
And then scroll down here
to Calling Search Space

00:16:40.850 --> 00:16:43.430 align:middle line:84%
and apply the calling
search space CSS-PHONES

00:16:43.430 --> 00:16:44.660 align:middle line:90%
to all my phones.

00:16:44.660 --> 00:16:50.030 align:middle line:84%
Scroll down and say Run
Immediately and Submit.

00:16:50.030 --> 00:16:52.930 align:middle line:84%
So now all three
phones, device CSS

00:16:52.930 --> 00:16:57.050 align:middle line:84%
is CSS-PHONES, which contains
the partition PT-INTERSITE,

00:16:57.050 --> 00:16:59.620 align:middle line:84%
which means they have
access to PT-INTERSITE

00:16:59.620 --> 00:17:02.740 align:middle line:84%
and the default,
which is PT-NONE.

00:17:02.740 --> 00:17:05.680 align:middle line:84%
Let's go and check on
any one of my device

00:17:05.680 --> 00:17:06.700 align:middle line:90%
on any one of my phone.

00:17:06.700 --> 00:17:16.780 align:middle line:90%


00:17:16.780 --> 00:17:20.020 align:middle line:84%
Same thing on side
B, I would go to--

00:17:20.020 --> 00:17:22.420 align:middle line:84%
now, on side B, I think
we only have one phone.

00:17:22.420 --> 00:17:24.550 align:middle line:84%
So I don't need to go
to bulk administration.

00:17:24.550 --> 00:17:28.224 align:middle line:84%
I can just directly go
and apply it to my phone.

00:17:28.224 --> 00:17:31.400 align:middle line:90%


00:17:31.400 --> 00:17:33.240 align:middle line:84%
So we only have
one Steve Rogers.

00:17:33.240 --> 00:17:34.280 align:middle line:90%
So let's click on that.

00:17:34.280 --> 00:17:42.130 align:middle line:90%


00:17:42.130 --> 00:17:45.950 align:middle line:84%
And give him access
to the CSS-PHONES.

00:17:45.950 --> 00:17:54.550 align:middle line:90%


00:17:54.550 --> 00:17:55.840 align:middle line:90%
And let's apply the settings.

00:17:55.840 --> 00:18:06.460 align:middle line:90%


00:18:06.460 --> 00:18:08.490 align:middle line:90%
So now on side B, it's done.

00:18:08.490 --> 00:18:11.280 align:middle line:84%
Phones have access
to CSS-PHONES.

00:18:11.280 --> 00:18:15.450 align:middle line:84%
Same thing if I look
at HQ, just to verify.

00:18:15.450 --> 00:18:16.860 align:middle line:90%
And let's say Tony Stark.

00:18:16.860 --> 00:18:19.620 align:middle line:90%


00:18:19.620 --> 00:18:22.920 align:middle line:84%
You would see the
CSS-PHONES has been applied

00:18:22.920 --> 00:18:25.050 align:middle line:90%
through bulk administration.

00:18:25.050 --> 00:18:27.150 align:middle line:84%
Next thing what
I'm going to do is,

00:18:27.150 --> 00:18:29.970 align:middle line:90%
what is the user going to dial?

00:18:29.970 --> 00:18:33.990 align:middle line:90%
He is going to dial 83033XXX.

00:18:33.990 --> 00:18:35.640 align:middle line:90%
So can I create a route pattern?

00:18:35.640 --> 00:18:38.340 align:middle line:84%
No, because the question
states that we can only

00:18:38.340 --> 00:18:41.610 align:middle line:84%
create one route pattern,
which is backslash plus bang,

00:18:41.610 --> 00:18:46.570 align:middle line:84%
on HQ cluster and
on side B cluster.

00:18:46.570 --> 00:18:52.165 align:middle line:84%
So what I'm going to do is
I will create a translation

00:18:52.165 --> 00:18:52.665 align:middle line:90%
pattern.

00:18:52.665 --> 00:18:58.460 align:middle line:90%


00:18:58.460 --> 00:19:02.770 align:middle line:84%
So on the HQ cluster, I will
create a translation pattern,

00:19:02.770 --> 00:19:07.840 align:middle line:90%
which dials side B, 83033XXX.

00:19:07.840 --> 00:19:10.270 align:middle line:90%
So I'm dialing eight digits.

00:19:10.270 --> 00:19:13.330 align:middle line:84%
This would go in the
partition intersite.

00:19:13.330 --> 00:19:16.940 align:middle line:84%
So now my phones have access
to this translation pattern.

00:19:16.940 --> 00:19:20.200 align:middle line:84%
Now, if you remember,
as per the requirement,

00:19:20.200 --> 00:19:24.010 align:middle line:84%
when I dial eight digits,
the calling number

00:19:24.010 --> 00:19:27.430 align:middle line:84%
being sent to SME
should be E164.

00:19:27.430 --> 00:19:29.170 align:middle line:84%
By default, what's
going to happen

00:19:29.170 --> 00:19:32.560 align:middle line:84%
if I don't make any changes,
since my phones have

00:19:32.560 --> 00:19:36.070 align:middle line:84%
the extension of four digits,
the calling number going to SME

00:19:36.070 --> 00:19:37.510 align:middle line:90%
would be four digits.

00:19:37.510 --> 00:19:38.960 align:middle line:90%
I need to change that.

00:19:38.960 --> 00:19:48.220 align:middle line:84%
So here, I would say change
the calling number to E164.

00:19:48.220 --> 00:19:52.990 align:middle line:84%
And I would also go and remove
the Provide Outside Dial Tone

00:19:52.990 --> 00:19:55.180 align:middle line:84%
because we're not
really dialing in PSTN.

00:19:55.180 --> 00:19:57.940 align:middle line:84%
We're not dialing 9 and
basically the access code

00:19:57.940 --> 00:20:00.070 align:middle line:90%
and then dialing some digits.

00:20:00.070 --> 00:20:02.320 align:middle line:84%
Since we're dialing intersite,
there's no access code.

00:20:02.320 --> 00:20:05.620 align:middle line:84%
I can remove the Provide
Outside Dial Tone.

00:20:05.620 --> 00:20:09.490 align:middle line:84%
And the called number, I
am going to prefix plus.

00:20:09.490 --> 00:20:11.560 align:middle line:90%
Now, why we prefixing plus?

00:20:11.560 --> 00:20:15.640 align:middle line:84%
Because if I don't prefix
plus, what's my route pattern

00:20:15.640 --> 00:20:16.360 align:middle line:90%
going to contain?

00:20:16.360 --> 00:20:18.693 align:middle line:84%
Only a single route pattern,
right, as per the question.

00:20:18.693 --> 00:20:21.700 align:middle line:84%
The route pattern will
have backslash plus bang.

00:20:21.700 --> 00:20:25.970 align:middle line:84%
Plus, which means for me
to hit the route pattern,

00:20:25.970 --> 00:20:29.480 align:middle line:84%
I need to prefix my called
number from eight digits,

00:20:29.480 --> 00:20:35.110 align:middle line:84%
which is here, from this
eight digits to +83033XXX.

00:20:35.110 --> 00:20:37.450 align:middle line:90%
So I'm prefixing that.

00:20:37.450 --> 00:20:40.210 align:middle line:84%
And then it needs to
hit the route pattern.

00:20:40.210 --> 00:20:43.120 align:middle line:84%
Now, the route
pattern is going to be

00:20:43.120 --> 00:20:47.230 align:middle line:84%
in the partition of partition
single route pattern.

00:20:47.230 --> 00:20:48.880 align:middle line:84%
Phones don't have
access to that.

00:20:48.880 --> 00:20:52.000 align:middle line:84%
I don't want my phones to
be directly having access

00:20:52.000 --> 00:20:55.660 align:middle line:84%
to the single route pattern
because he's never going

00:20:55.660 --> 00:20:57.850 align:middle line:90%
to dial +8303.

00:20:57.850 --> 00:21:01.030 align:middle line:90%
He will just dial 83033XXX.

00:21:01.030 --> 00:21:02.740 align:middle line:90%
It hits the translation pattern.

00:21:02.740 --> 00:21:04.960 align:middle line:90%
Calling number changes to E164.

00:21:04.960 --> 00:21:08.860 align:middle line:84%
Called number
changes to +83033XXX.

00:21:08.860 --> 00:21:11.720 align:middle line:84%
And then from there, it needs
to go to the route pattern.

00:21:11.720 --> 00:21:14.470 align:middle line:84%
So my translation pattern
calling search space

00:21:14.470 --> 00:21:18.070 align:middle line:84%
will have access to CSS
single route pattern, which

00:21:18.070 --> 00:21:20.590 align:middle line:84%
means my phones don't have
access to the route pattern

00:21:20.590 --> 00:21:22.090 align:middle line:90%
directly.

00:21:22.090 --> 00:21:24.250 align:middle line:84%
Phones have access to
the translation pattern.

00:21:24.250 --> 00:21:27.490 align:middle line:84%
The translation button changes
the calling number to E164,

00:21:27.490 --> 00:21:33.130 align:middle line:84%
called number to +83033XXX, and
then goes to the route pattern

00:21:33.130 --> 00:21:36.220 align:middle line:84%
because his CSS, the
transition pattern CSS,

00:21:36.220 --> 00:21:39.790 align:middle line:84%
is CSS single route pattern,
which contains the partition

00:21:39.790 --> 00:21:42.970 align:middle line:84%
single route pattern, which is
where my route pattern would

00:21:42.970 --> 00:21:43.640 align:middle line:90%
be.

00:21:43.640 --> 00:21:44.485 align:middle line:90%
Let's save this.

00:21:44.485 --> 00:21:51.040 align:middle line:90%


00:21:51.040 --> 00:21:53.980 align:middle line:84%
Exactly the same thing I
would do on side B. So let's

00:21:53.980 --> 00:21:58.120 align:middle line:84%
go to side B and go
to translation pattern

00:21:58.120 --> 00:22:01.870 align:middle line:84%
and do reverse when
side B calls HQ.

00:22:01.870 --> 00:22:05.050 align:middle line:90%
Let's add this.

00:22:05.050 --> 00:22:11.340 align:middle line:84%
So this would be 82022XXX,
which is HQ cluster.

00:22:11.340 --> 00:22:13.290 align:middle line:84%
This would go into
partition intersite.

00:22:13.290 --> 00:22:15.060 align:middle line:84%
So my phones of side
B will have access

00:22:15.060 --> 00:22:16.620 align:middle line:90%
to this translation pattern.

00:22:16.620 --> 00:22:18.570 align:middle line:84%
This translation
pattern will have access

00:22:18.570 --> 00:22:20.100 align:middle line:90%
to single route pattern.

00:22:20.100 --> 00:22:22.320 align:middle line:84%
Remove the Provide
Outside Dial Tone.

00:22:22.320 --> 00:22:25.808 align:middle line:84%
And enable the
checkbox for calling

00:22:25.808 --> 00:22:27.600 align:middle line:84%
for external phone
number mask, which means

00:22:27.600 --> 00:22:30.360 align:middle line:90%
my calling number becomes E164.

00:22:30.360 --> 00:22:33.000 align:middle line:84%
Called number needs to
be prefixed with plus.

00:22:33.000 --> 00:22:35.220 align:middle line:84%
Otherwise, it would not
match the route pattern

00:22:35.220 --> 00:22:38.010 align:middle line:84%
because the route
pattern has a plus.

00:22:38.010 --> 00:22:41.760 align:middle line:84%
So I need to prefix plus
to my called number.

00:22:41.760 --> 00:22:42.540 align:middle line:90%
Let's save this.

00:22:42.540 --> 00:22:48.040 align:middle line:90%


00:22:48.040 --> 00:22:50.530 align:middle line:84%
Next thing what
I'm going to do is

00:22:50.530 --> 00:23:01.320 align:middle line:84%
I will then go and
create a called xform,

00:23:01.320 --> 00:23:04.680 align:middle line:90%
a called party xform.

00:23:04.680 --> 00:23:08.960 align:middle line:84%
So this would be-- in
fact, you know what?

00:23:08.960 --> 00:23:11.060 align:middle line:90%
Let's do one thing.

00:23:11.060 --> 00:23:18.020 align:middle line:84%
At this point of time,
we would-- yeah, in fact,

00:23:18.020 --> 00:23:18.860 align:middle line:90%
let's do that.

00:23:18.860 --> 00:23:21.200 align:middle line:84%
Let's go and create
a transformation,

00:23:21.200 --> 00:23:23.510 align:middle line:90%
called party transformation.

00:23:23.510 --> 00:23:26.640 align:middle line:90%
Now, why are we doing this?

00:23:26.640 --> 00:23:30.360 align:middle line:84%
As of right now, if
I don't do anything,

00:23:30.360 --> 00:23:35.460 align:middle line:84%
the HQ cluster is going to send
calling number to SME as E164

00:23:35.460 --> 00:23:38.460 align:middle line:90%
based on translation pattern.

00:23:38.460 --> 00:23:43.277 align:middle line:84%
Called number
would be +83033XXX,

00:23:43.277 --> 00:23:45.360 align:middle line:84%
hits the route pattern,
and route pattern forwards

00:23:45.360 --> 00:23:50.250 align:middle line:84%
to the SIP trunk, which means
SME would get a +83033XXX.

00:23:50.250 --> 00:23:55.500 align:middle line:84%
So before it sends to SME, we
need to strip off the plus.

00:23:55.500 --> 00:23:57.870 align:middle line:84%
See, the thing is that
why am I then adding it?

00:23:57.870 --> 00:23:58.920 align:middle line:90%
Think about it.

00:23:58.920 --> 00:24:02.830 align:middle line:84%
I am adding the plus before
in the translation pattern

00:24:02.830 --> 00:24:05.790 align:middle line:84%
so that the translation
pattern hits the route pattern

00:24:05.790 --> 00:24:08.170 align:middle line:84%
because the route
pattern is a plus.

00:24:08.170 --> 00:24:10.350 align:middle line:90%
So it hits the route pattern.

00:24:10.350 --> 00:24:12.750 align:middle line:84%
From the route pattern,
it goes to SIP trunk.

00:24:12.750 --> 00:24:15.180 align:middle line:84%
From the SIP trunk,
before it goes out to SME,

00:24:15.180 --> 00:24:20.070 align:middle line:84%
I want to strip off the plus
again so that my SME gets--

00:24:20.070 --> 00:24:22.710 align:middle line:84%
which you can see here,
as per the drawing,

00:24:22.710 --> 00:24:28.200 align:middle line:84%
the SME gets 83033XXX
and not +8303.

00:24:28.200 --> 00:24:33.030 align:middle line:84%
So I would go and create a
called party transformation

00:24:33.030 --> 00:24:43.330 align:middle line:84%
pattern, which would say
if the called number--

00:24:43.330 --> 00:24:44.980 align:middle line:84%
it's a called party
transformation.

00:24:44.980 --> 00:24:46.850 align:middle line:90%
Called party transformation.

00:24:46.850 --> 00:24:53.050 align:middle line:84%
So which will say
backslash plus .83033XXX.

00:24:53.050 --> 00:24:57.190 align:middle line:84%
So if it is this, this goes
into called party transform.

00:24:57.190 --> 00:24:59.818 align:middle line:90%
Do a PreDot.

00:24:59.818 --> 00:25:02.605 align:middle line:84%
So strip off the plus
from the called number.

00:25:02.605 --> 00:25:05.330 align:middle line:90%


00:25:05.330 --> 00:25:07.280 align:middle line:90%
Let's save this.

00:25:07.280 --> 00:25:09.110 align:middle line:84%
Now, who will have
access to this?

00:25:09.110 --> 00:25:11.100 align:middle line:90%
My SIP trunk.

00:25:11.100 --> 00:25:14.660 align:middle line:84%
So now I would go and
create a SIP trunk.

00:25:14.660 --> 00:25:18.050 align:middle line:84%
Let's, in fact, do exactly
the same thing on--

00:25:18.050 --> 00:25:25.080 align:middle line:84%
oh, wait, this is side B. So
this should be 8202, not 303.

00:25:25.080 --> 00:25:38.960 align:middle line:90%
So this should be 82022XXX.

00:25:38.960 --> 00:25:42.230 align:middle line:84%
So on side B, this is
what I was dialing.

00:25:42.230 --> 00:25:46.490 align:middle line:84%
So I'm stripping off the
plus from the 82022XXX.

00:25:46.490 --> 00:25:50.995 align:middle line:84%
I'm stripping off the
plus, which should be here.

00:25:50.995 --> 00:25:57.120 align:middle line:84%
On HQ, in the called
party transformation--

00:25:57.120 --> 00:26:07.020 align:middle line:90%


00:26:07.020 --> 00:26:07.830 align:middle line:90%
Add New.

00:26:07.830 --> 00:26:11.190 align:middle line:90%


00:26:11.190 --> 00:26:15.150 align:middle line:90%
+.83033XXX.

00:26:15.150 --> 00:26:17.723 align:middle line:84%
This would go into the
partition called xform.

00:26:17.723 --> 00:26:18.390 align:middle line:90%
And do a PreDot.

00:26:18.390 --> 00:26:22.750 align:middle line:90%


00:26:22.750 --> 00:26:24.430 align:middle line:90%
Should be PreDot.

00:26:24.430 --> 00:26:26.720 align:middle line:90%
And save.

00:26:26.720 --> 00:26:31.650 align:middle line:84%
So both on HQ and side
B, I have done this.

00:26:31.650 --> 00:26:37.160 align:middle line:84%
So on side B, my called number
is 8202, which is of HQ.

00:26:37.160 --> 00:26:44.330 align:middle line:84%
And on HQ, my called number
is 83033XXX and a PreDot.

00:26:44.330 --> 00:26:45.860 align:middle line:90%
Now let's create a SIP trunk.

00:26:45.860 --> 00:26:46.895 align:middle line:90%
SIP trunk to SME.

00:26:46.895 --> 00:26:50.230 align:middle line:90%


00:26:50.230 --> 00:26:51.160 align:middle line:90%
So let's do a Find.

00:26:51.160 --> 00:26:52.660 align:middle line:84%
I don't think we
have any SIP trunk.

00:26:52.660 --> 00:26:55.118 align:middle line:84%
I think we only have one SIP
trunk from earlier task, which

00:26:55.118 --> 00:26:56.910 align:middle line:90%
was the present status one.

00:26:56.910 --> 00:26:57.885 align:middle line:90%
Let's do Add New.

00:26:57.885 --> 00:27:04.740 align:middle line:90%


00:27:04.740 --> 00:27:06.090 align:middle line:90%
Go to SIP trunk.

00:27:06.090 --> 00:27:09.730 align:middle line:90%


00:27:09.730 --> 00:27:10.230 align:middle line:90%
Next.

00:27:10.230 --> 00:27:12.850 align:middle line:90%


00:27:12.850 --> 00:27:15.640 align:middle line:84%
Let's name this as
SIP-TRUNK-TO-SME.

00:27:15.640 --> 00:27:22.380 align:middle line:90%


00:27:22.380 --> 00:27:24.900 align:middle line:84%
My device pool would
be the default one.

00:27:24.900 --> 00:27:28.210 align:middle line:90%
Let's scroll down.

00:27:28.210 --> 00:27:30.330 align:middle line:84%
You should enable Run
on All Active Nodes.

00:27:30.330 --> 00:27:32.740 align:middle line:84%
Again, in my topology,
I only have a publisher.

00:27:32.740 --> 00:27:34.500 align:middle line:90%
I don't have subscribers.

00:27:34.500 --> 00:27:37.000 align:middle line:84%
But in the lab exam, you
may have subscribers also.

00:27:37.000 --> 00:27:38.880 align:middle line:84%
So it's highly advisable
to just turn this

00:27:38.880 --> 00:27:45.840 align:middle line:84%
on so that it basically runs
on all the unified CM nodes.

00:27:45.840 --> 00:27:47.970 align:middle line:90%
Let's scroll down.

00:27:47.970 --> 00:27:56.470 align:middle line:84%
And here, in the called
party transformation CSS,

00:27:56.470 --> 00:27:57.610 align:middle line:90%
I would apply that.

00:27:57.610 --> 00:28:00.690 align:middle line:84%
So I'm applying it--
when it goes out

00:28:00.690 --> 00:28:06.910 align:middle line:84%
to SME in the outbound calls,
I would strip off the plus.

00:28:06.910 --> 00:28:08.800 align:middle line:84%
Now, I have two
ways of doing this.

00:28:08.800 --> 00:28:13.740 align:middle line:84%
Either I can apply it here,
or I can go to device pool

00:28:13.740 --> 00:28:14.580 align:middle line:90%
and apply it there.

00:28:14.580 --> 00:28:16.920 align:middle line:84%
If you see this checkbox
here, this checkbox

00:28:16.920 --> 00:28:20.460 align:middle line:84%
says Use Device Pool Called
Party Transformation CSS.

00:28:20.460 --> 00:28:24.480 align:middle line:84%
So if I don't apply it here
or even if I apply it here--

00:28:24.480 --> 00:28:27.390 align:middle line:84%
the called xform, if I
apply it here and do not

00:28:27.390 --> 00:28:29.520 align:middle line:84%
uncheck this box,
it's not going to work

00:28:29.520 --> 00:28:33.120 align:middle line:84%
because he's not going to check
this called party transform.

00:28:33.120 --> 00:28:36.060 align:middle line:84%
He's going to check the device
pool's called party transform.

00:28:36.060 --> 00:28:39.190 align:middle line:84%
And this SIP trunk is in
the default device pool.

00:28:39.190 --> 00:28:42.130 align:middle line:84%
So either I go
and apply it there

00:28:42.130 --> 00:28:44.700 align:middle line:84%
and keep this
checkbox enabled, or I

00:28:44.700 --> 00:28:46.920 align:middle line:90%
apply it here and uncheck this.

00:28:46.920 --> 00:28:48.220 align:middle line:90%
That's really up to you.

00:28:48.220 --> 00:28:51.690 align:middle line:84%
So maybe for HQ, I'll do
it inside the SIP trunk.

00:28:51.690 --> 00:28:54.330 align:middle line:84%
And for side B, I'll do
it inside the device pool

00:28:54.330 --> 00:28:56.320 align:middle line:84%
just to show you
the differences.

00:28:56.320 --> 00:28:59.250 align:middle line:90%
So I'll do this here.

00:28:59.250 --> 00:29:00.900 align:middle line:84%
Oh, I need to apply
the SIP profile.

00:29:00.900 --> 00:29:03.740 align:middle line:90%
Let's scroll down.

00:29:03.740 --> 00:29:07.520 align:middle line:84%
And the SIP trunk profile is
going to be the default one.

00:29:07.520 --> 00:29:09.980 align:middle line:84%
The SIP profile is going
to be the standard one.

00:29:09.980 --> 00:29:11.940 align:middle line:84%
And the SME's
addresses, hq-ucm--

00:29:11.940 --> 00:29:14.510 align:middle line:90%


00:29:14.510 --> 00:29:16.880 align:middle line:90%
I think it's hq-ucm-sme.ine.com.

00:29:16.880 --> 00:29:20.420 align:middle line:90%


00:29:20.420 --> 00:29:24.110 align:middle line:84%
Now, if you don't know the FQDN,
you can put the IP address.

00:29:24.110 --> 00:29:26.510 align:middle line:84%
If you want to put the
FQDN and you don't know it,

00:29:26.510 --> 00:29:31.220 align:middle line:84%
go to your DNS machine and
check the A record for the SME.

00:29:31.220 --> 00:29:33.830 align:middle line:84%
So I know that it's
hq-cucm-sme.ine.com.

00:29:33.830 --> 00:29:38.300 align:middle line:90%


00:29:38.300 --> 00:29:40.010 align:middle line:90%
And let's save this.

00:29:40.010 --> 00:29:46.850 align:middle line:90%


00:29:46.850 --> 00:29:49.300 align:middle line:84%
So now three
partitions we've used.

00:29:49.300 --> 00:29:53.200 align:middle line:84%
We've used the PT-INTERSITE
for the translation pattern.

00:29:53.200 --> 00:29:56.472 align:middle line:84%
We've used the
single route pattern.

00:29:56.472 --> 00:29:58.180 align:middle line:84%
We haven't created
the route pattern yet,

00:29:58.180 --> 00:30:00.760 align:middle line:84%
but we've still used the CSS
for the single route pattern

00:30:00.760 --> 00:30:02.260 align:middle line:90%
inside the translation pattern.

00:30:02.260 --> 00:30:05.007 align:middle line:84%
And then we've used
the called xform for--

00:30:05.007 --> 00:30:07.810 align:middle line:90%


00:30:07.810 --> 00:30:11.390 align:middle line:84%
when the call goes out to
SME, the called number,

00:30:11.390 --> 00:30:15.250 align:middle line:84%
which was changed by the
translation pattern to +8303

00:30:15.250 --> 00:30:19.090 align:middle line:84%
or +8202 from side
B's perspective,

00:30:19.090 --> 00:30:21.910 align:middle line:84%
that will strip off the
plus and send to SME,

00:30:21.910 --> 00:30:23.800 align:middle line:84%
which is done by
the called xform.

00:30:23.800 --> 00:30:27.040 align:middle line:84%
There's one CSS which
we haven't used,

00:30:27.040 --> 00:30:29.650 align:middle line:84%
the one which was
inbound from SME.

00:30:29.650 --> 00:30:33.510 align:middle line:90%
That is going to go here.

00:30:33.510 --> 00:30:35.730 align:middle line:84%
That is going to go
in the inbound calls,

00:30:35.730 --> 00:30:37.440 align:middle line:90%
calling search space.

00:30:37.440 --> 00:30:39.150 align:middle line:90%
I would say inbound from SME.

00:30:39.150 --> 00:30:40.620 align:middle line:90%
Now, what will this contain?

00:30:40.620 --> 00:30:43.860 align:middle line:84%
This contains the
partition inbound from SME.

00:30:43.860 --> 00:30:46.080 align:middle line:90%
Why are we doing this?

00:30:46.080 --> 00:30:51.540 align:middle line:84%
If you see in the whiteboard,
when the call comes in from pub

00:30:51.540 --> 00:30:54.330 align:middle line:84%
going down to the phone,
since the phone is

00:30:54.330 --> 00:30:58.680 align:middle line:84%
a four-digit extension, I need
to strip off the called number

00:30:58.680 --> 00:31:01.410 align:middle line:84%
from eight digits
to four digits.

00:31:01.410 --> 00:31:04.030 align:middle line:84%
And that's going to happen
in the translation pattern.

00:31:04.030 --> 00:31:09.540 align:middle line:84%
So my SIP trunk on the pub on
the inbound on the SIP trunk,

00:31:09.540 --> 00:31:12.480 align:middle line:84%
I would have access to
CSS-INBOUND-FROM-SME,

00:31:12.480 --> 00:31:15.420 align:middle line:84%
which has the partition
inbound from SME.

00:31:15.420 --> 00:31:18.700 align:middle line:84%
And that would go inside
a translation pattern.

00:31:18.700 --> 00:31:21.630 align:middle line:84%
So if I go back
to my HQ cluster--

00:31:21.630 --> 00:31:24.120 align:middle line:90%
let me go back here.

00:31:24.120 --> 00:31:25.470 align:middle line:90%
And first, let's save this.

00:31:25.470 --> 00:31:35.050 align:middle line:90%


00:31:35.050 --> 00:31:36.955 align:middle line:90%
And let's reset this.

00:31:36.955 --> 00:31:48.220 align:middle line:90%


00:31:48.220 --> 00:31:52.530 align:middle line:84%
And go to translation
pattern now.

00:31:52.530 --> 00:31:54.870 align:middle line:84%
And create another
translation pattern,

00:31:54.870 --> 00:31:58.410 align:middle line:84%
which only my SIP trunk has
access to, not my phones.

00:31:58.410 --> 00:32:00.060 align:middle line:90%
This is inbound.

00:32:00.060 --> 00:32:03.330 align:middle line:84%
So I will create a new
translation pattern,

00:32:03.330 --> 00:32:05.040 align:middle line:90%
which would be for my phone.

00:32:05.040 --> 00:32:07.740 align:middle line:84%
What's my called number
coming from side B?

00:32:07.740 --> 00:32:12.690 align:middle line:84%
Side B is going
to send 82022XXX.

00:32:12.690 --> 00:32:16.980 align:middle line:90%
So 8202.2XXX.

00:32:16.980 --> 00:32:20.670 align:middle line:84%
And this would go inside
PT-INBOUND-FROM-SME.

00:32:20.670 --> 00:32:22.710 align:middle line:84%
Calling search space
here would be none

00:32:22.710 --> 00:32:25.170 align:middle line:84%
because he doesn't need
access to anything.

00:32:25.170 --> 00:32:29.790 align:middle line:84%
He just needs access to PT-NONE
because my phone's directory is

00:32:29.790 --> 00:32:30.510 align:middle line:90%
in the PT-NONE.

00:32:30.510 --> 00:32:32.650 align:middle line:84%
There's no partition
applied to my directories.

00:32:32.650 --> 00:32:35.790 align:middle line:84%
So he only has
access to CSS-NONE.

00:32:35.790 --> 00:32:37.680 align:middle line:84%
So he would have
access to the phone.

00:32:37.680 --> 00:32:40.500 align:middle line:90%
And all I'm going to do here--

00:32:40.500 --> 00:32:42.990 align:middle line:84%
I can remove the
outside dial tone.

00:32:42.990 --> 00:32:44.970 align:middle line:84%
All I'm going to do
here is do a PreDot.

00:32:44.970 --> 00:32:51.450 align:middle line:90%


00:32:51.450 --> 00:32:53.040 align:middle line:90%
So what really happens here now?

00:32:53.040 --> 00:32:55.620 align:middle line:84%
When the call comes
in from SME, it

00:32:55.620 --> 00:32:58.320 align:middle line:84%
is coming as eight digits
as the called number.

00:32:58.320 --> 00:33:02.430 align:middle line:84%
The pub is going to check
the inbound CSS, which

00:33:02.430 --> 00:33:05.400 align:middle line:84%
has access to this
translation pattern, which

00:33:05.400 --> 00:33:10.470 align:middle line:84%
says if the called number
is 82022XXX, strip the 8202,

00:33:10.470 --> 00:33:12.660 align:middle line:84%
which means my called
number becomes four digits,

00:33:12.660 --> 00:33:15.930 align:middle line:90%
2001 or 2002 or 2003.

00:33:15.930 --> 00:33:21.360 align:middle line:84%
And it forwards to
wherever the phone is.

00:33:21.360 --> 00:33:23.190 align:middle line:90%
The phone is going to match.

00:33:23.190 --> 00:33:25.410 align:middle line:84%
The extension is going to
match because the phone is

00:33:25.410 --> 00:33:28.290 align:middle line:84%
inside the PT-NONE and
the translation pattern

00:33:28.290 --> 00:33:29.460 align:middle line:90%
has CSS-NONE.

00:33:29.460 --> 00:33:32.310 align:middle line:90%
So it has access to PT-NONE.

00:33:32.310 --> 00:33:33.030 align:middle line:90%
Let's save this.

00:33:33.030 --> 00:33:36.450 align:middle line:90%


00:33:36.450 --> 00:33:40.670 align:middle line:84%
Let's do exactly the same
thing on side B. So on side B,

00:33:40.670 --> 00:33:43.100 align:middle line:90%
I will first create a SIP trunk.

00:33:43.100 --> 00:34:03.420 align:middle line:90%


00:34:03.420 --> 00:34:05.030 align:middle line:90%
So SIP-TRUNK-TO-SME.

00:34:05.030 --> 00:34:11.690 align:middle line:84%
Device pool is the default.
Let's do apply to all nodes.

00:34:11.690 --> 00:34:14.060 align:middle line:84%
And inbound calling
search space is

00:34:14.060 --> 00:34:17.250 align:middle line:90%
going to be inbound from SME.

00:34:17.250 --> 00:34:21.570 align:middle line:84%
And in the outbound, this time,
I will not do anything here.

00:34:21.570 --> 00:34:23.429 align:middle line:84%
I will do it inside
the device pool.

00:34:23.429 --> 00:34:27.300 align:middle line:90%
So let's put the SME's address.

00:34:27.300 --> 00:34:28.889 align:middle line:90%
hq-ucm-sme.ine.com.

00:34:28.889 --> 00:34:31.409 align:middle line:90%


00:34:31.409 --> 00:34:34.440 align:middle line:84%
And SIP trunk profile is going
to be the non-secure one.

00:34:34.440 --> 00:34:36.510 align:middle line:84%
The SIP profile is going
to be the standard.

00:34:36.510 --> 00:34:37.710 align:middle line:90%
And save.

00:34:37.710 --> 00:34:42.750 align:middle line:84%
So notice I did not apply the
called party transformation

00:34:42.750 --> 00:34:44.520 align:middle line:90%
inside the SIP trunk.

00:34:44.520 --> 00:34:49.940 align:middle line:84%
I kept the checkbox enabled
for use device pool.

00:34:49.940 --> 00:34:52.060 align:middle line:84%
So for the plus
to be stripped off

00:34:52.060 --> 00:34:54.909 align:middle line:84%
when it's going
towards the SME, it's

00:34:54.909 --> 00:34:56.570 align:middle line:90%
not going to happen right now.

00:34:56.570 --> 00:34:59.320 align:middle line:84%
So I need to go
to my device pool

00:34:59.320 --> 00:35:05.190 align:middle line:84%
and apply the called party
transformation, which

00:35:05.190 --> 00:35:07.920 align:middle line:84%
you can see here
in the outbound,

00:35:07.920 --> 00:35:13.200 align:middle line:84%
I did not apply the called
party called xform CSS.

00:35:13.200 --> 00:35:14.380 align:middle line:90%
I'm using the device pool.

00:35:14.380 --> 00:35:16.620 align:middle line:90%
So let's go to device pool.

00:35:16.620 --> 00:35:19.090 align:middle line:90%
So system, device pool.

00:35:19.090 --> 00:35:22.900 align:middle line:90%


00:35:22.900 --> 00:35:23.750 align:middle line:90%
Let's do Find.

00:35:23.750 --> 00:35:28.190 align:middle line:90%


00:35:28.190 --> 00:35:30.365 align:middle line:90%
And choose the default one.

00:35:30.365 --> 00:35:33.340 align:middle line:90%


00:35:33.340 --> 00:35:39.610 align:middle line:84%
And here, under called
party transformation CSS,

00:35:39.610 --> 00:35:42.090 align:middle line:84%
I will go and apply
my called xform.

00:35:42.090 --> 00:35:48.440 align:middle line:90%


00:35:48.440 --> 00:35:50.135 align:middle line:90%
Let's apply and reset.

00:35:50.135 --> 00:35:59.010 align:middle line:90%


00:35:59.010 --> 00:36:03.450 align:middle line:84%
Next thing what we would do is
create because the SIP trunk

00:36:03.450 --> 00:36:07.920 align:middle line:84%
inbound calls has the
CSS-INBOUND-FROM-SME.

00:36:07.920 --> 00:36:10.710 align:middle line:84%
I need to create a translation
pattern which strips off

00:36:10.710 --> 00:36:13.410 align:middle line:84%
the called ID number from
eight digits to four digits

00:36:13.410 --> 00:36:16.030 align:middle line:84%
because my extensions
are four digits.

00:36:16.030 --> 00:36:21.360 align:middle line:84%
So let's do a Find and create
a new translation pattern

00:36:21.360 --> 00:36:29.260 align:middle line:84%
for my local number,
which is 8303.3XXX.

00:36:29.260 --> 00:36:32.650 align:middle line:84%
This would go into the
partition inbound from SME.

00:36:32.650 --> 00:36:34.690 align:middle line:90%
Let's remove this.

00:36:34.690 --> 00:36:36.640 align:middle line:90%
And no changes in the calling.

00:36:36.640 --> 00:36:40.291 align:middle line:84%
Called becomes four
digits with the PreDot.

00:36:40.291 --> 00:36:41.140 align:middle line:90%
And save.

00:36:41.140 --> 00:36:46.910 align:middle line:90%


00:36:46.910 --> 00:36:49.650 align:middle line:84%
Once you've done this,
SIP trunk is done.

00:36:49.650 --> 00:36:52.160 align:middle line:84%
Now the only thing we
need on HQ and side B

00:36:52.160 --> 00:36:54.660 align:middle line:84%
is to create a route
list and a route group.

00:36:54.660 --> 00:36:56.540 align:middle line:84%
Now, because my
question does not really

00:36:56.540 --> 00:37:02.940 align:middle line:84%
hint at anything towards your
standard local route group,

00:37:02.940 --> 00:37:07.685 align:middle line:84%
so I would directly call my SIP
gateway inside my route list.

00:37:07.685 --> 00:37:10.340 align:middle line:90%


00:37:10.340 --> 00:37:11.550 align:middle line:90%
I'm on side B right now.

00:37:11.550 --> 00:37:15.200 align:middle line:84%
So let's go to
route group first.

00:37:15.200 --> 00:37:16.235 align:middle line:90%
Create a route group.

00:37:16.235 --> 00:37:20.090 align:middle line:90%


00:37:20.090 --> 00:37:23.930 align:middle line:84%
And as for the question,
the name was RG-SME.

00:37:23.930 --> 00:37:26.060 align:middle line:84%
And this would contain
the SIP-TRUNK-TO-SME.

00:37:26.060 --> 00:37:30.790 align:middle line:90%


00:37:30.790 --> 00:37:31.690 align:middle line:90%
And save.

00:37:31.690 --> 00:37:34.530 align:middle line:90%


00:37:34.530 --> 00:37:36.750 align:middle line:90%
Let's do the same thing on HQ.

00:37:36.750 --> 00:37:38.025 align:middle line:90%
Create a route group.

00:37:38.025 --> 00:37:50.750 align:middle line:90%


00:37:50.750 --> 00:37:53.030 align:middle line:90%
RG-SME.

00:37:53.030 --> 00:37:54.965 align:middle line:84%
This would contain
the SIP-TRUNK-TO-SME.

00:37:54.965 --> 00:38:04.360 align:middle line:90%


00:38:04.360 --> 00:38:06.600 align:middle line:90%
So SIP-TRUNK-TO-SME and save.

00:38:06.600 --> 00:38:11.380 align:middle line:90%


00:38:11.380 --> 00:38:13.045 align:middle line:90%
Next, I create a route list.

00:38:13.045 --> 00:38:24.280 align:middle line:90%


00:38:24.280 --> 00:38:28.260 align:middle line:84%
So route list SME
as per the question.

00:38:28.260 --> 00:38:31.470 align:middle line:84%
This would contain
default. Let's save this.

00:38:31.470 --> 00:38:35.220 align:middle line:84%
And this would directly
call the route group

00:38:35.220 --> 00:38:37.240 align:middle line:90%
which contains the SIP trunk.

00:38:37.240 --> 00:38:39.660 align:middle line:90%
So here, instead of me--

00:38:39.660 --> 00:38:42.000 align:middle line:84%
first of all, let's enable
Run on All Active Nodes.

00:38:42.000 --> 00:38:44.020 align:middle line:84%
That's something
that you should do.

00:38:44.020 --> 00:38:47.735 align:middle line:90%
And then go to Add Route Group.

00:38:47.735 --> 00:38:49.360 align:middle line:84%
So because the question
does not really

00:38:49.360 --> 00:38:52.210 align:middle line:84%
hint at anything about
standard local route group,

00:38:52.210 --> 00:38:54.050 align:middle line:84%
this basically
means that instead

00:38:54.050 --> 00:38:56.740 align:middle line:84%
of you specifying the
gateway directly here,

00:38:56.740 --> 00:38:59.650 align:middle line:84%
you are going to go
back to the device pool

00:38:59.650 --> 00:39:01.962 align:middle line:90%
to check the local route group.

00:39:01.962 --> 00:39:04.420 align:middle line:84%
Since the question does not
really say anything about that,

00:39:04.420 --> 00:39:09.190 align:middle line:84%
I'm going to use the route group
inside the route list directly.

00:39:09.190 --> 00:39:10.330 align:middle line:90%
And let's save.

00:39:10.330 --> 00:39:12.010 align:middle line:84%
There's no changes
here in the calling,

00:39:12.010 --> 00:39:13.840 align:middle line:84%
called because all
the changes, we've

00:39:13.840 --> 00:39:16.150 align:middle line:84%
done in the translation
pattern and the SIP trunk.

00:39:16.150 --> 00:39:26.170 align:middle line:90%


00:39:26.170 --> 00:39:29.995 align:middle line:84%
Make sure you enable this Run
on All Active Nodes and save.

00:39:29.995 --> 00:39:36.470 align:middle line:90%


00:39:36.470 --> 00:39:39.230 align:middle line:84%
Let's go to side B and do
exactly the same thing.

00:39:39.230 --> 00:39:42.190 align:middle line:90%
So on side B, under Route List.

00:39:42.190 --> 00:39:48.010 align:middle line:90%


00:39:48.010 --> 00:39:49.330 align:middle line:90%
Create a route list.

00:39:49.330 --> 00:39:51.010 align:middle line:90%
We have no route list right now.

00:39:51.010 --> 00:39:55.200 align:middle line:90%


00:39:55.200 --> 00:39:59.010 align:middle line:90%
So route list dash SME.

00:39:59.010 --> 00:40:00.240 align:middle line:90%
Default. Save.

00:40:00.240 --> 00:40:04.470 align:middle line:90%


00:40:04.470 --> 00:40:07.690 align:middle line:90%
Add Route Group.

00:40:07.690 --> 00:40:09.665 align:middle line:90%
This would be the route group.

00:40:09.665 --> 00:40:10.165 align:middle line:90%
Save.

00:40:10.165 --> 00:40:17.630 align:middle line:90%


00:40:17.630 --> 00:40:20.420 align:middle line:84%
And then Run on
All Active Nodes.

00:40:20.420 --> 00:40:23.370 align:middle line:90%
Have the habit of doing that.

00:40:23.370 --> 00:40:24.270 align:middle line:90%
Next thing.

00:40:24.270 --> 00:40:27.060 align:middle line:84%
The last thing that I
do on my HQ and side B

00:40:27.060 --> 00:40:29.565 align:middle line:84%
is create the route pattern,
the single route pattern.

00:40:29.565 --> 00:40:34.750 align:middle line:90%


00:40:34.750 --> 00:40:36.752 align:middle line:84%
So there are no route
patterns right now,

00:40:36.752 --> 00:40:37.710 align:middle line:90%
which you can see here.

00:40:37.710 --> 00:40:40.470 align:middle line:90%
Same thing on HQ.

00:40:40.470 --> 00:40:43.230 align:middle line:84%
If I look at route
pattern, there

00:40:43.230 --> 00:40:48.450 align:middle line:84%
are no route
patterns on HQ also.

00:40:48.450 --> 00:40:57.370 align:middle line:84%
So on side B, I would go
and say backslash plus bang.

00:40:57.370 --> 00:41:01.840 align:middle line:84%
This goes inside the partition
single route pattern.

00:41:01.840 --> 00:41:07.630 align:middle line:84%
And the gateway is
going to be the RL-SME.

00:41:07.630 --> 00:41:10.620 align:middle line:90%
So don't apply the SIP trunk.

00:41:10.620 --> 00:41:13.120 align:middle line:84%
The SIP trunk cannot be applied
directly because now the SIP

00:41:13.120 --> 00:41:15.250 align:middle line:84%
trunk is inside the route
group, and route group is inside

00:41:15.250 --> 00:41:15.875 align:middle line:90%
the route list.

00:41:15.875 --> 00:41:18.780 align:middle line:90%
So apply your route list.

00:41:18.780 --> 00:41:21.090 align:middle line:90%
And let's save this.

00:41:21.090 --> 00:41:27.710 align:middle line:90%


00:41:27.710 --> 00:41:30.005 align:middle line:84%
Let's do exactly the
same thing on HQ.

00:41:30.005 --> 00:41:38.130 align:middle line:90%


00:41:38.130 --> 00:41:41.100 align:middle line:90%
So backslash plus bang.

00:41:41.100 --> 00:41:45.480 align:middle line:84%
This goes inside the
single route pattern.

00:41:45.480 --> 00:41:47.580 align:middle line:90%
Gateway would be the route list.

00:41:47.580 --> 00:41:51.290 align:middle line:90%
And let's save this.

00:41:51.290 --> 00:41:53.980 align:middle line:90%
So HQ and side B clusters done.

00:41:53.980 --> 00:41:56.210 align:middle line:84%
So so far, what's
going to happen?

00:41:56.210 --> 00:41:58.420 align:middle line:84%
Let's talk about from
HQ calling side B.

00:41:58.420 --> 00:42:00.160 align:middle line:84%
I haven't still
configured the SME.

00:42:00.160 --> 00:42:02.000 align:middle line:90%
So my call is not going to work.

00:42:02.000 --> 00:42:07.810 align:middle line:84%
But from the visual perspective,
when HQ is dialing side B,

00:42:07.810 --> 00:42:09.880 align:middle line:90%
what's going to happen now?

00:42:09.880 --> 00:42:15.130 align:middle line:84%
Phone calling number is four
digits, 2003, Tony Stark,

00:42:15.130 --> 00:42:20.110 align:middle line:84%
dialing side B. But he will
not dial side B's Steve Rogers

00:42:20.110 --> 00:42:21.520 align:middle line:90%
extension, 3003.

00:42:21.520 --> 00:42:27.070 align:middle line:90%
He's going to dial 83033003.

00:42:27.070 --> 00:42:28.900 align:middle line:90%
So he dials that.

00:42:28.900 --> 00:42:32.020 align:middle line:84%
From the phone to
the publisher of HQ,

00:42:32.020 --> 00:42:34.300 align:middle line:84%
the calling number
is four digits,

00:42:34.300 --> 00:42:37.450 align:middle line:90%
called number is eight digits.

00:42:37.450 --> 00:42:40.630 align:middle line:84%
It hits the translation pattern
because the phone CSS has

00:42:40.630 --> 00:42:43.840 align:middle line:84%
CSS-PHONES which contains
the PT-INTERSITE,

00:42:43.840 --> 00:42:46.300 align:middle line:90%
it hits the translation pattern.

00:42:46.300 --> 00:42:50.980 align:middle line:84%
The translation pattern changes
the calling number to E164

00:42:50.980 --> 00:42:58.090 align:middle line:84%
and the called number to
+83033003 and hits the route

00:42:58.090 --> 00:42:59.170 align:middle line:90%
pattern.

00:42:59.170 --> 00:43:03.140 align:middle line:84%
The route pattern
forwards to the routeless.

00:43:03.140 --> 00:43:04.640 align:middle line:90%
Routeless has the route group.

00:43:04.640 --> 00:43:06.350 align:middle line:90%
Route group has the SIP trunk.

00:43:06.350 --> 00:43:08.210 align:middle line:90%
It goes to the SIP trunk.

00:43:08.210 --> 00:43:12.570 align:middle line:84%
The SIP trunk in the
outbound called party CSS,

00:43:12.570 --> 00:43:14.810 align:middle line:84%
which we've applied,
the SIP trunk

00:43:14.810 --> 00:43:17.720 align:middle line:84%
when it's sending the call
out to SME, the calling

00:43:17.720 --> 00:43:20.990 align:middle line:84%
number will still remain
the same, which is E164.

00:43:20.990 --> 00:43:24.140 align:middle line:84%
The called ID number
will strip off the plus

00:43:24.140 --> 00:43:26.540 align:middle line:84%
and send eight
digits to SME, which

00:43:26.540 --> 00:43:30.680 align:middle line:84%
means the SME is going to
get E164 as the calling,

00:43:30.680 --> 00:43:35.960 align:middle line:84%
and called number
would be 83033003.

00:43:35.960 --> 00:43:38.180 align:middle line:84%
Same thing is going to
happen in reverse way.

00:43:38.180 --> 00:43:46.010 align:middle line:84%
When side B is calling HQ, he is
dialing eight digits, 82022XXX.

00:43:46.010 --> 00:43:48.470 align:middle line:84%
It goes to the
translation pattern.

00:43:48.470 --> 00:43:50.240 align:middle line:90%
Calling becomes E164.

00:43:50.240 --> 00:43:55.100 align:middle line:90%
Called becomes +82022XXX.

00:43:55.100 --> 00:43:57.650 align:middle line:84%
From the translation pattern,
goes to route pattern,

00:43:57.650 --> 00:44:00.740 align:middle line:84%
hits the backslash plus
bang, goes to SIP trunk,

00:44:00.740 --> 00:44:03.920 align:middle line:84%
SIP trunk strips off the
plus from the called number,

00:44:03.920 --> 00:44:07.400 align:middle line:84%
and the SME gets
calling number as E164

00:44:07.400 --> 00:44:11.150 align:middle line:90%
and called number as 82022XXX.

00:44:11.150 --> 00:44:13.340 align:middle line:90%
So eight digits.

00:44:13.340 --> 00:44:15.420 align:middle line:84%
Now we have to
configure the SME.

00:44:15.420 --> 00:44:18.660 align:middle line:90%
So let's go to SME.

00:44:18.660 --> 00:44:20.130 align:middle line:90%
And let's log in.

00:44:20.130 --> 00:44:22.810 align:middle line:90%
Administrator.

00:44:22.810 --> 00:44:28.030 align:middle line:90%
C1sc0123!.

00:44:28.030 --> 00:44:30.940 align:middle line:84%
The first thing on SME
that we would have to do.

00:44:30.940 --> 00:44:34.010 align:middle line:84%
Since my SIP trunk
is using the FQDN,

00:44:34.010 --> 00:44:40.540 align:middle line:84%
which is hq-ucm-sme.ine.com,
I must first go and check

00:44:40.540 --> 00:44:50.120 align:middle line:84%
on the SME if the server
name is the FQDN correctly

00:44:50.120 --> 00:44:54.605 align:middle line:84%
because sometimes you may have
the server name as an incorrect

00:44:54.605 --> 00:44:56.370 align:middle line:90%
FQDN in the lab exam.

00:44:56.370 --> 00:44:59.410 align:middle line:90%
So be careful with that.

00:44:59.410 --> 00:45:03.390 align:middle line:84%
So either you put the IP address
there, or you put the FQDN.

00:45:03.390 --> 00:45:06.270 align:middle line:84%
If you're putting the FQDN,
make sure it's resolvable.

00:45:06.270 --> 00:45:16.070 align:middle line:84%
So if I do a Find on the SME
and check, I see hq-cucm-sme.

00:45:16.070 --> 00:45:18.380 align:middle line:90%
But I don't see .ine.com.

00:45:18.380 --> 00:45:19.430 align:middle line:90%
So I'm going to add that.

00:45:19.430 --> 00:45:22.310 align:middle line:84%
Otherwise, my call is going to
fail because this address is

00:45:22.310 --> 00:45:23.540 align:middle line:90%
not going to resolve.

00:45:23.540 --> 00:45:26.300 align:middle line:90%
So .ine.com.

00:45:26.300 --> 00:45:27.050 align:middle line:90%
Let's save this.

00:45:27.050 --> 00:45:32.920 align:middle line:90%


00:45:32.920 --> 00:45:36.280 align:middle line:84%
Now, what does the
question state about SME?

00:45:36.280 --> 00:45:41.620 align:middle line:84%
The question states, SME,
when he gets the call from HQ,

00:45:41.620 --> 00:45:45.850 align:middle line:84%
he should change the calling
number to eight digits,

00:45:45.850 --> 00:45:48.040 align:middle line:90%
from E164 to eight digits.

00:45:48.040 --> 00:45:50.300 align:middle line:90%
Called number is unchanged.

00:45:50.300 --> 00:45:52.150 align:middle line:84%
So he's not changing
the called number.

00:45:52.150 --> 00:45:56.250 align:middle line:84%
He's only changing
the calling number.

00:45:56.250 --> 00:45:57.890 align:middle line:90%
So I'm going to go back.

00:45:57.890 --> 00:45:59.180 align:middle line:90%
And same thing reverse way.

00:45:59.180 --> 00:46:01.880 align:middle line:84%
When side B is
calling to HQ, SME

00:46:01.880 --> 00:46:05.600 align:middle line:84%
would send to HQ eight
digits as the calling number

00:46:05.600 --> 00:46:08.130 align:middle line:84%
and called would
remain unchanged.

00:46:08.130 --> 00:46:10.310 align:middle line:84%
So the only calling
part we have to change

00:46:10.310 --> 00:46:13.110 align:middle line:90%
from E164 to eight digits.

00:46:13.110 --> 00:46:15.060 align:middle line:90%
Let's go back.

00:46:15.060 --> 00:46:17.600 align:middle line:84%
And on the SME, first
thing I would do

00:46:17.600 --> 00:46:20.220 align:middle line:90%
is create two partitions.

00:46:20.220 --> 00:46:29.550 align:middle line:90%


00:46:29.550 --> 00:46:39.620 align:middle line:84%
Let's name this partition HQ
and partition side B. Next,

00:46:39.620 --> 00:46:45.220 align:middle line:84%
I will create two CSS,
one for each partition.

00:46:45.220 --> 00:46:52.950 align:middle line:90%


00:46:52.950 --> 00:47:01.830 align:middle line:84%
Let's name this as CSS
inbound from side B.

00:47:01.830 --> 00:47:04.260 align:middle line:84%
So when I'm getting
the call from side B,

00:47:04.260 --> 00:47:08.160 align:middle line:84%
he needs access to the partition
of HQ to go towards HQ.

00:47:08.160 --> 00:47:10.620 align:middle line:90%
So this would contain HQ.

00:47:10.620 --> 00:47:13.365 align:middle line:84%
So inbound from
side B contains HQ.

00:47:13.365 --> 00:47:17.950 align:middle line:90%


00:47:17.950 --> 00:47:21.010 align:middle line:84%
Let's create one more CSS,
which is inbound from HQ.

00:47:21.010 --> 00:47:23.830 align:middle line:90%


00:47:23.830 --> 00:47:33.610 align:middle line:84%
So CSS-INBOUND-FROM-HQ needs
access to partition side B.

00:47:33.610 --> 00:47:36.420 align:middle line:90%
Let's save this.

00:47:36.420 --> 00:47:40.980 align:middle line:84%
Now let's create two
translation patterns,

00:47:40.980 --> 00:47:43.110 align:middle line:84%
or maybe we can directly
create a route pattern.

00:47:43.110 --> 00:47:45.690 align:middle line:84%
There is no limitation of
creating a route pattern

00:47:45.690 --> 00:47:46.650 align:middle line:90%
on SME.

00:47:46.650 --> 00:47:48.690 align:middle line:84%
If you look at the
question, question states

00:47:48.690 --> 00:47:51.480 align:middle line:84%
that we can only have one
route pattern on HQ, which

00:47:51.480 --> 00:47:54.792 align:middle line:84%
is backslash plus bang, and
one route pattern on side B.

00:47:54.792 --> 00:47:56.250 align:middle line:84%
It does not say
anything about SME.

00:47:56.250 --> 00:47:58.720 align:middle line:84%
So on SME, I can create
multiple route patterns.

00:47:58.720 --> 00:48:02.460 align:middle line:84%
So what I'll do first
is I will create a SIP

00:48:02.460 --> 00:48:07.730 align:middle line:84%
trunk to HQ and SIP trunk to
side B. Let's create that.

00:48:07.730 --> 00:48:09.920 align:middle line:84%
I don't need to create
route groups or route list

00:48:09.920 --> 00:48:12.860 align:middle line:84%
on SME because the question
does not state that.

00:48:12.860 --> 00:48:14.525 align:middle line:90%
I can create if I want to.

00:48:14.525 --> 00:48:16.610 align:middle line:90%
You will not lose points.

00:48:16.610 --> 00:48:18.230 align:middle line:90%
But I don't need to.

00:48:18.230 --> 00:48:20.240 align:middle line:90%
So why waste time on that?

00:48:20.240 --> 00:48:23.920 align:middle line:90%
Let's create a SIP trunk.

00:48:23.920 --> 00:48:26.325 align:middle line:84%
So two SIP trunks
I need on my SME.

00:48:26.325 --> 00:48:29.490 align:middle line:90%


00:48:29.490 --> 00:48:32.610 align:middle line:90%
Let's name this as SIP-TRUNK-HQ.

00:48:32.610 --> 00:48:41.250 align:middle line:90%


00:48:41.250 --> 00:48:45.030 align:middle line:84%
And here, again, let's do
Run on All Active Nodes.

00:48:45.030 --> 00:48:51.180 align:middle line:84%
Here, in the inbound calls,
when he gets the call from HQ,

00:48:51.180 --> 00:48:54.435 align:middle line:84%
he needs access to
inbound from HQ.

00:48:54.435 --> 00:48:56.310 align:middle line:84%
So when the call comes
from HQ-- because this

00:48:56.310 --> 00:48:58.140 align:middle line:90%
is a SIP trunk towards HQ.

00:48:58.140 --> 00:49:00.510 align:middle line:90%
This is a SIP trunk for HQ.

00:49:00.510 --> 00:49:03.300 align:middle line:84%
So when the call comes
from HQ, he needs access

00:49:03.300 --> 00:49:07.350 align:middle line:84%
to CSS-INBOUND-FROM-HQ, which
contains the partition side B.

00:49:07.350 --> 00:49:10.050 align:middle line:90%
So the call can go to side B.

00:49:10.050 --> 00:49:23.630 align:middle line:84%
And let's put the destination
address as hq-cucm.ine.com.

00:49:23.630 --> 00:49:27.690 align:middle line:90%


00:49:27.690 --> 00:49:31.140 align:middle line:84%
And this is going to
be the default ones.

00:49:31.140 --> 00:49:32.490 align:middle line:90%
And let's save this.

00:49:32.490 --> 00:49:43.750 align:middle line:90%


00:49:43.750 --> 00:49:46.140 align:middle line:90%
Let's reset this.

00:49:46.140 --> 00:49:50.860 align:middle line:84%
Always good to reset them
once you create them.

00:49:50.860 --> 00:49:53.250 align:middle line:84%
Let's add one more SIP
trunk to side B now.

00:49:53.250 --> 00:50:02.870 align:middle line:90%


00:50:02.870 --> 00:50:10.600 align:middle line:84%
SIP trunk side B.
Default device pool.

00:50:10.600 --> 00:50:15.760 align:middle line:90%
And Run on All Active Nodes.

00:50:15.760 --> 00:50:18.370 align:middle line:84%
And on the inbound,
he has access to--

00:50:18.370 --> 00:50:20.860 align:middle line:84%
when the call comes
from side B, he

00:50:20.860 --> 00:50:24.160 align:middle line:84%
will have access
to partition HQ.

00:50:24.160 --> 00:50:28.105 align:middle line:84%
And let's go down
here and add the FQDN

00:50:28.105 --> 00:50:31.300 align:middle line:90%
for side B, which is hq dash--

00:50:31.300 --> 00:50:36.670 align:middle line:84%
or, in fact, it side B
dash cucm dot ine.com.

00:50:36.670 --> 00:50:39.610 align:middle line:84%
And the default SIP
trunk security profile.

00:50:39.610 --> 00:50:42.100 align:middle line:90%
Default SIP profile.

00:50:42.100 --> 00:50:43.120 align:middle line:90%
And save.

00:50:43.120 --> 00:50:45.920 align:middle line:90%
And let's reset that.

00:50:45.920 --> 00:50:48.650 align:middle line:84%
Now the only thing I need
is route patterns, two route

00:50:48.650 --> 00:50:49.160 align:middle line:90%
patterns.

00:50:49.160 --> 00:50:55.935 align:middle line:84%
One to go to HQ, one to go
to side B. Let's reset this.

00:50:55.935 --> 00:51:02.580 align:middle line:90%


00:51:02.580 --> 00:51:10.730 align:middle line:84%
So go back to call
routing and go

00:51:10.730 --> 00:51:13.790 align:middle line:90%
to Route/Hunt, Route Pattern.

00:51:13.790 --> 00:51:17.650 align:middle line:90%


00:51:17.650 --> 00:51:21.790 align:middle line:84%
Create a route pattern
for going towards HQ.

00:51:21.790 --> 00:51:23.290 align:middle line:90%
That's going to be--

00:51:23.290 --> 00:51:26.220 align:middle line:90%
so how is the call coming in?

00:51:26.220 --> 00:51:30.360 align:middle line:84%
If you see here, the call
coming in going towards side B

00:51:30.360 --> 00:51:31.620 align:middle line:90%
is eight digits.

00:51:31.620 --> 00:51:35.020 align:middle line:84%
And, again, the call going
towards HQ is eight digits.

00:51:35.020 --> 00:51:39.190 align:middle line:84%
So here, I'm going
to put if the call is

00:51:39.190 --> 00:51:49.590 align:middle line:84%
going to HQ, which is 82022XXX,
this goes in the partition HQ.

00:51:49.590 --> 00:51:52.960 align:middle line:90%


00:51:52.960 --> 00:51:55.000 align:middle line:90%
Gateway is going to be HQ.

00:51:55.000 --> 00:51:55.990 align:middle line:90%
Go towards HQ.

00:51:55.990 --> 00:51:59.090 align:middle line:90%


00:51:59.090 --> 00:52:07.760 align:middle line:84%
Change the calling number from
E164 to eight digits, 83033XXX.

00:52:07.760 --> 00:52:10.610 align:middle line:84%
So this is side
B's calling number

00:52:10.610 --> 00:52:13.970 align:middle line:84%
because side B was
sending E164 number.

00:52:13.970 --> 00:52:20.000 align:middle line:84%
I'm replacing that with side B's
calling number as eight digits.

00:52:20.000 --> 00:52:21.440 align:middle line:90%
Called number remains the same.

00:52:21.440 --> 00:52:22.815 align:middle line:84%
Everything else
remains the same.

00:52:22.815 --> 00:52:24.860 align:middle line:90%
Let's save this.

00:52:24.860 --> 00:52:28.190 align:middle line:84%
Now, who has access
to this route pattern?

00:52:28.190 --> 00:52:33.170 align:middle line:84%
When the call comes from side B,
it hits the SIP trunk of side B

00:52:33.170 --> 00:52:37.130 align:middle line:84%
on that inbound CSS,
has inbound from side B,

00:52:37.130 --> 00:52:40.160 align:middle line:90%
has access to partition HQ.

00:52:40.160 --> 00:52:43.520 align:middle line:84%
And that would match
this route pattern

00:52:43.520 --> 00:52:49.400 align:middle line:84%
which says that forward it to
HQ SIP trunk, change the calling

00:52:49.400 --> 00:52:52.520 align:middle line:84%
number to eight digits,
which you can see here.

00:52:52.520 --> 00:52:54.980 align:middle line:90%
Called, nothing has changed.

00:52:54.980 --> 00:52:58.980 align:middle line:84%
Let's add one more which
is going towards side B.

00:52:58.980 --> 00:53:05.220 align:middle line:84%
So 83033XXX, this would go
into the partition of side

00:53:05.220 --> 00:53:07.680 align:middle line:84%
B. Who has access
to this partition?

00:53:07.680 --> 00:53:10.170 align:middle line:90%
Inbound from HQ.

00:53:10.170 --> 00:53:14.270 align:middle line:84%
And this would go to
SIP trunk of side B.

00:53:14.270 --> 00:53:18.320 align:middle line:84%
And calling number would change
to eight digits of HQ, which

00:53:18.320 --> 00:53:21.950 align:middle line:90%
is 82022XXX.

00:53:21.950 --> 00:53:22.730 align:middle line:90%
And save.

00:53:22.730 --> 00:53:31.290 align:middle line:90%


00:53:31.290 --> 00:53:32.520 align:middle line:90%
So eight digits.

00:53:32.520 --> 00:53:36.210 align:middle line:84%
8303 is what I'm
dialing, called number.

00:53:36.210 --> 00:53:39.930 align:middle line:84%
And calling is changing to
8202 because this was coming

00:53:39.930 --> 00:53:43.080 align:middle line:90%
from HQ publisher as E164.

00:53:43.080 --> 00:53:47.220 align:middle line:84%
I'm replacing that with eight
digits as the calling number.

00:53:47.220 --> 00:53:48.100 align:middle line:90%
That's it.

00:53:48.100 --> 00:53:49.350 align:middle line:90%
That's all we need.

00:53:49.350 --> 00:53:50.590 align:middle line:90%
And I think we're done.

00:53:50.590 --> 00:53:53.490 align:middle line:84%
We should be able
to test this now.

00:53:53.490 --> 00:53:55.680 align:middle line:90%
Let's go to my--

00:53:55.680 --> 00:53:57.000 align:middle line:90%
so I'm on Jabber1.

00:53:57.000 --> 00:53:58.350 align:middle line:90%
Let's log in with Tony Stark.

00:53:58.350 --> 00:54:02.670 align:middle line:90%


00:54:02.670 --> 00:54:05.385 align:middle line:84%
Let's try making the call
and see if this works.

00:54:05.385 --> 00:54:10.920 align:middle line:90%


00:54:10.920 --> 00:54:15.185 align:middle line:84%
I will also go to Jabber2
and log in with Steve Rogers.

00:54:15.185 --> 00:54:22.120 align:middle line:90%


00:54:22.120 --> 00:54:24.430 align:middle line:90%
Just say OK for this error.

00:54:24.430 --> 00:54:26.200 align:middle line:84%
So I'm logged in
with Tony Stark.

00:54:26.200 --> 00:54:36.550 align:middle line:90%


00:54:36.550 --> 00:54:39.910 align:middle line:84%
And let's log in here
with Steve Rogers.

00:54:39.910 --> 00:54:41.941 align:middle line:90%
It should log in automatically.

00:54:41.941 --> 00:54:45.240 align:middle line:90%


00:54:45.240 --> 00:54:48.645 align:middle line:84%
Give it some time for the
phone to basically register.

00:54:48.645 --> 00:54:53.980 align:middle line:90%


00:54:53.980 --> 00:54:56.890 align:middle line:90%
So now Tony Stark is ready.

00:54:56.890 --> 00:54:58.230 align:middle line:90%
Let's look at Steve Rogers.

00:54:58.230 --> 00:54:59.115 align:middle line:90%
Accept this.

00:54:59.115 --> 00:55:04.550 align:middle line:90%


00:55:04.550 --> 00:55:07.970 align:middle line:84%
Give it again some time
for the phone to show up,

00:55:07.970 --> 00:55:09.200 align:middle line:90%
for the line to show up.

00:55:09.200 --> 00:55:17.740 align:middle line:90%


00:55:17.740 --> 00:55:21.600 align:middle line:84%
Now, my extension for Steve
Rogers is four digits, 3003.

00:55:21.600 --> 00:55:24.280 align:middle line:90%
But the call should work.

00:55:24.280 --> 00:55:25.030 align:middle line:90%
Let's check.

00:55:25.030 --> 00:55:26.310 align:middle line:90%
Let's give it some more time.

00:55:26.310 --> 00:55:27.840 align:middle line:90%
It's still registering.

00:55:27.840 --> 00:55:31.520 align:middle line:90%


00:55:31.520 --> 00:55:32.020 align:middle line:90%
OK.

00:55:32.020 --> 00:55:33.280 align:middle line:90%
So the phone is ready.

00:55:33.280 --> 00:55:39.480 align:middle line:84%
Let's go to Tony Stark and
dial 83033003, which is

00:55:39.480 --> 00:55:42.030 align:middle line:90%
the extension of Steve Rogers.

00:55:42.030 --> 00:55:47.400 align:middle line:84%
So 8303 and then the extension
of Steve Rogers, which is 3003.

00:55:47.400 --> 00:55:48.970 align:middle line:90%
And let's dial this.

00:55:48.970 --> 00:55:53.100 align:middle line:84%
You will not hear sound because
there's no sound right now.

00:55:53.100 --> 00:55:54.660 align:middle line:84%
We don't have
sound capabilities.

00:55:54.660 --> 00:55:58.290 align:middle line:84%
But the phone
should ring on here.

00:55:58.290 --> 00:56:00.610 align:middle line:90%
It should ring here.

00:56:00.610 --> 00:56:05.280 align:middle line:84%
Let's see why the
phone is not ringing.

00:56:05.280 --> 00:56:09.120 align:middle line:84%
So it seems like there
may be some mistake.

00:56:09.120 --> 00:56:10.320 align:middle line:90%
Or, in fact, it did ring.

00:56:10.320 --> 00:56:12.870 align:middle line:84%
So as you can see,
the calling number

00:56:12.870 --> 00:56:17.040 align:middle line:84%
is 82022003 which matches
the question requirement

00:56:17.040 --> 00:56:24.090 align:middle line:84%
that the side B user
should see 82022003.

00:56:24.090 --> 00:56:25.750 align:middle line:90%
And so it works.

00:56:25.750 --> 00:56:27.240 align:middle line:90%
Let's answer this call.

00:56:27.240 --> 00:56:28.335 align:middle line:90%
We should see video.

00:56:28.335 --> 00:56:32.200 align:middle line:90%


00:56:32.200 --> 00:56:35.800 align:middle line:90%
So I do see some video.

00:56:35.800 --> 00:56:39.270 align:middle line:84%
Now, if you do not see a
video, what you can do is just,

00:56:39.270 --> 00:56:41.190 align:middle line:90%
in fact, go back to here.

00:56:41.190 --> 00:56:45.690 align:middle line:84%
If you don't see a video,
you see VCAM, then just

00:56:45.690 --> 00:56:48.110 align:middle line:90%
cancel the call.

00:56:48.110 --> 00:56:53.040 align:middle line:90%
And go to your desktop.

00:56:53.040 --> 00:56:57.630 align:middle line:84%
So on your desktop,
inside Applications,

00:56:57.630 --> 00:57:03.180 align:middle line:90%
you would see e2eSoft VCam.

00:57:03.180 --> 00:57:04.140 align:middle line:90%
Double-click on that.

00:57:04.140 --> 00:57:08.550 align:middle line:90%


00:57:08.550 --> 00:57:12.690 align:middle line:90%
And I believe this is Jabber1.

00:57:12.690 --> 00:57:15.060 align:middle line:90%
So click on Tony Stark.

00:57:15.060 --> 00:57:16.230 align:middle line:90%
And close this.

00:57:16.230 --> 00:57:19.740 align:middle line:90%


00:57:19.740 --> 00:57:22.620 align:middle line:90%
Then go to side B phone.

00:57:22.620 --> 00:57:24.690 align:middle line:90%
Go back to Apps.

00:57:24.690 --> 00:57:29.890 align:middle line:84%
And you would see the folder or
the file called e2eSoft VCam.

00:57:29.890 --> 00:57:30.765 align:middle line:90%
Double-click on that.

00:57:30.765 --> 00:57:39.230 align:middle line:90%


00:57:39.230 --> 00:57:41.660 align:middle line:90%
And select Steve Rogers.

00:57:41.660 --> 00:57:43.730 align:middle line:90%
Double-click on Steve Rogers.

00:57:43.730 --> 00:57:45.680 align:middle line:90%
So you would see a picture.

00:57:45.680 --> 00:57:46.640 align:middle line:90%
And close this.

00:57:46.640 --> 00:57:47.990 align:middle line:90%
Say Yes.

00:57:47.990 --> 00:57:50.480 align:middle line:90%
Now make the call again from--

00:57:50.480 --> 00:57:52.310 align:middle line:84%
let's do this time
from Steve Rogers

00:57:52.310 --> 00:57:55.080 align:middle line:84%
to HQ just to see
if that works also.

00:57:55.080 --> 00:58:01.710 align:middle line:84%
So 82022003, which is
Tony Stark's extension.

00:58:01.710 --> 00:58:04.540 align:middle line:90%
Let's call this.

00:58:04.540 --> 00:58:07.210 align:middle line:90%
And let's hit Enter.

00:58:07.210 --> 00:58:08.440 align:middle line:90%
So it dials that.

00:58:08.440 --> 00:58:10.210 align:middle line:90%
It's dialing Tony Stark.

00:58:10.210 --> 00:58:11.560 align:middle line:90%
Let's look at Jabber1.

00:58:11.560 --> 00:58:13.930 align:middle line:84%
I should see the
phone ringing here.

00:58:13.930 --> 00:58:16.000 align:middle line:90%
There is a bit of delay.

00:58:16.000 --> 00:58:19.570 align:middle line:84%
Again, this could be because
of the CPU or anything.

00:58:19.570 --> 00:58:21.550 align:middle line:90%
But give it some time.

00:58:21.550 --> 00:58:24.280 align:middle line:84%
Give it a few seconds
for it to show up.

00:58:24.280 --> 00:58:27.730 align:middle line:90%
It does show up now, 83033000X.

00:58:27.730 --> 00:58:28.930 align:middle line:90%
And click on Answer.

00:58:28.930 --> 00:58:30.740 align:middle line:90%
And you should see video.

00:58:30.740 --> 00:58:33.070 align:middle line:90%
You should see Steve Rogers.

00:58:33.070 --> 00:58:36.850 align:middle line:84%
And Steve Rogers
should see Tony Stark.

00:58:36.850 --> 00:58:39.422 align:middle line:84%
Now, how do you verify
if audio is working?

00:58:39.422 --> 00:58:41.380 align:middle line:84%
Because you can't really
hear the audio, right?

00:58:41.380 --> 00:58:45.430 align:middle line:84%
Just do Control
Shift S. I mean, I

00:58:45.430 --> 00:58:49.450 align:middle line:84%
don't know what's the
shortcut for Windows machine

00:58:49.450 --> 00:58:51.230 align:middle line:84%
if you're using a
Windows machine.

00:58:51.230 --> 00:58:54.400 align:middle line:84%
But on Mac, it's
just Control Shift S.

00:58:54.400 --> 00:58:56.890 align:middle line:90%
You would see call statistics.

00:58:56.890 --> 00:58:59.110 align:middle line:90%
Look at the packets.

00:58:59.110 --> 00:59:01.600 align:middle line:84%
If you see the packets
flowing between the two,

00:59:01.600 --> 00:59:05.050 align:middle line:84%
I'm using the audio
codec as OPUS.

00:59:05.050 --> 00:59:07.900 align:middle line:84%
And you see the packets are
increasing, which basically

00:59:07.900 --> 00:59:10.750 align:middle line:90%
means audio is also working.

00:59:10.750 --> 00:59:14.030 align:middle line:84%
Let's close this
and end the call.

00:59:14.030 --> 00:59:16.670 align:middle line:90%


00:59:16.670 --> 00:59:21.370 align:middle line:84%
So with this, we've basically
met all the requirements

00:59:21.370 --> 00:59:22.900 align:middle line:90%
of the question.

00:59:22.900 --> 00:59:29.050 align:middle line:84%
We configured HQ and side B
cluster to route the calls

00:59:29.050 --> 00:59:30.460 align:middle line:90%
through SME.

00:59:30.460 --> 00:59:35.560 align:middle line:84%
And the SME had two
partitions, which

00:59:35.560 --> 00:59:38.590 align:middle line:84%
was one from HQ going
towards side B and one

00:59:38.590 --> 00:59:40.990 align:middle line:90%
from side B going towards HQ.

00:59:40.990 --> 00:59:43.490 align:middle line:84%
And we met all of
the requirements.

00:59:43.490 --> 00:59:45.380 align:middle line:84%
I hope this video was
informative to you,

00:59:45.380 --> 00:59:48.090 align:middle line:90%
and thank you for watching.

00:59:48.090 --> 00:59:49.000 align:middle line:90%