3CXPhone API CallTriggerCmd Plugins doesn't works

Discussion in '3CX Phone System - General' started by lospejos, Sep 27, 2015.

Thread Status:
Not open for further replies.
  1. lospejos

    Joined:
    Sep 27, 2015
    Messages:
    3
    Likes Received:
    0
    Hi!
    My 3CX PBX has version 14, 3CXPhone is v14 (14.0.44241.523). I've downloaded recent example from here: http://downloads.3cx.com/downloads/misc/CallTriggerCmdPlugin.zip
    I stopped 3CXPhone, copied files (replacing existing) to 3CXPhoneDir\PhoneApp:

    • CallTriggerCmd\bin\Release\CallTriggerCmd.exe
      CallTriggerCmd\bin\Release\CallTriggerCmd.exe.config
      CallTriggerCmd\bin\Release\CallTriggerCmdServiceProvider.dll
      CallTriggerCmdPlugin\bin\Release\CallTriggerCmdPlugin.dll
      References\MyPhoneCRMIntegration.dll
    I started 3CXPhone, then I started:
    3CXPhoneDir\PhoneApp\CallTriggerCmd.exe --listen, got console waiting for data.
    Than I performed a call form another phone to a number which I have registered in my 3CXPhone. But nothing happened. Console still empty. I expected to see some call info written in console. I expected to see some data in log file (which is "c:\Users\MyUser\AppData\Roaming\CallTriggerCmd\Logs\CallTriggerCmd.log", as I see form sources:
    Environment.GetFolderPath(specialFolder), @"CallTriggerCmd\Logs" in LogHelper.cs
    LogHelper.Log(Environment.SpecialFolder.ApplicationData, "CallTriggerCmd.log"... in CallTriggerCmdPlugin.cs
    ).

    Am I doing something completely wrong? Am I mistaken regarding this API is done for?

    My log "AppData\Roaming\3CXPhone for Windows\Logs\3CXPhoneForWindows.log" fragment (this is like a system log of 3CXPhone, I guess, not the same log file as from plugin I told above):
    [27.09.2015 10:20:55.531][1] Pro only added CallTriggerCmdPlugin, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    [27.09.2015 10:20:55.531][1] Pro only added CallTriggerCmdPlugin, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    [27.09.2015 10:20:55.531][1] Pro only added CallTriggerCmdPlugin, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    [27.09.2015 10:20:55.531][1] Pro only added CallTriggerCmdPlugin, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

    I suppose this means plugin loaded OK.
    Also when I start ProcessExplorer, I see "CallTriggerCmdPlugin" and "CallTriggerCmdServiceProvider" items loaded in tab ".NET Assembles" for process "3CXWin8Phone.exe".

    My goal is:
    1. Get call events (ringing, answered, ended etc) recorded in my backend system (I know this could be completed reading data directly from PostgreSQLm but I prefer to use public APIs whenever possible);
    2. Make some actions on client (not server) side, f.e. display info box about caller info, found in my backend system by caller number.

    Any help will be appreciated. Thanks!
     
  2. lospejos

    Joined:
    Sep 27, 2015
    Messages:
    3
    Likes Received:
    0
    Additional info:
    1. I've added log statements to almost all method calls inside plugin. Log file contains records about plugin init, but contains bo records about events.
    2. Debugging session accepted this assumption, breakpoints on event handlers was not called (but was called on another methods inside plugin).

    So my next question is: what kind of 3CX license should I have to make this plugin working?
     
  3. pj3cx

    pj3cx Active Member

    Joined:
    Aug 1, 2013
    Messages:
    645
    Likes Received:
    1
    Hi there,
    You will need the Pro license to use the call trigger cmd.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. cadbrowne

    Joined:
    Apr 5, 2017
    Messages:
    9
    Likes Received:
    0
    I realize this is an old thread, but I am having possibly the same problem: CallTriggerCmd --call does nothing.
    (If 3cx is running, it does nothing. If it is not running, CallTriggerCmd spits out errors, so I can tell it knows the difference, at least.)

    How do we tell which version we have?
     
    #4 cadbrowne, Apr 5, 2017
    Last edited: Apr 5, 2017
Thread Status:
Not open for further replies.