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

    Joined:
    Aug 14, 2012
    Messages:
    38
    Likes Received:
    3
    Hi,

    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:

    ACTION
    URL used for call - http://192.168.250.3/ivr/PbxAPI.aspx?func=make_call&from=201&to=210&pin=1234

    ERROR
    Response from 3CX Web app:

    Code:
    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.

    thanks

    Mark
     
  2. pj3cx

    pj3cx Active Member

    Joined:
    Aug 1, 2013
    Messages:
    645
    Likes Received:
    1
    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.