I agree with both Shripal and Peter E.

Local MOH source can be used with Broadworks as well. You will have to connect 
it using a ATA.

-Kumudu

From: VoiceOps [mailto:[email protected]] On Behalf Of Peter E
Sent: Tuesday, April 14, 2015 9:34 PM
To: Shripal Daphtary
Cc: [email protected]
Subject: Re: [VoiceOps] Key System Using Polycom VVX

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.

We also try and break people of the key system habit whenever possible.



On Apr 14, 2015, at 20:38, Shripal Daphtary 
<[email protected]<mailto:[email protected]>> wrote:
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.

Shri

On Mon, Aug 18, 2014 at 5:58 PM, Colton Conor 
<[email protected]<mailto:[email protected]>> wrote:
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?




_______________________________________________
VoiceOps mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/voiceops

_______________________________________________
VoiceOps mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/voiceops
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.
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to