Search results

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

I changed my hello_world (still waiting for approval) to:

I changed my "hello world" template in Meta's Whatsapp manager to new text for my company. Now I'm waiting for approval.

is this similar to https://www.3cx.com/community/threads/changing-the-default-hey-there-im-using-whatsapp-message.117565/

@okjose Changed my settings with your Postman example, worked great. @Nick Galea @Charles_3CX Please add this to 3CX. https://www.3cx.com/community/threads/changing-the-default-hey-there-im-using-whatsapp-message.117565/post-569477

You can use PhoneHome or PhoneHome2, but you have to define an output to PhoneHome or PhoneHome2 in your CRM template. See https://www.3cx.com/docs/server-side-crm-template-xml-description/#h.sby5dun21u5a

I don't know if it's related, barge, listen and whisper work in Webclient, but not in Desktop App (On pemise Debian 18.0 (Build 418), installed from Iso). Webclient / Panel / right click on call: In Desktop App 18.10.461 I have no option to barge in, listen or whisper right click webclient:

I'm on Enterprise 18.0 Update 5 (Build 418), Debian on premise (ESXi 7). When I try to register a Whatsapp sip trunk I get the following error in 3CX's activity log, Lc:10000(@WhatsAppAH[<sip:@:0/UDP>]) has invalid configuration: primary target is empty My business Whatsapp number is working...

DECT templates are located in /var/lib/3cxpbx/Data/Http/Templates/fxs and /var/lib/3cxpbx/Instance1/Data/Http/Templates/fxs (Debian). You have to change this parameter after every update.

Click on +1 in first post of this thread.

Please add Gigaset Nx70 as CSTA supported. It works since 2019.

Hello edossantos, thank you for your answer.Our CRM integration is working now. Perhaps I had a typo during my tests.

Hi All, I've created a custom CRM template for our ERP system. It uses a REST matching scenario and gets an XML result. Looking for 123456789 will find contacts in our ERP with separators blank " ", dash "-" or slash "/" in phone numbers like "123 4567 89", "1234-56789" or "12334/56789". Parsing...

Since Gigaset firmware version 2.43 there is an option to change this. See provisioning example here: https://teamwork.gigaset.com/gigawiki/pages/viewpage.action?pageId=902955346 <!-- New in SW 2.43.0 or higher name = Display results: name surname, surname = Display results: surname name -->...

Here is a thread in 3CX's German forum, with a solution (and more than one phone number) https://www.3cx.de/forum/threads/vollst%C3%A4ndige-telefonb%C3%BCcher-f%C3%BCr-gigaset-und-snom-workaround.96828/

https://github.com/qmexnetworks/3cx-zammad-bridge Works on my V16.

You need a PRO ode ENT licence. https://www.3cx.com/community/threads/jabra-engage-headset-integration-did-not-work.82695/post-383878

Has anybody tested CSTA on a Gigaset N870 DECT base with v18? I know - it is not supported by 3CX but works well on my v16 for 2 years now.

3cx-zammad-bridge monitors incoming calls in 3CX and communicates this to Zammad ticket system (https://zammad.org/ or https://zammad.com) accordingly. Perhaps you can use this as a starting point: https://github.com/qmexnetworks/3cx-zammad-bridge

Unfortunally 3Cx only publishes one number "mobile phone" in your phonebook. There exist several scrips which will send all numbers (home, work, ...) to Snom and Gigaset. Works well with my Snom M700 and Gigaset N870. See this thread in 3cx's german forum...