Support
Set Up and Align a Point-to-Point Wireless Bridge
Wireless Bridge
Summary
Follow the four stages below to diagnose a point-to-point bridge must carry CCTV, intercom or access-control traffic between buildings without losing evidence, configuration or device ownership.
Applies to
- Point-to-point wireless bridges
- Remote CCTV, gate and intercom links
Difficulty and time
Difficulty: Advanced
Estimated time: 45 to 120 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when a point-to-point bridge must carry CCTV, intercom or access-control traffic between buildings. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: bridge endpoints connect weakly, flap, or pass insufficient throughput for cameras.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Record the current channel, roles, IPs and alignment readings before adjustment.
Outdoor radio and mounting work needs competent installation
Observe local radio rules, electrical/surge protection and safe working-at-height practices. Do not align from an unsafe position.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Fresnel zone is obstructed
- Both endpoints use wrong bridge roles
- Channel is congested
- Alignment or throughput is inadequate
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: bridge endpoints connect weakly, flap, or pass insufficient throughput for cameras.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Record the current channel, roles, IPs and alignment readings before adjustment.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Bridge management/cloud > Network > Wireless Bridge/PTP > Link Status, Signal and Channel. Do not change anything until the displayed state is recorded.
- Open Bridge management/cloud > Network > Wireless Bridge/PTP > Link Status, Signal and Channel. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Confirm clear line of sight and Fresnel-zone clearance, not just visual aim.
- Record each endpoint IP, role, channel width, frequency and signal/SNR.
- Calculate expected camera bitrate in both normal and event peaks.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Set one endpoint as the documented base/AP and the other as station/client bridge.
- Use a clean permitted channel and conservative channel width.
- Physically align in small movements while watching live signal/SNR.
- Secure mounts, weatherproof cabling and use surge/earthing practices appropriate to the installation.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Run sustained throughput and packet-loss tests across the bridge.
- View all expected camera streams concurrently.
- Test at night/weather conditions if they affect the link.
- Restart both ends in a planned order and confirm automatic reconnection.
Controlled support test
Situation: The reported symptom was: bridge endpoints connect weakly, flap, or pass insufficient throughput for cameras.
Solution used: The current state was recorded in Bridge management/cloud > Network > Wireless Bridge/PTP > Link Status, Signal and Channel, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Ruijie Official PTP/PTMP Guide before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| bridge endpoints connect weakly, flap, or pass insufficient throughput for cameras | poor line of sight/Fresnel clearance, wrong roles/channel, interference, weak alignment or insufficient capacity | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when a clear correctly configured link still has unstable signal, loss or insufficient measured throughput.
Send the order number if available, exact model, firmware or app version, screenshot of Bridge management/cloud > Network > Wireless Bridge/PTP > Link Status, Signal and Channel, the failure time, and the result of the local proof test.
Related support guides
- Security Network Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- CCTV Buying Guide - CCTV and network planning guide.
Relevant product categories
- Ruijie Networking - Ruijie and Reyee networking products.
- CCTV Products - Cameras and recorders that use the network.
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
-
Where should I click first for wireless bridge setup CCTV?
Start at Bridge management/cloud > Network > Wireless Bridge/PTP > Link Status, Signal and Channel. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for AP/station role, peer identity, RSSI/signal, SNR, channel, negotiated rate, packet loss and uptime.
-
What must I avoid changing during the first check?
Observe local radio rules, electrical/surge protection and safe working-at-height practices. Do not align from an unsafe position.
-
How do I prove the correction worked?
Sustain the required aggregate traffic with acceptable latency/loss, then restart and confirm the bridge reconnects automatically.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Bridge management/cloud > Network > Wireless Bridge/PTP > Link Status, Signal and Channel, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.