We just upgraded to 9.1.2.37 and Call parking has changed pretty radically in Asterisk 13. We had a custom config for a large MTE tenant that wanted separate parking lots for each of its locations (but they all on Tenant in MTE. It appears to my Unix guy that the new asterisk parking lot module is commented out after the update.
Here are questions he has about it:
He created and empty parking config file
and was able to load the parking module.
* why was there no /etc/asterisk/res_parking.include created?
* is creating an empty file at that location an acceptable fix?
Is it expected behavior to comment out the new parking module on this update?
Doug
We think we figured out the
We think we figured out the issue and post this here as a question, but also in case others have had this issue... We DID have some custom stuff going on and the install MAY have been smart enough to figure that out, and not reference the below include. which is why we had to do this;
why didn't the upgrade add res_parking.include to
/etc/asterisk/extconfig.conf, to tell the plugin to get its config out of the
DB? The file was refreshed as part of the upgrade, but nothing was added to
it.
We added this to the /etc/asterisk/extconfig.conf:
"res_parking.include => mysql,pbxconf,ast_static_config"
We hope this is ok to do? Thirdlane?? It seems to have fixed the "no call parking on any tenant" problem we had with the upgrade.
Looks like none of our tenants have any entries in the DB for parking lots. Thirdlane?
Were were able to manually add them after rigging around the new module conf file and loading it,
Is this expected? What do we do for the rest of the tenants??
Fortunately, we don't have many, using parking. Advice Thirdlane?