Call Journaling not working after upgrading 3CX too version 18.0 (Build 307)

[Willemsbrug]

Hi,

After upgrading 3CX Our CRM intergration (D365) is no longer doing Call Journaling even though the toggle is enabled in the interface. Querying (using the test fucntionallity) seems to be working fine.

I've tried reconfiguring CRM intergration from the 3CX interface but that yielded no result.

Am I missing something? We're using a custom template which i've uploaded after updating 3CX.

Thanks in advance!

 

[Evolute IT]

Hi,

After upgrading 3CX Our CRM intergration (D365) is no longer doing Call Journaling even though the toggle is enabled in the interface. Querying (using the test fucntionallity) seems to be working fine.

I've tried reconfiguring CRM intergration from the 3CX interface but that yielded no result.

Am I missing something? We're using a custom template which i've uploaded after updating 3CX.

Thanks in advance!

1. Did you update your custom template to use the new fields for v18? EntityId/EntityType.

2. The U2 currently has a bug with the call journaling not working in all cases but that has been fixed in U3 Beta.

 

[Willemsbrug]

I have not made any andjustments to our custom template yet. Could you specify on the new fields we need to update?

I've enabled verbose logging and the error we're getting regarding abovementioned is:

Cannot create activity party: either partyid or addressused field should be present

Which i'm guessing correlates to your first suggestion.

 

[Evolute IT]

I have not made any andjustments to our custom template yet. Could you specify on the new fields we need to update?

I've enabled verbose logging and the error we're getting regarding abovementioned is:

Cannot create activity party: either partyid or addressused field should be present

Which i'm guessing correlates to your first suggestion.

You need to return EntityId and EntityType now in your lookups, those are saved in the phonebook and used during the Call Journaling, instead of the "Contact::" variables (which are no longer available.)

As for the partyid, it might be the fact that you didn't update the template.

Refer to the XML schema to know all the variables and outputs names.

 

[Willemsbrug]

Hi again!

It took me some time to figure out what changes needed to be made in the template. But I figured it out and refactored all Contact:: variables to EntitiyId/EntityType.

However im still getting the same error: Cannot create activity party: either partyid or addressused field should be present

I'll try your second suggestion to see if that works and will update here when done so.

 

[Evolute IT]

Hi again!

It took me some time to figure out what changes needed to be made in the template. But I figured it out and refactored all Contact:: variables to EntitiyId/EntityType.

However im still getting the same error: Cannot create activity party: either partyid or addressused field should be present

I'll try your second suggestion to see if that works and will update here when done so.

It could be related to a CRM bug in U2 (fixed in U3) where call reporting does not always find a contact if your setting is set to Match X number of digits.

 

[Willemsbrug]

Upgrading too U3 fixed it! Thanks!

 

[Willemsbrug]

Hi @ConceptsWeb,

I celebrated a bit too soon. After upgrading too v18 U3 call journaling is working fine but number matching doesn't seem to be working anymore.

Using the test functioanlity from the 3CX CRM Integration interface, it doesn't matter what number i query it always gives the message:

"CRM Integration is working OK but contact number does not exist. Check log for more info or try a different number."

I've tried different settings with regards to number matching in Advanced> contact > options:

- Match last 6/7/9/10 digits;
- Match exactly.

Any suggestions would be appreciated!

 

[Willemsbrug]

Still facing this issue: any guidance too a solution would be much appreacited.

Thank you!

 

[Evolute IT]

Still facing this issue: any guidance too a solution would be much appreacited.

Thank you!

You'll need to check the logs.