New · Calliseum services
Login and phone verification by call
A one-time code usually means an SMS: slow, paid, and blocked or filtered more often than a call. FlashCall and BackCall use the telephone call itself to prove that the user holds the number — nothing to type, nothing to install, and no SMS provider in the middle.
Two directions, one idea
| Mode | Who calls | What confirms the number | Your application learns |
|---|---|---|---|
| FlashCall | The system calls the user | Last digits of the caller ID shown on the phone | The HTTP response to its own request: 200 when the call was answered, a SIP code otherwise |
| BackCall | The user calls the system | The calling number (ANI) of the incoming call | A signed HTTP callback with received, or notreceived when the window expires |
FlashCall: the system calls the user
The application sends a JSON request to the Calliseum HTTP endpoint. The platform places a short call to the number; the last digits of the caller ID are the one-time code that the user reads back into your login form. The response tells the application whether the subscriber answered.
POST http://your-server:2172/flashing_call
Content-Type: application/json
{
"destAddr": "+7 495 1234567",
"message": {
"type": "FLASHINGCALL",
"data": { "text": "1234", "ttl": 1 }
}
}
200— the subscriber answered; a SIP code such as487means busy, and the call can be retried or replaced by an SMS.- The request and the response are plain HTTP and JSON, so any web application, CRM or helpdesk can use it.
- Call duration, RTP usage and SDP behaviour are script settings, so no media is set up when only the caller ID matters.
- The script decides what counts as success — return always
200and report the SIP code in the body, for example.
BackCall: the user calls the system
BackCall is the inbound variant, and the one to use when the user cannot receive a call — roaming, a PBX that blocks incoming, a number behind a gateway. The application registers the expected call with a transaction id, and the user dials the published number. The incoming call is matched by its caller ID, and the application receives a signed callback.
POST http://your-server:2172/backcall
Content-Type: application/json
{
"login": "client",
"password": "secret",
"phone": "+74951234567",
"transaction": "20261118-120000-4f3a9c",
"callback_url": "https://app.example.com/backcall/status"
}
The platform answers with the message id and the number it registered. When the call arrives, the callback carries the result:
{
"status": "received",
"phone": "74951234567",
"time_change_state": "2026-11-18 12:03:11",
"transaction": "20261118-120000-4f3a9c",
"sign": "sha256(transaction + key)"
}
received— a call from the expected number arrived inside the window;notreceived— it did not, and the pending request is closed by the background notify script.signis the SHA-256 of the transaction id with your shared key, so a callback cannot be forged.- Numbers are normalised to
7XXXXXXXXXX; the call can also be matched when a PBX forwards it to the platform as a normal inbound call. - Everyone sees the same thing: the user simply dials a number and hangs up, or hears a short confirmation.
Where it pays off
- Login and registration in a customer portal or mobile app without SMS cost.
- Confirmation of a phone number in a CRM, helpdesk or onboarding form.
- Second factor for an operator workstation or an administrator account.
- Confirming a callback request: the customer calls in, the system matches the number and opens the request.
- Markets where SMS delivery is slow, expensive or filtered.
How it fits Calliseum
Both services are Calliseum scripts on the same SIP engine and database as recording, notification, fax and conferencing. The HTTP endpoints are scripted too, so the request fields, the response codes and the callback format can be changed to match an existing API instead of changing the application.
Part of Calliseum, price on request. Login is licensed with the platform, not sold separately. Tell us the flow — sign-up, login, second factor or callback confirmation — and we will send a scope. Ask about FlashCall and BackCall.
Common questions
What is FlashCall?
The application sends a JSON request over HTTP and Calliseum calls the number. The last digits of the caller ID are the one-time code the user reads back. The HTTP response reports whether the call was answered; there is no SMS.
What is BackCall?
BackCall is the inbound variant. The application registers the expected phone number and a callback URL; the user dials the platform number, and the call is matched by its caller ID. The application then receives a signed callback with status received, or notreceived when the window expires.
Does the user need an app or a smartphone?
No. Any telephone will do: FlashCall works by showing the caller ID, and BackCall by the user calling a number.
How does the application know the callback is genuine?
The callback carries sign, the SHA-256 of the transaction id with a shared key. The application recomputes it and rejects anything that does not match.
What happens if the call does not arrive?
With BackCall the background notify script closes the request and posts notreceived, so the application can fall back to SMS or another method. With FlashCall the response returns a SIP code such as 487 when the subscriber is busy.
Is it expensive compared with SMS?
The call replaces the SMS, so there is no per-message provider fee, and Calliseum is licensed with the platform rather than per verification.