Tried on v17 – partially works but hangs for me when it starts to draw. The module.xml references version 12 of FreePBX. What versions have you developed it with ?
Thanks.
It may hang for a second if you have a lot of inbound routes as it’s reading the destination information each time.
You can disable the destination column in the Options which will only read inbound routes.
I thought the supported version referred to the minimum.
I have multiple versions that I test with, including 17.
Actually tested it in a fresh VM with nothing eg. no routes – separate error there missing a variable, raised it on GitHub for you – but even with a route and a basic IVR with one option, it spun. Maybe it didn’t like starting out with no routes and that clobbered something else (?)
Pretty much. It is described in the docs as what the server sends you based on your minimum version of FreePBX, but, if you are side-loading modules sans server, then it does seem to have a different meaning in practice. (A future author of a FreePBX module.xml DTD might consider this in more detail and maybe include a maximum version as well. Digressing further, you could have a git branch for 16, another git branch for 17, etc. See for example the “supported” lines in the framework v16 module.xml vs. the framework v17 module.xml).
Issue raised is resolved.
Let me know if it is drawing any quicker.
A normal dial plan should not take longer than a second.
More complex, maybe 2 to 4 seconds.
Many others have already expressed their thanks, but I figured it wouldn’t hurt to add mine! Thanks! It works much better than the previous module. Being signed is also a huge plus.
I always had trouble with cpviz failing on a route that was set to match any inbound route, but that is fixed on this version.
w00t! Got it to stop spinning and show me some graphics!
Did an uninstall/reinstall, but then when that still was spinning, opened up a debugging, in-browser Web Developer Tools Console – hit reload, and poof – there’s a pretty picture. And then another. And another
Will try to reproduce on another brand new VM soon. Seems like an initialization issue…
You can clear that message if the signature status in Module Admin shows Good.
If it shows anything else, you should uninstall, remove the module, then upload file or download from link and start fresh.
Also, you’re welcome. I’m glad that it is working for everyone.