What Is Cloud Telephony?

Cloud telephony moves your business phone system — numbers, routing, IVR, call handling and analytics — from on-premise PBX hardware to software hosted in the cloud and accessed via the internet. Instead of managing PRI lines and physical exchanges, your team uses web, desktop and mobile apps connected to virtual numbers. For Indian businesses, this also means handling DLT-registered headers and templates, local DIDs and TRAI-compliant routing without owning telecom infrastructure. Unlike a simple VoIP line that provides internet-based calling, cloud telephony provides a full business system: numbers, routing logic, queues and integrations.

VoIP is the underlying technology (voice over IP) that lets voice travel over the internet. Cloud telephony *uses* VoIP but adds business layers: virtual numbers/DIDs, SIP trunks, IVR menus, ACD queues, recordings, analytics and CRM integrations. Think of VoIP as the engine, cloud telephony as the complete vehicle. Many Indian providers describe their offering as cloud telephony to emphasize the full system, not just the VoIP protocol.

UCaaS (Unified Communications as a Service) bundles telephony with chat, video and collaboration (often internal). CCaaS (Contact Center as a Service) bundles telephony with contact-center tools (ACD, dialers, quality monitoring) for customer-facing teams. Cloud telephony is the telephony core; UCaaS/CCaaS are larger suites that *include* cloud telephony. Agilis' homepage positions cloud telephony as the platform that also powers contact-center capabilities — a cloud telephony core with CCaaS features, not a separate UCaaS suite.

At a high level: (1) Your business is assigned virtual or DID numbers (including local city codes or toll-free) via a provider's SIP trunk. (2) Inbound calls hit a cloud platform where IVR menus, routing rules and ACD queues decide the destination — this is SIP signaling (INVITE) to your media server or agent app. (3) Outbound calls, SMS and WhatsApp are triggered via APIs or campaign tools, routed through carrier and DLT-verified paths. (4) Call events, recordings and delivery receipts flow back to dashboards and CRMs via webhooks/API. All of this runs over SIP (Session Initiation Protocol) and RTP media, typically G.711 PCMA/PCMU for Indian carrier compatibility, not copper PRI.

Inbound: Customer dials +91 DID → Indian PSTN (Jio/Airtel/BSNL) → ITSP/DID provider SIP gateway → your cloud platform (IVR) → ACD → agent app (WebRTC) → CRM screen-pop. Outbound: Agent clicks call in CRM → API to cloud platform → SIP INVITE via trunk → PSTN → customer phone. Media is RTP/SRTP. IP whitelisting and static IPs are common for SIP trunk security (Exotel vSIP requires static IP, TLS on 443).

- Virtual / DID numbers and SIP trunks (static IP, TLS, G.711) - IVR and call-flow builder (multi-level, DTMF + speech) - Automatic Call Distribution (ACD) and queues - Dialers (predictive, progressive, preview) for outbound - Bulk messaging (SMS, voice broadcast/OBD, WhatsApp Business) - CRM integrations and REST APIs/webhooks - Analytics, call recordings, reporting and DIDs across 100+ Indian cities where providers support

| Aspect | Traditional PBX (PRI) | Cloud Telephony | | CapEx | High (PBX hardware, PRI lines) | Low (pay per user/minute, no hardware) | | Scaling | Hardware per channel | Add users/numbers in dashboard | | Remote work | Limited | Web/mobile apps, anywhere | | Integrations | Limited | CRM, API, webhooks native | | DLT/TRAI | Manual | Provider handles header/template and 140-series where applicable | | Maintenance | On-premise engineer | Provider-managed | | Trade-off | Dedicated PRI lines | Depends on internet quality and provider/carrier availability |

- Inbound support: IVR → ACD → best agent, with CRM screen-pop and recording. - Outbound sales: predictive dialer + click-to-call + automated follow-up SMS via DLT template. - Bulk campaigns: SMS OTP (transactional, 30-min post-transaction per TCCCPR 2025), voice reminders (OBD via 140 series), WhatsApp updates (template-approved). - Multi-location: geographic routing across offices or remote teams, time-zone rules.

Cloud platforms scale from 5 to 500+ seats without new exchanges; agents work via browser/WebRTC, supervisors monitor via live dashboards (call flow, agent performance). For Indian teams, this enables hybrid/remote without PRI. Concurrent call capacity depends on trunk channels (e.g., 50–100 channels for mid-size) and provider rate limits (Exotel vSIP default 200 CPM per trunk).

Cloud telephony requires reliable internet (MPLS/VPN for BFSI where needed, per Exotel docs) and depends on carrier/provider availability. Unlike PRI, internet or provider outages affect calls. Mitigations: multi-telco failover, geo-redundant trunks (Mumbai + Bangalore DCs), and provider 100% connectivity SLA where offered — but no provider guarantees zero downtime.

Typical controls: TLS/SRTP for SIP media, IP whitelisting, RBAC, encrypted recordings. For businesses handling personal data, DPDP Act 2023 requires purpose limitation, consent, and security safeguards (Sec. 8(5)); TRAI TCCCPR requires DLT consent handling. Do not claim Agilis is TRAI-approved or DOT-licensed unless verified — use 'carrier-grade' as hedged positioning.

India requires Principal Entity registration on DLT for commercial SMS, header/template approval, consent/preference scrubbing, and 140-series for promotional voice via auto-dialer. Local DIDs across 100+ cities, 5–7 day number porting, and INR billing are India-specific operational realities. Providers like Exotel/Ozonetel note TRAI/DoT compliance, VNO operation, and lawful interception readiness — verify your provider's status.

Common models in India: per-agent per month (₹999–2,500) + per-minute (₹0.30–1.20), or per-channel unlimited, or pay-per-minute SIP trunk (e.g., Rs 0.50/min at Edesy). Cloud telephony is often 50–60% cheaper than PBX over 3 years due to no hardware. For Agilis, pricing is prepaid lifetime/bulk per PricingSection, not per-agent SaaS — business confirmation required for exact model.

Checklist: (1) DLT PE/header/template status, (2) local DID needs, (3) IVR depth and multilingual (Hindi/English/regional), (4) ACD skills, (5) dialer modes needed, (6) CRM integration method (native vs API), (7) recording retention, (8) internet/MPLS readiness, (9) porting timeline. Ask for a demonstration with your actual call flow, not slides.

If you require air-gapped on-premise control for RBI-regulated workloads requiring data residency behind your firewall (per EnableX on-premise for RBI/SAMA), or if you have unreliable internet without MPLS, evaluate hybrid/on-premise. Small teams with very low volume may find simple virtual numbers sufficient.