call Pickup not working

rbyerjr

the call pickup button on the FOP screen is not picking up the call.
Details:
- FOP 2.27, Asterisk 1.8, Centos x64 6.4
- all associated extensions are in the same callgroup and pickupgroup (1)
- inbound call to other extension ignores the Call Pickup button, but if call pickup (*8) is done on the handset, it works.

- tried enabling & disabling no_pickupmark, and pickupchan, neither had any effect, commented them both back out.

- When perusing the full debug logs on asterisk, I see the Pickup when it is does from the handset. I see nothing, error or otherwise, of any attempt to call Pickup from the fop2 screen. I was running manager debug as well.

Any thoughts on how to progress this ?

Thanks,

nicolas

Do you have the "pickup" permission set for that particular fop2 user ? Do you see the extension/call you are trying to pickup in RINGING mode in the fop2 display? You can open the javascript console on your browser and check that when you attempt call pickups. My guess are: 1) not in ringing mode 2) lack of permissions.

Best regards,

rbyerjr

I was trying to be complete in my original post, but missed those 2 points:
1) the FOP user in question has ALL permissions.
2) There is no evidence of anything going on in the CLI, with full debug, verbose, and manager debug set. It looks like it is not doing anything. But, when I do the *8 from the phone, then the call picks up.

I will try the js console on the browser. That's a good idea

Ron

rbyerjr

fixed.
The problem was....
usage error on my part. :oops:
Apologies

rb

NdncRegister

As my call Pickup is also not working but i have restarted it again, then it show some java errors and may ask for permission Or DND Status is required some what, but some times its work properly and some time not, can i have the exact answer why this is happening again and again.

nicolas

Without posting proper debug logs and an exact description of your actions is not possible to give you any exact answer. Exact answers require exact questions and back data. None were provided. So you will receive this answer instead of an 'exact' one.

In any action in FOP2 does not work as you expect, please describe in exact detail what actions you performed, what you expected to happen and what happened instead. That together with the javascript console open on your browser, and if a command is seen as sent there, the debug log on the server side as well. The debug logs might not be needed at all because most of the time problems are just user errors or misconceptions on what should happen when something is done on FOP2.