qmexnetworks / 3cx-zammad-bridge

Monitors calls in 3CX and forwards this to Zammad
European Union Public License 1.2
15 stars 0 forks source link

V18 | Anruf aus Warteschlange #7

Open tg53 opened 7 months ago

tg53 commented 7 months ago

Hallo!

Wir haben 3CX v18 mit der zammadbridge verbunden. Das funktioniert auch soweit, aber nur bei direkten Anrufen an eine Nebenstelle.

Nach unserer Warteschlange, wenn am Haupttelefon abgehoben wird, wird der Anruf auch im Anrufprotokoll bei Zammad eingefügt, nur direkt ausgegraut und kommt nicht links in der Sidebar von Zammad. Der Anruf wird auch nur dann erkannt, wenn der Anruf entgegengenommen wird.

Wenn man nun eine Nebenstelle anruft, erscheint dieser direkt beim Klingeln in der Sidebar.

config.yaml:

Bridge:
  poll_interval: 0.5

3CX:
    user: "XX"
    pass: "XXX"
    host: "https://XXX"
    group: "DEFAULT"
    extension_digits: 2
    trunk_digits: 5
    queue_extension: 85
    country_prefix: 43

Zammad:
    endpoint: https://XX/api/v1/cti/XX
    log_missed_queue_calls: true

Log:

2024/04/09 10:39:17 Loaded extensions: [00 01 02 04 06 12]
2024/04/09 10:42:59 New call (Routing) with ID 5cc971ff-0982-4cea-a1cc-cd69f62439ae Inbound from 0660XXXXXXX to 02
[VERBOSE] 2024/04/09 10:42:59 Zammad Request - JSON Body: {"event":"newCall","from":"0660XXXXXXX","to":"02","direction":"in","call_id":"5cc971ff-0982-4cea-a1cc-cd69f62439ae","callid":"5cc971ff-0982-4cea-a1cc-cd69f62439ae","answeringNumber":"02","user":"XX1"}
[VERBOSE] 2024/04/09 10:42:59 Zammad Response - HTTP 200
[VERBOSE] 2024/04/09 10:43:12 Call with 3CX-ID 322 and Zammad-ID 5cc971ff-0982-4cea-a1cc-cd69f62439ae not reported by 3CX, assuming call ended
2024/04/09 10:43:12 Call with ID 5cc971ff-0982-4cea-a1cc-cd69f62439ae Inbound was not answered
[VERBOSE] 2024/04/09 10:43:12 Zammad Request - JSON Body: {"event":"hangup","from":"0660XXXXXXX","to":"02","direction":"in","call_id":"5cc971ff-0982-4cea-a1cc-cd69f62439ae","callid":"5cc971ff-0982-4cea-a1cc-cd69f62439ae","cause":"cancel","answeringNumber":"02"}
[VERBOSE] 2024/04/09 10:43:12 Zammad Response - HTTP 200
2024/04/09 10:54:02 New call (Talking) with ID c2eb9780-d6df-4124-afe3-850ab707c84b Inbound from 0660XXXXXXX to 00
[VERBOSE] 2024/04/09 10:54:02 Zammad Request - JSON Body: {"event":"newCall","from":"0660XXXXXXX","to":"00","direction":"in","call_id":"c2eb9780-d6df-4124-afe3-850ab707c84b","callid":"c2eb9780-d6df-4124-afe3-850ab707c84b","answeringNumber":"00","user":"XX2"}
[VERBOSE] 2024/04/09 10:54:02 Zammad Response - HTTP 200
2024/04/09 10:54:03 Call with ID c2eb9780-d6df-4124-afe3-850ab707c84b Inbound from 0660XXXXXXX was answered by 00
[VERBOSE] 2024/04/09 10:54:03 Zammad Request - JSON Body: {"event":"answer","from":"0660XXXXXXX","to":"00","direction":"in","call_id":"c2eb9780-d6df-4124-afe3-850ab707c84b","callid":"c2eb9780-d6df-4124-afe3-850ab707c84b","answeringNumber":"00","user":"XX2"}
[VERBOSE] 2024/04/09 10:54:03 Zammad Response - HTTP 200
[VERBOSE] 2024/04/09 10:54:09 Call with 3CX-ID 323 and Zammad-ID c2eb9780-d6df-4124-afe3-850ab707c84b not reported by 3CX, assuming call ended
2024/04/09 10:54:09 Call with ID c2eb9780-d6df-4124-afe3-850ab707c84b Inbound was hangup
[VERBOSE] 2024/04/09 10:54:09 Zammad Request - JSON Body: {"event":"hangup","from":"0660XXXXXXX","to":"00","direction":"in","call_id":"c2eb9780-d6df-4124-afe3-850ab707c84b","callid":"c2eb9780-d6df-4124-afe3-850ab707c84b","cause":"normalClearing","answeringNumber":"00"}
[VERBOSE] 2024/04/09 10:54:09 Zammad Response - HTTP 200