This FAQ document provides an overview of the GDMS Mobile Application by Grandstream, focusing on its core features and day-to-day operations. It is designed to help users understand how to deploy, manage, monitor, and secure Grandstream devices using the GDMS mobile platform. The questions and answers are based solely on the official GDMS Mobile Application documentation and address the most common operational scenarios users may encounter.
General Overview & Getting Started
The GDMS mobile application is a cloud-based management tool that allows users to manage Grandstream devices before, during, and after deployment. It provides centralized access for configuring, monitoring, upgrading firmware, and troubleshooting supported Grandstream products remotely through a mobile device.
GDMS separates management into independent subsystems based on product lines, including Unified Communications systems and Networking systems. Users can switch between these systems depending on whether they want to manage UC devices (such as phones and PBXs) or networking devices.
GDMS is designed for enterprises, service providers, system integrators, channel resellers, and multi-site organizations that need a centralized and secure platform to deploy and manage Grandstream devices at scale.
The GDMS mobile application supports various Grandstream products, including GRP, GXP, GXV, DP, WP series devices, On-Premise PBXs (UCM63xx, SoftwareUCM, GCC devices), and CloudUCM instances.
Key features include adding devices by scanning barcodes, remote device configuration, firmware upgrades, real-time device monitoring, alert notifications, SIP account management, and centralized device statistics and reporting.
The GDMS mobile application requires Android OS version 4.1 or later, or iOS version 9.0 or later, depending on the mobile device being used.
Android users can download the GDMS mobile application from the Google Play Store, while iOS users can download it from the Apple App Store
Users can create an account by selecting “Sign Up” on the GDMS app home page, filling in the required information, and verifying the account using a 6-digit verification code sent to their registered email address
Account registration requires a nickname, username, email address, password (8–64 characters with letters, numbers, and special characters), confirmation password, and selection of a user type such as Enterprise, Service Provider, or Personal User.
Users can log in using a username and password, Single Sign-On (SSO), or a Google account. The login method selected determines how authentication is performed during sign-in.
If login attempts fail more than five times, the account is temporarily frozen for 30 minutes. Users can either wait for the cooldown period to end or reset their password using the “Forgot Password” option to regain access.
Yes. If a GDMS account remains inactive for more than one year, it will be automatically locked. To restore access, the user must reset their password.
Device Onboarding & Device Overview
Devices can be added either by scanning the barcode on the device using the phone’s camera or by manually entering the device information. Both methods associate the device with the user’s GDMS account and a selected site.
Scanning a barcode allows users to add devices quickly and efficiently without manually typing the MAC address and serial number. It also enables fast configuration of SIP accounts and firmware management after the device is added.
Users can access the scanning function by tapping the scan icon located in the top-right corner of the Overview page or the Device page in the GDMS mobile application.
After scanning the barcode, users can assign a device name and specify the device location before adding it to a selected site within the GDMS platform.
Yes. Devices without a barcode, or remote devices, can be added manually by entering the required information, such as MAC address, serial number, and site through the “Manual Add” option.
Manual device addition requires entering the MAC address, serial number (S/N), and selecting a site. Optionally, users can also assign a device name for easier identification.
No. A single device can only be added to one GDMS account at a time. Once added, it cannot be claimed by another account unless it is removed first.
Users can search for devices using the device name, MAC address, or site name. Filtering options are also available to narrow results by model, device status, or site.
The Overview page displays statistics such as total extensions, total devices, total sites, account status, device status, device type distribution, and plan status within the selected organization.
Device status shows whether devices are online, offline, or abnormal. “Online” indicates normal connectivity to GDMS, while “Offline” or “Abnormal” indicates connectivity issues between the device and the platform.
The device type distribution summarizes how many audio devices, On-Premise PBX devices, and CloudUCM plans are present within the current organization.
Yes. If the user has permission to access multiple organizations, they can switch organizations directly from the Overview or Device pages to view device data specific to each organization
Device Management & Account Configuration
From the device action menu, users can configure SIP accounts, edit device information, upgrade firmware, reboot the device, or delete the device from the GDMS account, depending on the device type
Users can tap the action button next to a device in the device list to access available management options such as account configuration, firmware upgrade, reboot, or deletion
Users select “Account Configuration” from the device action menu, choose a SIP account under the current organization, and apply it to the device. The configuration is pushed immediately if the device is online.
“Assigned” means the SIP account is already linked to another device, while “Unassigned” indicates the account is not currently associated with any device and can be assigned freely
If the device is offline, the configuration will not synchronize immediately. The settings will be automatically pushed to the device once it reconnects to the GDMS platform
No. SIP accounts configured directly through a device’s local Web UI are not synchronized back to the GDMS platform
For DP series devices, users can configure SIP accounts and assign lines to handsets through the GDMS platform. Existing SIP accounts and line assignments can also be viewed, edited, or deleted
Line configuration allows users to assign specific SIP accounts to individual handsets. If no handset is specified, the system uses a default circular mode for call distribution
No. SIP account and line configurations that exist on the device itself are not synchronized back to the GDMS platform.
GDMS allows users to view On-Premise PBX devices such as UCM6300 series PBXs, SoftwareUCM, and GCC6000 series devices, including their network status and basic information.
Displayed information includes the device name, network status, IP address, assigned site, and device model. Users can also edit device details and reboot the PBX.
Users can view CloudUCM instances, reset the Super Administrator password, temporarily stop CloudUCM services, and resume services later without losing data or configuration.
Firmware Management, Alerts & Monitoring
Users can upgrade firmware by opening the device action menu, selecting “Upgrade Firmware,” choosing the target firmware version, and assigning the upgrade task to the device. The upgrade is executed once the device receives the task.
Firmware labeled as “Official Firmware” indicates that the version is released and supported by Grandstream’s official technical support team.
Yes. The GDMS mobile application allows users to upgrade firmware on a specific device by assigning the upgrade task directly from that device’s management menu.
Users can reboot a device by selecting “Reboot Device” from the device action menu. Once confirmed, the reboot task is immediately assigned to the device.
After confirmation, the reboot command is sent to the device instantly, and the device restarts as soon as it receives the task from the GDMS platform
Devices can be deleted by selecting “Delete” from the device action menu and confirming the action. Once deleted, the device is removed from the current GDMS account
GDMS supports alert messages related to account registration failures, PBX cloud storage issues, CPU traffic control, disk usage, memory usage, abnormal reboots, system crashes, and Fail2ban blocking events
Users can access the “Alert” page to view all alert messages generated by devices and services managed under their GDMS account.
Yes. Alerts can be filtered by type or by severity level to help users quickly identify critical or relevant issues.
GDMS classifies alert severity into three levels: Emergency, Warning, and Notice, allowing users to prioritize responses accordingly.
Tapping on an alert message displays additional details about the event, helping users understand the cause and context of the alert.
Users can view call statistics such as local and remote calls, concurrent remote calls, and extension usage over a 7-day or 30-day period for UCMRC and CloudUCM services
Account Settings, Security & Application Management
Users can view their personal information by navigating to the “Me” tab and selecting “Personal Information”, which displays the account details associated with the GDMS profile.
No. Personal account information cannot be changed directly from the GDMS mobile application. Users can only view the information.
Users can bind Google or Apple accounts to their GDMS account to enable alternative login methods, depending on the mobile platform being used.
Yes. Google accounts can only be used on Android devices, while Apple accounts can only be used on Apple (iOS) devices.
Users can check the MFA status by going to the Personal Information page in the GDMS mobile application, where the current MFA status is displayed.
No. MFA cannot be enabled or configured directly from the mobile application. Users must log in to the GDMS web interface to manage MFA settings.
GDMS supports Email Verification, Authentication Apps using TOTP, TOTP hardware tokens, and FIDO security keys that comply with FIDO2/WebAuthn standards.
During login, a verification code is sent to the user’s registered email address. The user must enter this code in the GDMS login prompt to complete authentication
Users can log out by navigating to the “Me” tab, opening Personal Information, and tapping the “Sign Out” button, then confirming the action
The current application version can be viewed by accessing the “Me” tab, where version information is displayed
The application automatically checks for new versions. If an update is available, users can tap “Upgrade Now” to download and install the latest version
Users can submit feedback by going to the “Me” tab and selecting “Feedback”, where they can describe the issue, attach screenshots if needed, and submit the report to technical support