nicknomo
Happy-IT-Guy
- Joined
- Mar 5, 2009
- Messages
- 63
- Reaction score
- 12
I'm not seeing the search this thread tool... so forgive me if this was already asked. The park.php script works perfectly for our systems, except for one major flaw (for us at least). It displays all parked calls. We use ParkingPro from Schmooze and certain phones can only park or retrieve calls from a give parking lot. In looking at the code in this script, I can say that I for sure do not know how to easily change the script to retrieve parked calls in the context (created via the ParkingPro module from Schmooze) that that extension only has express permission to use.
I would be glad to give any information on the context or conf files you may need, but unfortunately it is for sure displaying parked calls. Just all parked calls across all parking lots - we have 5.
I have been working on a YealinkV70 (firmware v70, v71, v72) provisioner package for Yealink T2x, T3x, T4x, VP530 devices and have almost everything working. I will have this package ready to go and updated at github for Andrew Nagy to hopefully approve and pull into the main code as another brand package (Yealink V70). My only hold up here is I really wanted to have a visual parking functionality that is compatible with ParkingPro to show parked calls for an extension's given default parking lot. If this isn't easily doable in the next few days I will just not include this functionality and merge it in later at github.
UPDATE: I found that the separate parkinglot names appear in AMI when typing Action: parkedcalls. I then also found under extensions_additional.conf that there is a new context for each extension, referring to which lot to park calls. There may be a way to create an entry in the provisioner to create a PHP script for each extension called park_$mac.php, query that extension's parkinglot assigned and only show the information relevant to that specific parking lot. But the AMI commands / PHP scripting goes beyond my abilities. I can help with the provisioner side, but need some assistance to be able to provision something like this to be compatible with the Parking Pro module.
-Jon
Well, the dirty way would be to hardcode it into the park script. Make it so that the park.php script only lists the calls for that parking lot, then make as many variants of the park script as there are parking lots. If you have two parking lots (e.g. 71-79 and 701-705), then you'd need two park scripts (one for each parking lot), and you'd have to assign them to the correct phones.
That is the best I can come up with that wouldn't take a lot of effort..