<?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 Call related IDs swapped in the event driven integration (EDI) framework in Contact Pro</title>
    <link>https://community.sinch.com/t5/Contact-Pro/Call-related-IDs-swapped-in-the-event-driven-integration-EDI/m-p/17633#M559</link>
    <description>&lt;P&gt;In version 25Q1, CALL_ID (known as Group ID in Dashboard) and CallGUID (known as Conversation ID in Dashboard) have been swapped in the EDI framework. Please check your EDI configurations used for calls. If you're using these IDs in your call-related configurations, your integration will not work correctly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE border="1"&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH width="60.9688px"&gt;Property&lt;/TH&gt;
&lt;TH width="60.9531px"&gt;JSON data type&lt;/TH&gt;
&lt;TH width="240.578px"&gt;Description&lt;/TH&gt;
&lt;TH width="116.469px"&gt;Reference syntax&lt;/TH&gt;
&lt;TH width="265.031px"&gt;Example values&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="60.9688px"&gt;ID&lt;/TD&gt;
&lt;TD width="60.9531px"&gt;string&lt;/TD&gt;
&lt;TD width="240.578px"&gt;
&lt;P&gt;Unique routing leg identifier of the contact&lt;/P&gt;
&lt;P&gt;For emails, this is the same as Group ID.&lt;/P&gt;
&lt;P&gt;For example:&lt;/P&gt;
&lt;DIV&gt;
&lt;UL&gt;
&lt;LI&gt;Can be used as the contact identifier for the &lt;EM&gt;/contacts&lt;/EM&gt; resource of CMI and RMI&lt;/LI&gt;
&lt;LI&gt;Can be used as the contact identifier for the &lt;EM&gt;/emails&lt;/EM&gt; resource of CMI&lt;/LI&gt;
&lt;LI&gt;In Dashboard, this is known as &lt;STRONG&gt;Conversation ID&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;TD width="116.469px"&gt;{contact.id}&lt;/TD&gt;
&lt;TD width="265.031px"&gt;
&lt;PRE&gt;1166301942A6EE11B3ED58961D1810CC&lt;/PRE&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="60.9688px"&gt;Group ID&lt;/TD&gt;
&lt;TD width="60.9531px"&gt;string&lt;/TD&gt;
&lt;TD width="240.578px"&gt;
&lt;P&gt;Unique group identifier of the contact&lt;/P&gt;
&lt;P&gt;For emails, this is the same as ID.&lt;/P&gt;
&lt;P&gt;For example:&lt;/P&gt;
&lt;DIV&gt;
&lt;UL&gt;
&lt;LI&gt;Can be used as the group identifier for the &lt;EM&gt;/chats&lt;/EM&gt; resource of CMI&lt;/LI&gt;
&lt;LI&gt;Can be used as the contact identifier for &lt;EM&gt;/emails&lt;/EM&gt; resource of CMI&lt;/LI&gt;
&lt;LI&gt;In Dashboard, this is known as &lt;STRONG&gt;Group ID&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;TD width="116.469px"&gt;{contact.guid}&lt;/TD&gt;
&lt;TD width="265.031px"&gt;
&lt;PRE&gt;5AB6E20342A6EE11B3ED58961D1810CC&lt;/PRE&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
    <pubDate>Fri, 13 Dec 2024 14:25:44 GMT</pubDate>
    <dc:creator>Niina_P</dc:creator>
    <dc:date>2024-12-13T14:25:44Z</dc:date>
    <item>
      <title>Call related IDs swapped in the event driven integration (EDI) framework</title>
      <link>https://community.sinch.com/t5/Contact-Pro/Call-related-IDs-swapped-in-the-event-driven-integration-EDI/m-p/17633#M559</link>
      <description>&lt;P&gt;In version 25Q1, CALL_ID (known as Group ID in Dashboard) and CallGUID (known as Conversation ID in Dashboard) have been swapped in the EDI framework. Please check your EDI configurations used for calls. If you're using these IDs in your call-related configurations, your integration will not work correctly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE border="1"&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH width="60.9688px"&gt;Property&lt;/TH&gt;
&lt;TH width="60.9531px"&gt;JSON data type&lt;/TH&gt;
&lt;TH width="240.578px"&gt;Description&lt;/TH&gt;
&lt;TH width="116.469px"&gt;Reference syntax&lt;/TH&gt;
&lt;TH width="265.031px"&gt;Example values&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="60.9688px"&gt;ID&lt;/TD&gt;
&lt;TD width="60.9531px"&gt;string&lt;/TD&gt;
&lt;TD width="240.578px"&gt;
&lt;P&gt;Unique routing leg identifier of the contact&lt;/P&gt;
&lt;P&gt;For emails, this is the same as Group ID.&lt;/P&gt;
&lt;P&gt;For example:&lt;/P&gt;
&lt;DIV&gt;
&lt;UL&gt;
&lt;LI&gt;Can be used as the contact identifier for the &lt;EM&gt;/contacts&lt;/EM&gt; resource of CMI and RMI&lt;/LI&gt;
&lt;LI&gt;Can be used as the contact identifier for the &lt;EM&gt;/emails&lt;/EM&gt; resource of CMI&lt;/LI&gt;
&lt;LI&gt;In Dashboard, this is known as &lt;STRONG&gt;Conversation ID&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;TD width="116.469px"&gt;{contact.id}&lt;/TD&gt;
&lt;TD width="265.031px"&gt;
&lt;PRE&gt;1166301942A6EE11B3ED58961D1810CC&lt;/PRE&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="60.9688px"&gt;Group ID&lt;/TD&gt;
&lt;TD width="60.9531px"&gt;string&lt;/TD&gt;
&lt;TD width="240.578px"&gt;
&lt;P&gt;Unique group identifier of the contact&lt;/P&gt;
&lt;P&gt;For emails, this is the same as ID.&lt;/P&gt;
&lt;P&gt;For example:&lt;/P&gt;
&lt;DIV&gt;
&lt;UL&gt;
&lt;LI&gt;Can be used as the group identifier for the &lt;EM&gt;/chats&lt;/EM&gt; resource of CMI&lt;/LI&gt;
&lt;LI&gt;Can be used as the contact identifier for &lt;EM&gt;/emails&lt;/EM&gt; resource of CMI&lt;/LI&gt;
&lt;LI&gt;In Dashboard, this is known as &lt;STRONG&gt;Group ID&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;TD width="116.469px"&gt;{contact.guid}&lt;/TD&gt;
&lt;TD width="265.031px"&gt;
&lt;PRE&gt;5AB6E20342A6EE11B3ED58961D1810CC&lt;/PRE&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Fri, 13 Dec 2024 14:25:44 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Contact-Pro/Call-related-IDs-swapped-in-the-event-driven-integration-EDI/m-p/17633#M559</guid>
      <dc:creator>Niina_P</dc:creator>
      <dc:date>2024-12-13T14:25:44Z</dc:date>
    </item>
  </channel>
</rss>

