<div dir="ltr"><div>The Acme Packet Palladion is now the Oracle "Session Monitor", or
"Enterprise Operations Monitor", depending on the market. They are the
same product suite, comprising the control plane monitor, fraud monitor,
and operations monitor. Newer versions of the AcmeOS SBCs have the
probes built-in. <br><br></div><div>Here is a link to the documentation and new Oracle product names:<br></div><div><br><a href="http://www.oracle.com/technetwork/indexes/documentation/oracle-comms-acme-packet-2046907.html">http://www.oracle.com/technetwork/indexes/documentation/oracle-comms-acme-packet-2046907.html</a><br>
<br></div>Lonny<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 12, 2014 at 2:45 PM, Ujjval Karihaloo <span dir="ltr"><<a href="mailto:ujjval@simplesignal.com" target="_blank">ujjval@simplesignal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Look at Palladion by Acmepacket now Oracle<span class="HOEnZb"><font color="#888888"><br></font></span><div class="gmail_extra">
<span class="HOEnZb"><font color="#888888"><br clear="all"><div><div dir="ltr">
<p><a name="144284732d5c9bbd_SafeHtmlFilter__MailAutoSig"><span style="color:#1f497d">Ujjval Karihaloo</span></a><span><span></span></span></p><br></div></div><br><br></font></span><div class="gmail_quote"><div class="im">
On Wed, Feb 12, 2014 at 1:15 PM, Brian Knight <span dir="ltr"><<a href="mailto:ml@knight-networks.com" target="_blank">ml@knight-networks.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>$DAY_JOB is at a national ISP/NSP where we resell VoIP services. We do peering with the VoIP carrier at one of our remote POP's. We are looking for a better way to be able to monitor the handoff of those calls to our carrier over that peering link.</div>
<div><br></div><div>We have quite a bit of instrumentation within our walled garden to tell us about call quality. We can monitor our QOS policies to ensure packets aren't being dropped by intermediate routers. If the customer uses our routers to terminate their SIP session, we can pull call quality stats from those routers as well. We can also use our own office telephones to make and receive test telephone calls, and we can of course run Wireshark captures from the switches to which those phones are connected.<br>
</div><div><br></div><div>However, we can't say for certain that the customer's RTP traffic actually made it on the wire connecting us to the VoIP provider, nor can we say that the traffic is being transmitted and received properly. The peering link is connected to a Cisco 12k router on our side, so there is no way (afaik) to mirror the port, as on a switch.</div>
<div><br></div><div>For the moment, I am envisioning that we'll need to deploy a server running Wireshark to the remote POP. It will need two network interfaces; one connected to a management network, the other a capture interface. The capture interface will connect to a network tap, and the network tap connected in-line between our router and the patch panel.</div>
<div><br></div><div>Wireshark is probably adequate for what we need. But I'm wondering if there is any software or an appliance that would do the job better. Given the usual details - calling number, called number, date and time - we want to be able to quickly inspect traffic and dig into the details of the stream. Do we see any missing packets from the media stream? What is the MOS score of a particular call? Do we see any missing packets coming from us? Any missing packets from the provider?</div>
<div><br></div><div>Alerting on bad call quality would be a nice-to-have addition.</div><div><br></div><div>Any recommendation would be appreciated. Thanks in advance.</div><span><font color="#888888"><div>
<br></div><div>-Brian Knight</div></font></span></div>
<br></div></div><div class="im">_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></div></blockquote></div><br></div></div>
<br>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div>