Hi Peplink Team,
We’re working on a use case involving the POTS Adapter in emergency communication environments, where Auto Dial functionality is critical for deployment. While the feature works well on a per-device basis, we’re currently looking for a way to apply Auto Dial numbers and related settings in bulk—similar to how Peplink routers support configuration templates or group-based tagging within InControl2.
This would significantly improve efficiency and consistency when scaling to larger deployments. Ideally, we’d like to see:
- Bulk configuration support via InControl2
- Ability to apply Auto Dial numbers across multiple units
- Tag-based or group-based configuration application
- Whitelist and Hotline toggle included in bulk options
Looking forward to any consideration for future roadmap support. Thank you!
2 Likes
Hi, we will implement this feature in 2.14.1 tentatively. A group-level POTS Adapter Settings screen will be added. Similar to the SSID Settings, you can create profiles, select devices by tags, toggle whitelisting (or blacklisting?), etc.
2 Likes
Hi Peplink Team,
That’s AWESOME news, THANK YOU! That upcoming release will help us out tremendously. I’m assuming the v2.14.1 release is planned for later this year, given we’re currently running firmware 1.1.3 on the POTS Adapter? If there’s a private beta or early access program, I’d love to participate in testing it out.
On a related note, I noticed you mentioned “blacklisting” in your reply. I wasn’t sure if I should start a new thread for an additional feature idea or continue here, please let me know what you prefer.
It’s related to a potential feature we’re exploring for the POTS Adapter:
Would it be possible to support a small set, maybe 5 or so, of user-defined numbers that, when manually dialed (e.g., 911, a local security number, or any 10-digit number the organization chooses), could be automatically mapped or rewritten to a preconfigured number before routing? This would be extremely useful in deployments where organizations don’t have SIP, PBX, or cloud infrastructure, often due to budget or complexity.
We’re currently working with an E911 partner to field test a scalable deployment, and this type of dial handling could be critical for expanding beyond Auto Dial use cases.
If helpful, I’ve put together a short diagram and NDA safe write up to clarify the use case and value. Happy to share it if you’d like more detail!
Thanks again for the roadmap visibility and looking forward to what’s next!