Click2CallPing¶

GET click2call/ping

Liveness probe for monitoring. Costs one SELECT 1 and reads process counters, so it can be polled often.

"The process answers" is not enough for this module: it can still be on the bus after losing its database or its status-polling cron, and in that state calls would silently stay in INITIATED forever. An empty problems array is what actually means healthy.

Access Control¶

Any authenticated session. The handler does not read __access, so service-to-service calls over the bus work without a token.

Request¶

RESTTCPSDK

GET request

GET https://{broker_domain}/click2call/ping
Authorization: <JWT_TOKEN>

{
  "command": "Click2CallPing",
  "extID": "1",
  "data": {}
}

const res = await platform.Click2CallPing({});

Request Data¶

This method takes no parameters.

Behavior¶

The polling cron marks itself on every tick, even when there is nothing to poll, so silence longer than five intervals is a fault rather than an absence of calls.
Use Click2CallHealth when you need the full picture instead of a probe.

Response Data¶

Problem codes: DATABASE_UNAVAILABLE, ADAPTERS_FAILED, POLL_CRON_STALLED.

{
  "ok": true,
  "problems": [],
  "service": "sct-click2call",
  "nodeID": "sct-click2call-3227647",
  "version": "0.0.1",
  "startedAt": "2026-08-24T13:32:41.702Z",
  "uptimeSec": 412,
  "time": "2026-08-24T13:39:33.118Z",
  "database": { "ok": true, "latencyMs": 1 },
  "adapters": { "loaded": 19, "failed": [] },
  "crons": {
    "enabled": true,
    "pollIntervalSec": 3,
    "lastPollAt": "2026-08-24T13:39:31.004Z",
    "lastPollAgoSec": 2,
    "runs": 137
  }
}

Errors¶

Code	Error	Description
`502`	`MOL_CALL_FAILED`	The module is not on the bus