Despite configuring all the Avaya System and Session Manager components in Web and Prognosis Client GUI.
Received Status UP and CDR Calls Database and files processing. However No CDR data being populated for SIP Calls within the files collected shown below
Session Manager CDRs require the ability of Prognosis to login to the Session Manager and do an SFTP "get" of the CDR files.
The screen capture shows the total Voice Streams are 0. Voice Stream information comes from RTCP packets sent to Prognosis.
If the above configuration suggestions do not cause the CDR and RTCP (Voice Stream) data to show in Prognosis, please open a Support case to work directly with an IR Support Engineer.
Thank you for the detailed feedback.
We only have Avaya H323 II Handsets, there are no SIP Avaya Phones to update the settings file requirement
We only have SIP Trunks active between Adjunct Platforms
i.) Cisco CUCM as well as CUBE
ii.) Oracle ACME SBC's
iii.) Unigy IPC V3
iv.) Avaya SBC 7.2.2 (Still in Build stage)
Would this be the reason CDR data is collected but there are 0 records to capture (reason why = 0 SIP Voice Streams)
Thank you Quinton
The lack of Voice Stream data from Session Managers is because of how the Avaya phones are registered. Avaya phones using H323 will only be registered to the Avaya Communication Manager (ACM). This will cause Prognosis to associate all QoS from the phones to the ACM.
Session Manager CDR and RTCP data are kept completely separate in the Session Manager. For this reason Prognosis uses differing Displays for the 2 data types.
Avaya Session Managers only provide call control, and do not ever touch the packets transporting the actual voice part of calls. Because the actual voice payload is never touched by the Session Managers, no QoS data is ever generated by Session Managers.
Session Manager CDR data never includes any Quality of Service (QoS) data. Session Manager CDR data will have other metrics such as call start and stop time. The Session Manager CDR data should be available to Prognosis.
Cisco CUCM and CUBE can each generate QoS metrics visable in Prognosis if configured correctly.
Unigy is not supported by Prognosis so no QoS metrics are available from these devices.
Avaya SBCEs can forward QoS data received in RTCP packets, but do not generate RTCP packets on their own. If the RTCP packets are sent to the ASBCE, the ASBCE can add its IP into the hop data, but this is the limit of ASBCE and QoS.
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