efounco wrote:The SNOM M9 works OK using the latest Firmware. Transferring and hold works fine with 3CX. However, we ran into a couple of issues involving ring-all groups with 3CX, SNOM M9 and SPA504G phones. Occasionally the phone would send a false disconnect signal to the server and disconnect the incoming call. The problem was intermittent and only seemed to be associated with certain incoming calls. We never "fixed" the problem but instead removed the SNOM M9s from the ring-all group. This eliminated the problem. As a standalone phone the SNOM M9 works fine (although not supported).
If you have an office environment, I would not recommend using wireless phones exclusively. Not only is the call quality lesser, transferring, parking and multi-line operations are much more difficult on a wireless phones. At the very least, get the operator(s) a nice phone with multiple BLF keys.
As for shared parking on a wireless phone, setup a group of virtual extensions inside of 3CX to dial an external number (500, 501, etc.). For the external number use SP0, SP1, SP2, etc. When you put a call into shared parking, simply dial the extension number associated with it from any phone and it will connect. You place calls into shared parking by simply transferring the call to the associated extension. BLF keys are nice to have for shared parking but not necessary...
Thanks for the detailed response - hopefully I can pick your brains a little more?
We provide 3CX on a hosted basis and all our clients are remote. The DECT phones on client sites are in the main a single phone for a user with a requirement to be more mobile than all other desk based users so they are not in exclusive use on a site for the reasons you specified.
Up to now we have been using M3's with up 4 handets on a basestation in some instances. What we have found is that the M3's often break - the handsets are very unreliable, which means we have to send out replacement handsets and then try and get the new handsets to talk to the existing basestation without being onsite - this has proven very difficult as the mechanism for pairing M3's is complex and far too much for our end users to follow and often requires multiple total resets of all handsets and the basestation to get them to work - again far too much for us to ask our remote clients to do.
We looked at the M9 as an obvious replacement but hit the call transfer bug with version 8 and havent looked at them since. Can you confirm call transfer (attended and blind) works with 3CX now (which versions do you use)?
Also what is the procedure like for pairing them with basestations and replacing/swapping handsets? Hopefully it's less complex than the M3. If it's still as bad we may have to look at either a Siemens Gigaset or Panasonic alternative, so if anyone has any expriences with those (good or bad) I'd be happy to hear them (especially in relation to pairing handsets to basestations and reliability of hardware).
Thanks
Paul