The IPCablecom2 Residential SIP Telephony effort is intended to replicate many of the residential
features currently available on the public switched telephone network (PSTN), except that the
features operate using a IPCablecom2-based IP (Internet Protocol) network using SIP (Session
Initiation Protocol) for VoIP (voice over IP) sessions. The IPCablecom2 Residential SIP Telephony
features described in this document are intended to form the basis for specification requirements
that define the behavior of SIP clients that interact with the IPCablecom2 network and the
corresponding network behavior.
This Recommendation describes the behaviour of residential telephony features using a standard
RST Client (called RST User Equipment, or RST UE, or simply UE in this document) connected to
the IPCablecom2 network.
Prior IPCablecom efforts have defined residential telephony capabilities that operate on an
IPCablecom IP network. IPCablecom defined an MGCP-based (Media Gateway Control Protocol)
architecture in which a centralized Call Management Server (CMS) controls the telephony services
provided by MTAs (Multimedia Terminal Adapters).
The IPCablecom2 Residential SIP Telephony specification defines how UEs can support residential
telephony capabilities similar to that of IPCablecom. This allows for the deployment of new types
of clients and services while maintaining continuity with existing residential telephony services.
This Recommendation is the overview document describing basic telephony features to be
supported in SIP.
It is an important objective of this work that interoperability between IPCablecom 2.0 and 3GPP
IMS is provided. IPCablecom 2.0 is based upon 3GPP IMS, but includes additional functionality
necessary to meet the requirements of cable operators. Recognizing developing converged
solutions for wireless, wireline, and cable, it is expected that further development of IPCablecom
2.0 will continue to monitor and contribute to IMS developments in 3GPP, with the aim of
alignment of 3GPP IMS and IPCablecom 2.0.
Note – The structure and content of this Recommendation have been organized for ease of use by
those familiar with the original source material; as such, the usual style of ITU-T recommendation
has not been applied.