When I try to add our Vega Gateway I click on Add Gateway, type in the IP, username, password and click click Discover and I get the following error.
Error:Undefined index: ip File:/var/www/html/admin/modules/vega/includes/VegaGwInterface.class.php:179
If I hit discover it does not find it, if i type the password wrong it tells me bad password so I know its seeing it. I can log into the Vega via IP with no issues. What am I missing?
I found the Vega module unhelpful and stopped using it. Firmware updates didn’t work and the provisioning is too simple, missing many important settings. If you have to edit the provisioning file by hand then it seems pointless. I managed a Vega through its web interface until eventually moving to a better gateway.
Ok, I Think there is a bug so. @kgupta Can you check please.
@billsimon I have never used this module in my life. Anyway, this module is commercial and if there is a bug in it, it should be fixed as well.
Why not improve this module by the way.
I know we have worked with Vega 50 and 60. They are not too expensive and work well.
It would make some sense for Vega provisioning to be worked into EPM, except that the provisioning method is a clunky SSH-and-paste-the-config session.
As for the iSymphony module, weird to deprecate the connector (which syncs PBX config to iSymphony) while still selling licenses for iSymphony itself.
The HA has been replaced by Advanced Recovery.
iSymphony, their support is not efficient. You paid, and next, there is no service.
I know lot of clients who paid a support and no serice.