Skinny Client Control Protocol: Difference between revisions

Revision as of 21:35, 6 April 2004

Revision as of 18:54, 15 January 2005

Line 1:

'''SCCP''' is a half-proprietary [[VoIP]] terminal control protocol originally developed by Selius Corporation. It is now owned and defined by [[Cisco Systems, Inc.]], whoas usesa itmessaging toset controlbetween theira skinny client and the Cisco [[7960CallManager]]. andExamples 7940of skinny clients include the Cisco 7900 series of IP phone such as the [[Cisco 7960]], [[voiceCisco over IP7940]] and the [[terminal (telecommunication)|terminal802.11b]]s (wireless [[telephone|phoneCisco 7920]]s). ItSkinny is rumoureda tolightweight beprotocol which allows for efficient communication with Cisco Call Manager which may act as a descendantproxy for signalling of call events with other common protocols such as [[IPDCH.323]], or[[SIP]], [[SGCPISDN]]. and/or [[MGCP]].

A skinny client users [[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 Selius Corporation in the late 1990's. As a remnant of the Selius origin of the current Cisco IP phones, the default device name format for registered Cisco phones with CallManager is SEP -- as in ''Selius Ethernet Phone'' -- followed by the [[MAC address]].

Other companies like [[Symbol Technologies]] and [[SocketIP]] have implemented this protocol in [[VoIP Terminal]]s (phones) and [[Media Gateway Controller]]s or [[Softswitch]]es.