Telecom and business communications

Manage communications.
Expand possibilities.

Routing, billing, cloud PBX, messaging and voice AI. We develop and integrate solutions for telecom operators and businesses.

Discuss a projectImplementation scenarios
15+ years in telecomUkraine · EU · USAWork under NDA
Carriers SIP trunks & interconnect
Asterisk IP PBX, IVR & call queues
Messaging SMS, RCS & messaging APIs
AI voice agents Call transfer to a live agent
CRM, BPM & ERP APIs & data synchronization
Billing Call & AI usage rating
Customer portal Numbers, users & invoices
Our focus

Who we help

We develop communications systems for providers, enterprises, public authorities and other public or private organisations.

Operators, providers, resellers

Telecom service growth

Interconnect and routing, real-time charging, wholesale settlement, BSS/OSS integration, fraud control and migration of legacy switches.

Telecom services
Enterprises, institutions, public authorities

Communications for organisations

Cloud PBX, Microsoft Teams calling, numbers and hotlines, one inbox for calls and messages, AI reception and billing per tenant.

Communications for organisations
From call to invoice

From calls to charges

uthorisation, routing, usage records and rating work as one chain. This is the core we build for providers that bill voice and AI usage.

  1. 01

    Customer call

    Your customer places a call over SIP or WebRTC.

  2. 02
    Account
    Balance or credit
    Destination allowed

    Authorise

    Account, balance or credit limit and the destination are checked first.

  3. 03
    Rate per minute
    Carrier A
    Carrier BEconomy
    Carrier CFailover

    Route selection

    Carrier rates for the destination are compared. The cheapest route connects; the next one waits as failover.

  4. 04
    Answered
    Connected time
    Customer
    AI agent, if used

    Record usage

    Connected time, and AI usage when an agent joins, land on the right customer.

  5. 05
    Telephonyconnected seconds
    AI agentminutes or tokens
    Tariffyour rules
    Added to invoice

    Rate & charge

    Your tariff prices the call. The balance is updated and the charge joins the period invoice.

How we implement billing and routing
Integration

Coordinated data exchange

We connect your Asterisk, CRM, billing and other systems through APIs and events. The rules and scope of integration follow your workflow.

Separate integrations

An example of fragmented workflows: manual work, duplicates and failed exchanges.

  1. Inconsistent formats

    CDRs need manual conversion.

  2. Unmatched customer

    Identifiers differ between systems.

  3. Duplicate records

    The same event is processed again.

  4. Delayed reports

    BI waits for a manual export.

  5. Delivery failure

    Someone must resend the failed event.

  6. Manual reconciliation

    Carrier and billing records are checked in spreadsheets.

With DooxSwitch

We implement validation, automated processing and delivery controls for these same systems.

  1. Standardised data

    We validate and convert CDRs.

  2. CRM matching

    We link records using agreed identifiers.

  3. Duplicate protection

    Repeated events are processed only once.

  4. BI updates

    Data is forwarded without manual exports.

  5. Delivery controls

    Queues retain events; retries restore delivery.

  6. Prepared reconciliation

    We match records and flag discrepancies.

Lines represent APIs, events and CDR files (call detail records). Movement illustrates data processing, not network speed. Voice traffic is not shown.

Deployment example

Call accounting

  1. Receive CDRs

    After a call ends, Asterisk supplies records of its participants, duration and outcome.

  2. Match records

    Records are linked to the account and CRM using agreed identifiers. Uncertain matches are flagged for review.

  3. Forward data

    Billing receives validated records for rating, while BI receives them for reporting.

Handling service failures

The central node represents a logical integration layer. We design component redundancy, persistent event queues, retries and protection against duplicate processing for the project. Retention periods, retry limits and error alerts are agreed separately.

Call behaviour during an outage is defined separately. It depends on whether the PBX needs external services for authorisation and routing. Failover is tested during deployment.

Explore the architecture
What we implement

Current services

Each service is scoped for your network, contracts and market rules.

Voice routing and interconnect

SIP trunks, least-cost routing, failover and number management on Asterisk or Kamailio.

Charging and billing

Real-time prepaid and postpaid charging, wholesale settlement, subscriber invoices and billing for AI usage.

Voice AI agents

AI reception and support agents on your telephony. They say they are AI, use approved tools and pass calls to people.

Messaging

SMS, RCS Business Messaging, WhatsApp and Viber through official APIs, with consent records and delivery tracking.

Fraud control and compliance

Rules against IRSF, Wangiri and SIM-box traffic. STIR/SHAKEN and 10DLC for the US, GDPR for the EU.

Monitoring and support

PBX migration, SLA-based support, monitoring, backups and recovery. Cloud cost and licence control.

Explore support

