FOP2/Asterisk 1.4 replace Queuemetrics
Obtained FOP2 to replace some cumbersome real-time components of Queuemetrics (QM); and to replace clunky XMPP messaging app...so less applications on user desktops. FOP2 installed on separate server (that also runs QM).
Application appears to be running, and can access; however cannot go live as have a problem with registration status of SIP peers, and IM chat functions.
Pilot config:
sip.conf has "qualify=yes" for each sip/xxxx [we will change this as go live to restrict permissions]
fop2.cfg all users have permission "all", poll_interval=1200, save_chat_log=1
Our two problems from installation are:
(1) Chat alerts are not being seen on recipient's Flash Operator Panel
(2) When FOP2 is restarted it makes all extensions "green" - i.e. registered....however during run it picks up changes and gradually greys them out (if they log off their PCs/soft phones)
Any thoughts?
Thanks
----
Asterisk server, Gateway server, QM server (reporting)
Server licensed (2.26). Asterisk 1.4.45. RedHat Ent x64.
SIP Softphone: Bria for Asterisk 2.5
Application appears to be running, and can access; however cannot go live as have a problem with registration status of SIP peers, and IM chat functions.
Pilot config:
sip.conf has "qualify=yes" for each sip/xxxx [we will change this as go live to restrict permissions]
fop2.cfg all users have permission "all", poll_interval=1200, save_chat_log=1
Our two problems from installation are:
(1) Chat alerts are not being seen on recipient's Flash Operator Panel
(2) When FOP2 is restarted it makes all extensions "green" - i.e. registered....however during run it picks up changes and gradually greys them out (if they log off their PCs/soft phones)
Any thoughts?
Thanks
----
Asterisk server, Gateway server, QM server (reporting)
Server licensed (2.26). Asterisk 1.4.45. RedHat Ent x64.
SIP Softphone: Bria for Asterisk 2.5
Comments
My recommendation is to comment out poll_interval or leave it as 86400, you do not want to poll for status every so often, it is not needed and it is actually harmful to the internal fop2 state machine, as actually the fop2 state machine has more information that the one you can poll from asterisk status responses. Anyways, I do not think the poll interval has anything to do with your issues.
Chat is as simple as it gets, it just works. But you must give "chat" permissions to all users. Are you sure all fop2 users have the chat permission? Also, users MUST be logged into fop2 to get an alert, as the fop2 page is the client. If you are not logged, there is no way to send the alert. To the party initiating the chat, if the other user is not logged, you will see it on your own chat window (it will inform the other user is not online and that it is saving a note to them).
About registration status, FOP2 just follows the events it receives from Asterisk. What you see is what Asterisk is informing via AMI events. The initial status is always "green", not gray, so not sure what are you seeing. The extensions become gray if asterisk sends a lagged or not registered peerstatus event via AMI.
If you want to troubleshot, you will have to start fop2_server in debug mode and look at those events. Are you using Asterisk Realtime for sip peers? In that case you m ust set rtcachefriends=yes
Also, qualify=yes or qualify=MILLLISECONDS must be set for every sip peer if you want to monitor its registration status, you cannot disable that, it is not a matter of permissions. You can try to catch me on the live help and we can review your issues on your pilot system together.
Best regards,
Many thanks for the update. Your explanation of FOP2 showing every extension as default=green=registered is clear. Basically FOP2 only uses AMI (and not commands such as "show sip peers") when it starts.
Is there anyway for FOP2 to read the current registration status when the server starts...as we're using this in a call centre environment and it would be nice to know which extensions have not registered (i.e. with PCs).
---
On the IM Chat functionality I have added the "chat" permission to each user:
e.g.
user=9199:9199:all,chat
But no alerts appear on the recipients FOP panel.
Are we missing something?
Thanks
Rob
FOP2 *does* query for status when it starts. It gets a clear picture of registration status IF there is status reported by Asterisk.
SIP Registration status is not the same as users being available or not, that depends on what you consider a "user", and what are the actions performed from them to become available.
Contact me via the live help, everything works fine in FOP2 for your environment, including the chat option. perhaps there are some things on your scenario that are not yet clear to me.