WEBVTT 00:00:00.000 --> 00:00:03.409 align:middle line:90% 00:00:03.409 --> 00:00:06.818 align:middle line:90% [AUDIO LOGO] 00:00:06.818 --> 00:00:09.750 align:middle line:90% 00:00:09.750 --> 00:00:12.225 align:middle line:90% Hello, and welcome to INE. 00:00:12.225 --> 00:00:15.150 align:middle line:84% Today in this video, we will look at section 2, Dial Plan, 00:00:15.150 --> 00:00:17.610 align:middle line:90% basically task 2.4. 00:00:17.610 --> 00:00:21.120 align:middle line:84% Now, this task is very similar to task 2.3. 00:00:21.120 --> 00:00:24.510 align:middle line:84% If you remember in 2.3, we were doing outbound calling 00:00:24.510 --> 00:00:26.670 align:middle line:90% to PSTN from HQ site. 00:00:26.670 --> 00:00:29.310 align:middle line:84% This time, we would be doing from site B. 00:00:29.310 --> 00:00:31.170 align:middle line:84% So this task says configure site B 00:00:31.170 --> 00:00:33.870 align:middle line:84% to satisfy the following dial plan requirements. 00:00:33.870 --> 00:00:37.350 align:middle line:84% Access code for all PSTN calls would be 9. 00:00:37.350 --> 00:00:41.310 align:middle line:84% All PST-- all calls to PSTN must be forwarded to SME 00:00:41.310 --> 00:00:43.560 align:middle line:90% from the site B UCM. 00:00:43.560 --> 00:00:46.950 align:middle line:84% SME must forward all calls to the pair of redundant CUBE's, 00:00:46.950 --> 00:00:48.750 align:middle line:90% which is R1 and R2. 00:00:48.750 --> 00:00:52.410 align:middle line:84% All calls, calling and called, from site 00:00:52.410 --> 00:00:56.250 align:middle line:84% B must be forwarded to SME as e164. 00:00:56.250 --> 00:01:01.380 align:middle line:84% And SME must send e164 down to the redundant CUBE's. 00:01:01.380 --> 00:01:04.709 align:middle line:84% The redundant CUBE's must translate e164 number 00:01:04.709 --> 00:01:08.700 align:middle line:84% into the formats required by the PSTN. 00:01:08.700 --> 00:01:14.340 align:middle line:84% Now, the requirement is that when site B dials local calls, 00:01:14.340 --> 00:01:16.230 align:middle line:90% it will dial 7 digits. 00:01:16.230 --> 00:01:18.300 align:middle line:84% However, he would be first dialing 9 00:01:18.300 --> 00:01:21.510 align:middle line:84% as the access code followed by 7 digits, which 00:01:21.510 --> 00:01:23.130 align:middle line:90% is a subscriber number. 00:01:23.130 --> 00:01:25.890 align:middle line:84% And the first digit of the subscriber number 00:01:25.890 --> 00:01:29.220 align:middle line:84% is going to be from 2 to 9, while remaining digits could 00:01:29.220 --> 00:01:30.330 align:middle line:90% be anything. 00:01:30.330 --> 00:01:33.600 align:middle line:84% For long distance national calls, 00:01:33.600 --> 00:01:35.370 align:middle line:90% he would be dialing 10 digits. 00:01:35.370 --> 00:01:38.490 align:middle line:84% First would be the access code 9 and then 00:01:38.490 --> 00:01:40.380 align:middle line:84% 10 digits, where the three digits would 00:01:40.380 --> 00:01:42.660 align:middle line:84% be the area code and then 7 digits 00:01:42.660 --> 00:01:44.610 align:middle line:90% would be the subscriber number. 00:01:44.610 --> 00:01:48.090 align:middle line:84% In the area code, the first digit would be from 2 to 9. 00:01:48.090 --> 00:01:50.310 align:middle line:84% In the subscriber number, the first digit 00:01:50.310 --> 00:01:53.280 align:middle line:90% is also going to be from 2 to 9. 00:01:53.280 --> 00:01:56.040 align:middle line:84% For international calls, they would be dialing 9, 00:01:56.040 --> 00:01:59.220 align:middle line:84% which is the access code, followed by 011, 00:01:59.220 --> 00:02:04.140 align:middle line:84% and then a variable digits, which could contain the pound 00:02:04.140 --> 00:02:07.290 align:middle line:90% sign or without the pound sign. 00:02:07.290 --> 00:02:10.139 align:middle line:84% As far as the PSTN is concerned, the PSTN 00:02:10.139 --> 00:02:14.130 align:middle line:84% expects for local and national calls expects 1 00:02:14.130 --> 00:02:17.310 align:middle line:84% followed by 3-digit area code, and then 00:02:17.310 --> 00:02:19.230 align:middle line:90% 7-digit subscriber number. 00:02:19.230 --> 00:02:20.520 align:middle line:90% This is for called. 00:02:20.520 --> 00:02:24.570 align:middle line:84% And for international, it expects 011 followed by any 00:02:24.570 --> 00:02:26.790 align:middle line:84% variable digits, which is for international, again, 00:02:26.790 --> 00:02:27.660 align:middle line:90% the called. 00:02:27.660 --> 00:02:32.250 align:middle line:84% For calling, the PSTN expects for local and national calls 00:02:32.250 --> 00:02:36.280 align:middle line:84% 10 digits, which is the area code and the subscriber number, 00:02:36.280 --> 00:02:39.000 align:middle line:84% so basically, without the plus and without the 1. 00:02:39.000 --> 00:02:42.660 align:middle line:84% And for international calls, we should send plus 00:02:42.660 --> 00:02:46.710 align:middle line:84% followed by the country code and then the 10-digit number. 00:02:46.710 --> 00:02:49.350 align:middle line:84% For all outbound calls, they must 00:02:49.350 --> 00:02:52.380 align:middle line:84% be serviced by the previously created route pattern which 00:02:52.380 --> 00:02:56.310 align:middle line:84% was backslash plus bang, which we had done in the intersite. 00:02:56.310 --> 00:02:58.980 align:middle line:84% So let's quickly go and build this. 00:02:58.980 --> 00:03:00.870 align:middle line:84% Now, before I configure anything, 00:03:00.870 --> 00:03:02.370 align:middle line:84% the first thing what I'm going to do 00:03:02.370 --> 00:03:05.850 align:middle line:84% is go back to my call manager and see what's preconfigured, 00:03:05.850 --> 00:03:08.340 align:middle line:84% of what did we do in the intercept, what 00:03:08.340 --> 00:03:11.380 align:middle line:84% all is preconfigured, and then what I need to do. 00:03:11.380 --> 00:03:15.030 align:middle line:84% So let's go first to the call manager. 00:03:15.030 --> 00:03:19.410 align:middle line:90% So here is where I have my-- 00:03:19.410 --> 00:03:26.250 align:middle line:84% this is my SME, and this is my site B called manager. 00:03:26.250 --> 00:03:30.600 align:middle line:90% Let's log in, so administrator. 00:03:30.600 --> 00:03:35.760 align:middle line:90% Password was c1sc0123! 00:03:35.760 --> 00:03:42.880 align:middle line:84% Now, on the call manager of site B, if you look at the devices-- 00:03:42.880 --> 00:03:44.130 align:middle line:90% let's look at the phone first. 00:03:44.130 --> 00:03:47.160 align:middle line:84% I believe we only have one phone, which is Steve Rogers. 00:03:47.160 --> 00:03:49.005 align:middle line:90% So let's look at device phones. 00:03:49.005 --> 00:03:52.040 align:middle line:90% 00:03:52.040 --> 00:03:56.120 align:middle line:84% That device as per the intersite task that we had done earlier, 00:03:56.120 --> 00:04:00.710 align:middle line:84% we had put the device CSS as CSS-PHONES. 00:04:00.710 --> 00:04:02.750 align:middle line:84% So the first thing that I would do 00:04:02.750 --> 00:04:08.090 align:middle line:84% is create a partition called PT-PSTN 00:04:08.090 --> 00:04:11.150 align:middle line:84% and put that partition in the phone's CSS 00:04:11.150 --> 00:04:13.430 align:middle line:84% so that the phone has access to that partition. 00:04:13.430 --> 00:04:15.180 align:middle line:84% That's the first thing that I would do. 00:04:15.180 --> 00:04:17.300 align:middle line:84% So let's quickly go and verify first 00:04:17.300 --> 00:04:19.324 align:middle line:84% that the phone belongs to which CSS. 00:04:19.324 --> 00:04:22.600 align:middle line:90% 00:04:22.600 --> 00:04:27.520 align:middle line:84% Let's log in on SME as well in the meanwhile, administrator, 00:04:27.520 --> 00:04:31.930 align:middle line:90% password, c1sc0123! 00:04:31.930 --> 00:04:45.150 align:middle line:90% And then go back to site B. 00:04:45.150 --> 00:04:47.505 align:middle line:84% So the requirement basically states-- 00:04:47.505 --> 00:04:49.500 align:middle line:84% it's similar to the earlier task that we 00:04:49.500 --> 00:04:51.090 align:middle line:90% did, which was for HQ site. 00:04:51.090 --> 00:04:53.710 align:middle line:84% The requirement is exactly the same. 00:04:53.710 --> 00:04:56.820 align:middle line:84% The site B cluster for calling and called 00:04:56.820 --> 00:04:59.880 align:middle line:90% would send e164 to SME. 00:04:59.880 --> 00:05:03.270 align:middle line:84% SME would send down to the CUBE calling 00:05:03.270 --> 00:05:06.120 align:middle line:90% and called both again e164. 00:05:06.120 --> 00:05:09.010 align:middle line:84% It is the router which is going to change-- 00:05:09.010 --> 00:05:11.100 align:middle line:84% which is going to do all the translations 00:05:11.100 --> 00:05:14.760 align:middle line:84% and sent to PSTN as per the requirement 00:05:14.760 --> 00:05:17.260 align:middle line:90% desired by the PSTN. 00:05:17.260 --> 00:05:19.260 align:middle line:84% So first thing, let's go to Device, 00:05:19.260 --> 00:05:26.690 align:middle line:90% Phones on site B. Let's do Find. 00:05:26.690 --> 00:05:33.170 align:middle line:84% And we have one phone here, which is CSFROGERS. 00:05:33.170 --> 00:05:39.790 align:middle line:84% And that phone has the device CSS as CSS-PHONES. 00:05:39.790 --> 00:05:45.610 align:middle line:84% So first thing what I would do is create a partition, 00:05:45.610 --> 00:05:48.085 align:middle line:84% and let's name this partition as PT-PSTN. 00:05:48.085 --> 00:05:55.420 align:middle line:90% 00:05:55.420 --> 00:05:59.080 align:middle line:84% And let's save this and then go back 00:05:59.080 --> 00:06:03.580 align:middle line:84% to call routing and the class of control. 00:06:03.580 --> 00:06:08.530 align:middle line:84% Go to Calling Search Space and give the phone CSS access 00:06:08.530 --> 00:06:10.060 align:middle line:90% to that partition. 00:06:10.060 --> 00:06:12.930 align:middle line:90% Let's do Find. 00:06:12.930 --> 00:06:16.560 align:middle line:90% We have CSS-PHONES here. 00:06:16.560 --> 00:06:22.400 align:middle line:84% Let's give him access to PT-PSTN and save. 00:06:22.400 --> 00:06:25.910 align:middle line:84% Now my phone has access to this partition. 00:06:25.910 --> 00:06:29.600 align:middle line:84% Next thing what I'm going to do is look at my route pattern. 00:06:29.600 --> 00:06:32.440 align:middle line:90% 00:06:32.440 --> 00:06:34.840 align:middle line:90% What route patterns do I have? 00:06:34.840 --> 00:06:37.090 align:middle line:84% Now, I only have one route pattern 00:06:37.090 --> 00:06:40.300 align:middle line:84% from the earlier task which we had done for intersite, which 00:06:40.300 --> 00:06:43.360 align:middle line:84% was backslash plus bang, and that partition, 00:06:43.360 --> 00:06:46.030 align:middle line:84% that route pattern is in the partition PT single route 00:06:46.030 --> 00:06:46.570 align:middle line:90% pattern. 00:06:46.570 --> 00:06:48.830 align:middle line:84% My phones don't have access to this. 00:06:48.830 --> 00:06:50.500 align:middle line:84% So what I'm going to do is I'm going 00:06:50.500 --> 00:06:52.570 align:middle line:84% to create some translation patterns 00:06:52.570 --> 00:06:56.770 align:middle line:84% and do the required changes for calling and called 00:06:56.770 --> 00:06:59.080 align:middle line:84% and then give the translation pattern 00:06:59.080 --> 00:07:01.520 align:middle line:90% access to this partition. 00:07:01.520 --> 00:07:03.282 align:middle line:90% So let's create some. 00:07:03.282 --> 00:07:04.615 align:middle line:90% Let's go to Translation Pattern. 00:07:04.615 --> 00:07:07.190 align:middle line:90% 00:07:07.190 --> 00:07:09.080 align:middle line:90% Let's do Find. 00:07:09.080 --> 00:07:11.180 align:middle line:84% So I should only have two translation patterns 00:07:11.180 --> 00:07:13.380 align:middle line:84% from the earlier task of intersite. 00:07:13.380 --> 00:07:16.040 align:middle line:84% Let's create some translation patterns for local calling, 00:07:16.040 --> 00:07:19.550 align:middle line:84% for national calling, and two for international calling. 00:07:19.550 --> 00:07:22.470 align:middle line:90% Let's do Add New. 00:07:22.470 --> 00:07:24.690 align:middle line:84% First one is going to be-- so he is dialing 00:07:24.690 --> 00:07:26.220 align:middle line:90% 9, which is the access code. 00:07:26.220 --> 00:07:29.190 align:middle line:84% I should strip off the 9 because I want-- as per the question, 00:07:29.190 --> 00:07:33.000 align:middle line:84% I want to send e164 as the calling and the called. 00:07:33.000 --> 00:07:35.880 align:middle line:84% So I need to strip off the 9, so 9 dot. 00:07:35.880 --> 00:07:38.160 align:middle line:84% The first digit of the subscriber number 00:07:38.160 --> 00:07:39.420 align:middle line:90% should be from 2 to 9. 00:07:39.420 --> 00:07:47.010 align:middle line:84% So let's make a box bracket, 2-9, then six XXX, 3, 4, 5, 6. 00:07:47.010 --> 00:07:48.812 align:middle line:90% So that becomes 9.2-9XXXXXX. 00:07:48.812 --> 00:07:52.290 align:middle line:90% 00:07:52.290 --> 00:07:54.450 align:middle line:84% This goes in the partition PT-PSTN, 00:07:54.450 --> 00:07:56.490 align:middle line:84% and so my phone has access to that. 00:07:56.490 --> 00:07:58.710 align:middle line:84% This translation pattern will need access 00:07:58.710 --> 00:08:00.150 align:middle line:84% to the single route pattern which 00:08:00.150 --> 00:08:04.770 align:middle line:84% is the plus 1, plus bang 1, which is single route pattern. 00:08:04.770 --> 00:08:06.780 align:middle line:84% We will keep the outside dial tone 00:08:06.780 --> 00:08:10.620 align:middle line:84% because we will be dialing 9 as the access code. 00:08:10.620 --> 00:08:14.040 align:middle line:84% So we want the outside dial tone. 00:08:14.040 --> 00:08:16.290 align:middle line:84% And then change the calling number. 00:08:16.290 --> 00:08:18.330 align:middle line:84% Right now my calling number is four-digit. 00:08:18.330 --> 00:08:20.800 align:middle line:84% My phones have the extension of four digits. 00:08:20.800 --> 00:08:25.310 align:middle line:84% So I would change that to e164 and change 00:08:25.310 --> 00:08:29.340 align:middle line:84% the called to a PreDot, so that strips off the 9. 00:08:29.340 --> 00:08:34.559 align:middle line:84% And let's add plus 1972 as the prefix digit. 00:08:34.559 --> 00:08:42.230 align:middle line:84% So now my called number becomes plus 19722-9XXXXXX. 00:08:42.230 --> 00:08:43.055 align:middle line:90% Let's save this. 00:08:43.055 --> 00:08:47.450 align:middle line:90% 00:08:47.450 --> 00:08:51.820 align:middle line:84% Let's copy this and make one for national. 00:08:51.820 --> 00:08:55.980 align:middle line:90% My national is going to be 9.2-- 00:08:55.980 --> 00:09:05.630 align:middle line:84% 9, in fact, 91, so 9.1, then 2-9XX, 00:09:05.630 --> 00:09:10.370 align:middle line:84% which is my area code, then again, box bracket 2-9XXXXXX. 00:09:10.370 --> 00:09:13.250 align:middle line:90% 00:09:13.250 --> 00:09:16.880 align:middle line:84% So this is what my national call looks like. 00:09:16.880 --> 00:09:18.950 align:middle line:84% If you look at the question, how is he 00:09:18.950 --> 00:09:20.120 align:middle line:90% dialing the national call? 00:09:20.120 --> 00:09:24.950 align:middle line:84% He will dial 9 as the access key followed by 1 and then the area 00:09:24.950 --> 00:09:28.470 align:middle line:84% code, which is 3 digits, and then the subscriber number, 00:09:28.470 --> 00:09:29.510 align:middle line:90% which is 7 digits. 00:09:29.510 --> 00:09:32.630 align:middle line:84% The area code first digit has to be from 2 to 9. 00:09:32.630 --> 00:09:35.690 align:middle line:84% The subscriber first digit has to be from 2 to 9. 00:09:35.690 --> 00:09:38.510 align:middle line:84% So I am stripping off just the 9. 00:09:38.510 --> 00:09:41.720 align:middle line:90% I want to keep the 1. 00:09:41.720 --> 00:09:43.910 align:middle line:90% This again goes to PT-PSTN. 00:09:43.910 --> 00:09:48.350 align:middle line:84% The translation pattern has access to the single route 00:09:48.350 --> 00:09:51.830 align:middle line:84% pattern, which is the route pattern backslash plus bang. 00:09:51.830 --> 00:09:54.920 align:middle line:84% I will keep the outside dial tone, 00:09:54.920 --> 00:09:59.120 align:middle line:84% change my calling to e164 called, do a PreDot. 00:09:59.120 --> 00:10:01.700 align:middle line:90% So that strips off the 9. 00:10:01.700 --> 00:10:04.940 align:middle line:90% And here I would just add plus. 00:10:04.940 --> 00:10:09.540 align:middle line:84% So now my called becomes plus 12-9XX2-9XXXXXX. 00:10:09.540 --> 00:10:16.400 align:middle line:90% 00:10:16.400 --> 00:10:18.090 align:middle line:90% Let's save this. 00:10:18.090 --> 00:10:20.710 align:middle line:90% So that's my national. 00:10:20.710 --> 00:10:24.700 align:middle line:84% Let's copy this and create one more for international. 00:10:24.700 --> 00:10:26.560 align:middle line:90% For international, we need two. 00:10:26.560 --> 00:10:30.380 align:middle line:84% One is without the pound sign, and one is with the pound sign. 00:10:30.380 --> 00:10:33.650 align:middle line:84% So let's create the one with the pound sign first. 00:10:33.650 --> 00:10:36.532 align:middle line:90% So that's going to be 90-- 00:10:36.532 --> 00:10:42.250 align:middle line:90% 9011.! 00:10:42.250 --> 00:10:44.740 align:middle line:84% Now we want to strip off the 9011. 00:10:44.740 --> 00:10:46.660 align:middle line:84% We don't want to strip off just the 9, 00:10:46.660 --> 00:10:49.870 align:middle line:84% because the question says we must send e164 as the calling 00:10:49.870 --> 00:10:50.870 align:middle line:90% and called it. 00:10:50.870 --> 00:10:53.770 align:middle line:84% So we don't want the called to have 011. 00:10:53.770 --> 00:10:58.030 align:middle line:84% We want the called to strip off the 9011. 00:10:58.030 --> 00:11:01.840 align:middle line:90% So I'm doing a 9011.! 00:11:01.840 --> 00:11:04.300 align:middle line:90% and then pound. 00:11:04.300 --> 00:11:08.950 align:middle line:84% This again goes back to PTSD, and single route pattern. 00:11:08.950 --> 00:11:10.750 align:middle line:84% I would have the outside dialed tone. 00:11:10.750 --> 00:11:13.240 align:middle line:84% I would keep the urgent priority. 00:11:13.240 --> 00:11:15.100 align:middle line:90% Calling will change to e164. 00:11:15.100 --> 00:11:20.560 align:middle line:84% Called would change from PreDot PreDot Trailing-#. 00:11:20.560 --> 00:11:24.661 align:middle line:84% I'm removing the 9011, and I'm removing the pound. 00:11:24.661 --> 00:11:27.760 align:middle line:90% And this would have-- 00:11:27.760 --> 00:11:30.550 align:middle line:84% this would have-- so what am I dialing? 00:11:30.550 --> 00:11:33.340 align:middle line:84% 9011 and then the country code and then 00:11:33.340 --> 00:11:36.650 align:middle line:84% the area number, area code, or the subscriber number. 00:11:36.650 --> 00:11:40.510 align:middle line:84% So I would only have the plus sign here. 00:11:40.510 --> 00:11:42.660 align:middle line:84% So let's say if I was dialing the UK 00:11:42.660 --> 00:11:49.860 align:middle line:84% number, 9011442085554444, 9011 get stripped off. 00:11:49.860 --> 00:11:55.560 align:middle line:84% The called number becomes 44-208-555-4444 and prefixing 00:11:55.560 --> 00:11:59.260 align:middle line:84% plus, which means my called number becomes plus 00:11:59.260 --> 00:12:04.800 align:middle line:90% 44-208-555-4444. 00:12:04.800 --> 00:12:05.670 align:middle line:90% Let's save this. 00:12:05.670 --> 00:12:08.510 align:middle line:90% 00:12:08.510 --> 00:12:11.470 align:middle line:84% Let's now copy this and make one more for without the pound 00:12:11.470 --> 00:12:13.740 align:middle line:90% sign. 00:12:13.740 --> 00:12:16.430 align:middle line:84% So that's going to be without the pound sign. 00:12:16.430 --> 00:12:18.500 align:middle line:84% Now, for the without the pound sign, 00:12:18.500 --> 00:12:21.050 align:middle line:84% you must remove the urgent priority. 00:12:21.050 --> 00:12:23.510 align:middle line:84% Because if you do not remove the urgent priority, 00:12:23.510 --> 00:12:26.900 align:middle line:84% the minute I dial 9011 and the first digit, 00:12:26.900 --> 00:12:29.040 align:middle line:84% it will just try to make the call. 00:12:29.040 --> 00:12:32.960 align:middle line:84% So we must wait for the interdigit timeout. 00:12:32.960 --> 00:12:35.300 align:middle line:84% So we must strip off the urgent priority. 00:12:35.300 --> 00:12:37.130 align:middle line:84% See, for local calls, I didn't need 00:12:37.130 --> 00:12:39.080 align:middle line:90% to remove the urgent priority. 00:12:39.080 --> 00:12:41.000 align:middle line:84% For national calls, I didn't need 00:12:41.000 --> 00:12:42.560 align:middle line:90% to remove the urgent priority. 00:12:42.560 --> 00:12:44.750 align:middle line:84% For international calls with the pound, 00:12:44.750 --> 00:12:46.880 align:middle line:84% I didn't need to remove the urgent priority 00:12:46.880 --> 00:12:51.480 align:middle line:84% because I have to end it with the pound for it to match. 00:12:51.480 --> 00:12:54.050 align:middle line:90% But 49011.! 00:12:54.050 --> 00:12:56.300 align:middle line:84% I need to remove the urgent priority. 00:12:56.300 --> 00:13:00.020 align:middle line:84% Otherwise, the minute I dial 9011 and the first digit, 00:13:00.020 --> 00:13:03.510 align:middle line:84% after that, it would just try to route the call. 00:13:03.510 --> 00:13:04.400 align:middle line:90% So remove that. 00:13:04.400 --> 00:13:06.500 align:middle line:90% Calling becomes e164. 00:13:06.500 --> 00:13:10.895 align:middle line:84% Called would just have a PreDot and a plus sign. 00:13:10.895 --> 00:13:13.700 align:middle line:90% 00:13:13.700 --> 00:13:15.550 align:middle line:90% So now what's going to happen? 00:13:15.550 --> 00:13:18.460 align:middle line:84% Phone CSS has access to PT-PSTN, which 00:13:18.460 --> 00:13:21.190 align:middle line:84% means when the phone dials, it hits these translation 00:13:21.190 --> 00:13:21.850 align:middle line:90% patterns. 00:13:21.850 --> 00:13:24.640 align:middle line:84% This translation pattern has access to the single route 00:13:24.640 --> 00:13:26.740 align:middle line:84% pattern, so it goes to the route pattern. 00:13:26.740 --> 00:13:29.650 align:middle line:84% In the route pattern, it points to routeless route group 00:13:29.650 --> 00:13:31.510 align:middle line:90% and goes to the SIP Trunk. 00:13:31.510 --> 00:13:36.910 align:middle line:84% On the SIP Trunk, if you remember, we had configured-- 00:13:36.910 --> 00:13:39.850 align:middle line:84% I believe we had configured called party transformation 00:13:39.850 --> 00:13:41.470 align:middle line:90% which strips off the plus. 00:13:41.470 --> 00:13:44.740 align:middle line:84% However, that plus is not going to be stripped off. 00:13:44.740 --> 00:13:49.000 align:middle line:84% The reason is going to be if you look at the PSTN, 00:13:49.000 --> 00:13:56.640 align:middle line:84% if you look at the SIP Trunk, it says 00:13:56.640 --> 00:14:01.690 align:middle line:84% that for outbound, use the device pool for call party 00:14:01.690 --> 00:14:02.410 align:middle line:90% transformation. 00:14:02.410 --> 00:14:05.920 align:middle line:84% If I look at the device pool, it calls the call party 00:14:05.920 --> 00:14:08.000 align:middle line:90% transformation, which is here. 00:14:08.000 --> 00:14:11.050 align:middle line:84% And if I look at the call party transformation pattern 00:14:11.050 --> 00:14:13.840 align:middle line:84% that we had done in the earlier task, 00:14:13.840 --> 00:14:17.770 align:middle line:90% it matches backslash plus 8202. 00:14:17.770 --> 00:14:23.110 align:middle line:84% It doesn't match backslash plus, I 00:14:23.110 --> 00:14:31.650 align:middle line:84% believe it was plus 1408 or 1972 or Hong Kong number or UK 00:14:31.650 --> 00:14:32.150 align:middle line:90% number. 00:14:32.150 --> 00:14:33.190 align:middle line:90% It does not match that. 00:14:33.190 --> 00:14:37.660 align:middle line:84% It only matches specific number, 8202. 00:14:37.660 --> 00:14:39.940 align:middle line:84% So when the call goes out from the SIP Trunk, 00:14:39.940 --> 00:14:41.900 align:middle line:84% the plus sign is not going to be removed, 00:14:41.900 --> 00:14:44.200 align:middle line:84% which means that my call manager is 00:14:44.200 --> 00:14:47.740 align:middle line:84% going to send to SME calling number as e164 00:14:47.740 --> 00:14:52.000 align:middle line:90% and called as e164. 00:14:52.000 --> 00:14:53.000 align:middle line:90% So that's it. 00:14:53.000 --> 00:14:57.130 align:middle line:84% That's all I need on my site B called manager. 00:14:57.130 --> 00:14:59.350 align:middle line:90% Let's now go to SME. 00:14:59.350 --> 00:15:02.120 align:middle line:84% On the SME, let's see what is there. 00:15:02.120 --> 00:15:05.800 align:middle line:84% The first thing that we would need as per the question, let's 00:15:05.800 --> 00:15:07.120 align:middle line:90% go back and check. 00:15:07.120 --> 00:15:09.340 align:middle line:84% The question does not really say to create 00:15:09.340 --> 00:15:12.190 align:middle line:90% any route groups or rout list. 00:15:12.190 --> 00:15:14.140 align:middle line:90% It does not say anything. 00:15:14.140 --> 00:15:17.050 align:middle line:84% Unlike the earlier task of HQ, we 00:15:17.050 --> 00:15:18.615 align:middle line:84% had to create a route group here. 00:15:18.615 --> 00:15:19.990 align:middle line:84% Here the question does not really 00:15:19.990 --> 00:15:22.117 align:middle line:84% say that, which means I don't really 00:15:22.117 --> 00:15:23.950 align:middle line:84% care to create a route group or a routeless. 00:15:23.950 --> 00:15:26.470 align:middle line:84% I will directly create a SIP Trunk pointing down 00:15:26.470 --> 00:15:30.020 align:middle line:84% to the peer, to the CUBE, redundant CUBE's. 00:15:30.020 --> 00:15:32.950 align:middle line:84% So let's go back here and create a SIP Trunk first. 00:15:32.950 --> 00:15:39.290 align:middle line:90% 00:15:39.290 --> 00:15:40.070 align:middle line:90% Let's do Find. 00:15:40.070 --> 00:15:43.490 align:middle line:90% 00:15:43.490 --> 00:15:48.310 align:middle line:84% So in fact, I already have a SME PSTN SIP 00:15:48.310 --> 00:15:51.220 align:middle line:90% Trunk from the earlier task. 00:15:51.220 --> 00:15:53.530 align:middle line:84% When we did the dial plan for HQ, 00:15:53.530 --> 00:15:57.070 align:middle line:84% we had created the SIP Trunk to PSTN 00:15:57.070 --> 00:16:02.110 align:middle line:84% which was pointing to the VCUBE's, so I just reuse that. 00:16:02.110 --> 00:16:04.150 align:middle line:84% I don't have to create a SIP Trunk. 00:16:04.150 --> 00:16:11.780 align:middle line:84% All I will do is go back to Partitions 00:16:11.780 --> 00:16:13.565 align:middle line:84% and check what partitions I have. 00:16:13.565 --> 00:16:16.840 align:middle line:90% 00:16:16.840 --> 00:16:20.350 align:middle line:84% So I have these partitions PT-PSTN 00:16:20.350 --> 00:16:22.570 align:middle line:90% which we had done for HQ. 00:16:22.570 --> 00:16:27.290 align:middle line:84% Let's go back to that translation pattern. 00:16:27.290 --> 00:16:30.100 align:middle line:90% What does that say? 00:16:30.100 --> 00:16:31.850 align:middle line:84% So we don't have any translation patterns. 00:16:31.850 --> 00:16:32.975 align:middle line:90% Let's go to route patterns. 00:16:32.975 --> 00:16:38.630 align:middle line:90% 00:16:38.630 --> 00:16:40.400 align:middle line:84% So we have one route pattern here 00:16:40.400 --> 00:16:43.250 align:middle line:90% which says backslash plus bang. 00:16:43.250 --> 00:16:47.740 align:middle line:84% And this is in the PSTN, which basically says any calls that 00:16:47.740 --> 00:16:53.290 align:middle line:84% come in with the called number as plus anything, 00:16:53.290 --> 00:16:56.590 align:middle line:84% any variable digits forwarded to PSTN. 00:16:56.590 --> 00:16:58.570 align:middle line:84% Now, who has access to this partition? 00:16:58.570 --> 00:17:01.300 align:middle line:84% Who needs access to this partition? 00:17:01.300 --> 00:17:04.434 align:middle line:84% The call is coming from site B to SME. 00:17:04.434 --> 00:17:05.810 align:middle line:90% On where is it coming in? 00:17:05.810 --> 00:17:09.130 align:middle line:84% It's coming in on the trunk, which 00:17:09.130 --> 00:17:12.609 align:middle line:90% is between site B and SME. 00:17:12.609 --> 00:17:19.030 align:middle line:84% So if I look back at trunk, this is the trunk strong to site B. 00:17:19.030 --> 00:17:20.810 align:middle line:90% It is coming in here. 00:17:20.810 --> 00:17:25.460 align:middle line:84% So from SME's perspective, it is inbound on this trunk link. 00:17:25.460 --> 00:17:29.020 align:middle line:84% And here, I have a CSS already preconfigured 00:17:29.020 --> 00:17:31.300 align:middle line:84% from earlier tasks that we had done. 00:17:31.300 --> 00:17:34.030 align:middle line:84% I think we had done this for intersite. 00:17:34.030 --> 00:17:40.060 align:middle line:84% So all I would do is go back to CSS, Class of Control, 00:17:40.060 --> 00:17:46.830 align:middle line:84% Calling Search Space, go to Find, go to INBOUND FROM Site B 00:17:46.830 --> 00:17:49.270 align:middle line:90% and give him access to PT-PSTN. 00:17:49.270 --> 00:17:51.910 align:middle line:90% 00:17:51.910 --> 00:17:54.970 align:middle line:84% So now when the call comes in from site B to SME, 00:17:54.970 --> 00:17:58.400 align:middle line:84% it hits the inbound CSS on the SIP Trunk, 00:17:58.400 --> 00:18:02.620 align:middle line:84% which is of site B on SME and checks to CSS. 00:18:02.620 --> 00:18:04.780 align:middle line:84% It has access to PT-PSTN, which means 00:18:04.780 --> 00:18:08.440 align:middle line:84% it goes to the route pattern and hits the backslash plus bang 00:18:08.440 --> 00:18:10.750 align:middle line:90% and goes towards the VCUBE. 00:18:10.750 --> 00:18:12.050 align:middle line:90% Let's save this. 00:18:12.050 --> 00:18:14.210 align:middle line:90% So nothing else on the SME. 00:18:14.210 --> 00:18:17.200 align:middle line:84% So you see, once you build a dial plan for HQ 00:18:17.200 --> 00:18:21.730 align:middle line:84% in the lab exam for site B, everything is 50% or 80% 00:18:21.730 --> 00:18:23.770 align:middle line:90% of the work is already done. 00:18:23.770 --> 00:18:27.370 align:middle line:84% All you have to do is give them access to the PSTNs 00:18:27.370 --> 00:18:30.760 align:middle line:84% to basically the respective partitions. 00:18:30.760 --> 00:18:32.320 align:middle line:90% Most of the work is done. 00:18:32.320 --> 00:18:34.480 align:middle line:90% Let's save this. 00:18:34.480 --> 00:18:38.920 align:middle line:84% Now, all I need to do is configure my VCUBE's. 00:18:38.920 --> 00:18:41.780 align:middle line:84% So what is my VCUBE going to receive? 00:18:41.780 --> 00:18:47.690 align:middle line:84% He is going to receive the call when site B dial-- let's 00:18:47.690 --> 00:18:49.610 align:middle line:90% say we talk about local call. 00:18:49.610 --> 00:18:53.300 align:middle line:84% When site B dials local calls, how will he dial it? 00:18:53.300 --> 00:18:56.140 align:middle line:90% He will dial 9-- 00:18:56.140 --> 00:19:02.720 align:middle line:84% 9-- 9-525-2222, which is a PSTN's phone number. 00:19:02.720 --> 00:19:05.010 align:middle line:84% If you don't know the PSTN's phone number, 00:19:05.010 --> 00:19:12.590 align:middle line:84% you can go to Jabber 3 and go to your Jabber 00:19:12.590 --> 00:19:14.870 align:middle line:90% and look at the dropdown. 00:19:14.870 --> 00:19:20.780 align:middle line:84% The number is plus 1-972-525-2222, 00:19:20.780 --> 00:19:25.170 align:middle line:84% which is the 525-2222 is your subscriber number. 00:19:25.170 --> 00:19:29.960 align:middle line:84% So site B calling 525-2222 is the local call. 00:19:29.960 --> 00:19:35.190 align:middle line:84% Site B calling 408-515-1111, that's a national call. 00:19:35.190 --> 00:19:38.670 align:middle line:84% Site B calling Hong Kong is an international call. 00:19:38.670 --> 00:19:42.630 align:middle line:84% Side B calling UK, that's an international call. 00:19:42.630 --> 00:19:45.980 align:middle line:84% So right now, if he's dot dialing site B to site 00:19:45.980 --> 00:19:48.420 align:middle line:90% B of PSTN, that's a local call. 00:19:48.420 --> 00:19:51.860 align:middle line:84% So he would not dial 91, give the area code. 00:19:51.860 --> 00:19:56.370 align:middle line:90% He would just dial 9-525-2222. 00:19:56.370 --> 00:19:58.860 align:middle line:84% So when he dials that, the calling 00:19:58.860 --> 00:20:06.180 align:middle line:84% number is four digit from my phone and called is 9-525-2222. 00:20:06.180 --> 00:20:09.210 align:middle line:84% Since the phone CSS has access to PT-PSTN, 00:20:09.210 --> 00:20:11.770 align:middle line:90% it hits the translation pattern. 00:20:11.770 --> 00:20:14.200 align:middle line:90% Calling number changes to e164. 00:20:14.200 --> 00:20:16.690 align:middle line:90% Called changes to e164. 00:20:16.690 --> 00:20:19.150 align:middle line:84% Translation pattern has access to route pattern. 00:20:19.150 --> 00:20:21.460 align:middle line:84% Route pattern forwards that to SME. 00:20:21.460 --> 00:20:26.635 align:middle line:84% SME gets the calling number as e164, called as e164. 00:20:26.635 --> 00:20:29.260 align:middle line:90% SME forwards that down to VCUBE. 00:20:29.260 --> 00:20:36.070 align:middle line:84% VCUBE receives calling number as e164, called as e164. 00:20:36.070 --> 00:20:40.660 align:middle line:84% So once it comes down to R1, what is it going to match? 00:20:40.660 --> 00:20:43.000 align:middle line:84% We don't want to match the default dial peer. 00:20:43.000 --> 00:20:45.440 align:middle line:84% So let's in fact, try and make the call first. 00:20:45.440 --> 00:20:47.530 align:middle line:90% So I'm going to go back here. 00:20:47.530 --> 00:20:49.090 align:middle line:90% This is PSTN. 00:20:49.090 --> 00:20:50.870 align:middle line:90% Let's take this here. 00:20:50.870 --> 00:20:58.690 align:middle line:84% Let's go to Jabber 2, which is my Steve Rogers, and go here. 00:20:58.690 --> 00:21:06.070 align:middle line:84% And let's dial 9-525-2222 and hit Enter. 00:21:06.070 --> 00:21:08.260 align:middle line:90% So I'm dialing this. 00:21:08.260 --> 00:21:18.190 align:middle line:84% If I look at R1 and do a show call active voice brief, 00:21:18.190 --> 00:21:19.225 align:middle line:90% what do I see? 00:21:19.225 --> 00:21:21.100 align:middle line:84% It's obviously that I've done the call hasn't 00:21:21.100 --> 00:21:22.122 align:middle line:90% come in here yet. 00:21:22.122 --> 00:21:23.080 align:middle line:90% It takes a bit of time. 00:21:23.080 --> 00:21:26.300 align:middle line:90% Just give it some time. 00:21:26.300 --> 00:21:28.240 align:middle line:90% So now I see some call-legs. 00:21:28.240 --> 00:21:36.470 align:middle line:84% Look at the call leg for dial peer is zero. 00:21:36.470 --> 00:21:39.290 align:middle line:84% So inbound it matched dial peer zero. 00:21:39.290 --> 00:21:42.860 align:middle line:84% Outbound it matched dial peer 10. 00:21:42.860 --> 00:21:45.920 align:middle line:84% We don't want to match inbound dial peer zero. 00:21:45.920 --> 00:21:49.460 align:middle line:84% So what I'm going to do is, if you remember for HQ site, 00:21:49.460 --> 00:21:51.530 align:middle line:84% we had created an inbound dial peer. 00:21:51.530 --> 00:21:53.150 align:middle line:90% I think it was dial peer 1,000. 00:21:53.150 --> 00:21:54.120 align:middle line:90% Let's go and check. 00:21:54.120 --> 00:22:03.500 align:middle line:84% Show run section dial-peer 1,000 or dial peer voice 1,000. 00:22:03.500 --> 00:22:05.090 align:middle line:90% This was the incoming dial peer. 00:22:05.090 --> 00:22:09.020 align:middle line:84% It was matching based on incoming calling number, which 00:22:09.020 --> 00:22:11.630 align:middle line:84% is calling e164 pattern-map 1,000. 00:22:11.630 --> 00:22:18.240 align:middle line:84% So let's go to show run section map 1,000. 00:22:18.240 --> 00:22:21.000 align:middle line:84% So this is matching the calling number from HQ only. 00:22:21.000 --> 00:22:23.620 align:middle line:84% All I'm going to do is go down inside this. 00:22:23.620 --> 00:22:33.540 align:middle line:84% So go to voice class e164 pattern-map 1,000 and add e164 00:22:33.540 --> 00:22:39.480 align:middle line:90% plus 1-972-303.... 00:22:39.480 --> 00:22:40.110 align:middle line:90% Enter. 00:22:40.110 --> 00:22:43.260 align:middle line:84% So now if I look at my e164 pattern-map, 00:22:43.260 --> 00:22:44.650 align:middle line:90% it has two numbers. 00:22:44.650 --> 00:22:47.310 align:middle line:84% So if the calling number is from HQ 00:22:47.310 --> 00:22:49.440 align:middle line:84% or if the calling number is from site B, 00:22:49.440 --> 00:22:51.150 align:middle line:90% it matches this pattern-map. 00:22:51.150 --> 00:22:55.060 align:middle line:84% And this pattern map has been called inside the dial 00:22:55.060 --> 00:22:58.290 align:middle line:84% peer 1,000 as the incoming calling 00:22:58.290 --> 00:23:01.290 align:middle line:84% e164 pattern map, which means that this dial peer is 00:23:01.290 --> 00:23:03.600 align:middle line:90% going to match for incoming. 00:23:03.600 --> 00:23:05.460 align:middle line:84% So let's just try remaking the call 00:23:05.460 --> 00:23:07.260 align:middle line:84% and checking which dial peer it's matching. 00:23:07.260 --> 00:23:12.690 align:middle line:84% Let's cancel this and redial 9-515-111-- 00:23:12.690 --> 00:23:17.700 align:middle line:90% oh, it's 525-2222. 00:23:17.700 --> 00:23:24.770 align:middle line:84% Let's redial that, go back to R1 and check show call 00:23:24.770 --> 00:23:27.830 align:middle line:90% active voice brief. 00:23:27.830 --> 00:23:28.790 align:middle line:90% Give it some time. 00:23:28.790 --> 00:23:31.550 align:middle line:84% Right now it doesn't show any call legs, again, 00:23:31.550 --> 00:23:36.320 align:middle line:84% because of CPU and memory capacity that we have. 00:23:36.320 --> 00:23:40.760 align:middle line:84% It takes a few seconds for it to actually show up. 00:23:40.760 --> 00:23:42.097 align:middle line:90% So now, I still-- 00:23:42.097 --> 00:23:43.180 align:middle line:90% now, I have two call legs. 00:23:43.180 --> 00:23:45.790 align:middle line:84% And look at my first incoming call leg. 00:23:45.790 --> 00:23:53.140 align:middle line:84% I see dial peer 1,000 here, which you can see here. 00:23:53.140 --> 00:23:55.960 align:middle line:84% That's my incoming call leg, and that's my outgoing call 00:23:55.960 --> 00:23:58.110 align:middle line:90% leg, which is 10. 00:23:58.110 --> 00:24:00.510 align:middle line:90% So incoming now it's matching. 00:24:00.510 --> 00:24:03.060 align:middle line:84% Now once it matches the incoming, 00:24:03.060 --> 00:24:05.340 align:middle line:90% I want to make changes. 00:24:05.340 --> 00:24:09.660 align:middle line:84% What does the PSTN expect as the calling number? 00:24:09.660 --> 00:24:12.090 align:middle line:84% Calling number should be 10 digits. 00:24:12.090 --> 00:24:17.080 align:middle line:84% Called number should be, I believe, it's 11 digits. 00:24:17.080 --> 00:24:20.040 align:middle line:90% Let's go and check again. 00:24:20.040 --> 00:24:24.140 align:middle line:84% So far local calls and national calls, the called number 00:24:24.140 --> 00:24:26.900 align:middle line:84% should be 1 followed by 3 digits and then followed 00:24:26.900 --> 00:24:29.460 align:middle line:84% by 7 digits, which means 11 digits. 00:24:29.460 --> 00:24:32.790 align:middle line:90% So let's go back here and check. 00:24:32.790 --> 00:24:34.760 align:middle line:84% Let's first recheck our dial peer 00:24:34.760 --> 00:24:37.490 align:middle line:90% 1,000, which is the incoming. 00:24:37.490 --> 00:24:40.020 align:middle line:84% I have a translation profile there also, 00:24:40.020 --> 00:24:41.930 align:middle line:90% which is for incoming from SME. 00:24:41.930 --> 00:24:43.280 align:middle line:90% Let's check what that is. 00:24:43.280 --> 00:24:45.940 align:middle line:90% Show run section voice. 00:24:45.940 --> 00:24:48.650 align:middle line:90% 00:24:48.650 --> 00:24:57.760 align:middle line:84% Let's do translation profile, voice translation profile. 00:24:57.760 --> 00:25:02.550 align:middle line:90% 00:25:02.550 --> 00:25:04.490 align:middle line:84% So I have a translation profile from SME 00:25:04.490 --> 00:25:07.970 align:middle line:84% which is matching translate called 21. 00:25:07.970 --> 00:25:09.110 align:middle line:90% Let's check that. 00:25:09.110 --> 00:25:13.400 align:middle line:90% Show run section voice. 00:25:13.400 --> 00:25:18.090 align:middle line:90% Let's do rule 21. 00:25:18.090 --> 00:25:23.046 align:middle line:84% So that matches international calls. 00:25:23.046 --> 00:25:30.320 align:middle line:84% So if the called number is the international dial number, 00:25:30.320 --> 00:25:32.600 align:middle line:90% it should match that. 00:25:32.600 --> 00:25:37.630 align:middle line:90% So that is for international. 00:25:37.630 --> 00:25:40.510 align:middle line:84% We are talking about local calls right now. 00:25:40.510 --> 00:25:43.230 align:middle line:84% So we don't really need to do anything on the incoming, 00:25:43.230 --> 00:25:46.110 align:middle line:84% at least right now for the international-- 00:25:46.110 --> 00:25:47.610 align:middle line:90% for the local and national. 00:25:47.610 --> 00:25:49.980 align:middle line:84% This is only matching the international numbers 00:25:49.980 --> 00:25:54.060 align:middle line:84% for called which is changing it to 011. 00:25:54.060 --> 00:25:57.150 align:middle line:84% The same thing is going to apply for site B also. 00:25:57.150 --> 00:25:59.700 align:middle line:84% But right now, we're talking about just local and national. 00:25:59.700 --> 00:26:02.580 align:middle line:84% So what I'm going to do is check my outbound dial peer now. 00:26:02.580 --> 00:26:07.644 align:middle line:90% Dial-peer voice 10. 00:26:07.644 --> 00:26:17.760 align:middle line:84% I think it's dial, dial-peer voice 10 voip. 00:26:17.760 --> 00:26:22.410 align:middle line:84% So here I have an outgoing local and national profile. 00:26:22.410 --> 00:26:24.390 align:middle line:90% Let's go and check that. 00:26:24.390 --> 00:26:27.990 align:middle line:84% Show run section voice translation profile. 00:26:27.990 --> 00:26:31.710 align:middle line:84% So that matches calling and called 10 and 11. 00:26:31.710 --> 00:26:32.640 align:middle line:90% Let's check that. 00:26:32.640 --> 00:26:38.080 align:middle line:84% Let's check the rule for rule 10. 00:26:38.080 --> 00:26:41.660 align:middle line:90% That matches 12-9. 00:26:41.660 --> 00:26:46.180 align:middle line:90% 00:26:46.180 --> 00:26:49.450 align:middle line:84% So that is stripping off the plus 1, 00:26:49.450 --> 00:26:57.090 align:middle line:84% and called is stripping off the plus and adding the 1. 00:26:57.090 --> 00:26:58.820 align:middle line:90% So this basically means-- 00:26:58.820 --> 00:27:01.890 align:middle line:90% 00:27:01.890 --> 00:27:04.650 align:middle line:84% this basically means that for local and national calls, 00:27:04.650 --> 00:27:05.920 align:middle line:90% I don't have to do anything. 00:27:05.920 --> 00:27:07.260 align:middle line:90% I just match the dial peer. 00:27:07.260 --> 00:27:09.870 align:middle line:84% It's already been taken care of from the HQ site. 00:27:09.870 --> 00:27:14.320 align:middle line:84% If I actually go and do a debug ccsip messages-- 00:27:14.320 --> 00:27:25.800 align:middle line:84% let's go back first here and make that call 9-525-2222. 00:27:25.800 --> 00:27:28.890 align:middle line:90% Go back to 1 and do a debug. 00:27:28.890 --> 00:27:31.500 align:middle line:90% We should see that it matches-- 00:27:31.500 --> 00:27:34.300 align:middle line:84% it's matching the incoming dial peer 1,000. 00:27:34.300 --> 00:27:36.900 align:middle line:84% For outgoing is matching dial peer 10. 00:27:36.900 --> 00:27:38.700 align:middle line:84% In the dial peer 10, we had already 00:27:38.700 --> 00:27:40.170 align:middle line:84% done the translation profile that 00:27:40.170 --> 00:27:45.480 align:middle line:84% matches anything that begins with plus 00:27:45.480 --> 00:27:49.140 align:middle line:84% and changes it to 10 digits for calling and changes the 00:27:49.140 --> 00:27:50.860 align:middle line:90% called to 11 digits. 00:27:50.860 --> 00:27:56.438 align:middle line:84% So if I check here now, let's look at the-- 00:27:56.438 --> 00:27:58.160 align:middle line:90% let's scroll back up. 00:27:58.160 --> 00:28:01.085 align:middle line:84% I'm going to go back first and do an un-- 00:28:01.085 --> 00:28:04.210 align:middle line:90% or let's pick up the call. 00:28:04.210 --> 00:28:10.920 align:middle line:84% So I pick up the call, go back to R1, and do un all. 00:28:10.920 --> 00:28:13.590 align:middle line:90% 00:28:13.590 --> 00:28:15.780 align:middle line:90% And let's disconnect. 00:28:15.780 --> 00:28:19.150 align:middle line:90% 00:28:19.150 --> 00:28:21.720 align:middle line:84% Go back to R1, and let's scroll back up. 00:28:21.720 --> 00:28:24.570 align:middle line:90% What did we receive from SME? 00:28:24.570 --> 00:28:32.560 align:middle line:84% So let's look at our incoming request. 00:28:32.560 --> 00:28:35.100 align:middle line:90% 00:28:35.100 --> 00:28:40.620 align:middle line:84% So let's scroll back up all the way up. 00:28:40.620 --> 00:28:49.040 align:middle line:84% Yeah, it should be somewhere here. 00:28:49.040 --> 00:28:50.220 align:middle line:90% Yeah, here you go. 00:28:50.220 --> 00:28:56.210 align:middle line:84% So incoming invite, e164 as the called, 00:28:56.210 --> 00:29:00.350 align:middle line:84% incoming as the calling, which is both are e164. 00:29:00.350 --> 00:29:02.870 align:middle line:84% What the cube does, he sends the invite 00:29:02.870 --> 00:29:08.360 align:middle line:84% to PSTN where he sends the called number as 1 00:29:08.360 --> 00:29:13.730 align:middle line:84% followed by 10 digits, 972, so basically 11 digits. 00:29:13.730 --> 00:29:17.340 align:middle line:84% Calling becomes 10 digits, which you can see here. 00:29:17.340 --> 00:29:19.433 align:middle line:84% So it meets the requirement of the question. 00:29:19.433 --> 00:29:21.350 align:middle line:84% So we didn't really have to do any translation 00:29:21.350 --> 00:29:23.900 align:middle line:84% rules, no translation profiles, because when 00:29:23.900 --> 00:29:26.750 align:middle line:84% we did that for HQ, it applies for site B 00:29:26.750 --> 00:29:29.915 align:middle line:90% also because we made it really-- 00:29:29.915 --> 00:29:35.000 align:middle line:84% we didn't apply the rule as plus backslash plus with a set 00:29:35.000 --> 00:29:36.650 align:middle line:90% calling for 408. 00:29:36.650 --> 00:29:39.080 align:middle line:90% We set 2-9.. 00:29:39.080 --> 00:29:42.740 align:middle line:84% So that means anything that begins with 2-9.. 00:29:42.740 --> 00:29:43.740 align:middle line:90% it matches that. 00:29:43.740 --> 00:29:45.710 align:middle line:84% So it matches site B. It matches HQ. 00:29:45.710 --> 00:29:47.730 align:middle line:90% It matches everyone. 00:29:47.730 --> 00:29:51.510 align:middle line:84% So my local calls is meeting the requirements. 00:29:51.510 --> 00:29:54.780 align:middle line:84% Let's go back to here and make a national call. 00:29:54.780 --> 00:29:55.970 align:middle line:90% So how do I dial national? 00:29:55.970 --> 00:30:00.410 align:middle line:84% 9 followed by 1, then the area code 408, then 00:30:00.410 --> 00:30:05.030 align:middle line:84% the subscriber number 515-1111, which is a PSTN and address. 00:30:05.030 --> 00:30:06.230 align:middle line:90% Let's dial this. 00:30:06.230 --> 00:30:10.355 align:middle line:84% Go back here and do a debug ccsip messages. 00:30:10.355 --> 00:30:13.950 align:middle line:90% 00:30:13.950 --> 00:30:17.570 align:middle line:84% And once it comes in here, I will do an undebug all. 00:30:17.570 --> 00:30:23.291 align:middle line:90% 00:30:23.291 --> 00:30:25.000 align:middle line:90% All right, so I have it here. 00:30:25.000 --> 00:30:31.950 align:middle line:84% Let's do undebug all, and let's scroll back up to the invite. 00:30:31.950 --> 00:30:35.250 align:middle line:84% So I received e164 as the called, 00:30:35.250 --> 00:30:38.130 align:middle line:90% e164 as the calling from SME. 00:30:38.130 --> 00:30:45.350 align:middle line:84% I sent across 11 digits as the called and 10 digits 00:30:45.350 --> 00:30:49.260 align:middle line:84% as the calling, which meets the requirement of national also. 00:30:49.260 --> 00:30:51.540 align:middle line:90% So I don't have to do anything. 00:30:51.540 --> 00:30:53.120 align:middle line:90% Now let's test international. 00:30:53.120 --> 00:30:55.280 align:middle line:84% For international, again, it's for incoming, 00:30:55.280 --> 00:30:58.250 align:middle line:84% it's going to match the same dial peer, dial peer 1,000. 00:30:58.250 --> 00:31:06.440 align:middle line:84% And in the dial peer 1,000, we have a translation profile 00:31:06.440 --> 00:31:12.960 align:middle line:84% for incoming from SME which matches the rule 21 for called, 00:31:12.960 --> 00:31:19.740 align:middle line:84% which says if I'm dialing Hong Kong or if I'm dialing UK, 00:31:19.740 --> 00:31:23.020 align:middle line:90% prepend 011 to that number. 00:31:23.020 --> 00:31:28.620 align:middle line:84% So strip off the plus and prepend 011 as the calling-- 00:31:28.620 --> 00:31:30.000 align:middle line:90% as the called. 00:31:30.000 --> 00:31:33.560 align:middle line:84% For calling, I'm not doing anything. 00:31:33.560 --> 00:31:37.040 align:middle line:90% I'm not making any changes. 00:31:37.040 --> 00:31:43.280 align:middle line:84% So because what is coming in from-- 00:31:43.280 --> 00:31:51.410 align:middle line:84% what is coming in from the SME calling e164? 00:31:51.410 --> 00:31:54.170 align:middle line:84% I'm not making any changes on the outbound dial peer 00:31:54.170 --> 00:31:56.840 align:middle line:90% also for international. 00:31:56.840 --> 00:32:02.210 align:middle line:84% But you can see here by doing short on section dial-peer 00:32:02.210 --> 00:32:07.720 align:middle line:84% voice 10 voip, I have destination pattern 00:32:07.720 --> 00:32:09.610 align:middle line:90% matching map 10. 00:32:09.610 --> 00:32:15.130 align:middle line:84% If I look at the show run section map 10, 00:32:15.130 --> 00:32:23.350 align:middle line:90% it matches plus 12-9..2-9..... 00:32:23.350 --> 00:32:25.210 align:middle line:90% Which only matches what? 00:32:25.210 --> 00:32:33.200 align:middle line:84% It matches the anything which is with plus 1 and then 00:32:33.200 --> 00:32:36.770 align:middle line:84% area code and then the subscriber number. 00:32:36.770 --> 00:32:41.018 align:middle line:84% So for dial peer 10, this was for local and national. 00:32:41.018 --> 00:32:42.310 align:middle line:90% This was not for international. 00:32:42.310 --> 00:32:45.370 align:middle line:84% For international, we were using dial peer 20 00:32:45.370 --> 00:32:47.080 align:middle line:90% which we had done earlier. 00:32:47.080 --> 00:32:51.880 align:middle line:84% I think it was dial peer 20, which you can see here. 00:32:51.880 --> 00:32:54.730 align:middle line:84% In the dial peer 20, I'm matching the map 20. 00:32:54.730 --> 00:32:59.890 align:middle line:84% And if I look at the map 20, this matches 011 as the called 00:32:59.890 --> 00:33:03.062 align:middle line:84% number, so only if my called number is 011. 00:33:03.062 --> 00:33:04.270 align:middle line:90% And where am I changing that? 00:33:04.270 --> 00:33:05.290 align:middle line:90% On the incoming. 00:33:05.290 --> 00:33:08.830 align:middle line:84% So on the incoming, I am changing the called number 00:33:08.830 --> 00:33:12.640 align:middle line:84% to 011 and then the variable digits and then matching that 00:33:12.640 --> 00:33:15.970 align:middle line:84% on dial peer 20, which matches 011T, 00:33:15.970 --> 00:33:18.100 align:middle line:84% which means that dial peer 20 is going to match 00:33:18.100 --> 00:33:18.850 align:middle line:90% for international. 00:33:18.850 --> 00:33:22.150 align:middle line:84% So for local and international-- for local and national, 00:33:22.150 --> 00:33:24.010 align:middle line:90% incoming would be 1,000. 00:33:24.010 --> 00:33:26.050 align:middle line:90% Outgoing would be dial peer 10. 00:33:26.050 --> 00:33:27.940 align:middle line:84% For international, incoming is going 00:33:27.940 --> 00:33:29.350 align:middle line:90% to be the dial peer 1,000. 00:33:29.350 --> 00:33:31.960 align:middle line:90% Outgoing would be dial peer 20. 00:33:31.960 --> 00:33:33.700 align:middle line:90% Let's check that. 00:33:33.700 --> 00:33:36.840 align:middle line:90% Let's make the call and check. 00:33:36.840 --> 00:33:43.925 align:middle line:84% So 9011442085554444, and let's do it with a pound. 00:33:43.925 --> 00:33:46.930 align:middle line:90% 00:33:46.930 --> 00:33:51.290 align:middle line:84% And let's go to 1 and do a debug ccsip messages. 00:33:51.290 --> 00:34:04.170 align:middle line:90% 00:34:04.170 --> 00:34:07.640 align:middle line:90% And let's do an un all. 00:34:07.640 --> 00:34:16.570 align:middle line:84% We can cancel this now and go back and check the sent invite. 00:34:16.570 --> 00:34:18.719 align:middle line:84% If I look at, this is the receive invite. 00:34:18.719 --> 00:34:22.050 align:middle line:90% Incoming was-- called was e164. 00:34:22.050 --> 00:34:24.239 align:middle line:90% Calling was e164. 00:34:24.239 --> 00:34:26.639 align:middle line:90% So I match dial peer 1,000. 00:34:26.639 --> 00:34:33.429 align:middle line:84% And on outbound, I changed the called to 011 country code 00:34:33.429 --> 00:34:34.870 align:middle line:90% and then the number. 00:34:34.870 --> 00:34:37.570 align:middle line:90% Calling was still e164. 00:34:37.570 --> 00:34:41.210 align:middle line:84% So it meets the requirement of the question. 00:34:41.210 --> 00:34:42.940 align:middle line:84% So obviously, the same thing we should 00:34:42.940 --> 00:34:45.429 align:middle line:84% do on R2 because the configuration 00:34:45.429 --> 00:34:46.900 align:middle line:90% is not replicated. 00:34:46.900 --> 00:34:49.090 align:middle line:84% We must do exactly the same thing on R2. 00:34:49.090 --> 00:34:50.220 align:middle line:90% So let's go to-- 00:34:50.220 --> 00:34:53.409 align:middle line:90% 00:34:53.409 --> 00:34:54.730 align:middle line:90% let's go to config t. 00:34:54.730 --> 00:34:59.830 align:middle line:90% 00:34:59.830 --> 00:35:04.060 align:middle line:84% I believe we only made changes to one thing, which 00:35:04.060 --> 00:35:06.960 align:middle line:90% was map 1,000. 00:35:06.960 --> 00:35:12.150 align:middle line:90% We added this. 00:35:12.150 --> 00:35:12.945 align:middle line:90% Let's go to R2. 00:35:12.945 --> 00:35:22.920 align:middle line:90% 00:35:22.920 --> 00:35:28.200 align:middle line:84% So if I look at show run section map 1,000, 00:35:28.200 --> 00:35:32.400 align:middle line:84% I see my e164-pattern-map, which has both the numbers. 00:35:32.400 --> 00:35:34.470 align:middle line:84% That's the only change that I had done. 00:35:34.470 --> 00:35:37.750 align:middle line:84% So with this, we've completed all our requirements. 00:35:37.750 --> 00:35:41.310 align:middle line:84% So you see on the CUBE side, I didn't really 00:35:41.310 --> 00:35:42.990 align:middle line:90% have to do much changes. 00:35:42.990 --> 00:35:46.140 align:middle line:84% If you keep it generally, if you keep your dial peers 00:35:46.140 --> 00:35:49.650 align:middle line:84% and your translation rules not specific, 00:35:49.650 --> 00:35:53.430 align:middle line:84% then you can actually reuse that translation rules for both HQ 00:35:53.430 --> 00:35:54.450 align:middle line:90% and site B. 00:35:54.450 --> 00:35:57.900 align:middle line:84% I don't have to rebuild separate translation 00:35:57.900 --> 00:36:03.860 align:middle line:84% rules, separate dial peers for my site B. With this, 00:36:03.860 --> 00:36:05.860 align:middle line:84% we've completed our task requirement. 00:36:05.860 --> 00:36:07.850 align:middle line:84% I hope this video was informative for you, 00:36:07.850 --> 00:36:10.500 align:middle line:90% and thank you for watching. 00:36:10.500 --> 00:36:11.000 align:middle line:90%