Ahh a memory I'd rather forget, unknown to most, John Todd and myself
started a free enum service, similar to what you're doing. (it was called
freenum.org) Unforunately, the project never really got going, due to lack
of time and interest (after thinking it over). I believe it would never have
enough numbers to warrant an enum lookup every time you call. Wasting time
doing a dns lookup for the 1 in 1000 chance an enum entry will be there
isn't worth it. Also, as soon as you get forged numbers (someone taking over
other people's numbers), you'll be in big trouble. "Our number was
taken
over and we lost 20% of our business as a result, i want a million dollars"
Here's a few points:
1) authenicating numbers - JT correctly pointed out, you can't allow people
to call you to verify as caller id can be spoofed. He proposed a group of
asterisk servers calling for verification. I was going to write into this
advertising info so you could get businesses to do the calling for you eg
"you will be contact by an * server, sponsored by blah <insert small
banner
or link>"
2) DNS - IMO, bind just won't work - PowerDNS or similar I'd suggest,
dumping a zone file from mysql when you reach large numbers of entries
doesn't scale
3) You need to work out a good and easy way to verify companies (ranges of
numbers). Targetting the single line people I don't think will yield you
enough numbers.
4) I think you need to allow users to either point their entry to their DNS
or make an easy interface that will generate an entry for them. Don't force
them to enter raw E164 entries (but let them if they really want to)
5) make a non profit organisation, or you'll get sued personally.
good luck, I'm sure JT will have a few comments (probably cursing my name)
Adam
> Anyone wishing to help build/manage openenum.net please contact me via
> email brian@bkw.org ... I would like to have someone assist in building
> and management.
>
> Thanks,
> bkw