SIPconnect 1.1 Technical Working Group meeting getting underway today in Colorado
Thursday, September 25th, 2008
In a few minutes out in Louisville, Colorado, at the headquarters of Cable Labs, a meeting of the SIP Forum Technical Working Group will be getting underway to work on the SIPconnect 1.1 specification. There will be about 25 people there in person ranging from SIP Forum board members to representatives of telcos, cable providers, SIP equipment vendors and even someone from Microsoft. I won’t be there in person but I’ll be joining about 15 others on a conference call connected into the room there in Colorado.
For the next day-and-a-half, we’ll be basically stepping through the SIPconnect 1.1 specification paragraph by paragraph to ensure that we can come to some degree of consensus on the various points and come out with a specification that can work for the market. You can see some of the documents created by various vendors in the SIP Forum repository although the actual document we’ll be working through is one that was sent out on the mailing list on September 22 integrating a variety of comments. (The message is in the list archive, but the attachments aren’t.)
It may sound like tedious work… and in truth some parts of it undoubtedly will be… but the end goal is to arrive at a SIPconnect specification that can be widely used in the marketplace to drive more SIP connectivity.
WHAT IS SIPconnect?
So what is SIPconnect, anyway? Essentially, it is a specification for how to connect a SIP-based system on a company’s premise (such as an IP-PBX) to a SIP Service Provider. We’re now commonly calling such a connection a “SIP trunk”. The majority of such connections will be to provide PSTN connectivity to the on-premise system.
The ultimate goal is that you will be able to purchase a “SIPconnect-compliant” premise system (like an IP-PBX) and easily connect it to a “SIPconnect-compliant” Service Provider without spending huge amounts of time doing interoperability testing (as you often need to do today). Essentially SIPconnect specifies an agreed-upon set of RFCs related to SIP that both sides agree to implement in certain ways.
SIPconnect 1.1 is in process because while SIPconnect 1.0 is out now, some issues have been identified and the SIP Forum would like to address those issues so that the SIPconnect specification can gain wider usage.
WHAT IS THE VOXEO ANGLE?
We’re interested really from both viewpoints. On the one side, we’re interested in looking at SIPconnect for Prophecy so that customers can install our software on their premise and be able to rapidly connect to a SIP Service Provider. On the other side, we’re interested in how customers can connect their on-premise IP-PBXs to our hosted application platform to be able to interact with applications running on our platform. We also have an interest on our back-end in making SIP interop easier between our SIP cloud and that of the SIP Service Providers that we connect to.
So we’re interested in SIPconnect from a variety of angles. Does this mean we’re committed to becoming “SIPconnect-compliant”? Well, not yet… we need to see how the specification comes out. But we are definitely interested in anything that makes SIP interoperability work better.
Stay tuned for more info…
Technorati Tags: sip, sipconnect, voip, sip forum
Want to learn how Voxeo can help unlock your communications and deliver
a better customer experience?
Please contact us!
If you found this post interesting or helpful, please consider either
subscribing via RSS, becoming
a fan on Facebook, or
following us on Twitter.
The next
RSS Feed




