Post a Reply
1559 views

quirk or perhaps a bug

  1. 13 years ago

    jdhatch

    8 Apr 2011

    Nicolas,

    I found something that may be a small bug.

    I created a custom extension 2999 (sends to an outside number) and if I add it to my 3100 queue using "3100*" and "2999#" the fop2 service seems to stop.

    "service fop2 start" gets it going again.

    If using the fop2 webpanel and "add to 3100" and "remove from 3100" there is no service problem.

    Thanks, Jason

  2. admin

    8 Apr 2011 Administrator

    Hi,

    Are you using fop 2.20 final? If so, please start fop2_server in debug mode and perform the action so we can see the fatal error:

    service fop2 stop
/usr/local/fop2/fop2_server -X 511

    If you do the addition/removal and fop2_sever crashes, paste the error you see here.

    Best regards,

  3. jdhatch

    8 Apr 2011

    ** MAIN End of block from localhost

    127.0.0.1 <- Event: QueueMemberAdded
    127.0.0.1 <- Privilege: agent,all
    127.0.0.1 <- Queue: 3100
    127.0.0.1 <- Location: Local/2999@from-queue/n
    127.0.0.1 <- MemberName: 2999
    127.0.0.1 <- Membership: dynamic
    127.0.0.1 <- Penalty: 0
    127.0.0.1 <- CallsTaken: 0
    127.0.0.1 <- LastCall: 0
    127.0.0.1 <- Status: 1
    127.0.0.1 <- Paused: 0
    127.0.0.1 <- Server: 0

    • * MAIN AMI event received...
    • * MAIN There's an 'Event' in the event block
    • * MAIN Event detected block_count = 1 (Event: QueueMemberAdded)
    • * MAIN There are 1 blocks for processing
    • * MAIN Answer block cleared

    ** DIGEST_EVENT: start

    • * PROCESA_BLOQUE 0
    • * PROCESA_BLOQUE QUEUEMEMBERADDED 0
    • * QUEUE MEMBER LIST start
    • * QUEUE MEMBER LIST devuelve <div class='memberready myclick' id='qm!QUEUE/3100!Local/2999@from-queue/n'></div><span>2999</span><br class='clear'/><div class='memberready myclick' id='qm!QUEUE/3100!Local/2200@from-queue/n'></div><span>B Reception</span><br class='clear'/><div class='memberready myclick' id='qm!QUEUE/3100!Local/2102@from-queue/n'></div><span>Chelsea</span><br class='clear'/><div class='memberready myclick' id='qm!QUEUE/3100!Local/2110@from-queue/n'></div><span>Cindi</span><br class='clear'/><div class='memberready myclick' id='qm!QUEUE/3100!Local/2111@from-queue/n'></div><span>Donna</span><br class='clear'/><div class='memberready myclick' id='qm!QUEUE/3100!Local/2100@from-queue/n'></div><span>LeighAnn</span><br class='clear'/><div class='memberready myclick' id='qm!QUEUE/3100!Local/2101@from-queue/n'></div><span>Lora</span><br class='clear'/>

    Can't call method "setMemberName" on an undefined value at script/fop2_server_2.20.pl line 3406.
    [root@pfm ~]#

  4. admin

    8 Apr 2011 Administrator

    can you please verify your fop2 version?

    /usr/local/fop2/fop2_server -v

    md5sump /usr/local/fop2/fop2_server

    Best regards,

  5. jdhatch

    8 Apr 2011

    [root@pfm ~]# /usr/local/fop2/fop2_server -v
    fop2_server version 2.20
    [root@pfm ~]# md5sum /usr/local/fop2/fop2_server
    b20267e789e235d02267b33c3e43f5fe /usr/local/fop2/fop2_server

  6. admin

    13 Apr 2011 Administrator

    Thanks for the report!

    I found the problem and fixed it. It will be available on version 2.21. One way to fix it right now would be to force uppercase on button channel names, as the problem comes when using "Local/" type channels versus "LOCAL/". If the autoconfiguration script is modified to convert channel names to uppercase it will work with no crashes, but the correct fix is to modify the daemon to do this itself and work fine in both cases with no crash.

    Best regards,

  7. jdhatch

    16 Apr 2011

    Thanks,
    It is not an urgent issue and I will wait for the update.

    Thanks, Jason

or Sign Up to reply!