Details

    • Type: Feature Requests Feature Requests
    • Status: Closed (View Workflow)
    • Resolution: Invalid
    • Affects Version/s: 2.11
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Backend Engine:
      All
    • Confirmation:
      Unreviewed
    • Distro:
      FreePBX Distro

      Description

      Not sure how fpbx use to do it but here is a new way. I always use users and devices so code is written with that in mind:

      exten => 777888,1,Read(LUISTERUSER,please-enter-the&extension,4,,2,10)
      exten => 777888,n,Wait(1)
      exten => 777888,n,Playback(auth-thankyou)
      exten => 777888,n,Wait(1)
      ;for users and devices part
      exten => 777888,n,Set(LUISTERDEVICE=${DB(DEVICE/${LUISTERUSER}/user)}
      ;end
      exten => 777888,n,Playback(connecting)
      exten => 777888,n,SayDigits(${LUISTERUSER})
      exten => 777888,n,Wait(1)
      exten => 777888,n,ChanSpy(SIP/${LUISTERDEVICE},dbs)
      exten => 777888,n,Hangup()
      

        Activity

        Hide
        Philippe Lindheimer added a comment -

        this is wrong.

        if you are trying to lookup the user so you can get their one or more devices, you would have to go to the AMPUSER object, get the one or more devices, then go to the device object for each of those devices and get the dial string which will provide the proper channel technology and native device information. (and if you have multiple devices logged into the same user, you would have to deal with that which is maybe looking for the active channel to choose which one, and if there are more then 1, then make some decision?)

        Closing the ticket since the example is misleading to others, if you want to update it so it is correct I'll be glad to re-open it in case it is of interest to others. As far as ChanSpy in general, it does need some rewriting mostly around ACLs and easier usage although it is another type of feature where environments that it is important are better served with visual tools such as iSymphony which has the capability to choose specific calls to spy on.

        Show
        Philippe Lindheimer added a comment - this is wrong. if you are trying to lookup the user so you can get their one or more devices, you would have to go to the AMPUSER object, get the one or more devices, then go to the device object for each of those devices and get the dial string which will provide the proper channel technology and native device information. (and if you have multiple devices logged into the same user, you would have to deal with that which is maybe looking for the active channel to choose which one, and if there are more then 1, then make some decision?) Closing the ticket since the example is misleading to others, if you want to update it so it is correct I'll be glad to re-open it in case it is of interest to others. As far as ChanSpy in general, it does need some rewriting mostly around ACLs and easier usage although it is another type of feature where environments that it is important are better served with visual tools such as iSymphony which has the capability to choose specific calls to spy on.

          People

          • Assignee:
            Philippe Lindheimer
            Reporter:
            franss
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development