PUT /api/v1/object_manager_attributes/[ID of the object]
Ou can set the input type in the body.
I am not sure if this working with 3-digit numbers but it works great with regular phone numbers.
We have added “Direktdurchwahl” as an object. So additionally to Phone and Mobile we had a third object for a phone number. Also here our CTI integration did not find this number. But after changing the type to “input > tel” it worked fine.
In our case the phone number would be +49 30 577 017 10 and the “Direktdurchwahl” would be +49 30 577 017 125. So it still is a complete number, not only the last 3 digits.
We use this since some of our customers phone out with their “central number” but when I want to call them, I don’t want to got through their front desk but call them directly.
I have tried to enter our internal 2 digit extension and called my colleague but that is not working. So it might be the length of the digits or maybe the cti api does provide a different/complete number?!
I solved this problem on the phone server side instead of Zammad. In the script that does the notification to Zammad I added a rewrite rule. In case an internal caller signals only the 3 digit extension number it gets changed to the complete number before calling the Zammad CTI api.
Maybe that is an option for you.