Posted: Sat Dec 20, 2003 8:02 pm Post subject: [Asterisk-doc] Enum documentation
This is a multi-part message in MIME format.
--------------050505080504000802070005
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey guys,
~ Here's my first draft of the documentation I wrote for ENUM.
Questions, comments, flames all welcome! (First flame dispelled: I
use MS Word, deal with it)
Pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Posted: Mon Dec 22, 2003 9:08 pm Post subject: [Asterisk-doc] Enum documentation
This is a multi-part message in MIME format.
--------------030106050105010107030909
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Peter Grace wrote:
Quote:
Hey guys,
~ Here's my first draft of the documentation I wrote for ENUM.
Questions, comments, flames all welcome! (First flame dispelled: I
use MS Word, deal with it)
Ok, Flames is my choice. I'm a bit picky on Enum.
I added some text in the start, then I gave up. This text is not about Enum,
it's about a platform that used an Enum-like structure to do a TPC.int for telephony.
A good solution, but not Enum and propably something that should be in an appendix.
When covering Enum we should cover Enum. The solution here is very interesting, but not
a general text (How to build your own VoIP routing with Enum-like systems) and not an
Enum description. On the Wiki, this would be sorted in under Tips and tricks, but not
as general documentation.
The text is good PR for enum.fierymoon.com and that's propably something good - to lower
phone costs. There's also some good examples on dial plan solutions and system building
on Asterisk.
Posted: Mon Dec 22, 2003 9:16 pm Post subject: [Asterisk-doc] Enum documentation
Peter Grace wrote:
Quote:
Hey guys,
~ Here's my first draft of the documentation I wrote for ENUM.
Questions, comments, flames all welcome! (First flame dispelled: I
use MS Word, deal with it)
Ok, Flames is my choice. I'm a bit picky on Enum.
I added some text in the start, then I gave up. This text is not about Enum,
it's about a platform that used an Enum-like structure to do a TPC.int for telephony.
(Leif got my text, couldn't send it out on the list due to size limitation)
A good solution, but not Enum and propably something that should be in an appendix.
When covering Enum we should cover Enum. The solution here is very interesting, but not
a general text (How to build your own VoIP routing with Enum-like systems) and not an
Enum description. On the Wiki, this would be sorted in under Tips and tricks, but not
as general documentation.
The text is good PR for enum.fierymoon.com and that's propably something good - to lower
phone costs. There's also some good examples on dial plan solutions and system building
on Asterisk.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum