User Login Passwords not 'Syncing'

[crossit]

Also. Just noticed when I set my presence to "at lunch" or any other status FOP2 doesn't reflect the change till you log off and in again. Something must be a miss here.

[nicolas]

Your manager permissions are not dispatching user events. Add "all" both to read/write in /etc/asterisk/manager.conf

[crossit]

pbx*CLI> manager show user admin

   username: admin
     secret: <Set>
        acl: yes
  read perm: system,call,log,verbose,command,agent,user,config,dtmf,reporting,cdr,dialplan,originate,agi,all
 write perm: system,call,log,verbose,command,agent,user,config,dtmf,reporting,cdr,dialplan,originate,agi,all

displayconnects: yes

Still not responding as expected.

A.J.

[nicolas]

All I can say is that it works fine. You should start fop2_server in debug mode and try to capture the output and look for clues there.

service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 511

then change status a couple of time and look for UserEvents or activity when you do the change.

[crossit]

OK got it working. Changed the default port on the original FOP panel seemed to do the trick. Even though I have the original FOP set to not startup in amportal.conf this still was affecting things somehow?

For now I'll just reload asterisk every so often to refresh the login password. If this could be added as a feature in the next update it'd be much appreciated.

A.J.

[nicolas]

Hi,

good you have it working. Regarding the update of passwords, changes from any external tool cannot be tracked, the feature should be added to that tool (it must send some kind of event to AMI). Changing the password from voicemail might be possible, but I *think& that comedian mail does not broadcast any event at all in AMI.. in that case, the feature should be added to asterisk, not fop2.

In any case, my recommendation is to use a big long password for fop2 and not resuse the easy to guess voicemail pin number.

[jamuel]

If you must use asterisk voicemail passwords, this works really well:

In /etc/asterisk/voicemail.conf set:

externpassnotify = /usr/local/fop2/tickle_fop2.sh

And then have a script like this:

# cat > /usr/local/fop2/tickle_fop2.sh 
#!/bin/bash
sudo /usr/bin/killall -HUP fop2_server
exit 0;
<CTRL><d>

# chown asterisk.asterisk /usr/local/fop2/tickle_fop2.sh
# chmod u+x /usr/local/fop2/tickle_fop2.sh

Don't forget to add user asterisk to /etc/sudoers (using visudo):

asterisk ALL=(ALL) NOPASSWD: /usr/bin/killall -HUP fop2_server

Cheers,

JPS

[crossit]

I also noticed that if I change a display name in freepbx that this change isn't reflected in FOP2 after a reload. What should be triggering this?

[nicolas]

The fop2 buttons configuration page will not update a label automatically, you have to control button labels from that page when using fop2admin. There is a button to update all labels in the fop2 buttons page, or you can modify them individually.

Best regards,

[crossit]

OK back to this topic. In regard to "use a big long password for FOP2" what is the easiest way to implement this? If I use the FreePBX FOP2 Admin module can I set one long password for all the users easily? Is there an easy way to let users manage their own pass from the panel settings menu? Even better yet can I sync this pass with Active Directory?

[nicolas]

Hi,

You can modify the autoconfig-users-freepbx.sh script and use whatever tool you like to create user configurations, including ldap queries. But you will have to install the proper tools and write/modify the script to suit your needs.

Best regards,