Forward phone numbers over API not working

Phone
,
1

**API Endpoint(s) and/or Zoom API Event
**
with the old and depracted API post/phone/extension/{extensionId}/call_handling/settings/{settingType}

new api
post/phone/users/{userId}/call_forward_settings/{hourType}

**
Description**
with the old and depracted API post/phone/extension/{extensionId}/call_handling/settings/{settingType}

I was able to set phone forwardings so that the get a banner message within its client, that the phonenumber is forwarded.

image
image1360×402 24 KB

With that new API
post/phone/users/{userId}/call_forward_settings/{hourType}

that type of forwarding will not be set.
It is just setting typical callhandlings, but no forwardings.

image
image631×402 12.4 KB

What do I miss?
Why expactaion was, that this is still a functionallty of the number and moved to new number_management API, but here I cannot find anything about call forwarding.

3

Hi @dennis.raulien
Thanks for reaching out to us!
I am happy to look further into this.
Could you please share with me the entire request URL and request body you are sending with the deprecated endpoint, as well as the request URL and request body you are sending with the new endpoint.
That way I will try and reproduce this on my end and escalate this to the right team

4

Hi Elisa,

sure i can give you the needed information.

First of you have to know, that i am working with PowerShell for my Scripts.

This is the older part with the depracted API, which created the call forwarding as expacted for the user, that this is visible and can be disabled.

$extension_ID = <zoom_phone-extension-ID>
$imported_call_forwarding_details.number = <external_phonenumber_in_E164_format>

#create a JSON Body for a new call forward

$jsonbody = @{
"sub_setting_type" = "call_forwarding"
"settings" = @{
  "description" = "Call forwarding to: "+$imported_call_forwarding_details.number
  "phone_number" = $imported_call_forwarding_details.number
  }
} | ConvertTo-Json -Depth 10

#check token and update header if token is expired befgore you call every api.
$headers = Update-Headers
$uri_string = $base_uri + "/phone/extension/" + $extension_ID + "/call_handling/settings/business_hours"

Invoke-RestMethod -uri $uri_string -Method POST -Body $jsonbody -Headers $headers -ContentType "application/json"

And if i am correct. the new one looks like this.

$jsonbody = @{                 
   "holiday_hour_id" = ""
   "break_hour_id" = ""
   "call_forward_settings" = @(@{
       "enable" = $true
       "phone_number" = "+4915238XXXXXX"
       "phone_number_description" = "Dennis EXT"
       "external_contact" = @{
            "external_contact_id" = ""
       }
    })
} | ConvertTo-Json -Depth 10

$uri_string = $base_uri +"/phone/users/" + $user_ID + "/call_forward_settings/business_hours"

Invoke-RestMethod -uri $uri_string -Method POST -Headers $headers -ContentType 'application/json' -Body $jsonbody

But this only creates the opportunity to let the user decide where he want to route his calls and add the option to the call handlings.
But it doesn´t forward the entire number and user to the defined external number as expacted and it also don´t give them the opportunity to disable this forwarding.

5

hi @elisa.zoom
did you noticed my reply and could you validate my findings on this topic?
The case becomes a bit more urgent on our side.

greetings,
Dennis

6

Hey @dennis.raulien
Sorry for the late reply here. I am currently trying to replicate this on my end but I am having trouble reaching the first endpoint you shared. I will continue testing tomorrow and will reach out via DM if I need more details.

7

Hey @dennis.raulien
I am trying to replicate this but I do not get the banner you are showing with the deprecated API call.
Would you be able to meet with me so I can see exactly what you are doing, I will record the call and share logs with our Engineering team.
I will send you my scheduler link via DM so we can find a time to meet