In my previous post "SIP Trunking is Hot!"
I mentioned SIPconnect and how important this standard will be to SIP trunking. Well at ITEXPO
, the SIP Forum announced an important ratification of version 1.0 of the SIPconnect Technical Recommendation.
The SIP Forum announced today that it has ratified version 1.0 of the SIPconnect Technical Recommendation with the unanimous approval of the SIP Forum Board of Directors.
The SIPconnect Technical Recommendation v.1.0, an important initiative of the SIP Forum, is a standards-based approach to direct IP peering between SIP-enabled IP PBXs and VoIP service provider networks, and specifies a reference architecture, required protocols and features and implementation rules necessary for seamless interconnection between IP PBXs and VoIP service providers. As SIPconnect was designed to directly tie enterprise customers to VoIP service providers using an end-to-end IP connection, it eliminates the need for a VoIP gateway, improves voice quality and creates a stable foundation for personalized applications and rich media services.
The formal adoption by the SIP Forum Board of the SIPConnect 1.0 Technical Recommendation is based on recognition that the recommendation has been through credible peer review, 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.
"I want to thank all of the participants in the SIPconnect Task Group for their selfless efforts and valuable time necessary to reach consensus and complete the ratification process," said Richard Shockey, Technical Working Group Chair of the SIP Forum. "This was truly an industry-wide effort that we can continue to build on."
Eric Burger, Chairman of the Board of the SIP Forum, commented, "You can expect more work like this from the SIP Forum as we continue to grow our community and revitalize our Technical Working Group to tackle additional interoperability issues."
The SIPconnect Technical Recommendation has recently enjoyed a number of independent implementations, as witnessed by the rapid adoption of the SIPconnect Compliant Program. The SIPconnect Compliant Program offers equipment manufacturers, software providers and service providers the means to attain SIPconnect Certification by the SIP Forum, as well as enjoy the use of a unique certification mark created by the Forum to ensure interoperability among IP communications equipment, software and services.
The SIPconnect Compliant logo serves as the "Seal of Compatibility" for companies that have agreed to abide by the terms of the licensing agreement, and is permitted only on compliant equipment and services that has been rigorously reviewed by the SIP Forum SIPconnect Compliant committee. Several industry leaders and SIP Forum members have recently been awarded the SIPconnect Compliant mark, including Acme Packet, Avaya, BroadSoft, Cbeyond Digium, Ingate Systems and McLeodUSA.
The SIPconnect v.1.1 Task Group
Due to the rapid adoption of SIPconnect and the SIPConnect Compliant Program, there has been substantial interest in enhancing the work through an updated version of the recommendation - SIPconnect 1.1. To that end, the SIP Forum has announced the formation of the SIPconnect 1.1 Task Group.
As with all SIP Forum recommendations, SIPconnect 1.1 will not attempt to create new standards, since that is the work of standards bodies such as the IETF. The goal of SIP Forum specifications is to develop workable and implementable technical recommendations or profiles based on existing industry standards.
The newly formed SIPconnect 1.1 task group will follow the same IETF-like procedures that were adopted by the SIP Forum Technology Working Group and successfully used by the SIPConnect 1.0 task group.
In order to assess the requirements, goals and potential milestones for the task group charter, it will be necessary to assess from the SIP community what is required in the next version of SIPconnect. To that end, the SIPForum Board of Directors wishes to formally open a discussion of requirements for SIPConnect 1.1 at this time.
Those interested in participating in the SIPconnect v.1.1 development effort or being part of the Task Group must be either a Participant or Full Member of the SIP Forum. To join the SIP Forum, head on over to http://www.sipforum.org