Grandstream UCM6302 CloudUCM Deployment Scenarios User Guide

: June 1, 2024
: GRANDSTREAM

Table of Contents

Grandstream UCM6302 CloudUCM Deployment Scenarios
Product Information
Product Usage Instructions
FAQ
Introduction
CloudUCM Scenario
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

Grandstream UCM6302 CloudUCM Deployment Scenarios

Product Information

Specifications:

Product Name: CloudUCM
Manufacturer: Grandstream
Deployment Scenarios: 5 different scenarios outlined
Compatibility: Works with Grandstream PBX solutions, analog telephony adapters, and ITSPs

Product Usage Instructions

Scenario 1:

This scenario involves deploying CloudUCM with endpoints behind a NAT router. Follow these steps:

Deploy CloudUCM with FXO gateway behind the firewall.
Peer the CloudUCM with the FXO gateway using a SIP trunk.
Establish calls through the PSTN line via the SIP trunk and FXO gateway.

Scenario 2:

In this scenario, CloudUCM is peered with an ITSP via a SIPtrunk. To set up:

Peer CloudUCM with the SIP trunk provider (ITSP).
Deploy local SIP endpoints behind a NAT router.
Deploy remote SIP endpoints in home offices and mobile devices.

Scenario 3:

Deploy a UCM6302 device within the local network and peer it through a SIP trunk to the ITSP. Steps:

Peer CloudUCM with the local UCM6302 device.
Register extensions on CloudUCM to establish calls to local SIP endpoints on UCM6302.

Scenario 4:

This scenario involves registering local and remote SIP endpoints in CloudUCM and peering it with ITSP and an analog gateway. Follow:

Peer CloudUCM with ITSP and analog gateway using SIP trunk.
Establish calls through different trunks of CloudUCM.

Scenario 5:

This scenario divides topology into Global Work Area and Exclusive Private Work Area. Steps:

Deploy remote and local SIP endpoints on CloudUCM in Global Work Area.
Connect UCM6300 device to ITSP’s VoIP trunk in Exclusive Private Work Area.
Establish calls between Global and Exclusive Private Work Areas through the SIP trunk.

FAQ

Q: Can CloudUCM be deployed without a SIP trunk?
- A: Yes, CloudUCM can be deployed without a SIP trunk in scenarios where direct peering is possible with other telephony solutions.
Q: How many deployment scenarios are outlined for CloudUCM?
- A: There are a total of 5 deployment scenarios outlined for CloudUCM in the user manual.

Introduction

In this guide, we will outline some of the scenarios in which the CloudUCM is deployed with other Grandstream telephony solutions. This includes deploying the CloudUCM with a Grandstream PBX solution, with an analog telephony adapter or peered directly to an ITSP using a SIP trunk.

CloudUCM Scenario

CloudUCM Scenario 1

In the first scenario, a CloudUCM is deployed with endpoints located in an office behind a NAT router, and remote users which are mobile. In the office, behind the firewall, an FXO gateway has been deployed, which is peered with the CloudUCM using a SIP trunk. $Grandstream -UCM6302 -CloudUCM -Deployment -Scenarios-fig $1$$

This type of deployment allows the local SIP endpoints and the remote SIP endpoints to be established through the PSTN line. The calls would initially go through the SIP trunk which peers the CloudUCM and the HT8XX analog adapter, then it would go outwards to the PSTN through the FXO port of the adapter.

CloudUCM Scenario 2

In the second scenario, we have a SIP trunk peered between the CloudUCM and a SIP provider (ITSP). We have local SIP endpoints which are deployed in an office behind a NAT router. We also have mobile Remote SIP Endpoints which are deployed in home offices and mobile devices. A SIP trunk peered between the CloudUCM and the SIP trunk provider (ITSP).

This deployment allows the local and remote SIP endpoints to establish calls through the CloudUCM and reach into the SIP trunk provided by the ITSP which is peered with the CloudUCM

CloudUCM Scenario 3

In this deployment example, a UCM6302 device is deployed within the local network and is peered through a SIP trunk to the ITSP. The CloudUCM, in this case, can be peered with the local UCM6302 device and the extensions which are registered on the CloudUCM can establish calls to the local SIP endpoints which are registered on the local UCM6302 device

CloudUCM Scenario 4

In this scenario, the local and remote SIP endpoints are registered in the CloudUCM. The CloudUCM is peered using a SIP trunk with the ITSP. The CloudUCM is peered to the analog gateway. Both remote and local SIP endpoints can establish calls through the different trunks of the CloudUCM

CloudUCM Scenario 5

Our topology is divided into two general areas.

Global Work Area: In this area, remote and local SIP endpoints are deployed and registered on the CloudUCM. A SIP trunk is provided by ITSP on the Exclusive Private Work Area, which has been peered with the CloudUCM.
Exclusive Private Work Area: In this area, the UCM6300 device is connected directly to the ITSP’s VoIP trunk, and endpoints are registered in the UCM6300 device.

The remote SIP endpoint and local SIP endpoints in the Global Work Area can establish calls to the SIP endpoints on the Exclusive Private Work Area through the SIP trunk which is established between the CloudUCM and the ITSP.