WEBVTT 00:00:00.000 --> 00:00:03.444 align:middle line:90% 00:00:03.444 --> 00:00:06.888 align:middle line:90% [AUDIO LOGO] 00:00:06.888 --> 00:00:09.840 align:middle line:90% 00:00:09.840 --> 00:00:12.255 align:middle line:90% Hello, and welcome to INE. 00:00:12.255 --> 00:00:15.510 align:middle line:84% Today in this video, we will look at section 6, CMS, 00:00:15.510 --> 00:00:18.360 align:middle line:90% basically task 6.3. 00:00:18.360 --> 00:00:20.280 align:middle line:84% Now, here on this task it says that we 00:00:20.280 --> 00:00:22.560 align:middle line:84% need to configure a SIP trunk between the call 00:00:22.560 --> 00:00:26.190 align:middle line:84% manager and CMS to allow users and endpoints that 00:00:26.190 --> 00:00:29.970 align:middle line:84% are registered to the call manager to dial into CMS 00:00:29.970 --> 00:00:34.450 align:middle line:84% and connect with users who have their cospaces. 00:00:34.450 --> 00:00:39.390 align:middle line:84% And we also need to configure an interactive voice response 00:00:39.390 --> 00:00:42.930 align:middle line:84% on the CMS that will prompt callers to enter the space 00:00:42.930 --> 00:00:45.390 align:middle line:90% ID to join the CMS space. 00:00:45.390 --> 00:00:48.990 align:middle line:84% Set the IVR to respond to extension 8888. 00:00:48.990 --> 00:00:54.270 align:middle line:84% In short, Tony Stark can dial this IVR from Jabber 1 PC. 00:00:54.270 --> 00:00:57.000 align:middle line:84% You are allowed to create a route pattern on the call 00:00:57.000 --> 00:00:57.960 align:middle line:90% manager. 00:00:57.960 --> 00:01:00.930 align:middle line:84% Now, before we actually do this task, 00:01:00.930 --> 00:01:05.310 align:middle line:84% the first thing what we're going to do is log into CMS 00:01:05.310 --> 00:01:09.100 align:middle line:84% and see the cospaces that we created in the earlier video. 00:01:09.100 --> 00:01:12.360 align:middle line:84% So if I look at my CMS, and let's say 00:01:12.360 --> 00:01:19.300 align:middle line:84% I log in and go to Configuration, Spaces, 00:01:19.300 --> 00:01:23.440 align:middle line:84% you would see that in the earlier video 6.2, task 6.2, 00:01:23.440 --> 00:01:27.310 align:middle line:84% we had configured the cospaces for users belonging 00:01:27.310 --> 00:01:30.070 align:middle line:90% to the organization HQ. 00:01:30.070 --> 00:01:34.420 align:middle line:84% So we have three cospaces here, one for hq-one, one for hq-two, 00:01:34.420 --> 00:01:38.860 align:middle line:84% and one for hq-three, in fact, one for Tony Stark. 00:01:38.860 --> 00:01:40.510 align:middle line:90% I don't see the name here. 00:01:40.510 --> 00:01:43.000 align:middle line:84% I believe in the earlier video, we did not really 00:01:43.000 --> 00:01:46.550 align:middle line:90% configure the cospace name. 00:01:46.550 --> 00:01:49.810 align:middle line:84% So let's say if something like this happens in the lab exam, 00:01:49.810 --> 00:01:51.910 align:middle line:84% let's say, if there was a requirement where 00:01:51.910 --> 00:01:55.480 align:middle line:84% you wanted the name to be there, you 00:01:55.480 --> 00:02:01.420 align:middle line:84% can always go back and edit your GID mappings 00:02:01.420 --> 00:02:05.930 align:middle line:84% or basically your mappings, your LDAP mappings and resynchronize 00:02:05.930 --> 00:02:08.419 align:middle line:90% so that these names come up. 00:02:08.419 --> 00:02:10.930 align:middle line:84% Again, this is not a part of the task, 00:02:10.930 --> 00:02:12.310 align:middle line:90% but I'll just show it to you. 00:02:12.310 --> 00:02:13.810 align:middle line:84% Let's say if you made some mistake 00:02:13.810 --> 00:02:16.850 align:middle line:84% and you want to rectify it, how do you actually do it? 00:02:16.850 --> 00:02:19.180 align:middle line:84% So I'll show you that first, and then I 00:02:19.180 --> 00:02:22.810 align:middle line:84% will come back to task 6.3 and show you 00:02:22.810 --> 00:02:24.410 align:middle line:90% how we can achieve that. 00:02:24.410 --> 00:02:31.150 align:middle line:84% So going back to my Postman, I believe 00:02:31.150 --> 00:02:34.810 align:middle line:90% I have my Postman opened up. 00:02:34.810 --> 00:02:35.755 align:middle line:90% Let's open that up. 00:02:35.755 --> 00:02:40.410 align:middle line:90% 00:02:40.410 --> 00:02:42.270 align:middle line:90% So open up Postman. 00:02:42.270 --> 00:02:50.100 align:middle line:84% Make sure that you have the SSL certificate check disabled. 00:02:50.100 --> 00:02:54.660 align:middle line:90% I believe that is disabled. 00:02:54.660 --> 00:02:56.310 align:middle line:90% It is disabled. 00:02:56.310 --> 00:02:57.490 align:middle line:90% Let's go back. 00:02:57.490 --> 00:02:59.130 align:middle line:90% So I have these tabs here. 00:02:59.130 --> 00:03:03.720 align:middle line:84% If you remember in the earlier video, we had done-- 00:03:03.720 --> 00:03:08.880 align:middle line:84% we basically did the LDAP server. 00:03:08.880 --> 00:03:10.140 align:middle line:90% This was the LDAP server. 00:03:10.140 --> 00:03:13.920 align:middle line:84% Let's do a GET so that we see the response here. 00:03:13.920 --> 00:03:15.480 align:middle line:90% This was the LDAP server. 00:03:15.480 --> 00:03:18.600 align:middle line:84% I believe this was the LDAP mapping. 00:03:18.600 --> 00:03:20.800 align:middle line:90% Let's do a GET here as well. 00:03:20.800 --> 00:03:22.740 align:middle line:90% This was my LDAP mapping. 00:03:22.740 --> 00:03:27.120 align:middle line:84% Let's go to-- this was my LDAP sources. 00:03:27.120 --> 00:03:30.040 align:middle line:90% Let's do a GET. 00:03:30.040 --> 00:03:34.160 align:middle line:84% And then I had my LDAP sync here. 00:03:34.160 --> 00:03:35.740 align:middle line:90% Let's do a GET. 00:03:35.740 --> 00:03:38.340 align:middle line:90% So what you can do is-- 00:03:38.340 --> 00:03:40.000 align:middle line:84% in fact, the LDAP sync is already done. 00:03:40.000 --> 00:03:42.120 align:middle line:84% So we don't really have to do anything. 00:03:42.120 --> 00:03:45.330 align:middle line:90% Let's go back to LDAP-- 00:03:45.330 --> 00:03:47.340 align:middle line:90% this was the LDAP sources. 00:03:47.340 --> 00:03:52.270 align:middle line:84% What you can do is go back to your LDAP mapping 00:03:52.270 --> 00:04:01.190 align:middle line:84% and add another entry here, which would be called as-- 00:04:01.190 --> 00:04:02.420 align:middle line:90% I believe it was-- 00:04:02.420 --> 00:04:06.350 align:middle line:84% if you look back at the documentation, 00:04:06.350 --> 00:04:11.180 align:middle line:90% I believe it was cospace name. 00:04:11.180 --> 00:04:15.230 align:middle line:84% Let's go back to the documentation and check that. 00:04:15.230 --> 00:04:18.110 align:middle line:84% I believe it was the cospace name. 00:04:18.110 --> 00:04:19.130 align:middle line:90% Let's go and check. 00:04:19.130 --> 00:04:20.130 align:middle line:90% What do we have here? 00:04:20.130 --> 00:04:22.730 align:middle line:84% So we have cospace calling ID mapping. 00:04:22.730 --> 00:04:27.900 align:middle line:84% We have the cospace secondary URI mapping. 00:04:27.900 --> 00:04:35.250 align:middle line:90% And then we have name mapping. 00:04:35.250 --> 00:04:36.950 align:middle line:84% So I have the name mapping, but I don't 00:04:36.950 --> 00:04:38.760 align:middle line:90% have the cospaceNameMapping. 00:04:38.760 --> 00:04:42.150 align:middle line:84% So let's go and add that, so cospaceNameMapping. 00:04:42.150 --> 00:04:46.050 align:middle line:90% 00:04:46.050 --> 00:04:48.870 align:middle line:90% And here we would give it as-- 00:04:48.870 --> 00:04:56.550 align:middle line:84% let's give the name as dollar, cn common name, dollar, 00:04:56.550 --> 00:05:01.650 align:middle line:90% apostrophe s Meeting Space. 00:05:01.650 --> 00:05:04.890 align:middle line:84% Now, obviously, we want to not create a new entry. 00:05:04.890 --> 00:05:06.400 align:middle line:90% We want to modify it. 00:05:06.400 --> 00:05:09.510 align:middle line:84% So we would go and change this to put 00:05:09.510 --> 00:05:15.570 align:middle line:84% what would basically add this entry into the existing LDAP 00:05:15.570 --> 00:05:16.500 align:middle line:90% mapping. 00:05:16.500 --> 00:05:17.475 align:middle line:90% Let's going to a Send. 00:05:17.475 --> 00:05:20.130 align:middle line:90% 00:05:20.130 --> 00:05:21.930 align:middle line:90% It says there was a failure. 00:05:21.930 --> 00:05:24.900 align:middle line:84% Obviously, we have to go back and specify-- 00:05:24.900 --> 00:05:26.580 align:middle line:84% whenever you're making changes, you 00:05:26.580 --> 00:05:30.390 align:middle line:84% have to actually go and specify the ID. 00:05:30.390 --> 00:05:42.670 align:middle line:84% So let's copy this ID and paste it here, forward slash, paste, 00:05:42.670 --> 00:05:48.580 align:middle line:84% and then you can do PUT and Send. 00:05:48.580 --> 00:05:49.720 align:middle line:90% So 200 OK. 00:05:49.720 --> 00:05:53.220 align:middle line:90% Let's do a GET now. 00:05:53.220 --> 00:05:55.340 align:middle line:84% And if I do a GET with the ID, you 00:05:55.340 --> 00:05:57.330 align:middle line:90% would see all your entries here. 00:05:57.330 --> 00:06:01.040 align:middle line:84% So I have the name mapping, CDR mapping, cospace mapping, 00:06:01.040 --> 00:06:04.490 align:middle line:84% coSpaceUriMapping, SecondaryUriMapping, 00:06:04.490 --> 00:06:05.850 align:middle line:90% and authentication. 00:06:05.850 --> 00:06:08.030 align:middle line:90% So my mapping is done. 00:06:08.030 --> 00:06:13.940 align:middle line:84% I would now need to go back to my LDAP sources. 00:06:13.940 --> 00:06:16.115 align:middle line:90% And let's do a GET. 00:06:16.115 --> 00:06:20.190 align:middle line:90% 00:06:20.190 --> 00:06:22.930 align:middle line:90% Let's do a GET. 00:06:22.930 --> 00:06:23.860 align:middle line:90% Let's resync. 00:06:23.860 --> 00:06:30.350 align:middle line:84% So I'm going to go back here and do a POST to a LDAP sync. 00:06:30.350 --> 00:06:33.110 align:middle line:84% I don't have to change my LDAP source because the source is 00:06:33.110 --> 00:06:33.900 align:middle line:90% still the same. 00:06:33.900 --> 00:06:35.360 align:middle line:84% I haven't really made any changes. 00:06:35.360 --> 00:06:37.700 align:middle line:84% I only modified the LDAP mapping. 00:06:37.700 --> 00:06:41.510 align:middle line:84% I did not create a new LDAP mapping. 00:06:41.510 --> 00:06:44.270 align:middle line:84% I did PUT, which basically modifies the current LDAP 00:06:44.270 --> 00:06:44.990 align:middle line:90% mapping. 00:06:44.990 --> 00:06:46.850 align:middle line:84% And because the same mapping is being 00:06:46.850 --> 00:06:50.030 align:middle line:84% used in the LDAP source, which is being called here, 00:06:50.030 --> 00:06:52.640 align:middle line:84% if you look at the body, it's being called 00:06:52.640 --> 00:06:55.880 align:middle line:84% inside the same LDAP mapping, ID is being called here, 00:06:55.880 --> 00:06:58.830 align:middle line:84% I don't have to make any changes to LDAP sync. 00:06:58.830 --> 00:07:00.530 align:middle line:90% And all I can do is do a sync. 00:07:00.530 --> 00:07:04.970 align:middle line:90% Let's do a GET and see. 00:07:04.970 --> 00:07:06.840 align:middle line:90% I have three entries. 00:07:06.840 --> 00:07:08.240 align:middle line:90% Let's go back to-- 00:07:08.240 --> 00:07:12.170 align:middle line:84% let's minimize this and go back to my CMS. 00:07:12.170 --> 00:07:14.990 align:middle line:90% And let's do Spaces. 00:07:14.990 --> 00:07:19.490 align:middle line:84% I now see the name here, which is Tony Stark's Meeting Space, 00:07:19.490 --> 00:07:23.220 align:middle line:84% hq one's Meeting Space, and hq two's Meeting Space. 00:07:23.220 --> 00:07:26.690 align:middle line:84% So all you have to do is go and modify your LDAP 00:07:26.690 --> 00:07:30.980 align:middle line:84% mapping to have that entry for the cospaceNameMapping, 00:07:30.980 --> 00:07:35.160 align:middle line:84% and give the common name and some words, if you want. 00:07:35.160 --> 00:07:40.530 align:middle line:84% So I gave-- it as $cn$'s Meeting Space. 00:07:40.530 --> 00:07:44.990 align:middle line:84% So it shows you as the common-- the name, Tony Stark's Meeting 00:07:44.990 --> 00:07:45.890 align:middle line:90% Space. 00:07:45.890 --> 00:07:48.673 align:middle line:84% And everything else is still the same. 00:07:48.673 --> 00:07:50.340 align:middle line:84% So you see, if you want to make changes, 00:07:50.340 --> 00:07:53.270 align:middle line:84% you can always go and make changes to your settings. 00:07:53.270 --> 00:07:55.740 align:middle line:84% Or if you want, you can delete your LDAP mapping, 00:07:55.740 --> 00:07:58.640 align:middle line:84% you can delete your LDAP sources, delete your LDAP sync, 00:07:58.640 --> 00:08:00.560 align:middle line:84% and then recreate the LDAP mapping, 00:08:00.560 --> 00:08:03.620 align:middle line:84% recreate the LDAP source, and then do a sync again. 00:08:03.620 --> 00:08:05.120 align:middle line:84% So it's really up to you if you want 00:08:05.120 --> 00:08:09.420 align:middle line:84% to make the changes by deleting it or by modifying it. 00:08:09.420 --> 00:08:13.070 align:middle line:84% So coming back now, we will now go and do our task, the task 00:08:13.070 --> 00:08:14.100 align:middle line:90% requirements. 00:08:14.100 --> 00:08:15.860 align:middle line:84% So the first requirement was obviously 00:08:15.860 --> 00:08:23.810 align:middle line:84% to create a SIP trunk between the call manager and your CMS. 00:08:23.810 --> 00:08:25.730 align:middle line:84% So to create the SIP trunk, the first thing 00:08:25.730 --> 00:08:28.940 align:middle line:84% that we would need to do is create a SIP trunk security 00:08:28.940 --> 00:08:29.820 align:middle line:90% profile. 00:08:29.820 --> 00:08:32.450 align:middle line:84% So let's go back to our call manager. 00:08:32.450 --> 00:08:38.900 align:middle line:84% Go to System Security, so System Security, SIP Trunk Security 00:08:38.900 --> 00:08:40.340 align:middle line:90% Profile. 00:08:40.340 --> 00:08:43.700 align:middle line:84% And here we would create a new SIP Trunk Security 00:08:43.700 --> 00:08:45.440 align:middle line:90% Profile for CMS. 00:08:45.440 --> 00:08:49.400 align:middle line:84% So let's copy the Non Secure SIP Trunk Security Profile. 00:08:49.400 --> 00:08:50.150 align:middle line:90% Let's copy this. 00:08:50.150 --> 00:08:52.910 align:middle line:90% 00:08:52.910 --> 00:08:55.850 align:middle line:90% And let's name this CMS. 00:08:55.850 --> 00:08:58.520 align:middle line:84% The only thing that we need here-- 00:08:58.520 --> 00:09:02.420 align:middle line:84% the only thing we need here is this checkbox to be enabled, 00:09:02.420 --> 00:09:04.760 align:middle line:90% accept replaces header. 00:09:04.760 --> 00:09:05.850 align:middle line:90% That's all we need. 00:09:05.850 --> 00:09:10.550 align:middle line:84% Let's save this and now create a SIP trunk. 00:09:10.550 --> 00:09:13.060 align:middle line:84% So we will create a SIP trunk which will use this SIP trunk 00:09:13.060 --> 00:09:15.500 align:middle line:90% security profile. 00:09:15.500 --> 00:09:18.650 align:middle line:90% Let's do Add New. 00:09:18.650 --> 00:09:21.150 align:middle line:90% This would be SIP trunk. 00:09:21.150 --> 00:09:29.100 align:middle line:84% Next, let's name this as SIP-TRUNK-TO-CMS. 00:09:29.100 --> 00:09:37.040 align:middle line:90% 00:09:37.040 --> 00:09:40.800 align:middle line:84% Device pool would be the default. 00:09:40.800 --> 00:09:44.030 align:middle line:84% Let's scroll down, run on all active nodes 00:09:44.030 --> 00:09:47.390 align:middle line:84% if you have publisher and subscriber. 00:09:47.390 --> 00:09:50.030 align:middle line:84% If you want to give PSTN access, you can. 00:09:50.030 --> 00:09:52.340 align:middle line:84% Again, you don't really need that. 00:09:52.340 --> 00:09:53.375 align:middle line:90% Let's scroll down. 00:09:53.375 --> 00:09:56.060 align:middle line:90% 00:09:56.060 --> 00:10:00.370 align:middle line:84% Let's enable redirecting header inbound, 00:10:00.370 --> 00:10:02.560 align:middle line:90% redirecting header outbound. 00:10:02.560 --> 00:10:04.850 align:middle line:84% And here we would give you a CMS address, 00:10:04.850 --> 00:10:06.415 align:middle line:90% which is hq-cms.ine.com. 00:10:06.415 --> 00:10:09.110 align:middle line:90% 00:10:09.110 --> 00:10:14.200 align:middle line:84% And the SIP trunk profile is going 00:10:14.200 --> 00:10:17.110 align:middle line:84% to be the one that we created, which was for CMS. 00:10:17.110 --> 00:10:20.920 align:middle line:84% The SIP profile is not going to be the standard one. 00:10:20.920 --> 00:10:22.840 align:middle line:84% You should not be using the standard one. 00:10:22.840 --> 00:10:28.360 align:middle line:84% You would be using a specially built-in created profile which 00:10:28.360 --> 00:10:29.920 align:middle line:84% is available for CMS, which is going 00:10:29.920 --> 00:10:34.120 align:middle line:84% to be called as SIP Profile for TelePresence Conferencing. 00:10:34.120 --> 00:10:38.170 align:middle line:84% And the normalization script is also something 00:10:38.170 --> 00:10:40.240 align:middle line:90% that you would have to select. 00:10:40.240 --> 00:10:43.150 align:middle line:84% And that's going to be the Cisco TelePresence Conductor 00:10:43.150 --> 00:10:44.110 align:middle line:90% Interrupt. 00:10:44.110 --> 00:10:47.770 align:middle line:84% Now, if you don't select this, your SIP trunk 00:10:47.770 --> 00:10:50.020 align:middle line:84% is not going to show us full service. 00:10:50.020 --> 00:10:51.550 align:middle line:84% So these are a few things that you 00:10:51.550 --> 00:10:54.130 align:middle line:84% would need to do when you create your SIP trunk. 00:10:54.130 --> 00:10:54.850 align:middle line:90% Let's save this. 00:10:54.850 --> 00:11:00.080 align:middle line:90% 00:11:00.080 --> 00:11:03.160 align:middle line:84% And once you save it, just make sure you reset your SIP trunk. 00:11:03.160 --> 00:11:06.850 align:middle line:90% 00:11:06.850 --> 00:11:09.940 align:middle line:84% And let's go back to our SIP trunk. 00:11:09.940 --> 00:11:17.060 align:middle line:90% 00:11:17.060 --> 00:11:18.095 align:middle line:90% Let's do a Find. 00:11:18.095 --> 00:11:22.360 align:middle line:90% 00:11:22.360 --> 00:11:24.760 align:middle line:84% If you look at my SIP-TRUNK-TO-CMS, 00:11:24.760 --> 00:11:28.270 align:middle line:84% that's the first one here, it should show up as-- 00:11:28.270 --> 00:11:33.910 align:middle line:84% data should show up as full, as full in service. 00:11:33.910 --> 00:11:34.915 align:middle line:90% Let's give it some time. 00:11:34.915 --> 00:11:53.650 align:middle line:90% 00:11:53.650 --> 00:11:56.280 align:middle line:84% So while we wait for SIP trunk to come up, 00:11:56.280 --> 00:11:57.750 align:middle line:90% to be in full service-- 00:11:57.750 --> 00:12:01.350 align:middle line:84% the SIP trunk status should show up as full service. 00:12:01.350 --> 00:12:05.220 align:middle line:84% While we wait for that, what we can do is go back to our CMS 00:12:05.220 --> 00:12:07.950 align:middle line:84% and create a defined the IVR port. 00:12:07.950 --> 00:12:11.690 align:middle line:84% For that, we go to Configuration, General. 00:12:11.690 --> 00:12:16.010 align:middle line:84% And here at the bottom, you will see the IVR numeric ID. 00:12:16.010 --> 00:12:19.400 align:middle line:84% Here is where you would define the IVR number. 00:12:19.400 --> 00:12:23.990 align:middle line:84% I believe the IVR number was 8888 as per the question, 00:12:23.990 --> 00:12:25.443 align:middle line:90% and let's save this. 00:12:25.443 --> 00:12:25.985 align:middle line:90% Let's submit. 00:12:25.985 --> 00:12:36.290 align:middle line:90% 00:12:36.290 --> 00:12:37.590 align:middle line:90% OK, so that's done. 00:12:37.590 --> 00:12:40.350 align:middle line:84% If we go back to Configuration, General, 00:12:40.350 --> 00:12:43.250 align:middle line:84% you would see that I have my IVR number. 00:12:43.250 --> 00:12:45.650 align:middle line:84% Lastly, we would go back to our call manager 00:12:45.650 --> 00:12:49.850 align:middle line:90% and create a route pattern. 00:12:49.850 --> 00:12:52.160 align:middle line:84% Our route pattern needs to be created. 00:12:52.160 --> 00:12:53.730 align:middle line:90% I believe my phones-- 00:12:53.730 --> 00:12:58.700 align:middle line:84% let's go back to my phones first and check 00:12:58.700 --> 00:13:00.930 align:middle line:90% which CSS my phone has. 00:13:00.930 --> 00:13:03.770 align:middle line:84% If you don't have any physical phones, we have Jabber. 00:13:03.770 --> 00:13:07.310 align:middle line:90% So I have HQ ONE and Tony Stark. 00:13:07.310 --> 00:13:13.280 align:middle line:84% I believe if I go back to Stark and look at his device CSS, 00:13:13.280 --> 00:13:16.340 align:middle line:90% he belongs to CSS-Phones. 00:13:16.340 --> 00:13:25.510 align:middle line:84% And if I look at CSS-Phones, CSS-Phones 00:13:25.510 --> 00:13:29.240 align:middle line:84% has access to these partitions Outbound-to-PSTN. 00:13:29.240 --> 00:13:32.920 align:middle line:84% And so maybe I can create one partition. 00:13:32.920 --> 00:13:36.430 align:middle line:84% If you want, you can keep it in the default none partition just 00:13:36.430 --> 00:13:37.640 align:middle line:90% to keep it simple. 00:13:37.640 --> 00:13:41.060 align:middle line:84% The question really does not say that we have any restrictions. 00:13:41.060 --> 00:13:44.210 align:middle line:84% So I would suggest keep it as simple as possible. 00:13:44.210 --> 00:13:49.180 align:middle line:84% So maybe you can directly go and create a route pattern 00:13:49.180 --> 00:13:51.340 align:middle line:90% that your phone has access to. 00:13:51.340 --> 00:13:55.735 align:middle line:84% So go back here and say route pattern to 8888. 00:13:55.735 --> 00:13:57.610 align:middle line:84% And this would be in the none partition. 00:13:57.610 --> 00:14:02.080 align:middle line:84% This would use the gateway as SIP-TRUNK-TO-CMS, 00:14:02.080 --> 00:14:04.820 align:middle line:90% and that's it. 00:14:04.820 --> 00:14:06.740 align:middle line:90% That's all we need. 00:14:06.740 --> 00:14:07.600 align:middle line:90% Let's do a Save. 00:14:07.600 --> 00:14:17.510 align:middle line:90% 00:14:17.510 --> 00:14:21.420 align:middle line:84% Once we do a Save, my user should be able to dial this. 00:14:21.420 --> 00:14:25.400 align:middle line:84% So when Tony Stark who is on Jabber, 00:14:25.400 --> 00:14:29.000 align:middle line:84% if you look at Jabber here, he is already prelogged in. 00:14:29.000 --> 00:14:30.050 align:middle line:90% It's all preconfigured. 00:14:30.050 --> 00:14:31.580 align:middle line:90% He's prelogged in. 00:14:31.580 --> 00:14:36.380 align:middle line:84% If he dials 8888, he is going to look at his device 00:14:36.380 --> 00:14:37.910 align:middle line:90% CSS and CSS-Phones. 00:14:37.910 --> 00:14:41.430 align:middle line:84% But because my route pattern is in the none partition, 00:14:41.430 --> 00:14:44.870 align:middle line:84% my Jabber machine, my Tony Stark CSS 00:14:44.870 --> 00:14:46.620 align:middle line:90% has access to none partition. 00:14:46.620 --> 00:14:48.530 align:middle line:84% So he would be able to dial 8888, 00:14:48.530 --> 00:14:51.050 align:middle line:84% which goes to the SIP-TRUNK-TO-CMS. 00:14:51.050 --> 00:14:54.110 align:middle line:84% Let's go back to my SIP trunk and see 00:14:54.110 --> 00:14:55.580 align:middle line:90% if the SIP trunk has come up. 00:14:55.580 --> 00:14:59.100 align:middle line:90% 00:14:59.100 --> 00:15:01.150 align:middle line:90% It still shows that it's not up. 00:15:01.150 --> 00:15:04.965 align:middle line:84% Let's go back to my SIP trunk and scroll down. 00:15:04.965 --> 00:15:07.690 align:middle line:90% 00:15:07.690 --> 00:15:16.390 align:middle line:84% Let's uncheck this redirect, and uncheck the redirect outbound. 00:15:16.390 --> 00:15:17.470 align:middle line:90% Let's Save this. 00:15:17.470 --> 00:15:21.420 align:middle line:90% 00:15:21.420 --> 00:15:25.670 align:middle line:84% Let's scroll down, check if my name is correct. 00:15:25.670 --> 00:15:28.520 align:middle line:90% hq-cms.ine.com. 00:15:28.520 --> 00:15:34.100 align:middle line:84% The SIP trunk profile is proper, and SIP profile 00:15:34.100 --> 00:15:37.130 align:middle line:84% is using the SIP profile for TelePresence Conferencing. 00:15:37.130 --> 00:15:41.830 align:middle line:84% And I'm using the correct normalization script. 00:15:41.830 --> 00:15:49.453 align:middle line:90% 00:15:49.453 --> 00:15:51.120 align:middle line:84% There's a meeting server interrupt also. 00:15:51.120 --> 00:15:52.120 align:middle line:90% Let's go and check that. 00:15:52.120 --> 00:16:02.710 align:middle line:90% 00:16:02.710 --> 00:16:04.550 align:middle line:90% Let's reset. 00:16:04.550 --> 00:16:08.330 align:middle line:84% In fact, it shows us full service. 00:16:08.330 --> 00:16:11.650 align:middle line:84% So maybe it was the correct one that we used. 00:16:11.650 --> 00:16:13.510 align:middle line:84% We don't need the Cisco Meeting Server. 00:16:13.510 --> 00:16:14.110 align:middle line:90% Let's wait. 00:16:14.110 --> 00:16:18.790 align:middle line:84% Let's reset this and go back and check if it comes back 00:16:18.790 --> 00:16:19.570 align:middle line:90% as full service. 00:16:19.570 --> 00:16:33.100 align:middle line:90% 00:16:33.100 --> 00:16:34.870 align:middle line:84% Yeah, I think it was the right one. 00:16:34.870 --> 00:16:38.020 align:middle line:84% We just had to uncheck the redirect header for inbound 00:16:38.020 --> 00:16:38.890 align:middle line:90% and outbound. 00:16:38.890 --> 00:16:41.650 align:middle line:84% So I'm going to go back to my normalization script 00:16:41.650 --> 00:16:46.891 align:middle line:84% and change this back to cisco telepresence conductor 00:16:46.891 --> 00:16:47.860 align:middle line:90% interrupt. 00:16:47.860 --> 00:16:49.075 align:middle line:90% And let's save this. 00:16:49.075 --> 00:16:51.940 align:middle line:90% 00:16:51.940 --> 00:16:53.545 align:middle line:90% And let's reset this. 00:16:53.545 --> 00:17:03.090 align:middle line:90% 00:17:03.090 --> 00:17:04.069 align:middle line:90% Let's do a Find. 00:17:04.069 --> 00:17:18.940 align:middle line:90% 00:17:18.940 --> 00:17:22.240 align:middle line:84% You would not be able to make the outbound call to the IVR 00:17:22.240 --> 00:17:25.959 align:middle line:84% if your SIP trunk does not show full status or full status. 00:17:25.959 --> 00:17:46.090 align:middle line:90% 00:17:46.090 --> 00:17:50.520 align:middle line:84% Let's go back to my Jabber, and let's try making the call just 00:17:50.520 --> 00:17:52.640 align:middle line:84% to see if you're able to dial the IVR. 00:17:52.640 --> 00:17:55.880 align:middle line:90% 00:17:55.880 --> 00:18:06.470 align:middle line:90% So let's dial 8888. 00:18:06.470 --> 00:18:08.960 align:middle line:84% Obviously, you would not be able to hear anything. 00:18:08.960 --> 00:18:11.330 align:middle line:90% But it should redirect to CMS. 00:18:11.330 --> 00:18:13.460 align:middle line:84% This is the CMS page that you see, 00:18:13.460 --> 00:18:20.630 align:middle line:84% and I should be able to maybe dial somebody's IVR extension 00:18:20.630 --> 00:18:22.010 align:middle line:90% or in fact, somebody's space. 00:18:22.010 --> 00:18:25.280 align:middle line:84% Let's say if I wanted to go to hq-one space, 00:18:25.280 --> 00:18:30.260 align:middle line:84% I would just say 2001 and then hash. 00:18:30.260 --> 00:18:32.270 align:middle line:84% This would take me to the cospace 00:18:32.270 --> 00:18:35.090 align:middle line:90% of hq-one in the conference. 00:18:35.090 --> 00:18:38.000 align:middle line:84% So now if hq-one wants to join the conference, 00:18:38.000 --> 00:18:39.930 align:middle line:90% he should be able to join. 00:18:39.930 --> 00:18:41.600 align:middle line:90% So how do I know it's 2001? 00:18:41.600 --> 00:18:47.540 align:middle line:84% If I go back to my CMS and look at the cospaces, 00:18:47.540 --> 00:18:52.550 align:middle line:84% you would see that the call ID for hq-one is 2001. 00:18:52.550 --> 00:18:56.240 align:middle line:84% So all I did was I dialed the IVR 8888. 00:18:56.240 --> 00:18:58.970 align:middle line:84% And then if you actually had speaker, 00:18:58.970 --> 00:19:02.630 align:middle line:84% you would hear that please dial the call 00:19:02.630 --> 00:19:04.730 align:middle line:84% ID that you want to join the conference. 00:19:04.730 --> 00:19:06.890 align:middle line:84% So you would just say 2001, which 00:19:06.890 --> 00:19:10.520 align:middle line:84% is hq-one space and pound, and you 00:19:10.520 --> 00:19:12.440 align:middle line:90% would join the hq-one space. 00:19:12.440 --> 00:19:16.385 align:middle line:84% So right now, I am in the space of hq-one, 00:19:16.385 --> 00:19:18.200 align:middle line:84% which you can see I am the only one right 00:19:18.200 --> 00:19:19.940 align:middle line:90% now in the conference. 00:19:19.940 --> 00:19:23.990 align:middle line:84% Hq-one right now has not joined because we haven't really 00:19:23.990 --> 00:19:28.160 align:middle line:84% configured integration between CMS and expressways right now. 00:19:28.160 --> 00:19:31.050 align:middle line:84% And hq-one is on the outside at this point of time. 00:19:31.050 --> 00:19:34.910 align:middle line:84% So testing the actual conference between the two users, 00:19:34.910 --> 00:19:37.085 align:middle line:84% you would not be able to test in this task. 00:19:37.085 --> 00:19:38.960 align:middle line:84% The only thing that you would be able to test 00:19:38.960 --> 00:19:40.670 align:middle line:90% is can you dial the IVR? 00:19:40.670 --> 00:19:42.260 align:middle line:84% How do I know I'm dialing the IVR? 00:19:42.260 --> 00:19:45.260 align:middle line:84% If this screen shows up, this Cisco logo 00:19:45.260 --> 00:19:46.550 align:middle line:90% is basically for CMS. 00:19:46.550 --> 00:19:49.010 align:middle line:84% If this screen shows up, your IVR is working. 00:19:49.010 --> 00:19:54.650 align:middle line:84% And then if you go to the keypad and dial 2001 and pound, 00:19:54.650 --> 00:19:57.980 align:middle line:84% you should be able to see conference keyword here, which 00:19:57.980 --> 00:20:00.350 align:middle line:84% basically shows that you are now in the conference. 00:20:00.350 --> 00:20:02.600 align:middle line:84% But yes, you are the only one in the conference 00:20:02.600 --> 00:20:06.230 align:middle line:84% right now because hq-one has not joined the conference yet. 00:20:06.230 --> 00:20:08.870 align:middle line:84% With this, we've basically met all of the requirements 00:20:08.870 --> 00:20:10.490 align:middle line:90% of this question. 00:20:10.490 --> 00:20:13.610 align:middle line:84% And I'm going to go back, in the meanwhile, 00:20:13.610 --> 00:20:17.060 align:middle line:84% and check if my SIP trunk is showing as full. 00:20:17.060 --> 00:20:17.630 align:middle line:90% Let's check. 00:20:17.630 --> 00:20:19.320 align:middle line:90% It's showing us full service. 00:20:19.320 --> 00:20:20.960 align:middle line:84% So with this, we've completed all 00:20:20.960 --> 00:20:24.230 align:middle line:84% of our task requirements, which meets the requirement 00:20:24.230 --> 00:20:25.640 align:middle line:90% of the question. 00:20:25.640 --> 00:20:27.660 align:middle line:84% I hope this video was informative to you, 00:20:27.660 --> 00:20:30.220 align:middle line:90% and thank you for watching.