When I view the SMGR dashboard, I don't see any data for SIP voice streams(see below)
Where is the data derived from and are there any tips you can give to troubleshoot this?
The SMGR and ASMs are all correctly added to prognosis and are showing as UP and i can obtain environmental data from the server(HW/CDR etc).
SIP Voice Stream data in Avaya System/Session Manager comes from RTCP Streams, as with Avaya Communication Manager.
System/Session Manager only communicate with control data, and do not transport the actual voice payload. Because the voice payload is never handled, Session Managers do not generate RTCP Streams for any calls.
Only Avaya RTCP capable SIP phones registered to a Session Manager can show in the Session Manager SIP Voice Streams Dashboard. Trunks do not generate RTCP Streams, so will never show Voice Stream data.
The SIP phones will need to use an updated 46xxsettings.txt file to direct their Voice Streams to Prognosis.After the new 46xxsettings.txt file has been dowloaded by the SIP phone from and TFTP server, the phone will need to be rebooted to enable the change.
The following Prognosis Online Help may be helpful in making the 46xxsettings.txt change: Monitoring Avaya SIP Phone Voice Streams (found under: Home > Prognosis for Unified Communications > Avaya Aura Communication Manager > Configuration > Avaya Setup > Configure RTCP Monitoring)
Prognosis is able to interpret the RTCP data sent by Avaya Communication Manager MEDPRO boards, Gateways and Avaya phones compatible with the 46xxsettings.txt file.
I was not able to verify if B179 SIP conference phones send RTCP data. If RTCP data is sent, I was not able to confirm it is in the same format as the other Avaya Communication Manager endpoints. The February 2015 "Release Notes for Avaya B179 SIP Conference Phone Releases 184.108.40.206 and 220.127.116.11" (https://downloads.avaya.com/css/P8/documents/101007938) advises "RTCP monitoring support will not be available until our next release". I was not able to find a newer document confirming RTCP monitoring is now supported.
If the RTCP is sent by B179 SIP conference phones in the same format sent by the other supported endpoints, then yes, Prognosis can interpret the RTCP data correctly.
Ultimately, Avaya is the best resource to query about the B179 SIP conference phone and about if it sends RTCP data in the same format as other Avaya Communication Manager endpoints. I would like to provide a better response, but was not able to find the correlating Avaya documentation.
Thanks Scott- we are running the latest version of FW and there is a file within the web set up that allows you to specify an RTCP destination. I will check with Avaya and post their feedback against this thread once received.
Thanks for your support