[VoiceOps] Key System Using Polycom VVX

Adam Vocks Adam.Vocks at cticomputers.com
Mon Aug 18 18:11:25 EDT 2014

Switchvox 5.8.5 supports VVX phones.




We have a 150 user installation of switchvox 5.8.5 and vvx-410 phones.




From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton Conor
Sent: Monday, August 18, 2014 4:59 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Key System Using Polycom VVX


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. 


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.


I was thinking switchvox, but they don't have phone feature packs for the VVX line only the older phones.


Adtran has the 7060, but according to the latest release notes:


ADTRAN branded VVX phones (model names ADTRAN VVX 300, ADTRAN VVX 310, ADTRAN

VVX 400, ADTRAN VVX 410, ADTRAN VVX 500, and ADTRAN VVX 600) work with NetVanta

7000 series AOS release version R10.8.0 and beyond without requiring an additional license key purchase.

The equivalent Polycom branded phones will not work with release R10.8..0. If you are currently using the

equivalent Polycom branded phones with the NetVanta 7000 series, you will need to either remain on a

pre-R10.8 release version or use the ADTRAN branded version of the VVX phones until a licensing

mechanism can be added to allow the use of Polycom branded VVX models.


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. 


Any recommendations?




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20140818/73bf56f0/attachment.html>

More information about the VoiceOps mailing list