Obelisk
EN
Live operations

The IT picture behind every extension.

Bring phones, softphones, reported versions, registration states and response latency into one view. Give IT a practical starting point for device maintenance and faster investigation.

PJSIP contacts and devices
Latency thresholds
Overview and map
Your thresholds. Your organisation.

Make the signals work for your team.

Personal RTT thresholds

In Preferences, choose when response latency should attract your attention. Enable or disable warning and critical alerts independently and set each threshold in milliseconds.

Warning > 100 msCritical > 400 ms

These are the starting values. Your saved preferences define your alerts.

Explore personal Preferences

Groups, visibility and privacy

In Operational views, administrators organise Status into groups of extensions, choose which entries to show and control whether operator names are visible. Status has its own name-privacy setting.

Dashboard / WallboardMonitorStatus

The same administrative area brings together Dashboard and Wallboard queue sections, Monitor groups and Status groups. Each workspace keeps the visibility and privacy settings appropriate to its data.

Explore Operational views
In practice

Read the signal.
Choose the next step.

One failed device stays visible

ReachableHigh pingUnreachable

A person may register both a desk phone and a softphone. The overview counts the detected extension once and uses its most severe contact status, so a reachable device does not hide another device’s registration failure. Open the contact rows to identify which endpoint needs attention.

Compare devices and locations

Use device and version groups to look for a shared equipment pattern, then inspect the public-IP map for a shared network pattern. Together, the two views help you investigate whether affected registrations cluster around a phone version or a connection used by several extensions.

If agents report call issues, start with high-RTT or unreachable contacts. Inspect registration details and device versions, then compare whether the problem affects one endpoint or a wider group.

Put it to work

01

Compare the make/model and firmware or software version reported by registered SIP contacts. Grouped counts make different versions visible and help you identify devices to review before planning updates.

02

Read the contact round-trip time reported by Asterisk alongside its registration state. Personal warning and critical thresholds, coloured badges and the high-ping filter help you focus the investigation.

03

Start with the extension health overview, then inspect names, devices, IP addresses, reported versions and registration expiry. Groups, search and sorting help you narrow the issue to the contacts that need attention.

04

Read device, extension, IP address and response time together, including multiple contacts associated with one extension.

05

Search the table, select a group or filter high latency to focus on the endpoints that need attention.

06

Open the map for an approximate geographic view of public IP contacts, with the same resource visibility as the rest of the page.

What you can do

01

A diagnostic overview

Diagnostics overview: normal, high ping, critical ping, unreachable contacts and undetermined status.

02

Inspect individual contacts

Sortable contact table with extension/AOR, person, device, version, registration state, RTT, IP and registration expiry.

03

Understand the device mix

Distribution of reported device names and software versions, with expandable remaining categories.

04

Location with context

Map of permitted extensions and public-IP locations, clustered with diagnostic severity.

05

Focus on the exception

Search, groups, high-ping filter, pagination and pausable refresh.

06

Display sessions

Use a dedicated Display account for read-only access to authorized live views, with a configurable session duration.

07

See devices by model and version

Compare the make/model and firmware or software version reported by registered SIP contacts. Grouped counts make different versions visible and help you identify devices to review before planning updates.

08

Find slow or unreachable contacts

Read the contact round-trip time reported by Asterisk alongside its registration state. Personal warning and critical thresholds, coloured badges and the high-ping filter help you focus the investigation.

09

Move from the overview to the contact

Start with the extension health overview, then inspect names, devices, IP addresses, reported versions and registration expiry. Groups, search and sorting help you narrow the issue to the contacts that need attention.

Read the detail with confidence

What does this view measure?

The diagnostics overview counts each detected, permitted extension once. The contact table can contain several registrations per extension; extensions with no detected contacts are not included.

User-Agent data is reported by clients, not a certified physical-device inventory.

User-Agent data is reported by clients, not a certified physical-device inventory.

IP location is approximate

IP location is approximate; network registration is not availability to receive calls.

Continue exploring

Request your demo

The complete Obelisk experience. Tell us about your contact center.

Loading the request form…