We just purchased 3cx along with Polycom 670 phones after testing with Grandstream 2010's and find their sound quality and reliability lacking. Everything is working great 3cx is functioning well and integrating much better into our CRM than our old system, and the Polycom's sound amazing and are extremely customizable and flexible with the built in microbrowser and very reliable so far.
We would like better support for all the Polycom's features and since it was mentioned 3cx would like to work more closely with Polycom, so I thought I would list everything we have found so far that is lacking:
1. Polycom presence/BLF. We are living without this key feature right now only because the 3cx Assistant somewhat makes up for it, but having to rely on the users PC when the phone has the ability is not a long term solution.
2. Server based DND. Polycom seems to have a option for the DND key to be server based, from what I can tell this only works with Broadcom. We are currently experimenting with remapping the DND to a *61 speed dial and having a *60 "Available" soft key, this is better but still clunky, at least if 3cx flip flopped Away/Avail on *61 or perhaps a special flipflop dailcode, the user could toggle their status with one key.
3. This relates to #1 and #2 and is not Polycom specific, although Polycom seems to have more presence statuses than ringing/busy. But having away/available affect phone BLF seems like an obvious omission, but when we where testing the Grandstreams with working BLF we noticed 3cx does not notify the phone when someone goes away, only ringing and busy.
4. Reject call handling. Polycom sends a 603 Decline response when the reject softkey is pressed on an incoming call, 3cx does not route this to VM like a 486 response. I know there is some debate about whether 603 is a correct response, but most other softpbx's seem to just accept this and route to VM.
5. Polycom directory management. Currently 3cx writes out a 000000000000-directory.xml for Polycom phones, this directory is only picked up when a new phone is initialized, after that the phone looks for a specific [mac-address]-directory.xml and even attempts to "put" this back to the provisioning server when a user edits their directory on the phone. This directory also has speeddials and buddywatch flags which could be very specific to the extension. I have seen some scripts to try and merge a master directory with a phone's directory to keep it up to date, it would be ideal if 3cx could manage this instead.
