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: URL Pop-up: DNID / Custom

FOP2: URL Pop-up: DNID / Custom

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 94 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.
  • R
    R
    rscl
    wrote on last edited by
    #1

    Hi,

    Asterisk 1.4 on CentOS 5 (FreePBX ISO install)

    I am using custom dialplan to store DNID for every call in mysql under column "userfield".

    When using url pop-up feature of FOP2, I need to use the DNID value as a part of the URL.
    Is this possible ?

    Any pointers, ideas are appreciated.

    Thank you.

    Best regards,
    Sans

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

      Is it not possible, unless you modify the dialplan to set the callerid name to the dnid..

      1 Reply Last reply
      0
      • R
        R
        rscl
        wrote on last edited by
        #3

        Any possibilities of modifying the script to use DNID instead of clid
        -OR-
        within the script, assign the value of DNID ($userfield) to clid variable ?

        Thx

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

          The problem is this:

          There are not standard events sent via AMI regarding extra variables.. parsing CDR events via manager is overkill for that feature. In FOP(1) there is the option to save every channel variable that is "Set" and then pass that to the panel itself, but it is quite expensive on CPU as it has to inspect every event looking for the "set" application, etc.

          The next release will have a command "setvar" that can be sent to the client, and that will pass the key/value pair to the notification scripts. But you will have to custom code the event processing in FOP2Callbacks.pm and return a setvar event accordingly. It will consume quite a lot of cpu, but should be possible to do (on a custom basis, and programming it specifically).

          The callerid name is handy for passing simple values like this one, many people do not like the idea but sometimes it makes perfect sense, it does not consume CPU and it is easy to implement without disrupting anything.

          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