Summary:ASTERISK-18653: Parking Slot Number Not Being Cleared
Reporter:David Cabrejos (drcabrejos)Labels:
Date Opened:2011-10-03 10:25:08Date Closed:2011-10-03 12:27:51
Versions: Frequency of
Environment:Attachments:( 0) parkedcalls_show_log.txt
Description:Installed asterisk version since this release had finally a fix from a previous bug I had opened [17183] which solved multiple parking slots being redirected to the wrong parking lot.

Now, I'm being faced with an issue on which the parking slot number is not being cleared anymore.

An example with 3 users (A, B, C) will be explained:

- User A calls User B.
- User B parks User A by dialing 700
- User A is parked in parking slot number 701
- User C picks up parked call by dialing 701
- User C and User A hangs the phone   <--- PARKING LOT 701 DOES NOT SHOW IN 'PARKEDCALLS SHOW' ANYMORE (Expected)
- 1 hour later... (or any time later)
- User A calls User B.
- User B parks User A by dialing 700
- User A is parked in parking slot number 702   <--- SHOULD HAVE BEEN IN 701 (Not expected)

Issuing "parkedcalls show" in asterisk, it shows that there is no calls being parked after users hang up the phone, as expected, however it will not clear the parking lot number.

It will only park again in parking slot 701 after parking lot 710 is reached.
This is not a normal behavior.

In features.conf:

context => parkedcalls-test
parkext => 700
parkpos => 701-710
parkingtime => 120
findslot => next

Please let me know if you need any outputs or more information about this bug.

I'm attaching the logs of the calls just in case with the outputs of 'parkedcalls show'. I'm only displaying the test parking lots, not all of the ones I currently have on my system.

Thank you,

David Cabrejos
Comments:By: David Cabrejos (drcabrejos) 2011-10-03 10:28:06.989-0500

This is the log of what happened in the example process explained in this bug, with the "parkedcalls show" command being displayed throughout the process.

By: Richard Mudgett (rmudgett) 2011-10-03 12:11:34.269-0500

This is the expected behavior because you have "findslot => next" configured.

The parking fixes made the findslot option actually work again.

By: David Cabrejos (drcabrejos) 2011-10-03 12:26:26.103-0500


Thanks for the info. I guess I was used to having that option enabled and broken.

I just removed the option and everything is working out as it used to work for me.

Closing this issue! Thank you!

By: David Cabrejos (drcabrejos) 2011-10-03 12:27:51.973-0500

Problem was fixed and it was a configuration problem.

'findslot => next' had to be disabled for what I was looking for.