MasterVitronic / fusionpbx

Automatically exported from code.google.com/p/fusionpbx
0 stars 0 forks source link

Hotdesking - Scripts hangs up after entering extention & password #479

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. dial *072
2. Enter Unique Extention ID + #
3. Enter Password + #

What is the expected output? What do you see instead?
Expected:
Message saying saved and updated information on Hotdesk Page.

Nothing happens instead.

What version of the product are you using? On what operating system?
Fusion Version:  3.4 (Dev branch) build 4637
Operating System:    Linux pbx 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 
25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Please provide any additional information below.
I did check the VM via *98 for the tested extensions and that worked with the 
provided passwords.
So VM password is correctly set. 

(If the native Postgresql option is included in the stable branche in the 
install script I can test that as well)

Original issue reported on code.google.com by wil...@poort.net on 10 Oct 2013 at 2:14

GoogleCodeExporter commented 9 years ago
Version:     3.4 (Dev Branch) build 4649
Operating System:    Linux pbxii 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 
20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Uptime:  15:08:12 up 1 day, 1:58, 0 users, load average: 0.15, 0.20, 0.22
Date:    Sun, 20 Oct 2013 15:08:12 +0200

Still no success, the message now though is, "Login incorrect"
Voicemail login does work correctly for same extension so password is correct 
but not accepted in hotdesking script.

Original comment by wil...@poort.net on 20 Oct 2013 at 1:12

GoogleCodeExporter commented 9 years ago
Found something:
Marc, at dial_string.lua at line 130 I noticed you check against variable 
caller_pin_number, shouldn't this be vm_password ? 

if (voicemail_password ~= caller_pin_number) then  ==> if (voicemail_password 
~= vm_password) then

I still have to restart memcached though to activate the new setting.

Original comment by wil...@poort.net on 20 Oct 2013 at 2:05

GoogleCodeExporter commented 9 years ago
Extra input.
line 211   I gues extension_uuid should be db_extension_uuid?
     freeswitch.consoleLog("NOTICE", "extension_uuid: ".. extension_uuid .. "\n");  ==>
     freeswitch.consoleLog("NOTICE", "db_extension_uuid: ".. db_extension_uuid .. "\n");

I also seen an error in the Freeswitch log concerning memcached:
2013-10-20 16:29:20.529479 [ERR] switch_core_session.c:2613 Invalid Application 
memcache

memcached does run from the cli and the memcached module is active as well.

at the fs_cli memcache can also be executed.

Original comment by wil...@poort.net on 20 Oct 2013 at 2:39

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Willem, both the memcache issue and pin number are fixed. Please confirm that 
it is working.

Original comment by markjcrane@gmail.com on 31 Oct 2013 at 2:02

GoogleCodeExporter commented 9 years ago
Marc,

Both issue's are solved now. Thanks!

URL: http://fusionpbx.googlecode.com/svn/branches/dev/fusionpbx
Repository Root: http://fusionpbx.googlecode.com/svn
Repository UUID: e2954ef0-caed-11de-bd98-e341d93cc3cc
Revision: 4669
Node Kind: directory
Schedule: normal
Last Changed Author: markjcrane@gmail.com
Last Changed Rev: 4669
Last Changed Date: 2013-10-31 04:48:08 +0100 (do, 31 okt 2013)

Original comment by wil...@bien.nl on 31 Oct 2013 at 12:24

GoogleCodeExporter commented 9 years ago
Thanks for testing and reporting back, I'm closing the issue.

Original comment by markjcrane@gmail.com on 31 Oct 2013 at 1:19