Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension Mobility cisco_service.ini AMI Issues #1

Open
jttri777 opened this issue Nov 13, 2020 · 0 comments
Open

Extension Mobility cisco_service.ini AMI Issues #1

jttri777 opened this issue Nov 13, 2020 · 0 comments

Comments

@jttri777
Copy link

Hi,

Everything working now, however after an upgrade from FreePBX 13 - 15 I was getting a "HTTP Error [500]" message on my Cisco phones when pressing the services button. I went into the cisco_service.ini file and commented out the amportal file. I uncommented and set the "mode" to "software", uncommented the DB and AMI sections and filled in the necessary settings. This, however, made no difference.

After some more investigation I commented out the AMI settings, leaving only the DB section uncommented. After testing on the handsets, the "HTTP Error [500]" has disappeared and the service presented itself, however upon logging in the system seemed to "log in", however the phone did not reset itself. A manual soft-reset (power cycling) would cause the phone to reboot "logged in" to the correct EM extension. I assumed this was something to do with the AMI connection and the sccp restart command not being called correctly, the DB seemed to be updating correctly.

The PHP logs presented these error messages:

Undefined index: server in /var/www/html/cisco/service.inc/ami.class.php on line 304
Undefined index: username in /var/www/html/cisco/service.inc/ami.class.php on line 308
Undefined index: port in /var/www/html/cisco/service.inc/ami.class.php on line 322

After changing the AMI section in cisco_service.ini from...

[AMI]
HOST=localhost
USER=admin
secret=blahblahblah
PORT=5038

to...

[AMI]
server=localhost
username=admin
secret=blahblahblah
port=5038

...the errors seem to have gone away. I know the settings should be being picked up from the amportal.conf file, however this solution seems to be working for the time being. Just thought i'd raise this in case anyone else has a similar problem.

Thanks
James.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant