In the middle of the page is the Select a Call State to Configure drop-down list, which shows every possible call state. Below this are the Unselected Softkeys and Selected Softkeys boxes with the functions available for the selected call state.
Note
The Undefined softkey will create a blank space to position softkeys on the phone display. It is helpful for phone users to have a function (for example, End Call) on the same softkey in all the call states. The Undefined softkey is used for exactly this purpose in the Connected Transfer call state to make the End Call function show on the second softkey, to be compatible with all the other states that use the End Call softkey, such as Connected, Off Hook, and Ring Out.
1. With the Select a Call State to Configure drop-down list set to On Hook, click the Forward All (CFwdAll) item in the Selected Softkeys box, and then click the left-facing arrow between the two lists to move the item to the Unselected Softkeys list. This leaves just the Redial (Redial) and NewCall (NewCall) functions when the phone is on-hook. See Figure 9-40 for an example of this page.
Figure 9-40. Restricted User On-Hook Softkeys 2. Click the Save button.
Note
It is necessary to click Save before changing to a different call state, or any changes made to the current call state will be lost.
3. From the Select a Call State to Configure drop-down list, select Connected. Use the same process to move the Transfer (Trnsfer), Conference (Confrn), Conference List (ConfList), Select (Select), Join (Join), Direct Transfer (DirTrfr), and Video Mode Command (VidMode) softkeys by clicking the left-facing arrow between the two lists to move the items to the Unselected Softkeys list. (Note that the Ctrl key can be used to select more than one item at a time.) The only items remaining in the Connected call state should be Hold (Hold), End Call (EndCall), and Park (Park). Click the Save button.
4. Use the Select a Call State to Configure drop-down list to select On Hold. Move the Direct Transfer (DirTrfr), Select (Select), and Join (Join) softkeys to the Unselected Softkeys list. The only items remaining in the On Hold call state should be Resume (Resume) and New Call (NewCall). Click the Save button.
5. Use the Select a Call State to Configure drop-down list to select Off Hook. Move the Forward All (CFwdAll), Pick Up (Pickup), Group Pick Up (GPickup), and Meet Me (MeetMe) softkeys to the Unselected Softkeys list. The only items remaining in the Off Hook call state should be Redial (Redial) and End Call (NewCall). Click the Save button. 6. Use the Select a Call State to Configure drop-down list to select Remote In Use. Move all the softkeys to the Unselected Softkeys list. There should be no items remaining in the Selected Softkeys box. Click the Save button. Task 9: Common Phone Profile
Common phone profiles are mainly concerned with the hardware settings on the phone. For example, phones with color displays have backlighting that uses power to light up the display. To reduce energy consumption, the phones turn off the backlighting if they are inactive for a period of time, after hours, or on the weekend. This power-saving behavior can be configured as part of the standard common phone profile (or a custom profile).
On the Cisco Unified CM Administration page, navigate to Device > Device Settings > Common Phone Profile and click the Find button if no templates are listed. By default, there is a standard template, and it can be modified but cannot be deleted. Click the Standard Common Phone Profile to see the details. For this task, just look at the various settings, as there will be no changes made. To see the display power settings (for phones with backlit screens), scroll down to the Product Specific Configuration Layout and the Display On Time. Notice that the system will keep the display on from 7:30 a.m. for 10-1/2 hours (until 6 p.m.). See Figure 9- 41 for an example of this page.
Figure 9-41. Common Phone Profile Configuration Task 10: Device Defaults
Device defaults impact the settings used for phones that are autoimported. The device defaults determine the firmware the phones get, the device pool they will register to, and the phone button template to use. The settings are customizable by phone model and protocol, so it is possible for a 7962 phone using SIP to register to a different device pool than a 7962 phone using SCCP. On the Cisco Unified CM Administration page, navigate to Device > Device Settings > Device Defaults. (This is one of the few pages where you do not need to click a Find button to see the entries!) Scroll down to find the phone models for which you created custom phone button templates, and from the Phone Template column, use the drop-down list to select the custom template for that phone. Make sure that you get the desired protocol (SCCP or SIP) for the phone model! Figure 9-42 shows an example of a 7962 using SCCP and a Cisco IP Communicator using SCCP, with custom phone templates.
Figure 9-42. Device Defaults Configuration
Notice that by renaming the default device pool to Madison DP, all phones will autoregister to the Madison DP by default and get the various settings configured.
Click the Save button. Task 11: Testing
1. Use the instructions in Lab 9-3, Step 2-2 to reenable autoregistration. (As noted in Lab 9-3, Step 4-1, the previous phone numbers are still in the system and will not be handed out again, so increase the ending directory number to a higher number than previously used in Lab 9-3.)
2. Connect two phones that have the custom phone button templates configured and let them autoregister. (It might be necessary to reset the network settings on the phones to get them to clear the previous setting and register. See the hardware section of the Introduction for more information.) From the phones, there will be no obvious changes, other than the new directory numbers. Each phone will still have only one directory number assigned. However, if you examine the details of the phone, you will see the number of line buttons correctly assigned, as designated in the template, but only one of them has a directory number.
3. On the Cisco Unified CM Administration page, navigate to Device > Phone and click Find. Listed here are all the phones registered in the system.
where you see the fields configured for phones. On the left side, the increased number of line buttons will be assigned. See Figure 9-43 for an example of this page.
Figure 9-43. Phone Configuration After Device Pool and Phone Button Template
Note
If you scroll down to the Location item under the Device Information section on the right side of the page, you will notice it is showing Hub_None, instead of the Madison Location that was set in the device pool. The location is a required parameter, so the Hub_None location is assigned by default, but the Device Pool location setting will override Hub_None on the phone; thus the Madison Location is active for the phone. However, if any other location is assigned directly on this phone, it will override the Device Pool setting.
Task 12: Cleanup
Use the instructions in Lab 9-3, Steps 4-1 and 4-2 to disable autoregistration and remove all phones.
Lab 9-5: Registering Phones Manually
Figure 9-44. Topology Diagram Equipment Required
This lab uses the following equipment: • Cisco router
• Switch that supports voice VLANs
• CUCM Server or PC with VMware Workstation installed and a VM of CUCM • Two or more IP Phones (desk phone or soft phone on PC or Windows VM) • Lab configuration from Lab 9-4
Learning Objective
Upon completion of this lab, you will be able to register phones manually. Scenario
SOI is adding two phones, each with three directory numbers. While using autoregistration, as shown in Labs 9-3 and 9-4, would import the phones, there are enough other options to configure after the autoregistration that manually registering a phone can be faster. If SOI needed more than a dozen or so phones registered at a time, the Bulk Automation Tool (BAT) (covered in Lab 9-6) is the best solution.