Avaya VoIP Monitoring Manager Reference
69
There is no data currently available for this endpoint.
Explanation
This happens when calls are too short to produce reporting data, or the reporting data has been
lost.
If the actual call duration is comparable to the reporting period (or shorter than the reporting
period), there may be no RTCP packets received. The endpoints normally provide a reception
report, but in this situation none will be received before the call ends.
Endpoints are identified by data that they send in RTCP packets. Hence if no packet is received,
at least one of the session participants cannot be identified. The report shows unknown endpoint.
Calls that do not generate one or more RTCP packets are reported as having the default duration
of five seconds. The actual call may have been longer up to 10 or 15 seconds.
Even if one RTCP packet is generated during a short call, it could be lost due to other
environmental factors. For example, one participant might have silence suppression enabled, with
the packet sent during the suppression period.
No Endpoints Matched the Search
If you receive the following error message, it could be due to one of the situations as described:
No endpoint matched the given search.
There are no endpoints reporting to the RTCP Monitor or the chosen VoIP Monitoring
Manager Server.
The calls are active, but since no data is being sent to the RTCP Monitor, the ip-network-
region form and the system-parameters ip-options form for the Avaya Communication
Manager system are not configured correctly.
There were no endpoints that matched the QoS parameters in the search.
There were no endpoints that matched the search for phone number, SIP username,
Network Address, or date range as specified in the Search dialog box.
Try Broadening the Search:
Select a different date range in the Search dialog box.
Use a more general phone number pattern.
Search for all endpoints instead of just those matching a given phone number, SIP
username, or network address.
Server Unavailable
If you receive one of the following error messages, the VoIP Monitoring Manager Server has not
been started. You must start the VoIP Monitoring Manager Server and verify that the machine
you have attempted to connect with is the machine running the VoIP Monitoring Manager Server.
If you are using the Web Client, you must refresh your browser to reconnect to the Server.
Comentarios a estos manuales