Skip to main content

Network sites

Feature RequestV5.0

We need to establish a relationship between legal locations (Network sites), clients, and equipment installed at these locations. This will allow for better informing of clients and tracking the number of clients attached to locations, and equipment at these sites.


Main goals for release 5.0:

  • tracking equipment connected to Network sites;

  • add and track the number of clients attached to the Network site in manual format by adding an Access device to the customer’s service;

  • possibility to send email/SMS to cohorts of users connected to Network sites;

  • add map coverage of sites.

Posted by Vitalii Basenko (Splynx PM) ·
Status: Released3 comments

Log in to comment and vote

Comments3

  • bwm-dc

    •

    May 31, 2024

    We are using technology (Tarana) that actually allows clients to "roam" or relocate between sites in the event of an outage. This has somewhat limited our ability to "locate" clients (we can't really set a single Location/tower for a client because they may actually connect to a second site if the first site is down for some reason).

    We are relying on MAC authentication (DHCP+RADIUS), so we lean on the statistics page to know where a customer has connected... It would be nice to have better visibility and communication like this!

  • WISP Daniel

    •

    May 29, 2024

    Cool!

    I have been using a crude workaround to get this working by creating an additional field called AP on every client, and then when we send mass alerts we can select individual access points on the tower instead of the entire location.

    • Vitalii Basenko (Splynx PM)

      Team•

      May 30, 2024

      @Pudgy Buns You will see a new functionality with connection client service-Access device-Network site. So, you can send messages not only to all clients connected to the access device but also to all client services linked to a network site.