Dashboard or live views show no resources
Separate an AMI connection failure from an empty inventory, a hidden group or a restriction on the current account.
Recognize the symptom
The page opens but expected queues or extensions do not appear, or their live state fails to update. First establish whether this affects all accounts and all live pages or only one team leader and one view.
Possible causes
Possible causes are an unreachable AMI service, incorrect connection credentials or permissions, stale inventory, shared hidden resources, and account or personal visibility settings. An empty view by itself does not prove that the PBX has stopped handling calls.
Check before changing anything
In System and utilities, inspect the saved PBX connection and its check result. Compare the same view with an administrator account. If the administrator sees the resources, review Operational views, account scopes and Preferences before touching AMI credentials or firewall rules.
Take a targeted action
Correct the identified connection setting or access restriction, then refresh the relevant inventory and save the view if needed. Keep Monitor and Status extension groups separate. Do not expose AMI broadly to resolve one client-side visibility problem; the application connects to AMI from the server.
Verify the result
Check the original account again and observe a known resource through a normal refresh. Verify visibility and live state independently. If the connection succeeds but inventory remains incomplete, record the affected PBX identifiers and diagnostic findings instead of creating substitute resources.