Call Pickup

While a phone/extension is ringing, I press that button and then press Call Pickup. My phone rings and when I answer it just hangs up. Am I doing it wrong?

Comments

  • You are not doing it wrong. But callpickup behaviour has changed and now is REALLY picky about extension contexts. That is why I changed the internals and I am now forcing a global var PICKUPMARK before performing the actual pickup, and it will work fine pretty much always.

    If you use centos 5 32 bits and want to test drive the "pre release" version, download this two files:

    http://www.fop2.com/downloads/fop2_server
    http://www.fop2.com/downloads/fop2.js

    Replace the ones you have with these two. Flush your browser cache. Restart fop2 and try again.

    Those files are not going to be there forever.. I will remove them as soon as the next version is released, that will be pretty soon.

    Best regards,
  • That works the way I would expect it to now. Thank you!
  • Hi,

    I'm using a CentOS release 5.3 (32 bits version) and I have the same problem.
    So, I download the 2 files. but the fop2_server is for x86-64 and not x86_32.

    Can you help me ?
  • Hi,

    Download the complete tarball from http://www.fop2.com/downloads/fop2.tgz , that one is for centos 5 , 32 bits for sure.

    Best regards,
  • Fine. It is running :D

    I find a problem I think. When I do a restart, or a start, or a stop it says : Can't listen to port 4445.
    So I kill the process and do a "restart". Now, it never achieves the restart.

    I suppose it is an error of manipulation. Isn't it ?

    BR
  • Hi,

    What are you restarting and how? Maybe you have fop1 still running and listening on port 4445? Best regards,
  • With the fop2.tgz found on http://www.fop2.com/downloads.

    In /var/www/html/panel/op_server.cfg I have

    listen_port=4446

    When I do a netstat -an | grep 444 I only see :

    tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:4446 0.0.0.0:* LISTEN

    So fop1 is really listening on the port 4446 and fop2 on the port 4445.

    I only do a /usr/local/fop2/fop2_server restart after modification of the file buttons.cfg.
    My fop2.cfg is :
    [general]
    ; AMI definitions
    manager_host=localhost
    manager_port=5038
    manager_user=fop2
    manager_secret=fop2
    ;event_mask=call,agent
    
    ; Daemon definitios
    ;listen_port      = 4445
    ;restrict_host    = www.asternic.org
    ;web_dir          = /var/www/html/operator/fop2
    
    ; Global Config
    language           = en
    poll_interval      = 86400
    poll_voicemail     = 1
    monitor_ipaddress  = 0
    
    ; Force blind transfer on asterisk 1.6
    blind_transfer     = 1
    
    ; Master Password that overrides any individual one
    master_key = 5678
    
    ; --- SAMPLE USER LIST ---
    user=701:1234:all
    user=704:1234:all
    ;user=620:1234:all
    ;user=621:1234:all
    ;user=622:1234:all
    ;user=623:1234:meetme
    buttonfile=buttons.cfg
    ; ------ END SAMPLE ------
    
    ; This line is NOT commented, it executes 
    ; the autoconfig configuration for FreePBX
    ;#exec autoconfig-users-freepbx.sh
    

    I just try the command fop2_server restart on a new installation and it's the same.
    So, when I need to restart fop2 I do
    ps ax | grep fop2
    kill fop2_pid
    fop2_server --start &
    

    My installations are registered.

    Strange ...
    BR
  • Hello,

    The start,stop,restart options are for the init script that should be installed in /etc/rc.d/init.d or /etc/init.d depending on your linux distribution. The init script does what you did to fop2_server directly in a graceful manner..

    /etc/rc.d/init.d/fop2 [start|stop|restart|reload]

    Best regards,
  • OK.
    I understand ...

    Thx
Sign In or Register to comment.