Status Pages

Status pages aggregate your probe health data into a public, shareable dashboard that displays real-time and historical SIP infrastructure status. They are a powerful way to demonstrate service quality to customers, internal teams, and stakeholders without granting them access to your CallMeter account.

What Status Pages Show

A status page presents a consolidated view of the probes you select as components. Visitors see:

• Overall system status -- A single banner reflecting the health of all components
• Individual component status -- Each probe displayed as a named component with its current health state
• Uptime history -- A visual timeline (uptime bar) showing health transitions over recent days
• SLA compliance -- Uptime percentage calculated from probe health data
• Incident timeline -- Periods of degradation or failure highlighted on the history bar

Status pages require no authentication to view. Anyone with the URL can see the current and historical health of your SIP services.

Creating a Status Page

1. Open your project and navigate to Status Pages in the sidebar
2. Click New Status Page
3. Fill in the configuration:
   • Name -- A descriptive title displayed at the top of the page (e.g., "VoIP Infrastructure Status" or "SIP Trunk Health")
   • Description -- Optional text explaining what the page monitors
   • Probes -- Select the probes to include as components on the page
4. Click Create

Your status page is immediately available at its public URL.

Customizing Your Status Page

After creating a status page, you can customize its appearance and content to match your organization brand.

Branding Options

• Logo -- Upload your company logo to display at the top of the status page
• Colors -- Customize the primary accent color to match your brand
• Description -- Add context about what infrastructure is being monitored and how to interpret the statuses

Component Organization

Each probe you add becomes a component on the status page. Components are displayed in the order you arrange them. Use clear, customer-facing names for each component so visitors understand what they represent.

Examples of good component names:

• "Primary SIP Trunk (US East)"
• "Backup SIP Trunk (EU West)"
• "IVR System"
• "Conference Bridge"
• "Recording Service"

Understanding Status Indicators

Component Health States

Each component (probe) displays one of the following states:

Overall Page Status

The banner at the top of the status page reflects the worst status among all components:

This gives visitors an instant read on whether your SIP infrastructure is functioning normally.

Uptime History and SLA Tracking

Uptime Bar

Each component displays a horizontal bar chart representing its health over recent days. Each segment in the bar corresponds to a time period and is colored based on the probe health during that window:

• Green segments indicate healthy periods
• Yellow segments indicate degraded periods
• Red segments indicate unhealthy periods
• Gray segments indicate no data

Uptime Percentage

Below each component, CallMeter calculates and displays the uptime percentage based on the ratio of healthy time to total monitored time. This is a direct measure of SLA compliance.

For example, if a probe has been healthy for 719 out of 720 hours in a 30-day period, the uptime percentage is displayed as 99.86%.

Using SLA Data

Uptime percentages from status pages serve as evidence for SLA compliance discussions:

• Share the status page URL in SLA reports
• Reference historical uptime when negotiating contracts
• Use probe threshold configurations to define what constitutes an SLA breach

Sharing Your Status Page

Public URL

Every status page has a unique public URL that you can share directly:

• Send it to customers as part of your service documentation
• Include it in your support portal or knowledge base
• Add it to your SLA documentation
• Link it from your company website

Embedding

You can embed a status page into your own website or internal dashboard using an iframe. This lets you integrate CallMeter health data into your existing monitoring view without redirecting users to an external page.

<iframe
  src="https://status.callmeter.io/your-page-slug"
  width="100%"
  height="600"
  frameborder="0"
  title="SIP Infrastructure Status"
></iframe>

Adjust the width and height to fit your layout. The embedded view is responsive and adapts to the container size.

Real-World Use Cases

Proving Quality to Customers

If you are a SIP trunk provider or a hosted PBX vendor, sharing a status page with your customers demonstrates transparency. Customers can check the page at any time to see if an issue is on your side or theirs.

Internal NOC Dashboard

Network Operations Center (NOC) teams can display status pages on wall monitors for at-a-glance infrastructure health. Since the page auto-refreshes, it always shows the latest probe results.

Vendor Accountability

When you rely on upstream SIP providers, create probes that test their trunks and expose the results on a status page. This gives you documented evidence of their service quality over time.

Multi-Region Monitoring

Create separate status pages for each geographic region or data center. Each page includes only the probes relevant to that region, giving stakeholders a focused view.

Managing Status Pages

Editing a Status Page

1. Navigate to Status Pages in your project
2. Click on the status page you want to modify
3. Update the name, description, branding, or probe selection
4. Click Save

Changes are reflected immediately on the public URL.

Adding or Removing Components

To add a new probe as a component:

1. Edit the status page
2. Select additional probes from the available list
3. Save

To remove a component, deselect the probe and save. Removing a probe from the status page does not stop or delete the probe itself.

Deleting a Status Page

1. Navigate to Status Pages
2. Click the options menu on the status page
3. Select Delete
4. Confirm the deletion

The public URL stops working immediately after deletion.

Best Practices

• Use meaningful component names -- Customers should understand what each component represents without needing technical knowledge
• Group related probes -- If you monitor multiple aspects of the same service (registration, call setup, media quality), include them all on one status page
• Set appropriate thresholds -- The health states shown on the status page are only useful if your probe thresholds reflect real quality standards
• Communicate with your audience -- Use the description field to explain what the status page monitors and how to interpret different states
• Review regularly -- As your infrastructure evolves, update your status pages to reflect current architecture

Next Steps

• Creating a Probe -- Set up probes to populate your status page
• Threshold Configuration -- Define what constitutes healthy, degraded, and unhealthy
• Webhooks -- Get automated alerts alongside your status page