Enabling Single-Site On-Net Calling

1. Implementing and Hardening IP Phones Enabling Single-Site On-Net Calling

2. Outline Endpoint Configuration Tools and Elements Overview IP Phone Auto-Registration Configuring Auto-Registration Cisco Unified Communications ManagerBAT and Cisco Unified Communications Manager Auto-Register Phone Tool Using Cisco Unified Communications Manager BAT for Adding Phones to Cisco Unified Communications Manager Manually Adding Phones to Cisco Unified Communications Manager Hardening Cisco IP Phones

3. Endpoint Configuration Tools and Elements Overview

4. Configuration Methods and Tools

5. Endpoint Basic Configuration Elements Phone NTP Reference Date / Time Group Presences Group Device Pool Cisco Unified CM Group Regions Locations Security Profile Softkey Templates Phone Button Templates SIP Profile (SIP Phones Only) Common Phone Profile

6. Phone NTP Reference • Ensures that a SIP phone gets its date and time from the NTP server. • If NTP servers do not respond, the SIP phone uses the date header in the 200 OK response.

7. Date/Time Group Configuration • Date/Time groups define time zones for devices connected to Cisco Unified Communications Manager. • Date/time group is assigned to device pool. • Device pool is assigned to device.

8. Device Pools • Device pools define sets of common characteristics for devices. • The device pool structure supports the separation of user and location information. • The device pool contains only device- and location-related information.

9. Cisco Unified CM Group • A Cisco Unified CM Group specifies a prioritized list of up to three Cisco Unified Communications Managers. • The first Cisco Unified Communications Manager in the list serves as the primary Unified CM for that group, and the other members of the group serve as secondary and tertiary (backup) Unified CM.

10. Regions • Use regions to specify the bandwidth that is used for an audio or video call within a region and between regions by codec type. • The audio codec determines the type of compression and the maximum amount of bandwidth that is used per audio call.

11. Locations • Use locations to implement call admission control in a centralized call-processing deployment. • Call admission control enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls.

12. Phone Security Profile • The Phone Security Profile window includes security-related settings such as device security mode, CAPF settings, digest authentication settings (for SIP phones only), and encrypted configuration file settings. • You must apply a security profile to each phone that is configured in Cisco Unified Communications Manager Administration.

13. Device Settings Device Settings contain default settings, profiles, templates, and common device configurations that can be assigned to a device or device pool.

14. Device Defaults Configuration Use device defaults to set the default characteristics of each type of device that registers with a Cisco Unified Communications Manager.

15. Phone Button Template Phone button templates specify how the phone buttons of a Cisco IP phone should be used. Options include lines, speed dials, and functions such as callback, call pickup, etc. Each Cisco IP phone has one phone button template assigned.

16. Softkey Template Softkey template configuration allows the administrator to configure softkey layouts which are assigned to Cisco Unified IP phones.

17. SIP Profile A SIP profile comprises the set of SIP attributes that are associated with SIP trunks and SIP endpoints. SIP profiles include information such as name, description, timing, retry, call pickup URI, and so on.

18. Common Phone Profile Common phone profiles include phone configuration parameters and are assigned to IP phones.

19. Relationship Between Phone Configuration Elements Phone Softkey Template Phone Buttons Template Device Security Profile Device Pool Date/TimeGroup Regions Locations Common Phone Profile SIP Profile(SIP Phones only) NTP Reference

20. IP Phone Auto-Registration

21. Autoregistration Supported by all Cisco IP phones. Existing endpoints are not affected. Automatically adds Cisco IP phones not found in database (based on MAC addresses). An autoregistration directory number range is configured and each phone added by autoregistration is assigned with the next available directory number of the configured range. Cisco Unified Communications ManagerBAT can be used to make bulk changes after autoregistration. Cisco Unified Communications Manager Auto-Register Phone Tool can be used to associate phones with specific directory numbers.

22. Autoregistration Process Autoregistration may occur as part of the IP phone startup process when the IP phone tries to download its configuration file from the TFTP server. The Cisco IP phone with MAC address 0015C5AABBDD attempts to download configuration from TFTP server: If TFTP server does not contain IP phone configuration file (e.g., SEP0015C5AABBDD.cnf.xml), the TFTP server returns “Read Error” to the IP phone. IP phone will then download XmlDefault.cnf.xml from the TFTP server. IP phone will update its firmware based on the phone load information defined in the configuration file. DHCP Unified CM Cisco TFTP 6 3 1 4 5 2

23. Autoregistration Process (Cont.) IP phone will then register to the Cisco Unified Communications Managerserver configured for autoregistration defined in the XmlDefault.cnf.xml. Cisco Unified Communications Managerwill automatically create a phone device record in the database and assign a DN from the configured autoregistration range to the first line of the device and then create the configuration file (SEP0015C5AABBDD.cnf.xml). IP phone will then download the configuration file (SEP0015C5AABBDD.cnf.xml) and register to the Cisco Unified Communications Manager. DHCP Unified CM Cisco TFTP 6 3 1 4 5 2

24. Considerations for Autoregistration Only one directory number can be assigned. Directory number is assigned out of a pool; no control which phone gets which directory number. Autoregistration protocol (SCCP or SIP) is set globally within the cluster. Autoregistration is enabled per Cisco Unified Comunications Manager Group but can be activated selectively on group members. Endpoints that support both SIP and SCCP firmware will be converted between SIP or SCCP automatically. Only Cisco IP phones are supported. Manual configuration changes are typically required, but process of adding phones is speeded up and MAC address typing errors are eliminated.

25. Configuring Auto-Registration

