3CX / Zammad Integration Status

[noneya]

Hello, just looking for an update on the Zammad integration. I see notes on this going back to 2020, but nothing solid.

Is there any beta available for this we can test? We are self hosting both Zammad and 3CX

Thanks

 

[edossantos]

Unfortunately there is no official integration for Zammad at the moment.

 

[Guillaume Bourgeois]

You can try this one, maybe it still works. I have not tested

https://www.3cx.com/community/threads/zammad-integration-template.86036/post-406520

Shared by @greychain
Go tell him thank you.
NO OFFICIAL INTEGRATION
At your peril !​

 

[avido]

Hi!

Anybody was successful to integrate Zammad in v20?

 

[Evolute IT]

You can try this one, maybe it still works. I have not tested

https://www.3cx.com/community/threads/zammad-integration-template.86036/post-406520

Shared by @greychain
Go tell him thank you.
NO OFFICIAL INTEGRATION
At your peril !​

Hi!

Anybody was successful to integrate Zammad in v20?

Try this one?

If that doesn't work then it needs modifications most likely. If you know APIs, you can probably fix it.

 

[avido]

Yes we have a client and his programmer adapted the template but there is still problems ongoing
This is the feedback we got from the programmer.

I have now created a new version of the template. The only problem was that the API in the template that you used (http://worldclockapi.com/api/json/utc/now) is no longer available and your replacement (http://worldtimeapi .org/api/timezone/Europe/Vienna) provides a different time format. For testing purposes, I deployed an API that provides exactly the right format: https://worker-utc-datetime.matthias-411.workers.dev/

Theoretical this should have correlated the calls correctly most of the time based on the time it took to ring and hang up. However, during testing I noticed that there are other problems with 3CX. Apparently the integration works differently depending on whether you're using the test or actually calling. In the case of a real call, the phone number is incorrect (as you described, only the last few digits without an area code) and the time API is not called correctly. These problems do not seem to be remediable at the moment. It seems to me as if this is one of the problems that 3CX introduced when switching to v20 and has not yet solved. So far I haven't found anyone online who could integrate with v20.

 

[Evolute IT]

Then you must check the logs and figure out what's wrong.

3CXSystemService.log, search for "CRM:" to find all CRM related stuff.

 

[autohaus]

You can also use this tool: https://github.com/qmexnetworks/3cx-zammad-bridge

It monitors 3cx queue calls and reports them to Zammad. Works with V18

 

[avido]

You can also use this tool: https://github.com/qmexnetworks/3cx-zammad-bridge

It monitors 3cx queue calls and reports them to Zammad. Works with V18

ok, i will forward the info to the programmer to make a Test with v20

Just notice suppossed will not work

Caution

So far its not working with 3CX V20, 3CX announced a new API for Update 2 as soon as the new API is out we can make the bridge work again, as 3CX V20 is not feature complete yet, you should stick with V18