Call Parking with Parking Pro

FreePBX 17, Asterisk 22.8.4 (certified), core 17.0.18.56
parking 17.0.2.10
parkpro 17.0.1.6 (17.0.1.7 is listed as available but Module Admin says up to date and won’t download it, even with --edge)

Symptom
After patching PHP and running fwconsole ma upgradeall, direct-to-slot parking stopped working. A blind transfer to a slot (e.g. 71) hangs up and the caller hears “I’m sorry, there is no call parked here.” Parking with ##70# still works, which is our workaround for now. No park button is in use, only transfers to the slot number.

What I found
This matches issue #1080 (Parking Pro suppresses the FREEI-2850 fix in base parking), and it’s related to #1074 / the “One touch BLF parking broken after update to parking v17.0.2.7” thread.

A call trace of a blind transfer to slot 71 shows:

  • The call goes to from-internal-xfer-dest and runs Dial(Local/71@from-internal-xfer/n,HhTtr)
  • macro-parked-call is then entered on the Local channel with args (71,parkinglot_2)
  • BLINDTRANSFER and ATTENDEDTRANSFER are empty there, so step 5 doesn’t jump to attemptpark
  • PARKIE is empty, so it plays pbx-invalidpark and hangs up

freepbx*CLI> dialplan show from-internal-xfer-dest
[ Context ‘from-internal-xfer-dest’ created by ‘pbx_config’ ]
‘50’ => 1. Set(CHANNEL(parkinglot)=parkinglot_3) [extensions_additional.conf:10095]
2. Goto(from-internal-xfer,50,1) [extensions_additional.conf:10096]
‘60’ => 1. Set(CHANNEL(parkinglot)=default) [extensions_additional.conf:10089]
2. Goto(from-internal-xfer,60,1) [extensions_additional.conf:10090]
‘70’ => 1. Set(CHANNEL(parkinglot)=parkinglot_2) [extensions_additional.conf:10092]
2. Goto(from-internal-xfer,70,1) [extensions_additional.conf:10093]
‘h’ => 1. Hangup() [extensions_additional.conf:10110]
‘#X*.’ => 1. Dial(Loc@from-internal-xferl/${EXTEN*@from-internal-xfer@from-internal-xfer*/n,${DIAL_OPTIONS}) [extensions_additional.conf:10107]
2. Hangup() [extensions_additional.conf:10108]
‘**X.’ => 1. Dial(Local/${EXTEN@from-internal-xfer@from-internal-xfer/n,${DIAL_OPTIONS}) [extensions_additional.conf:10104]
2. Hangup() [extensions_additional.conf:10105]
‘_X.’ => 1. Dial(Local/${EXTEN@from-internal-xfer@from-internal-xfer/n,${DIAL_OPTIONS}) [extensions_additional.conf:10101]
2. Hangup() [extensions_additional.conf:10102]
‘_X’ => 1. Dial(Local/${EXTEN@from-internal-xfer@from-internal-xfer/n,${DIAL_OPTIONS}) [extensions_additional.conf:10098]
2. Hangup() [extensions_additional.conf:10099]
Include => ‘from-internal-xfer-dest-custom’ [pbx_config]

-= 8 extensions (15 priorities) in 1 context. =-

php -r “require_once(‘/etc/freepbx.conf’); var_dump(function_exists(‘parkpro_get_config’));”
bool(true)

Questions

  1. Has anyone with Parking Pro active gotten direct-slot transfers working again, and if so how?
  2. Does Parking Pro 17.0.1.7 contain a fix? I can’t pull it, so I can’t test.
  3. Is there a supported fix planned for the bypass logic being skipped when parkpro is loaded?

Disabling parkpro is listed as a workaround in #1080, but this customer uses multiple lots, so that isn’t practical. I also have about 12 other boxes running FreePBX 17. I checked with one customer who matches software versions and they can park fine. They do not have Park Pro installed though,

Additionally, Park and Announce is still working properly for this customer. It is just when a user tries to park direct-to-slot that it fails. Maintenance support has been renewed for Parking Pro and Paging Pro

Downgrading core to 17.0.18.49 seems to have resolved it for now to where they can function properly.

fwconsole ma downloadinstall core --tag 17.0.18.49
fwconsole reload

I’ll confirm that this has been an issue since Sept 2026

Call PArk Malfunctions - Commercial Modules - FreePBX Community Forums

I agree, you can downgrade the core to that version; however “parking” and “parkpro” will show they are dependent on core 17.0.18.51 or higher.

Right now, just to make sure dependencies are correct, I’ve downgraded parking, parkpro and core to the following versions:
fwconsole ma downloadinstall core --tag 17.0.18.50
fwconsole ma downloadinstall parking --tag 17.0.2.3
fwconsole ma downloadinstall parkpro --tag 17.0.1.5
fwconsole reload

That then fixes our parking issue for us. If you upgrade past core 17.0.18.50, it will not playback the parking lot number they were transfered to.

Just in case others have this issue. I thought it was resolved with parking 17.0.2.10, but that isn’t true on our system:

Chris

Thanks for that. We were having some weird issues still but only for those customers with parkpro and pagepro.

My client originally called about regular parking lot not working. Got that working, but then realized they used parking pro. A call would come in and be parked on 71. It would still announce but it would light up park 72 and announce the call. It would not let them pickup before the announcement and blf cleared.

Rolled back to your versions and I think it is back to normal. I rarely use those modules but the few that do have similar issues as this particular client (who is now fixed hopefully).

Downgraded to the versions you mentioned and it seems to be working. Do you typically have to wait for the announcement to finish before picking up the call? If I press the red BLF 71 slot before the announcement it transfers the parking lot to the caller and they hear “sales call holding on 71” and not the actual phone.

Downgrading broke regular direct to slot parking again. Transfers to the caller and the caller hears im sorry there is no call parked here.

Sigh

I’d have to test, it on our setup. Most our phones are setup with just a Parking button. I do have some staff that have the individual parking lots mapped, so I’ll have to test and see.

And in regards to picking up the call, I don’t believe you have to wait. From what I remember it shows up in the queue once you push it. We don’t use Park and Announce, we just use regular parking, so that may be different from the park and announce option.

I’ll have to open a ticket with Sangoma at this point. Based on the release notes, it looks like it tries to play the announcement and just disconnects the call.

We’re having a similar issue with some queues, where staff are stating that when they answer the call it disconnects, like it isn’t transferring the call to them. So, may be a similar bug potentially. We’re running Asterisk 22.10.1, as we tried 22.11.0 and ran into some bugs. So we did downgrade to 22.10.1 and running those modules I put in the previous post.

Chris

Ok, maybe we have ours setup a little different. On some of our receptionist desks, we have it setup where they have the 3 parking lots mapped via BLF. It will turn red when there is a call in the parking lot. Now, I had them test (and they already said they haven’t had issues) and when they push the button, it just puts me in that parking lot.

So in our case, we have the parking lot number as 6900, then I have individual button programed to the individual slots, so 6901, 6902, 6903. If they have me on the call and push the BLF for 6901, it just puts me on hold and I show in the parking lot.

Now, this is with the versions I posted above, so not the latest version.

Right now, everything is working as we’re expecting.

I’m going to open a ticket with Sangoma support about the latest modules, as I will confirm if we update, then when we use just the Parking button, it will sound like it starts to play the slot number, but then disconnects the call.

Chris

Looking through the forum, there are a good amount of relatively-recent threads about unexpected parking behavior. This bit us too. I think there might have been changes in base Asterisk parking routines, which as a result changed how FreePBX parking modules behave (both paid and free modules).

For us, going back to going live in 2018 it’s been pretty straightforward. One parking lot 70 with park slots 71-78 for it. Our front desk receptionist runs the Flash Operator Panel 2 web app for visually managing calls. For a caller that needs to be parked, the receptionist would just press the blind transfer feature code on the desk phone while the caller is on the line with them (i.e. - ##70#). After they completed that, the park slot number would be read back to the receptionist and they could see the parked call in FOP2. The desk phone wanting to pick up the call would just hit the speed dial button for pickup and dial the park slot. No BLF buttons for anything to do with parking.

With a recent combination FreePBX and Asterisk update, the park slot wasn’t being read back to the receptionist. Otherwise the call behavior was the same. Folks on here stated that the park slot should’ve never been read back in the first place, seeing the receptionist party was already disconnected from the call after blind transferring. All I know it is was working this way for 8 years. :grinning_face:

For us at least, our solution was to ditch the blind transfer feature code, in favor of the supervised transfer feature code for parking the calls. Then the park slot is read back as expected. And we added BLF buttons on the receptionist desk phones for the park slots, as another level of redundancy alongside FOP2.

Long story short is when it comes to parking, there is more than one way to skin a cat. Between feature codes, speed dial, BLF, etc. we were able to pivot once the behavior changed. Not the best situation due to it being somewhat unexpected though.

For us, we’ve had the same setup since 2018. And we have it programmed to use the “Park” app. Before the update, if they push “Park”, it would move the caller to the queue and playback the slot number to the receptionist. Now, it just transfers the call.

This gave us one button that they could park a call and also look at the parking queue. If we change that, we will have to use another button, one for Parking and one for the Parking Lot listing.

I agree, this wasn’t expected. I have a ticket open with Sangoma support.

Chris