This Frequently Asked Questions (FAQ) document provides concise answers and guidance for using the GCC Series UC Endpoints Module. It is intended to assist administrators and users in resolving common issues and understanding key features.
Overview & Capabilities
The UC Endpoints module is used to centrally manage, provision, monitor, and upgrade endpoint devices connected to the GCC PBX. It covers VoIP endpoints such as IP phones and ATAs, as well as IPC devices like IP cameras.
The module supports Grandstream SIP endpoints, selected third-party SIP devices, software-based SIP clients, and Grandstream IP cameras (IPC devices). Device support depends on model compatibility and provisioning method.
The Overview dashboard displays endpoint statistics such as total devices, SIP registration status, IPC device status, firmware upgrade progress, and device type distribution for quick operational visibility.
VoIP Devices refer to SIP-based communication endpoints such as IP phones and ATAs, while IPC Devices refer to IP cameras integrated into the system for monitoring and access via dialing.
Yes. The UC Endpoints module depends on the PBX module for extension management, provisioning logic, and call-related features. The PBX module must be enabled before UC Endpoints functionality can be fully used.
Fast Provisioning & Deployment Methods
Fast Provisioning in GCC UC Endpoints is a deployment mechanism that simplifies and automates the registration of VoIP endpoints to the GCC PBX.
It allows administrators to:
- Create SIP extensions in the GCC PBX.
- Generate a unique 6-digit profile code per extension.
- Register devices without manually configuring SIP user ID, authentication ID, or password on the endpoint.
Fast Provisioning significantly reduces deployment time and configuration errors, and supports bulk provisioning, zero-touch onboarding, and multiple endpoint types (IP phones, Wi-Fi phones, video phones).
Initial Dial-up Deployment is used to provision and register SIP extensions on VoIP endpoints that do not support One-Click Configuration.
It enables administrators to deploy SIP accounts to such devices by:
- Manually pushing a SIP NOTIFY message from the GCC VoIP Devices to the endpoint.
- Allowing the user to dial a profile code from the device keypad.
- Automatically retrieving the SIP account configuration and completing extension registration, including MAC address association.
This method provides a fallback provisioning mechanism for legacy or unsupported endpoints while still leveraging GCC Fast Provisioning.
Yes. Fast Provisioning and Initial Dial-up Deployment require the endpoints and the GCC device to be on the same LAN to support discovery, SIP messaging, and configuration delivery.
Profile codes can be configured with expiration periods, usage limits, and permanent validity options to prevent unauthorized or unintended device provisioning.
Yes. Administrators can import extensions in bulk using an Excel template, associating extension numbers with MAC addresses, network priority, and call security parameters.
VoIP Devices Management
The GCC supports three auto-provisioning methods for VoIP devices:
- SIP NOTIFY: Devices initiate provisioning by sending a SIP SUBSCRIBE message; the GCC responds with a SIP NOTIFY containing the configuration server URL.
- DHCP OPTION 66: Devices will send out a DHCP DISCOVER request. The GCC receives it and returns the DHCP OFFER with the config server path URL in Option 66.
- mDNS: Devices send out an mDNS query to get the TFTP server address. The GCC will respond with its address, and the device will then send a TFTP request to download the XML config file.
GCC only responds to provisioning requests that include a specific filename in the URL, such as cfg.xml or cfg{mac}.xml
When VoIP devices boot up on the same LAN, they can be automatically discovered by the GCC as part of the provisioning process. Additionally, administrators can manually trigger discovery from the Web UI to locate existing devices on the network.
The UC Endpoints module supports three discovery methods, which can be selected when running a manual scan:
- PING: Detects reachable devices by ICMP response
- ARP: Discovers devices using the ARP table
- SIP Message (NOTIFY): Uses SIP signaling to identify VoIP endpoints
Once discovered, devices appear in the VoIP Devices list with identifying details such as MAC address, IP address, model, vendor, firmware version, and registration status.
Yes. The UC Endpoints module allows VoIP devices to be manually added and configured before they are discovered on the network.
Once the device is physically connected and powered on, it will then be discovered and provisioned using the predefined configuration.
Yes. The UC Endpoints module allows administrators to directly access an endpoint’s Web UI from the GCC interface. This option is available in the VoIP Devices list for each discovered or manually added endpoint.
The administrator selects a device from Device Management→VoIP Devices, and clicks the Web UI access icon opens the endpoint’s embedded web interface directly.
Yes. The UC Endpoints module supports bulk updates for VoIP devices. Administrators can select multiple devices from Device Management→VoIP Devices, which unlocks a batch update action from the toolbar. The GCC then sends a SIP NOTIFY message to all selected endpoints at the same time, and each device retrieves the updated configuration.
Yes. The UC Endpoints module allows administrators to import and export the VoIP devices list using CSV/XLS format files.
Provisioning in the UC Endpoints module uses a multi-layer configuration model, where each layer has a defined priority. Higher layers override lower layers when the same parameter is configured in multiple places.
The provisioning architecture is defined as follows:
- Global Policy (lowest priority): intended for system-wide defaults such as localization, network settings, call features, security, and maintenance parameters.
- Global Templates: allow administrators to create reusable configuration profiles that can be selectively applied to devices. Multiple global templates can be assigned to a single device and ordered by priority.
- Model Templates (highest priority): model-level configuration that applies to all devices of a given model.
IPC Devices
The IPC Devices section in the UC Endpoints module is used to manage and integrate Grandstream IP cameras with the GCC system for monitoring and access control purposes.
IPC device integration uses RTSP (Real Time Streaming Protocol) for video streaming. For media transport, the default protocol is UDP.
Each IPC device is assigned a Device Number that users can dial to access the camera stream. When dialed, the system connects the user to the configured camera stream.
Yes. Access can be restricted at a granular level to specific users or organizational units. This ensures only authorized users can view specific cameras.
Heartbeat Detection is a device availability monitoring mechanism that allows the system to determine whether the IP camera is reachable and operational.
The GCC monitors IPC device status by Periodically sending RTSP OPTIONS heartbeat messages to evaluate the device’s response and determine online status. This enables real-time status visibility within the UC Endpoints module.