Re: Happy New Year and E911

>
>
>Hash: SHA1
>
>On Tuesday 07 January 2003 23:28, Scott Siebold wrote:
>  
>
>>Our competitor was forced to change their system  to conform to post
>>phone pickup to
>>send their request for lookup.
>>    
>>
>
>- - From a software engineer/parallel software design PoV, the solution
is to use 
>their process until incoming calls pass a pre-determined rate of 
>inbound-requests, then switch.  May take some tinkering to determine
the 
>exact threshold, and it'll depend on the reference system's ability to
deal 
>with accesses, too, but its doable.
>
>ObGZG: Ok, I'm a geek, I couldn't help it.
>  
>
It isn't the answering point that was being overloaded it was the point 
where the lookup was being
done at. The originating point must be allowed to send the request for a

lookup as quickly as the
calls are answered  or the system will not work . The only connection 
between answering point and
lookup point is a dedicated line (actually two lines) over which the 
request for a lookup goes out and
the response comes back.

 I don't know the details about California but in the midwest four 
states (Illinois, Indiana,
Wisconsin and Michigan) are managed out of one location (Indianapolis). 
Local disasters happen
regularly (plane crashes, train derailments, fires, etc.) and may cause 
major increase in demand locally
but do not effect the system. It's when demand increases over a large 
area and multiple sites start
maxing out that the demand has an impact.

It was AT&T that designed  the system and as designed would not be 
overloaded. The
competitor was looking no further then the local answering points and so

the speed advantage was
used as a selling point.. The problem was not discovered until a large 
area disaster occurred.

I'm also a "geek" and have no problems with other "geek" comments.

Scott Siebold