Vianordis
--:--:-- UTCVianordis / SUPPORT
communication

Visoris

Beta

Visoris is a customer-scoped VoIP observability dashboard for call volumes, traffic sources, quality trends, capacity, errors, and service health. It helps authorized operators investigate degraded calling and routing behavior.

Open Visoris
Beta operating manual

Visoris beta monitoring manual

Review customer-scoped VoIP traffic and call-quality dashboards without confusing diagnostic trends with verified root cause.

Manual
Version 1.0
Product
Visoris 1.0.0 beta
Verified
July 15, 2026
Language
English · Source
Owner
Visoris communications product and support
Source
visoris · 14f6af8
Review cycle
45 days
Start here

Audience, scope, and prerequisites

Covers the current customer-scoped Visoris dashboard and context controls for call and traffic monitoring. It does not cover video surveillance; no camera, recording, motion-event, or physical-access workflow exists in the verified source.

Who this is for

  • Customer VoIP operators
  • Service support analysts
  • Visoris tenant and global administrators

Before you sign in

  • A Visoris role and assigned customer or customer group
  • An incident time range, affected service, and user-impact description
  • Access to approved corroborating call or service evidence
Access model

Roles and responsibilities

RoleAccessResponsibilities
Customer userReview the dashboard for the assigned customer context.
  • Confirm customer and time range
  • Avoid accessing unrelated customer data
Customer administratorManage permitted customer scope through matching customer or universal groups.
  • Maintain group assignments
  • Review diagnostic access
Global administratorSwitch to authorized customer contexts and investigate across assigned scope.
  • Reconfirm context before every action
  • Preserve separation between customers
Workspace map

Navigation

Dashboard

/dashboard

Review call, traffic, and summary charts for the active customer.

Customer selector

Dashboard header

Switch context when administrator permission and customer assignment allow it.

Customer files

/api/files/{filePath}

Retrieve only customer-scoped assets through the protected application route.

Chapter 01

Review the monitoring dashboard

Always bind observations to the active customer, exact time range, and a corroborating operational signal.

Procedure 1.1

Confirm or switch customer context

Ensure every dashboard observation belongs to the intended customer.

  1. 1
    Read the customer header

    Confirm company identity before reviewing charts.

  2. 2
    Open the selector when authorized

    Choose only a customer assigned to your administrative scope.

  3. 3
    Wait for context reload

    Do not interpret charts until the selected customer is shown consistently.

  4. 4
    Record the context

    Include the customer and time zone in incident notes.

Expected result

The dashboard and any customer asset requests are scoped to the intended organization.

Procedure 1.2

Review call and traffic trends

Use the dashboard to identify the time and shape of an anomaly.

  1. 1
    Define the incident window

    Record start, end, time zone, affected route or service, and user symptoms.

  2. 2
    Review traffic sources

    Compare current distribution with the normal baseline for the customer.

  3. 3
    Review call and summary charts

    Look for aligned changes in volume, failures, quality, capacity, or active registrations as exposed.

  4. 4
    Check neighboring periods

    Determine whether the change is isolated, gradual, recurring, or ongoing.

  5. 5
    Capture sanitized values

    Record metrics and timestamps without unnecessary call-party data.

Expected result

The analyst identifies a bounded anomaly or confirms the dashboard does not show one for the reported interval.

Chapter 02

Investigate and escalate

A chart correlation is not root cause; compare it with service, routing, network, or call evidence.

Procedure 2.1

Correlate a call-quality incident

Combine dashboard signals with approved operational evidence.

  1. 1
    Select representative failures

    Use sanitized call or service identifiers from the incident process.

  2. 2
    Compare timing

    Align customer reports, dashboard changes, deployments, provider events, and routing or network alarms.

  3. 3
    Test a hypothesis

    State what evidence would confirm or disprove capacity, route, endpoint, network, or provider causes.

  4. 4
    Avoid unsupported conclusions

    Mark observations as correlation until the underlying service evidence confirms cause.

  5. 5
    Assign next action

    Route the case to the responsible network, voice, provider, or application team.

Expected result

The incident record distinguishes user impact, dashboard evidence, hypothesis, and the team responsible for deeper diagnosis.

Procedure 2.2

Escalate a monitoring defect

Report missing, stale, cross-customer, or implausible metrics with a reproducible scope.

  1. 1
    Confirm context and refresh once

    Check customer identity and time range before declaring data stale.

  2. 2
    Compare with a trusted source

    Use an approved service or call record to demonstrate the discrepancy.

  3. 3
    Record chart and time

    Include component name, expected value, observed value, and time zone.

  4. 4
    Escalate securely

    Use sanitized identifiers and never attach unrestricted customer files.

Expected result

Support receives a bounded monitoring discrepancy without unnecessary customer or call data.

Operating rules

Security and data handling

  • Confirm customer context before every investigation.
  • Use minimum call-party and customer data in notes and screenshots.
  • Do not retrieve customer files outside the protected scoped route.
  • Separate diagnostic correlation from verified root cause.
  • Report cross-customer visibility immediately.
Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Visoris 1.0.0 beta scope and must be rechecked when the product changes.

  • The verified application is VoIP monitoring, not video surveillance.
  • The current interface exposes a single dashboard rather than detailed camera, recording, or event workflows.
  • Some chart labels retain generic template terminology such as sales or traffic and require product-owner interpretation.
  • SNMP-based call-quality monitoring is described as a subscription capability and may not be enabled.
  • Dashboard data completeness and refresh cadence depend on configured upstream collectors.
Problem solving

Troubleshooting

You cannot sign in to Visoris

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

  1. Open the application from the approved portal and complete sign-in again.
  2. Confirm that the correct organizational identity and tenant are selected.
  3. If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

  1. Confirm the role and prerequisites listed for the procedure.
  2. Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
  3. Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search for the item by its stable name or identifier.
  3. Do not repeat irreversible or externally visible actions until the original operation status is known.

Charts are empty or stale

Likely cause: Customer context is unset, collectors are not configured, upstream data is delayed, or the dashboard component failed.

  1. Confirm the selected customer and refresh once.
  2. Compare with a known service signal for the same interval.
  3. Escalate the chart name, time window, and sanitized expected value.

The wrong customer appears

Likely cause: Session context, group assignment, or administrator switching state is incorrect.

  1. Stop the investigation and do not open files or expand the view.
  2. Record the displayed customer and time without copying its data.
  3. Sign out and report a potential tenant-isolation incident.
Escalation

Contact support

Contact support when

  • A repeatable Visoris error blocks an approved workflow
  • Expected data, permissions, or tenant boundaries appear incorrect
  • A security, privacy, compliance, or data-loss concern is suspected
  • Cross-customer data or assets are visible
  • Monitoring is unavailable during a live service incident
  • Dashboard terminology or values cannot be mapped to an operational metric

Include

  • The page, action, and expected result
  • The exact error text and time of occurrence, including time zone
  • Your tenant, role, browser, and a sanitized record or item identifier
  • Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

  • Passwords, access tokens, API keys, recovery codes, or session cookies
  • Unredacted personal, health, financial, or other regulated data
  • Private encryption keys or complete confidential documents unless an approved channel is provided
Contact support