Whoever carries your calls changes nothing

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.

1 event

1. 1 The phone rings Incoming call
2. 2 Webex reports the number
3. 3 Haus iT Caller ID standardises it
4. 4 Your CRM or ERP looks it up Your customer data stays here
5. 5 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, a list of supported providers is pointless — it could never be complete and would age constantly. That is exactly why we do not keep one.

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.

The test: 22 languages, 26 countries

Our portal speaks 22 languages. We held the corresponding countries against Cisco’s official list of where Webex may be sold at all.

25 of 26

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.