jawaid Posted December 16, 2021 Report Share Posted December 16, 2021 I have enabled HubSpot Integration and put the API key as follows: However when a call has been terminated this is not stored on Hubspot. In the log file I get the following: HTTP 104.17.202.204: Certificate for api.hubapi.com could not be verified Any ideas how I can get around this? Thanks Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 16, 2021 Report Share Posted December 16, 2021 Please make sure that the "Baltimore CyberTrust Root" is installed. If not, reset the certificate list on your PBX or import the following certificate as Trusted Root CA for server authentication: -----BEGIN CERTIFICATE----- MIIDdzCCAl+gAwIBAgIEAgAAuTANBgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJJ RTESMBAGA1UEChMJQmFsdGltb3JlMRMwEQYDVQQLEwpDeWJlclRydXN0MSIwIAYD VQQDExlCYWx0aW1vcmUgQ3liZXJUcnVzdCBSb290MB4XDTAwMDUxMjE4NDYwMFoX DTI1MDUxMjIzNTkwMFowWjELMAkGA1UEBhMCSUUxEjAQBgNVBAoTCUJhbHRpbW9y ZTETMBEGA1UECxMKQ3liZXJUcnVzdDEiMCAGA1UEAxMZQmFsdGltb3JlIEN5YmVy VHJ1c3QgUm9vdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKMEuyKr mD1X6CZymrV51Cni4eiVgLGw41uOKymaZN+hXe2wCQVt2yguzmKiYv60iNoS6zjr IZ3AQSsBUnuId9Mcj8e6uYi1agnnc+gRQKfRzMpijS3ljwumUNKoUMMo6vWrJYeK mpYcqWe4PwzV9/lSEy/CG9VwcPCPwBLKBsua4dnKM3p31vjsufFoREJIE9LAwqSu XmD+tqYF/LTdB1kC1FkYmGP1pWPgkAx9XbIGevOF6uvUA65ehD5f/xXtabz5OTZy dc93Uk3zyZAsuT3lySNTPx8kmCFcB5kpvcY67Oduhjprl3RjM71oGDHweI12v/ye jl0qhqdNkNwnGjkCAwEAAaNFMEMwHQYDVR0OBBYEFOWdWTCCR1jMrPoIVDaGezq1 BE3wMBIGA1UdEwEB/wQIMAYBAf8CAQMwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3 DQEBBQUAA4IBAQCFDF2O5G9RaEIFoN27TyclhAO992T9Ldcw46QQF+vaKSm2eT92 9hkTI7gQCvlYpNRhcL0EYWoSihfVCr3FvDB81ukMJY2GQE/szKN+OMY3EU/t3Wgx jkzSswF07r51XgdIGn9w/xZchMB5hbgF/X++ZRGjD8ACtPhSNzkE1akxehi/oCr0 Epn3o0WC4zxe9Z2etciefC7IpJ5OCBRLbf1wbWsaY71k5h+3zvDyny67G7fyUIhz ksLi4xaNmjICq44Y3ekQEe5+NauQrz4wlHrQMz2nZQ/1/I6eYs9HRCwBXbsdtTLS R9I4LtD+gdwyah617jzV/OeBHRnDJELqYzmp -----END CERTIFICATE----- Quote Link to comment Share on other sites More sharing options...
jawaid Posted December 21, 2021 Author Report Share Posted December 21, 2021 Thanks - already had the certificate for "Baltimore CyberTrust Root", but reset anyway and then it started working. Quote Link to comment Share on other sites More sharing options...
Matevz Posted May 30 Report Share Posted May 30 Hi There I just tried to enable this integration, but looks like Hubspot is now changing API access slightly. I've added permissions to view/create/edit contacts and activities and added API into PBX, but it doesn't read/write anything from Hubspot CRM. Have reloaded "Baltirmore Cybertrust Root" and deleted and re-added as per above. Error Log: [5] 11:58:27.729 APP: Port 959: Incoming call in domain ************ on port 959 trunk **** (1) [5] 11:58:27.729 GENE: Port 959: Received incoming call from inter-office trunk [5] 11:58:27.730 APP: Call 698: New call created with Call-ID 959 [4] 11:58:27.730 APP: Call 698: Dial number ********* [4] 11:58:29.760 TLS: DTLS Client certificate was present, but could not be verified and therefore was ignored [5] 11:58:39.219 SIP: BYE Response: Terminate 9dc78be4@pbx can you help? cheers Matt Quote Link to comment Share on other sites More sharing options...
Vodia Telephone System Posted May 30 Report Share Posted May 30 Yes HubSpot has changed the API. You can still use the old API and authentication method of API key with only private apps, that you can create on HubSpot. Public apps are now OAuth based and we have added that support since 69.0.4, recently released. In the same area where you added the API key before, you have to press the Get OAuth Token button and using your Hubspot account credentials give it access. Then calls should be logged as before. If, it does not work for some reason, please put in a trouble ticket with us. Thanks, Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.