CloudUCM is a cloud-based PBX that requires no hardware for deployment, significantly reducing maintenance costs. IP phones and Wave can connect to CloudUCM from anywhere as long as they are connected to the Internet and can be used for audio calls/video calls/meetings, allowing people around the world to easily collaborate with one another.
For more details, please refer to: http://myucm.cloud/
While both CloudUCM and UCM are stable and efficient phone systems with their own advantages, CloudUCM has the following benefits:
The following are essential features of a good cloud PBX provider:
CloudUCM has all of these features above.
CloudUCM converts capital expenditures into operating expenditures.
No. RemoteConnect features are already included with your CloudUCM purchase. UCM RemoteConnect is a cloud service for physical UCMs that allows system administrators to remotely and securely access their systems without complex firewall configurations.
Concurrent calls are calculated assuming a call between a caller and callee counts as a single call. In contrast to the way UCMRC remote calls counts the caller and callee lines as two separate calls if both parties are registered via UCMRC, the same call would be counted as only one call with CloudUCM.
Note: In an N-way conference, each party would count towards the concurrent call limit (e.g., three N-way conference members would count as three concurrent calls).
Yes. Please refer to the Plan Specifications page to see the concurrent registration limits of each plan. While any SIP endpoint/softphone client can register to a CloudUCM extension as long as it doesn't exceed the concurrent registration limit, each extension can have only one Wave PC registration and one Wave Mobile registration.
No. The call duration and concurrent number of emergency calls are not restricted by any CloudUCM plan specifications.
Method 1: For Grandstream endpoints only:
Add the Grandstream IP phone to GDMS. Look for the newly added phone on the VoIP Device page. In the Options column for that phone, click on the button to enter the Account Configuration page. Select the desired CloudUCM extension and save your settings.
Method 2: If the endpoint is not on GDMS, cannot be added to GDMS, or is from another manufacturer, you can register it to CloudUCM by configuring the settings in the following table.
For more details, please refer to the document How to Configure CloudUCM on IP Phones.
|
Settings
|
Parameters
|
Values
|
|
|
Account Settings->Basic Settings
(Required)
|
SIP Server
|
CloudUCM SIP Server Address.
This information can be found under UCM
Web GUI->CloudUCM Plan page.
Note: Must include port number. By default, UDP/TCP is 5060, and TLS is 5061.
(Example: xxx.a.myucm.cloud:5061)
|
|
|
Account
|
Enter the desired extension on the CloudUCM.
|
||
|
Password
|
Enter the extension’s SIP password.
|
||
|
NAT Traversal
|
STUN
|
||
|
DNS Mode (Optional)
|
SRV
|
||
|
DNS SRV Failover Mode (Optional)
|
Use current server until no response
|
||
|
Account Settings->SIP Settings
(Optional. While TLS is recommended, UDP and TCP are also supported)
|
SIP Transport
|
Supports TLS/UDP/TCP. It is recommended to use TLS or TLS/TCP for security reasons.
|
|
|
Account Settings->SIP Settings
(Optional. If your network environment is not stable, configuring these is recommended.)
|
REGISTER Expiration (m)
|
50 (TLS or TCP)
3 (UDP) |
|
|
Enable Session Timer
|
Yes
|
||
|
Session Expiration (s)
|
600
|
||
|
Min-SE (s)
|
90
|
||
|
Caller Request Timer
|
Yes
|
||
|
Callee Request Timer
|
Yes
|
||
|
UAC Specify Refresher
|
UAC
|
||
|
UAS Specify Refresher
|
UAS
|
||
|
Security Settings->TLS Settings
(Required)
|
Minimum TLS Version
|
1.2 or 1.3
|
|
|
Maximum TLS Version
|
1.2 or 1.3
|
What happens if the CloudUCM plan expires?
When the CloudUCM plan expires, your CloudUCM will stop running and can no longer be used. We will temporarily preserve the data in the cloud server for up to 30 days, during which you can renew your plan. Please be mindful of plan expiration dates and renew at your earliest convenience.
CloudUCM subscription plans are sold by authorized resellers. You can place orders for CloudUCM plans by contacting your Grandstream equipment reseller.
You can sign in to the GDMS to request a trial or contact your Grandstream equipment reseller.
The plan will not take effect until the CloudUCM device has been activated. For example, if you purchase a 1-year Plus plan on April 2nd, 2024, and the device is not activated until May 5th, 2024, the plan will take effect from May 5th, 2024 up to May 5th, 2025.
Yes. Since CloudUCM plans take effect only when the CloudUCM devices are activated, there is no cost or fee for holding plans for unactivated devices. Additionally, this allows for quick responses to customer requirements.
No. Each CloudUCM device is a cloud PBX virtual machine with its own separate storage space for data and files. Sharing a CloudUCM with other customers may result in fatal security and privacy breaches. A channel reseller can purchase a CloudUCM plan for each customer separately based on their deployment requirements such as the number of extensions and concurrent calls (see CloudUCM Plan Specifications).
Yes. You would need to subscribe to the CloudUCM plan for this CloudUCM to continue using it.
You can set up regular storage cleanup through the CloudUCM’s Maintenance page or purchase an add-on plan to expand your storage space.
If the existing number of extensions exceeds the max limit of the new plan, the excess extensions will need to be deleted within 7 days. Otherwise, all extensions will be disabled and cannot be used. If the storage space usage exceeds the max limit of the new plan, several CloudUCM services such as calling, and meetings will become inaccessible until the excess data is cleared.
Yes. Otherwise, you will not be able to use it. You can activate a CloudUCM on GDMS or click the activation link in the CloudUCM activation email. Once activated, the CloudUCM will be running and accessible for management.
There are two ways:
Method 1: Customers can directly enter the CloudUCM’s address into their address bar (e.g. https://test-aaa.m.myucm.cloud:8443) to bring up the CloudUCM management portal.
Method 2: The channel reseller can create and assign a sub-account on GDMS to each customer, and the customer can log into GDMS with those accounts and access their CloudUCM.
Yes, you can use the MAC address of the CloudUCM device and its initial password to add it to GDMS platform for remote management such as syncing extensions to it, remotely accessing the CloudUCM management portal, upgrading firmware, rebooting, resetting to factory, and etc.
Yes. CloudUCM supports register trunks, peer trunks, and WebRTC trunks.
On the PBX Settings -> SIP Settings -> Transmission Protocol page, you can enable all transport protocols needed for your trunks. Only TLS is enabled by default.
Peer Trunk:
a. You need to configure Provider Name, Host Name, and Transport.
b. If the other party is a CloudUCM, the host name would be the domain address of the CloudUCM, and you will need to enable the Domain Connection Mode.
c. If the other party is a UCM63xx with UCMRC services, the host name is the UCMRC domain address of the UCM63xx device with the port number (5061), the transport protocol is TLS, and you will need to enable the Domain Connection Mode.
Register Trunk:
a. You need to configure Provider Name, Host Name, Transport, Registration Number, and Password.
b. If the other party is a CloudUCM, the host name is the domain address of the CloudUCM.
c. If the other party is a UCM63xx with UCMRC services, the host name is the UCMRC domain address of the UCM63xx device with the port number (5061), and the transport protocol is TLS.
CloudUCM supports integrating and deploying with PSTN Analog Trunks and SIP Trunk Providers under private and external networks and supports mutual Trunk registration with other UCMs/CloudUCMs. Please refer to the CloudUCM Deployment Scenario Instructions for more details.
Currently not supported. HA redundancy between CloudUCM and UCM63xx/CloudUCM is in the future plan.
Yes. You can create multiple organizations or sites on the GDMS platform to manage CloudUCM for your customers. For different customers, it is recommended to create multiple organizations and add CloudUCMs for different customers to different organizations for management. Each organization has its own CloudUCM devices, VOIP devices, extensions, tasks, and other data.
If a customer needs different CloudUCMs under one organization to be managed by separate departments, you can create multiple sites under the organization and add CloudUCMs to those different sites for management.
For more details, please refer to the CloudUCM Multi-tenant Management User Guide.
While creating the SIP trunk, the user needs to uncheck the option “Keep Trunk CID”, fills in the “From User” field with the trunk username, and configures the DOD number correctly. Then, the FROM header will be filled with the trunk username, and the Remote-Party-ID header will carry the DOD number simultaneously in the SIP messages.
If the user wants to display the configured DOD number on the callee side, the user needs to uncheck option "Keep Trunk CID" for the SIP trunk.
1. If you need to set your CloudUCM to register to the peer device, you need to set it to a Register SIP Trunk.
2. If the peer device does not have a fixed address, you can select to configure the Account SIP Trunk, and set the peer device to register to the account trunk number in the CloudUCM. After the CloudUCM successfully registers the peer device, the CloudUCM obtains the address of the peer device.
3. For other usage scenarios, it is recommended to configure as Peer SIP Trunk.
1. Please check the Inbound Routes -> Pattern settings and see if the pattern settings have been correctly configured.
2. Please check the Blacklist settings in the Inbound Routes module and see if the inbound call number is on the blacklist.
3. Please check the option “Verify Inbound Requests” in your VoIP Trunks settings. If this option is enabled, the entry request is authenticated. If the peer party does not support the authentication initiated by the registration terminal, please do not check this option.