We are using "Shared Parking" on our systems (We have three). In 15.5 Update 6 (I think that's the correct version) - there appears to be an issue. (at least we didn't notice this before we applied the update.)
We run a bunch of the Yealink W52 Cordless phones. Since they don't have BLF, we have to create a separate dummy extensions, and that dummy extension forwards to the Share Parking slot. For example - if you dial 776, it forwards you to SP6 (Shared Parking 6), 770 goes to Share Parking 0.
Our corded phones are all Fanvil X6. Since they have BLF buttons, when the park slot is in use, the line turns red. So no one ever tries to park a second call into the same slot.
If a Cordless phone parks a call - it does turn busy on the Fanvil X6 phones' corresponding park slot.
When any phone parks calls to the SAME park slot using those "Dummy" extensions - (Cordless or Corded) the people in the PARK slots can talk with each other - like a conference call. (Our MOH Announcement is playing in the background). It even works with 3 or more people. Not just two.
Those dummy extensions never register (as designed). They are not setup for voicemail or multiple call handling. So it forwards instantly to the corresponding Shared Parking Spot. When I run reports - it shows those calls are parked in the correct spot, but then it shows more calls dropped in that slot (if you park multiple calls to the same spot while they are already in use).
I know the other type of park spot it supposed to allow multiple calls to be queued (Which is why we don't use them. There's no way to know which call in the slot your picking up. First in, last out and all) I have two other phone systems (neither on Update 6, but neither has cordless phones either)... so I am going to test and see what happens when I try it on a sub update 6 3CX system.
This doesn't seem as though it should be possible. (Shared Parking is set to forward any call that has been parked for 2 minutes to the operator.)
Greg
We run a bunch of the Yealink W52 Cordless phones. Since they don't have BLF, we have to create a separate dummy extensions, and that dummy extension forwards to the Share Parking slot. For example - if you dial 776, it forwards you to SP6 (Shared Parking 6), 770 goes to Share Parking 0.
Our corded phones are all Fanvil X6. Since they have BLF buttons, when the park slot is in use, the line turns red. So no one ever tries to park a second call into the same slot.
If a Cordless phone parks a call - it does turn busy on the Fanvil X6 phones' corresponding park slot.
When any phone parks calls to the SAME park slot using those "Dummy" extensions - (Cordless or Corded) the people in the PARK slots can talk with each other - like a conference call. (Our MOH Announcement is playing in the background). It even works with 3 or more people. Not just two.
Those dummy extensions never register (as designed). They are not setup for voicemail or multiple call handling. So it forwards instantly to the corresponding Shared Parking Spot. When I run reports - it shows those calls are parked in the correct spot, but then it shows more calls dropped in that slot (if you park multiple calls to the same spot while they are already in use).
I know the other type of park spot it supposed to allow multiple calls to be queued (Which is why we don't use them. There's no way to know which call in the slot your picking up. First in, last out and all) I have two other phone systems (neither on Update 6, but neither has cordless phones either)... so I am going to test and see what happens when I try it on a sub update 6 3CX system.
This doesn't seem as though it should be possible. (Shared Parking is set to forward any call that has been parked for 2 minutes to the operator.)
Greg
