Hello, people of the past! Sorry for the gravedigging, but we have a local 3CX v15 SP3 set up, and everything is working pretty well. Most of my frustrations are things that I, tinkerer, want to fiddle with but there's no real way to fiddle with them. Oh, I'd also like to be able to feed in an external caller ID source like OpenCNAM. But, that's off-topic.
We're an IT company, and we quite like the notion of our technicians being able to bring their extension out into the field, and have used this already, and in this capacity, it worked fine.
The scenario I encountered the other day, however, I'm not sure how to deal with.
A technician in the field had called another firm (some manufacturer or service provider, etc.). Later, while he was still in the field, that firm called back in for him, but didn't have/didn't key in his extension. I took this call. Now, we ended up handling the situation just fine (one of our staff texted him almost immediately so he called the firm back), but it raised some questions. Typically, we park the call on one of our shared parking extensions, then intercom over to the other person, then they pick up the parked call.
As far as I can tell, the v14.0.57 Android (and iPhone, I believe) apps do not appear to contain BLF panels or any other immediately apparent means of accessing the parking orbits, nor any way that we could find to create speed-dials, so that users wouldn't have to remember the dial codes to access the parking orbits... assuming I could get that to work at all.
3CX shows dial codes of *0[orbit#] to park, *1[orbit#] to pickup. However, with a call parked in SP1, dialing *0[anything, or no orbit at all] results in "Forbidden", and *1[same] in "Not found."
The shared parking works perfectly fine on our Yealink phones, but I cannot for the life of me determine how to access any parking from our cellphones. Is there some way that we're missing to call up a BLF panel? And is the Shared Parking somehow separate from the dial-code parking orbits? Is there something I need to configure to enable the dial-code parking orbits, if so?
We've tried setting up an extension 101 that forwards to these, but it causes the same effect - either forbidden, or not found.
Really, the worst case scenario is that we teach our users to do attended transfers instead, but it would be absolutely capital if we could figure this out.