If it does, I think if you do this too many times the world might explode. I'm trying to think of the real answer. Broadworks (R14 or newer) is pretty flexible for setting up different device types, but I haven't spent much time on the gateway side of that. -Scott -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan Stratton Sent: Wednesday, September 16, 2009 4:48 PM To: Mark R Lindsey Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] What to look for in a SIP Trunking concept? 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
VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops