Zoom Phone API - Unable to set outbound caller ID on duplicated line appearances

API and Webhooks
1

API Endpoint(s) and/or Zoom API Event(s)
https://developers.zoom.us/docs/api/phone/#tag/line-keys/PATCH/phone/extension/{extensionId}/line_keys

Description
The key_assignment child attribute outbound_caller_id does not work for duplicated line appearance keys.
Error?
No error message. API returns a 204 message indicating success, but Outbound Caller ID field remains unchanged when viewed on web config. Works correctly for primary (non-duplicated) line appearance.

How To Reproduce
Steps to reproduce the behavior:
*1. Request URL / Headers **(without credentials or sensitive info like emails, uuid, etc.
https://api.zoom.us/v2/phone/extension/:extensionId/line_keys
Body:

{
“line_keys”: [
{
“line_key_id”: “-”,
“index”: 3,
“alias”: “”,
“key_assignment”: {
“extension_id”: “-”,
“extension_number”: “-”,
“phone_number”: “+”,
“display_name”: “-”
},
“outbound_caller_id”: “+12223334444”
}
]
}

2. Bearer token
3. No errors

web_line_keys
web_line_keys1253Ă—455 24.9 KB

2

Hey @gpieroni
Thanks for reaching out and worry for the late reply here! looking into this.
Can you confirm you are passing the same outbound_caller_id for the 3 line keys? is that what you are intending to do?

3

Hi Elisa - yes confirmed - I’m passing the same outbound_caller_id for all 3 line keys. It updates just fine on the first line key but doesn’t update on the other 2 duplicated line keys..

4

Would you please clarify what’s your use case and why would you be passing the same outbound caller ID to different key lines? @gpieroni

5

Hi Elisa - we are using Avaya J100 phones with Zoom, which automatically populate 3 line appearances as described here:

When provisioning Avaya J100 series IP phones, account owners and admins will see a minimum of three-line Key Appearance on their devices, enabling them to program additional keys for line appearances.

We want to send the main company number out as outbound caller ID regardless of which line appearance a user selects. The default is to send their own number out and we have hundreds of these devices which is why we’re looking to streamline their provisioning with the API.

Let me know if you need any more info - thanks!

6

Thanks @gpieroni
This is very helpful. As I don’t have the right set up for testing, it is becoming a little harder for me to troubleshoot and help you.
So to recap. You are using Avaya J100 phones and it is by default that you are getting duplicates (I think I am good until here), when you try to change the outbound caller ID, they just wont change via API? Can you change them manually?

7

Hi Elisa - yes that’s all correct.

I can manually change the outbound caller ID, just not via the API.

Note the API works to change outbound caller ID on the primary line; it just doesn’t work when trying to update the duplicated line appearances.

You can add duplicated line appearances on any user - you don’t need to have an Avaya J100 phone assigned to them if you’d like to test it yourself.

8

Interesting, ok @gpieroni
Could you please share with me the tracking ID of the request you are sending (the example you shared in the very first image). You can find that in the response headers.
I will use this to report this issue on my end

9

Hi Elisa - Here’s the tracking ID of an example. Let me know if you need any additional information. Thanks!

x-zm-trackingid: WEB_113a71a7aa84490fddbc97c5b712d460

1 Like
10

Thanks @gpieroni
I created an internal ticket for our Engineering team to take a look at this ( ZSEE-164481 internal ticket number for reference)

11

Hi @elisa.zoom- has there been any response from the engineering team on this ticket? Thanks!

12

Hi @gpieroni
Thanks for your patience here.
I just heard back from our team, and this has been flagged as a bug. We will enhance this API to support what you see in the web portal.
Thanks for bringing this up, and I will update you when I have an ETA for this fix.

13

Hi @elisa.zoom that’s great news thank you for the update.

1 Like
14

Hey @gpieroni
Quick update about this issue.
I talked to our engineering team again, and they confirmed this is not a bug but a feature request.
He will talk to the Developer to get an ETA and to confirm if this is on the roadmap

15

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.