Shared Park from mobile v20

Status
Not open for further replies.

treynolen

Gold Partner
Advanced Certified
Joined
Feb 14, 2019
Messages
42
Reaction score
2
In the past, we've created "dummy" extensions which forward to SP1, SP2, etc. so that a user can dial the extension number to utilize shared parks from the mobile app. For example, 501 may forward to SP1, 502 to SP2, etc. This has worked well, but seems to have stopped working upon upgrade to v20. I've tried making the dummy extension a user in the department and assigning the receptionist role, but dialing the extension always results in a "not found" error.

What is going to be the recommended way to utilize shared parks from a mobile device in v20? I am familiar with parking orbits, and am not talking about that. Our users want to utilize shared parks.
 
You should use Parking Orbit for parking calls via dial codes with mobile apps:

To park a call:​

BLIND Transfer Button followed by *00 to 09 to specify the parking orbit.
For example, *01 will place the call in the parking orbit 1.
*02 will place the call in the parking orbit 2.

To pick up a parked call:​

*10 to 19 where the 0 – 9 is the park orbit number
For example *11 will pick up any calls parked in parking orbit 1
*12 will pick up any calls parked in parking orbit 2
 
As I mentioned, we are familiar with the parking orbits, but our users prefer to use the shared parks because of being able to see this on the BLFs.

So, are you saying this is another feature we lose in v20?
 
  • Like
Reactions: treynolen
Parking orbits have other issues, like accidental joining of customer calls if someone isn't careful. That isn't possible with SP today...
 
  • Like
Reactions: Evolute IT
Parking orbits have other issues, like accidental joining of customer calls if someone isn't careful. That isn't possible with SP today...
Actually it is...if a call is parked in SP2 and someone uses the above to transfer a call to SP2 then they will talk to each other. Which is another reason why BLFs are important for the mobile apps... Using dummy extensions is not ideal for that reason but it was a bit easier for users to transfer to or pick up from an SP without dialing in upper case.
 
  • Like
Reactions: EmmettsIT
Actually it is...if a call is parked in SP2 and someone uses the above to transfer a call to SP2 then they will talk to each other. Which is another reason why BLFs are important for the mobile apps... Using dummy extensions is not ideal for that reason but it was a bit easier for users to transfer to or pick up from an SP without dialing in upper case.
I've heard people state this before, but I could never replicate. Also, per 3CX, it's not designed to do that. I'll provide the following screenshot and URL to back this statement up - 1 person per room.

1702431798647.png

https://www.3cx.com/blog/docs/call-parking/
 
  • Like
Reactions: Evolute IT
Last edited:
  • Like
Reactions: SweetAction
I'm glad someone remembered...

And yes, while I use Dummy exts, I know that any issues from them to not file as a bug report, hence why I keep forgetting that issue.
 
:) Unfortunately from the mobile app one cannot type letters to dial an SP slot. One can type it elsewhere, and copy/paste, which is not that handy... So, if you are next to a PC you can use the web client to unpark, otherwise a co-worker would need to pick up and transfer the call to you.
 
I'm finding this thread the day after I've upgraded to v20. It's a major problem for us, as all of our clients use the "phantom" extensions for accessing parking spots with their cell phones. I'm hoping it gets reintroduced soon.
 
  • Like
Reactions: SteveITS
Well won't we all have to move to v20 soon?
 
Did someone reproduce this issue with V20 RC3 ? Still failing dialling SPx ?
Thank you !
 
Thank you @Vali_3CX for your reply !

Does it also work from the IPBX itself ?
There were reports that (dummy) extensions having transfer rules to SPx did not work/transfer anymore with V20.
Does V20 RC3 correct this ?

Thank you again !
 
@benrg
I checked and it's on work, but I cannot give you an ETA.
 
At least good news, thank you very much @Vali_3CX !
 
  • Like
Reactions: Vali_3CX
Did our first client upgrade this weekend and found the same issue. Will be holding off on upgrading the rest until this gets cleared up.
 
  • Like
Reactions: Jay K
@stressless As per my colleagues @Vali_3CX mentioned this is on the road but cannot provide any ETA when it will be released.
 
  • Like
Reactions: JuanR_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,972
Messages
590,068
Members
164,888
Latest member
Tim Cook