Skip to main content

​
Colleagues

The Colleagues page is a live directory of every teammate’s SIP extension. Each row shows the colleague’s current presence — available, on a call, do not disturb, away, or disabled — and offers a one-click call straight to their extension from the in-browser softphone. Use it instead of dialling extension numbers by hand.

​
Reach the page

Open /voice/colleagues directly, or search “Colleagues” in the command palette. The page lives in the Voice section and reads the same set of SIP credentials you manage under Voice → Extensions.

​
Live presence states

Presence updates automatically. Each colleague carries one of five states: The state updates within a few seconds of a colleague answering or hanging up. Hovering a greyed-out Call button explains why the colleague cannot be called right now. Use the search box at the top to filter the list by name or extension as your team grows.

​
Call a colleague with one click

  1. Find the colleague in the list (search filters by name or extension).
  2. Click Call on their row. The in-browser softphone dials their extension number directly — an internal call, so no outbound dialing rules apply.
  3. If you are already mid-call, the button stays disabled until your current call ends.
From the row’s menu (the ··· icon) you can also open the colleague’s extension record to edit, delete, or rotate its credentials — the same controls as on the Voice → Extensions page.

​
Intercom instead of ringing

When a colleague is on a call or in do-not-disturb, the Intercom button still works: it opens a two-way or push-to-talk session to the colleague’s softphone, which auto-answers. Choose the mode from the Intercom dropdown.

​
Colleagues vs. Extensions vs. Attendant console

These three surfaces look at the same SIP credentials from different angles:
  • Colleagues — a quick-contact directory: glance at presence, click to call. Read-only presence with one-click dialing.
  • Voice → Extensions — the management surface: create, edit, disable, and rotate credentials for each SIP endpoint.
  • Voice → Attendant console — a front-desk operator surface: answer, transfer, park, and pick up inbound callers already in progress. Its lamp field shows the same presence states, but every action there re-targets a live inbound call rather than originating one.
If you only need to route yourself to a teammate, use Colleagues. If you need to create or retire endpoints, use Extensions. If you run a front desk answering inbound callers, use the Attendant console.

​
Limits

  • Visible teammates = enabled SIP credentials. A colleague only appears once they have a SIP credential; disabling that credential shows the row as Disabled instead of hiding it.
  • Your own row is excluded. The list never shows you; it is a directory of colleagues to call.
  • Internal calls only. Click-to-call dials extension numbers or SIP usernames on-net. It does not place outbound (PSTN) calls.

​
Under the hood: presence snapshot + stream

The Colleagues page is a UI over two API read paths you can also consume from your own integration — a single-shot snapshot and a live server-sent-events (SSE) stream. Both return the same shape, so pick one: poll the snapshot, or hold the stream open and parse each frame.

​
One-shot snapshot

Each entry in states is one colleague’s SIP credential. The emittedAt timestamp stamps the snapshot; treat it as the freshness marker when you poll.

​
Live stream (SSE)

For a dashboard or wallboard that must flip presence the moment a call starts or ends, hold an SSE stream instead of polling. The API pushes a full snapshot on connect, then re-pushes whenever a colleague’s call status changes, plus a cadence tick so a missed event self-heals.
Each event carries the same {states, emittedAt} payload as the snapshot, on an SSE data: line:
Keepalive comments (: ping) arrive every few seconds — ignore them. A stream is capped at 30 minutes, so reconnect when the connection closes.

​
Wire state values

The wire uses the RFC 4235 dialog states for an active call, plus three lifecycle states: activeSince and direction are non-null only for early / confirmed (a call in progress). The page renders early and confirmed together as On call.

​
Click-to-call

In the dashboard, the Call button hands the target straight to the in-browser softphone, so the click never round-trips through the REST API. If you build your own click-to-call, originate via the browser softphone dial endpoint:
to is the colleague’s extension number (or SIP username). Both the Colleagues click and this endpoint place an internal, on-net call — outbound PSTN is never involved.

​
Cross-references