Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. FOP2 dial box trouble

FOP2 dial box trouble

Scheduled Pinned Locked Moved Support
13 Posts 3 Posters 260 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    M
    may213
    wrote on last edited by
    #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!

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #4

      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,

      1 Reply Last reply
      0
      • M
        M
        may213
        wrote on last edited by
        #5

        Nicolas,

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

        1 Reply Last reply
        0
        • I
          I
          itdept2015
          wrote on last edited by
          #6

          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?

          1 Reply Last reply
          0
          • N
            N
            nicolas
            wrote on last edited by
            #7

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

            1 Reply Last reply
            0
            • I
              I
              itdept2015
              wrote on last edited by
              #8

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

              1 Reply Last reply
              0
              • N
                N
                nicolas
                wrote on last edited by
                #9

                Did you create custom permissions? What is the output from

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

                ?

                1 Reply Last reply
                0
                • I
                  I
                  itdept2015
                  wrote on last edited by
                  #10

                  10998:@admin escribió:

                  Did you create custom permissions? What is the output from

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

                  ?

                  I got this:
                  perm=norecordings:record:

                  1 Reply Last reply
                  0
                  • I
                    I
                    itdept2015
                    wrote on last edited by
                    #11

                    10998:@admin escribió:

                    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.

                    1 Reply Last reply
                    0
                    • N
                      N
                      nicolas
                      wrote on last edited by
                      #12

                      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,

                      1 Reply Last reply
                      0
                      • I
                        I
                        itdept2015
                        wrote on last edited by
                        #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!

                        1 Reply Last reply
                        0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        Powered by NodeBB Contributors
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups