3CX Integration With QQCatalyst

[NSBG]

Hello,

I am trying to get CRM integration working with QQCatalyst for a customer, and I am having issues getting authentication to work.
3CX is hosted on a Debian server.

The QQC API requires the ClientID and ClientSecret to be sent as a base64 encoded basic authentication header with the username and password sent in the body with a grant_type of "password" which I was able to authenticate with in Postman.

I used the 3CX CRM template builder to make an XML template using OAuth, but I have not been able to figure out how to adjust the template to the necessary format, I get a "Bad Request" response from the CRM. I have tried adding headers to the "Auth" and "OAuthGetRefreshToken" scenarios with the encoded ClientID and ClientSecret and adding post values for the username and password, neither of which changed the response.

I also tried a template with no authentication as noted in This thread but some options shown there do not appear to be available and I am unable to set the token, it seems to be removed when the template is uploaded to the server.

Has anyone been able to get this to work? Any guidance is appreciated.

 

[Evolute IT]

This is not OAuth, but rather Basic auth.

You need to use the Scenario Auth type and create your Auth scenario that will do this request with the correct body.

 

[NSBG]

I was able to get authentication working with this. Thank you!

I am still not getting a popup when answering calls, even though the correct contact url is returned.

I am testing this in the web client with integration set to "Automatically open contact URL when CRM integration is enabled" and no adblock, popups set to allowed.

 

[Evolute IT]

Do you see the contact icon and name in the dialer when the call is incoming?

Also, Chrome/Edge might block popups. Check the address bar right end.

 

[NSBG]

There is no contact icon in the dialer. No contacts at all in 3CX yet. I think the issue may be that the inbound number has a leading 1, while the existing contacts in the CRM are 10-digit only.

The test lookup still returns the correct info with 11-digit numbers, and contact matching is set to 10 digits.

 

[Evolute IT]

There is no contact icon in the dialer. No contacts at all in 3CX yet. I think the issue may be that the inbound number has a leading 1, while the existing contacts in the CRM are 10-digit only.

The test lookup still returns the correct info with 11-digit numbers, and contact matching is set to 10 digits.

Strange. You'll need to check the logs in verbose to see the full request sent to the CRM.

 

[NSBG]

I set a callerID reformatting rule for inbound calls to remove the 1 so they match. It still isn't detecting it as a match for some reason, even though the numbers shown in the logs are now exactly the same. Does it need to match all variables or just the phone number? I have attached the relevant part of the verbose logs in case it helps.

 

[NSBG]

I was able to get this working by enabling the "Enable Contact Creation" option, afterwards CRM contacts were populated in 3CX contacts and call popups started working.

Thank you so much for your help @ConceptsWeb!