I asked for and received the http:/192.168.1.210:50003/launch.jnlp
after configuring the client, isymphony reports ‘server does not have a connection to asterisk’
their forum documents that error means it is a credential problem in the AMI.
I only see admin as a manager and the manager_custom.conf is commented out in manager.conf.
What gives?
I am running aastra-scripts and it seems to be okay despite their credentials residing in the commented out custom.conf.
In further pursuit for a solution to my iSymphony credential issue,
I created a new virtual machine with 1.87.210.57
During the install process of both 1.88 and 1.87 I received a red warning meesage multiple times something to the tune of :
"bad kmod package ‘kmod-bnx2i-PAE-rhel5u7-2.7.0.3-1.e15_7.i686’ does not require a kernel " I wish I could be more precise, but the ongoing installation screen kept corrupting the red error output.
Both installations continued to completion.
1.87.210.57 accepted the FreePBX first time admin credentials and then when trying to login ‘No direct script access allowed’ from config.php.
1.88.210.57 I can continue on to my original issue ‘iSymphony server not connected to asterisk.’ I will update this thread after resolving the iSymphony issue with Mike at i9. No other apparent issues.
It appears their latest module is not putting in the manager settings like it use to. I have informed Mike and Art of the issue.
To fix your problem go into FreePBX GUI and under settings section click on Asterisk API and create a new API connection.
Username is isymphony and password should be ismanager*con.
In deny put 0.0.0.0/0.0.0.0 and allow put 127.0.0.1/255.255.255.0
Than select all for read and write. Save your changes and apply them and it should work. You might need to reload iSymphony with service isymphony restart