This Frequently Asked Questions (FAQ) document provides concise answers and guidance for using Grandstream GWN76xx indoor and outdoor Wi-Fi access points. It is intended to assist installers, administrators, and end users in planning deployments, resolving common issues, and understanding key features.
Product Overview & Models
GWN7603 / GWN7605 / GWN7605LR: 100 concurrent clients.
GWN7630 / GWN7615 / GWN7624 / GWN7625: 200+ concurrent clients.
GWN7630LR: 250+ concurrent clients.
GWN7604 / GWN7660E / GWN7660ELR / GWN7661E / GWN7662 / GWN7670 / GWN7670WM / GWN7670LR: 256 concurrent clients.
GWN7665 / GWN7672: 384 concurrent clients.
GWN7660 / GWN7660LR / GWN7661: 500+ concurrent clients.
GWN7664E / GWN7664ELR: 512 concurrent clients.
GWN7664 / GWN7664LR: 750+ concurrent clients.
Note: These are maximum design limits, real usable clients per AP depend on environment and traffic.
When used as an embedded controller, a GWN76xx access point can manage up to 50 local GWN APs.
The only exceptions are GWN7624 and GWN7625, whose embedded controller can manage up to 30 local GWN APs.
Most GWN76xx indoor access points provide up to 175 meters of coverage in open, ideal conditions.
There are a few models with different typical ranges:
- Up to 100 meters: GWN7603, GWN7604, GWN7624, GWN7661, GWN7661E
- Up to 165 meters: GWN7605, GWN7625
Most GWN76xx outdoor / LR access points provide up to 300 meters of coverage in open, ideal conditions.
Some models have different typical ranges:
- Up to 250 meters: GWN7605LR, GWN7660LR
- Up to 350 meters: GWN7670LR
Indoor GWN76xx access points are designed to be installed inside buildings such as offices, shops, hotels and schools. They focus on good coverage and performance in rooms and corridors, with compact housings for ceiling or wall mounting, but they are not intended to be exposed to rain, dust or direct sunlight.
Outdoor GWN76xx access points are built for open areas like courtyards, parking lots, campuses and building exteriors. They offer longer coverage range in open space and use weather-resistant, rugged enclosures that protect against rain, dust, temperature changes and UV. Outdoor models in this series usually end with LR or ELR, where LR means Long Range and ELR means Enterprise-grade Long Range.
The GWN76xx series includes models that support Wi-Fi 5, Wi-Fi 6 and Wi-Fi 7. All models are backward compatible with older Wi-Fi standards (802.11a/b/g/n). As a general rule:
- Models with 766x in the name are Wi-Fi 6 (802.11ax).
- Models with 767x in the name are Wi-Fi 7 (802.11be).
- All other GWN76xx models (such as the 760x, 761x, 762x and 763x families) are Wi-Fi 5 (802.11ac).
This gives a quick way to identify whether a GWN76xx access point is Wi-Fi 5, 6 or 7 without checking each individual datasheet.
The main factors that really define the “level” of a GWN76xx access point are:
- MIMO / spatial streams (2×2, 3×3, 4×4, etc.): MIMO is the most important indicator of how powerful an access point is. More spatial streams mean more parallel radio chains, which translates into higher real throughput and better performance with many clients connected at the same time. For example, a 4×4 AP can usually handle more users and heavier traffic than a 2×2 AP in the same environment. Client capacity and how “high-end” a model is are largely driven by its MIMO configuration.
- Wi-Fi generation and model family (Wi-Fi 5 / 6 / 7): The Wi-Fi standard defines efficiency and support for newer features, but it is typically secondary to MIMO when it comes to pure capacity. In the GWN76xx series:
- GWN766x models are Wi-Fi 6 (802.11ax).
- GWN767x models are Wi-Fi 7 (802.11be).
- Most remaining GWN76xx models are Wi-Fi 5 (802.11ac), with the exception of GWN7604, which is also Wi-Fi 6 (802.11ax).
Newer generations bring better spectrum efficiency, latency improvements, and support for modern clients (especially in dense environments), but they still rely heavily on the underlying MIMO configuration.
- Indoor vs outdoor design and coverage range: The third key factor is whether the AP is designed for indoor or outdoor use and the typical coverage range it provides. Indoor models focus on coverage inside buildings (offices, shops, hotels, schools), while outdoor LR/ELR models are long-range, weather-protected units for external areas such as campuses, courtyards or parking lots. Range and environment (indoor vs outdoor) determine how many APs are needed and where they can be physically installed.
In practice, MIMO defines the capacity “tier” of the device, Wi-Fi generation defines the technology level, and indoor/outdoor range defines where and how it can be deployed.
Deployment, Installation & Power
GWN76xx access points are designed to be powered only via Power over Ethernet (PoE) through their Ethernet port. They do not include a separate AC power adapter.
Any compatible PoE switch or PoE injector can be used, and models may require PoE, PoE+, or PoE++ depending on their power needs. For planning purposes, always check the datasheet of the specific GWN76xx model to confirm its PoE requirement and power budget.
The front multi-color LED shows power, upgrade, provisioning, and mesh status:
- OFF: Unit is powered off, or there is an abnormal power supply.
- Blinking green: Firmware update in progress.
- Solid green: Firmware update successful.
- Blinking red: Delete paired slave/factory reset initiated.
- Solid red: Firmware update failed.
- Solid pink: Unit not provisioned (not adopted by any controller/master).
- Blinking blue: Unit provisioning in progress.
- Solid blue: Unit is provisioned successfully and operating normally.
- Blinking white: Access Point location feature is active (Locate / Blink command).
- Solid yellow: Mesh disconnection.
- Blinking pink: Slave AP is disconnected from the master device (for example, no network or the master is offline).
For indoor GWN76xx access points, the recommended placement is usually on the ceiling, roughly in the center of the area to be covered, with as few obstacles as possible (not hidden in a cabinet and not right next to large metal objects or thick concrete). Mount the AP at a typical ceiling height and space neighboring APs so their coverage overlaps smoothly instead of being stacked on top of each other.
For outdoor LR / ELR GWN76xx access points, mount the unit on a stable wall or pole, above head height, with a clear line of sight to the area you want to cover. Avoid mounting directly behind walls, trees, or other large obstacles, and orient the front/antenna side toward the coverage area.
These are general deployment guidelines. For precise recommendations such as optimal mounting height, tilt, antenna pattern and supported use cases, the datasheet and official radio/antenna specifications of the specific GWN76xx model must be consulted.
The number of GWN76xx access points you need always depends on several factors:
- the specific GWN76xx model (Wi-Fi generation, MIMO, indoor/outdoor, range)
- the area and building structure (size, walls, floors, obstacles, materials)
- the number of clients and the type of traffic (light browsing vs voice, video, etc.)
As a very rough general rule:
- One indoor GWN76xx AP can often cover around 100–150 m² of open office or room space with normal user density.
- High-density or “busy” areas (classrooms, meeting rooms, crowded open offices) usually require more APs placed closer together than a simple square-meter rule suggests.
These numbers are only rough guidelines, not something to design a big project on.
For important or precise deployments, the layout should be based on the datasheet of the specific model and a proper wireless site survey (Wi-Fi site survey) or Wi-Fi design, where coverage and signal are actually measured or simulated for the real environment instead of relying just on area estimates.
Yes. Indoor and outdoor GWN76xx access points can be used in the same network and are managed in the same way. They share the same feature set, security options, and controller/management options, etc.
In practice, indoor models are installed inside the building, while outdoor LR/ELR models are used to cover external areas such as entrances, terraces, parking lots, or campuses. The main differences are coverage range and the level of weather protection of the hardware; RF planning, channel selection, and management are handled normally, just as in any multi-AP deployment.
This is normal behavior. Disabling the LAN port only stops the Ethernet connection, while the PoE power remains active.
Initial Setup & Wi-Fi Configuration
GWN76xx access points use DHCP by default, so they obtain an IP address automatically. You can find it using Grandstream tools in this order:
- From the controller (if the AP is paired): If the AP is managed by a controller such as a GWN access point in controller mode, a compatible Grandstream router/GCC device, or GDMS Networking (cloud), simply log in to the controller and open the device list. The AP will appear there with its IP address and other details.
- Using the GWN Discovery Tool: From a computer on the same network as the AP, run the GWN Discovery Tool (available from Grandstream’s Support → Tools page). Click Scan, and the tool will list all GWN APs it finds, showing each device’s MAC address and IP. You can then open the AP’s web GUI directly from the tool.
- Using the MAC-address URL: If you know the AP’s MAC address (printed on the label), and your computer is on the same network, you can type this into a browser:
https://gwn_<MAC>.local
replacing<MAC>with the AP’s MAC address without separators. The browser will resolve that name and take you to the AP’s web interface, revealing its IP.
After the GWN76xx is powered and connected to the network, it creates a default Wi-Fi network:
- Default SSID:
GWNxxxxxx, wherexxxxxxare the last 6 digits of the AP’s MAC address. - Default Wi-Fi password: a random, unique password generated for that unit.
- Where to find them: both the default SSID and password are printed on the MAC tag on the AP itself and on the product box label.
GWN76xx access points support the main legacy and modern Wi-Fi security modes. Under Security Mode for an SSID, you can choose:
- Open (no encryption)
- WEP 64-bit / 128-bit
- WPA/WPA2 mixed, WPA2-only (PSK)
- WPA2-Enterprise (802.1X / RADIUS)
- OSEN and WPA2/OSEN (for secure hotspot / captive portal scenarios)
- WPA2/WPA3 transition mode
- WPA3-Personal and WPA3-192 (Enterprise) on supported models/firmware
Security note: Use WPA2 or WPA3 (or WPA2/WPA3) for normal networks. Avoid Open, WEP, and plain WPA except for very specific legacy or guest/captive-portal cases, as they are considered weak or insecure.
Yes. In a multi-AP deployment, you can decide which GWN76xx access points will broadcast each SSID. It is not required that every AP uses the same set of SSIDs.
Whether the APs are managed by the embedded controller on a GWN76xx, by GDMS Networking (Cloud), by GWN Manager (on-premise), or by a GWN router / GCC device, the idea is the same:
you go to the SSID configuration and use the Device Membership (or similar) section to select which access points and radios (2.4 GHz / 5 GHz / 6 GHz where available) will broadcast that SSID.
This way you can, for example, enable a guest SSID only on public-area APs and keep internal SSIDs on office APs, all within the same managed deployment.
To time-limit an SSID, you first create a schedule, then attach it to the SSID.
- Create the schedule
- Go to System → Schedule.
- Click Create New Schedule.
- Define the days and time range when the SSID should be active (for example, Mon–Fri, 08:00–18:00).
- Save the schedule.
- Apply the schedule to the SSID
- Go to SSIDs and edit the SSID you want to control.
- In the Wi-Fi tab, scroll down to Enable Schedule and check it.
- In Schedule, select the schedule you created.
- Save.
The SSID will now be broadcast only during the configured time window and will automatically turn off outside those hours.
Features & Capabilities
Yes. GWN76xx access points let you control which devices can connect to an SSID by using MAC-based access lists.
Step 1 – Create the MAC access list
- Log in to the GWN Web GUI (standalone AP or controller interface).
- Go to Access Control → Access List.
- Click Add to create a new list.
- Give the list a Name and add the client MAC addresses you want to control.
- Save the list.
Step 2 – Apply the list to an SSID
- Go to SSIDs.
- Edit the SSID you want to protect.
- On the Wi-Fi tab, find Use MAC Filtering.
- Select one of the modes:
- Whitelist – only clients whose MAC addresses are in the selected list are allowed to connect.
- Blacklist – all clients can connect except the MAC addresses in the selected list.
- Choose the access list you created earlier.
- Click Save / Apply.
Note: MAC filtering should be used as an additional control. It does not replace proper Wi-Fi security, such as WPA2/WPA3 encryption.
Yes. GWN76xx access points support roaming when they are part of the same Wi-Fi network managed by a controller.
The controller can be:
- Another GWN AP.
- GDMS Networking or GWN Manager.
- Another compatible Grandstream controller, like GWN Routers, GCC Devices.
You configure the SSIDs and security once on the controller, and it automatically pushes the settings to all adopted APs. Client devices then see one unified Wi-Fi network and can move between APs without manually reconnecting.
Roaming decisions are still made by the client, but GWN76xx APs improve the experience using:
- Client Steering, including options such as RSSI Threshold and Client Access Threshold to push devices toward a stronger or less loaded AP.
- Voice Enterprise (11k/11v/11r fast roaming) for smoother roaming with real-time apps like voice and video
With a controller-based deployment, proper RF design, and compatible clients, roaming between GWN76xx APs can be effectively seamless.
GWN76xx access points include a built-in captive portal feature that can be used to create guest Wi-Fi or controlled access networks. On a GWN76xx acting as controller/master, the basic workflow is:
- Create or customize the splash page (logos, background, text, buttons, etc.)
- Create a captive portal policy that defines how users authenticate and how long access is granted
- Enable Captive Portal on the desired SSID and select that policy
On the AP’s own controller, the captive portal typically supports options such as:
- free access with click-through (“login for free”)
- simple password/login page
- voucher-based access
- RADIUS-based authentication
- integration with directory/identity services (for example, Active Directory, SAML SSO, etc., depending on platform and version)
When GWN76xx access points are managed by GDMS Networking (Cloud), GWN Manager on-premise, or a GWN router / GCC, additional captive portal options and integrations can be available, including social logins (such as Facebook, X, Google, Active Directory) and more advanced policies. The exact list of supported methods and configuration steps depends on the controller platform and firmware, so for detailed combinations and limits, the official user manual and platform documentation should always be checked.
In all cases, the logic is the same: design the splash page, define the captive portal policy, then apply that policy to the SSID you want to use for guest or controlled access.
PPSK (Per-User / Per-Device Pre-Shared Key) lets you keep a WPA2/WPA3 password–based Wi-Fi, but instead of one shared password for everyone, each user or device gets its own key. If one key is leaked, you can revoke only that account, and you can even map different keys to different VLANs and bandwidth limits.
On a GWN76xx using its own web UI as controller, the basic setup is:
- Create the SSID with PPSK enabled
- Go to SSIDs and add/edit the Wi-Fi network.
- Under Access Security, set Security Mode (for example WPA2 or WPA2/WPA3).
- Set WPA Key Mode to PPSK without RADIUS (local PPSK accounts) or PPSK with RADIUS (keys managed by an external RADIUS server).
- Save the SSID.
- Create PPSK accounts
- Go to Access Control → PPSK and click Add.
- Select the SSID and fill in: account name, Wi-Fi key, optional maximum number of access clients, optional MAC address, upload/download limits and VLAN if needed.
- Save. Each entry is now a separate PPSK account with its own password and options.
Clients then connect to the same SSID, but each user/device uses the unique Wi-Fi key that was created for them.
Note: The concept of PPSK is the same when GWN76xx APs are managed by GDMS Networking (Cloud), GWN Manager, a GWN router or GCC device, but the web interface layout and menus are different on those controllers. For the exact paths and any platform-specific options, the corresponding controller documentation should be checked.
Time Policy lets you limit how long a client can stay connected to Wi-Fi and define when they are allowed to reconnect. It’s basically a timed session control per user, useful for guest Wi-Fi or shared environments.
On a GWN76xx acting as controller:
- Go to Access Control → Time Policy and add a new policy.
- Limit Client Connection Time: how long a client may stay connected (for example, 2 hours).
- Client Reconnect Timeout Type: how the timer is reset so the client can connect again:
- Reset Hourly / Reset Daily / Reset Weekly: timer resets on that schedule (with Hour of the Day and, for weekly, Day of the Week).
- Timed Reset: clients must wait a specific Client Reconnect Timeout period before they are allowed to reconnect.
- Save the policy.
Then, on the SSID:
- Edit the SSID, go to the Wi-Fi tab, and set Client Time Policy to the policy you created.
Any client connecting to an SSID that uses this Time Policy will be disconnected once their allowed connection time is reached, and can only reconnect again according to the reconnect/reset rules you configured. Time is tracked per policy, so if multiple SSIDs share the same Time Policy, the client’s usage is counted across all of those SSIDs together.
Management & Controller Options
GWN76xx access points can be managed by a controller, which can be:
- another GWN access point running as a controller.
- a compatible Grandstream router.
- a GCC device.
- GDMS Networking (cloud)
- GWN Manager (on-premises)
In all cases, the basic requirement is the same: the AP must be reachable on the same network/VLAN as the controller and must not be already bound to another controller or GDMS Networking account.
Because each controller type has a different web UI, the exact steps to discover and pair APs are slightly different. Users should always follow the pairing procedure described in the user manual of the specific controller they are using.
As an example, when a GWN access point is acting as the controller, you typically:
- Connect the new APs to the same network and power them on.
- Log in to the controller AP’s web interface.
- Go to the Access Points / Configuration page and use Discover AP.
- Select the discovered AP and click the Pair icon so it becomes managed by the controller.
Once paired, configuration is done on the controller, and the controller pushes settings to the managed APs.
The number of GWN76xx access points you can manage depends on which controller or platform you use:
- When a GWN access point, Grandstream router, or GCC device acts as the controller, the maximum number of APs is model-dependent. Each controller model has its own capacity, so you should check that product’s datasheet or documentation.
- GDMS Networking (cloud) is designed for large-scale deployments and is not limited to a fixed AP count.
- GWN Manager runs on a Linux server, and its capacity mainly depends on the server hardware resources (CPU, RAM, storage) and how the system is sized.
If the AP is not pairing (or shows as “discovered” but won’t adopt), check these points:
- Make sure the AP is on the same LAN/VLAN as the controller (GWN AP, router, GCC device, or GDMS Networking local controller). If it’s behind another router, on a different subnet, or on a guest VLAN, discovery/pairing can fail.
- Check that the AP is not acting as a controller itself. If its own embedded controller is enabled, disable it or perform a factory reset so it comes up as a plain AP.
- Verify the AP is not already paired to another controller or bound to GDMS Networking. If it is, unpair / delete it from the old controller or unbind it from GDMS Networking, then reboot and try pairing again.
- Confirm both the controller and the AP are on compatible firmware versions (normally the same major release). If needed, upgrade the standalone AP first using its web UI, then retry pairing.
If all of the above are correct and the AP still won’t pair, factory reset the AP, connect it again to the controller’s network, wait until it is discovered, and then try pairing once more.
The Failover feature lets you designate one slave GWN76xx access point as a backup for the embedded master controller. It is used only in deployments where one AP is acting as the local master that manages other GWN76xx APs.
On the master AP, you select a paired slave AP as the failover device. The master automatically pushes the full network configuration to this failover AP, and it keeps monitoring the master’s status (link, power, etc.). If the primary master goes offline for any reason, the failover AP promotes itself to a temporary backup master, so the wireless network keeps running with the last synchronized configuration.
During this temporary failover mode, you can log in to the failover AP’s web UI with a special account:
- Username:
failover - Password: the previous master password (the master AP that went offline)
In this state, the web UI is mostly read-only; you can view the configuration and perform limited actions such as rebooting slave APs, but you cannot permanently change the network design.
If the original master comes back online, it automatically resumes control, and the failover AP drops back to being a normal slave. If the original master does not return and you decide that the failover AP should permanently take over, you can press “Switch to Master” in the failover interface. At that point, it becomes the new master controller with full write permissions, and the old master can no longer reclaim the role. You then log in using the usual admin credentials of the prior master (username admin and its admin password).
All GWN76xx access points include an embedded controller and a very similar web interface, so any GWN76xx model that has the embedded controller feature can be used as the primary (master) device in a local deployment.
In this type of setup:
- One AP is used as the primary / master.
- Other GWN APs are paired to it as slaves/subordinates and receive their configuration from that primary AP.
- There are no special licenses or software editions required; the role is purely how you use the AP in the deployment.
For best results, it is recommended to pick the most capable AP in the site as the primary, for example:
- a newer Wi-Fi 6 or Wi-Fi 7 model instead of an older Wi-Fi 5 model.
- an AP with higher MIMO / radio capacity (e.g. 4×4 instead of 2×2).
- an AP installed where it has stable power and wired uplink and is always on.
Example: if you have, for example, a Wi-Fi 7 4×4 GWN767x and an older Wi-Fi 5 2×2 GWN76xx, the Wi-Fi 7 4×4 unit is the recommended choice for the primary/master, while the others operate as slaves in the same group.
No. Setting a static IP address on an Range Extender (mesh) AP is not possible, as the Range Extender AP identifies itself as a the Central AP when using a static IP.
Security, Maintenance & Troubleshooting
A GWN76xx access point can be reset to factory defaults in two ways:
- From the web interface: log in to the AP’s web GUI, go to System → Maintenance, then in the General section click Factory Reset / Reset and confirm. The AP will reboot and start with factory default settings.
- Using the hardware reset button: with the AP powered on, press and hold the reset button for about 7 seconds, then release it. The exact location of the reset button depends on the model, so refer to the device label or quick installation guide if needed. The LEDs will blink, and the AP will reboot with factory defaults.
If the AP is paired with GDMS Networking (cloud), a factory reset does not remove it from the GDMS Networking account. When the uplink is reconnected, GDMS Networking can automatically push the previous configuration back to the device. To keep the AP fully reset and unmanaged, remove or unbind it from GDMS Networking first, then perform the factory reset.
GWN76xx access points can be upgraded through whatever is managing them. The basic idea is:
- If the AP is standalone or acting as a controller itself, you upgrade from its own web UI
- If the AP is paired to a controller, you normally upgrade it from the controller’s interface
A controller can be another GWN access point, a compatible Grandstream router or GCC device, GDMS Networking (cloud), or GWN Manager (on-premises). Each has a different web UI and menu names, so the exact clicks will vary; users should always follow the firmware-upgrade section of the controller’s documentation.
For the case where a GWN76xx access point itself is the device you are logged into (standalone or AP-as-controller), the process is generally:
- Go to Grandstream’s official firmware page: https://www.grandstream.com/support/firmware and in the WiFi Access Points section, find your exact model.
- Copy the value in the HTTP Upgrade Server column for the firmware version you want.
- Log in to the AP’s web UI and go to System → Maintenance → Upgrade.
- Set Upgrade Protocol (usually HTTP or HTTPS), paste the copied value into the Firmware Server field, click Save, then click Upgrade Now and wait until the upgrade finishes without rebooting or powering off the AP.
If that AP is also acting as a controller with other APs paired to it, you can then go to the controller’s Access Points / Configuration page, select the adopted APs, and use the Upgrade option so they all pull firmware from the same server, instead of upgrading each one manually.
As an alternative, you can download the .bin firmware file for your model from the same firmware page, host it on your own local HTTP/HTTPS/TFTP server, and put your server’s address and path in the Firmware Server field instead of the Grandstream URL.
You can back up and restore the configuration of a GWN76xx access point from its web interface.
Log in to the AP’s Web GUI (either as a standalone AP or the AP acting as controller), then go to System → Maintenance and look for the Config section.
Use Download Configuration to save the current config file to your computer, and Upload Configuration to restore a previously saved config file to the AP.
If you cannot access the web GUI of the AP, check the following:
- Power and network connection: Confirm the AP is powered by PoE, the Ethernet cable is connected correctly, and the link/activity LEDs are on. If there is no network link, the web interface will not be reachable.
- Same network / VLAN: Make sure your PC or mobile device is on the same LAN/VLAN as the AP, or connected to an SSID that bridges to that network. Being on a different VLAN, guest network, or VPN can prevent access.
- Correct IP address: Verify the IP. You can obtain it from:
- the controller’s device list (if the AP is paired),
- the router/DHCP lease table
- the GWN Discovery Tool or the MAC-based URL (
https://gwn_<MAC>.local) from a device on the same network.
- Use HTTPS and accept the certificate: Open
https://<AP_IP>(orhttps://gwn_<MAC>.local). The AP uses a self-signed certificate, so your browser may show a warning that you need to bypass. - Controller-managed credentials: If the AP is managed by a controller (another GWN AP, Grandstream router/GCC, or GDMS Networking), the username/password and configuration are controlled from the controller. Log in to the controller to check or change credentials instead of trying unknown logins on the AP.
- Factory reset as last resort: If access is still not possible and valid credentials are not available, perform a factory reset on the AP and then re-adopt it to the controller.
On a standalone GWN76xx (using its own web interface), alerts are configured directly on the access point:
- Go to System → Alert.
- Under Alert Configure, choose which events should trigger an alert (for example: memory usage, AP/SSID throughput, admin-password change, firmware upgrade, rogue AP, AP offline).
- Under the Email tab, enable Email Notification, then fill in the sender account (From address, SMTP username/password, SMTP host/port) and one or more receiver email addresses.
- Save and apply. The AP will now send email notifications for the selected local events.
When the same GWN76xx devices are added to a management platform such as GDMS Networking (cloud) or GWN Manager (on-premise), alerting becomes centralized and more flexible:
- Alerts are configured once on the platform and apply to all managed APs, routers, and switches.
- You can select many more alert types (system, performance, security, and network events) and control how they are delivered.
- In addition to email and a web dashboard, the platform can send notifications via mobile app and supported third-party channels such as Wave, WhatsApp, Telegram, or webhooks.
The AP alone can send basic email alerts for its own status, while GDMS Networking or GWN Manager provides richer, multi-channel notifications for the entire Grandstream network.