his is the way to go; should any supported Cisco phone be added, you won't have to chase down the firmware files. It fills the flash: drive and con- figuration with a lot of unneeded entries, but it will save you time in the future. Make sure all the files are there. You'll see in a bit how the phone knows which ones to read. Telephony Service CME is configured with the telephony-service command. There are two ways to con- figure it-manually or with a setup script: Chapter 30: VolP R1-PBX(config)#telephony-service ? setup Start setup for Cisco Call Manager Express. Please refer to w.cisco.com/univercd/cc/td/doc/product/access/ip_ph/ip_ks/index.htm for full documentation. you're in a lab environment, I encourage you to run the setup script at least once. This might be of limited use in the real world, but it's a good idea to get a feel for what it will configure. Since I'm a command-line geek, I'm going in full bore and configuring it the hard way. Within the telephony service configuration, we will specify the firmware the phones should load. First, we'll tell CME to create the phone configuration files automatically from the firmware and config. We do this with the create cnf-files command: R1-PBX(config)#telephony-service R1-PBX(config-telephony)#create cnf-files Creating CNF files Now we specify which firmware files should be loaded for each model phone in our environment: R1-PBX(config-telephony)# load 7960-7940 P00308000900 Updating CNF files CNF files updating complete R1-PBX(config-telephony)# load 7970 SCCP70.9-1-1SR1S Updating CNF files CNF files update complete The "Updating CNF files" message appears as a result of the create cnf-files com- mand we ran earlier. If we hadn't run that first, nothing would happen when we issued the load command. The order isn't important. If we were to run the load command first, the config files would be generated when we ran the create cnf-files command. You can always rerun the command to regenerate the config files if you wish: R1-PBX(config-telephony)#create cnf-file