This document describes how Vyopta Product Support can be engaged when you have an issue with the Vyopta product.
In order to ensure that Vyopta is able to offer the best possible support experience, it is essential that all support requests are raised via the Vyopta helpdesk at https://support.vyopta.com.
A case raised by other means (email, phone call, IM session etc) may not be accepted by the Vyopta support team, for the following reasons:
- Such requests are visible to only one team member
- This team member may be off-shift, busy, absent or on vacation – it may therefore be many days before you receive a response.
- In-ticket documentation is necessary to allow other engineers to work on the ticket or provide input
- Engineers work in many time-zones – synchronous handover may not be possible
- A high-priority ticket may ‘follow-the-sun’ – the ticket must contain the hand-over information.
- Should an escalation be required, all relevant documentation is present in the ticket
- Ticket queues are monitored – other channels are looked at only as availability permits
If you are receiving this document in response to a request for assistance that was not sent via the helpdesk then please take the following actions:
- Visit the help centre at https://support.vyopta.com/hc - in many cases you will be able to find the answer to any issues you are experiencing in our knowledge base
- If you cannot find the answer to your problem, then raise a ticket at https://support.vyopta.com and an engineer will get back to you as soon as one is available.
All tickets raised should contain the following information:
- A description of the fault seen – this must be as specific as possible
- Where appropriate, a description of what is expected to be seen
- Any error messages displayed
- Screenshots showing the problem
- An impact statement, if possible.
By way of examples:
Vyopta not working.
When monitoring a call between any endpoints - for example EP1 and EP2, a blank page is displayed when clicking the Quality link in the CPM Monitoring dataset for call with source EP1.
The data source is shown as EPM.
No error messages are displayed.
The quality statistics for the call in-progress on EP1 are expected to be seen.
We are therefore unable to monitor calls between endpoints.