cancel
Showing results for 
Search instead for 
Did you mean: 

Avaya ONEX Agent - detail on active/finished calls is unreliable

Highlighted
IR Partner

Avaya ONEX Agent - detail on active/finished calls is unreliable

Hi

 

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.

 

Thanks

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Avaya ONEX Agent - detail on active/finished calls is unreliable

Hello Johnathan,

 

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.

 

Thank you,

Scott Baldwin

View solution in original post

4 REPLIES 4
Highlighted

Re: Avaya ONEX Agent - detail on active/finished calls is unreliable

Hello Johnathan,

 

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.

 

Thank you,

Scott Baldwin

View solution in original post

Highlighted
IR Partner

Re: Avaya ONEX Agent - detail on active/finished calls is unreliable

Thanks Scott.

 

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

 

Highlighted
05 Base Camper

Re: Avaya ONEX Agent - detail on active/finished calls is unreliable

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.

Highlighted
IR Partner

Re: Avaya ONEX Agent - detail on active/finished calls is unreliable

Hi,

 

We are using media gateways with integral VOIP modules - we arent using MED PRO

 

Thyanks 

Webinar: Keep the modern workforce connected

Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.

Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.

Join webinar