Microsoft Teams migration
Keep your SIP intercoms, IP paging and cameras
CyberGate bridges your existing SIP devices to Microsoft Teams via Azure. No on-premise SBC, no extra hardware on site, no separate end-user app to deploy.
How the bridge works
Your devices, Azure, Teams
one encrypted SIP-TLS path
Devices talk to CyberGate in Azure over outbound SIP-TLS only. From there, calls land in your existing Teams tenant natively.
CyberGate runs as a SaaS in Microsoft Azure. Your SIP devices establish an outbound, encrypted SIP-TLS session to CyberGate in your tenant's region. No inbound firewall rules, no NAT traversal workarounds, no on-premise Session Border Controller.
On the Teams side, calls reach your users in the native Microsoft Teams client they already use, on desktop, on mobile, or on a Teams Desk Phone. There is no extra app to install, no second identity to manage. Calls follow your Teams call-routing exactly as a regular Teams call would.
CyberGate is hosted in Azure and operated under ISO 27001. Access management runs through the same Microsoft account your team already uses for Teams.
From signup to first call
Four steps to
production
Scope the work order in advance. Every step is one team's responsibility and links to the page that closes it.
Step 1: Check device compatibility
Start with our compatibility list to confirm your SIP intercoms, IP paging system, or IP cameras are supported. If your device isn't listed, talk to us before quoting the customer.
Step 2: Subscribe via Azure Marketplace
Purchase CyberGate through Microsoft AppSource or Azure Marketplace. Billing goes through your customer's existing Microsoft agreement, so there is no separate procurement cycle.
Step 3: Activate in the CyberGate Management Portal
Sign in to the Management Portal with a Microsoft account that belongs to the Teams tenant. Activate the subscription and add the devices you want to connect.
Step 4: Point your SIP devices to CyberGate
Configure each device's SIP credentials following our device configuration manual. Once registered, the device calls into Teams natively, and Teams users can call the device.
Replacing a PBX intercom that dials mobile numbers
Most intercoms we take over were wired into a PBX that rang a list of mobile numbers one after the other. Facility manager first, then a colleague, then the security desk. Whoever picked up dialled a code on the keypad and the door opened. CyberGate does the same thing, and nobody has to change how they answer.
| Old PBX setup | CyberGate equivalent |
|---|---|
| Intercom rings mobile 1, then 2, then 3 | Sequential call group, participants in the order you set, with a ring duration of 5 to 30 seconds each |
| Answer on the mobile | Answer in the Teams app on that same mobile |
| Press a code on the keypad to open the door | Press the door-open button in the CyberGate app during the call |
| Nobody answers, forward to an external number | Works, but audio only. The door opens over DTMF, not with the button |
Forwarding is the one flow that changes. A call that leaves your Teams tenant for an external number loses the video and loses the door-open button in the CyberGate app. DTMF still works, so whoever picks up on that number can open the door with a code. Keep every participant inside the tenant and you keep both.
Step-by-step setup is in the CyberGate quick start manual. For what else belongs on the scope list before a Teams Phone cutover, read PBX out, Teams in.
Why integrators pick CyberGate
What makes this
sellable to IT
Four differentiators that matter when you're defending this choice to a customer's IT and security team.
Live two-way audio and video
The only solution in market that delivers bidirectional audio and live video between SIP devices and the Teams user, so visitors and operators see each other in real time.
No on-premise SBC
No Session Border Controller to size, rack, license, patch, or replace. The bridge runs as a SaaS in Azure, so the customer's site footprint stays at zero.
Native Microsoft Teams client
Calls land in the Teams app your users already run. No separate end-user app to deploy, no second login, no extra training, and no second tool for IT to support.
Hosted in Azure, ISO 27001
CyberGate runs in Microsoft Azure under ISO 27001-certified operations. Identity goes through the customer's existing Microsoft account, so there are no separate credentials to store, rotate, or audit.
When you're knee-deep in a Teams Voice migration, the last thing you want to deal with is a tedious door acces integation. CyberGate's setup was straightforward, self-explanatory, and fast! Licensing is equally easy. And the support team has been lightning-quick to anwser any questions.
Few options for Teams and only one did video
We were looking for a way to get a video intercom that would work with Microsoft teams, and there seemed to be very few options on this front. Then we found CyberGate, which delivered exactly what we needed, an the pre an post- sales support has been brilliant.
- Connected a standard SIP intercom to Microsoft Teams, the bridge that made it possible when no native-Teams option existed
- Delivered exactly what they needed: live video between the door and the Teams user
- Strong pre- and post-sales support throughout
The CyberGate is an excellent solution to connect our intercoms to Teams. A great enables, which more than satisfied our customers!
Via our CyberGate SIP to Teams application you can now connect your Robin SIP audio- or Robin SIP video door intercom to your Microsoft Teams Tenant.
- Teams Users can answer incoming calls from the Robin (video) door station – with 2-way audio and live video – on their Teams desktop client, Teams compatible desk phone or Teams Smartphone app and open the door for visitors.
- The new multi-ring feature in CyberGate enables the Teams Tenant to configure a group of Teams Users as destination, so that multiple Teams User will be notified simultaneously if someone rings the door station, and the 1st responder will be connected to the visitor.
Integrator questions
Quick answers
FAQ
My device isn't on the compatibility list. What now?
Talk to us before you commit anything to the customer. We test new devices regularly and may have field experience with yours; if not, we'll work with you to verify it.
What SIP transport and codecs does CyberGate support?
CyberGate supports SIP over UDP (port 5060), TCP (port 5060), and TLS (port 5061).
What firewall rules do we need to open?
Only outbound traffic from the device network to CyberGate in Azure is required:
- SIP signalling: UDP/TCP 5060 and TLS 5061 to cybergate.cybertwice.com
- RTP audio/video: UDP 30000–30191 to cybergate.cybertwice.com
No inbound firewall rules and no NAT traversal configuration are required, because devices initiate the session, not the cloud. The WAN IP(s) the devices register from must be added under Network settings in the CyberGate Management Portal.
Can a single tenant connect devices across multiple sites?
Yes. A single CyberGate subscription supports devices across multiple physical sites within the same Microsoft tenant. All devices register against the same tenant, regardless of which site they sit in.
How does call-routing to a Teams user or call queue work?
A device calls a destination address that resolves to either a single Teams user (user@yourtenant.com) or a CyberGate Call Group (groupname@cybergate.cybertwice.com).
Routing to a Microsoft Teams Call Queue is not supported, because the Microsoft APIs available to CyberGate do not support calls to queues from third-party integrators. CyberGate provides three call group types as an alternative, configured in the Management Portal under Basic > Call Group:
- Multi Ring: up to 15 Teams users ring simultaneously. First to answer takes the call.
- Sequential: up to 15 participants (Teams users or Multi Ring groups) are called one after the other, with a configurable ring duration per entry (5–30 seconds).
- Meeting: the device starts a pre-configured Teams meeting and invites everyone to join, so several Teams users see and hear the device at the same time.
See the Management Portal docs for configuration details.
How is billing structured, per device or per tenant?
CyberGate is sold as three separate Microsoft Marketplace offers, one for each hardware category:
- CyberGate for IP Video Intercoms with Teams
- CyberGate for IP Cameras with Teams
- CyberGate for IP Paging with Teams
Each offer is a per-device subscription purchased through Microsoft Marketplace. Within a single offer, one subscription covers multiple devices of that type ("number of users" in Marketplace = number of devices), and the device count can be increased or decreased at any time in the CyberGate Management Portal. All billing terms include a 30-day free trial. Connecting devices of different types (e.g. intercoms and cameras) requires the corresponding subscriptions.
For current pricing tiers, see the CyberGate pricing page. Setup details are in the Purchase and Setup docs.
Ready to connect your first device?
Spin up a proof-of-concept tenant, talk to our engineering team about a specific device, or request a quote. Whichever fits your stage.
