We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.2
cat /etc/os-release
Caller is not identified if the caller has only entered a telephone number (no firstname, lastname, email).
Caller should get identified, even if the caller has only entered a telephone number (no firstname, lastname, email).
curl --request POST 'http://localhost:3000/api/v1/users' -H "Authorization: Token token=XXX" --header 'Content-Type: application/json' \ --data-raw '{ "phone": "493012345" }'
curl --request POST 'http://localhost:3000/api/v1/cti/XXX' \ --header 'Content-Type: application/json' \ --data-raw '{ "event": "newCall", "from": "493012345", "to": "490000001", "direction": "in", "callId": "307fa962-de8d-4ffc-817b-7f699320415991", "user": ["Christopher Miller", "Emma Taylor"] }'
Verify caller log entry, you can see the caller didn't got identified.
Ticket#10152999
yes
The text was updated successfully, but these errors were encountered:
Fixes #5117 - Caller is not identified if the caller has only entered…
b27a0d2
… a telephone number (no firstname, lastname, email).
da3e688
a511033
martini
No branches or pull requests
Used Zammad Version
6.2
Environment
cat /etc/os-release
): anyActual behaviour
Caller is not identified if the caller has only entered a telephone number (no firstname, lastname, email).
Expected behaviour
Caller should get identified, even if the caller has only entered a telephone number (no firstname, lastname, email).
Steps to reproduce the behaviour
Verify caller log entry, you can see the caller didn't got identified.
Support Ticket
Ticket#10152999
I'm sure this is a bug and no feature request or a general question.
yes
The text was updated successfully, but these errors were encountered: