<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Metaswitch but as its not really media handling it isnt terribly
relevant. <br>
<br>
The latest Oracle SBC;s will transcode Opus as will many software
platforms (Freeswitch, Frafos, etc)<br>
<br>
<div class="moz-cite-prefix">On 12/5/2015 9:15 AM, Colton Conor
wrote:<br>
</div>
<blockquote
cite="mid:CAMDdSzM2uzRH3Ut0-Bnn4gYB5E6-iaPxx4DvGyp5V67_WBAyvA@mail.gmail.com"
type="cite">
<div dir="ltr">Ryan,
<div><br>
</div>
<div>What voice platform are you using with OPUS? </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Dec 3, 2015 at 12:42 PM, Ryan
Delgrosso <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ryandelgrosso@gmail.com" target="_blank">ryandelgrosso@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Anthony,<br>
We do this pretty frequently with a high success rate. It
really depends on the site size and usage patterns.<br>
<br>
A couple of things to keep in mind:<br>
<ol>
<li>If its a 1-2 user remote office the service profile
is realy no different than a residential user. Deploy
accordingly. <br>
</li>
<li>For higher user density sites we usually will deploy
some kind of edge router (edgemarc / simplewan etc). A
small amount of QOS at egress goes a long way on
asymmetrical connections. <br>
</li>
<li>Abandon G711 where possible for a FEC codec (Opus is
my weapon of choice). A tiny amount of packet loss or
jitter on Opus makes zero difference. A larger amount
of packet loss, which would generate clicks and pops
on G711 will not be as noticable over Opus (and still
sound superior to most cell conversations. If
necessary transcode at edge to support this. <br>
</li>
<li>Abandon standard ports. This is really more about
avoiding psuedo-intelligent ALG's in the path for the
1-2 user sites.<br>
</li>
<li>Be reasonable. Nobody is going to (ok some will try
but it should be advised against) run a 200+ user shop
on adsl. <br>
</li>
</ol>
I'm happy to discuss in more depth offline if you have
specific questions<span class="HOEnZb"><font
color="#888888"><br>
<br>
-Ryan <br>
</font></span><span class=""> <br>
<div>On 12/2/2015 2:25 PM, Anthony Orlando via VoiceOps
wrote:<br>
</div>
</span>
<blockquote type="cite"><span class="">
<div
style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida
Grande,sans-serif;font-size:16px">
<div dir="ltr">Is anyone having success deploying
HPBX over DSL? Not service providers that own the
plant but those of you using another providers
DSL. Have you been successful? If so what were
the engineering guidelines you used? What were
the tolerances you used? Any feedback would be
very welcomed.</div>
</div>
<br>
<fieldset></fieldset>
<br>
</span><span class="">
<pre>_______________________________________________
VoiceOps mailing list
<a moz-do-not-send="true" href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a>
<a moz-do-not-send="true" href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</span></blockquote>
<br>
</div>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a moz-do-not-send="true"
href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/voiceops"
rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>