I am trying to fetch SIP Invite headers information using SIP Traces API , I could see it to have the information i am looking for but when i run this API in Data action or in Developer tools i am getting response as 200 OK and the Data is empty as in below.
API -- /api/v2/telephony/siptraces
For input i am passing
Start Date - 2020-10-20T00:07:21.205-07:00
End Date - 2020-10-20T23:07:21.205-07:00
Conversation ID -- <>
Response i am getting is
{
"data": [],
"count": 0,
"selfUri": "/api/v2/telephony/siptraces"
}
Not sure if i am missing anything , please advise.
The first thing I would do is make sure that your OAUTH client you are using in data actions or your personal credentials (in the developer tools) have the following permissions: telephony:pcap:view and the following OAuth scopes: telephony and telephony:readonly. Scopes are irrelevant when using a client credential grant because client credential grants are auto-configured with an everything scope.
Just in case, if you are looking for the SIP Call-ID of a call, associated with a specific Conversation (Conversation ID), note that this piece of information is also available in the Analytics Conversation Details.
In the response (conversation details), there is a "protocolCallId" attribute, in the conversation -> participant -> session.
If you take the first participant on an inbound call (customer/external), the "protocolCallId" will contain the SIP Call-ID of the incoming call (coming from the SIP Trunk Provider/gateway/...).
There is no conversion that I am aware of.
As a clarification, I am not in Product Management/Engineering - I just used this query in the past for a test/integration I was working on.
It was with a Twilio SIP Trunk to Genesys Cloud (BYOC Cloud - Edges in the cloud).
The Call-ID I could retrieve using Analytics Conversation Details and the "protocolCallId" (under the first conversation participant - that represents the entry/start point of the voice call - call from the SIP Trunk in our case) was the exact same one I could find in PCAP traces on Twilio side.
So it seems to copy the exact Call-ID string value - no processing/conversion - into "protocolCallId".
One clarification - just in case: each participant involved in the call will have its own SIP Call-ID. The Genesys Cloud platform is not acting as a SIP Proxy for the call's participants. You will find the SIP Call-ID used by each participant in the "protocolCallId" attribute under the corresponding conversation's participant.