[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: question about burglar alarm dispute (San Francisco Bay Area)
"Just Looking" <nospam@xxxxxxxxxx> wrote in message
news:47e18599$0$17336$4c368faf@xxxxxxxxxxxxxxxxx
>
> They have developed a way to
> identify an account that has caller ID blocked so they can be certain to
> bill you. Therefore, once notified of a run away, you need to get a hold
> of
> the offending account one way or another and stop the signal (and the
> bill)
> from coming in.
>
> It doesn't matter whose fault it was or wasn't. The signal could have and
> should have been stopped. The billing for service call could have been
> done
> after the full facts were know.
>
The reason the customer is upset is they have a huge phone bill, this was
because the receiver number was a toll call. ANI will identify incoming
calls regardless if caller ID is blocked if the call is made to a toll free
line, but this wasn't a toll free line hence the phone bill. I'm not aware
of any way to identify an call on the fly with caller ID blocked if the call
is placed to a regular (non toll free) other than from the phone companies
MUD records.
What signal?, remember the reason for the multiple calls was
because the thing wasn't actually able to send a signal, it kept calling
trying to send a signal and apparently only gave up after it was finally
able to get the signal acknowledged. Stopping the signal would have been
akin to closing the stable door after the horse has bolted.
Doug
alt.security.alarms Main Index |
alt.security.alarms Thread Index |
alt.security.alarms Home |
Archives Home