Skinny Client Control Protocol (SCCP)
There are two ways to add phones to the Cisco Unified Communications Manager database. The traditional method is to use the Phone Configuration window to manually add the phones, but auto-registration is much faster. In many cases, you might not want to use auto-registration; for example, if you want to assign a specific directory number to a phone at a clinical pharmacy. Furthermore, any college or pharmacy student who uses Skinny Client Control Protocol (SCCP) has the most secure way to control the devices that have access to your PBX environment, especially when managing voice gateway connections through Cisco CallManager.
There is one step that should take place before any endpoint registration, regardless of the chosen registration method. Firstly, you must configure your system parameters, which include basic configurations such as your Communications Manager groups and device pools. Device pools define sets of common characteristics for all devices in the pool. Moreover, the device pool structure supports the separation of user and location information. Although the device pool contains information about systems, devices, and locations. Entering the appropriate configuration mode is essential for setting up these network protocols effectively.
If you do not use auto-registration, you must manually define and add your endpoints to the Cisco Unified Communications Manager database. Thereupon, the CUCM can utilize a variety of endpoint types. Here are a few examples:
- Cisco SCCP IP Phones – hardware IP phones that are using Skinny protocol
- Cisco SIP IP Phones – hardware IP phones that are using the SIP messaging protocol
- Cisco IP Communicator – software phone that is running on your Windows machine
- Third party SIP phones – IP phones from third party vendors that are running general SIP signaling.
- Cisco ATA 186 – analogue telephone adapter; used to provide interfaces for analogue devices like FAX machines
- CIT Ports – In an automated call distribution environment, CTI ports serve as virtual ports for call control between various components.
Before using it, use the following procedures to add a Cisco Unified IP Phone to Cisco Unified Communications Manager. You can also use these procedures as a hint on how to configure any kind of third-party phone. After you add a Cisco Unified IP Phone to Cisco Unified Communications Manager Administration, the RIS Data Collector service displays the device name, registration status, and the IP address of the Cisco Unified Communications Manager to which the phone is registered in the Phone Configuration window.
Task 1: Configure Communications Manager System Parameters for SCCP
In this task, we will prepare a Cisco Unified Communications Manager for IP phones for two sites. For Chicago (Site 2), the branch site, we will manually add phones.
For inactive media, the Skinny Client Control Protocol (SCCP) defaults to a timeout duration of 120 seconds, indicating the longest a call can remain active without media traffic before resource release.
It is crucial to specify the port number within the command syntax to avoid conflicts and ensure proper communication between devices, especially in scenarios involving protocols like SCCP and gatekeeper configurations.
Activity Procedure
Complete these steps:
- Firstly, from Communications Manager Administration page, go to System > Cisco Unified CM Group.
- Next, on the Find and List Unified CM Group page, click Find button to list all Communications Manager Groups that have been configured on the system. If this is a new installation, there will be one Communications Manager Group called Default.
- click on Communications Manager Group Default to change its configuration.
- On the Cisco Unified Communications Manager group configuration page, if you perform a new installation, the system selects only the publisher server as a member for the default Cisco Unified Communications Manager group. Because this topology includes only one Communications Manager, the available servers list will not display any other servers.
- The first item on Selected Cisco Unified Communications Managers will become the active call processing engine for this Communications Manager group.
- Click Save button to save any changes on the system and click Ok to restart all active devices assign with this Communications Manager group.
- On the Cisco Unified Communications Manager Administration page, from the menu select System > Device Pool.
- On Find and list Device pools page, click Find button to list all device pools configured on the system.
- If this is a new installation, only one device pools called default is on the list.
- To add new device pool, click Add new button.
- Create a new device pool with the following parameters:
– Device Pool Name: Chicago
– Cisco Unified Communications Manager group: Default
– Date and time group: CMLocal
– Region: default
– SRST Reference: disable - Click Save to store the new device pools configuration
- Repeat step 10 – 12 for another device pools with the following parameters, but do not add a new device pool. Modify the existing device pool Default with the following parameters:
– Device Pool Name: SanJose
– Cisco Unified Communications Manager group: Default
– Date and time group: CMLocal
– Region: default
– SRST Reference: disable - Confirm that the cluster have two device pools – SanJose and Chicago.
Activity Verification
Once you achieve these results, you have successfully completed this task.
- 2 Device Pools are created.

Task 2: Manually add SCCP Phones to Cisco Communications Manager
Configure an SCCP phone and register it in Cisco Unified Communications Manager. The SCCP client, a software component that runs on IP phones, utilizes SCCP for signaling in call management. During the registration process, the SCCP client establishes a TCP connection for communication with the Call Manager.r.
Activity Procedure
Complete these steps:
Before you manually add any SCCP phones into the CUCM, you must know the MAC addresses of these phones. In this lab, we will use the VTGO phone for the SCCP phones. Since we will add these phones manually, you must know and record their MAC addresses.
- Firstly, on Cisco Unified Communications Manager Administration page, from the menu select Device > Phone.
- Then on Find and list phones, click Find button to list all IP Phones have been configured on the cluster. If this is a new installation, no IP phones will be listed.
- Next, click Add New button to add new IP Phone.
- On Add a new phone button, select Cisco 7965 for the phone type, and click Next.
- Now, select SCCP and click Next.
- Add phone with the following parameter:
– Device Name: MAC address which is used by this particular phone
– Description: Phone2-1
– Device Pool: Chicago
– Owner: Anonymous
– Phone button Template: Standard Cisco 7965 SCCP
– Device Security Profile: Cisco 7965 – Standard SCCP Non-Secure Profile - Click Save.
- On Phone configuration page, click Line [1] – Add a New DN link, to modify the phone number of the phone.
- Use the following parameter for the directory number configuration:
– Directory number: 3001 - Click Save and then Apply.
- Next, if you want to add more phones, you have to repeat steps 3 – 10. For example Phone 2-2 will have the following configuration:
– Device Name: MAC address which is used by this particular phone
– Description: Phone 2-2
– Device Pool: Chicago
– Owner: Anonymous
– Phone button template: Default Cisco 7965 Template.
– Device security profile: Standard SCCP Profile for Cisco 7965
– Directory number: 3002 - Click Save and then Apply.
- Start the VTGO application for the required phones. (Site 2 Phone 1 & 2)
- Verify the TFTP Server configuration. It should point out to 10.1.1.10. You can check this by viewing the setting of the VTGO softphone.
- Lastly, we will manually added two IP Phones with numbers 3001 and 3002, allowing calls to be made between them using the 4-digit directory numbers.
Activity Verification
Once you achieve these results, you have successfully completed this task.
- Cisco Communications Manager registers the IP Phones, assigns them to the Device Pool for Chicago, and applies the button template. The IP Phones can establish a call between each other.
- The Skinny Client Control Protocol (SCCP) plays a crucial role in managing VoIP signaling and resource conservation, ensuring efficient communication between analog endpoints and Call Manager applications.
