#computertelephony

Live, measured metrics for the hashtag #computertelephony from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #computertelephony

This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.

$5.00/ year · 17-character #name
Claim #computertelephony — $5.00/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
4
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 4
0.8
Avg reactions / post
Mastodon · last 4

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 15:42 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 15:42 UTC

No related tags with measured usage found for #computertelephony.

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 15:42 UTC

Everything below is measured over the latest 4 public posts (spanning ~26453 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (4)

Avg boosts / post: 0.3

Top of the latest posts

  • @bithive The biggest cost, in Germany or otherwise, is the people who do the talking to the callees. It dwarfs the costs of RTNR and suchlike. That has long since (i.e. decades ago) been optimized, both by mechanizing the Hell out of the ca

    JdeBP@[email protected]♥ 3↻ 02026-01-25 14:32 UTCView post →

  • @PGBeattie It already exists, long since. But it's only available on SIP 'phones. Loop-disconnect signalling doesn't have the protocol for sending the data. But on a SIP call the SBC can do what is known as a CNAM lookup when a call comes i

    JdeBP@[email protected]♥ 0↻ 12025-11-20 12:11 UTCView post →

  • @keefeglise @bytebro Actually, from an engineering perspective that's dead easy, as being out of synch is largely the default. It's synchronizing them that's hard. Digital sound codecs even introduce extra things that have to be compensated

    JdeBP@[email protected]♥ 0↻ 02023-10-15 21:17 UTCView post →

Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/computertelephony