FOP2 dial box trouble

  1. 12 years ago

    Asterisk 1.8
    FreePBX 2.9 with FOP2 module 1.2.9

    ./fop2_server -v
    fop2_server version 2.24

    Flash Operator Panel 2 - White Label Version.

    Originate call to selected extension work well.
    Dial from dial box won't work.

    Permissions for user 393 from autoconfig-users-freepbx.sh:

    perm=helpdesk:dial,hangup,hangupself,phonebook,pickup,preferences,queueagent,spy,transfer,transferexternal:
    user=393:393:helpdesk,operator:All Trunks,All Conferences,All Queues,All Extensions,All Buttons

    Here is log per Originate and Dial:

    === Originate ===
    <= <msg data="20|originate|10|ef03dc3ea7f7c333c114779f990d1168" />

    -- PROCESS_FLASH_COMMAND origen 20 accion originate destino 10 password ef03dc3ea7f7c333c114779f990d1168

    VALIDAR USUARIO 393@GENERAL

    VALIDAR USUARIO 393 OK con clave regular (XXX.XXX.XXX.XXX )

    Validation ok, have dial permissions for 10

    ORIGINATE:
    Action: Originate
    Channel: SIP/393
    Exten: 398
    Context: from-internal
    Priority: 1
    CallerID: 393 <393>
    Async: True

    === Dial ===

    <= <msg data="20|dial|398|ef03dc3ea7f7c333c114779f990d1168" />

    -- PROCESS_FLASH_COMMAND origen 20 accion dial destino 398 password ef03dc3ea7f7c333c114779f990d1168

    VALIDAR USUARIO 393@GENERAL

    VALIDAR USUARIO 393 OK con clave regular (81.26.144.130)

    Validation wrong, no custom permissions

    DIAL permission denied!

    ====

    I don't understand what is wrong in my config and what permission need here to make call from dial box.

  2. admin

    16 Feb 2012 Administrator

    Hi,

    As the dialbox can be used to dial ANY number, a custom permission is not enough to allow dialing from there. You must use the regular "dial" permission in that user to enable the dialbox.

    Hope my explanation makes sense.

    Best regards,

  3. Hi,

    As the dialbox can be used to dial ANY number, a custom permission is not enough to allow dialing from there. You must use the regular "dial" permission in that user to enable the dialbox.

    Hope my explanation makes sense.

    Best regards,

    Hi Nicolas,

    User has dial permission, you can see it from autoconfig-users-freepbx.sh output:

    perm=helpdesk:dial,hangup,hangupself,phonebook,pickup,preferences,queueagent,spy,transfer,transferexternal:
    user=393:393:helpdesk,operator:All Trunks,All Conferences,All Queues,All Extensions,All Buttons

    (group is included in the group "helpdesk" that have dial permission)

    Btw, FOP2 server said about "custom" permission when there is dial attempt from dial-box:

    <= <msg data="20|dial|398|ef03dc3ea7f7c333c114779f990d1168" />

    -- PROCESS_FLASH_COMMAND origen 20 accion dial destino 398 password ef03dc3ea7f7c333c114779f990d1168

    VALIDAR USUARIO 393@GENERAL

    VALIDAR USUARIO 393 OK con clave regular (81.26.144.130)

    Validation wrong, no custom permissions

    DIAL permission denied!

  4. admin

    16 Feb 2012 Administrator

    No, the user does not have the dial permission:

    user=393:393:helpdesk,operator:All Trunks,All Conferences,All Queues,All Extensions,All Buttons

    It has some custom permissions, and as I said, the dial permission in a custom permition only allows you to use the dial button, not the dial box. You should see something like this in the user setting if you want the dialbox to work:

    user=393:393:dial,helpdesk,operator:All Trunks,All Conferences,All Queues,All Extensions,All Buttons

    Best regards,

  5. Nicolas,

    Thank you for help, problem solved.
    I understand now what is difference between regular and custom permissions ;)

  6. 9 years ago

    I have several users that even if I give them "all" permission, they still don't have a dial button in FOP2. The phone is provisioned and everything is working except the dial button will not show (this is a licensed FOP2). I run the autoconfig-users-freepbx.sh and currently get this for that user (I switched it back off of "all" to the permissions I want that user to have):

    user=400:1324:dial,hangupself,pickup,transfer,transferexternal:All Extensions:configonreload

    What else can I check to debug this?

  7. admin

    23 Oct 2015 Administrator

    Do you have other action buttons visible? Like transfer, hangup?

  8. Yes, the other buttons show. All show and hide as I edit their permissions. Just not "dial".

  9. admin

    23 Oct 2015 Administrator

    Did you create custom permissions? What is the output from

    /usr/local/fop2/autoconfig-users.sh | grep perm

    ?

  10. @admin Did you create custom permissions? What is the output from

    /usr/local/fop2/autoconfig-users.sh | grep perm

    ?

    I got this:
    perm=norecordings:record:

  11. @admin Did you create custom permissions? What is the output from

    /usr/local/fop2/autoconfig-users.sh | grep perm

    ?

    No recordings is to keep people from recording, but using "all". I ended up dropping this and giving detailed permissions to the appropriate templates. So I'm not using that anymore.

  12. admin

    4 Nov 2015 Administrator

    When you create custom permissions, those are for restricting the action to a select target of buttons. Some action permissions do not always apply to selected targets (like dial, that will let you dial ANY number, apart from the extensions/queues or other buttons you might have visible in FOP2). That is why you *cannot* use 'dial' on a custom permission. You will always have to explicitly add 'dial' to a template or user permission if you want them to be able to dial outside numbers or to enable click to call. You can create a custom record permission to limit the record action to a subset of buttons, but you cannot add 'dial' or 'preferences' or other permissions that are global into that restricted permissions, as you will be actually disable the action altogether.

    Best regards,

  13. UPDATE: Ends up it wasn't a bug at all. Restrictions wasn't the problem either. This was a PEBKAC (problem exists between keyboard and chair). First off, the reception phone I was trying to log in with was not yet provisioned (set up in FreePBX, but phone was not plugged in). Thus the dial option would not show.

    Then, once I noticed that and provisioned the phone, I was clicking dial from my desk and the reception phone was getting the ring, 300 feet away (I was expecting my phone the ring, stupidly), so I wasn't noticing it was actually working. It just looked like it wasn't responding, but it was waiting for the phone to be picked up.

    Perhaps a little indication to pick up the phone, or phone not provisioned would be nice (if that data is accessible to fop2). If not, then at least people will see this forum and slap their foreheads like I did. Cheers!

or Sign Up to reply!