User's Manual
Table Of Contents
- ROAMEO Family Wireless Intercom System
- •TR-1800 •AP-1800
- CHAPTER 1 Certification Information
- CHAPTER 2 Introduction
- CHAPTER 3 System Overview
- CHAPTER 4 Site Survey
- CHAPTER 5 Installation
- CHAPTER 6 Basic Operation
- CHAPTER 7 Beltpack Overview
- System Quick Start
- Button Operation – Common
- Menu Structure – Main Menu Access
- Aux Input Menu
- AUX DIM Menu
- Volume Limit Menu
- Headset Select Menu
- Mic Gain
- Sidetone
- Mic Noise Gate
- Hot Mic
- Talk/Listen LED Buttons
- Front Display Brightness
- Top Display Brightness
- LCD Timeout
- Call Tally Talk
- Screen Flip
- Master Talk Switch
- Low Battery Alert
- Call Waiting Alert
- DECT Connection Alert
- Matrix Connection Alert
- Dark Mode Boot Alert
- Key Clicks Alert
- Alerts Levels
- Key Assignments
- Icon Help
- Scroll List
- CHAPTER 8 Access Point Overview
- AP-1800 Front Panel Description
- IPedit Requirements
- IPedit Main Window
- Configuration
- Device Name Field
- Description Field
- Version Field
- IP Address Field
- Netmask Field
- Gateway Address Field
- DNS Server Field
- Domain Name Field
- MAC Address Field
- Use Static IP Settings Check Box
- Disable RSTP Check Box
- Type Field
- Status Field
- Sessions Field
- AP Channels Field
- BP Channels Field
- Sync Display Box
- System ID Field
- PIN Field
- Zone Drop Down Menu
- CODEC Drop Down Menu
- AP ID Number Field
- Sync Master Check Box
- Intercom Alpha Field
- Channel Description Field
- Destination Type Drop Down Menu
- Destination Device Name Field (OMNEO devices and AP-1800 ROAMEO Access Point Only)
- Destination IP Address Field
- Destination Description Field
- Destination Channel Drop Down Menu
- Destination Channel Description Field
- Receiver Latency Field
- DECT BPID
- DECT Zone Selection Field
- Configuration
- CHAPTER 9 Maintenance
- CHAPTER 10 Troubleshooting, Accessories and Replacements
150 Troubleshooting, Accessories and Replacements ROAMEO System
Bosch Security Systems, Inc.
Technical Manual
F.01U.306.750
Rev. 01
No DECT
connection
displayed on
beltpack
• The access points are not
powered-up or have not
finished powering-up.
• Verify all access points covering the area are powered-up.
All access points should have a green light next to the
power jack.
• The beltpack is out of range
of an access point.
• Verify the RF coverage of an access point includes the
immediate vicinity of the beltpack. Bring the beltpack
closer to an access point.
• The beltpack is not
subscribed to the system.
• Ensure the beltpack has a Home access point. Verify the
access point is in the system where the beltpack's BP ID is
entered into one of the channels of the access point. Also,
verify the beltpack has an assigned path (OMNEO channel)
to the Matrix. Bring the beltpack within 40 feet (12 m) and
in the line-of-sight of an access point on the same system as
the Home access point. Subscribe the beltpack.
For more information, see “Subscribe the Beltpack and Connect
to the Access Point” on page 70.
• The zone set up for the
beltpack is not a valid zone
for the access point covering
the area.
• Verify the beltpack's zone setup on it's Home access point
(found in IPedit). Using IPedit, verify the access points to
which the beltpack is connecting are in the same zone.
• The audio CODEC of
beltpack does not match the
CODEC of the access point
providing coverage for the
area.
• Verify the beltpack's Home access point CODEC set up.
Using IPedit, verify the access points that the beltpack is
connecting to use same CODEC as the beltpack's Home
access point.
NOTE: All APs on a system must be set to the same audio
CODEC, G.722 or G.726. When a change is made to
the CODEC, the beltpack must be re-subscribed to
access points in the system.
For more information, see “CODEC Drop Down Menu” on
page 133.
No matrix
connection on
beltpack
• The Matrix is offline. • Ensure the matrix is on and operating.
• The Matrix has not fully
booted.
• Ensure the matrix is fully booted. This can take several
minutes.
• Ethernet from the access
point to matrix is down.
• Verify the access points are connected to the Matrix.
NOTE: Always have Ethernet switches active before booting
the Matrix. If the switches are not active, the DHCP
server (if being used) may fault in assigning proper IP
addresses because it cannot discover the entire network
when it boots.
• The RF DECT link to the
access point is down.
• If the RF DECT link is down the Matrix connection is also
down.
For more information, see “No DECT connection displayed on
beltpack” on page 150.
Issue Possible Cause Solution