Configuring CUBE IPSLA metrics with Prognosis

[ghinson]

I'd like to configure IPSLA on a Cisco Unified Border Element (model 2921) and integrate it with Prognosis so that the IPSLA and voice quality metrics tables are populated in the Cisco SBC Web view for Prognosis. Does anyone have a sample configuration on the CUBE side they'd be willing to provide?

[GeraldC1]

Here's one:

https://help.prognosis.com/prognosis/116/setup-cisco-ios-ip-sla-operations-13605064.html

HTH

[ghinson]

Thanks for the reply. I used the following configuration, where 172.31.2.170 is the IP of my prognosis server:

ip sla 1
udp-jitter 172.31.2.170 16384 codec g711ulaw
tos 184
owner IR
exit
ip sla schedule 1 life forever start-time now

However when I run "show ip sla statistics" I get a mos value of 0 in Prognosis and a latest operation return code of "No connection" on CUBE

z.router#sh ip sla statistics
IPSLAs Latest Operation Statistics

IPSLA operation id: 1
Type of operation: udp-jitter
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 13:23:46 MDT Wed Oct 30 2019
Latest operation return code: No connection
RTT Values:
Number Of RTT: 0 RTT Min/Avg/Max: 0/0/0 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 0
Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Jitter Time:
Number of SD Jitter Samples: 0
Number of DS Jitter Samples: 0
Source to Destination Jitter Min/Avg/Max: 0/0/0 milliseconds
Destination to Source Jitter Min/Avg/Max: 0/0/0 milliseconds
Over Threshold:
Number Of RTT Over Threshold: 0 (0%)
Packet Loss Values:
Loss Source to Destination: 0
Source to Destination Loss Periods Number: 0
Source to Destination Loss Period Length Min/Max: 0/0
Source to Destination Inter Loss Period Length Min/Max: 0/0
Loss Destination to Source: 0
Destination to Source Loss Periods Number: 0
Destination to Source Loss Period Length Min/Max: 0/0
Destination to Source Inter Loss Period Length Min/Max: 0/0
Out Of Sequence: 0 Tail Drop: 0
Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
Calculated Planning Impairment Factor (ICPIF): 0
Mean Opinion Score (MOS): 0
Number of successes: 0
Number of failures: 1
Operation time to live: Forever

Thinking it was an issue with IP SLA communicating on port 16384 with Prognosis, I went into the Prognosis windows server and created a firewall exception for UDP/16384 to match, but that didn't make a difference on connection state. Any ideas on what I'm missing?