Hello.
I’m not able to dial out when logged in via UCP. To my big surprise i’m reachable when logged in but when i try to hit the dial button of the phone within UCP i see the not possible icon or how do you call it? The Phone Icon itself is green. Anyways, does it work for someone?
thanks and cheers
Works for me but the phone in UCP 14 will display errors. you should post screenshots.
Here is a screenshot on how it looks on my side. I also cannot hit the number buttons. I can only enter numbers by
hitting the number buttons on my keyboard.
thanks and cheers
t.
You have no phone status. This will not work.
I see. What could be the reason i have none? Do i need to have registered a real phone to that extension to be able to dialout? Is there a documentation somewhere?
thanks for your answer
t…
Open up the javascript console. There will be errors there.
Actually there are no errors in the javascript console. Looks good to me. Any other hints?
thanks and cheers
t.
(image deleted)
Thats not the javascript console. Thats the javascript resource window.
So you have a problem with the presencestate module. Install that module. I can’t see what’s calling it. You’d have to during on developer mode in freepbx for use to be able to tell what module is calling that
I’m still stuck with that issue. Any ideas how to proceed? Presence State Module is installed and at version 14.0.1.2.
thanks and cheers
t.
Reinstall the module.
Is there a fwconsole command for this? I ask because i get:
Presence State cannot be disabled because the following modules depend on it: restapps
The restapps are nowhere to find.
thanks and cheers
Found it. Reinstalled pm2. Still the same.
[root@voip ~]# fwconsole ma disable restapps
Module restapps successfully disabled
Updating Hooks...Done
[root@voip ~]# fwconsole ma disable vqplus
Module vqplus successfully disabled
Updating Hooks...Done
^[[A[root@voip ~]# fwconsole ma uninstall pm2
Module pm2 successfully uninstalled
Updating Hooks...Done
[root@voip ~]# fwconsole ma install pm2
Installing/Updating Required Libraries. This may take a while...The following messages are ONLY FOR DEBUGGING. Ignore anything that says 'WARN' or is just a warning
[npm-cache] [INFO] using /home/asterisk/.package_cache as cache directory
[npm-cache] [INFO] [composer] Dependency config file /var/www/html/admin/modules/pm2/node/composer.json does not exist. Skipping install
[npm-cache] [INFO] [npm] config file exists
[npm-cache] [INFO] [npm] cli exists
[npm-cache] [INFO] [npm] hash of /var/www/html/admin/modules/pm2/node/package.json: b84d380aaab5f619c0c9f4060cc86a0c
[npm-cache] [INFO] [npm] cache exists
[npm-cache] [INFO] [npm] clearing installed dependencies at /var/www/html/admin/modules/pm2/node/node_modules
[npm-cache] [INFO] [npm] ...cleared
[npm-cache] [INFO] [npm] retrieving dependencies from /home/asterisk/.package_cache/npm/3.10.10/b84d380aaab5f619c0c9f4060cc86a0c.tar.gz
[npm-cache] [INFO] [bower] Dependency config file /var/www/html/admin/modules/pm2/node/bower.json does not exist. Skipping install
[npm-cache] [INFO] [npm] done extracting
[npm-cache] [INFO] successfully installed all dependencies
Finished updating libraries!
Generating CSS...Done
Module pm2 successfully installed
Updating Hooks...Done
[root@voip ~]# fwconsole ma enable vqplus
Module vqplus successfully enabled
Updating Hooks...Done
^[[A[root@voip ~]# fwconsole ma enable restapps
Module restapps successfully enabled
Updating Hooks...Done
[root@voip ~]#Uh, that was the wrong module. Here we go:
[root@voip ~]# fwconsole ma uninstall presencestate
Dropping table presencestate_list...Done
Dropping table presencestate_prefs...Done
Module presencestate successfully uninstalled
Updating Hooks...Done
[root@voip ~]#
[root@voip ~]# fwconsole ma install presencestate
Updating table presencestate_list...Done
Updating table presencestate_prefs...Done
Generating CSS...Done
Module presencestate successfully installed
Updating Hooks...Done
[root@voip ~]# fwconsole ma enable restapps
Module restapps successfully enabled
Updating Hooks...Done
[root@voip ~]#
But still the same.
Sorry. I’m unsure of your specific issue.
Must have been solved with one of the latest updates. Now it works.