Thread: Concept - system area, not dialing.

Hello WIDEMR,

It's possible it might be one following things:

-The system area is not assigned to the area list used in the contact id dialler communications task.
-The process groups assigned to the system inputs do not have the appropriate communications flags checked.
-Monitoring has not mapped the CID data appropriately. (Assuming the dialler is seizing the line).

I'd go with 1 or 3 of the above. Process groups unlikely to be at fault unless they have been changed.

Try triggering a reportable event and do a review check, should see the dialer pick up, and hangup in the log.

Btw, if set account code in the comms task can leave it 0000 in the areas if all areas are to be same code.

Don't know if you have tried disarming and rearming system area (9) after changing the account.

Originally Posted by WIDEMR

Just a quick question for all you concept guys.... im more a tecom man.

A system that has been going for while, concept 3000, seems to not be reporting system area events, ie ac fail, low batt, tampers ect.

Gone through system area, it has all the zones i want in the area, C01:S04 (ac fail) for example and shows in area, (system silent)

System area is on, 24hr is on.....

If i set of tamper, or ac fail (set for 2 min) it comes up on the kp, but dosent report.

Had 0000 as account code, other areas all had a account code (and the same code) so i changed the sys area account to that same code, still no luck.

O&C are set as Y, but i honestaly not sure if it sent those, i believe it hasnt, but that would help if i knew, ill check. All other areas are reporting o&c's and all alarms ect fine, so i assume the comms task is ok.

Anything else i need to check?

Be going back in few days to do more work.

This sounds to me more like a communications task funny, when you trigger the dialler if you go menu-1-1 and go back through the review does it state that the communications task for the b2b dialler is HELDUP?

1. Check the Dialler (Menu-7-3-1) make sure you've got a CID or IRFAST comms task enabled, with phone numbers (Menu-7-3-2) and it is ENABLED (Use 9 to enable and disable)
2. Check to make sure that you dont have PCDIRECT/Windirect or any other (Insight or other Comms Task) enabled that uses port 0 (Use help-9 to drill down or help-0 to drill up inside menu-7-3-1)
3. The good old test butt will help out, do normal alarms go through? Do open and closes for other areas go through, is there a filter against the communications task (Area list filter, menu 7-3-1)

Some places to start...

ReD

yeah is 3000

All other areas, o/c's and zones are reporting fine, as i said unsure if o/c's are going through for sys area (area 9) ill check when i go back out.

Yeah tested with phone butt, i have a fluke ts52 with screen and dtmf digit grabbing, so i can actually see it dial the number and what number, area account codes ect. and for sys events its not picking up the line or trying to dial, but as said displays the ac fail, tampers ect on kp

The only thing that I can think of without seeing the program wold be that there is some kind of area list associated with the commuications task. If the area is on, and your getting alarms coming up in review and the keypads, plus your getting alarms through on other areas, thats all I can really think of, as mentioned before...

Got a copy of the program Its got me interested... whats the firmware? Type 0/1/2 board? Anything special about its setup or needs?

Red