NORTH ANDOVER, USA: The SIP Forum announced that it has ratified Version 1.1 of the SIPconnect Technical Recommendation, with the unanimous approval of the SIP Forum Board of Directors. The new version of the recommendation, developed by the SIP Forum’s SIPconnect Task Group, is a follow-on to Version 1.0 ratified in 2008, and provides a more definitive and standardized set of guidelines for seamless, end-to-end interoperability between SIP-enabled IP-PBXs and service provider networks.
The SIPconnect Technical Recommendation, which represents the consensus of a broad cross section of the global telecom community, is one of the most important initiatives of the SIP Forum, aimed at providing an up-to-date, international framework for direct IP peering between SIP-enabled enterprises and service provider networks, ensuring the interoperability of network elements across the IP environment and providing a level playing field for vendors and service providers as they develop new equipment and IP applications for deployment.
“There should be no question that enterprises and service providers are well along the path to all IP-based real-time communications, especially for voice,” said Richard Shockey, SIP Forum chairman of the Board and chairman of the SIPconnect Task Group. “The industry at large will not be able to fulfill the promise of Unified Communications unless the global conversion from TDM/Class 5 to SIP-based services shifts into high gear. High Definition Voice and point-to-point Video Calling, among other advanced services, are technically feasible today. SIP Trunking is the fastest-growing offering in the North American telecom market. Even the U.S. Federal Communications Commission has observed that interconnected VoIP is growing at 20 percent per year.”
He continued: “The SIP Forum’s SIPconnect initiative is a substantial advance in providing a consistent and implementable framework for both enterprises and service providers to deploy advanced SIP-based communications. SIPconnect offers enterprises and whole industries such as manufacturing, finance and healthcare real value by promoting – and enabling -- interoperability.”
The SIPconnect 1.1 Technical Recommendation features an array of enhancements from Version 1.0 such as more comprehensive guidelines about security and SIP end-point and media endpoint functionality. Highlights include:
* Standards-based support for both Static (DNS-based) and Registration (SIP REGISTER-based) modes of operation incorporating the newly approved RFC 6140.
* Description of SIP endpoint functionality required for interworking, with detailed discussion of various error conditions and appropriate responses to those errors.
* Description of media endpoint functionality required for interworking.
* Focus on Phone number (i.e., E-164) based SIP Address of Record.
* Additional voice services using SIP techniques.
* A detailed description of transaction layer security (TLS) usage.
* A roadmap on what implementers can expect in subsequent SIPconnect revisions (IPv6, emergency services, etc.).
SIPconnect puts forth a technical profile based on IETF standards aimed at putting all networks and service providers on the same playing field. The formal adoption by the SIP Forum Board of the SIPconnect Technical Recommendation Version 1.1 is based on recognition that the document has been through comprehensive peer review by known technical experts, including broad membership and significant community review, that it is stable and is well-understood, and that it is believed to have resolved known design choices.
“Because of the SIP Forum’s consensus-oriented approach to developing technical specifications, this updated SIPconnect recommendation drew a wide swath of participation from leading companies in the IP communications industry,” said Marc Robins, president and MD of the SIP Forum. “These participants have been very active in the SIPconnect Task Group effort, and submitted comments, suggested edits and other useful information as the work progressed. The SIP Forum also owes a debt of gratitude for the work and commitment to the project from Spencer Dawkins, Senior Standards Manager at Huawei Technologies USA and the primary document editor of the SIPconnect 1.1 specification.”
SIPconnect 1.1 contributing companies included Acme Packet, AT&T, Avaya, Bandwidth.com, Boeing, Broadsoft, CableLabs, Cablevision, Cbeyond, Cisco, Columbia University, Comcast Cable, Cox Communications, Digium, Encore Software, GENBAND, Global Crossing, Huawei, Ingate Systems, MetaSwitch, Microsoft, NeuStar, Nokia, Nortel, PAETEC, Panasonic, Pbxnsip, Polycom, Radvision, Samsung, Siemens Enterprise Communications, Sonus Networks, Tekelec, Tele2 Nederland, Voxeo, and XO Communications.