Skinny Call Control Protocol
From Wikipedia, the free encyclopedia
 |
This article does not cite any references or sources. (October 2007) Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed. |
| The five-layer TCP/IP model |
|---|
| 5. Application layer |
|
DHCP · DNS · FTP · Gopher · HTTP · IMAP4 · IRC · NNTP · XMPP · POP3 · RTP · SIP · SMTP · SNMP · SSH · TELNET · RPC · RTCP · RTSP · TLS (and SSL) · SDP · SOAP · GTP · STUN · NTP · (more) |
| 4. Transport layer |
| TCP · UDP · DCCP · SCTP · RSVP · ECN · (more) |
| 3. Network/internet layer |
| IP (IPv4 · IPv6) · OSPF · IS-IS · BGP · IPsec · ARP · RARP · RIP · ICMP · ICMPv6 · IGMP · (more) |
| 2. Data link layer |
| 802.11 (WLAN) · 802.16 · Wi-Fi · WiMAX · ATM · DTM · Token ring · Ethernet · FDDI · Frame Relay · GPRS · EVDO · HSPA · HDLC · PPP · PPTP · L2TP · ISDN · ARCnet · LLTD · (more) |
| 1. Physical layer |
| Ethernet physical layer · RS-232 · SONET/SDH · G.709 · Optical fiber · Coaxial cable · Twisted pair · (more) |
SCCP (Skinny Call Control Protocol) is a proprietary terminal control protocol originally developed by Selsius Corporation. It is now owned and defined by Cisco Systems, Inc. as a messaging set between a skinny client and the Cisco CallManager. Examples of skinny clients include the Cisco 7900 series of IP phone such as the Cisco 7960, Cisco 7940 and the 802.11b wireless Cisco 7920, along with Cisco Unity voicemail server. Skinny is a lightweight protocol which allows for efficient communication with Cisco CallManager.[1] CallManager acts as a signaling proxy for call events initiated over other common protocols such as H.323, SIP, ISDN and/or MGCP.
A skinny client uses TCP/IP to and from one or more Call Managers in a cluster. RTP/UDP/IP is used to and from a similar skinny client or H.323 terminal for the bearer traffic (real-time audio stream). 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.
Cisco acquired SCCP technology when it acquired Selsius Corporation in 1998.[2] As a remnant of the Selsius origin of the current Cisco IP phones, the default device name format for registered Cisco phones with CallManager is SEP -- as in Selsius Ethernet Phone -- followed by the MAC address.
Other companies like Symbol Technologies and SocketIP have implemented this protocol in VoIP Terminals (phones) and Media Gateway Controllers or Softswitches. Open Source implementations of SCCP/Skinny exist and are now part of the Asterisk (PBX) system.
A company named IPBlue has created a software phone (soft phone) which uses SCCP for signaling, too. This phone in fact appears to the Cisco CallManager server as a 7960 hardware phone.
In addition, Cisco has come out with its own version of a skinny softphone called Cisco IP Communicator as well as SIP-based softphone called Cisco Unified Personal Communicator. Previously, Cisco had a JTAPI/CTI version of a softphone called Cisco IP Softphone.
