[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: share account #

Subject: Re: share account #
From: Jim <alarminex@xxxxxxx>
Date: 16 Apr 2007 20:31:06 -0700
Newsgroups: alt.security.alarms
References: <HRpTh.1988$vD4.1226@bigfe9> <461e40a8$0$10299$815e3792@xxxxxxxxxxxxxx> <1176388942.693471.227000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <461ee5bf$0$24709$4c368faf@xxxxxxxxxxxxxx> <1176436073.067268.98000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <500ad$461f0e75$43bca3f1$3366@xxxxxxxxx>

On Apr 12, 11:59?pm, Nick Lawrence <n...@xxxxxxx> wrote:
> One problem this method (below) will encounter is when receivers &
> automation systems track caller-id for incoming calls,
> and encounter caller-id mismatch events. Will cause confusion in the
> station.
>
>
>
My central is aware of the installation and they've somehow "linked"
the numbers the accounts call in on.

This was an account that was "switched" from another central so they
"ok'd" it when I explained how it was set up, how old the account was
and therefore the reason it was done that way. If they had a problem
with it, I would have changed it.

Follow-Ups:
- Re: share account #
  - From: Mark Leuck

References:
- share account #
  - From: SamIam
- Re: share account #
  - From: Crash Gordon
- Re: share account #
  - From: Jim
- Re: share account #
  - From: Mark Leuck
- Re: share account #
  - From: Jim
- Re: share account #
  - From: Nick Lawrence

Prev by Message: Re: share account #
Next by Message: Re: share account #
Previous by thread: Re: share account #
Next by thread: Re: share account #
Index(es):
- Message
- Thread

alt.security.alarms Main Index | alt.security.alarms Thread Index | alt.security.alarms Home | Archives Home