Call direction discrepancy between call log and recording endpoints

Phone
1

We use zoom’s phone API to retrieve recordings and call logs. We noticed that the direction in the recording response differs from the response for the pertaining call log for the same call log id. Why is this? We should have the same direction on both responses; which one is correct and how can we work round this?

Recording response: (from /phone/recordings)

{
  "id": "recording_123",
  "caller_number": "caller_123",
  "caller_number_type": 2,
  "caller_name": "caller_name_123",
  "callee_number": "callee_123",
  "callee_number_type": 1,
  "callee_name": "Foo Bar",
  "direction": "outbound",
  "duration": 292,
  "download_url": "download_url_foobar",
  "file_url": "file_url_foobar",
  "date_time": "2024-05-21T09:48:07Z",
  "recording_type": "Automatic",
  "call_log_id": "call_log_123",
  "call_id": "call_123",
  "owner": {
    "type": "user",
    "id": "user_123",
    "name": "Foo Bar",
    "extension_number": 1234567890
  },
  "site": {
    "id": "site_123"
  },
  "end_time": "2024-05-21T09:52:59Z",
  "disclaimer_status": 0
}

Call log response:

{
  "id": "call_log_123",
  "user_id": "user_123",
  "call_type": "voip",
  "caller_number": "caller_phone_number_123",
  "caller_number_type": 2,
  "caller_number_source": "external",
  "caller_location": "United Kingdom",
  "callee_user_id": "callee_user_id_123",
  "callee_number": "callee_phone_number_123",
  "callee_number_type": 1,
  "callee_name": "Foo Bar",
  "direction": "inbound",
  "duration": 293,
  "result": "Auto Recorded",
  "date_time": "2024-05-21T09:48:05Z",
  "path": "pstn",
  "site": {
    "id": "site_123",
    "name": "site-name-foo-bar"
  },
  "recording_id": "recording_123",
  "recording_type": "Automatic",
  "has_voicemail": false,
  "call_id": "call_123",
  "owner": {
    "type": "user",
    "id": "owner_123",
    "name": "Foo Bar",
    "extension_number": 1234567890
  },
  "caller_country_code": "44",
  "caller_country_iso_code": "GB",
  "callee_did_number": "callee_phone_number_123",
  "callee_country_code": "44",
  "callee_country_iso_code": "GB",
  "answer_start_time": "2024-05-21T09:48:06Z",
  "call_end_time": "2024-05-21T09:52:59Z",
  "department": "dept_123",
  "cost_center": ""
}
2

Is anyone still available to answer this query?

3

Hi @dlzoomdev , not sure for this. What is the complete call path?

5

Hi @gianni.zoom

Thanks for getting back to me. The first payload is the response for /phone/call_logs/:id/recordings and the second payload is the response for /phone/call_logs/:callLogId.

Would it be possible to have a private call to help you diagnose this further?

6

Hi @dlzoomdev , can you please review this document:

It speaks to getting the call path which may be able to illuminate for the behavior you’re seeing. If it still does not line up after then, we can figure out next steps for clarity.

7

Hi @gianni.zoom

I used the old endpoint /phone/call_logs/:callLogId as well as the new endpoint /phone/call_history/{callLogId} and both of the them share the same discrepancy; they both show the call direction as inbound but /phone/call_logs/:id/recordings shows the same call as having a direction of outbound.

I would like to request a further investigation - can we figure out what steps we need to take?

8

Hi @gianni.zoom

Can we get an update on this issue we reported please? It would be good to have a private chat with you or another of your peers to disucss this further as there may be information to be shared to assist you further.

Cheers,

9

Hi @dlzoomdev ,

Yes please provide the following in the private message I’m initiating (check notifications) and I will escalate accordingly:

  • client id

  • dev email associated with credentials making API request

  • API response zm-tracking-id (found in the response headers) from all responses

  • screenshots of call direction fields

10

Hi @dlzoomdev , thanks for providing the info needed to test! This is being investigated internally and I will share more updates as they become available (ZSEE-135322).

1 Like
11

Followed up with service engineering on this. Still waiting to hear back.

1 Like