Open tbagwell opened 4 years ago
asternic
commented
3 years ago Hi,
I made some updates on commits 97dd4800c4d83ac2f9ed98b84a13910b0f46e124 and 633c7f22d0dc395b374404349470ee1730304d3f on issabelPBX to work on the parking issues. IssabelPBX release 49 will be uploaded into issabel-beta repository if you want to test it out and report back. Thanks,
tbagwell
commented
3 years ago I gave tested what you have put in. I made a new parking lot.. And put some ext into that lot.. I can use the g-park for that lot. And it will light up that button for the park location. but when you try to answer it. It come back with there isn't a call in that lot.
Also can you make it where you can transfer a call right to the lot.. Like gpark is 700.. And the lot is 701.. What I would love to see is that you can put it right to lot 701 without using the 700.
tbagwell
commented
3 years ago I also notice that you can use the other parking codes also. But if you it will put the call back into the park lot that you are set to or back to the default parking lot if you are not set to a lot
When will the new IaaabelPBX and Core coming out. Wanting to test the multi parking lot that the notes say that it should have.
Parking Lot cannot be upgraded:
IssabelPBX version 2.11.0.48 or higher is required, you have 2.11.0 Core module version 2.11.0.48 or higher is required, you have 2.11.0.47
Please try again after the dependencies have been installed.
Will the new parking also have park to station in it like was build into freepbx 12?
Here is the parking bug that I have seen.
https://forum.issabel.org/d/2472-bug-in-parking-bug-problem https://github.com/IssabelFoundation/issabel/issues/43
This is a big problem in the parking coding. I Did make an Issues also over at https://github.com/IssabelFoundation/issabel/issues/43 I am just posting it here to try and make sure it happen to get looked at. This bug is in every running system that has been change to using the res_parking_additional.conf for the park info.
The normal setting for the Parking is 700 by default. If it happen to be setup for 700 with slots 701-703. It will save the info into the extensions_additional.conf and res_parking_additional.conf
res_parking_additional.conf parkext=700 parkpos=701-703 context=parkedcalls parkext_exclusive=no parkingtime=150 comebacktoorigin=no parkedplay=both courtesytone=beep parkedcalltransfers=caller parkedcallreparking=caller parkedmusicclass=default findslot=first Now if we do a command feature show. We happen to see this. Call parking (Parking lot: default)
Parking extension : 700 Parking context : parkedcalls Parked call extensions: 701-750 Parkingtime : 45000 ms Comeback to origin : yes Comeback context : parkedcallstimeout (comebacktoorigin=yes, not used) Comeback dial time : 30 MusicOnHold class : default Enabled : Yes
how if you look at the Parked call extensions line. You will see the system say that the slots are from 701-750. When it show be 701-703
How this is where the problem come in. If change the lot to 800 with slots 801-803. And saved We can see in the file res_parking_additional.conf it has been update. parkext=800 parkpos=801-803 context=parkedcalls parkext_exclusive=no parkingtime=150 comebacktoorigin=no parkedplay=both courtesytone=beep parkedcalltransfers=caller parkedcallreparking=caller parkedmusicclass=default findslot=first If we run a feature show command again. We will see this. Call parking (Parking lot: default)
Parking extension : 700 Parking context : parkedcalls Parked call extensions: 701-750 Parkingtime : 45000 ms Comeback to origin : yes Comeback context : parkedcallstimeout (comebacktoorigin=yes, not used) Comeback dial time : 30 MusicOnHold class : default Enabled : Yes
Also if try to park into 800 now it will recall the call back to the ext without even parking. If you take what is in the res_parking_additional.conf into the features_general_additional.conf Do a reload and it will show the right parking info.
So all in all it looks like the system isn't loading any info in the res_parking_additional.conf file. So this is messing up the parking system if the lot has been changed.
you will have to copy the info from the res_parking_additional.conf into the feature_additional.conf file. And then make it where it can't be change. then it will load the info all right.