Recommended SMS Modem for SeQent Alarm Notification

Quick Reference

1. Recommended Hardware

For new SeQent alarm notification deployments that require SMS delivery over a cellular network, the standard recommendation is the MultiTech MultiConnect rCell 100 Series. Two models are currently recommended.

MTR-L4G1-B07-WW (Worldwide)

• Series: MultiConnect rCell 100
• Region: Worldwide variant. Default first choice for most deployments.
• Carrier (US): T-Mobile compatible
• Product page: multitech.com/product/multiconnect-rcell-100-series-mtr-l4g1-b07-ww
• DigiKey: digikey.ca/en/products/detail/multi-tech-systems-inc/MTR-L4G1-B07-WW/18625259

MTR-LNA7-B10-US (United States)

• Series: MultiConnect rCell 100
• Region: US-specific variant.
• Carrier (US): T-Mobile compatible
• Product page: multitech.com/product/multiconnect-rcell-100-series-mtr-lna7-b10-us

Supplier: Procurement is typically through DigiKey. Other authorized MultiTech distributors are acceptable, but DigiKey is the path used by SeQent for North American customers based on recent orders.

2. SIM Card Requirements

The modem requires a SIM card with the following plan characteristics:

• SMS / text messaging enabled. This is mandatory. The alarm notification path uses SMS delivery over the cellular network.
• No data plan. Recommend a plan that has SMS / text messaging enabled and explicitly excludes data. This keeps cost down, reduces the attack surface, and matches the way the modem is used in SeQent deployments.
• Voice is not required for alarm-only use cases.

3. Carrier and Regional Considerations

Both recommended models have been validated for North American deployments on T-Mobile. For deployments outside North America, carrier and band compatibility must be verified before ordering.

Regional check required. Some regions require a 5G-compatible modem before paging will work. If a project is deployed outside North America, or if the customer’s carrier mandates 5G, raise the band and carrier requirement at the Statement of Work stage so the correct rCell variant is ordered the first time.

4. Field Deployment Notes

These notes are drawn from recent on-site deployments and apply to first-time configuration of an rCell 100 modem on a customer network.

• Initial web admin access. If the modem does not respond on HTTP/HTTPS at its documented default IP, switch the modem to DHCP and connect it directly to a laptop.
• Password complexity. The modem’s login system rejects certain special characters (the hash character # was rejected on a recent install). Use alphanumeric passwords, or create an additional admin user with simpler credentials when the customer’s password policy includes rejected characters.
• Static IP planning. Confirm and document the static IP assignment for each modem before site work begins. Address conflicts on customer networks have caused repeat troubleshooting cycles.
• Local firewall. If alarm tests fail with login incorrect or failed to connect to modem, retest from a non-firewalled device. Endpoint firewalls on the technician’s laptop have caused false-negative test failures.
• SMS / Telnet settings. When configuring SMS delivery, verify login credentials, the destination phone numbers on the distribution list, and the SMS settings per the MultiTech configuration document before declaring the path broken.