Skinny Client Control Protocol: Difference between revisions

Revision as of 08:41, 10 July 2015

Revision as of 16:45, 10 July 2015

Line 1:

{{distinguish|Signalling Connection Control Part}}

The '''Skinny Client Control Protocol''' ('''SCCP''', or short ''Skinny'') is a proprietary network terminal control protocol originally developed by [[Selsius. CiscoSystems]], which was acquired Selsiusby [[Cisco Systems]] in 1998.

The SCCP technology is now owned and defined by [[Cisco Systems]]. SCCP is a lightweight IP-based protocol for session signaling with [[Cisco Unified Communications Manager]], (formerly callednamed ''CallManager)''. SCCP is used to communicate between IP devices and Cisco Unified Communications Manager. <ref> [http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_5_1/ccmsys/a08procl.pdf Understanding IP Telephony Protocols] </ref><ref>[http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080624977.shtml Call states sent to SCCP endpoints by Cisco CallManager]</ref> Examples of SCCP clients include the Cisco 7900 series of IP phones, Cisco IP Communicator softphone and the [[802.11b]] wireless Wireless IP Phone 7920, along with Cisco Unity voicemail server. CallManager acts as a signaling proxy for call events initiated over other common protocols such as [[H.323]], [[Session Initiation Protocol]] (SIP), [[ISDN]] and/or [[Media Gateway Control Protocol|MGCP]].

==Protocol components==

AAn SCCP client uses [[TCP/IP]] to communicate with one or more Call Manager applications in a cluster. It uses the [[Real-time Transport Protocol]] (RTP) over [[User Datagram Protocol|UDP]]-transport for the bearer traffic (real-time audio stream) with other '''Skinny''' 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 Analoganalog media gateways, such as the VG248 gateway, register and communicate with [[CallManager|Cisco Unified Communications Manager]] using SCCP.

==Origin==

Line 14:

==Other implementations==

Other companies, such likeas [[Symbol Technologies]], SocketIP, and [[Digium]], have implemented thisthe protocol in VoIP Terminalsterminals and IP (phones), [[Mediamedia Gatewaygateway Controllercontroller]]s, and [[Softswitchsoftswitch]]es. An open source implementation is available in the [[Asterisk (PBX)|Asterisk]] and [[FreeSWITCH]] systems.<ref>http://wiki.freeswitch.org/wiki/Mod_skinny</ref> systems. IPBlue<ref>http://www.ipblue.com/ IPBlue</ref> marketsprovides a software phone ([[soft phone]]) which uses SCCP for signaling andthat emulates a Cisco 7960 hardware phonetelephone. Twinlights Software<ref>http://www.twinlightssoftwareipblue.com/ Twinlights SoftwareIPBlue</ref> Twinlights Software distributes a [[soft phone]] implementation for [[Android (operating system)|Android]] -based devices.<ref>http://www.twinlightssoftware.com/ Twinlights Software</ref> The Cisco Unified Application Environment, the product acquired by Cisco when they purchased [[Metreos]] supports using SCCP to emulate Cisco 7960 hardware phones allowing applications to access all Cisco line-side features.

==See also==

*[[Voice over Internet Protocol]]

* [[Media Gateway Control Protocol Architecture]]

==References==