<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>Aastra/Mitel work well in a key mode emulation.. 9 line keys and support for SCA .. Thousands deployed and work great<br>
<br>
Sent from my iPhone
<div><br>
</div>
<div>Todd Wolf</div>
<div>President / COO</div>
<div>Unified Technologies</div>
<div>212 Canco Road</div>
<div>Portland, ME 04103</div>
<div>(207) 956-6402</div>
<div><br>
</div>
</div>
<div><br>
On Aug 18, 2014, at 5:26 PM, "Joshua Elson" <<a href="mailto:joshelson@gmail.com">joshelson@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">SLA/SCA functionality, if that's what desired, on the VVX line is spotty at best and is not supported at all on Asterisk/Switchvox, at least not in the way your users will likely expect. At worst, it just simply doesn't work. Not to mention
that the VVX phone performance has been... let's call it "questionable," to put it mildly. We've deployed many hundreds of them and we see pretty consistent complaints about laggy touchscreen performance and we get random reboots followed by core dumps from
the phones on our provisioning infrastructure dozens of times every week. If you're looking for key system features and thinking of using the VVX expansions, they barely work (and ONLY on the latest 5.x software), and really don't work as advertised with
provisioning.
<div><br>
</div>
<div>If "true" SCA/SLA type functionality is a must, you're pretty much stuck with Linksys SPA, Snom, or legacy Polycom Soundpoint lines on a Broadsoft-based switch. Of course, there's almost no real need for the key system if people are willing to holistically
look at how they use the phones, but that's a whole different batle...</div>
<div><br>
</div>
<div>Just my $.02.</div>
<div><br>
</div>
<div>Josh</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Aug 18, 2014 at 3:58 PM, Colton Conor <span dir="ltr">
<<a href="mailto:colton.conor@gmail.com" target="_blank">colton.conor@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 dir="ltr">Can anyone recommend an onsite IP PBX that fully supports the Polycom VVX series of phones? When I say support I mean auto configure, do firmware updates, etc...I know most all IP PBX's will at least be able to use the VVX as a SIP extension.
<div><br>
</div>
<div>The clients wants to emulate a key system. The IP PBX should support SIP trunks of course for connection to the PSTN. The client also wants the ability to use a local MoH source, paging, and other common key system features that hosted systems don't do
very well.
<div><br>
</div>
<div>I was thinking switchvox, but they don't have phone feature packs for the VVX line only the older phones.</div>
<div><br>
</div>
<div>Adtran has the 7060, but according to the latest release notes:</div>
<div><br>
</div>
<div>
<div>ADTRAN branded VVX phones (model names ADTRAN VVX 300, ADTRAN VVX 310, ADTRAN</div>
<div>VVX 400, ADTRAN VVX 410, ADTRAN VVX 500, and ADTRAN VVX 600) work with NetVanta</div>
<div>7000 series AOS release version R10.8.0 and beyond without requiring an additional license key purchase.</div>
<div>The equivalent Polycom branded phones will not work with release R10.8.0. If you are currently using the</div>
<div>equivalent Polycom branded phones with the NetVanta 7000 series, you will need to either remain on a</div>
<div>pre-R10.8 release version or use the ADTRAN branded version of the VVX phones until a licensing</div>
<div>mechanism can be added to allow the use of Polycom branded VVX models.</div>
<div><br>
</div>
<div>Looks like that won't be a good option since the client already has regular Polycom VVX phones not the ones with Adtran's badge on them. </div>
<div><br>
</div>
<div>Any recommendations?</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</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>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>VoiceOps mailing list</span><br>
<span><a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a></span><br>
</div>
</blockquote>
</body>
</html>