The NetQoS uses a SPAN port on the callmanager network I believe to intercept SCCP traffic and call quality metrics as they come in from the IP Phones. I guess prognosis hits the AXL interfaces now to get all it's info? Not sure which app you are talking about.
<br><br><div><span class="gmail_quote">On 10/11/07, <b class="gmail_sendername">Gibson, Brian (Jersey City)</b> <<a href="mailto:brian.gibson@stifel.com">brian.gibson@stifel.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How does their app work in the 5.1 environment? I assume they no longer install a shim on the server?<br><br>-----Original Message-----<br>From: Matthew Saskin [mailto:<a href="mailto:matt@saskin.net">matt@saskin.net</a>
]<br>Sent: Thursday, October 11, 2007 12:55 PM<br>To: Ed Leatherman<br>Cc: Gibson, Brian (Jersey City); cisco voip list<br>Subject: Re: [cisco-voip] CM/IPT monitoring tools<br><br>I've become more and more intrigued by the NetQoS product - truly one of
<br>the few out there that can give insight into voice quality *without*<br>relying on CDR/CMR's.<br><br>Personally, we run Prognosis internally and for all of our clients. The<br>most recent versions (8.1 for CM 4x and 8 for CM5+) are great - I've yet
<br>to run into any issues with the agent installation as it is on the Cisco<br>"whitelist" which is generally taken as gospel.<br><br>With prognosis, you can get as granular with alerting as you want - for<br>example you can alert at anything down to a specific single phone
<br>unregistering - bad call quality from a single phone, etc.<br><br>Also for what it's worth, we chose prognosis after doing an extended<br>bake-off between it, cisco ops manager, and NetIQ.<br><br>-matt<br></blockquote>
</div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations