Jump to content
  • PBXCall.ConnectedNumber


    VBScript   → Lua


    This property returns the intenal extension of the user a call was connected to right after a Connect To GSE block.





    This function returns a string value.


    If you connect a call to a group and need to know which user of this group has taken the call, this property can be requested right after leaving the Connected exit of the Connect To block.


    There is another function PBXCall.ConnectedName which returns the name of the user who took the call.



    The return value of this function is getting updated if after the call got connected initially and then transferred from there to another user. This of course requires the call routing script not to be left immediately after the Connect To block. This can be achieved by using the Timeout parameter of the Wait for Disconnect block to check the PBXCall.ConnectedNumber value e.g. every second for changes.


    An example for exactly this functionality can be found in the A.2 - Check Status and Update Ticket example of the Zendesk Integration, an Open ECR Extensions open source project.


    This example gathers all relevant information of a call and stores them into a Zendesk support ticket. Once a call was connect, a Wait For Disconnect block with a 1 second Timout is used, to check regularly if, the call is getting transferred any further, and if so updates the information which is getting written into the ticket. 


    if sConnectedName <> PBXCall.ConnectedName then
      sConnectedName = PBXCall.ConnectedName
      sCallStatus = sCallStatus & _
        FormatDateTime(Now) & " : Call connected to " & sConnectedName & "." & vbCrLF
    end if



    Please note, that this functions returns an empty string, once the call was disconnected.



    Tom Wellige


  • Create New...

Important Information

By using this site, you agree to our Terms of Use and have taken note of our Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.