A SIP Trunk Standard Emerges

David Byrd : Byrd's Eye View
David Byrd
Chief Marketing Officer for ANPI

A SIP Trunk Standard Emerges

In a recent interview I noted that Broadvox has done more interoperability testing (IOT) than any other carrier. The interviewer then responded with a very pertinent question, “Did we find interoperability testing a good thing?” the answer is a resounding “No!” We do it because we have to in order to support the greatest variety of IP PBXs out there.

There are alternatives to IOT such as using our good friends at Ingate and AudioCodes. Both of these offer E-SBCs, IADs and gateways to make IOT almost obsolete. Moreover, the addition of their equipment improves network security and quite frankly helps both the customer and the service provider avoid unnecessary cost due to illegal PBX hacking and call hijacking. However, you can’t convince everyone to spend the additional money and too often they want the simpler install. But I digress.

With the advent of SIPConnect v1.1 we may have a standard for SIP Trunking where we can finally discontinue or at least slow down our IOT activity. It will take some time to see SIP Connect v1.1 compatible equipment and end points but at least a standard now exists.

It will require additional work as two important elements are not addressed in the standard, Faxing and IPv6. I can wait a bit longer for IPv6 but all of us want an answer for FoIP as soon as possible.

If you have an interest in reading the document please do so SIPConnect 1.1 Technical Recommendation for SIP Trunking. It represents the next step for SIP and will support the ever increasing adoption rate for SIP Trunking. It will make it easier for application developers to add new functionality without the concern of mixed platforms or networks.

To the SIP Forum, good job!

Enhanced by Zemanta


Related Articles to 'A SIP Trunk Standard Emerges'
BBQ Shrimp.png
Feedback for A SIP Trunk Standard Emerges

Leave a comment

Featured Events