- Joined
- May 23, 2024
- Messages
- 7
- Reaction score
- 0
Hi,
I previously had a working SuiteCRM API integration with 3CX v18, but since upgrading to 3CX v20, I'm unable to establish a proper connection.
On the SuiteCRM side, I verified that the refresh_token is correctly generated during OAuth communication—this seems to be working fine. However, it appears that parsing my XML configuration causes a crash in 3CX v20, and no connection attempts are even initiated towards SuiteCRM (verified via tcpdump).
The 3CX integration test returns the following message:
Despite this message, no CRM log is generated, and the existing logs contain no exceptions or useful details.
Interestingly, if I remove the scenario ID attribute from my XML configuration, changing from:
<Scenario Id="Contacts" Type="REST" EntityId="Contacts" EntityOrder="[LookupOrder]">
to:
<Scenario Type="REST" EntityId="Contacts" EntityOrder="[LookupOrder]">
then I do get a connection established and see clear error messages in the CRM log of 3CX ("scenario ID is missing...") . However, as soon as I add the ID attribute back, the integration reverts to the previous issue—showing the "all ok" message, but without actual communication.
Could you please help identify what's causing this XML configuration issue or crash in 3CX v20?
I've attached the complete XML file for your reference.
Thanks in advance for your assistance!
I previously had a working SuiteCRM API integration with 3CX v18, but since upgrading to 3CX v20, I'm unable to establish a proper connection.
On the SuiteCRM side, I verified that the refresh_token is correctly generated during OAuth communication—this seems to be working fine. However, it appears that parsing my XML configuration causes a crash in 3CX v20, and no connection attempts are even initiated towards SuiteCRM (verified via tcpdump).
The 3CX integration test returns the following message:
"CRM-Integration funktioniert ordnungsgemäß, aber die Kontaktnummer wurde nicht gefunden. Überprüfen Sie das Protokoll für Details oder versuchen Sie es mit einer anderen Nummer."
Despite this message, no CRM log is generated, and the existing logs contain no exceptions or useful details.
Interestingly, if I remove the scenario ID attribute from my XML configuration, changing from:
<Scenario Id="Contacts" Type="REST" EntityId="Contacts" EntityOrder="[LookupOrder]">
to:
<Scenario Type="REST" EntityId="Contacts" EntityOrder="[LookupOrder]">
then I do get a connection established and see clear error messages in the CRM log of 3CX ("scenario ID is missing...") . However, as soon as I add the ID attribute back, the integration reverts to the previous issue—showing the "all ok" message, but without actual communication.
Could you please help identify what's causing this XML configuration issue or crash in 3CX v20?
I've attached the complete XML file for your reference.
Thanks in advance for your assistance!