26. Steps for Configuring Autoregistration Verify (or change) the autoregistration phone protocol. Ensure that autoregistration is enabled on one Cisco Unified CM Group. For each Cisco Unified CM of the Cisco Unified CM Group, enable or disable autoregistration and, if enabled, configure a range of DNs to be assigned. Manual reconfiguration or Cisco Unified Communications Manager BAT may be used to personalize autoregistered devices.

27. Step 1: Assigning The Default Autoregistration Protocol Autoregistration Phone Protocol

28. Step 2: Cisco Unified Communications Manager Group Configuration Enable autoregistration

29. Step 3: Cisco Unified Communications Manager Configuration Enter directory number range for autoregistration Enable autoregistration

30. Cisco Unified Communications Manager BAT and Auto-Register Phone Tool

31. Using Cisco Unified Communications Manager BAT To Add IP Phones Cisco Unified Communications Manager BAT allows for bulk update, add, or delete of records: Can also be used to add phones BAT file has to include MAC addresses of IP phones and directory numbers Alternative to manually putting MAC addresses into BAT files: Use autoregistration to add phones (and their MAC addresses) automatically Export phone records using Cisco Unified Communications Manager BAT Edit directory numbers in exported files, replacing the directory numbers assigned with autoregistration by the desired directory numbers Use edited file to bulk update phone directory numbers Both methods do not scale for large deployments

32. Cisco Unified Communications Manager Auto-Register Phone Tool A set of Cisco CRS scripts and application that has to be installed onto a Cisco CRS server Allows automated phone adds for large deployments Desired phones and their directory numbers are added with dummy MAC addresses using Cisco Unified Communications Manager BAT Autoregistration is enabled so that new phones can be used to call an IVR application, which allows users to enter their directory number Application updates phone with that directory number. Dummy MAC address is replaced by the address of the calling phone Scales to large deployments because: MAC addresses are automatically added MAC address-to-phone configuration association is done automatically based on user input

33. Cisco Unified Communications Manager Auto-Register Phone Tool Requirements Unified CM Auto-Register Phone Tool Services has to be activated in Unified CM. Unified CM Auto-Register Phone Tool has to be downloaded from Cisco Unified Communications Manager plug-in page and installed onto a Cisco CRS/Unified Contact Center 5.0 server. Unified CM Auto-Register Phone Tool installation prerequisites: Ensure that the publisher for Unified CM is configured and running. Ensure that the Cisco CRS server is configured. Optional Unified CM Auto-Register Phone Tool service parameters may be configured.

34. Process of Adding IP Phones Using the Unified CM Auto-Register Phone Tool 1 2 4 3 • Administrator uses Unified CM BAT to preconfigure device records with dummy MAC address. • New phones are added to network and they autoregister to the Unified CM, which creates new device records with a directory number out of the autoregistration pool. • Phone user dials a Unified CM AutoRegister Phone Tool directory number. • Unified CM routes call to Unified CM Auto-Register Phone Tool application on Cisco CRS.

35. Process of Adding IP Phones Using the Unified CM Auto-Register Phone Tool (Cont.) 5 6 7 8 • Cisco CRS prompts user to enter the directory number to be associated with the IP phone and looks up the phone record with that directory number. • Cisco CRS updates the dummy MAC address of the found phone record with the MAC address of the actual device. • Phone downloads new config from Unified CM/TFTP.

36. Using Unified CM BAT for Adding Phones To Cisco Unified Communications Manager

37. Cisco Unified Communications Manager BAT Configuration Procedure The Cisco Unified Communications Manager BAT configuration process includes these steps: Verify that the Bulk Provisioning Services have been activated. Configure Cisco Unified Communications Manager BAT template. Create the CSV data input file. Validate the data input files. Insert the devices into the Cisco Unified Communications Manager database.

38. Step 2: Configuring Unified CM Phone Template Enter the phone templatename Configure device parameters

39. Step 2: Configuring Unified CM Line Template (Cont.) Enter the line template name Configure line parameters

40. Step 3: Uploading CSV Files Locate the file to upload Select the Target and Transaction Type

41. Step 4: Validating Phones Configuration Select the file to validate Select the template to be used Validate all details Start Validation

42. Step 5: Inserting IP Phones into Unified CM Database Select the file and template Start the insertion Select immediately

43. Manually Adding Phones to Cisco Unified Communications Manager

44. Cisco IP Phone Configuration Procedure Add the IP phone. Configure phone settings. Add directory number(s).

45. Step 1: Adding the IP Phone • Select phone type, e.g. 7960 • Select phone protocol (SIP or SCCP)

46. Step 2: Phone Configuration Required parameters: MAC Address (Device Pool) (Phone Button Template) (Common Phone Profile) (Location) (Built-In Bridge) (Privacy) (Device Mobility Mode) Device Security Profile () = parameters with default values

47. Step 3: Directory Number Configuration Required parameters: Directory Number Presence Group Auto Answer Visual Message Waiting Indicator Policy Ring Setting (Phone Idle) Maximum Number of Calls Busy Trigger () = parameters with default values

48. Verify Endpoint Configuration To verify that the phone configuration is done successfully, do the following: Verify that the phone is registered. Verify that the correct Cisco Unified Communications Manager is used. Verify the IP address of the phone. Verify that the lines are associated to the correct phone(s).

49. Verify Endpoint Configuration (Cont.)

50. Third-Party SIP Phone Configuration Procedure • Configure the end user in Cisco Unified Communications Manager. • Configure the device in Cisco Unified Communications Manager. • Associate the device to the end user. • Configure the third-party SIP phone.