Support
Bosch Alarm Notification and Communication Path Checklist
Bosch Communication Support
Summary
Use this page when a Bosch alarm site is unsure whether the system still communicates correctly after NBN, router, phone-line or monitoring changes.
Applies to
- Older Bosch alarm systems
- Sites with changed phone, internet or monitoring paths
- Communication and reporting trouble conditions
Difficulty and time
Difficulty: Moderate
Estimated time: 15 to 35 minutes for safe checks
What you will need
- Keypad access
- History of modem, NBN or phone changes
- Monitoring or technician contact details
- Photos of the communicator or panel area if safe
This guide is not about bypassing or disabling an alarm. It is about working out whether the communication path the customer thinks they still have is actually the one the panel is using today.
Before you start
- Ask whether the site used an old phone-line dialler path.
- Ask whether the premises moved to NBN, new modem hardware or mobile backup recently.
- Write down any keypad messages before power-cycling anything.
- If the site is monitored, treat communication certainty as important, not optional.
Step 1: Work out what the system is meant to report through
- Ask whether the panel used a traditional phone line, IP module, GSM path or another communicator.
- Do not assume the current internet modem automatically replaced the old alarm reporting path.
- If the customer cannot answer this, involve the technician or monitoring provider sooner rather than later.
Step 2: Check the obvious infrastructure changes first
- Ask whether the old PSTN service was removed.
- Check whether the modem, NBN box or communications cabinet has power.
- Ask whether a router was replaced and the alarm path never rechecked afterwards.
- Look for a keypad communication or line-fault indication.
Step 3: Separate customer-safe checks from technician checks
It is fine for the customer to confirm power, recent changes and fault wording. It is not fine to improvise panel rewiring or deeper communicator programming.
- Customer-safe: note the trouble message, confirm power, confirm recent NBN or router changes.
- Technician-level: communicator programming, panel wiring, monitoring-path recommissioning and reporting tests.
Step 4: Decide whether the system still meets the site expectation
Sometimes the real answer is that the alarm is still arming locally, but the reporting path the customer thought they had no longer exists.
- Confirm whether the customer expects professional monitoring, app alerts or both.
- Confirm whether the present hardware can still deliver that path.
- If not, treat the job as an upgrade or recommissioning job rather than a quick fix.
Related support guides
Relevant product categories
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
- Can an NBN change break Bosch alarm reporting?
Yes. If the old reporting path relied on a traditional phone line or a communicator that was never recommissioned after the change, the site may lose reporting without realising it straight away.
- Should I change communicator settings myself?
Not unless you are the competent technician responsible for that system. Customer-safe checks should stay at the infrastructure and fault-message level.
- What should I tell support first?
Tell them what changed on site, what the keypad says, and what communication path the customer believes the system should still be using.