WEBVTT 00:00:00.000 --> 00:00:02.952 align:middle line:90% 00:00:02.952 --> 00:00:06.396 align:middle line:90% [AUDIO LOGO] 00:00:06.396 --> 00:00:09.850 align:middle line:90% 00:00:09.850 --> 00:00:11.835 align:middle line:90% Hello and welcome to INE. 00:00:11.835 --> 00:00:13.210 align:middle line:84% Today in this video, we will look 00:00:13.210 --> 00:00:17.810 align:middle line:84% at section 1, Phone Registration and IM&P basically, task 1.3. 00:00:17.810 --> 00:00:20.200 align:middle line:84% Now, here on this task 1.3, we need 00:00:20.200 --> 00:00:22.900 align:middle line:90% users to log in through Jabber. 00:00:22.900 --> 00:00:26.170 align:middle line:84% Now, the question states that users in HQ-CUCM 00:00:26.170 --> 00:00:28.870 align:middle line:84% need to log in to Jabber and ensure 00:00:28.870 --> 00:00:30.730 align:middle line:84% the following requirements are met, 00:00:30.730 --> 00:00:33.370 align:middle line:84% configure user HQ ONE with the following requirements, 00:00:33.370 --> 00:00:37.570 align:middle line:84% extension should be set to 2001, use trivial names 00:00:37.570 --> 00:00:39.340 align:middle line:90% such as HQ Phone 1. 00:00:39.340 --> 00:00:42.200 align:middle line:84% The phone should display a globalized calling number, 00:00:42.200 --> 00:00:46.990 align:middle line:84% which is +14082022001 on the top left-hand corner of the phone 00:00:46.990 --> 00:00:48.250 align:middle line:90% screen. 00:00:48.250 --> 00:00:51.220 align:middle line:84% Configure user HQ Two with the following requirements, again, 00:00:51.220 --> 00:00:56.080 align:middle line:84% for extension for phone 2 or user 2 should be 2002. 00:00:56.080 --> 00:00:58.240 align:middle line:84% The trivial name or some name should 00:00:58.240 --> 00:01:00.615 align:middle line:90% be defined as HQ Phone 2. 00:01:00.615 --> 00:01:02.490 align:middle line:84% The phone should display again, the call is-- 00:01:02.490 --> 00:01:06.700 align:middle line:84% a globalized calling number +14022022002 on the top 00:01:06.700 --> 00:01:08.650 align:middle line:84% left-hand corner of the phone screen. 00:01:08.650 --> 00:01:12.190 align:middle line:84% And then same thing has to be done for the third user, which 00:01:12.190 --> 00:01:13.790 align:middle line:90% is Tony Stark. 00:01:13.790 --> 00:01:17.390 align:middle line:84% Now, users must be able to log into Jabber without manual 00:01:17.390 --> 00:01:19.830 align:middle line:84% configuration in Javver Advanced settings, 00:01:19.830 --> 00:01:22.910 align:middle line:84% which basically means that we would not manually define 00:01:22.910 --> 00:01:24.830 align:middle line:90% the IM&Ps IP address. 00:01:24.830 --> 00:01:28.490 align:middle line:84% Instead, we would go and create an SRV record 00:01:28.490 --> 00:01:32.480 align:middle line:84% on the DNS machine so that the lookup can happen 00:01:32.480 --> 00:01:36.398 align:middle line:84% and it can get all the call manager information, 00:01:36.398 --> 00:01:37.940 align:middle line:84% the certificates of the call manager, 00:01:37.940 --> 00:01:40.410 align:middle line:90% and the IM&P information. 00:01:40.410 --> 00:01:43.340 align:middle line:84% So once complete, log into Jabber-1 PC using the account 00:01:43.340 --> 00:01:46.490 align:middle line:90% tony-stark@ine.com. 00:01:46.490 --> 00:01:47.390 align:middle line:90% So let's do this. 00:01:47.390 --> 00:01:50.720 align:middle line:84% Now, if you remember in the earlier task, for HQ side, 00:01:50.720 --> 00:01:53.930 align:middle line:84% we had downloaded all the users from LDAP. 00:01:53.930 --> 00:01:56.712 align:middle line:84% So we already have the end users through LDAP, 00:01:56.712 --> 00:01:58.670 align:middle line:84% and they're getting authenticated through LDAP. 00:01:58.670 --> 00:02:02.750 align:middle line:84% All we now need to do is create a device phone for them. 00:02:02.750 --> 00:02:05.850 align:middle line:84% Now, in the lab exam, there are no physical phones anymore. 00:02:05.850 --> 00:02:08.330 align:middle line:84% So everything is going to be through Jabber. 00:02:08.330 --> 00:02:10.250 align:middle line:84% So obviously, if your Jabber does not work 00:02:10.250 --> 00:02:11.942 align:middle line:84% or if you're not able to log in, you 00:02:11.942 --> 00:02:14.150 align:middle line:84% are not going to pass the lab exam because you're not 00:02:14.150 --> 00:02:16.100 align:middle line:90% able to do any testing. 00:02:16.100 --> 00:02:18.740 align:middle line:84% So you need your phones to register. 00:02:18.740 --> 00:02:20.990 align:middle line:84% In fact, not your phones but your Jabber to be able to 00:02:20.990 --> 00:02:22.570 align:middle line:90% log in. 00:02:22.570 --> 00:02:24.640 align:middle line:84% So let's quickly go and build this. 00:02:24.640 --> 00:02:29.890 align:middle line:84% So your own HQ site as for our earlier configuration, 00:02:29.890 --> 00:02:32.820 align:middle line:84% the only thing we have is the end user, which 00:02:32.820 --> 00:02:34.380 align:middle line:90% was imported through LDAP. 00:02:34.380 --> 00:02:39.370 align:middle line:84% And all of these users already have the IM&P enabled, 00:02:39.370 --> 00:02:42.210 align:middle line:84% which you if you remember in task 1.1 we had done that. 00:02:42.210 --> 00:02:46.570 align:middle line:84% It has IM&P enabled and has the service profile also defined. 00:02:46.570 --> 00:02:49.440 align:middle line:84% So the only thing what we need to do is go to Device 00:02:49.440 --> 00:02:51.660 align:middle line:90% and create three phones. 00:02:51.660 --> 00:02:54.470 align:middle line:90% So let's go to Add New. 00:02:54.470 --> 00:02:57.740 align:middle line:84% And I would select from here, go all the way down 00:02:57.740 --> 00:03:04.982 align:middle line:84% and select the Client Services Framework and then hit Next. 00:03:04.982 --> 00:03:06.440 align:middle line:84% Since there are no physical phones, 00:03:06.440 --> 00:03:08.523 align:middle line:84% we are only going to be logging in through Jabber, 00:03:08.523 --> 00:03:10.820 align:middle line:84% so we select Client Services Framework. 00:03:10.820 --> 00:03:13.430 align:middle line:84% Give the name-- give the device name as whatever you want. 00:03:13.430 --> 00:03:17.490 align:middle line:84% Let's say we name this as CSFONE for HQ ONE. 00:03:17.490 --> 00:03:22.220 align:middle line:90% This is going to be HQ phone 1. 00:03:22.220 --> 00:03:24.225 align:middle line:84% And device pool is going to be default. 00:03:24.225 --> 00:03:25.850 align:middle line:84% So I'm just keeping everything default, 00:03:25.850 --> 00:03:27.050 align:middle line:90% just keeping it simple. 00:03:27.050 --> 00:03:29.460 align:middle line:84% Try and keep it simple in the lab exam. 00:03:29.460 --> 00:03:33.710 align:middle line:84% So my device pool is going to be default. My phone template is 00:03:33.710 --> 00:03:36.350 align:middle line:84% going to be the Client Services Framework. 00:03:36.350 --> 00:03:39.260 align:middle line:84% Let's scroll down and select the user. 00:03:39.260 --> 00:03:42.170 align:middle line:90% The owner is going to be hq-one. 00:03:42.170 --> 00:03:47.040 align:middle line:84% And then scroll down and define your device security profile, 00:03:47.040 --> 00:03:49.460 align:middle line:84% which is going to be Cisco Unified Client Services 00:03:49.460 --> 00:03:52.760 align:middle line:84% Framework-Standard SIP Nonsecure Profile. 00:03:52.760 --> 00:03:55.730 align:middle line:84% And select the SIP profile as Standard Sip Profile. 00:03:55.730 --> 00:03:57.980 align:middle line:84% Again, these are all default settings which are there. 00:03:57.980 --> 00:03:59.300 align:middle line:90% I didn't really create them. 00:03:59.300 --> 00:04:02.870 align:middle line:84% They are there by default. So select them and say Save. 00:04:02.870 --> 00:04:09.050 align:middle line:84% So now basically I have created a device on my call manager. 00:04:09.050 --> 00:04:10.740 align:middle line:84% Next thing I define the extension. 00:04:10.740 --> 00:04:13.430 align:middle line:84% So let's click on the Add new DN. 00:04:13.430 --> 00:04:17.660 align:middle line:84% This DN is going to be 2001 for HQ Phone 1. 00:04:17.660 --> 00:04:19.459 align:middle line:84% The name, description-- let's give 00:04:19.459 --> 00:04:22.520 align:middle line:90% this description as HQ Phone 1. 00:04:22.520 --> 00:04:25.340 align:middle line:84% Now, again, try and be very specific in the lab exam. 00:04:25.340 --> 00:04:28.790 align:middle line:84% If they say that use trivial names such as HQ Phone 1, 00:04:28.790 --> 00:04:30.840 align:middle line:84% it basically means use that name. 00:04:30.840 --> 00:04:34.470 align:middle line:84% So I would suggest use it exactly as for the question. 00:04:34.470 --> 00:04:36.170 align:middle line:90% So HQ phone 1. 00:04:36.170 --> 00:04:39.425 align:middle line:84% Let's give the alerting name as HQ Phone 1. 00:04:39.425 --> 00:04:42.800 align:middle line:90% 00:04:42.800 --> 00:04:47.000 align:middle line:90% And let's copy this. 00:04:47.000 --> 00:04:48.170 align:middle line:90% Scroll down. 00:04:48.170 --> 00:04:51.530 align:middle line:84% I don't have any CSS or anything right now, just keep it simple. 00:04:51.530 --> 00:04:54.740 align:middle line:84% Scroll all the way down, and here we 00:04:54.740 --> 00:05:01.490 align:middle line:84% will define the display caller ID as HQ Phone 1. 00:05:01.490 --> 00:05:04.100 align:middle line:84% And then the external phone number mask is going to be 00:05:04.100 --> 00:05:09.260 align:middle line:90% +14082022001. 00:05:09.260 --> 00:05:12.830 align:middle line:84% And nothing has been mentioned about the busy trigger 00:05:12.830 --> 00:05:15.470 align:middle line:84% or anything, but again, in this question, 00:05:15.470 --> 00:05:16.970 align:middle line:84% it does not really mention anything. 00:05:16.970 --> 00:05:20.150 align:middle line:84% But in the lab exam, what you should do 00:05:20.150 --> 00:05:23.190 align:middle line:90% is do a hybrid approach. 00:05:23.190 --> 00:05:25.680 align:middle line:84% So there are three ways to actually configure things. 00:05:25.680 --> 00:05:29.630 align:middle line:84% One is doing it as for the task step by step, 00:05:29.630 --> 00:05:33.680 align:middle line:84% or doing everything together, or doing a hybrid. 00:05:33.680 --> 00:05:36.470 align:middle line:84% If you do everything question by question, 00:05:36.470 --> 00:05:39.080 align:middle line:84% you have less chances of error, but it 00:05:39.080 --> 00:05:41.990 align:middle line:84% takes longer to configure all the requirements 00:05:41.990 --> 00:05:45.920 align:middle line:84% of the task all the way from section 1 to section 5 00:05:45.920 --> 00:05:47.930 align:middle line:90% or section 6 or section 7. 00:05:47.930 --> 00:05:51.380 align:middle line:84% It takes longer because you have to come back to the end user 00:05:51.380 --> 00:05:55.040 align:middle line:84% or come back to the device phone and add the checkboxes let's 00:05:55.040 --> 00:05:57.110 align:middle line:84% say for mail or the busy trigger. 00:05:57.110 --> 00:06:01.080 align:middle line:84% You have to enable all of those things coming back to it. 00:06:01.080 --> 00:06:03.410 align:middle line:84% So doing it step by step as for the question, 00:06:03.410 --> 00:06:08.540 align:middle line:84% it's less prone to you having making-- basically making 00:06:08.540 --> 00:06:10.470 align:middle line:90% mistakes, but it takes longer. 00:06:10.470 --> 00:06:14.630 align:middle line:84% So that's the problem area of doing it question by question. 00:06:14.630 --> 00:06:18.290 align:middle line:84% If you do it as everything together, 00:06:18.290 --> 00:06:23.272 align:middle line:84% then it's faster but you have more chances of making errors 00:06:23.272 --> 00:06:24.980 align:middle line:84% because you're actually doing everything, 00:06:24.980 --> 00:06:27.860 align:middle line:84% you're enabling all the tick marks earlier in the start, 00:06:27.860 --> 00:06:30.140 align:middle line:84% everything even for voicemail and everything 00:06:30.140 --> 00:06:32.870 align:middle line:84% you're enabling now, so it's faster 00:06:32.870 --> 00:06:36.090 align:middle line:84% but you have more chances of making a mistake. 00:06:36.090 --> 00:06:38.900 align:middle line:84% So what I suggest is do a hybrid approach where 00:06:38.900 --> 00:06:40.288 align:middle line:90% you do a few things-- 00:06:40.288 --> 00:06:42.830 align:middle line:84% even though it's more than what is required in the question-- 00:06:42.830 --> 00:06:45.260 align:middle line:84% you do a few more things so that you don't really 00:06:45.260 --> 00:06:48.600 align:middle line:84% have to come back but not everything. 00:06:48.600 --> 00:06:51.270 align:middle line:84% So again, I would do it as for the question 00:06:51.270 --> 00:06:53.850 align:middle line:84% right now because we're not really configuring voice mail, 00:06:53.850 --> 00:06:57.970 align:middle line:84% so I'm just going to do specifically for the question. 00:06:57.970 --> 00:06:59.410 align:middle line:90% So that's all I need. 00:06:59.410 --> 00:07:02.680 align:middle line:90% Let's go ahead and save this. 00:07:02.680 --> 00:07:05.610 align:middle line:84% And then go back down all the way here 00:07:05.610 --> 00:07:09.330 align:middle line:84% to User Associated With Line, and here I 00:07:09.330 --> 00:07:14.110 align:middle line:84% would associate my user, which is hq-one to this line. 00:07:14.110 --> 00:07:16.800 align:middle line:84% The reason we are doing this is because we want present status. 00:07:16.800 --> 00:07:18.295 align:middle line:84% Now, if you look at the question, 00:07:18.295 --> 00:07:20.920 align:middle line:84% the question really does not say anything about present status. 00:07:20.920 --> 00:07:22.980 align:middle line:84% But again, in the lab exam, I highly 00:07:22.980 --> 00:07:25.800 align:middle line:84% recommend that you have present status enabled 00:07:25.800 --> 00:07:28.290 align:middle line:84% so you have the line defined with the user, 00:07:28.290 --> 00:07:31.170 align:middle line:84% and you have a SIP trunk created to the IM&P 00:07:31.170 --> 00:07:33.820 align:middle line:90% so that present status shows up. 00:07:33.820 --> 00:07:36.000 align:middle line:84% So let's say if the user goes on the call, 00:07:36.000 --> 00:07:40.060 align:middle line:84% it shows as busy versus he's available. 00:07:40.060 --> 00:07:41.110 align:middle line:90% So that's all we need. 00:07:41.110 --> 00:07:46.210 align:middle line:84% Let's save this, and that should be enough. 00:07:46.210 --> 00:07:50.130 align:middle line:84% Let's go back to the end user now to HQ Phone 1 00:07:50.130 --> 00:07:53.470 align:middle line:84% and attach that device which we created. 00:07:53.470 --> 00:07:54.900 align:middle line:90% So go back here. 00:07:54.900 --> 00:07:57.570 align:middle line:90% Say Device Association. 00:07:57.570 --> 00:08:01.470 align:middle line:84% Click on Find and attach this CSFONE 00:08:01.470 --> 00:08:04.380 align:middle line:84% that we created to this end user. 00:08:04.380 --> 00:08:07.560 align:middle line:90% And let's say go back and save. 00:08:07.560 --> 00:08:10.300 align:middle line:90% So HQ Phone 1 is done. 00:08:10.300 --> 00:08:13.150 align:middle line:90% Let's now go to one more device. 00:08:13.150 --> 00:08:15.240 align:middle line:90% Let's go back to Phones. 00:08:15.240 --> 00:08:16.380 align:middle line:90% Click on Find. 00:08:16.380 --> 00:08:18.330 align:middle line:90% Do a super copy. 00:08:18.330 --> 00:08:20.700 align:middle line:84% That saves a lot of time, so do a super copy. 00:08:20.700 --> 00:08:25.920 align:middle line:84% Give the name as CSFTWO and say Save. 00:08:25.920 --> 00:08:33.135 align:middle line:84% Change the owner to HQ Phone 2 and save this. 00:08:33.135 --> 00:08:35.960 align:middle line:90% 00:08:35.960 --> 00:08:43.330 align:middle line:84% Then go back to the DN, and change this to 2002. 00:08:43.330 --> 00:08:50.030 align:middle line:90% So this would be HQ Phone 2. 00:08:50.030 --> 00:08:57.270 align:middle line:90% HQ Phone 2. 00:08:57.270 --> 00:08:59.280 align:middle line:90% Then scroll back down. 00:08:59.280 --> 00:09:03.825 align:middle line:84% Your display name is going to be HQ Phone 2. 00:09:03.825 --> 00:09:06.750 align:middle line:90% 00:09:06.750 --> 00:09:13.980 align:middle line:84% Your external phone mask is going to be +14082022002 00:09:13.980 --> 00:09:15.720 align:middle line:90% and then associate. 00:09:15.720 --> 00:09:17.460 align:middle line:90% Let's save this first. 00:09:17.460 --> 00:09:27.780 align:middle line:84% Let's associate the line to hq-two and save this. 00:09:27.780 --> 00:09:34.580 align:middle line:84% Let's go back to end user to hq-two now and do a device 00:09:34.580 --> 00:09:44.220 align:middle line:84% association where we will attach CSFTWO to the end user hq-two. 00:09:44.220 --> 00:09:49.570 align:middle line:90% Let's go back and hit save. 00:09:49.570 --> 00:09:53.500 align:middle line:84% Next thing we need one more for Tony Stark, 00:09:53.500 --> 00:09:57.240 align:middle line:90% so let's go and create one. 00:09:57.240 --> 00:10:01.370 align:middle line:84% Or in fact, let's go back into a super copy. 00:10:01.370 --> 00:10:03.480 align:middle line:90% So super copy. 00:10:03.480 --> 00:10:06.065 align:middle line:90% Let's name this as CSFSTARK. 00:10:06.065 --> 00:10:08.750 align:middle line:90% 00:10:08.750 --> 00:10:11.480 align:middle line:90% Save. 00:10:11.480 --> 00:10:21.820 align:middle line:84% The name is going to be Tony Stark, 00:10:21.820 --> 00:10:26.740 align:middle line:84% and the owner is going to be Tony Stark. 00:10:26.740 --> 00:10:27.640 align:middle line:90% Let's save this. 00:10:27.640 --> 00:10:30.850 align:middle line:90% 00:10:30.850 --> 00:10:32.440 align:middle line:84% I believe that's the name required. 00:10:32.440 --> 00:10:34.030 align:middle line:90% The name should be Tony Stark. 00:10:34.030 --> 00:10:40.480 align:middle line:84% In fact, let's keep this exactly how it was so Tony Stark 00:10:40.480 --> 00:10:41.350 align:middle line:90% and save. 00:10:41.350 --> 00:10:45.310 align:middle line:90% 00:10:45.310 --> 00:10:46.770 align:middle line:90% Go back to your DN. 00:10:46.770 --> 00:10:55.260 align:middle line:84% This is going to be 2003, and that's going to be Tony Stark. 00:10:55.260 --> 00:10:56.210 align:middle line:90% Tony Stark. 00:10:56.210 --> 00:11:07.900 align:middle line:90% 00:11:07.900 --> 00:11:13.550 align:middle line:84% And my display name is going to be Tony stark. 00:11:13.550 --> 00:11:17.450 align:middle line:90% 00:11:17.450 --> 00:11:24.320 align:middle line:84% And my external phone mask is going to be 1408202003. 00:11:24.320 --> 00:11:28.500 align:middle line:84% Scroll down and associate the end user, 00:11:28.500 --> 00:11:34.990 align:middle line:84% which is going to be tony-stark, and let's save this. 00:11:34.990 --> 00:11:41.430 align:middle line:84% So if I go back now and let's say go back to Device, Phones, 00:11:41.430 --> 00:11:43.260 align:middle line:84% I have-- in fact, you know what, there's 00:11:43.260 --> 00:11:46.350 align:middle line:90% one mistake here for HQ CFSTWO. 00:11:46.350 --> 00:11:48.457 align:middle line:84% I did not change the device description. 00:11:48.457 --> 00:11:49.290 align:middle line:90% Let's change this 2. 00:11:49.290 --> 00:11:55.595 align:middle line:90% 00:11:55.595 --> 00:11:57.720 align:middle line:90% And this all looks good. 00:11:57.720 --> 00:12:03.570 align:middle line:84% So now I go back to my end user and go to tony-stark, 00:12:03.570 --> 00:12:10.370 align:middle line:84% and do a device association with the CSF, 00:12:10.370 --> 00:12:12.860 align:middle line:90% which is going to be CSFSTARK. 00:12:12.860 --> 00:12:15.710 align:middle line:90% 00:12:15.710 --> 00:12:19.770 align:middle line:90% Let's go back and save this. 00:12:19.770 --> 00:12:23.340 align:middle line:84% So now I have three devices created, 00:12:23.340 --> 00:12:27.410 align:middle line:84% which is CSFONE, which is for hq-one, CFSTWO, 00:12:27.410 --> 00:12:30.600 align:middle line:84% which is for hq-two, and CSFSTARK, 00:12:30.600 --> 00:12:31.730 align:middle line:90% which is for Tony Stark. 00:12:31.730 --> 00:12:34.490 align:middle line:84% And they all have the line has the user, 00:12:34.490 --> 00:12:38.990 align:middle line:84% and the end user has the device association done. 00:12:38.990 --> 00:12:42.500 align:middle line:84% Next thing what I'm going to do is go to my Trunk-- 00:12:42.500 --> 00:12:44.390 align:middle line:84% Device, Trunk and create a SIP trunk 00:12:44.390 --> 00:12:46.950 align:middle line:84% to my IM&P for my present status. 00:12:46.950 --> 00:12:49.680 align:middle line:90% So let's go and do a Find. 00:12:49.680 --> 00:12:51.630 align:middle line:90% And let's click on Add New. 00:12:51.630 --> 00:12:53.978 align:middle line:90% And click on SIP Trunk. 00:12:53.978 --> 00:12:56.020 align:middle line:84% Again, the question really does not mention that, 00:12:56.020 --> 00:12:57.810 align:middle line:84% but again, it's highly recommended 00:12:57.810 --> 00:13:00.090 align:middle line:84% that you do that in the lab exam. 00:13:00.090 --> 00:13:02.460 align:middle line:90% Let's say Next. 00:13:02.460 --> 00:13:15.590 align:middle line:84% Let's give this name as SIP-TRUNK-TO-MI-P. 00:13:15.590 --> 00:13:21.960 align:middle line:84% My device pool is going to be default. Let's scroll down. 00:13:21.960 --> 00:13:25.460 align:middle line:84% You can click on Run On All Active Nodes. 00:13:25.460 --> 00:13:27.020 align:middle line:90% Scroll down. 00:13:27.020 --> 00:13:31.430 align:middle line:84% Redirecting diversion header for inbound 00:13:31.430 --> 00:13:35.670 align:middle line:84% and redirecting diversion header for outbound. 00:13:35.670 --> 00:13:37.990 align:middle line:84% And define the destination address, 00:13:37.990 --> 00:13:41.430 align:middle line:84% which is the IM&P's address which is hq-imp.ine.com. 00:13:41.430 --> 00:13:48.810 align:middle line:84% And then my SIP trunk security profile 00:13:48.810 --> 00:13:51.240 align:middle line:84% is going to be the default one, which is the Nonsecure SIP 00:13:51.240 --> 00:13:52.262 align:middle line:90% Trunk Profile. 00:13:52.262 --> 00:13:54.720 align:middle line:84% The SIP profile is also going to be the standard one, which 00:13:54.720 --> 00:13:55.770 align:middle line:90% is the SIP Profile. 00:13:55.770 --> 00:14:06.667 align:middle line:84% Let's save this, and let's reset this. 00:14:06.667 --> 00:14:08.750 align:middle line:84% The next thing once we have the SIP trunk created, 00:14:08.750 --> 00:14:12.290 align:middle line:84% we need to publish the SIP trunk to the IM&P which 00:14:12.290 --> 00:14:15.860 align:middle line:84% is going to be done from System, go to Service Parameters. 00:14:15.860 --> 00:14:19.420 align:middle line:90% So that is here. 00:14:19.420 --> 00:14:22.130 align:middle line:90% Click on your UCM. 00:14:22.130 --> 00:14:25.810 align:middle line:90% Go to call manager. 00:14:25.810 --> 00:14:31.300 align:middle line:84% And here you can do a Control-F and search for presence. 00:14:31.300 --> 00:14:34.540 align:middle line:84% You would see IM and Presence Publish Trunk, 00:14:34.540 --> 00:14:39.520 align:middle line:84% and select your SIP trunk that we created, and say Save. 00:14:39.520 --> 00:14:40.540 align:middle line:90% Done. 00:14:40.540 --> 00:14:42.860 align:middle line:84% Now, would the users be able to log in? 00:14:42.860 --> 00:14:44.800 align:middle line:84% Let's say if I go back now to my Jabber, 00:14:44.800 --> 00:14:47.140 align:middle line:90% so I am on my Jabber-1 machine. 00:14:47.140 --> 00:14:51.400 align:middle line:84% If I look down here, I have the Jabber application. 00:14:51.400 --> 00:14:57.760 align:middle line:84% If I try and log in with the user, let's say, 00:14:57.760 --> 00:15:04.930 align:middle line:84% hq-one@ine.com or hq-two@ine.com or even tony-stark@ine.com. 00:15:04.930 --> 00:15:08.540 align:middle line:84% If I try and log in, I would not be able to log in. 00:15:08.540 --> 00:15:14.050 align:middle line:84% So if I actually try-- let's try one, 00:15:14.050 --> 00:15:18.700 align:middle line:90% hq-1@ine.com and hit Continue. 00:15:18.700 --> 00:15:22.000 align:middle line:84% And just do a Control-Shift-D so that it gives me 00:15:22.000 --> 00:15:25.270 align:middle line:84% the diagnostic for my Jabber, you 00:15:25.270 --> 00:15:27.700 align:middle line:84% would see that it's trying to go to collab-edge. 00:15:27.700 --> 00:15:31.120 align:middle line:84% It's not really trying to connect 00:15:31.120 --> 00:15:35.470 align:middle line:84% to the on-premise publisher because I haven't defined 00:15:35.470 --> 00:15:40.730 align:middle line:84% the call manager's IP address or even the IM&P's information. 00:15:40.730 --> 00:15:43.930 align:middle line:84% So it says that you cannot find the services automatically. 00:15:43.930 --> 00:15:46.610 align:middle line:84% Click on advanced setting, and set it up manually. 00:15:46.610 --> 00:15:48.820 align:middle line:84% So I would have to go to Advanced settings 00:15:48.820 --> 00:15:51.910 align:middle line:84% and click on IM&P and define the IM&P's address. 00:15:51.910 --> 00:15:55.550 align:middle line:84% But my question states that we should not be doing that. 00:15:55.550 --> 00:16:01.120 align:middle line:84% It should automatically find the services automatically 00:16:01.120 --> 00:16:03.680 align:middle line:84% without you going and defining it manually. 00:16:03.680 --> 00:16:07.910 align:middle line:84% So for this we would require an SRV record 00:16:07.910 --> 00:16:11.410 align:middle line:84% on your Active Directory or DNS machine so 00:16:11.410 --> 00:16:15.790 align:middle line:84% that the lookup can happen through Cisco UDS. 00:16:15.790 --> 00:16:21.260 align:middle line:84% So let's go back to my DNS machine which is here. 00:16:21.260 --> 00:16:23.650 align:middle line:84% Click on ine.com-- right click on that. 00:16:23.650 --> 00:16:27.190 align:middle line:90% Go to Other New Records. 00:16:27.190 --> 00:16:31.690 align:middle line:84% Scroll down to SRV, and click on Create Record. 00:16:31.690 --> 00:16:36.940 align:middle line:84% Here I would give service as _cisco-uds. 00:16:36.940 --> 00:16:40.270 align:middle line:84% The protocol is going to be _tcp. 00:16:40.270 --> 00:16:42.940 align:middle line:90% The port number would be 8443. 00:16:42.940 --> 00:16:44.830 align:middle line:90% And who's offering this service? 00:16:44.830 --> 00:16:50.240 align:middle line:84% Your publisher so hq-cucm.ine.com. 00:16:50.240 --> 00:16:53.440 align:middle line:90% Let's click on OK and say Done. 00:16:53.440 --> 00:16:56.500 align:middle line:84% So now I have an SRV record, which 00:16:56.500 --> 00:17:02.770 align:middle line:84% should allow me now to go and connect to the services. 00:17:02.770 --> 00:17:07.450 align:middle line:84% Let's click on Find services again and click this on Reload. 00:17:07.450 --> 00:17:09.312 align:middle line:90% Let's see what happens. 00:17:09.312 --> 00:17:09.895 align:middle line:90% Let's go back. 00:17:09.895 --> 00:17:21.387 align:middle line:90% 00:17:21.387 --> 00:17:23.470 align:middle line:84% So it found the certificate for your call manager. 00:17:23.470 --> 00:17:25.930 align:middle line:90% Let's click on Accept. 00:17:25.930 --> 00:17:28.060 align:middle line:90% Let's now define the password. 00:17:28.060 --> 00:17:31.930 align:middle line:90% The password was C1c0123! 00:17:31.930 --> 00:17:33.250 align:middle line:90% Where C was uppercase. 00:17:33.250 --> 00:17:34.910 align:middle line:90% Sign In. 00:17:34.910 --> 00:17:39.260 align:middle line:84% And if I click on Reload, you should see if you scroll down, 00:17:39.260 --> 00:17:43.210 align:middle line:84% you would see that found the SRV lookup, so the _cisco-uds, 00:17:43.210 --> 00:17:45.400 align:middle line:84% which points to your call manager. 00:17:45.400 --> 00:17:47.740 align:middle line:84% It should now also find-- it should get the certificate 00:17:47.740 --> 00:17:50.080 align:middle line:90% for the IM&P also. 00:17:50.080 --> 00:17:50.650 align:middle line:90% Let's wait. 00:17:50.650 --> 00:17:56.640 align:middle line:90% 00:17:56.640 --> 00:17:58.740 align:middle line:84% It should give me a pop up for IM&P. 00:17:58.740 --> 00:18:01.568 align:middle line:84% It says cannot communicate with the server. 00:18:01.568 --> 00:18:03.610 align:middle line:84% So I was not able to communicate with the server. 00:18:03.610 --> 00:18:06.162 align:middle line:90% Let's reset this and try again. 00:18:06.162 --> 00:18:07.890 align:middle line:90% So hq-one@ine.com. 00:18:07.890 --> 00:18:33.120 align:middle line:90% 00:18:33.120 --> 00:18:37.230 align:middle line:90% Password was C1c0123! 00:18:37.230 --> 00:18:38.265 align:middle line:90% and sign in. 00:18:38.265 --> 00:19:01.997 align:middle line:90% 00:19:01.997 --> 00:19:04.330 align:middle line:84% It still says that I cannot communicate with the server. 00:19:04.330 --> 00:19:06.590 align:middle line:84% Let's go back and check what we are missing 00:19:06.590 --> 00:19:08.880 align:middle line:90% or there's something going on. 00:19:08.880 --> 00:19:11.420 align:middle line:84% Let's go back first back to the SRV record 00:19:11.420 --> 00:19:17.040 align:middle line:84% and look at if we gave that correctly. 00:19:17.040 --> 00:19:22.910 align:middle line:84% So ine.com and let's look at this CRV lookup. 00:19:22.910 --> 00:19:23.930 align:middle line:90% Cisco. 00:19:23.930 --> 00:19:26.900 align:middle line:84% Let's double click on that or maybe go to Properties. 00:19:26.900 --> 00:19:34.100 align:middle line:84% So that looks OK, _cisco-uds, 8443, hq-ucm.ine.com. 00:19:34.100 --> 00:19:36.830 align:middle line:90% So that looks OK. 00:19:36.830 --> 00:19:40.680 align:middle line:84% And let's go back to my Jabber machine, and look at this. 00:19:40.680 --> 00:19:42.335 align:middle line:90% So what does it say? 00:19:42.335 --> 00:19:48.810 align:middle line:90% 00:19:48.810 --> 00:19:52.650 align:middle line:84% So it says the specified domain either does not exist 00:19:52.650 --> 00:19:55.920 align:middle line:90% or could not be contacted. 00:19:55.920 --> 00:19:58.610 align:middle line:90% Let's go back to the CLI. 00:19:58.610 --> 00:20:01.640 align:middle line:90% 00:20:01.640 --> 00:20:05.370 align:middle line:84% I believe the command prompt is-- 00:20:05.370 --> 00:20:10.020 align:middle line:84% let's scroll down to Windows System 00:20:10.020 --> 00:20:12.560 align:middle line:90% and go to command prompt. 00:20:12.560 --> 00:20:14.390 align:middle line:84% So on Jabber-1 machine, I'm actually 00:20:14.390 --> 00:20:16.670 align:middle line:84% going to my command prompt and just checking 00:20:16.670 --> 00:20:18.800 align:middle line:90% if my SRV lookup is OK. 00:20:18.800 --> 00:20:24.755 align:middle line:84% So let's do nslookup, and do set type=srv. 00:20:24.755 --> 00:20:27.710 align:middle line:90% 00:20:27.710 --> 00:20:31.030 align:middle line:84% And then let's do _cisco-uds._tcp.ine.com. 00:20:31.030 --> 00:20:36.530 align:middle line:90% 00:20:36.530 --> 00:20:41.120 align:middle line:84% So it looks like my SRV record is OK. 00:20:41.120 --> 00:20:46.580 align:middle line:84% It gives me the IP address of my call manager, which is also OK. 00:20:46.580 --> 00:20:51.590 align:middle line:84% So for some reason the Jabber says 00:20:51.590 --> 00:20:54.680 align:middle line:84% that the specified domain either does not exist or could not 00:20:54.680 --> 00:20:55.910 align:middle line:90% be contacted. 00:20:55.910 --> 00:20:58.070 align:middle line:84% Let's also do-- let's exit out from here-- 00:20:58.070 --> 00:21:01.250 align:middle line:84% let's also do a ping to hq-cucm.ine.com. 00:21:01.250 --> 00:21:04.160 align:middle line:90% 00:21:04.160 --> 00:21:05.810 align:middle line:90% Am I able to ping that? 00:21:05.810 --> 00:21:06.900 align:middle line:90% I am able to ping. 00:21:06.900 --> 00:21:09.720 align:middle line:84% So I know my DNS A-record is also correct. 00:21:09.720 --> 00:21:11.150 align:middle line:90% So that's OK. 00:21:11.150 --> 00:21:15.390 align:middle line:84% Let's now go-- let's scroll back and look at one more thing. 00:21:15.390 --> 00:21:18.110 align:middle line:84% Let's go back to your call manager. 00:21:18.110 --> 00:21:24.500 align:middle line:84% Go to System, Server, and let's do a Find. 00:21:24.500 --> 00:21:28.670 align:middle line:84% Because if you remember, if you look at my US Service what we 00:21:28.670 --> 00:21:33.050 align:middle line:84% had defined under the US Service for my call manager, 00:21:33.050 --> 00:21:37.940 align:middle line:84% we had defined under publisher hq-cucm.ine.com, 00:21:37.940 --> 00:21:41.640 align:middle line:84% which means my server settings should also have that. 00:21:41.640 --> 00:21:45.050 align:middle line:84% So for IM&P, it's hq-imp.ine.com, 00:21:45.050 --> 00:21:48.770 align:middle line:84% but for my call manager it's only hq-cucm. 00:21:48.770 --> 00:21:50.270 align:middle line:90% So that could be the problem. 00:21:50.270 --> 00:21:55.510 align:middle line:84% Let's go and change this hostname to be hq-cucm.ine.com. 00:21:55.510 --> 00:21:57.260 align:middle line:84% It should be a fully qualified domain name 00:21:57.260 --> 00:21:58.902 align:middle line:90% or it should be an IP address. 00:21:58.902 --> 00:22:00.110 align:middle line:90% Let's go ahead and save this. 00:22:00.110 --> 00:22:03.260 align:middle line:90% 00:22:03.260 --> 00:22:12.980 align:middle line:84% And go back to your Jabber machine which is here. 00:22:12.980 --> 00:22:14.300 align:middle line:90% Let's try and sign in again. 00:22:14.300 --> 00:22:16.970 align:middle line:90% 00:22:16.970 --> 00:22:19.580 align:middle line:90% Reload. 00:22:19.580 --> 00:22:22.010 align:middle line:84% In fact, now he got some more information here. 00:22:22.010 --> 00:22:36.200 align:middle line:90% 00:22:36.200 --> 00:22:39.280 align:middle line:84% And now he got the certificate for the IM&P. 00:22:39.280 --> 00:22:42.360 align:middle line:90% Let's accept that. 00:22:42.360 --> 00:22:45.720 align:middle line:90% And we should be good to go. 00:22:45.720 --> 00:22:46.620 align:middle line:90% It should log in. 00:22:46.620 --> 00:22:47.730 align:middle line:90% It did log in. 00:22:47.730 --> 00:22:51.780 align:middle line:84% If I look at the diagnostic, I see some error or system error. 00:22:51.780 --> 00:22:54.400 align:middle line:84% I think this is a Windows error, so just say OK. 00:22:54.400 --> 00:22:58.260 align:middle line:84% If I look at my Jabber, I am logged in now as hq-one, 00:22:58.260 --> 00:23:00.010 align:middle line:90% so we know it's working. 00:23:00.010 --> 00:23:07.820 align:middle line:84% And he should have his extension, which is 2001. 00:23:07.820 --> 00:23:10.700 align:middle line:90% Let's go back here. 00:23:10.700 --> 00:23:11.990 align:middle line:90% But now it's OK. 00:23:11.990 --> 00:23:14.630 align:middle line:90% So he has his extension 2001. 00:23:14.630 --> 00:23:17.280 align:middle line:84% And if I look back-- let's reload this, 00:23:17.280 --> 00:23:19.400 align:middle line:84% and see what information we have. 00:23:19.400 --> 00:23:25.400 align:middle line:84% So we had the search for hq-cucm.ine.com, 00:23:25.400 --> 00:23:30.470 align:middle line:90% the hq-imp.ine.com and ine.com. 00:23:30.470 --> 00:23:32.330 align:middle line:84% And if you look at the UDS servers, 00:23:32.330 --> 00:23:36.500 align:middle line:90% earlier it was saying hq-cucm. 00:23:36.500 --> 00:23:39.050 align:middle line:90% It was not showing .ine.com. 00:23:39.050 --> 00:23:43.430 align:middle line:84% That was your problem because your server, FQDN, was not 00:23:43.430 --> 00:23:47.660 align:middle line:84% matching the UC Service that we had because your A-record is 00:23:47.660 --> 00:23:49.850 align:middle line:84% a fully qualified domain name, so your server name 00:23:49.850 --> 00:23:51.450 align:middle line:90% should also be the same. 00:23:51.450 --> 00:23:51.950 align:middle line:90% OK. 00:23:51.950 --> 00:23:54.000 align:middle line:90% So now hq-one is able to log in. 00:23:54.000 --> 00:23:55.280 align:middle line:90% Let's log out. 00:23:55.280 --> 00:23:58.850 align:middle line:84% Let's sign out, and test HQ Phone 2. 00:23:58.850 --> 00:24:03.365 align:middle line:84% Let's reset this, and log in with hq-two@ine.com. 00:24:03.365 --> 00:24:10.530 align:middle line:90% 00:24:10.530 --> 00:24:12.530 align:middle line:84% So again, if you don't really know the username, 00:24:12.530 --> 00:24:14.360 align:middle line:84% then you can go back to your end user. 00:24:14.360 --> 00:24:16.640 align:middle line:84% If you remember in LDAP we had imported the user. 00:24:16.640 --> 00:24:23.600 align:middle line:84% The name is hq-one or hq-two, and it's @ine.com. 00:24:23.600 --> 00:24:29.096 align:middle line:84% Let's go back to my Jabber and log in as hq-two. 00:24:29.096 --> 00:24:30.830 align:middle line:90% Let's just see if that works. 00:24:30.830 --> 00:24:47.140 align:middle line:90% 00:24:47.140 --> 00:24:51.430 align:middle line:84% It takes a bit of time, but you should be able to log in. 00:24:51.430 --> 00:24:56.610 align:middle line:90% Let's put the password C1c0123!. 00:24:56.610 --> 00:24:59.610 align:middle line:90% Sign in. 00:24:59.610 --> 00:25:03.030 align:middle line:84% It should sign in as hq-two, and you should get the extension 00:25:03.030 --> 00:25:12.260 align:middle line:90% to 2002. 00:25:12.260 --> 00:25:13.940 align:middle line:84% Now, as for the question, it says 00:25:13.940 --> 00:25:16.070 align:middle line:84% that once we complete all the configuration, 00:25:16.070 --> 00:25:18.920 align:middle line:84% we must log into Jabber-1 one using Tony Stark. 00:25:18.920 --> 00:25:21.900 align:middle line:84% So we would log in as Tony Stark and keep it as that. 00:25:21.900 --> 00:25:24.470 align:middle line:84% So we would not log in as hq-one or hq-two. 00:25:24.470 --> 00:25:27.080 align:middle line:84% We would just test with hq-one, test with hq-two 00:25:27.080 --> 00:25:28.980 align:middle line:90% so that they are able to log in. 00:25:28.980 --> 00:25:31.010 align:middle line:84% But then finally we would keep the user 00:25:31.010 --> 00:25:34.580 align:middle line:90% logged in as Tony Stark. 00:25:34.580 --> 00:25:37.850 align:middle line:84% So again, I get this Windows error, but that's OK. 00:25:37.850 --> 00:25:39.740 align:middle line:90% Just say OK. 00:25:39.740 --> 00:25:41.720 align:middle line:90% And I'm logged in. 00:25:41.720 --> 00:25:44.790 align:middle line:90% The phone should get-- 00:25:44.790 --> 00:25:48.105 align:middle line:84% so now the phone is ready and HQ Phone 2 00:25:48.105 --> 00:25:49.530 align:middle line:90% should be able to make calls. 00:25:49.530 --> 00:25:54.100 align:middle line:84% Let's log out and finally log in with Tony Stark. 00:25:54.100 --> 00:25:58.620 align:middle line:84% Let's reset this and log in with tony-stark@ine.com. 00:25:58.620 --> 00:26:24.990 align:middle line:90% 00:26:24.990 --> 00:26:29.910 align:middle line:90% Let's put the password C1c0123. 00:26:29.910 --> 00:26:35.170 align:middle line:84% I think it was C1c0123!, so I gave the wrong password. 00:26:35.170 --> 00:26:38.390 align:middle line:90% 00:26:38.390 --> 00:26:39.095 align:middle line:90% It should fail. 00:26:39.095 --> 00:26:54.620 align:middle line:90% 00:26:54.620 --> 00:26:55.430 align:middle line:90% Oh, it logged in. 00:26:55.430 --> 00:26:58.120 align:middle line:90% Maybe I gave the right password. 00:26:58.120 --> 00:27:00.240 align:middle line:90% So I'm logged in. 00:27:00.240 --> 00:27:04.260 align:middle line:84% You should see the extension as 2003, 00:27:04.260 --> 00:27:06.545 align:middle line:84% and he should be able to make calls. 00:27:06.545 --> 00:27:07.920 align:middle line:84% I mean, right now we don't really 00:27:07.920 --> 00:27:09.940 align:middle line:84% have any other user logged in anywhere else, 00:27:09.940 --> 00:27:12.360 align:middle line:84% so we would not be able to make any calls to anybody else 00:27:12.360 --> 00:27:14.520 align:middle line:84% because we only have one machine which is Jabber-1. 00:27:14.520 --> 00:27:18.420 align:middle line:84% So I can either log in with hq-one or hq-two or Tony Stark. 00:27:18.420 --> 00:27:20.730 align:middle line:84% But once we reach section 2 where 00:27:20.730 --> 00:27:23.670 align:middle line:84% we would be doing intersite calling 00:27:23.670 --> 00:27:25.890 align:middle line:84% or even calling the PSTN, then you 00:27:25.890 --> 00:27:28.290 align:middle line:84% should be able to log in and make calls 00:27:28.290 --> 00:27:31.557 align:middle line:84% outbound to PSTN or even to site B. 00:27:31.557 --> 00:27:33.390 align:middle line:84% But at this point of time, all we need to do 00:27:33.390 --> 00:27:35.820 align:middle line:84% is test if Jabber is able to log in, 00:27:35.820 --> 00:27:40.320 align:middle line:84% and he gets the phone assigned to him, 00:27:40.320 --> 00:27:42.250 align:middle line:90% and we are able to log in. 00:27:42.250 --> 00:27:45.870 align:middle line:84% So I would keep this as like this and do not log off. 00:27:45.870 --> 00:27:49.920 align:middle line:84% Just keep it as logged in as Tony Stark. 00:27:49.920 --> 00:27:52.110 align:middle line:84% With this, we've basically met the requirements 00:27:52.110 --> 00:27:55.410 align:middle line:84% of the question where now my Jabber works, and we did not 00:27:55.410 --> 00:27:57.000 align:middle line:90% configure manual-- 00:27:57.000 --> 00:28:00.600 align:middle line:84% we did not do manual configuration of the IM&P. 00:28:00.600 --> 00:28:05.580 align:middle line:84% We defined an SRV record on the DNS machine which defines 00:28:05.580 --> 00:28:12.300 align:middle line:84% the _cisco-uds SRV lookup record so that when I log in through 00:28:12.300 --> 00:28:15.630 align:middle line:84% Jabber, it does the lookup, and gets the certs for the call 00:28:15.630 --> 00:28:20.160 align:middle line:84% manager and IM&P. Make sure that your UC Service, FQDN, 00:28:20.160 --> 00:28:23.850 align:middle line:84% matches with the server settings on your publisher. 00:28:23.850 --> 00:28:25.960 align:middle line:84% I hope this video was informative to you, 00:28:25.960 --> 00:28:28.460 align:middle line:90% and thank you for watching. 00:28:28.460 --> 00:28:29.000 align:middle line:90%