Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
•
IT Security NachrichtenBetrüger phishen mit vermeintlicher Reisebestätigung - IT-Markt(24.09.2026 um 23:41 Uhr)
••
Sicherheitslücken (CVE)IT Security News Daily Summary 2026-09-24(24.09.2026 um 23:55 Uhr)
•
Sicherheitslücken (CVE)IT Security News Roundup: 2026-09-24(24.09.2026 um 23:57 Uhr)
•
Sicherheitslücken (CVE)IT Security News Hourly Summary 2026-09-25 00h : 9 posts(25.09.2026 um 00:00 Uhr)
•••
IT NachrichtenMicrosoft puts Brad Smith in charge of communications(25.09.2026 um 00:08 Uhr)
•••
IT Security NachrichtenBetrüger phishen mit vermeintlicher Reisebestätigung - IT-Markt(24.09.2026 um 23:41 Uhr)
••
Sicherheitslücken (CVE)IT Security News Daily Summary 2026-09-24(24.09.2026 um 23:55 Uhr)
•
Sicherheitslücken (CVE)IT Security News Roundup: 2026-09-24(24.09.2026 um 23:57 Uhr)
•
Sicherheitslücken (CVE)IT Security News Hourly Summary 2026-09-25 00h : 9 posts(25.09.2026 um 00:00 Uhr)
•••
IT NachrichtenMicrosoft puts Brad Smith in charge of communications(25.09.2026 um 00:08 Uhr)
••
Intelligence View
⚡ tsecurity.de Intelligence

How I Got Caller ID Working in Canada Using RingCentral, Twilio, and ElevenLabs

Background ElevenLabs is “the most realistic voice AI platform” (their words), and it really is fantastic. I have been using it to automatically call people, leave messages, and run outbound phone workflows. Since the business already had…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!




Background



ElevenLabs is “the most realistic voice AI platform” (their words), and it really is fantastic. I have been using it to automatically call people, leave messages, and run outbound phone workflows. Since the business already had a Twilio number, I used ElevenLabs' Twilio starter kit for outbound calling.



The app worked beautifully, except for one big problem.






The Problem



Caller ID simply did not work.



Even though the Twilio number had a name set, calls were coming through as just the phone number. And let’s be honest, nobody answers mystery numbers these days 😅.



This was killing our answer rate because the agent was leaving tons of voicemails since people did not know who was calling.






Why Caller ID in Canada Is Weird



In the United States, caller ID is driven by the CNAM database.



Canada does not have this.



Instead, Canadian carriers such as Telus, Bell, and Rogers control caller name lookup themselves. That means:




  • CNAM registration in Twilio does nothing

  • Caller ID must originate from a number registered with a Canadian carrier

  • Twilio's Branded Calling pilot is mostly focused on the US (I applied and was rejected because our account was too small)



So the Canadian telecom monopoly strikes again 😔.






Exploring Solutions (and Hitting Dead Ends)






1. Twilio Fix Attempts



I tried everything:




  • Setting CNAM fields

  • Testing different API configurations

  • Applying for Branded Calling

  • Double checking every setting in the Twilio console



Nothing worked.






2. SIP Trunking: Initial Hope



I started digging into SIP trunking.




SIP trunking is an internet based replacement for traditional phone lines (PSTN or ISDN). It lets businesses make and receive calls over IP instead of physical lines.




ElevenLabs supports SIP trunking, so this seemed promising.



However, caller ID would still depend on having a Canadian registered number on the SIP provider. That meant SIP alone was not a solution.






3. RingCentral Plus Telus: Another Possible Path



We did have a Telus registered number through RingCentral. Telus Business Connect is essentially RingCentral under the hood.



RingCentral also has a great API and supports SIP trunking.



I set up:




  • SIP trunking in ElevenLabs

  • A SIP enabled extension in RingCentral



Then I hit another blocker.


RingCentral only allows SIP connections through their internal network. They do not allow external services like ElevenLabs to connect.



Another dead end.






The Shower Thought



While washing my hair, I suddenly thought:




What if I place the call using RingCentral, which gives proper caller ID, and then transfer or bridge the call to Twilio or ElevenLabs afterward?




I tried it.



I could place the call through RingCentral and the caller ID worked.



But the audio routing did not cooperate.




  • RingCentral greetings still played

  • The ElevenLabs audio did not come through

  • Conference or bridge attempts did not solve it



Close, but still not usable.






The Actual Solution



The answer turned out to be much simpler than expected.






Let RingCentral call Twilio directly.



Here is the flow:




  1. Set the RingCentral (Telus) number to forward all calls to a Twilio number.


    Caller ID stays intact because RingCentral is the origin of the call.


  2. Configure the Twilio number to trigger a webhook on inbound calls.


    The webhook points to your app with the ElevenLabs agent.


  3. Handle the call in your app like any normal inbound Twilio call.


    ElevenLabs takes over from there.







Why This Works




  • The call originates from a Canadian carrier, which preserves caller ID

  • Twilio only handles the call after it is already ringing, so CNAM is not needed

  • The ElevenLabs agent behaves exactly like a normal inbound Twilio call

  • No SIP trunking or bridging complexity is required



The first time I answered my phone and saw the company name and heard the ElevenLabs voice agent start speaking, I was stunned. It finally worked.






The Results



You can see in this screenshot people are picking up more calls because of the caller ID!








TL;DR




  1. Forward your RingCentral (Telus) number to your Twilio number

  2. Configure Twilio to fire a webhook on inbound calls

  3. Handle the call in your app using your ElevenLabs logic

SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - How I Got Caller ID Working in Canada Using RingCentral, Twilio, and ElevenLabs
id: 9274a052-b731-4189-85fa-e72b8311dfc1
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-25"
        description = "YARA Signature for "
    strings:
        $str = "How I Got Caller ID Working in" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("How I Got Caller ID Working in Canada Us")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*How I Got Caller ID Working in Canada Us*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "How I Got Caller ID Working in Canada Us"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich How I Got Caller ID Working in Canada Us.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten How I Got Caller ID Working in Canada Using RingCentral, Twilio, and ElevenLabs

Thematisch verwandte Begriffe: Caller, Working, Canada, Using · 6 Treffer

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-87722 | Uncontrolled Resource Consumption (CWE-400 / CWE-1333) in regex search q…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel • Rechts: nächster Artikel • unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel TTP ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...
↗ Original-Quelle