Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

API GET through Make_call not working since v14 upgrade

Discussion in '3CX Phone System - General' started by eQDoBBs, Nov 16, 2015.

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

    Aug 14, 2012
    Likes Received:

    We have a web based CRM to which I have created a script using a CURL call provides one click call functionality with 3CX. This has been working fine, but since I upgraded to v14.1 this weeked, is no longer working.

    When running the URL manually I get an error:

    URL used for call -

    Response from 3CX Web app:

    Parser Error
    Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 
    Parser Error Message: Could not load type 'PbxAPI'.
    Source Error: 
    Line 1:  <%@ Page Language="C#" AutoEventWireup="true" Codebehind="PbxAPI.aspx.cs" Inherits="PbxAPI" %>
    Source File: /ivr/PbxAPI.aspx    Line: 1 
    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18055
    My users are desperate to get this working again.


  2. pj3cx

    pj3cx Active Member

    Aug 1, 2013
    Likes Received:
    Hi there,
    I'm afraid the HTTP API is deprecated in v14 as per document http://www.3cx.com/blog/docs/3cx-http-api/ : "Important Note: HTTP API is available in 3CX Phone System V12 and 12.5 only."

    One should use the others interfaces available such as the Call Control API (http://www.3cx.com/blog/docs/call-control-api/) on server-side or tel protocol (http://www.3cx.com/blog/voip-howto/tel-protocol-3cxphone/) and TAPI driver (comes with 3CXPlugins) on client-side.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.