One thing I have noticed is that we dont always seem to get RTCP information from our 1x users- is there anything that could be causing this? Is there anything special in the configuration that we need to look at? Sometimes we make a call and when we serach back for that extension, there is no detail at all for the endpoint.
Solved! Go to Solution.
There shouldn't be anything special about One-X that would cause missing RTCP Streams. One-X will of course to need be configured to send the RTCP streams to Prognosis. Prognosis listens for the data and records it.
Use the search in the Prognosis Web UI should find the extension. Drilldown on the extension from the seach results. Active RTCP Streams should show at the bottom of the page. To view past RTCP Streams, Drilldown on the Finished Calls link in the upper right of the page. If the RTCP Streams are not showing in Prognosis, the further troubleshooting is needed.
If Prognosis never has any RTCP data for a specific extension, I would suspect a One-X misconfiguration, or something in the network blocking the packets.
If the RTCP data for a specific extension is missing intermittenly, the range of possibilities grows.
To troubleshoot the missing RTCP data issue, I usually use a Wireshark capture on the Monitoring Node with test calls to verify if the data is reaching the Prognosis server or not.
Use the following Capture Filter in Wireshark during test calls: dst host <Server_IP_Address> and port 5005
When reviewing the capture, use the following Display Filter: ip.addr == <One-X_IP_Address> && udp.port == 5005
Please let us know if additional direction is needed.
Its a weird one as it seems to happen occasaionally- one x RTCP does work as we received from other clients but we are seeing some instances where there are no records at all against a OX extension.
Thnaks for the tips- will use WS next time we have any issues of RTCP not being sent to Prognosis
All the best
Prognosis does not support RTCP on Avaya's older 2302 MedPros, only the newer 2602s. Check and see if those voice streams missing RTCP data are traversing the older circuit packs.
Having looked at the planning phase in session one of this series, we will turn our focus to the readiness phase. The all important technical capabilities assessment, ensuring the network, endpoints and users are adequately prepared for the move.
Hear first hand from IR's Global Head of Information Systems and Technology, Jason Schwendinger, on how he has been tackling these issues.Join webinar