On Wed, 16 Sep 2009, Mark R Lindsey wrote:
SIPConnect has a lot of good ideas and rules. It describes "well behaved" SIP trunking behavior.
But, unfortunately, they've moved beyond the generally-accepted Best Current Practices. For example, they now *require* service provider (SP) support for encrypted VoIP signaling. SIPConnect also requires parent/child registration; i.e., "trunk group" registration. Some platforms can now support that, and it's a great feature. But other good platforms don't support it (yet).
Can BroadWorks, support registration in broadworks to broadworks SIP trunking?
<> Nathan Stratton CTO, BlinkMind, Inc. nathan at robotics.net nathan at blinkmind.com http://www.robotics.net http://www.blinkmind.com