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.