1 00:00:00,530 --> 00:00:01,640 Welcome back. 2 00:00:01,730 --> 00:00:07,190 This is part two of our discussion on the Cisco IP phone startup process. 3 00:00:07,550 --> 00:00:13,430 Previously, we looked at how an IP phone obtains power, how it learns its VLAN information using CDP 4 00:00:13,430 --> 00:00:14,720 or LDPE. 5 00:00:15,140 --> 00:00:20,750 Are we going to continue the discussion by looking at how an IP phone acquires an IP address, how it 6 00:00:20,750 --> 00:00:25,580 downloads its firmware and configuration, and how it registers with the CU CM. 7 00:00:25,910 --> 00:00:29,750 We'll also discuss the two signaling protocols of Skinny and SIP. 8 00:00:31,360 --> 00:00:38,560 Now once the phone is obtained, power booted and received its VLAN information by a CDP or LDPE. 9 00:00:38,590 --> 00:00:41,050 It then requires an IP address. 10 00:00:42,320 --> 00:00:45,980 You could manually configure an IP address on a Cisco IP phone. 11 00:00:46,250 --> 00:00:51,140 That's fine when you only have two or three phones, but if you have a deployment of several thousand 12 00:00:51,140 --> 00:00:55,310 phones, it's very unlikely that you want to configure the IP addresses manually. 13 00:00:55,700 --> 00:01:02,030 So more common method of allocating IP addresses in the real world is to use a DHCP server. 14 00:01:03,850 --> 00:01:07,210 So in this example, the phone is on the voice VLAN. 15 00:01:07,570 --> 00:01:16,120 The PC is on the data VLAN and you've configured a DHCP server with a scope for both the data VLAN and 16 00:01:16,120 --> 00:01:17,170 the voice VLAN. 17 00:01:17,530 --> 00:01:23,920 And you've set up a layer three switch to forward DHCP requests to the DHCP server. 18 00:01:24,310 --> 00:01:32,770 Otherwise you could configure a DHCP server on the voice VLAN or on the switch or other networking device. 19 00:01:33,720 --> 00:01:35,490 Now a lot of VoIP deployments. 20 00:01:35,490 --> 00:01:41,910 The DHCP server is configured on the layer three switch so that when the phone sends out a broadcast 21 00:01:41,910 --> 00:01:45,330 requesting an IP address, it receives a directly from the switch. 22 00:01:45,780 --> 00:01:52,290 However, you could run the DHCP server on a Cisco Unified Communications Manager that's not generally 23 00:01:52,290 --> 00:01:53,280 recommended. 24 00:01:53,490 --> 00:02:00,930 You would only run the DHCP service on the Q CM if you had less than 1000 phones in your topology. 25 00:02:02,200 --> 00:02:04,360 In a Cisco IP phone environment. 26 00:02:04,360 --> 00:02:09,490 It's very important that you configure the following options on the DHCP server. 27 00:02:10,090 --> 00:02:13,990 Firstly, you need to configure the network and mask for the voice VLAN. 28 00:02:14,410 --> 00:02:19,450 So what subnet of the IP phone is on and what mask are they going to use? 29 00:02:20,080 --> 00:02:26,740 You're going to specify option three, commonly known as default router or default gateway, and then 30 00:02:26,740 --> 00:02:32,980 you need to specify option 150, which specifies the IP address of the TFTP server. 31 00:02:33,190 --> 00:02:38,370 The phones need to get their configuration and updated firmware from a FTP server. 32 00:02:38,380 --> 00:02:40,570 So option 150 is critical. 33 00:02:41,210 --> 00:02:48,080 So once the DHCP request has been received, the DHCP server will send a DHCP offer back to the phone 34 00:02:48,440 --> 00:02:51,530 and that offer will contain these parameters. 35 00:02:52,710 --> 00:02:59,490 Now, once again, the unified communications manager can be configured to act as a DHCP server for 36 00:02:59,490 --> 00:03:01,290 up to 1000 phones. 37 00:03:01,740 --> 00:03:07,140 This is not recommended because only one DHCP server can be configured per cluster. 38 00:03:07,590 --> 00:03:11,070 In other words, it's a stand alone DHCP server with no backup. 39 00:03:11,670 --> 00:03:13,980 The service would normally be run on the publisher. 40 00:03:14,430 --> 00:03:20,430 Multiple subnets can be configured on the DHCP server, but it's generally not recommended to do this 41 00:03:20,550 --> 00:03:24,900 because of the issue of no redundancy and lack of scalability. 42 00:03:24,960 --> 00:03:31,230 So it's better to use an external DHCP server running on a router or a switch or on a Windows server 43 00:03:31,260 --> 00:03:32,880 or Linux server. 44 00:03:33,330 --> 00:03:38,370 In other words, use an external DHCP server rather than the CU cm. 45 00:03:39,900 --> 00:03:46,830 I'd like to show you, however, how to set up DHCP on the Cisco Unified Communications Manager. 46 00:03:47,280 --> 00:03:53,160 What you need to do is open up a browser and point it to https. 47 00:03:53,490 --> 00:03:54,490 Colon forge slash. 48 00:03:54,510 --> 00:03:58,890 Forward slash the IP address of your unified communications manager. 49 00:03:58,890 --> 00:04:01,350 Ford slash CM service. 50 00:04:01,740 --> 00:04:06,000 Now because the Q CM is using a self sign certificate. 51 00:04:06,730 --> 00:04:13,660 Your browser won't recognise the certificate, so you've got to click continue to this website to accept 52 00:04:13,660 --> 00:04:14,590 the certificate. 53 00:04:15,570 --> 00:04:22,019 The only issue you need to be aware of is that the self signed certificate is not recognized by your 54 00:04:22,019 --> 00:04:25,350 operating system and Internet Explorer or Firefox. 55 00:04:25,620 --> 00:04:30,960 You've just got to make sure that the server you're connecting to is the correct server. 56 00:04:31,080 --> 00:04:36,330 So the server that you think you're connecting to is the correct CAC server. 57 00:04:36,660 --> 00:04:41,940 Notice on the top right hand side, there are various menu options and we'll cover a lot of this during 58 00:04:41,940 --> 00:04:42,840 this course. 59 00:04:43,170 --> 00:04:48,870 We are currently on the Serviceability Menu, which allows us, for instance, to start and stop services. 60 00:04:49,800 --> 00:04:52,320 You need to log in with your username and password. 61 00:05:00,880 --> 00:05:03,220 Well, just increase the size of the browser window here. 62 00:05:04,920 --> 00:05:08,100 You need to go to tools service activation. 63 00:05:08,370 --> 00:05:11,190 We're going to activate the DHCP service. 64 00:05:13,690 --> 00:05:15,940 And yeah, you can see a list of services. 65 00:05:16,360 --> 00:05:21,040 The service that we need to activate is the Cisco DHCP Monitor Service. 66 00:05:21,700 --> 00:05:25,200 I'll discuss the various services in more detail later in this course. 67 00:05:25,210 --> 00:05:28,720 But notice for instance, there's the Cisco Core Manager Service. 68 00:05:29,450 --> 00:05:32,900 The Cisco TFTP service and so forth and so on. 69 00:05:34,720 --> 00:05:36,100 But you need to click Save. 70 00:05:38,150 --> 00:05:43,400 The SIU team will warn you that activating and deactivating services can take a while. 71 00:05:43,580 --> 00:05:44,300 We'll just click. 72 00:05:44,300 --> 00:05:44,990 Okay. 73 00:05:45,470 --> 00:05:48,140 You just need to wait for the page to refresh. 74 00:05:49,130 --> 00:05:51,980 And that will be a confirmation that the service is activated. 75 00:05:56,410 --> 00:05:56,700 Okay. 76 00:05:56,710 --> 00:05:58,780 The update operation was successful. 77 00:05:58,930 --> 00:06:02,590 To check if the service is running, we can go to tools control center. 78 00:06:02,590 --> 00:06:04,000 Feature Services. 79 00:06:08,160 --> 00:06:09,930 And in the list of services. 80 00:06:13,390 --> 00:06:17,860 We can see that the Cisco DXB Monitor service has started. 81 00:06:19,280 --> 00:06:20,960 And it has been activated. 82 00:06:21,470 --> 00:06:29,780 So going to the top of the page, I can select the Cisco Unified Cwm Administration Option and click 83 00:06:29,780 --> 00:06:30,380 go. 84 00:06:30,620 --> 00:06:34,920 This will take me to the administration pages of Q CM. 85 00:06:37,430 --> 00:06:39,230 I just want to point out the URL. 86 00:06:39,320 --> 00:06:41,120 Notice it's https. 87 00:06:41,510 --> 00:06:45,420 Colon Ford slash forward slash 10 to 1 one. 88 00:06:45,440 --> 00:06:50,300 In other words, the IP address of you see UCM Ford slash CM admin. 89 00:06:50,600 --> 00:06:52,970 This is a famous URL to remember. 90 00:06:53,580 --> 00:07:01,670 See, UCM is the administration pages of the Cisco Unified Communications Manager or call manager or 91 00:07:01,670 --> 00:07:03,230 whatever you prefer to call it. 92 00:07:09,500 --> 00:07:11,000 Going to the system menu. 93 00:07:11,240 --> 00:07:16,010 I can choose the option dhcp dhcp server. 94 00:07:18,530 --> 00:07:20,960 There is no default dhcp server. 95 00:07:20,990 --> 00:07:23,270 But just to show you that I can click find. 96 00:07:25,340 --> 00:07:28,130 And you'll notice here it says zero records found. 97 00:07:28,280 --> 00:07:29,780 So let's click add new. 98 00:07:34,510 --> 00:07:38,500 I choose the IP address of my Q CM. 99 00:07:38,950 --> 00:07:42,010 So that's the server that I'm going to configure DHCP on. 100 00:07:42,520 --> 00:07:46,240 I can then specify a primary DNS server. 101 00:07:46,510 --> 00:07:49,210 So whatever the IP addresses of my DNS server. 102 00:07:53,760 --> 00:07:56,730 So primary and secondary DNS servers can be configured. 103 00:07:57,420 --> 00:08:00,150 I can specify the primary TFTP server. 104 00:08:00,180 --> 00:08:01,560 Now this is very important. 105 00:08:01,560 --> 00:08:07,140 Remember, option 150 is required for the phones to get their configuration and firmware. 106 00:08:09,070 --> 00:08:14,380 So this will be the IP address of my SIU CM server or comms manager server. 107 00:08:15,200 --> 00:08:21,350 There are various other options that I can specify here, like the IP address, leash time and so forth. 108 00:08:21,710 --> 00:08:25,580 We're just going to leave all of those at default values and click Save. 109 00:08:28,150 --> 00:08:33,880 So I've specified information like my DNS server and my TFTP server. 110 00:08:33,909 --> 00:08:41,770 Now going to system dhcp dhcp subnet, I can create various subnets. 111 00:08:44,670 --> 00:08:45,870 I'm going to click ADD. 112 00:08:47,760 --> 00:08:55,320 What you're doing here is essentially creating scopes or subnets for devices on different VLANs or subnets 113 00:08:55,320 --> 00:08:56,880 within your organization. 114 00:08:57,710 --> 00:09:00,380 Once again I can select my DHCP server. 115 00:09:01,780 --> 00:09:04,180 I can now specify the subnet. 116 00:09:04,750 --> 00:09:07,540 So, for instance, 10.2 2.0. 117 00:09:08,420 --> 00:09:11,780 Specify the starting IP address to allocate to my phones. 118 00:09:11,780 --> 00:09:15,440 10.2 2.1 and IP address. 119 00:09:17,080 --> 00:09:22,870 So these are just values that specify the IP addresses to give to the phones. 120 00:09:23,700 --> 00:09:26,000 I can specify my router's IP address. 121 00:09:26,010 --> 00:09:30,030 10.2 2.101. 122 00:09:30,880 --> 00:09:35,830 I can specify my subnet mask to 55 to 50 5 to 55.0. 123 00:09:36,430 --> 00:09:38,260 I could specify my domain name. 124 00:09:40,280 --> 00:09:43,640 Once again I could specify my TFTP server. 125 00:09:49,320 --> 00:09:57,030 Notice it's the same IP address as the IP address of my DHCP server because both the FTP server and 126 00:09:57,030 --> 00:10:00,000 the DHCP server are running on my c UCM server. 127 00:10:00,900 --> 00:10:07,230 Once again, I could specify various other options, including the least time for this scope or the 128 00:10:07,240 --> 00:10:08,550 specific subnet. 129 00:10:08,760 --> 00:10:10,230 I could then click Save. 130 00:10:14,310 --> 00:10:18,840 That's how you configure DHCP on q cm. 131 00:10:19,380 --> 00:10:25,590 In a separate section of this course, I'm going to show you how to set up SIU CME with DHCP. 132 00:10:25,590 --> 00:10:28,200 In other words, configuring DHCP on a router. 133 00:10:29,330 --> 00:10:34,790 Once the phones have received an IP address, the phones will attempt to download their firmware and 134 00:10:34,790 --> 00:10:37,280 configuration from a FTP server. 135 00:10:38,060 --> 00:10:45,120 Phones get updated firmware and their phone configuration from the TFTP server running on the Q CM. 136 00:10:45,470 --> 00:10:53,510 The Cisco TFTP service builds configuration files and serves embedded component executable ring files 137 00:10:53,510 --> 00:10:56,360 and device configuration files to the phone's. 138 00:10:57,930 --> 00:11:03,510 So when the phone connects to the TFTP server, it's going to attempt to download a device specific 139 00:11:03,510 --> 00:11:05,010 configuration file. 140 00:11:05,520 --> 00:11:07,500 In other words, a phone with a mac address. 141 00:11:07,500 --> 00:11:08,940 Quadruple A, quadruple B. 142 00:11:08,970 --> 00:11:16,100 Quadruple C will attempt to download a file starting with CEP, which once again just stands for Celsius 143 00:11:16,110 --> 00:11:21,160 Ethernet phone with its MAC address config XML. 144 00:11:21,660 --> 00:11:30,000 That configuration file is built automatically on the Q CM when you add that phone to the Q configuration. 145 00:11:30,950 --> 00:11:37,400 If the phone is not being created on the communications manager or C cm, the phone will attempt to 146 00:11:37,400 --> 00:11:42,110 download a file xml default CNF XML. 147 00:11:42,320 --> 00:11:47,660 This is a configuration file that contains basic settings like the firmware. 148 00:11:47,690 --> 00:11:53,060 The phone should be using and the communications manager that the phone should be communicating with. 149 00:11:53,510 --> 00:12:01,870 So it points to the Q CM server and provides details like the IP address of the Q CM and the port number 150 00:12:01,880 --> 00:12:05,480 the phone should be using when communicating to the Q CM. 151 00:12:05,810 --> 00:12:12,230 It can also contain other information like location information and URLs for phone buttons. 152 00:12:13,350 --> 00:12:18,270 To configure TFTP on the SIU cm you need to do the following. 153 00:12:19,730 --> 00:12:21,380 On the navigation pages. 154 00:12:21,410 --> 00:12:23,390 Go to the serviceability menu. 155 00:12:24,200 --> 00:12:26,720 So select serviceability and then click go. 156 00:12:29,180 --> 00:12:36,860 You could also go directly to https IP address of the Q cm forward slash CM service. 157 00:12:38,470 --> 00:12:42,580 Under the Tools menu, we're going to select service activation once again. 158 00:12:44,010 --> 00:12:45,060 Under the services. 159 00:12:45,060 --> 00:12:47,520 You'll notice Cisco TFTP. 160 00:12:48,060 --> 00:12:50,640 So we'll select that and then click Save. 161 00:12:50,670 --> 00:12:54,750 We once again warned about activating and deactivating services and we'll just click. 162 00:12:54,750 --> 00:12:55,380 Okay. 163 00:12:57,470 --> 00:12:59,870 And the update operation has been successful. 164 00:13:01,550 --> 00:13:05,300 Notice the Cisco TFTP service is activated. 165 00:13:06,200 --> 00:13:10,970 That's all there is to configuring TFTP on the QC server. 166 00:13:12,500 --> 00:13:19,010 Once the phone has downloaded its configuration and updated its firmware, it will attempt to communicate 167 00:13:19,010 --> 00:13:28,190 with the Q CM to important port numbers that you need to remember or TCP port 2000 use by skinny client 168 00:13:28,190 --> 00:13:33,620 control protocol or skinny and TCP port 5060 used by SIP. 169 00:13:34,770 --> 00:13:39,990 The two signaling protocols used on handsets in Cisco environments are skinny or SEP. 170 00:13:40,720 --> 00:13:45,340 So the phones will now try to connect to the system and register. 171 00:13:46,520 --> 00:13:49,580 These are default numbers and can be changed. 172 00:13:51,330 --> 00:13:54,840 To change them on the Q CM You would do the following. 173 00:13:55,990 --> 00:14:00,670 Under the navigation menu, you would go to Cisco Unified CRM Administration. 174 00:14:00,700 --> 00:14:01,060 Click. 175 00:14:01,060 --> 00:14:01,630 Go. 176 00:14:03,770 --> 00:14:09,290 Under the system menu, you can go to the option Cisco Unified Cwm. 177 00:14:12,070 --> 00:14:13,690 And then notice this option. 178 00:14:13,690 --> 00:14:14,590 Find. 179 00:14:17,780 --> 00:14:20,660 You can see in this example, we have one Q. 180 00:14:20,660 --> 00:14:22,460 CM So I'm going to click on that option. 181 00:14:24,720 --> 00:14:30,780 And scrolling down to the bottom, you'll notice you have options here for the TCP port settings for 182 00:14:30,780 --> 00:14:31,650 the server. 183 00:14:32,010 --> 00:14:37,410 The first one is Ethernet phone port, in other words, skinny, which is port 2000. 184 00:14:37,530 --> 00:14:41,430 Then we have TCP, listen, port and TCP lives. 185 00:14:41,910 --> 00:14:49,830 MGP is typically used on gateways rather than phones, but you could change the port numbers used over 186 00:14:49,830 --> 00:14:50,370 here. 187 00:14:50,830 --> 00:14:53,700 Here's the port used by SIP 5060. 188 00:14:54,090 --> 00:14:58,770 And if you want to use secure sip, the port number by default is 5061. 189 00:14:59,070 --> 00:15:03,810 You can change the port numbers just by changing the options in this list. 190 00:15:04,910 --> 00:15:12,830 Now Skinny Cold Control Protocol, or CCP, commonly known as Skinny, is a Cisco Proprietary Terminal 191 00:15:12,830 --> 00:15:14,120 Control Protocol. 192 00:15:14,690 --> 00:15:20,810 This is the first of two protocols used for signaling and control of Cisco IP phones. 193 00:15:21,050 --> 00:15:24,110 The second one is session initiation, protocol or SIP. 194 00:15:24,440 --> 00:15:30,920 The recommended protocol for implementation of Cisco IP phones has for many years been skinny. 195 00:15:31,400 --> 00:15:35,650 That is changing these days as more features are added to SIP. 196 00:15:35,660 --> 00:15:38,990 But for now, understand that Skinny is a proprietary protocol. 197 00:15:38,990 --> 00:15:40,920 It's a stimulus protocol. 198 00:15:40,940 --> 00:15:45,050 For every event, the device sends a message to the system. 199 00:15:45,200 --> 00:15:50,540 The phones themselves are clients to the unified communications manager. 200 00:15:50,570 --> 00:15:58,280 They cannot even provide dial tone without the SIU cm telling them to provide that dial tone. 201 00:15:58,610 --> 00:16:04,910 It's proprietary, which has the advantage of quick additions and changes, but disadvantage of not 202 00:16:04,910 --> 00:16:06,920 being interoperable with other vendors. 203 00:16:07,370 --> 00:16:12,770 Once again, it's a client server architecture where the SIU, CM is in control of the IP phones. 204 00:16:13,250 --> 00:16:19,850 It allows for simple configuration where the phones themselves have no configuration but get their entire 205 00:16:19,850 --> 00:16:21,860 configuration from the SIU cm. 206 00:16:22,520 --> 00:16:26,180 The SIU CM maintains the dull plan and root patterns. 207 00:16:26,420 --> 00:16:29,870 In other words, it maintains all the information for the phones. 208 00:16:29,900 --> 00:16:35,240 The phones themselves can do nothing without the SIU cm telling them what to do. 209 00:16:36,230 --> 00:16:39,020 So, for example, if we had a situation like this. 210 00:16:39,780 --> 00:16:48,240 With IP phone 1000, an IP phone 1001 connected to a switch physically, but registered with the Cisco 211 00:16:48,240 --> 00:16:49,680 communications manager. 212 00:16:50,490 --> 00:16:54,670 These phones are totally under the control of the Q CM. 213 00:16:55,600 --> 00:17:02,530 If 1000 win or -- the phone would send a skinny message to the SIU cm saying I'm more --, what 214 00:17:02,530 --> 00:17:03,310 must I do? 215 00:17:03,970 --> 00:17:08,680 And the C.U. scheme would send a message to the phone saying Play dial tone. 216 00:17:09,040 --> 00:17:14,839 It's important to notice that Dalton does not come from the SIU like it would in a traditional environment. 217 00:17:14,859 --> 00:17:18,190 The dull tone is played locally from the phone. 218 00:17:18,990 --> 00:17:25,980 If the phone dialed digit let's say digit one that would be sent to the Q Cwm becomes manager, would 219 00:17:25,980 --> 00:17:31,500 process that message and send a message back saying stop dial tone. 220 00:17:31,620 --> 00:17:35,550 Now, there are a lot of other messages taking place in the background, but I just want to show you 221 00:17:35,550 --> 00:17:37,620 a high level overview of the process. 222 00:17:38,190 --> 00:17:40,650 For subsequent digits, the same thing would happen. 223 00:17:41,220 --> 00:17:46,740 The phone would send a message to the comms manager and the comms manager would send messages back. 224 00:17:47,100 --> 00:17:54,420 For example, when you dial digit, let's say digit one that digit displays on your phone because a 225 00:17:54,420 --> 00:17:59,910 message has been sent to the comms manager and a message is being sent back again saying display this 226 00:17:59,910 --> 00:18:01,410 digit on the phone. 227 00:18:02,420 --> 00:18:11,300 Once 1000 has dialled digits 1001, the comms manager can match those digits to a phone that's currently 228 00:18:11,300 --> 00:18:12,170 registered. 229 00:18:12,500 --> 00:18:19,160 In other words, this handset becomes manager, has a record of all phones that are currently available 230 00:18:19,160 --> 00:18:20,360 and registered. 231 00:18:20,660 --> 00:18:26,480 So the comms manager will send a skinny message to this phone telling it to ring. 232 00:18:26,870 --> 00:18:30,740 It'll also tell the phone to make its lamp flash. 233 00:18:31,160 --> 00:18:38,180 Other messages that are sent to the phone are to change the display so that 1001 can see that the call 234 00:18:38,180 --> 00:18:39,710 is coming from 1000. 235 00:18:40,190 --> 00:18:46,640 When the user answers the call, a skinny message is sent back to the comms manager, telling the comms 236 00:18:46,640 --> 00:18:48,930 manager that the phone is now or hook. 237 00:18:49,340 --> 00:18:55,250 The comms manager will send a message back to the phone, telling it to stop ringing, telling it to 238 00:18:55,250 --> 00:19:00,200 stop flashing its lamp, telling it to change its display, and so forth and so on. 239 00:19:00,710 --> 00:19:06,710 The moral of the story is that these two phones can do nothing without the comms manager telling them 240 00:19:06,710 --> 00:19:07,580 what to do. 241 00:19:08,030 --> 00:19:16,820 They are clients to the server as EUCOM will then send messages to both phones, telling the phones 242 00:19:16,820 --> 00:19:19,760 to set up an OTP stream to each other. 243 00:19:20,980 --> 00:19:26,530 It's important to remember that the OTP streams are direct between the two phones. 244 00:19:26,950 --> 00:19:35,860 So there's a separate ATP stream from 1000 to 1001 and another separate unidirectional ATP stream from 245 00:19:35,860 --> 00:19:37,990 1001 to 1000. 246 00:19:38,750 --> 00:19:43,200 The OTP streams do not flow via the SIU cm. 247 00:19:43,220 --> 00:19:45,860 They are direct between the two handsets. 248 00:19:46,130 --> 00:19:51,410 Obviously physically they are flowing through the switch, but logically they are going directly to 249 00:19:51,410 --> 00:19:52,190 one another. 250 00:19:53,130 --> 00:20:00,090 So the comms manager communicates with both phones, telling them about each other because Phone 1000 251 00:20:00,090 --> 00:20:07,140 needs to know the IP address of 1001 so that it can stream the IP to the right IP address. 252 00:20:07,620 --> 00:20:15,210 1000 also needs to know the port number that 1001 is using so it can stream to the right port number. 253 00:20:15,690 --> 00:20:21,900 And by the same token, 1001 needs to know the IP address and port number that 1000 is using. 254 00:20:22,260 --> 00:20:28,380 So skinny messages are used by the system to communicate that information to the handsets. 255 00:20:28,710 --> 00:20:34,290 But once the call is established, the SIU CM is no longer involved in the conversation. 256 00:20:34,560 --> 00:20:41,580 The two devices are communicating directly with each other without any interaction from the SIU cm. 257 00:20:43,110 --> 00:20:47,610 Now session initiation protocol or CIP is an open standard. 258 00:20:47,820 --> 00:20:52,150 Unlike Skinny, which is proprietary, it's a peer to peer protocol. 259 00:20:52,170 --> 00:20:54,900 Unlike Skinny, which is client server. 260 00:20:55,290 --> 00:21:01,470 But be aware, please, that SIP supports basic functionality in the open standards. 261 00:21:01,830 --> 00:21:08,430 But to get featured parity with Skinny SIP has been extended by Sysco to provide the functionality. 262 00:21:08,790 --> 00:21:13,830 So even though SIP is an open standard, it is extended by vendors to provide features. 263 00:21:13,980 --> 00:21:21,780 So don't expect to be able to go and buy a cheap SIP handset from your local retailer and connect it 264 00:21:21,780 --> 00:21:28,410 to a Cisco core manager or express environment and have the same features as Sysco phones. 265 00:21:28,440 --> 00:21:29,650 That's not going to happen. 266 00:21:29,670 --> 00:21:35,280 You're going to be able to make and receive calls and have basic functionality, but don't expect the 267 00:21:35,280 --> 00:21:38,580 same features as what you'll get on a Cisco handset. 268 00:21:39,240 --> 00:21:43,050 A peer to peer protocol isn't a great idea when you have 10,000 phones. 269 00:21:43,050 --> 00:21:49,410 So in SIP we have the concept of a proxy server, which as an analogy controls the call between the 270 00:21:49,410 --> 00:21:50,340 two phones. 271 00:21:50,940 --> 00:21:56,070 Please note this is not a pure client server environment like you have in Skinny. 272 00:21:56,160 --> 00:22:02,490 Certain processing can be done by the local handset with most of the processing done by the Q CM. 273 00:22:02,850 --> 00:22:10,320 Whereas in Skinny all processing is done on the CU cm SIP is becoming more and more popular, and over 274 00:22:10,320 --> 00:22:15,420 the last few years, Sysco has been investing more and more in the features and functionality of their 275 00:22:15,420 --> 00:22:16,350 SIP phones. 276 00:22:16,980 --> 00:22:19,920 One of the great things that you get with is presence. 277 00:22:20,490 --> 00:22:26,940 SIP also provides interoperability with other vendors and is the protocol of choice for interoperability 278 00:22:26,940 --> 00:22:28,080 between vendors. 279 00:22:29,080 --> 00:22:35,740 Once registered with the SIU Cwm, the phones will download their soft key templates. 280 00:22:36,130 --> 00:22:40,870 We'll be talking more about the soft key template later, but essentially that is the layout of some 281 00:22:40,870 --> 00:22:42,310 of the buttons on the phone. 282 00:22:44,160 --> 00:22:48,030 That concludes our discussion of the Cisco IP phone start up process. 283 00:22:48,540 --> 00:22:50,850 We looked at how an IP phone obtains power. 284 00:22:51,330 --> 00:22:55,350 We discussed different methods of provisioning power to an IP phone. 285 00:22:55,830 --> 00:23:02,550 We looked at how an IP phone obtains VLAN information, IP addressing configuration and firmware and 286 00:23:02,550 --> 00:23:04,530 how it registers with a system. 287 00:23:04,980 --> 00:23:11,910 We also discussed the two signaling protocols that can be used by Cisco IP phones, skinny and SIP. 288 00:23:12,790 --> 00:23:13,930 Thank you for watching.