Products

SCCP Protocol

Metreos offers a number of products that help Cisco customers get the most out of their IP telephony investment - using SCCP today and providing for a seamless transition to SIP over time.

SCCP Applications

Metreos offers a number of packaged applications that use SCCP such as:

  • PhoneProxy
    Enables secure deployment of Cisco IP phones to homes without a VPN router, and provides for secure use of Cisco IP Communicator by aggregating traffic crossing from the data to the voice VLAN and by obscuring CallManager information.
  • ClusterMobility
    Enables mobile users to move freely and transparently among CallManager clusters, retaining their phone's features and a single phone number.
  • More
    Other Metreos packaged applications such as RapidRecord, ActiveRelay and VoiceTunnel also can be easily deployed using SCCP.

SCCP Developer Tools

The Metreos Visual Designer is a visual integrated development environment (IDE) for rapid VoIP development. It enables developers from the data center (who may lack IP telephony development experience) to easily and rapidly develop applications - using SCCP and other major protocols - to converge voice with enterprise applications and data. Using this approach, development time for new VoIP applications is dramatically reduced to days rather than weeks or months, and maintenance of applications is made much faster and easier.

SCCP Application Environment

The Metreos Application Environment is the industry's first and only complete application environment for VoIP. It includes the Metreos Application Runtime, Metreos Media Engine, Metreos Management Console and Metreos Visual Designer. The Metreos Application Environment includes support for SCCP, as well as a variety of other protocols such as SIP, H.323, JTAPI, Cisco Extension Mobility and Cisco IP Phone Services.

About the SCCP Protocol

The SCCP protocol is a Cisco protocol standard for real-time calls and conferencing over Internet Protocol (IP). With the SCCP protocol, Cisco IP phones can co-exist in an H.323 environment.

An H.323 proxy can be used to communicate with the Skinny client using the SCCP protocol. In such a case, the telephone is a Skinny client over IP, in the context of H.323. A proxy is used for the H.225 and H.245 signaling.

With the SCCP protocol architecture, the vast majority of the H.323 processing power resides in an H.323 proxy — the Cisco CallManager. The end stations (IP phones) run what is called the Skinny client, which consumes less processing overhead. The client communicates with CallManager using connection-oriented (TCP/IP-based) communication to establish a call with another H.323-compliant end station. Once CallManager has established the call, the two H.323 end stations use connectionless (UDP/IP-based) communication for audio transmissions.