I just installed the v17 beta on Debian 12. Yay! I love Debian, so this is good to see (for me at least).
Only issue is that dynamic routes is not yet available as a module on v17. Is there a roadmap that I can use to see when features/modules will become available? I am not needing this for production, so no dire emergency.
I believe this is a community maintained module iirc. That means someone will have to submit a patch. I think there is enough usage of this that someone will.
I reached out to the maintainer and heās aware that 17 exists and that dynroute ver. 16.x is not currently working on FreePBX 17.
Cloning 17 from the repo above, and browsing to the dynroutes page shows this error:
SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens
File:/var/www/html/admin/modules/dynroute/Dynroute.class.php:83
Thanks for this. I did check before asking here. I clicked on the issues link in the module and it went nowhere, then I went to the fork and there was no issues link.
The links you posted here work fine. Not sure how you got there though.
I posted up 2 issues I found. One is a missing field on the dynamic routes data entry form and the other is WRT calling agi scripts.
@kgupta told me to check my PHP code from the command line as v8 is stricter, but I had already done this. I created a new script with two active lines. These were to instantiate an AGI object and then to do an AGI->verbose(āHello Worldā). This script failed also.
Kapil has closed my ticket, so I suppose until someone with more programming cred than I reports it, it might stay broken.
<?php
// set up AGI env
include("phpagi.php");
$AGI = new AGI();
$AGI->verbose("Hello world");
?>
It is resolved now. The PHP script worked from command line, but following @lgaetz directive to ensure the files do not have CRLF at ends of lines, I downloaded the files to my Windows PC and used Notepad++ to ensure all lines were in Linux format (LF only). I then uploaded that back to the server with SCP and the script ran from AGI OK.
I blamed Nano editor, but I created a small test file in nano and did a hexdump on it. This confirmed it was only adding LF to the end, so I can only assume that when transferring the scripts from the old v16 server to the new v17 server, I somehow allowed Windows to modify the files.