Re: "Failure to communicate" problems

[tourman <robercampbell@xxxxxxxxx>]

On Apr 24, 6:40=A0am, "Hakma" <ha...@xxxxxxxxx> wrote:
> If it is on SIA, change the reporting format to CID. We are using a CS wi=
th
> a name that starts with "L" and their receiver seems to have problem talk=
ing
> SIA with the newer DSC controls. Once in a while, their receiver also has
> problem talking 4/2 with a single digit reporting code.
>
> "tourman" <robercampb...@xxxxxxxxx> wrote in message
>
> news:1158e748-b3af-43a7-b95f-03245b110033@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > Perhaps some of the regulars can suggest a solution to a problem I'm
> > having. =A0For years now, I've been having random failures to
> > communicate that are not caused by improper programming of the panels.
> > There seems to be no pattern to them that I can determine, nor is it
> > make specific. The station is no help and insist there are enough
> > lines coming in to handle any amount of traffic. Whenever they happen,
> > I have the client send a manual test through to the station, and it
> > always goes through properly. This only seems to occur with
> > conventional land lines
>
> > I get daily reports and every day, and there is at least one panel
> > that doesn't seem to have communicated it's test signal (out of a base
> > of 1100 accounts). When I check, rarely is it a real problem....
>
> > Can anyone familiar with station technology suggest potential
> > solutions/problems that could be occurring. I'm at a loss...

RHC: Yes, my station also has the same problem. SIA is only for the
older DSC panels but the newer 1616 / 1832 / Alexor panels MUST use
Contact ID....dunno why but it's no real problem. This is not the
source of my difficulties since I knew this from the beginning and
accounted for it.