TheSkinny Client Control Protocol (SCCP) is a proprietary network terminal control protocol originally developed bySelsius Systems, which was acquired byCisco Systems in 1998.
SCCP is a lightweight IP-based protocol for session signaling with Cisco Unified Communications Manager, formerly namedCallManager.[1][2] The protocol architecture is similar to themedia gateway control protocol architecture, in that is decomposes the function of media conversion in telecommunication for transmission via anInternet Protocol network into a relatively low-intelligence customer-premises device and a call agent implementation that controls the CPE via signaling commands. The call agent product is Cisco CallManager, which also performs as a signaling proxy for call events initiated over other common protocols such asH.323, andSession Initiation Protocol (SIP) forvoice over IP, orISDN for thepublic switched telephone network.
An SCCP client usesTCP/IP to communicate with one or more Call Manager applications in a cluster. It uses theReal-time Transport Protocol (RTP) overUDP-transport for the bearer traffic (real-time audio stream) with otherSkinny clients or an H.323 terminal. SCCP is a stimulus-based protocol and is designed as a communications protocol for hardware endpoints and other embedded systems, with significant CPU and memory constraints.
Some Cisco analog media gateways, such as the VG248 gateway, register and communicate with Cisco Unified Communications Manager using SCCP.
Cisco acquired SCCP technology when it acquired Selsius Corporation in 1998.[3] For this reason the protocol is also referred to in Cisco documentation as the Selsius Skinny Station Protocol. Another remnant of the origin of the Cisco IP phones is the default device name format for registered Cisco phones with CallManager. It isSEP, as inSelsius Ethernet Phone, followed by theMAC address. Cisco also has marketed a Skinny-based softphone called Cisco IP Communicator.
Examples of SCCP client devices include the Cisco 7900 series of IP phones, Cisco IP Communicator softphone, and the802.11b wireless Wireless IP Phone 7920, along with Cisco Unity voicemail server.
Other companies, such asSymbol Technologies, SocketIP, andDigium, have implemented the protocol in VoIP terminals and IP phones,media gateway controllers, andsoftswitches. An open source implementation of a call agent is available in theAsterisk andFreeSWITCH systems.[4] IPBlue provides asoft phone that emulates a Cisco 7960 telephone.[5] Twinlights Software distributes a soft phone implementation forAndroid-based devices.[6] The Cisco Unified Application Environment, the product acquired by Cisco when they purchasedMetreos, supports using SCCP to emulate Cisco 7960 phones allowing applications to access all Cisco line-side features.