<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WebEx Contact Center Session IDs in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4703355#M3323</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1401790"&gt;@BlakeR&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, the task and taskDetail objects under search are aggregates.&lt;/P&gt;
&lt;P&gt;We are working on publishing a new type of object that will give you call legs. Will post on this thread once there is an updated ETA and when it is available for testing.&lt;/P&gt;
&lt;P&gt;To answer your query - all call sessions are tracked by the unique taskId = callSessionId = interactionId = is the ID of that interaction and remains constant for the entire lifecycle of the call.&lt;/P&gt;
&lt;P&gt;When you retrieve a call recording you will use the same identifier.&lt;/P&gt;
&lt;P&gt;Now regarding the new callLeg object, it is still in the works - will post once you're able to separate the call legs and obtain separate aggregates. The API does not support that today - you will only get the finalQueue = lastQueue Id and name&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Arunabh.&lt;/P&gt;</description>
    <pubDate>Fri, 14 Oct 2022 12:46:16 GMT</pubDate>
    <dc:creator>Arunabh Bhattacharjee</dc:creator>
    <dc:date>2022-10-14T12:46:16Z</dc:date>
    <item>
      <title>WebEx Contact Center Session IDs</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4695031#M3322</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm trying to track down if WebEx CC has Session IDs I can pull to link multiple Agent Contacts to 1 overall customer session.&lt;/P&gt;&lt;P&gt;Example Call: Customers calls in and is transferred from Agent A -&amp;gt; Agent B -&amp;gt; Agent C before hanging up.&lt;/P&gt;&lt;P&gt;I'm currently using the "Search" Graphql API, and specifically referencing this query:&amp;nbsp;&lt;A href="https://github.com/CiscoDevNet/webex-contact-center-api-samples/blob/main/graphql-sample/allContactFields.graphql" target="_blank"&gt;https://github.com/CiscoDevNet/webex-contact-center-api-samples/blob/main/graphql-sample/allContactFields.graphql&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had our client make test call like the example call above and it only came back as one record instead of 3 separate records.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 21:06:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4695031#M3322</guid>
      <dc:creator>BlakeR</dc:creator>
      <dc:date>2022-09-27T21:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: WebEx Contact Center Session IDs</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4703355#M3323</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1401790"&gt;@BlakeR&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, the task and taskDetail objects under search are aggregates.&lt;/P&gt;
&lt;P&gt;We are working on publishing a new type of object that will give you call legs. Will post on this thread once there is an updated ETA and when it is available for testing.&lt;/P&gt;
&lt;P&gt;To answer your query - all call sessions are tracked by the unique taskId = callSessionId = interactionId = is the ID of that interaction and remains constant for the entire lifecycle of the call.&lt;/P&gt;
&lt;P&gt;When you retrieve a call recording you will use the same identifier.&lt;/P&gt;
&lt;P&gt;Now regarding the new callLeg object, it is still in the works - will post once you're able to separate the call legs and obtain separate aggregates. The API does not support that today - you will only get the finalQueue = lastQueue Id and name&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Arunabh.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Oct 2022 12:46:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4703355#M3323</guid>
      <dc:creator>Arunabh Bhattacharjee</dc:creator>
      <dc:date>2022-10-14T12:46:16Z</dc:date>
    </item>
    <item>
      <title>Re: WebEx Contact Center Session IDs</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4715082#M3324</link>
      <description>&lt;P&gt;Update: The ETA for the new object types (Call Legs, Call Activities, etc) is some time in January (tentative, subject to change based on testing).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2022 18:27:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-contact-center-session-ids/m-p/4715082#M3324</guid>
      <dc:creator>Arunabh Bhattacharjee</dc:creator>
      <dc:date>2022-11-02T18:27:50Z</dc:date>
    </item>
  </channel>
</rss>

