The most common question in a first conversation is not which CRM we connect. It is: “Does this work with our phone provider?”
The answer is short and sounds too easy: the provider does not appear in our path at all.
Where the tile listens
Haus iT Caller ID is an app inside the Webex client — in the sidebar, next to the conversation. It listens to a single event the client itself reports: `sidebar:callStateChanged`. It says that a call is starting, and gives the other party’s number.
- The phone rings Incoming call
- Webex reports the number
- Haus iT Caller ID standardises it
- Your CRM or ERP looks it up Your customer data stays here
- The sidebar names the caller
Before that event lies the whole world of telephony: lines, number ranges, SIP trunks, contracts. After it lies our work. The two never touch.
Four ways to get Webex Calling
Webex Calling is the phone system. The route to the public network is not always supplied by Cisco. Cisco itself distinguishes four options:
- Cisco Calling Plans — Cisco is the carrier itself.
- Cloud Connected PSTN — a Cisco-certified provider; Cisco speaks of service in “over 65 countries”.
- Local Gateway — in Cisco’s own words this lets you use “virtually any PSTN provider around the world”.
- Webex for Placetel — a separate product built on Webex.
The third point is the decisive one. If virtually any provider can be connected, there cannot be a complete list – that is not a gap in the research, it is how the product is built.
For Local Gateway, Cisco names the European countries one by one, from Albania to Ukraine, and puts the reach at over 190 markets worldwide. In Europe, the question „is Webex Calling available in my country?" therefore has only one answer: yes.
The list nobody can find
The second route is different. The certified providers are a finite list per country – it just is not published anywhere.
Checked on 23 September 2026: Cisco's availability page names countries, not providers. The old community article about the „Global Availability Tool" now redirects to that same page – the tool its instructions describe no longer exists in that form. And the detailed document is linked by Cisco itself with the note „Partner access required".
To see the names you need access to Control Hub. They are under Services → PSTN & Routing → PSTN providers, with a filter by country. That is the only route we found.
What is actually in there
We looked – on 23 September 2026, from an organisation in the European home region. Unfiltered: 62 providers in three groups. One preferred, 45 certified, 16 without that certification.
Filtered by country it becomes a manageable choice:
| Country | Providers | of those certified | Only here |
|---|---|---|---|
| Germany | 19 | 14 | Deutsche Telekom |
| Austria | 17 | 12 | no Cisco Calling Plans |
| Switzerland | 19 | 14 | Swisscom, Sunrise |
| Spain | 18 | 13 | Gamma |
| France | 20 | 13 | Alphalink, Phenix |
What is telling is not the totals but the differences. Austria has neither Cisco Calling Plans nor Deutsche Telekom – both exist one border further north. Someone buying in Vienna cannot buy what they would in Paderborn.
Gamma is in Spain but not in Austria – although Gamma has owned Placetel since 2024. Owning a company and serving a country are two different things.
Certified does not mean available
Two groups sit side by side in the same list: certified providers and ones that are not. Looking at the name alone, you cannot tell.
And „certified" says nothing about your country. Symbio, for instance, is a certified Cisco partner – covering Australia, New Zealand and Singapore. For a line in Hamburg that is no help. It is the same false step as „has an API" and „can search by phone number".
Where we stand ourselves
For completeness, because we get asked: we are a Placetel Gold Partner – and Placetel is on that list as a certified provider. We are not a Cisco-certified carrier ourselves; that is the role of Swisscom, Telekom and Telefónica. Haus iT delivers Webex Calling as a Placetel partner – in Germany, in Austria and, as CASA IT, in Spain.
For caller recognition none of this matters. It hangs on the client, not on the provider – which is why this sits at the bottom and not at the top.
The countries where Cisco is the carrier
From Cisco’s Calling Plan help page, dated 5 August 2026, verbatim: Belgium, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Lithuania, Luxembourg, Netherlands, Poland, Sweden, Switzerland, United Kingdom — plus the United States, Canada, Australia and New Zealand.
Austria and Spain are not on it. That does not mean Webex Calling is unavailable there — it means Cisco does not sell the line itself. The route runs through a certified provider or a Local Gateway. Nothing changes for caller recognition.
Putting it to the test: 24 languages
Our portal speaks 24 languages. We held the corresponding countries against Cisco's official list of where Webex may be sold at all – last checked on 23 September 2026.
The one missing entry is Russia. Cisco’s list names Albania, Georgia, Moldova, Turkey and Ukraine — not Russia. We cannot sell there because Cisco cannot.
The Russian interface stays all the same. Russian is not the language of a country but of people — in Riga, in Kyiv, in Berlin. Someone working in Germany whose first language is Russian should be able to read the tile in Russian.
The best proof arrived unasked
Our own platform runs on Placetel. Its ownership in short: in 2013 BroadSoft bought Placetel. In 2018 Cisco bought BroadSoft — Placetel became Cisco. In 2024 Cisco sold Placetel to Gamma Communications, a British company.
So the carrier beneath our product changed owner. Not one line of the caller recognition had to change. Anyone who had tied recognition to a carrier feature would have had a project on their hands.
Where it does not work
This promise has a limit, and it costs us business: the call must reach the Webex client.
If you use Webex only for meetings and messaging while running a separate phone system, the event never fires — the phone rings on a device the client knows nothing about. TAPI exists for that case, with different prerequisites: a driver, a machine, a firewall that cooperates.
That is also the difference from classic CTI. A link to a particular phone system has to be built per system and maintained per version. An app in the Webex client is built once.
The question that counts instead
Not “which carriers do you work with?” but “does it ring in the Webex client?” If it does, the telephony side is settled and exactly one task remains — connecting your CRM to the portal. That is the side where it gets interesting.
Frequently asked questions
Does caller recognition work with my phone provider?
Yes. Haus iT Caller ID listens to one event from the Webex client (sidebar:callStateChanged), not to the phone system or the carrier. If the call rings in the Webex client, it is recognised — no matter who carried it.
Who can supply Webex Calling in Germany?
Cisco itself through Cisco Calling Plans; a certified provider through Cloud Connected PSTN; any provider at all through a Local Gateway; or Webex for Placetel. Cisco names Germany explicitly in its Calling Plan country list.
What about Austria, Switzerland, Spain and France?
Switzerland and France are in Cisco’s Calling Plan list, Austria and Spain are not. There the route runs through a certified provider or a Local Gateway — Cisco writes that this lets you use “virtually any PSTN provider around the world”. For caller recognition it makes no difference.
Do I have to change provider?
No. There is nothing to configure on the carrier side: no forwarding, no SIP trunk, no entry in the phone system. The only thing you set up is access to your CRM.
When does it not work?
When the call does not reach the Webex client. If you use Webex only for meetings and messaging while running a separate phone system, the event never fires. TAPI is the other road then, with different prerequisites.
Is call content processed?
No. What is processed is the other party’s phone number, in order to look it up in your CRM. No recording, no transcript, no content.