<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree with both Shripal and Peter E.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Local MOH source can be used with Broadworks as well. You will have to connect it using a ATA.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Kumudu<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> VoiceOps [mailto:voiceops-bounces@voiceops.org]
<b>On Behalf Of </b>Peter E<br>
<b>Sent:</b> Tuesday, April 14, 2015 9:34 PM<br>
<b>To:</b> Shripal Daphtary<br>
<b>Cc:</b> voiceops@voiceops.org<br>
<b>Subject:</b> Re: [VoiceOps] Key System Using Polycom VVX<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I agree with Shripal, it is doable in broadworks. Depending on the model of VVX, though, your performance may vary. It seems they are using a lesser chip, probably to get the price down, and their performance suffers when hit with too many
simultaneous messages. So, a small SCA environment with small volume should work but a bunch of SCAs in a busy environment could be a problem, especially for the lower end of the VVX line.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We also try and break people of the key system habit whenever possible. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Apr 14, 2015, at 20:38, Shripal Daphtary <<a href="mailto:shripald@gmail.com">shripald@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">depending on the size, Colton, you should be able to emulate a key system with BWKS. i think i remember that you are bwks service provider right? I think broadsoft actually has a document related to creating a key (square) System. Basically,
the accounts you create are the lines, e.g. lines 1 through 4. Register each phone with the 4 Lines/accounts. Share the lines to each endpoint with SCA and then use series completion to ring sequentially through lines 1 through 4. i don't know how big this
implementation can get, but i'm assuming it would get annoying anything past 4-8 lines. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Shri <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Aug 18, 2014 at 5:58 PM, Colton Conor <<a href="mailto:colton.conor@gmail.com" target="_blank">colton.conor@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">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. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I was thinking switchvox, but they don't have phone feature packs for the VVX line only the older phones.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adtran has the 7060, but according to the latest release notes:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">ADTRAN branded VVX phones (model names ADTRAN VVX 300, ADTRAN VVX 310, ADTRAN<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">VVX 400, ADTRAN VVX 410, ADTRAN VVX 500, and ADTRAN VVX 600) work with NetVanta<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">7000 series AOS release version R10.8.0 and beyond without requiring an additional license key purchase.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The equivalent Polycom branded phones will not work with release R10.8.0. If you are currently using the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">equivalent Polycom branded phones with the NetVanta 7000 series, you will need to either remain on a<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">pre-R10.8 release version or use the ADTRAN branded version of the VVX phones until a licensing<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">mechanism can be added to allow the use of Polycom branded VVX models.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Any recommendations?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">_______________________________________________<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">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></p>
</div>
</div>
This communication (including any attachments) may contain privileged or confidential information of Alteva and is intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, you should notify the author and
delete this communication from your system, including any attachments. Any disclosure, copying, saving or distribution of this communication, or the taking of any action based on it, is strictly prohibited. Any views or opinions expressed are solely those
of the author and do not necessarily represent those of Alteva.
</body>
</html>