<?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>article Hop in Glossary</title>
    <link>https://community.sinch.com/t5/Glossary/Hop/ta-p/7563</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;For every entity (and associated store and forward machine) a message touched in its path to delivery is regarded as a hop. The count starts when an enterprise submits a message to a network and stops when the message reaches the final terminating operator SMSC. An example of a single hop: Acme Inc. sends a message to an AT&amp;amp;T subscriber via the Sinch network, then Sinch sends the message to AT&amp;amp;T for on-net delivery. An example of a multi hop: Acme Inc. needs to send a message to an AT&amp;amp;T subscriber, but has to use an intermediary service, like SMSAGG Inc. SMSAGG sends the message to Sinch for delivery, which would be two hops. If Sinch uses its own&amp;nbsp;&lt;A href="https://www.sinch.com/products/operators/value-added-services/smsc/" target="_blank"&gt;SMSC&lt;/A&gt;&amp;nbsp;for delivery, then this would be a zero-hop connection. In general, the less hops the better, as each hop takes time and can potentially have latency and security vulnerabilities.&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Thu, 03 Jun 2021 16:51:09 GMT</pubDate>
    <dc:creator>Shahzad_Ismail</dc:creator>
    <dc:date>2021-06-03T16:51:09Z</dc:date>
    <item>
      <title>Hop</title>
      <link>https://community.sinch.com/t5/Glossary/Hop/ta-p/7563</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;For every entity (and associated store and forward machine) a message touched in its path to delivery is regarded as a hop. The count starts when an enterprise submits a message to a network and stops when the message reaches the final terminating operator SMSC. An example of a single hop: Acme Inc. sends a message to an AT&amp;amp;T subscriber via the Sinch network, then Sinch sends the message to AT&amp;amp;T for on-net delivery. An example of a multi hop: Acme Inc. needs to send a message to an AT&amp;amp;T subscriber, but has to use an intermediary service, like SMSAGG Inc. SMSAGG sends the message to Sinch for delivery, which would be two hops. If Sinch uses its own&amp;nbsp;&lt;A href="https://www.sinch.com/products/operators/value-added-services/smsc/" target="_blank"&gt;SMSC&lt;/A&gt;&amp;nbsp;for delivery, then this would be a zero-hop connection. In general, the less hops the better, as each hop takes time and can potentially have latency and security vulnerabilities.&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 03 Jun 2021 16:51:09 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Glossary/Hop/ta-p/7563</guid>
      <dc:creator>Shahzad_Ismail</dc:creator>
      <dc:date>2021-06-03T16:51:09Z</dc:date>
    </item>
  </channel>
</rss>

