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, 2023 Report Share Posted May 30, 2023 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, 2023 Report Share Posted May 30, 2023 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...
Matevz Posted April 10 Report Share Posted April 10 Hi Team we have sold the PBX to one of our customers with hope CRM integration with Hubspot will work; however due to too many issues with PC softphone client on v69, we cannot upgrade our production server to that version. Any chance you could push update for OAuth and Hubspot integration to v68 so I can use this feture on your most stable Version 68.0.37? thank you Quote Link to comment Share on other sites More sharing options...
Vodia Telephone System Posted April 15 Report Share Posted April 15 The oauth hubspot is supported only in v69. And v69.2.4 is pretty stable. But if they still want to stay with v68, then they can do it the old way with hubspot but have to create a private app (essentially integration) in Hubspot that uses the API key. You can open a ticket for further details if needed. Thanks, Quote Link to comment Share on other sites More sharing options...
Matevz Posted April 15 Report Share Posted April 15 thanks, will attempt latest version again, I can see windows desktop app is performing better now, so hopefully we can finally transition Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted July 16 Report Share Posted July 16 Has anyone had any luck with HubSpot (with private apps and API) with Vodia 68.0.37? Quote Link to comment Share on other sites More sharing options...
Matevz Posted July 16 Report Share Posted July 16 Hi didn't work for me, I was advised to move to new version, but still not that confident about it as I still get random issues with notifications not working unless app is restarted. Still not that confident on moving our production to this version 69. Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted July 16 Report Share Posted July 16 3 hours ago, Matevz said: Still not that confident on moving our production to this version 69. yep, too many issues to move production yet. Need to get Hubspot working though.. we even got the client to setup private apps because Viodia claim it works this way. Quote Link to comment Share on other sites More sharing options...
Matevz Posted July 17 Report Share Posted July 17 I had support ticket on this as we tried to get it going with v68 but haven't had much luck. They proposed to just push with upgrade. They tried to fix some issues reported with the app but also didn't get far I have updated to latest version today (v69.3.2) on our staging server and testing it and so far not too many issues... Hopefully we are finally ready to change our production over Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted July 17 Report Share Posted July 17 Our main issue with 69 is the account cost changes. We use call queues as standard call management ... we need to be able to either change this or provide a reasonable reason why we are increasing the costs. Upgrading because 1 client wants to use HubSpot will impact all. Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted July 17 Report Share Posted July 17 is this part of the problem? No hubspot?? Quote Link to comment Share on other sites More sharing options...
Matevz Posted July 17 Report Share Posted July 17 Hi Richard I believe above is client side CRM integration (extension directly talks to CRM) server side is done in admin portal, but I couldn't get it working, even though I have followed the setup guide, just nothing got pushed to Hubspot. Hopefully it works in new version, however I think it is still some limitations with it Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted Sunday at 10:21 PM Report Share Posted Sunday at 10:21 PM On 7/17/2024 at 10:09 AM, Matevz said: I have updated to latest version today (v69.3.2) on our staging server and testing it and so far not too many issues... Hopefully we are finally ready to change our production over do you use the Windows app or Grandstream phones? We have big issues with both of those on V69. Quote Link to comment Share on other sites More sharing options...
Matevz Posted Sunday at 11:28 PM Report Share Posted Sunday at 11:28 PM We are on Yealink deskphones and Windows app. Since last update looks a lot more stable Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted Sunday at 11:31 PM Report Share Posted Sunday at 11:31 PM Yealink and HTek phones seem ok, Grandstream wont dial out (but will if I revert back to V68). How did you stop the Windows app call notification from staying on screen? Our client is reliant on it so we cant simply disable notifications. Quote Link to comment Share on other sites More sharing options...
Matevz Posted Monday at 12:36 AM Report Share Posted Monday at 12:36 AM Hi Richard you can't disable notifications as otherwise you will not be able to get notified on new calls. When we updated from 69.1 to 69.1.3 this stopped, however there were other issues since we did last patch, we don't have issues with notifications - there are couple of minor glitches, but nothing that would cause issues with the service so far Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted Monday at 01:03 AM Report Share Posted Monday at 01:03 AM 16 minutes ago, Matevz said: you can't disable notifications as otherwise you will not be able to get notified on new calls yes, exactly. 16 minutes ago, Matevz said: When we updated from 69.1 to 69.1.3 and still ok with 69.3.2? We were testing with V69.3.2 and Windows app 6.2.1. The message notifications stay on the screen if another queue member or ring group member answers the phone. Quote Link to comment Share on other sites More sharing options...
Matevz Posted Wednesday at 03:54 AM Report Share Posted Wednesday at 03:54 AM Hi Richard strange, not happening on my side anymore. Had this issue with versions below 69.1 the main issue that latest build resolved was issue: 1. Receiving or making call 2. remote side hangs up 3. App will flash and unless you click on X on hanged up call, your extension will be busy Had to restart the phone every time this happened. Quote Link to comment Share on other sites More sharing options...
Matevz Posted Wednesday at 03:56 AM Report Share Posted Wednesday at 03:56 AM I guess the only thing that sometimes helped with the app is to clear storage or reinstall the app, especially after upgrades Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted Wednesday at 05:50 AM Report Share Posted Wednesday at 05:50 AM update: Changing the GS SRTP mode to 'Optional' and if in a queue log out and back in seems to cure the GS external calling issue. The notification on the Windows app now seems to do what it is suposed to .. except if it is paired with another phone. If it is in a queue or ring group then when another caller answers the call the notification dissapears, but if you answer it on another phone (same ext.) the notification remains. Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted Wednesday at 07:29 AM Report Share Posted Wednesday at 07:29 AM any tricks? When I try to add another tenant to their HubSpot using the OAuth token button all I can see is our Hubspot account.. no option to add another. It seems it was because I was logged into our account. ...... it is now prompting me for login details for a new account, this will mean I will get access to our clients HubSpot data? If they change login details will that mean I need to reinstate the OAuth? Quote Link to comment Share on other sites More sharing options...
RichardDCG Posted Thursday at 05:56 AM Report Share Posted Thursday at 05:56 AM On 7/24/2024 at 1:54 PM, Matevz said: strange, not happening on my side anymore. Had this issue with versions below 69.1 the main issue that latest build resolved was issue: 1. Receiving or making call 2. remote side hangs up 3. App will flash and unless you click on X on hanged up call, your extension will be busy Had to restart the phone every time this happened. odd things happening. The notifications did seem to start working properly for no apparent reason. ..... then started banking up again. But for individual users not all users as was before. Nothing changed on PC's or PBX. The same PC that has calls banking up can login as another extension and the notifications clear on an answered call, then when they log back in as their ext. the notifications start banking again! It seems to be some sort of caching, but nothing seems to clear it. We also get the 1,2,3 point above. Have they resolved for you? 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.