Summary

  • India says it is ready to join an ITU proposal for joint trials on selected international routes; the cited record does not name participating countries or operators or show that a trial has started.
  • ITU standards describe how a network can authenticate the calling line attached to a call. They do not verify the speaker’s identity, the truth of the conversation, or whether the call is fraudulent.

A national result meets an international boundary

India's domestic anti-fraud programme has several moving parts. At an ITU roundtable in New Delhi on 9 October, Minister of State for Communications Chandra Sekhar Pemmasani cited the ASTR tool, the Sanchar Saathi app, the Digital Intelligence Platform and a Financial Fraud Risk Indicator. A Ministry of Communications release says ASTR had helped disconnect more than 8.2 million connections (82 lakh), the app had around 25 million downloads, the platform connected more than 1,600 organisations, and the risk indicator had helped prevent suspected losses above ₹50 billion (5,000 crore) in 15 months. These are government-reported measures: downloads are not active users, disconnections are not a count of victims, and suspected avoided losses are not an audited total. (Ministry of Communications release)

The minister's international proposal is more specific than a general call for cooperation. India welcomed an ITU proposal for joint trials, said it was ready to contribute, and suggested starting between willing countries on selected routes using different network technologies. That is a proposal for future testing. The public statement does not identify a partner country, participating carrier, timetable, funding arrangement or live route.

The test matters because a call can cross several independent operator and national domains before it reaches a handset. A domestic filter may assess a number inside one jurisdiction. At a border, the receiving network needs a reason to trust that the calling line presented upstream was authorized to use that number—and it needs the relevant evidence to survive the journey.

What the certificate says—and what it cannot say

The technical pieces are not brand new. ITU-T Q.3057, Q.3062 and Q.3063 are in force, dating respectively from 2020 and 2022. In broad terms, they define a trustable-network architecture, protected signaling procedures and calling-line identification (CLI) authentication. Under Q.3063, a certificate is tied to proof about a calling number at the originating local exchange. A network security gateway can attach certificate and signature material to call signaling; transit exchanges carry the call; a destination network can verify the evidence and may pass a security indication onward. (Q.3057; Q.3062; Q.3063)

That is a bounded claim. A certificate can support the proposition that the line was authorized by the relevant network. It does not establish which person is speaking, whether an authorized subscriber has been impersonated in another way, what the caller intends, or whether a claim made during the conversation is true. Nor does the standard itself show that a carrier has deployed the mechanism. Q.3063 makes destination-side presentation optional, while transit networks and interworking protocols can affect what arrives. A signed number is one useful signal; it is not a fraud verdict.

The remaining standards work is also part of the story. ITU lists draft Q.3070 on certificate issuance and draft E.1122 on a registration-authority anchor as ongoing, determined work. Q.3070 is under Member State consultation with a deadline of 4 March 2027. “Determined” does not mean published and in force. ITU's 1 October preview described the New Delhi roundtable as a discussion of practical implementation and the potential for a proof of concept; its programme examined falsified caller-line identity across interconnected networks. Neither document reports a completed trial. (ITU status page; SG11 consultation notice; roundtable programme)

The route, not the announcement, is the evidence

A useful proof of concept would show what happens across named routes and network types: how many calls carry valid, missing, expired, revoked or unverifiable credentials; whether transit operators preserve the authentication information; how destinations treat each status; and what callers and recipients actually see. It would also report call completion, false acceptance, false rejection, complaint outcomes and the handling of legacy interconnection. These are questions for an evaluation, not requirements India or ITU has announced.

Without that evidence, the domestic figures and the international standards describe different layers. They show that India has built national controls and that a technical signaling framework exists. They do not yet show that an international caller-line claim can be trusted end to end, or that authentication reduces fraud on a live route. The next proof is operational: who trusts which authority, on which path, and with what consequence when the evidence is absent or fails.