WEBVTT 00:00:00.000 --> 00:00:04.293 align:middle line:90% 00:00:04.293 --> 00:00:07.155 align:middle line:90% [AUDIO LOGO] 00:00:07.155 --> 00:00:10.020 align:middle line:90% 00:00:10.020 --> 00:00:12.420 align:middle line:90% Hello, and welcome to INE. 00:00:12.420 --> 00:00:14.400 align:middle line:84% Today, in this video, we will look at Section 2 00:00:14.400 --> 00:00:17.910 align:middle line:84% Dial Plan Part 4, basically Task 2.9, 00:00:17.910 --> 00:00:19.800 align:middle line:90% where we would configure ILS. 00:00:19.800 --> 00:00:21.990 align:middle line:84% Here in this task, it says configure ILS 00:00:21.990 --> 00:00:26.130 align:middle line:84% to allow HQ and site B clusters to call each other using URI. 00:00:26.130 --> 00:00:27.520 align:middle line:90% SME must be the hub. 00:00:27.520 --> 00:00:30.600 align:middle line:84% And HQ and site B clusters would be the spoke. 00:00:30.600 --> 00:00:34.290 align:middle line:84% All calls must display URI as the calling number, 00:00:34.290 --> 00:00:38.190 align:middle line:84% verify by dialing steve-rogers@ine.com from 00:00:38.190 --> 00:00:40.020 align:middle line:90% the user Tony Stark. 00:00:40.020 --> 00:00:43.380 align:middle line:84% Verify also by dialing tonystark@ine.com 00:00:43.380 --> 00:00:46.080 align:middle line:90% from the user Steve Rogers. 00:00:46.080 --> 00:00:50.640 align:middle line:84% Also ensure that Tony Stark advertises an alternate number 00:00:50.640 --> 00:00:54.570 align:middle line:84% 72022003 and this pattern must be learned 00:00:54.570 --> 00:00:58.950 align:middle line:84% by site B. Site B user Steve Rogers must be able to dial 00:00:58.950 --> 00:01:00.060 align:middle line:90% this alternate number. 00:01:00.060 --> 00:01:03.810 align:middle line:84% In short, display always shows URI. 00:01:03.810 --> 00:01:05.160 align:middle line:90% So let's quickly do this. 00:01:05.160 --> 00:01:06.780 align:middle line:84% Now the first thing before we even 00:01:06.780 --> 00:01:08.880 align:middle line:84% do wireless, the first thing we have to do 00:01:08.880 --> 00:01:11.730 align:middle line:84% is we have to understand that there is no physical phone 00:01:11.730 --> 00:01:13.110 align:middle line:90% anymore in the lab exam. 00:01:13.110 --> 00:01:14.250 align:middle line:90% We're using Jabber. 00:01:14.250 --> 00:01:17.800 align:middle line:84% So Jabber would not support URI dialing by default. 00:01:17.800 --> 00:01:20.200 align:middle line:84% So we have to modify the Jabber config file. 00:01:20.200 --> 00:01:22.900 align:middle line:84% So we would have to do that first. 00:01:22.900 --> 00:01:29.130 align:middle line:84% So basically, allowing our users to dial URI from Jabber Let's 00:01:29.130 --> 00:01:31.810 align:middle line:90% quickly do that part first. 00:01:31.810 --> 00:01:40.470 align:middle line:84% So first thing what I'm going to do is go to let's go to my-- 00:01:40.470 --> 00:01:42.510 align:middle line:90% let's close all these Windows. 00:01:42.510 --> 00:01:45.000 align:middle line:84% We have Jabber to Steve Rogers here. 00:01:45.000 --> 00:01:49.050 align:middle line:90% We have Tony Stark here. 00:01:49.050 --> 00:01:52.720 align:middle line:90% And let's go to the browser. 00:01:52.720 --> 00:01:57.000 align:middle line:84% Let's go to cisco.com and get the base Jabber config file 00:01:57.000 --> 00:02:00.010 align:middle line:84% because it's very difficult for us to actually type that out. 00:02:00.010 --> 00:02:01.950 align:middle line:84% So I'm just going to go to cisco.com and find 00:02:01.950 --> 00:02:06.970 align:middle line:84% the document to be able to create the Jabber config file. 00:02:06.970 --> 00:02:13.895 align:middle line:84% So first thing what I'm going to do is go to cisco.com. 00:02:13.895 --> 00:02:19.300 align:middle line:84% Let's go to support, go to all products, 00:02:19.300 --> 00:02:26.770 align:middle line:84% unified communication, Jabber for Windows scroll 00:02:26.770 --> 00:02:28.990 align:middle line:90% down to Configuration. 00:02:28.990 --> 00:02:34.300 align:middle line:84% And then look for multi-domain support in Cisco Jabber. 00:02:34.300 --> 00:02:35.260 align:middle line:90% Click on that. 00:02:35.260 --> 00:02:39.430 align:middle line:84% Scroll all the way down to the deployment and installation 00:02:39.430 --> 00:02:40.930 align:middle line:90% guide. 00:02:40.930 --> 00:02:42.100 align:middle line:90% Open that up. 00:02:42.100 --> 00:02:49.400 align:middle line:84% And let's search for UTF in the document. 00:02:49.400 --> 00:02:50.870 align:middle line:90% Just keep searching that. 00:02:50.870 --> 00:02:55.410 align:middle line:84% You should find this config here. 00:02:55.410 --> 00:02:57.350 align:middle line:90% So this is what we need. 00:02:57.350 --> 00:03:02.510 align:middle line:84% We need to create this on our Notepad, 00:03:02.510 --> 00:03:04.280 align:middle line:84% basically we need to create this file. 00:03:04.280 --> 00:03:06.260 align:middle line:84% And then we would add-- we would basically 00:03:06.260 --> 00:03:08.880 align:middle line:90% enable SIP URI dialing. 00:03:08.880 --> 00:03:11.090 align:middle line:90% So let's do that. 00:03:11.090 --> 00:03:15.460 align:middle line:84% So first thing what I'm going to do is let's open up-- 00:03:15.460 --> 00:03:16.870 align:middle line:90% go to Jabber1. 00:03:16.870 --> 00:03:19.360 align:middle line:90% Let's open up Notepad. 00:03:19.360 --> 00:03:21.910 align:middle line:90% I believe that should be-- 00:03:21.910 --> 00:03:24.700 align:middle line:90% let's close this. 00:03:24.700 --> 00:03:28.220 align:middle line:90% It should be on the desktop. 00:03:28.220 --> 00:03:31.880 align:middle line:84% So you go inside the Applications folder 00:03:31.880 --> 00:03:33.420 align:middle line:90% and open up Notepad. 00:03:33.420 --> 00:03:44.550 align:middle line:90% 00:03:44.550 --> 00:03:46.005 align:middle line:90% Let's open a new file. 00:03:46.005 --> 00:03:49.450 align:middle line:90% 00:03:49.450 --> 00:03:55.720 align:middle line:84% And here is where I would create my Jabber config file. 00:03:55.720 --> 00:03:57.370 align:middle line:84% Now obviously in the lab exam, you 00:03:57.370 --> 00:04:00.070 align:middle line:84% would be able to copy paste from the document. 00:04:00.070 --> 00:04:03.680 align:middle line:84% Here in our lab, we would not be able to copy paste. 00:04:03.680 --> 00:04:04.930 align:middle line:90% I'm just going to type it out. 00:04:04.930 --> 00:04:07.570 align:middle line:90% 00:04:07.570 --> 00:04:10.862 align:middle line:90% Let me quickly take this to-- 00:04:10.862 --> 00:04:13.900 align:middle line:90% 00:04:13.900 --> 00:04:17.860 align:middle line:84% my other screen, so that I can do a copy paste, 00:04:17.860 --> 00:04:19.370 align:middle line:90% I can type it out. 00:04:19.370 --> 00:04:27.490 align:middle line:84% So first thing what we need is a question XML version 00:04:27.490 --> 00:04:33.470 align:middle line:90% equals double quotes 1.0. 00:04:33.470 --> 00:04:47.480 align:middle line:84% And encoding equals UTF-8 that's my first line. 00:04:47.480 --> 00:04:58.020 align:middle line:84% The second line was config version equals 1.0. 00:04:58.020 --> 00:05:00.780 align:middle line:84% And the last thing is close the config. 00:05:00.780 --> 00:05:04.810 align:middle line:90% So /config and close this. 00:05:04.810 --> 00:05:10.770 align:middle line:84% So this is my base what I actually copied from here. 00:05:10.770 --> 00:05:13.680 align:middle line:84% Once I have this, the next thing that I would do 00:05:13.680 --> 00:05:17.340 align:middle line:90% is go inside this. 00:05:17.340 --> 00:05:22.790 align:middle line:84% So between the configs, I would go and type policies. 00:05:22.790 --> 00:05:25.880 align:middle line:90% 00:05:25.880 --> 00:05:28.780 align:middle line:90% And again, type /policies. 00:05:28.780 --> 00:05:31.560 align:middle line:90% 00:05:31.560 --> 00:05:37.260 align:middle line:84% And between that, I would enable SIP URI dialing. 00:05:37.260 --> 00:05:40.200 align:middle line:90% Now for that, the command is-- 00:05:40.200 --> 00:05:44.270 align:middle line:90% so let's type here. 00:05:44.270 --> 00:05:54.080 align:middle line:84% Enable SIP URI dialing, close that. 00:05:54.080 --> 00:05:58.340 align:middle line:84% Now if you notice one thing, the dialing is double L. So again, 00:05:58.340 --> 00:06:03.710 align:middle line:84% it's basically, British English versus the American English 00:06:03.710 --> 00:06:07.730 align:middle line:84% because sometimes we write dialing as D-I-A-L-I-N-G. 00:06:07.730 --> 00:06:11.900 align:middle line:84% So here as for the documentation is concerned, it is double L. 00:06:11.900 --> 00:06:23.540 align:middle line:84% So enable SIP, this should be SIP URI so URI dialing. 00:06:23.540 --> 00:06:27.110 align:middle line:90% So enable SIP URI-- 00:06:27.110 --> 00:06:28.370 align:middle line:90% seems like it's wrong. 00:06:28.370 --> 00:06:31.310 align:middle line:90% 00:06:31.310 --> 00:06:33.730 align:middle line:90% So enable SIP URI dialing. 00:06:33.730 --> 00:06:40.480 align:middle line:84% Set that to true and then, again, close this out. 00:06:40.480 --> 00:06:48.420 align:middle line:90% So enable SIP URI dialing. 00:06:48.420 --> 00:06:50.010 align:middle line:90% And close this out. 00:06:50.010 --> 00:06:50.560 align:middle line:90% That's it. 00:06:50.560 --> 00:06:54.040 align:middle line:84% That's all we need in our Jabber config file. 00:06:54.040 --> 00:06:57.850 align:middle line:90% So SIP URI dialing. 00:06:57.850 --> 00:07:03.400 align:middle line:84% So open it, set it to true, and then close it out. 00:07:03.400 --> 00:07:06.860 align:middle line:90% Let's save this file. 00:07:06.860 --> 00:07:10.810 align:middle line:90% So let's save. 00:07:10.810 --> 00:07:12.210 align:middle line:90% Save it on desktop. 00:07:12.210 --> 00:07:14.870 align:middle line:90% 00:07:14.870 --> 00:07:16.050 align:middle line:90% Let's set this to-- 00:07:16.050 --> 00:07:28.423 align:middle line:90% 00:07:28.423 --> 00:07:28.923 align:middle line:90% XML. 00:07:28.923 --> 00:07:38.910 align:middle line:90% 00:07:38.910 --> 00:07:41.844 align:middle line:84% So the name should be jabber-config.xml. 00:07:41.844 --> 00:07:46.580 align:middle line:90% 00:07:46.580 --> 00:07:49.570 align:middle line:90% Let's save this. 00:07:49.570 --> 00:07:54.400 align:middle line:84% So now I have my Jabber config file, which you can see here. 00:07:54.400 --> 00:07:56.750 align:middle line:90% Let's go to Properties. 00:07:56.750 --> 00:07:58.790 align:middle line:84% As you can see, it's an XML file, 00:07:58.790 --> 00:08:03.330 align:middle line:84% jabber-config.xml Now the file name should be the same. 00:08:03.330 --> 00:08:05.310 align:middle line:84% I mean, if you don't give the same name, 00:08:05.310 --> 00:08:07.268 align:middle line:84% let's say if you give some other name, it's OK. 00:08:07.268 --> 00:08:11.210 align:middle line:84% But you'll have to go and add that to all your users 00:08:11.210 --> 00:08:13.020 align:middle line:90% as your Jabber config file. 00:08:13.020 --> 00:08:16.130 align:middle line:84% But if you use the default name, which is jabber-config, 00:08:16.130 --> 00:08:21.180 align:middle line:84% then you don't really need to add this to the users. 00:08:21.180 --> 00:08:25.640 align:middle line:84% So once I have this file, let's go back to our call manager. 00:08:25.640 --> 00:08:28.040 align:middle line:84% Now we don't have subscribers, we only have publisher. 00:08:28.040 --> 00:08:30.770 align:middle line:84% In the lab exam, you would have the publisher and subscriber. 00:08:30.770 --> 00:08:32.480 align:middle line:84% You would have to upload this file 00:08:32.480 --> 00:08:34.820 align:middle line:84% to both your publisher and subscriber 00:08:34.820 --> 00:08:37.010 align:middle line:90% and restart your TFTP service. 00:08:37.010 --> 00:08:39.950 align:middle line:84% So what I'm going to do is just go to my publisher. 00:08:39.950 --> 00:08:43.200 align:middle line:84% I only have one publisher, I don't have subscriber. 00:08:43.200 --> 00:08:46.070 align:middle line:84% So I would only do it on my publisher of HQ. 00:08:46.070 --> 00:08:48.450 align:middle line:84% And same thing, you would do it for site B also. 00:08:48.450 --> 00:08:49.715 align:middle line:90% So let's go to site B also. 00:08:49.715 --> 00:08:52.810 align:middle line:90% 00:08:52.810 --> 00:08:54.330 align:middle line:84% So what we are really doing here is 00:08:54.330 --> 00:08:59.340 align:middle line:84% we are just enabling Jabber to support URI dialing. 00:08:59.340 --> 00:09:00.540 align:middle line:90% Let's log in. 00:09:00.540 --> 00:09:09.100 align:middle line:90% 00:09:09.100 --> 00:09:11.730 align:middle line:90% Let's go to OS administration. 00:09:11.730 --> 00:09:18.070 align:middle line:90% 00:09:18.070 --> 00:09:22.090 align:middle line:84% Same thing on site B. Go to OS Administration. 00:09:22.090 --> 00:09:26.470 align:middle line:90% 00:09:26.470 --> 00:09:27.610 align:middle line:90% And log in. 00:09:27.610 --> 00:10:49.120 align:middle line:90% 00:10:49.120 --> 00:10:50.530 align:middle line:90% It's taking a bit of time. 00:10:50.530 --> 00:10:56.960 align:middle line:90% 00:10:56.960 --> 00:10:59.720 align:middle line:84% See right now if I go to my Steve Rogers, 00:10:59.720 --> 00:11:07.160 align:middle line:84% and let's say if I try to dial tony-stark@ine.com, 00:11:07.160 --> 00:11:10.940 align:middle line:84% I don't really see the call option, the call button. 00:11:10.940 --> 00:11:12.710 align:middle line:84% I don't see that because it doesn't really 00:11:12.710 --> 00:11:15.395 align:middle line:84% support URI dialing at this point of time. 00:11:15.395 --> 00:11:18.820 align:middle line:90% 00:11:18.820 --> 00:11:20.050 align:middle line:90% Let's go back here. 00:11:20.050 --> 00:11:22.710 align:middle line:84% So let's go to a software upgrades 00:11:22.710 --> 00:11:26.880 align:middle line:90% and let's go to TFTP management. 00:11:26.880 --> 00:11:29.920 align:middle line:90% 00:11:29.920 --> 00:11:31.300 align:middle line:90% Same thing here. 00:11:31.300 --> 00:11:36.410 align:middle line:84% Go to software upgrades, TFTP management. 00:11:36.410 --> 00:11:38.180 align:middle line:84% And here, we would upload the file. 00:11:38.180 --> 00:11:41.720 align:middle line:90% 00:11:41.720 --> 00:11:50.060 align:middle line:84% As to browse from Jabber config file and just put the directory 00:11:50.060 --> 00:11:51.177 align:middle line:90% add as /upload. 00:11:51.177 --> 00:11:54.100 align:middle line:90% 00:11:54.100 --> 00:12:02.330 align:middle line:84% So on HQ UCM, I have uploaded the file successfully. 00:12:02.330 --> 00:12:05.215 align:middle line:84% Let's now go to site B. Go to upload. 00:12:05.215 --> 00:12:12.390 align:middle line:90% 00:12:12.390 --> 00:12:17.994 align:middle line:84% Browse Jabber config file and forward slash. 00:12:17.994 --> 00:12:20.766 align:middle line:90% 00:12:20.766 --> 00:12:22.430 align:middle line:90% Uploaded successfully. 00:12:22.430 --> 00:12:26.190 align:middle line:84% Now obviously, for the TFTP to serve this file, 00:12:26.190 --> 00:12:28.650 align:middle line:84% we would need to restart the TFTP service. 00:12:28.650 --> 00:12:31.200 align:middle line:84% So now let's go to serviceability. 00:12:31.200 --> 00:12:34.830 align:middle line:90% 00:12:34.830 --> 00:12:35.820 align:middle line:90% Same thing here. 00:12:35.820 --> 00:12:41.400 align:middle line:90% 00:12:41.400 --> 00:12:46.250 align:middle line:90% And let's click on Go. 00:12:46.250 --> 00:12:47.210 align:middle line:90% Let's log in. 00:12:47.210 --> 00:12:51.150 align:middle line:90% 00:12:51.150 --> 00:12:54.150 align:middle line:90% Click on Go. 00:12:54.150 --> 00:12:55.185 align:middle line:90% Let's log in. 00:12:55.185 --> 00:13:06.900 align:middle line:90% 00:13:06.900 --> 00:13:09.750 align:middle line:84% Let's go to Control Center Feature Services and restart 00:13:09.750 --> 00:13:10.250 align:middle line:90% TFTP. 00:13:10.250 --> 00:14:16.580 align:middle line:90% 00:14:16.580 --> 00:14:17.080 align:middle line:90% All right. 00:14:17.080 --> 00:14:18.500 align:middle line:90% Let's go to Tools. 00:14:18.500 --> 00:14:21.390 align:middle line:90% 00:14:21.390 --> 00:14:24.735 align:middle line:84% So I'm on site B. Control center Feature Services. 00:14:24.735 --> 00:14:27.720 align:middle line:90% 00:14:27.720 --> 00:14:29.890 align:middle line:90% Let's choose our UCM. 00:14:29.890 --> 00:14:38.130 align:middle line:90% 00:14:38.130 --> 00:14:40.720 align:middle line:90% And restart. 00:14:40.720 --> 00:14:43.585 align:middle line:84% Select TFTP and restart that service. 00:14:43.585 --> 00:14:46.360 align:middle line:90% 00:14:46.360 --> 00:14:48.420 align:middle line:84% So now the new Jabber config file 00:14:48.420 --> 00:14:51.355 align:middle line:84% would be served to the Jabber user when he logs in. 00:14:51.355 --> 00:14:52.980 align:middle line:84% Obviously, you'll have to go back there 00:14:52.980 --> 00:14:56.340 align:middle line:84% and reset your Jabber and re log in. 00:14:56.340 --> 00:15:09.270 align:middle line:90% 00:15:09.270 --> 00:15:09.770 align:middle line:90% All right. 00:15:09.770 --> 00:15:11.250 align:middle line:90% So site B is done. 00:15:11.250 --> 00:15:19.140 align:middle line:84% Let's go to HQ, Tools, Control Center Feature Services. 00:15:19.140 --> 00:15:22.730 align:middle line:90% Choose your publisher. 00:15:22.730 --> 00:15:25.430 align:middle line:90% Now again, I'm mentioning this. 00:15:25.430 --> 00:15:27.600 align:middle line:84% In the lab exam, you would have a subscriber also. 00:15:27.600 --> 00:15:29.930 align:middle line:84% So make sure you upload TFTP, the file, 00:15:29.930 --> 00:15:32.360 align:middle line:84% to all your publisher and subscriber. 00:15:32.360 --> 00:15:35.450 align:middle line:84% And then restart the TFTP service on both publisher 00:15:35.450 --> 00:15:37.170 align:middle line:90% and subscriber. 00:15:37.170 --> 00:15:38.490 align:middle line:90% So scroll down. 00:15:38.490 --> 00:15:41.740 align:middle line:90% Let's go to TFTP and restart. 00:15:41.740 --> 00:15:45.660 align:middle line:90% 00:15:45.660 --> 00:15:46.210 align:middle line:90% That's it. 00:15:46.210 --> 00:15:50.610 align:middle line:84% So now your Jabber should support URI dialing. 00:15:50.610 --> 00:15:55.350 align:middle line:84% I would obviously have to go to my Jabber machine 00:15:55.350 --> 00:16:03.540 align:middle line:90% and sign out and reset it. 00:16:03.540 --> 00:16:09.890 align:middle line:84% So let's reset this and re login with steve-rogers@ine.com. 00:16:09.890 --> 00:16:16.580 align:middle line:90% 00:16:16.580 --> 00:16:21.780 align:middle line:84% I think Steve Rogers was configured manually. 00:16:21.780 --> 00:16:26.040 align:middle line:84% So going to advance settings and defining the IM&P address, 00:16:26.040 --> 00:16:34.840 align:middle line:84% which, I think it was, in fact, it was the call manager. 00:16:34.840 --> 00:16:38.510 align:middle line:84% Let's go and put the call managers IP, 00:16:38.510 --> 00:16:40.850 align:middle line:90% which is site B-CUCM.ine.com. 00:16:40.850 --> 00:16:48.060 align:middle line:90% 00:16:48.060 --> 00:17:03.220 align:middle line:84% And those steve-rogers@ine.com Password was c1sc0123!. 00:17:03.220 --> 00:17:07.500 align:middle line:90% And we should be able to log in. 00:17:07.500 --> 00:17:12.900 align:middle line:84% So force site B in my initial config or settings, 00:17:12.900 --> 00:17:17.864 align:middle line:84% which is pre-configured for you for site B, I had not used 00:17:17.864 --> 00:17:18.364 align:middle line:90% IMNP. 00:17:18.364 --> 00:17:22.160 align:middle line:84% I had directly logged in to the call manager. 00:17:22.160 --> 00:17:29.750 align:middle line:84% So this is what I had configured earlier for Steve Rogers. 00:17:29.750 --> 00:17:33.050 align:middle line:84% And for HQ, let's go back and see. 00:17:33.050 --> 00:17:35.220 align:middle line:90% So it's already restarted. 00:17:35.220 --> 00:17:36.920 align:middle line:90% Let's go to my Jabber. 00:17:36.920 --> 00:17:42.740 align:middle line:84% For HQ, I was using Cisco UDS so srv records. 00:17:42.740 --> 00:17:47.120 align:middle line:84% I had srv of records for HQ site so I can directly log in. 00:17:47.120 --> 00:17:47.885 align:middle line:90% Lets sign out. 00:17:47.885 --> 00:17:51.350 align:middle line:90% 00:17:51.350 --> 00:17:54.000 align:middle line:90% Reset this. 00:17:54.000 --> 00:17:57.050 align:middle line:84% So for Tony Stark or for HQ site users, 00:17:57.050 --> 00:17:59.030 align:middle line:84% I would not have to go to Advanced Settings. 00:17:59.030 --> 00:18:01.475 align:middle line:84% So let's log in with tony-stark@ine.com. 00:18:01.475 --> 00:18:04.310 align:middle line:90% 00:18:04.310 --> 00:18:08.810 align:middle line:84% It should find the certs for publisher and for your IMNP 00:18:08.810 --> 00:18:12.380 align:middle line:84% also because I have the CRB records 00:18:12.380 --> 00:18:16.850 align:middle line:84% on my DNS machine for HQ site, which 00:18:16.850 --> 00:18:20.045 align:middle line:90% points to the publisher of HQ. 00:18:20.045 --> 00:18:29.730 align:middle line:90% 00:18:29.730 --> 00:18:36.183 align:middle line:90% I log in with c1sc0123! 00:18:36.183 --> 00:18:37.715 align:middle line:90% It should find the certs. 00:18:37.715 --> 00:18:51.450 align:middle line:90% 00:18:51.450 --> 00:18:54.420 align:middle line:84% In the meanwhile, site B is up and ready 00:18:54.420 --> 00:18:55.590 align:middle line:90% which you can see here. 00:18:55.590 --> 00:19:05.930 align:middle line:90% 00:19:05.930 --> 00:19:09.250 align:middle line:84% And Tony Stark has also logged in. 00:19:09.250 --> 00:19:13.420 align:middle line:84% If I look at Steve Rogers now, let's say if he dials 00:19:13.420 --> 00:19:22.030 align:middle line:84% tony-stark@ine.com, I get the sign of making a call 00:19:22.030 --> 00:19:26.238 align:middle line:84% because now my Jabber supports URI dialing. 00:19:26.238 --> 00:19:28.780 align:middle line:84% So obviously I wouldn't be able to dial at this point of time 00:19:28.780 --> 00:19:30.640 align:middle line:84% because I haven't configured ILS. 00:19:30.640 --> 00:19:33.070 align:middle line:84% But at least I should be able to-- 00:19:33.070 --> 00:19:36.160 align:middle line:84% I should be able to see that green button to make a call 00:19:36.160 --> 00:19:42.610 align:middle line:84% by let's say doing steve-rogers@ine.com I should 00:19:42.610 --> 00:19:45.550 align:middle line:84% get that calling button here, which I do see which basically 00:19:45.550 --> 00:19:50.230 align:middle line:84% means that my Jabber config file was served to both these users 00:19:50.230 --> 00:19:53.960 align:middle line:84% which has SIP URI dialing enabled. 00:19:53.960 --> 00:19:57.860 align:middle line:84% Now that we've enabled URI dialing for the Jabber users, 00:19:57.860 --> 00:20:00.970 align:middle line:84% we should now be able to configure ILS. 00:20:00.970 --> 00:20:03.280 align:middle line:90% So let's quickly do that now. 00:20:03.280 --> 00:20:08.140 align:middle line:84% Let's minimize this and go to my call manager. 00:20:08.140 --> 00:20:12.790 align:middle line:84% First thing what I'm going to do is go to both my users 00:20:12.790 --> 00:20:18.350 align:middle line:90% and define URI for the end user. 00:20:18.350 --> 00:20:24.460 align:middle line:84% So on site B, I only have one user, which is Steve Rogers. 00:20:24.460 --> 00:20:26.300 align:middle line:84% And that's for the question, the name, 00:20:26.300 --> 00:20:29.860 align:middle line:84% the URI for Steve Rogers was steve-rogers@ine.com 00:20:29.860 --> 00:20:35.020 align:middle line:84% and for Tony Stark on HQ was tony-stark@ine.com. 00:20:35.020 --> 00:20:38.800 align:middle line:84% I do have two more users on HQ, HQ1 and HQ2. 00:20:38.800 --> 00:20:42.280 align:middle line:84% So I even the question really does not say anything about it 00:20:42.280 --> 00:20:46.330 align:middle line:84% and it only talks about verifying from Tony 00:20:46.330 --> 00:20:49.570 align:middle line:84% to Steve Rogers or Steve Rogers to Tony. 00:20:49.570 --> 00:20:53.500 align:middle line:84% I would suggest that don't be in the gray area, do it for HQ1 00:20:53.500 --> 00:20:54.980 align:middle line:90% and HQ2 also. 00:20:54.980 --> 00:20:58.990 align:middle line:84% So whichever users are there, you should do it for them. 00:20:58.990 --> 00:21:06.540 align:middle line:90% Let's go to Administration. 00:21:06.540 --> 00:21:08.170 align:middle line:90% And let's log in. 00:21:08.170 --> 00:21:09.690 align:middle line:90% So first thing on HQ. 00:21:09.690 --> 00:21:15.180 align:middle line:84% Let's go to end user and for each of my user, 00:21:15.180 --> 00:21:18.090 align:middle line:90% I will define-- 00:21:18.090 --> 00:21:22.635 align:middle line:84% I will basically define the directory URI. 00:21:22.635 --> 00:21:25.190 align:middle line:90% 00:21:25.190 --> 00:21:26.400 align:middle line:90% So I have three users here. 00:21:26.400 --> 00:21:28.470 align:middle line:90% Let's go to HQ one first. 00:21:28.470 --> 00:21:31.340 align:middle line:84% Irrespective of wherever the wherever you log in from, 00:21:31.340 --> 00:21:33.830 align:middle line:84% I should be able to dial using URI. 00:21:33.830 --> 00:21:36.900 align:middle line:90% 00:21:36.900 --> 00:21:40.070 align:middle line:84% So right now these users are through LDAP. 00:21:40.070 --> 00:21:42.687 align:middle line:84% So I would not be able to make any changes. 00:21:42.687 --> 00:21:44.270 align:middle line:84% So first thing that I would have to do 00:21:44.270 --> 00:21:46.650 align:middle line:84% is convert them to be a local user. 00:21:46.650 --> 00:21:50.165 align:middle line:84% So let's convert them to be a local user. 00:21:50.165 --> 00:21:54.550 align:middle line:90% 00:21:54.550 --> 00:21:59.290 align:middle line:84% And then go to directory URI and this would be HQ-1@ine.com. 00:21:59.290 --> 00:22:02.740 align:middle line:90% 00:22:02.740 --> 00:22:03.760 align:middle line:90% Let's save this. 00:22:03.760 --> 00:22:12.940 align:middle line:90% 00:22:12.940 --> 00:22:14.190 align:middle line:90% Let's scroll down. 00:22:14.190 --> 00:22:16.155 align:middle line:84% I believe there's nothing else that we need. 00:22:16.155 --> 00:22:21.753 align:middle line:90% 00:22:21.753 --> 00:22:23.170 align:middle line:84% There's nothing else that we need. 00:22:23.170 --> 00:22:24.330 align:middle line:90% Let's go back to HQ-2. 00:22:24.330 --> 00:22:31.020 align:middle line:90% 00:22:31.020 --> 00:22:32.955 align:middle line:84% Convert him to be a local user again. 00:22:32.955 --> 00:22:38.170 align:middle line:90% 00:22:38.170 --> 00:22:42.085 align:middle line:84% And directory URI would be hq-2@ine.com. 00:22:42.085 --> 00:22:45.555 align:middle line:90% 00:22:45.555 --> 00:22:46.055 align:middle line:90% Save. 00:22:46.055 --> 00:22:58.250 align:middle line:90% 00:22:58.250 --> 00:23:00.020 align:middle line:90% Then go to Tony Stark. 00:23:00.020 --> 00:23:05.310 align:middle line:90% 00:23:05.310 --> 00:23:07.320 align:middle line:90% Let's convert him to local user. 00:23:07.320 --> 00:23:11.860 align:middle line:90% 00:23:11.860 --> 00:23:17.040 align:middle line:84% And then add the directory URI as tony-stark@ine.com. 00:23:17.040 --> 00:23:24.150 align:middle line:84% Let's do exactly the same thing on site B for Steve Rodgers. 00:23:24.150 --> 00:23:28.020 align:middle line:84% On site B I only have one user, which is Steve Rogers. 00:23:28.020 --> 00:23:44.700 align:middle line:90% 00:23:44.700 --> 00:23:47.320 align:middle line:90% This is anyway a local user. 00:23:47.320 --> 00:23:50.910 align:middle line:84% So I can directly go and put the directory URI, 00:23:50.910 --> 00:23:52.770 align:middle line:90% which is steve-rogers@ine.com. 00:23:52.770 --> 00:23:57.550 align:middle line:90% 00:23:57.550 --> 00:23:59.290 align:middle line:90% Let's save this. 00:23:59.290 --> 00:24:04.990 align:middle line:84% Now all my end users, they have the directory URI defined. 00:24:04.990 --> 00:24:08.410 align:middle line:84% The next thing is when the phone-- 00:24:08.410 --> 00:24:12.460 align:middle line:84% when the user is dialing the remote end, 00:24:12.460 --> 00:24:16.550 align:middle line:84% all my directory URIs are a part of a special partition, 00:24:16.550 --> 00:24:18.470 align:middle line:84% which is a directory URI partition . 00:24:18.470 --> 00:24:22.610 align:middle line:84% My phone needs access to that partition. 00:24:22.610 --> 00:24:24.820 align:middle line:84% So if I actually look at my let's say site 00:24:24.820 --> 00:24:33.350 align:middle line:84% B and the phones all of these users, so on site B, 00:24:33.350 --> 00:24:38.030 align:middle line:84% I only have one user, one CSF, which is Steve Rogers. 00:24:38.030 --> 00:24:44.630 align:middle line:84% He belongs to the device CSS is CSS phones. 00:24:44.630 --> 00:24:49.800 align:middle line:84% So that devices CSS needs access to directory URL partition. 00:24:49.800 --> 00:24:53.090 align:middle line:84% So if you see here the phone has access to CSS phones. 00:24:53.090 --> 00:24:57.560 align:middle line:84% And if I go back to my class of control and the calling search 00:24:57.560 --> 00:25:09.750 align:middle line:84% space, and find CSS phones, I need 00:25:09.750 --> 00:25:12.510 align:middle line:84% to give my phone access to the partition, which 00:25:12.510 --> 00:25:15.420 align:middle line:90% is directory URI partition. 00:25:15.420 --> 00:25:17.960 align:middle line:90% So which is here, directory URI. 00:25:17.960 --> 00:25:19.460 align:middle line:90% Let's give them access to that. 00:25:19.460 --> 00:25:21.928 align:middle line:90% 00:25:21.928 --> 00:25:23.720 align:middle line:84% Because if I don't give him access to that, 00:25:23.720 --> 00:25:27.800 align:middle line:84% he would not be able to dial using URI. 00:25:27.800 --> 00:25:28.400 align:middle line:90% Let's save. 00:25:28.400 --> 00:25:30.470 align:middle line:84% Let's do the same thing on HQ site. 00:25:30.470 --> 00:25:32.870 align:middle line:84% So the HQ phones they have access 00:25:32.870 --> 00:25:35.490 align:middle line:90% to the device CSS phones. 00:25:35.490 --> 00:25:38.630 align:middle line:84% So again on HQ site under the calling search space 00:25:38.630 --> 00:25:41.480 align:middle line:84% for the CSS phones, I would have to give him access 00:25:41.480 --> 00:25:43.340 align:middle line:90% to directory URI partition. 00:25:43.340 --> 00:25:48.390 align:middle line:90% 00:25:48.390 --> 00:25:49.235 align:middle line:90% Let's to find. 00:25:49.235 --> 00:25:54.340 align:middle line:90% 00:25:54.340 --> 00:25:55.470 align:middle line:90% Go to CSS phones. 00:25:55.470 --> 00:26:02.020 align:middle line:90% 00:26:02.020 --> 00:26:05.200 align:middle line:84% And give them access to a directory URI. 00:26:05.200 --> 00:26:06.085 align:middle line:90% Let's save this. 00:26:06.085 --> 00:26:10.190 align:middle line:90% 00:26:10.190 --> 00:26:12.380 align:middle line:84% Now if I actually go to devise phones, 00:26:12.380 --> 00:26:15.780 align:middle line:84% I just want to show you something. 00:26:15.780 --> 00:26:16.625 align:middle line:90% Let's do a find-- 00:26:16.625 --> 00:26:19.900 align:middle line:90% 00:26:19.900 --> 00:26:28.930 align:middle line:84% let's go to any one of the user, let's say Tony Stark, 00:26:28.930 --> 00:26:41.410 align:middle line:84% go under your line 2003 and scroll down. 00:26:41.410 --> 00:26:45.490 align:middle line:84% If you see the directory URI that I created for the end user 00:26:45.490 --> 00:26:47.670 align:middle line:90% tony-stark@ine.com. 00:26:47.670 --> 00:26:49.060 align:middle line:90% This didn't exist earlier. 00:26:49.060 --> 00:26:51.320 align:middle line:84% The minute I went to the end user. 00:26:51.320 --> 00:26:53.860 align:middle line:84% And I added the directory URI, if you 00:26:53.860 --> 00:26:56.980 align:middle line:84% see by default that's in the partition of directory URI. 00:26:56.980 --> 00:27:01.480 align:middle line:84% That's why I need to give him access to this partition. 00:27:01.480 --> 00:27:07.150 align:middle line:84% Next thing that I'm going to do is on my HQ, HQ and site 00:27:07.150 --> 00:27:09.580 align:middle line:90% B they need to be the spokes. 00:27:09.580 --> 00:27:11.230 align:middle line:90% And SME is going to be hub. 00:27:11.230 --> 00:27:15.730 align:middle line:84% So make sure your cluster ID or your cluster name is unique. 00:27:15.730 --> 00:27:18.500 align:middle line:84% So I'm going to go to each one of the device. 00:27:18.500 --> 00:27:23.280 align:middle line:90% So go to your publisher of HQ. 00:27:23.280 --> 00:27:24.980 align:middle line:90% Go to Enterprise Parameters. 00:27:24.980 --> 00:27:28.190 align:middle line:90% 00:27:28.190 --> 00:27:32.310 align:middle line:84% And change your cluster ID to be a unique cluster ID. 00:27:32.310 --> 00:27:34.970 align:middle line:84% So right now the cluster ID is a standalone cluster 00:27:34.970 --> 00:27:39.680 align:middle line:84% which would basically mean that all my HQ site B, SME they 00:27:39.680 --> 00:27:41.160 align:middle line:90% would have the same name. 00:27:41.160 --> 00:27:42.660 align:middle line:90% So they need to be unique. 00:27:42.660 --> 00:27:45.675 align:middle line:84% So let's give for HQ, let's give HQ. 00:27:45.675 --> 00:27:46.175 align:middle line:90% Save. 00:27:46.175 --> 00:27:56.710 align:middle line:90% 00:27:56.710 --> 00:27:57.835 align:middle line:90% And let's reset. 00:27:57.835 --> 00:28:01.480 align:middle line:90% 00:28:01.480 --> 00:28:02.365 align:middle line:90% Apply Config. 00:28:02.365 --> 00:28:13.470 align:middle line:90% 00:28:13.470 --> 00:28:14.475 align:middle line:90% And let's reset. 00:28:14.475 --> 00:28:26.200 align:middle line:90% 00:28:26.200 --> 00:28:27.850 align:middle line:90% Let's now go to-- 00:28:27.850 --> 00:28:30.950 align:middle line:90% 00:28:30.950 --> 00:28:37.340 align:middle line:84% let's now go to site B. And go to Enterprise Parameters 00:28:37.340 --> 00:28:40.370 align:middle line:90% and do exactly the same thing. 00:28:40.370 --> 00:28:57.380 align:middle line:84% For site B, let's give the name as site B. 00:28:57.380 --> 00:29:00.230 align:middle line:90% Let's take this at the site. 00:29:00.230 --> 00:29:01.390 align:middle line:90% Open up SME as well. 00:29:01.390 --> 00:29:08.850 align:middle line:90% 00:29:08.850 --> 00:29:10.010 align:middle line:90% Let's apply the config. 00:29:10.010 --> 00:29:19.000 align:middle line:90% 00:29:19.000 --> 00:29:19.885 align:middle line:90% And let's reset. 00:29:19.885 --> 00:29:37.220 align:middle line:90% 00:29:37.220 --> 00:29:38.965 align:middle line:90% Let's do the same thing on SME. 00:29:38.965 --> 00:30:52.630 align:middle line:90% 00:30:52.630 --> 00:30:55.160 align:middle line:84% In the meanwhile, whilst SME is opening up, 00:30:55.160 --> 00:30:56.720 align:middle line:90% let's go back to HQ. 00:30:56.720 --> 00:31:00.050 align:middle line:84% And now go to service parameters. 00:31:00.050 --> 00:31:02.283 align:middle line:84% There's one more thing that we need to change 00:31:02.283 --> 00:31:03.200 align:middle line:90% in service parameters. 00:31:03.200 --> 00:31:06.500 align:middle line:84% By default, the display preference 00:31:06.500 --> 00:31:09.950 align:middle line:84% is DN because the question says that whenever 00:31:09.950 --> 00:31:11.450 align:middle line:84% you make the call, you should always 00:31:11.450 --> 00:31:14.390 align:middle line:90% display the URI, not the DN. 00:31:14.390 --> 00:31:16.940 align:middle line:84% By default the display preferences DN. 00:31:16.940 --> 00:31:19.850 align:middle line:90% We would change that to URI. 00:31:19.850 --> 00:31:22.475 align:middle line:90% So let's go to our call manager. 00:31:22.475 --> 00:31:26.470 align:middle line:90% 00:31:26.470 --> 00:31:28.505 align:middle line:90% And go to call manager. 00:31:28.505 --> 00:31:37.040 align:middle line:90% 00:31:37.040 --> 00:31:40.180 align:middle line:90% And just search for-- 00:31:40.180 --> 00:31:47.890 align:middle line:90% go to advanced and search for-- 00:31:47.890 --> 00:31:50.460 align:middle line:90% 00:31:50.460 --> 00:31:55.780 align:middle line:84% Control-F, search for URI dialing. 00:31:55.780 --> 00:31:58.050 align:middle line:84% So you should see URI dialing display preference. 00:31:58.050 --> 00:32:02.190 align:middle line:84% Default is DN, change this to URI and save. 00:32:02.190 --> 00:32:11.580 align:middle line:90% 00:32:11.580 --> 00:32:12.580 align:middle line:90% Save done. 00:32:12.580 --> 00:32:17.550 align:middle line:84% Let's do the same thing on site B under service parameters. 00:32:17.550 --> 00:32:27.100 align:middle line:90% 00:32:27.100 --> 00:32:27.745 align:middle line:90% Call manager. 00:32:27.745 --> 00:32:37.520 align:middle line:90% 00:32:37.520 --> 00:32:38.835 align:middle line:90% Go to advanced. 00:32:38.835 --> 00:32:42.950 align:middle line:90% 00:32:42.950 --> 00:32:49.040 align:middle line:90% And search for URI dialing. 00:32:49.040 --> 00:32:52.660 align:middle line:90% Change this to URI. 00:32:52.660 --> 00:32:57.520 align:middle line:84% So now if the URI is available, he is going to show the URI. 00:32:57.520 --> 00:33:00.635 align:middle line:84% If URI is not available, he'll show the DN. 00:33:00.635 --> 00:33:05.050 align:middle line:84% But at least the preference is said to URI. 00:33:05.050 --> 00:33:07.610 align:middle line:84% Let's go back to SME now and make the changes. 00:33:07.610 --> 00:33:10.570 align:middle line:84% So let's go first to Enterprise Parameters, 00:33:10.570 --> 00:33:14.620 align:middle line:84% change the cluster ID name to be something else. 00:33:14.620 --> 00:33:15.600 align:middle line:90% Let's make it SME. 00:33:15.600 --> 00:33:20.060 align:middle line:90% 00:33:20.060 --> 00:33:24.400 align:middle line:90% So that's going to be SME. 00:33:24.400 --> 00:33:25.525 align:middle line:90% Let's save this. 00:33:25.525 --> 00:33:37.450 align:middle line:90% 00:33:37.450 --> 00:33:38.340 align:middle line:90% Apply Config. 00:33:38.340 --> 00:33:44.610 align:middle line:90% 00:33:44.610 --> 00:33:45.930 align:middle line:90% And reset. 00:33:45.930 --> 00:33:48.840 align:middle line:90% 00:33:48.840 --> 00:33:51.060 align:middle line:84% Next thing what we're going to do is after the reset, 00:33:51.060 --> 00:33:53.490 align:middle line:84% we will go to Service Parameters and again 00:33:53.490 --> 00:33:57.910 align:middle line:84% change the Display Preference to be URI. 00:33:57.910 --> 00:34:00.840 align:middle line:90% 00:34:00.840 --> 00:34:03.180 align:middle line:84% So go back to Service Parameters, 00:34:03.180 --> 00:34:06.400 align:middle line:84% go back to your UCM, service type 00:34:06.400 --> 00:34:07.650 align:middle line:90% is going to be called manager. 00:34:07.650 --> 00:34:16.150 align:middle line:90% 00:34:16.150 --> 00:34:19.820 align:middle line:90% Let's search for URI dialing. 00:34:19.820 --> 00:34:21.639 align:middle line:84% So you don't really need to go to Advance, 00:34:21.639 --> 00:34:26.020 align:middle line:84% but you can directly search for URI dialing without advance. 00:34:26.020 --> 00:34:32.380 align:middle line:84% Let's change this to URI and save. 00:34:32.380 --> 00:34:36.040 align:middle line:84% Now once this is done, now think about the communication, 00:34:36.040 --> 00:34:39.560 align:middle line:84% how is the communication between HQ and site B going to happen? 00:34:39.560 --> 00:34:47.679 align:middle line:84% Now there is a SIP trunk, which was configured earlier 00:34:47.679 --> 00:34:50.679 align:middle line:84% when we had done inter side between HQ and site B 00:34:50.679 --> 00:34:51.820 align:middle line:90% through the SME. 00:34:51.820 --> 00:34:54.250 align:middle line:84% If you remember, we had configured a SIP trunk from HQ 00:34:54.250 --> 00:34:56.690 align:middle line:90% to SME from site B to SME. 00:34:56.690 --> 00:35:01.810 align:middle line:84% So using the SIP trunk I would allow URI dialing. 00:35:01.810 --> 00:35:03.610 align:middle line:84% So first thing what I'm going to do 00:35:03.610 --> 00:35:11.740 align:middle line:84% is go to SME and under the partition, which my-- 00:35:11.740 --> 00:35:13.630 align:middle line:84% if you look at my SIP trunk on SME, 00:35:13.630 --> 00:35:15.700 align:middle line:84% SME has two SIP trunks, one going 00:35:15.700 --> 00:35:19.210 align:middle line:84% towards HQ, one going towards site B. 00:35:19.210 --> 00:35:25.320 align:middle line:84% And on each of these trunks, and I think 00:35:25.320 --> 00:35:28.830 align:middle line:90% this is the one going to-- 00:35:28.830 --> 00:35:32.250 align:middle line:84% under the HQ, I have inbound CSS applied. 00:35:32.250 --> 00:35:34.830 align:middle line:84% So when I receive anything from HQ, 00:35:34.830 --> 00:35:40.110 align:middle line:84% I have an inbound CSS from HQ called CSS inbound from HQ. 00:35:40.110 --> 00:35:43.410 align:middle line:84% There's one more CSS inbound from site B. 00:35:43.410 --> 00:35:46.590 align:middle line:84% So when the call comes from site B. So these SIP 00:35:46.590 --> 00:35:49.050 align:middle line:84% trunks, these CSS, they require access 00:35:49.050 --> 00:35:50.920 align:middle line:90% to directory URI partition. 00:35:50.920 --> 00:35:53.340 align:middle line:84% So let's go to calling search space. 00:35:53.340 --> 00:36:05.410 align:middle line:90% 00:36:05.410 --> 00:36:07.360 align:middle line:84% So basically, what's going to happen 00:36:07.360 --> 00:36:11.590 align:middle line:84% is when the call comes in using URI from HQ, 00:36:11.590 --> 00:36:16.150 align:middle line:84% it hits the SME on the trunk from HQ. 00:36:16.150 --> 00:36:18.130 align:middle line:90% And that has an inbound CSS. 00:36:18.130 --> 00:36:21.040 align:middle line:84% So that needs access to directory URI partition 00:36:21.040 --> 00:36:22.790 align:middle line:84% otherwise the call is going to fail. 00:36:22.790 --> 00:36:26.135 align:middle line:84% So on both my trunks, on the CSS, 00:36:26.135 --> 00:36:30.150 align:middle line:84% I would give him access to a directory URI. 00:36:30.150 --> 00:36:32.770 align:middle line:90% So let's go and add that. 00:36:32.770 --> 00:36:48.530 align:middle line:84% So inbound from HQ and also inbound from site B. 00:36:48.530 --> 00:36:51.320 align:middle line:84% I do not need to go and apply directory URI 00:36:51.320 --> 00:36:55.280 align:middle line:84% partition to CSS inbound PSTN because PSTN is not 00:36:55.280 --> 00:36:57.260 align:middle line:90% dialing using URI. 00:36:57.260 --> 00:36:58.830 align:middle line:90% So that is not needed. 00:36:58.830 --> 00:37:00.830 align:middle line:84% But HQ is dialing site B and site 00:37:00.830 --> 00:37:03.140 align:middle line:84% VS telling HQ so on the SIP trunk 00:37:03.140 --> 00:37:07.640 align:middle line:84% on SME for both the clusters on the inbound CSS, 00:37:07.640 --> 00:37:11.330 align:middle line:84% I need to go and give them access to directory URI. 00:37:11.330 --> 00:37:15.100 align:middle line:84% Once this is done, I would then go and-- 00:37:15.100 --> 00:37:17.930 align:middle line:90% 00:37:17.930 --> 00:37:22.910 align:middle line:84% I would then go to create a SIP profile that 00:37:22.910 --> 00:37:28.100 align:middle line:90% allows FQDN in the SIP request. 00:37:28.100 --> 00:37:30.770 align:middle line:84% By default, the SIP request will not support FQDN. 00:37:30.770 --> 00:37:33.540 align:middle line:90% It only supports IP addresses. 00:37:33.540 --> 00:37:40.010 align:middle line:84% So we want to create a SIP profile, which is going to be-- 00:37:40.010 --> 00:37:45.870 align:middle line:84% which is basically going to be supporting FQDN. 00:37:45.870 --> 00:37:49.010 align:middle line:84% So let's go and create a SIP profile. 00:37:49.010 --> 00:37:56.390 align:middle line:90% 00:37:56.390 --> 00:37:58.760 align:middle line:84% But if you minimize the screen, I can't see it. 00:37:58.760 --> 00:38:04.180 align:middle line:90% 00:38:04.180 --> 00:38:04.890 align:middle line:90% OK. 00:38:04.890 --> 00:38:06.750 align:middle line:90% Let's go to Device. 00:38:06.750 --> 00:38:08.550 align:middle line:90% Device Settings. 00:38:08.550 --> 00:38:10.455 align:middle line:90% Go to SIP Profile. 00:38:10.455 --> 00:38:16.790 align:middle line:90% 00:38:16.790 --> 00:38:17.735 align:middle line:90% And do a find. 00:38:17.735 --> 00:38:20.590 align:middle line:90% 00:38:20.590 --> 00:38:22.660 align:middle line:90% Copy your standard SIP profile. 00:38:22.660 --> 00:38:25.910 align:middle line:90% 00:38:25.910 --> 00:38:27.620 align:middle line:90% And let's name this-- 00:38:27.620 --> 00:38:30.650 align:middle line:84% is the profile being used for ILS. 00:38:30.650 --> 00:38:33.860 align:middle line:84% And the only thing that we need here 00:38:33.860 --> 00:38:35.900 align:middle line:90% is to enable this checkbox. 00:38:35.900 --> 00:38:39.330 align:middle line:84% Use fully qualified domain name in SIP request. 00:38:39.330 --> 00:38:40.070 align:middle line:90% Let's save this. 00:38:40.070 --> 00:38:46.457 align:middle line:90% 00:38:46.457 --> 00:38:48.790 align:middle line:84% Let's do the same thing on site B. Create a SIP profile. 00:38:48.790 --> 00:39:01.190 align:middle line:90% 00:39:01.190 --> 00:39:02.615 align:middle line:90% Copy your standard one. 00:39:02.615 --> 00:39:05.780 align:middle line:90% 00:39:05.780 --> 00:39:08.750 align:middle line:90% Let's name this as ILS. 00:39:08.750 --> 00:39:12.440 align:middle line:84% And enable the checkbox for use fully qualified domain name 00:39:12.440 --> 00:39:13.565 align:middle line:90% in SIP request. 00:39:13.565 --> 00:39:17.110 align:middle line:90% 00:39:17.110 --> 00:39:18.645 align:middle line:90% Let's do the same thing on SME. 00:39:18.645 --> 00:39:33.990 align:middle line:90% 00:39:33.990 --> 00:39:36.480 align:middle line:90% Copy the standard one. 00:39:36.480 --> 00:39:41.010 align:middle line:84% Rename it to something, let's say ILS. 00:39:41.010 --> 00:39:45.040 align:middle line:84% And enable the checkbox, use fully qualified domain name. 00:39:45.040 --> 00:39:47.520 align:middle line:84% Now once you've created the SIP profile, 00:39:47.520 --> 00:39:50.430 align:middle line:84% we need to use the set profile on all our trunks. 00:39:50.430 --> 00:39:52.980 align:middle line:90% So HQ has a trunk to SME. 00:39:52.980 --> 00:39:55.050 align:middle line:84% So on HQ site, I would have to do that. 00:39:55.050 --> 00:39:56.970 align:middle line:90% Site B has a trunk to SME. 00:39:56.970 --> 00:39:58.690 align:middle line:90% On site B I have to do that. 00:39:58.690 --> 00:40:00.420 align:middle line:84% And on SME, we have two trunks one 00:40:00.420 --> 00:40:02.580 align:middle line:84% towards HQ, one towards site B, we 00:40:02.580 --> 00:40:05.800 align:middle line:84% have to apply the SIP profile on all those sides. 00:40:05.800 --> 00:40:08.050 align:middle line:90% So let's start with SME. 00:40:08.050 --> 00:40:13.010 align:middle line:90% So under my SIP trunk. 00:40:13.010 --> 00:40:14.990 align:middle line:90% Let's go to my SIP trunk. 00:40:14.990 --> 00:40:18.010 align:middle line:90% 00:40:18.010 --> 00:40:19.420 align:middle line:90% I have a sip trunk to HQ. 00:40:19.420 --> 00:40:25.120 align:middle line:90% 00:40:25.120 --> 00:40:27.850 align:middle line:90% Scroll all the way down. 00:40:27.850 --> 00:40:32.050 align:middle line:84% And here, if you see this tab here calling and connected 00:40:32.050 --> 00:40:35.530 align:middle line:84% party info format because the question states 00:40:35.530 --> 00:40:42.070 align:middle line:84% that we need to display URI when the call comes in, even if you 00:40:42.070 --> 00:40:44.980 align:middle line:84% are your dialing preferences URI, which we did in Service 00:40:44.980 --> 00:40:47.360 align:middle line:84% Parameters, even if that is the case, 00:40:47.360 --> 00:40:50.620 align:middle line:84% you would still not display URI because your trunk 00:40:50.620 --> 00:40:53.410 align:middle line:90% says that delivered DN only. 00:40:53.410 --> 00:40:57.520 align:middle line:84% So we would have to change this to deliver 00:40:57.520 --> 00:41:01.540 align:middle line:84% URI and DN in connected party if available. 00:41:01.540 --> 00:41:04.320 align:middle line:90% 00:41:04.320 --> 00:41:08.820 align:middle line:84% And then scroll down to your SIP profile 00:41:08.820 --> 00:41:12.960 align:middle line:84% and choose the SIP profile that we created, the one with ILS. 00:41:12.960 --> 00:41:13.980 align:middle line:90% Save this. 00:41:13.980 --> 00:41:16.860 align:middle line:84% Make sure you do not forget to reset your SIP trunk. 00:41:16.860 --> 00:41:26.820 align:middle line:90% 00:41:26.820 --> 00:41:27.915 align:middle line:90% Let's reset this. 00:41:27.915 --> 00:41:37.450 align:middle line:90% 00:41:37.450 --> 00:41:40.550 align:middle line:84% Let's now go and add the second trunk, 00:41:40.550 --> 00:41:45.865 align:middle line:84% which was towards site B which is this one. 00:41:45.865 --> 00:41:50.250 align:middle line:90% 00:41:50.250 --> 00:41:57.070 align:middle line:84% Scroll all the way down, we must deliver URI and DNF available 00:41:57.070 --> 00:42:00.490 align:middle line:84% and the SIP profile is going to be the one 00:42:00.490 --> 00:42:02.305 align:middle line:90% that we created ILS one. 00:42:02.305 --> 00:42:11.370 align:middle line:90% 00:42:11.370 --> 00:42:13.110 align:middle line:90% Let's reset this. 00:42:13.110 --> 00:42:14.610 align:middle line:84% Again, the most common mistake is 00:42:14.610 --> 00:42:16.290 align:middle line:84% that you actually configure everything 00:42:16.290 --> 00:42:18.720 align:middle line:84% and actually everything is configured correctly. 00:42:18.720 --> 00:42:20.620 align:middle line:84% But you forget to reset your trunk. 00:42:20.620 --> 00:42:21.750 align:middle line:90% And your call fails. 00:42:21.750 --> 00:42:24.630 align:middle line:84% So make sure you always reset when you make changes 00:42:24.630 --> 00:42:26.940 align:middle line:90% to your SIP trunk. 00:42:26.940 --> 00:42:31.130 align:middle line:84% Reset request was sent successfully. 00:42:31.130 --> 00:42:43.590 align:middle line:90% And now we go to HQ site. 00:42:43.590 --> 00:42:44.670 align:middle line:90% Let's go to HQ. 00:42:44.670 --> 00:42:46.230 align:middle line:90% Go to my SIP trunk to SME. 00:42:46.230 --> 00:42:57.140 align:middle line:90% 00:42:57.140 --> 00:42:59.105 align:middle line:90% So I have one SIP trunk to SME. 00:42:59.105 --> 00:43:01.750 align:middle line:90% 00:43:01.750 --> 00:43:12.880 align:middle line:84% Go all the way down and change your deliver URI and DN 00:43:12.880 --> 00:43:18.070 align:middle line:84% and change your SIP profile to ILS one. 00:43:18.070 --> 00:43:20.080 align:middle line:90% Let's save and reset. 00:43:20.080 --> 00:43:37.496 align:middle line:90% 00:43:37.496 --> 00:43:41.500 align:middle line:84% Let's do the same thing on site B. Site B 00:43:41.500 --> 00:43:42.910 align:middle line:90% also has a SIP trunk to SME. 00:43:42.910 --> 00:44:05.510 align:middle line:90% 00:44:05.510 --> 00:44:11.390 align:middle line:84% So deliver URI and DN and SIP profile 00:44:11.390 --> 00:44:15.200 align:middle line:84% would be the one for ILS, which supports fully qualified domain 00:44:15.200 --> 00:44:17.105 align:middle line:90% name in SIP request. 00:44:17.105 --> 00:44:29.020 align:middle line:90% 00:44:29.020 --> 00:44:30.810 align:middle line:90% Let's reset this. 00:44:30.810 --> 00:44:39.140 align:middle line:90% 00:44:39.140 --> 00:44:41.435 align:middle line:84% Next thing now, now that we've done all of this, 00:44:41.435 --> 00:44:43.700 align:middle line:84% now the next thing is to create a SIP route 00:44:43.700 --> 00:44:48.650 align:middle line:84% pattern that how should I be able to dial those SIP 00:44:48.650 --> 00:44:49.520 align:middle line:90% requests? 00:44:49.520 --> 00:44:53.940 align:middle line:84% So I'm going to call routing go to SIP route pattern. 00:44:53.940 --> 00:45:01.320 align:middle line:84% So on HQ and on site B, so because SME 00:45:01.320 --> 00:45:03.420 align:middle line:84% does not have any end users or any Jabber 00:45:03.420 --> 00:45:05.250 align:middle line:90% users locally connected. 00:45:05.250 --> 00:45:11.690 align:middle line:84% So I need to do this separate pattern on HQ and site B. 00:45:11.690 --> 00:45:13.065 align:middle line:84% So let's go to SIP route pattern. 00:45:13.065 --> 00:45:22.400 align:middle line:90% 00:45:22.400 --> 00:45:28.360 align:middle line:84% So on HQ, if you do a find, there's nothing. 00:45:28.360 --> 00:45:31.240 align:middle line:90% Let's do an Add New. 00:45:31.240 --> 00:45:35.650 align:middle line:84% Do domain routing and give the pattern as site 00:45:35.650 --> 00:45:39.550 align:middle line:84% B. So if I'm dialing site B. Now this 00:45:39.550 --> 00:45:43.630 align:middle line:84% is, I believe this is the cluster ID name that we used. 00:45:43.630 --> 00:45:46.930 align:middle line:84% So give this and use the trunk that we 00:45:46.930 --> 00:45:53.910 align:middle line:84% created to SME which was RL-SME and to save. 00:45:53.910 --> 00:45:57.750 align:middle line:84% So the go to site B, which is your cluster ID, 00:45:57.750 --> 00:46:01.830 align:middle line:84% you will go through SME, which is the trunk. 00:46:01.830 --> 00:46:06.550 align:middle line:84% Same thing on site B, I would say to go to HQ, 00:46:06.550 --> 00:46:09.970 align:middle line:84% you would use the trunk going to SME. 00:46:09.970 --> 00:46:15.490 align:middle line:84% So domain routing, to go to HQ, to go to SME. 00:46:15.490 --> 00:46:20.170 align:middle line:84% So on HQ, I'm putting site B. On site B and putting HQ. 00:46:20.170 --> 00:46:21.640 align:middle line:90% And let's save this. 00:46:21.640 --> 00:46:30.610 align:middle line:90% 00:46:30.610 --> 00:46:32.020 align:middle line:90% Now do I need anything? 00:46:32.020 --> 00:46:34.570 align:middle line:84% Do I need a SIP route pattern on SME? 00:46:34.570 --> 00:46:35.560 align:middle line:90% Yes. 00:46:35.560 --> 00:46:38.980 align:middle line:84% Even though there are no Jabber users there, 00:46:38.980 --> 00:46:41.770 align:middle line:84% you still need a SIP route pattern 00:46:41.770 --> 00:46:45.760 align:middle line:84% which matches both HQ and site B that if you want to go to HQ, 00:46:45.760 --> 00:46:47.410 align:middle line:90% use the trunk going to HQ. 00:46:47.410 --> 00:46:48.970 align:middle line:84% If you want to go towards site B, 00:46:48.970 --> 00:46:50.770 align:middle line:84% use the trunk going towards site B. 00:46:50.770 --> 00:46:53.530 align:middle line:84% And the name that-- the pattern name that we gave 00:46:53.530 --> 00:46:56.270 align:middle line:90% you was your cluster ID name. 00:46:56.270 --> 00:46:58.980 align:middle line:90% So let's go to SME now. 00:46:58.980 --> 00:47:00.420 align:middle line:90% Go to call routing. 00:47:00.420 --> 00:47:02.010 align:middle line:90% Go to a SIP route pattern. 00:47:02.010 --> 00:47:03.240 align:middle line:90% Here, I would create two. 00:47:03.240 --> 00:47:06.540 align:middle line:84% So on HQ, there was only one site B. On site B, 00:47:06.540 --> 00:47:08.250 align:middle line:90% there was only one HQ. 00:47:08.250 --> 00:47:10.260 align:middle line:84% On SME, there would be two, one for HQ 00:47:10.260 --> 00:47:11.835 align:middle line:90% going towards SIP trunk of HQ. 00:47:11.835 --> 00:47:15.450 align:middle line:84% One for site B going towards SIP trunk of site B. Let's 00:47:15.450 --> 00:47:16.380 align:middle line:90% create one here. 00:47:16.380 --> 00:47:22.950 align:middle line:90% 00:47:22.950 --> 00:47:26.960 align:middle line:84% So HQ will go using the SIP trunk HQ. 00:47:26.960 --> 00:47:37.380 align:middle line:90% 00:47:37.380 --> 00:47:39.540 align:middle line:90% Let's add one more. 00:47:39.540 --> 00:47:44.090 align:middle line:90% 00:47:44.090 --> 00:47:51.420 align:middle line:84% Site B will go using the trunk to site B. 00:47:51.420 --> 00:47:56.610 align:middle line:84% Now once we've done this, now we configure SME as the hub. 00:47:56.610 --> 00:48:04.160 align:middle line:84% To configure SME as the hub, we would go to Advanced Features, 00:48:04.160 --> 00:48:10.448 align:middle line:84% and we would go to ILS configuration on the SME. 00:48:10.448 --> 00:48:13.965 align:middle line:84% And change this to be the hub cluster. 00:48:13.965 --> 00:48:17.830 align:middle line:90% 00:48:17.830 --> 00:48:22.690 align:middle line:84% Ensure you enable exchange global dial plan replication 00:48:22.690 --> 00:48:24.250 align:middle line:90% with remote clusters. 00:48:24.250 --> 00:48:27.890 align:middle line:84% Otherwise, you would not learn about the remote sites. 00:48:27.890 --> 00:48:31.900 align:middle line:84% So basically, HQ would not learn about site B and site 00:48:31.900 --> 00:48:34.850 align:middle line:84% B would not learn about HQ from SME. 00:48:34.850 --> 00:48:38.050 align:middle line:84% So make sure you enable this checkbox, 00:48:38.050 --> 00:48:41.450 align:middle line:84% give any route string that you want. 00:48:41.450 --> 00:48:43.240 align:middle line:90% Let's just say it's SME. 00:48:43.240 --> 00:48:46.510 align:middle line:84% And synchronize, let's say every one minute. 00:48:46.510 --> 00:48:49.520 align:middle line:84% I don't want to use TLS, let's use a password. 00:48:49.520 --> 00:48:55.120 align:middle line:90% Let's use a password c1sc0123! 00:48:55.120 --> 00:48:57.560 align:middle line:90% and c1sc0123!. 00:48:57.560 --> 00:49:00.040 align:middle line:90% And save. 00:49:00.040 --> 00:49:06.830 align:middle line:90% 00:49:06.830 --> 00:49:09.170 align:middle line:84% It'll ask you for the registration server since he 00:49:09.170 --> 00:49:10.400 align:middle line:90% himself is the hub. 00:49:10.400 --> 00:49:13.670 align:middle line:84% I don't need to specify any registration server. 00:49:13.670 --> 00:49:14.360 align:middle line:90% Just do OK. 00:49:14.360 --> 00:49:48.440 align:middle line:90% 00:49:48.440 --> 00:49:51.035 align:middle line:84% Once you've done that, make sure you do a save again. 00:49:51.035 --> 00:49:55.910 align:middle line:90% 00:49:55.910 --> 00:49:57.570 align:middle line:90% And one hub is found right now. 00:49:57.570 --> 00:49:58.820 align:middle line:90% There are no spokes right now. 00:49:58.820 --> 00:50:04.520 align:middle line:84% Let's go now to site B. Go to Advanced Features, 00:50:04.520 --> 00:50:13.640 align:middle line:84% ILS configuration, make him into a spoke. 00:50:13.640 --> 00:50:15.500 align:middle line:84% So he would be a spoke cluster, make 00:50:15.500 --> 00:50:19.230 align:middle line:84% sure we enable this because we want routes to be advertised. 00:50:19.230 --> 00:50:21.170 align:middle line:90% So this could be anything. 00:50:21.170 --> 00:50:27.570 align:middle line:84% Let's say site B. And let's use the same password, 00:50:27.570 --> 00:50:33.300 align:middle line:90% which was c1sc0123!. 00:50:33.300 --> 00:50:35.850 align:middle line:90% c1sc0123! 00:50:35.850 --> 00:50:40.260 align:middle line:84% and change your synchronized cluster every one minute. 00:50:40.260 --> 00:50:41.902 align:middle line:90% Let's save this. 00:50:41.902 --> 00:50:43.860 align:middle line:84% They should ask me for the registration server. 00:50:43.860 --> 00:50:46.350 align:middle line:84% Here, I need to define who the hub is. 00:50:46.350 --> 00:50:47.790 align:middle line:90% So my hub was the SME. 00:50:47.790 --> 00:50:50.030 align:middle line:84% So let's give the SME IP address, which is 11.100. 00:50:50.030 --> 00:51:10.390 align:middle line:90% 64.14 and say, OK. 00:51:10.390 --> 00:51:14.760 align:middle line:84% Same thing I would do on HQ, advanced features, 00:51:14.760 --> 00:51:16.210 align:middle line:90% ILS configuration. 00:51:16.210 --> 00:51:21.650 align:middle line:90% 00:51:21.650 --> 00:51:22.660 align:middle line:90% So site B is done. 00:51:22.660 --> 00:51:26.090 align:middle line:90% Make sure you do a Save again. 00:51:26.090 --> 00:51:29.570 align:middle line:90% And you should see the hub. 00:51:29.570 --> 00:51:32.590 align:middle line:84% So if you do a refresh, you should see one hub. 00:51:32.590 --> 00:51:33.475 align:middle line:90% So give it some time. 00:51:33.475 --> 00:51:38.430 align:middle line:90% 00:51:38.430 --> 00:51:41.790 align:middle line:84% In the meanwhile, let's go to the HQ site 00:51:41.790 --> 00:51:43.380 align:middle line:90% and make him also into a spoke. 00:51:43.380 --> 00:51:46.600 align:middle line:90% 00:51:46.600 --> 00:51:51.770 align:middle line:84% Route string would be HQ, this would be every one minute. 00:51:51.770 --> 00:52:00.310 align:middle line:84% Make sure you enable this, this will use the password c1sc0123! 00:52:00.310 --> 00:52:03.790 align:middle line:90% c1sc0123! 00:52:03.790 --> 00:52:05.920 align:middle line:90% and save. 00:52:05.920 --> 00:52:08.560 align:middle line:84% Put the IP address of your hub, which is sme, 00:52:08.560 --> 00:52:32.440 align:middle line:90% 11.100.64.14 and OK. 00:52:32.440 --> 00:52:36.070 align:middle line:84% Let's try going back to ILS configuration just 00:52:36.070 --> 00:52:38.410 align:middle line:84% to see if we've learned about the hub on site 00:52:38.410 --> 00:52:48.670 align:middle line:84% B. It says that it's trying to register to the SME. 00:52:48.670 --> 00:52:51.480 align:middle line:90% Let's wait. 00:52:51.480 --> 00:52:54.780 align:middle line:84% Let's refresh this on the SME and see if we found the spoke. 00:52:54.780 --> 00:53:00.400 align:middle line:90% 00:53:00.400 --> 00:53:01.825 align:middle line:90% So no spokes found yet. 00:53:01.825 --> 00:53:05.010 align:middle line:90% 00:53:05.010 --> 00:53:07.620 align:middle line:90% Let's go back here, save. 00:53:07.620 --> 00:53:29.530 align:middle line:90% 00:53:29.530 --> 00:53:31.000 align:middle line:84% While they're synchronizing, what 00:53:31.000 --> 00:53:33.172 align:middle line:84% I'm going to do is if you look at the question, 00:53:33.172 --> 00:53:34.630 align:middle line:84% there was also one more requirement 00:53:34.630 --> 00:53:38.750 align:middle line:84% that Tony Stark should advertise an alternate number also. 00:53:38.750 --> 00:53:45.640 align:middle line:84% So in the meanwhile, I'm going to go to Device, Phones, 00:53:45.640 --> 00:53:46.930 align:middle line:90% and go to Tony Stark. 00:53:46.930 --> 00:53:54.410 align:middle line:90% 00:53:54.410 --> 00:54:07.470 align:middle line:84% Go to his line and scroll down and add an enterprise alternate 00:54:07.470 --> 00:54:07.970 align:middle line:90% number. 00:54:07.970 --> 00:54:09.230 align:middle line:90% It's not an E16 phone number. 00:54:09.230 --> 00:54:11.410 align:middle line:84% So it's an enterprise alternate number. 00:54:11.410 --> 00:54:12.370 align:middle line:90% Click on that. 00:54:12.370 --> 00:54:18.220 align:middle line:90% And the number was 72022003. 00:54:18.220 --> 00:54:21.340 align:middle line:84% Make sure you add him to the local route partition, which 00:54:21.340 --> 00:54:22.880 align:middle line:90% is your default one. 00:54:22.880 --> 00:54:27.190 align:middle line:90% And advertise this using ILS. 00:54:27.190 --> 00:54:29.410 align:middle line:84% We want to advertise this using ILS. 00:54:29.410 --> 00:54:30.475 align:middle line:90% Let's save this. 00:54:30.475 --> 00:54:38.440 align:middle line:90% 00:54:38.440 --> 00:54:39.295 align:middle line:90% And apply. 00:54:39.295 --> 00:54:44.320 align:middle line:90% 00:54:44.320 --> 00:54:45.385 align:middle line:90% Let's reset him also. 00:54:45.385 --> 00:54:58.860 align:middle line:90% 00:54:58.860 --> 00:55:03.480 align:middle line:84% Now if I go down to-- so this thing, this alternate number 00:55:03.480 --> 00:55:05.100 align:middle line:84% thing, we only did this for Tony Stark 00:55:05.100 --> 00:55:07.710 align:middle line:84% because the question says only for Tony, not for site B, 00:55:07.710 --> 00:55:09.090 align:middle line:90% not for Steve Rogers. 00:55:09.090 --> 00:55:11.310 align:middle line:84% So on HQ, under the device phone, 00:55:11.310 --> 00:55:15.120 align:middle line:84% I added an alternate number for Tony Stark, 00:55:15.120 --> 00:55:18.280 align:middle line:84% which was an enterprise alternate number. 00:55:18.280 --> 00:55:22.590 align:middle line:84% Now if I go down to let's scroll down, 00:55:22.590 --> 00:55:26.100 align:middle line:84% let me minimize the screen a bit. 00:55:26.100 --> 00:55:34.990 align:middle line:84% Go all the way down to call routing and go to-- 00:55:34.990 --> 00:55:42.220 align:middle line:90% 00:55:42.220 --> 00:55:43.960 align:middle line:90% why don't I see it? 00:55:43.960 --> 00:55:45.908 align:middle line:90% Let's minimize even further. 00:55:45.908 --> 00:55:47.200 align:middle line:90% It's not fitting in the screen. 00:55:47.200 --> 00:55:49.900 align:middle line:84% It's a global dial plan replication. 00:55:49.900 --> 00:55:55.340 align:middle line:84% Go to partition for learn numbers. 00:55:55.340 --> 00:56:00.300 align:middle line:90% So one is advertising a URI. 00:56:00.300 --> 00:56:03.240 align:middle line:90% One is advertising a number. 00:56:03.240 --> 00:56:06.773 align:middle line:84% We are advertising a number also besides the URI. 00:56:06.773 --> 00:56:08.190 align:middle line:84% So go to this partition, partition 00:56:08.190 --> 00:56:13.530 align:middle line:84% for learn numbers and patterns to find-- 00:56:13.530 --> 00:56:22.580 align:middle line:90% 00:56:22.580 --> 00:56:32.590 align:middle line:84% If you see the default one, where are we? 00:56:32.590 --> 00:56:34.690 align:middle line:90% Wait hold on. 00:56:34.690 --> 00:56:40.770 align:middle line:84% Let's go back to global dial plan. 00:56:40.770 --> 00:56:41.730 align:middle line:90% Partitions. 00:56:41.730 --> 00:56:44.890 align:middle line:90% 00:56:44.890 --> 00:56:47.500 align:middle line:84% So if you see here, the partition for enterprise 00:56:47.500 --> 00:56:48.580 align:middle line:90% alternate number. 00:56:48.580 --> 00:56:52.340 align:middle line:90% 00:56:52.340 --> 00:56:56.240 align:middle line:84% We basically need to give him access to-- 00:56:56.240 --> 00:57:00.080 align:middle line:90% 00:57:00.080 --> 00:57:02.990 align:middle line:84% we basically need to put him in a partition which 00:57:02.990 --> 00:57:04.763 align:middle line:90% the trunk has access to. 00:57:04.763 --> 00:57:05.930 align:middle line:90% In fact, I'll show you this. 00:57:05.930 --> 00:57:07.180 align:middle line:90% I won't do anything right now. 00:57:07.180 --> 00:57:09.840 align:middle line:84% This call is going to fail, I'll show you why. 00:57:09.840 --> 00:57:12.630 align:middle line:84% So let's just keep as it is right now. 00:57:12.630 --> 00:57:21.520 align:middle line:84% Let's go back and check if I have found. 00:57:21.520 --> 00:57:24.810 align:middle line:84% So now I can see I found one hub and two spokes. 00:57:24.810 --> 00:57:31.910 align:middle line:84% If I look back on site B and let's refresh, 00:57:31.910 --> 00:57:34.220 align:middle line:90% I found one hub and two spokes. 00:57:34.220 --> 00:57:37.970 align:middle line:84% And if I scroll down from the SME, 00:57:37.970 --> 00:57:42.650 align:middle line:84% I have learned HQ and site B. So if I wanted to go to HQ, 00:57:42.650 --> 00:57:48.480 align:middle line:84% I need to route to basically SME. 00:57:48.480 --> 00:57:54.740 align:middle line:84% So if I look at HQ also scroll down, you would see under SME, 00:57:54.740 --> 00:57:57.470 align:middle line:84% I have two routes which is learned HQ 00:57:57.470 --> 00:58:02.790 align:middle line:84% and site B. So at this point of time URI dialing should work. 00:58:02.790 --> 00:58:05.270 align:middle line:84% But the alternate number is going to fail. 00:58:05.270 --> 00:58:08.140 align:middle line:90% URI dialing should work. 00:58:08.140 --> 00:58:16.040 align:middle line:84% Let's go and check by going to Jabber one and dialing 00:58:16.040 --> 00:58:18.140 align:middle line:90% steve-rogers.com. 00:58:18.140 --> 00:58:26.780 align:middle line:84% Let's call and check here if the phone rings. 00:58:26.780 --> 00:58:41.040 align:middle line:90% 00:58:41.040 --> 00:58:44.550 align:middle line:84% So I see that the phone does not ring. 00:58:44.550 --> 00:58:45.960 align:middle line:90% Why is that? 00:58:45.960 --> 00:58:48.600 align:middle line:90% Now think about the call flow. 00:58:48.600 --> 00:58:54.420 align:middle line:84% HQ dials steve-rogers-- steve-rogers@ine.com. 00:58:54.420 --> 00:58:56.980 align:middle line:90% It goes by the SIP trunk to SME. 00:58:56.980 --> 00:58:58.990 align:middle line:84% SME has access to a directory URI 00:58:58.990 --> 00:59:00.640 align:middle line:90% partition on the inbound CSS. 00:59:00.640 --> 00:59:03.430 align:middle line:84% So he forwards it down to trunk to site B. 00:59:03.430 --> 00:59:08.560 align:middle line:84% When it comes to site B on the trunk, when it comes to site B, 00:59:08.560 --> 00:59:10.750 align:middle line:90% site B needs to-- 00:59:10.750 --> 00:59:14.320 align:middle line:84% the trunk needs to have access to the directory URI partition 00:59:14.320 --> 00:59:17.470 align:middle line:90% where that URI is on site B. 00:59:17.470 --> 00:59:25.010 align:middle line:84% So if I look back on site B. Let's go back to site B. 00:59:25.010 --> 00:59:32.178 align:middle line:84% If I look at site B, on my trunk, which 00:59:32.178 --> 00:59:42.890 align:middle line:84% is trunk to SME, my inbound CSS, CSS inbound from SME. 00:59:42.890 --> 00:59:45.860 align:middle line:84% Now if you remember, we had given directory 00:59:45.860 --> 00:59:50.990 align:middle line:84% URI partition access inbound on sme, 00:59:50.990 --> 00:59:52.970 align:middle line:84% for both, from HQ and from site B. 00:59:52.970 --> 00:59:55.490 align:middle line:84% But on HQ and site B, we never configured anything 00:59:55.490 --> 00:59:56.520 align:middle line:90% for the inbound. 00:59:56.520 --> 01:00:00.440 align:middle line:84% So if I look at the call routing under call of Control, 01:00:00.440 --> 01:00:06.490 align:middle line:84% Calling Search Space, the inbound CSS on my trunk, 01:00:06.490 --> 01:00:08.940 align:middle line:84% which is from SME, on site B, does not 01:00:08.940 --> 01:00:10.440 align:middle line:90% have access to directory URIs. 01:00:10.440 --> 01:00:13.140 align:middle line:84% When the call comes in the way to site B, 01:00:13.140 --> 01:00:15.750 align:middle line:84% site B doesn't have access to this partition 01:00:15.750 --> 01:00:18.940 align:middle line:84% because the URI is inside that default partition. 01:00:18.940 --> 01:00:24.950 align:middle line:84% So let's give him access to that, save. 01:00:24.950 --> 01:00:29.750 align:middle line:84% Same thing if site B calls HQ, it goes to SME. 01:00:29.750 --> 01:00:32.810 align:middle line:84% SME's inbound CSS has access to directory URIs. 01:00:32.810 --> 01:00:36.080 align:middle line:84% So it forwards it towards the SIP trunk towards HQ. 01:00:36.080 --> 01:00:40.400 align:middle line:84% Once it reaches HQ, HQ's inbounds CSS from SME 01:00:40.400 --> 01:00:42.320 align:middle line:84% does not have access to directory URI. 01:00:42.320 --> 01:00:47.400 align:middle line:84% So even on HQ, I would have to go and do that. 01:00:47.400 --> 01:00:55.670 align:middle line:84% So under call routing, inbound from SME. 01:00:55.670 --> 01:00:58.850 align:middle line:90% 01:00:58.850 --> 01:01:02.810 align:middle line:84% Give him access to directory URI partition. 01:01:02.810 --> 01:01:04.850 align:middle line:84% See phones need access to directory URI 01:01:04.850 --> 01:01:06.800 align:middle line:90% partition to dial. 01:01:06.800 --> 01:01:10.850 align:middle line:84% But the remote side, trunk needs access to directory URI 01:01:10.850 --> 01:01:13.070 align:middle line:84% to be able to forward the call to the local user. 01:01:13.070 --> 01:01:15.780 align:middle line:90% 01:01:15.780 --> 01:01:19.310 align:middle line:84% So if I look at it from the perspective of-- 01:01:19.310 --> 01:01:21.780 align:middle line:90% let me, in fact, draw this out. 01:01:21.780 --> 01:01:26.370 align:middle line:84% So if I look at it from a perspective of call flow, 01:01:26.370 --> 01:01:28.330 align:middle line:90% so I have my phone. 01:01:28.330 --> 01:01:32.760 align:middle line:84% Phone needs access to directory URI partition. 01:01:32.760 --> 01:01:39.390 align:middle line:84% So in fact, this is directory URI partition. 01:01:39.390 --> 01:01:42.500 align:middle line:84% And this is my call manager here. 01:01:42.500 --> 01:01:45.080 align:middle line:90% This is my SIP trunk to SME. 01:01:45.080 --> 01:01:50.260 align:middle line:90% 01:01:50.260 --> 01:01:53.760 align:middle line:84% And this is my site B call manager. 01:01:53.760 --> 01:01:56.590 align:middle line:90% And I have my phone here. 01:01:56.590 --> 01:02:01.230 align:middle line:84% So for the phone to dial the URI, phone CSS, 01:02:01.230 --> 01:02:04.530 align:middle line:84% device css of the phone needs access to directory URI. 01:02:04.530 --> 01:02:08.730 align:middle line:84% Once it goes to SME, SME's inbound 01:02:08.730 --> 01:02:12.900 align:middle line:84% needs access to directory URI partition. 01:02:12.900 --> 01:02:16.110 align:middle line:84% Once it reaches the site B cluster, 01:02:16.110 --> 01:02:19.620 align:middle line:84% inbound on site B on the trunk side, 01:02:19.620 --> 01:02:23.730 align:middle line:90% I need directory URI access. 01:02:23.730 --> 01:02:26.580 align:middle line:84% This is for calls going in this direction. 01:02:26.580 --> 01:02:28.740 align:middle line:84% If the call is going in this direction, 01:02:28.740 --> 01:02:32.490 align:middle line:84% then the phone here needs access to a directory URI, 01:02:32.490 --> 01:02:36.780 align:middle line:84% then here's inbound on SME from site B, 01:02:36.780 --> 01:02:41.700 align:middle line:84% I would need directory URI, and then inbound on HQ, 01:02:41.700 --> 01:02:44.160 align:middle line:84% I would need access to directory URI. 01:02:44.160 --> 01:02:45.820 align:middle line:90% This is what I need. 01:02:45.820 --> 01:02:47.655 align:middle line:90% So let's do that. 01:02:47.655 --> 01:02:51.730 align:middle line:90% 01:02:51.730 --> 01:02:54.405 align:middle line:84% So we've done that, let's try making the call again. 01:02:54.405 --> 01:03:00.310 align:middle line:90% 01:03:00.310 --> 01:03:06.670 align:middle line:90% steve-rogers@ime.com let's call. 01:03:06.670 --> 01:03:10.770 align:middle line:84% Go to site B. And now as you can see 01:03:10.770 --> 01:03:18.060 align:middle line:84% that I see the call coming in from Tony Stark and the call 01:03:18.060 --> 01:03:18.700 align:middle line:90% works. 01:03:18.700 --> 01:03:21.390 align:middle line:90% So I'm basically dialing URI. 01:03:21.390 --> 01:03:26.040 align:middle line:84% Let's in fact-- is it going to go through R1 and R2, which 01:03:26.040 --> 01:03:29.730 align:middle line:90% is my gateway routers? 01:03:29.730 --> 01:03:31.920 align:middle line:90% Not really because we're not-- 01:03:31.920 --> 01:03:34.910 align:middle line:90% or in fact, you know what? 01:03:34.910 --> 01:03:36.800 align:middle line:84% We're going from SME-- no, in fact, it's not 01:03:36.800 --> 01:03:40.640 align:middle line:84% going to go through router 1 because my trunk is to SME 01:03:40.640 --> 01:03:42.890 align:middle line:84% and SME has a trunk direct to site B. 01:03:42.890 --> 01:03:45.060 align:middle line:84% So it's not going to go through R1 and R2. 01:03:45.060 --> 01:03:49.580 align:middle line:84% So we can't really check why by doing a debug CC SIP messages. 01:03:49.580 --> 01:03:52.875 align:middle line:84% But I am making the call using URI. 01:03:52.875 --> 01:03:58.100 align:middle line:90% 01:03:58.100 --> 01:04:00.760 align:middle line:90% Let's end this call. 01:04:00.760 --> 01:04:02.545 align:middle line:90% Let's try from site B also. 01:04:02.545 --> 01:04:05.880 align:middle line:90% 01:04:05.880 --> 01:04:08.150 align:middle line:90% So I'm going to dial Tony Stark. 01:04:08.150 --> 01:04:15.340 align:middle line:90% 01:04:15.340 --> 01:04:18.370 align:middle line:84% So I see the call coming in from Steve Rogers. 01:04:18.370 --> 01:04:20.300 align:middle line:90% And I'm able to make that call. 01:04:20.300 --> 01:04:23.620 align:middle line:84% So right now, one thing what we've done 01:04:23.620 --> 01:04:26.980 align:middle line:84% is we've basically configured ILS 01:04:26.980 --> 01:04:29.680 align:middle line:84% so that both the Jabber users, both sides, 01:04:29.680 --> 01:04:31.720 align:middle line:90% can dial each other using URI. 01:04:31.720 --> 01:04:34.960 align:middle line:84% Basically, HQ users can dial site B 01:04:34.960 --> 01:04:38.500 align:middle line:84% using the username@ine.com and site 01:04:38.500 --> 01:04:44.110 align:middle line:84% B can dial HQ by putting the username at ine.com. 01:04:44.110 --> 01:04:45.850 align:middle line:90% So one part is done. 01:04:45.850 --> 01:04:55.300 align:middle line:84% The next requirement was to see if our alternate extension is-- 01:04:55.300 --> 01:04:57.640 align:middle line:90% if I'm able to dial that. 01:04:57.640 --> 01:04:58.990 align:middle line:90% Let me, in fact cancel this. 01:04:58.990 --> 01:05:06.860 align:middle line:90% 01:05:06.860 --> 01:05:09.470 align:middle line:90% And let's look at that. 01:05:09.470 --> 01:05:11.510 align:middle line:84% I think that call is going to fail. 01:05:11.510 --> 01:05:12.510 align:middle line:90% Let's try it. 01:05:12.510 --> 01:05:20.000 align:middle line:84% So from site B which is here, let's end this. 01:05:20.000 --> 01:05:27.200 align:middle line:90% I will dial 72022003. 01:05:27.200 --> 01:05:30.695 align:middle line:84% So I'm dialing this number, which is of Tony Stark. 01:05:30.695 --> 01:05:36.120 align:middle line:90% 01:05:36.120 --> 01:05:39.480 align:middle line:84% Let's see on HQ if the call rings on Tony Stark. 01:05:39.480 --> 01:06:03.300 align:middle line:90% 01:06:03.300 --> 01:06:05.880 align:middle line:84% So it's not really ringing on Tony's number 01:06:05.880 --> 01:06:07.860 align:middle line:90% because the call is failing. 01:06:07.860 --> 01:06:09.690 align:middle line:84% And like I said earlier, that call 01:06:09.690 --> 01:06:15.390 align:middle line:84% is going to fail because you don't really have access 01:06:15.390 --> 01:06:20.790 align:middle line:84% to that alternate number because by default the alternate number 01:06:20.790 --> 01:06:27.810 align:middle line:84% goes in a specific partition which you don't have access to. 01:06:27.810 --> 01:06:32.820 align:middle line:84% If I look back at HQ site and let's say if I go to Device, 01:06:32.820 --> 01:06:46.820 align:middle line:84% Phones, go to-- in fact check on HQ Device Phones, 01:06:46.820 --> 01:06:47.810 align:middle line:90% go to Tony Stark. 01:06:47.810 --> 01:06:51.210 align:middle line:90% 01:06:51.210 --> 01:06:51.960 align:middle line:90% Go to your line. 01:06:51.960 --> 01:07:00.340 align:middle line:90% 01:07:00.340 --> 01:07:05.500 align:middle line:84% And scroll down to your alternate number. 01:07:05.500 --> 01:07:08.290 align:middle line:84% We never defined any route partition 01:07:08.290 --> 01:07:13.030 align:middle line:84% as such here, which means that this alternate number is going 01:07:13.030 --> 01:07:18.520 align:middle line:90% to be in the default partition. 01:07:18.520 --> 01:07:20.950 align:middle line:84% And my phones don't have access to that. 01:07:20.950 --> 01:07:25.160 align:middle line:84% My remote site also doesn't have access to that. 01:07:25.160 --> 01:07:26.680 align:middle line:84% So let's in fact troubleshoot this 01:07:26.680 --> 01:07:30.700 align:middle line:84% and see how we can get this to work now. 01:07:30.700 --> 01:07:32.920 align:middle line:84% So to troubleshoot this what we're going to do 01:07:32.920 --> 01:07:34.780 align:middle line:84% is, first thing that we will do is 01:07:34.780 --> 01:07:41.110 align:middle line:84% we will check if you've actually learned that partition. 01:07:41.110 --> 01:07:42.830 align:middle line:84% That's the first thing that we will do. 01:07:42.830 --> 01:07:47.080 align:middle line:84% So what I'm going to do is first go to HQ side 01:07:47.080 --> 01:07:50.290 align:middle line:90% and go on the call routing. 01:07:50.290 --> 01:07:53.020 align:middle line:84% Go to Global Dial Plan Replication 01:07:53.020 --> 01:07:55.510 align:middle line:84% and look at Learning Directory URIs. 01:07:55.510 --> 01:07:59.830 align:middle line:84% So we know that HQ is able to dial site B using URI 01:07:59.830 --> 01:08:01.160 align:middle line:90% because we just tested that. 01:08:01.160 --> 01:08:05.890 align:middle line:84% So we know that he must have learned steve-rogers@ine.com. 01:08:05.890 --> 01:08:08.950 align:middle line:84% He learned this you are from site B through SME. 01:08:08.950 --> 01:08:11.380 align:middle line:84% Similarly, if I go to site B and go 01:08:11.380 --> 01:08:14.440 align:middle line:84% to call routing under Global Dial Plan 01:08:14.440 --> 01:08:17.859 align:middle line:84% Replication under a learned directory URI, 01:08:17.859 --> 01:08:22.569 align:middle line:84% you would see that he has learned three URIs from HQ site 01:08:22.569 --> 01:08:24.850 align:middle line:84% through SME, which you can see here. 01:08:24.850 --> 01:08:27.880 align:middle line:84% But HQ Tony Stark was also advertising 01:08:27.880 --> 01:08:29.493 align:middle line:90% an alternate number. 01:08:29.493 --> 01:08:30.910 align:middle line:84% So let's see if he's learned that, 01:08:30.910 --> 01:08:32.680 align:middle line:90% if site B has learned that. 01:08:32.680 --> 01:08:36.729 align:middle line:84% If I look at site B and go to learn numbers. 01:08:36.729 --> 01:08:39.550 align:middle line:84% I should see that new number, which Tony Stark was 01:08:39.550 --> 01:08:41.510 align:middle line:90% advertising, I should see that. 01:08:41.510 --> 01:08:47.470 align:middle line:84% So 72022003 is being learned from cluster ID HQ, 01:08:47.470 --> 01:08:49.000 align:middle line:90% route string is HQ. 01:08:49.000 --> 01:08:54.310 align:middle line:84% And if you notice that when HQ advertises that alternate route 01:08:54.310 --> 01:08:57.850 align:middle line:84% or alternate number, he puts that in the partition globally 01:08:57.850 --> 01:09:00.010 align:middle line:90% learned enterprise numbers. 01:09:00.010 --> 01:09:01.569 align:middle line:90% It's in this partition. 01:09:01.569 --> 01:09:04.149 align:middle line:84% Does my phone have access to that? 01:09:04.149 --> 01:09:07.779 align:middle line:84% My phone my Jabber user site B is going to dial that, 01:09:07.779 --> 01:09:09.590 align:middle line:84% but he doesn't have access to that. 01:09:09.590 --> 01:09:12.130 align:middle line:84% So what I need to do is on site B, 01:09:12.130 --> 01:09:17.109 align:middle line:84% I don't need to do this on HQ because on HQ, it's 01:09:17.109 --> 01:09:18.580 align:middle line:90% a local user. 01:09:18.580 --> 01:09:20.470 align:middle line:90% It's a user on HQ itself. 01:09:20.470 --> 01:09:25.420 align:middle line:84% On site B, site B is going to be dialing 72022003 01:09:25.420 --> 01:09:28.399 align:middle line:84% and he needs access to this partition. 01:09:28.399 --> 01:09:36.010 align:middle line:84% So if I look at my phone CSS, calling search space, which 01:09:36.010 --> 01:09:42.330 align:middle line:84% is CSS Phones, it doesn't have access to that partition. 01:09:42.330 --> 01:09:44.279 align:middle line:90% And which was that partition? 01:09:44.279 --> 01:09:48.270 align:middle line:84% If you go back to, let's say HQ and go to global plan 01:09:48.270 --> 01:09:51.630 align:middle line:84% replication learn numbers, he's not learning anything. 01:09:51.630 --> 01:09:53.490 align:middle line:84% HQ is not learning anything from site B 01:09:53.490 --> 01:09:56.820 align:middle line:84% because site B is not advertising a lone number. 01:09:56.820 --> 01:09:59.700 align:middle line:84% Site B is only advertising a URI. 01:09:59.700 --> 01:10:02.970 align:middle line:84% HQ is advertising URI and learn numbers. 01:10:02.970 --> 01:10:04.560 align:middle line:90% And basically alternate number. 01:10:04.560 --> 01:10:08.070 align:middle line:84% And by default that was inside a different partition, 01:10:08.070 --> 01:10:09.430 align:middle line:90% which you can see here. 01:10:09.430 --> 01:10:12.840 align:middle line:84% So either you have a choice of adding 01:10:12.840 --> 01:10:15.630 align:middle line:84% global learned enterprise numbers 01:10:15.630 --> 01:10:19.950 align:middle line:84% and give the phone access to that partition or you could 01:10:19.950 --> 01:10:27.150 align:middle line:84% go on site B, go here to partitions for learn members-- 01:10:27.150 --> 01:10:31.830 align:middle line:84% for learn numbers and patterns, go here, 01:10:31.830 --> 01:10:35.160 align:middle line:84% and change the partition of the enterprise 01:10:35.160 --> 01:10:37.020 align:middle line:84% alternate numbers from this global 01:10:37.020 --> 01:10:39.240 align:middle line:84% learned enterprise numbers to a partition 01:10:39.240 --> 01:10:42.210 align:middle line:84% which your phone has access to, for example, PT Intersite. 01:10:42.210 --> 01:10:44.520 align:middle line:84% If I change this also, it will work. 01:10:44.520 --> 01:10:48.420 align:middle line:84% Or if I give the phone access to that global learned enterprise 01:10:48.420 --> 01:10:51.100 align:middle line:84% numbers, again, that would work also. 01:10:51.100 --> 01:10:52.380 align:middle line:90% So either one you can do. 01:10:52.380 --> 01:10:53.310 align:middle line:90% Let's save this. 01:10:53.310 --> 01:10:58.230 align:middle line:90% 01:10:58.230 --> 01:11:01.820 align:middle line:84% And now if I look back at call routing, 01:11:01.820 --> 01:11:09.850 align:middle line:84% and look at learn numbers, the partition for that number 01:11:09.850 --> 01:11:12.770 align:middle line:84% is now PT Intersite which my phone has access to. 01:11:12.770 --> 01:11:20.260 align:middle line:84% So now if I go back to Steve Rogers which is on Jabber 2 01:11:20.260 --> 01:11:31.145 align:middle line:84% and dial 72022003 and hit Enter, it should ring on Tony Stark. 01:11:31.145 --> 01:11:39.530 align:middle line:90% 01:11:39.530 --> 01:11:40.595 align:middle line:90% Let's give it some time. 01:11:40.595 --> 01:11:51.250 align:middle line:90% 01:11:51.250 --> 01:11:55.840 align:middle line:84% It's still not going to ring because again my trunks need 01:11:55.840 --> 01:11:59.660 align:middle line:84% access to that enterprise partition. 01:11:59.660 --> 01:12:06.490 align:middle line:84% So what I would do is go to my HQ go under my Class 01:12:06.490 --> 01:12:17.780 align:middle line:84% Of Control go to Calling Search Space. 01:12:17.780 --> 01:12:24.680 align:middle line:84% And my inbound from SME, I would give access to globally learned 01:12:24.680 --> 01:12:33.720 align:middle line:84% enterprise number, give them access to that, 01:12:33.720 --> 01:12:45.020 align:middle line:84% then go to HQ Calling Search Space, inbound from SME, 01:12:45.020 --> 01:12:47.610 align:middle line:84% give access to globally learn enterprise numbers. 01:12:47.610 --> 01:12:53.080 align:middle line:90% 01:12:53.080 --> 01:12:55.090 align:middle line:90% Go to SME, onboard the trunks. 01:12:55.090 --> 01:13:08.440 align:middle line:90% 01:13:08.440 --> 01:13:11.140 align:middle line:84% So we have two trucks here on SME, one towards HQ, 01:13:11.140 --> 01:13:13.720 align:middle line:84% one toward site B. And there's an inbound CSS 01:13:13.720 --> 01:13:14.750 align:middle line:90% on each one of them. 01:13:14.750 --> 01:13:16.450 align:middle line:84% So both of them would need access 01:13:16.450 --> 01:13:24.780 align:middle line:90% to the default partition. 01:13:24.780 --> 01:13:31.140 align:middle line:84% So I would go to Class of Control, Calling Search Space, 01:13:31.140 --> 01:13:37.400 align:middle line:84% to find one is HQ, from HQ, give him 01:13:37.400 --> 01:13:38.700 align:middle line:90% access to enterprise numbers. 01:13:38.700 --> 01:13:42.510 align:middle line:90% 01:13:42.510 --> 01:13:54.145 align:middle line:84% And then from site B, give him access to enterprise numbers. 01:13:54.145 --> 01:13:59.320 align:middle line:90% 01:13:59.320 --> 01:14:01.800 align:middle line:84% So all my trunks have access to enterprise numbers, 01:14:01.800 --> 01:14:05.130 align:middle line:84% on HQ, on site B, and two on SME. 01:14:05.130 --> 01:14:09.420 align:middle line:84% On site B's phone has access to PT intersite 01:14:09.420 --> 01:14:12.450 align:middle line:84% because we changed the partition for the phone 01:14:12.450 --> 01:14:14.800 align:middle line:90% to be in the PT intersite. 01:14:14.800 --> 01:14:17.700 align:middle line:84% So if I had not changed that, even the phone CSS 01:14:17.700 --> 01:14:22.850 align:middle line:84% would require access to global enterprise number. 01:14:22.850 --> 01:14:33.880 align:middle line:84% Let's go and retry by dialing 72022003. 01:14:33.880 --> 01:14:34.930 align:middle line:90% And look back here. 01:14:34.930 --> 01:14:36.070 align:middle line:90% Now, the phone rings. 01:14:36.070 --> 01:14:39.290 align:middle line:84% And as you can see, I see that URI also, 01:14:39.290 --> 01:14:45.040 align:middle line:84% which is steve-rogers@ine.com which basically means that I 01:14:45.040 --> 01:14:48.700 align:middle line:84% have successfully completed the task where I configure ILS, 01:14:48.700 --> 01:14:51.500 align:middle line:84% where I can now do URI dialing, at the same time, 01:14:51.500 --> 01:14:53.840 align:middle line:84% I can dial the alternate extension, 01:14:53.840 --> 01:14:57.400 align:middle line:84% which HQ user is advertising through ILS. 01:14:57.400 --> 01:15:00.400 align:middle line:84% But just make sure that you have the correct partitions 01:15:00.400 --> 01:15:02.680 align:middle line:84% given to your trunks and to your phones. 01:15:02.680 --> 01:15:04.870 align:middle line:84% So phones, for outbound dialing, you 01:15:04.870 --> 01:15:07.540 align:middle line:84% would require access to directory URI. 01:15:07.540 --> 01:15:09.190 align:middle line:84% If you're dialing the alternate number, 01:15:09.190 --> 01:15:12.370 align:middle line:84% you require access to the enterprise alternate number 01:15:12.370 --> 01:15:14.930 align:middle line:84% partition, which is, again, the default one. 01:15:14.930 --> 01:15:16.870 align:middle line:84% And all your trunks require access 01:15:16.870 --> 01:15:21.250 align:middle line:84% to directory URI and the alternate number partition. 01:15:21.250 --> 01:15:23.120 align:middle line:84% I hope this video was informative for you. 01:15:23.120 --> 01:15:25.500 align:middle line:90% And thank you for watching. 01:15:25.500 --> 01:15:26.000 align:middle line:90%