JCH | 2022-04-08 07:05:45 UTC | #1
Hi, I can find the sip call-id using /api/v2/telephony/siptraces that is all good, but is there a api that could be used to find the interactionID linked to the call-id when i have the call-id ?
Best Regards Johan
jcp | 2022-04-08 08:03:18 UTC | #2
Hi The interactionID is the same as the conversationId parameter returned in the SIP Trace.
https://help.mypurecloud.com/glossary/conversation/
JCH | 2022-04-08 08:23:31 UTC | #3
Hi, I understand that the interactionID is the same as conversationsID, my question was if I have the call-id and would like to get the interactionID/ConversationID that is linked to that call-id.
If I for instance use that api /api/v2/telephony/siptraces and search using call-id as the search string, I don´t get the Interaction/Converstaion ref back.
"data": [ { "id": "0", "method": "INVITE", "ruriUser": "xxx", "ruriDomain": "18.197.177.95", "fromUser": "yyy", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "zzz", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "1 INVITE", "userAgent": "", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces"
Jerome.Saint-Marc | 2022-04-08 09:07:19 UTC | #4
Hello,
The API endpoint description for GET /api/v2/telephony/siptraces is a bit obscure "For example, some records contain conversationId but not all relevant records for that call may contain the conversationId" But what it means (after doing a test) is that the conversationId attribute will not appear in all of these records. If you are checking an inbound call (external to Genesys Cloud), you should see the conversationId attribute in the record with "method"="200" that should appear after the "method"="INVITE" record.
NB: I also tried this endpoint using conversationId, dateStart and dateEnd as parameters, and all records for that call were returned (including the ones where conversationId does not appear in record attribute).
Regards,
JCH | 2022-04-08 09:35:01 UTC | #5
Thanks, however I don´t see the same on my side when I use BYOC. I am not able to find the conversation anywhere in the output. In my case I have a flow that transfer to number if that could be causing it ?
Complete output, when using call-id as search string with "GET /api/v2/telephony/siptraces":
{ "data": [ { "id": "0", "method": "INVITE", "ruriUser": "x", "ruriDomain": "18.197.177.95", "fromUser": "x", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "x", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "1 INVITE", "userAgent": "", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces" }, { "id": "1", "method": "100", "ruriUser": "", "ruriDomain": "", "fromUser": "x", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "x", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "1 INVITE", "userAgent": "", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces" }, { "id": "2", "method": "200", "ruriUser": "", "ruriDomain": "", "fromUser": "x", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "x", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "1 INVITE", "userAgent": "GENESYS-SIPSERVICE/1.0.0.4740", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces" }, { "id": "3", "method": "ACK", "ruriUser": "x", "ruriDomain": "10.72.240.141", "fromUser": "x", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "x", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "1 ACK", "userAgent": "", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces" }, { "id": "4", "method": "BYE", "ruriUser": x", "ruriDomain": "10.72.240.141", "fromUser": "x", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "x", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "2 BYE", "userAgent": "", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces" }, { "id": "5", "method": "200", "ruriUser": "", "ruriDomain": "", "fromUser": "x", "fromTag": "SDqknq601-6mFLGRcWP1g.", "toUser": "x", "callid": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "cseq": "2 BYE", "userAgent": "GENESYS-SIPSERVICE/1.0.0.4740", "correlationId": "SDqknq601-61e98c427bfad611e5ba49b3f4645917-dimf0f2010", "node": "remotenode", "dbnode": "remotenode", "selfUri": "/api/v2/telephony/siptraces" } ], "count": 6, "selfUri": "/api/v2/telephony/siptraces" }
Jerome.Saint-Marc | 2022-04-08 09:54:55 UTC | #6
Can you try the following?
In your trunk configuration (Admin - Telephony - Trunks), under Protocol section, in "Header/Invite", can you enable the "Conversation Headers" toggle?
This adds a x-inin-cnv header (in 200 OK) with the conversationId. It is enabled by default in my environment and I can't disable it (was a beta). So I can't try without and check if this is what makes the conversationId attribute appear in sip traces.
Let me know.
Regards,
JCH | 2022-04-08 10:24:56 UTC | #7
Thanks, that did the trick I can now see conversationID !!! { "id": "3", "method": "200", "ruriUser": "", "ruriDomain": "", "fromUser": "x", "fromTag": "SDabttd01-ceE5AyZy7lA.", "toUser": "x", "callid": "SDabttd01-6c0b659fe6b7716ad104e6d72cabb2a9-163u120", "cseq": "1 INVITE", "userAgent": "GENESYS-SIPSERVICE/1.0.0.4740", "correlationId": "SDabttd01-6c0b659fe6b7716ad104e6d72cabb2a9-163u120", "node": "remotenode", "dbnode": "remotenode", "conversationId": "5cc06de9-38b3-483d-bb4c-e15c43e0d9b8", "selfUri": "/api/v2/telephony/siptraces" }
system | 2022-05-09 10:25:12 UTC | #8
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 14238