Thanks for the input Tim, ill start to put together a site for
registration and some tools for testing and to aid people in getting setup.
Once this is up and running locally we should extend this out to the
other asterisk user groups such as New York, we could create quite a
nice large peering ring in time.
Phil.
Tim St. Pierre wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I really like the idea.
I have put hooks in my system for SIP peerings from the beginning, but
never had the opportunity to use them.
It always seemed a little backwards to me when two IP clients are
connecting over the PSTN.
100 DIDs isn't a bad number, but it could be a little bit high. We are
primarily a business provider, and have just under 100 DIDs, but many
more endpoints than that, since most of our customers have 6-10 phones
but only 1 or 2 DIDs.
I agree with connectivity requirements.
We should probably agree that g.711u/A be mandatory, with other codecs
optional (negotiated upon INVITE).
- -Tim
Philip Mullis wrote:
I'm popping this off to both list so please forgive me for the cross post.
Id like to propose the creation of a /DUNDi/^(TM) network for providers
/ trunk users if one doesn't already exist (starting with the members
within our group).
There is quite a few of us now I imagine have become providers over the
years along with a number of heavy sip trunk users.
Although for some this proposal wouldn't offer drastic reductions in
upstream provider channel usage; it would however save all of us
tariffed channels if we end up calling DID's in our respective DUNDI cloud.
The /DUNDi/^(TM) network member requirements I'm suggesting at this time
-minimum of 100 DIDs and (maybe this should be lower?)
-connectivity in a data center or a well manage off-site fiber.
(concerns over voice quality mandate this choice)
There is currently a similar exchange for Data called TORIX, I hope to
start something for VOICE (primarily for people at 151, but not limited
to that location)
Please let me know your thoughts or if anyone is interested.
Regards
Philip Mullis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJkLzmI1xz6nMGzusRAgLRAJ9qXebGEgKx5m+ZXaQ/judb7Tc5ZACff7LH
PbnKdLzA1KVj93idY7yvR0w=
=Vfzm
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]