[VoIP] Status monitoring

[Dennis D Hock]

John,

I think that given this is a hobby perhaps a year should be the alloted
time to let a person get something built and get an office MW assigned on
it.  Would it be possible to use Chads or someone elses build to do the
continous automated verification?  That would allow someoont to check the
codes and post as well as try to discover who the person is and what they
want to do.

I think one of us should pick it up and would be willing to try if there
isn't too much deep Asterisk work (doesn't sound like it).  I don't think
Greg should have to pick it up.

My thoughts.

Dennis Hock

-----voip-bounces at lists.ckts.info wrote: -----


To: Voice Over IP Tandem for Analog Switches <voip at lists.ckts.info>
From: John Novack <jnovack at stromberg-carlson.org>
Sent by: voip-bounces at lists.ckts.info
Date: 08/26/2007 10:45PM
Subject: Re: [VoIP] Status monitoring


Jayson Smith wrote:
> Hi,
>
>      Here's something I posted last June on the subject:
> Another issue with which I'm likely to start a flamewar is timeframes.
> Let's say a guy comes along, thinks CNET is totally cool, and registers
an office code thinking he'll set up an Asterisk box.  After a while, for
some reason, he loses interest in the project and we never hear from him
again.
> Yet, his office code is patiently waiting for him to activate it, and
during this infinite time, from now until the end of the world, nobody else
can take it.  Once again, I'm not saying this has happened, but if it ever
were to happen, there should probably be a policy where any office code
that's been registered but goes unused for so long, and the registrant is
unreachable or no longer interested, should be freed up for someone else to
use.
>
As the community grows, this will be come more of a bone of contention.
In some cases it may even discourage someone from joining the group. I
know of one case that someone said "if I can't have Nxx then I don't
want to join in " Of course, Greg has a reasonable solution with the
ability to split office codes, and reasonable members will certainly
find a way to share 10000 numbers.

> Here are my thoughts now. Maybe someone should do a one-time polling of
all office codes, looking for those that, although listed in the Wiki, come
back as invalid when a call is attempted. I presume this is what happens
when an office code is registered but never activated?
One time may not be such a good idea, as almost anything wrong on the
net can cause a one time outage, from the ISP to dyndns not properly
updated to a hardware failure such as Remco's.
Long term inactivity needs to be addressed, though. I know of several
codes that have never been in use, some reserved by members that don't
participate in the list community, others that have specific numbers in
the directory that haven't worked in months, and others that have been
reserved but will be up and running later this year.
> Greg may have records, even though they are not accessible to us, of name
and Email address of registrant and date of registration. For invalid
office codes that have been registered for a long time (how long?) someone
should attempt to contact the registrant. If there's still interest, retain
the code. If not, release the code. For those people who don't respond,
have outdated contact info, etc.
> post a list of names, office codes, and dates to this list to see if
anyone here knows the people in question and can provide any insight. If
so, use that info to decide. If, within a reasonable time (How long?) there
are no nibbles, release those codes. Just my thoughts.
>
And perhaps someone would consider doing this besides Greg?
Greg has a more than full time job and a family and I am sure better
things to do than track this kind of thing.
One item missing from the reservation page, probably for good reason, is
contact information for whoever reserved the code. Not sure if even Greg
has that.

I assume this is less of a problem with the UK numbering?

John Novack

--
Dog is my co-pilot

_______________________________________________
VoIP mailing list
VoIP at lists.ckts.info
http://lists.ckts.info/mailman/listinfo/voip
Project Web Page: http://www.ckts.info/