Communications for organisations

Microsoft Teams, Cisco, 3CX and contact centres. Calls, email, messaging and CRM.

For business

Interaction workflows

Scriptum, Power Automate and CRM / ERP integration. From a call or message to a ticket and approval.

Platforms and integrations

Cloud workspaces

Azure Virtual Desktop and Windows 365 for agents and remote teams. Softphone, CRM and managed access.

Business communications
Video communications

Video, AI and billing

We implement video meetings with AI processing, CRM integration and cost tracking. We integrate digital avatars — AI representatives that hold video conversations using your knowledge base and hand complex questions over to a person.

For formal proceedings, we deploy the Megapolis video meeting solution.

Explore capabilities
Video
Teams, tenants, customers
AI
Transcription, summaries, tasks
Digital avatars
AI representatives in video conversations
Billing
Usage, limits, invoices
Since 2010

15+ years in telecom

DooxSwitch is the telecom practice of Intecracy Ukraine, a member of Intecracy Group. We have built and supported VoIP billing, softswitch and contact-centre software since 2010.

Our clients work with us under strict NDAs. That is why this site shows implementation scenarios instead of named case studies.

About usImplementation scenarios
Company
Intecracy Ukraine LLC
Group
Intecracy Group
Markets
Ukraine, European Union, United States
Confidentiality
Every project under NDA
Implementation scenarios

Deployment scenarios

We work under strict NDAs, so we do not name clients or publish their figures. These scenarios are eneralised from our practice since 2010: the situation, what we implement and what changes.

Wholesale carrier

Rates and settlements

Situation

Supplier rate decks arrive by email in different formats. Disputes over traffic are checked by hand in spreadsheets.

Implementation

  • Rate-deck import with validation and effective dates
  • CDR mediation for every partner
  • Automatic reconciliation with supplier invoices
  • A dispute workflow with the records attached

What changes

Margin per destination is visible without manual work, and disputes start from data both sides can check.

Internet provider

Subscriber telephony

Situation

A regional provider sells internet access and wants to offer telephony without a second billing system.

Implementation

  • A SIP service on Asterisk with number allocation
  • Voice usage passed into the existing billing through an API
  • Call history and settings in the customer portal

What changes

Customers get one account and one invoice for internet and voice.

Business centre

Shared tenant reception

Situation

A building hosts dozens of companies. One reception answers calls, and every tenant has its own contract.

Implementation

  • A multi-tenant PBX with numbers per company
  • A reception workspace that answers in each tenant’s name
  • Statements per tenant for calls, numbers and messages

What changes

Tenants get their own service, and the building operator charges each company for what it used.

Contact centre

AI with human handoff

Situation

Routine calls create queues at peak hours, while complex requests wait.

Implementation

  • A voice agent on Asterisk that says it is an AI
  • Booking and CRM tools with confirmation steps
  • Handoff with the reason and transcript
  • Telecom and AI cost recorded for each call

What changes

Operators spend their time on calls that need a person, and the cost of each resolved request is visible.

Legacy Asterisk

Phased migration

Situation

An old Asterisk with chan_sip, a hand-written dial plan and an unsupported operating system carries live traffic.

Implementation

  • An inventory of the dial plan, trunks and integrations
  • Migration to PJSIP on the current Asterisk LTS
  • A parallel run, then cutover by trunk or by tenant

What changes

The system runs on supported versions, the configuration is documented, and every step can be rolled back.

US VoIP provider

US telecom compliance

Situation

A provider that sends calls into US networks must sign them, and its business texting must be registered.

Implementation

  • STIR/SHAKEN signing and verification through a certificate provider
  • Robocall mitigation procedures and records
  • 10DLC brand and campaign registration through a messaging partner
  • Consent records for messaging

What changes

Calls carry an attestation level, messaging campaigns are registered, and consent can be shown on request.

We work under strict NDAs. Client names, figures and identifying details are never published. The scenarios above describe typical situations; your project is scoped on its own facts.

Questions

Common questions

Short answers to what clients usually ask first.

Keep Asterisk?

Yes. Most projects keep Asterisk as the telephony core. We add routing, billing, voice AI or integrations around it and check version compatibility during the audit.

Ready-made platform?

No. We implement and integrate software for your service, on your infrastructure or in the cloud you choose. Open-source components and your current systems are reused where they fit.

Which markets?

Ukraine, the European Union and the United States. Rules differ: GDPR in the EU, STIR/SHAKEN and 10DLC in the US. We include the ones that apply in the project scope.

Getting started?

Send a short description of your service and systems. We start with an audit and agree a first stage you can test before a wider rollout.

Describe your task

What you run today, what should change and by when. We reply with questions or a first proposal.

Contact us