Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parking #20

Open
tbagwell opened this issue Oct 8, 2019 · 3 comments
Open

parking #20

tbagwell opened this issue Oct 8, 2019 · 3 comments

Comments

@tbagwell
Copy link

tbagwell commented Oct 8, 2019

  1.  Want to know when you coming out with the new core. When you go to download the modules. It show a parking and recording updates. But when you try to download them. you will come back with that error. There isn't a 		module update to 2.11.0.48. The last one we have is 2.11.0.47. So what I was wondering when are they going to post the update 2.11.0.48.
    

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.

  1. Will the new parking also have park to station in it like was build into freepbx 12?

  2. Here is the parking bug that I have seen.

https://forum.issabel.org/d/2472-bug-in-parking-bug-problem
IssabelFoundation/issabel#43

This is a big problem in the parking coding.
I Did make an Issues also over at IssabelFoundation/issabel#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.

@asternic
Copy link
Contributor

Hi,

I made some updates on commits 97dd480 and 633c7f2 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
Copy link
Author

tbagwell commented May 3, 2021

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
Copy link
Author

tbagwell commented May 3, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants