SDP and ICE Candidate retrieval via Conversation API v2

NICE CXone API & Integrations
1

Greetings team members. We are investigating a discrepancy between the SIP signaling logs and the data returned by /api/v2/conversations/{conversationId}. According to RFC3261 section 14, the SDP should contain ICE candidates during the offer/answer exchange. However, when querying conversation details at us-east-1 on Genesys Cloud version 2023.09, the mediaDetails array returns null for ICE candidates. We are using the standard OAuth token flow. The SIP trace confirms successful ICE connectivity. See below for the API request:

GET /api/v2/conversations/{conversationId}
Authorization: Bearer {token}

Is there a specific flag required to expose these fields in the API response?

2 Likes
2

Apologize for asking something basic but the authentication seems off. Tried to pull the same data using Python requests. Code looks like this:

import requests
token = get_token()
headers = {Authorization: Bearer ${token}}
resp = requests.get(url, headers)

The script fails with a 401 error every time. The issue appears to be in the header syntax. Does anyone know if the token needs to be refreshed more frequently for call detail endpoints?

2 Likes
3

Rate limits are likely the bottleneck here when querying high volumes. Used JMeter to simulate concurrent call retrievals and saw throttling after 50 requests per second. Suggest batching the API calls by querying for conversation details instead of individual lookups.

Verified this approach reduces latency significantly during peak load testing sessions.

2 Likes