<?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 MO (Mobile Originated) in Glossary</title>
    <link>https://community.sinch.com/t5/Glossary/MO-Mobile-Originated/ta-p/7618</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;A message (for example, an&amp;nbsp;&lt;A href="https://www.sinch.com/products/apis/messaging/sms/" target="_blank" rel="noopener"&gt;SMS&lt;/A&gt;&amp;nbsp;message) sent from a mobile handset to an application is referred to as an MO message. In the context of SMS, the term describes the process and flow of a handset sending a short message submission to its home network SMSC utilizing the mo-ForwardSM transaction, which will store and forward to the destination mobile number or&amp;nbsp;&lt;A href="https://www.sinch.com/products/apis/messaging/numbers/short-codes/" target="_blank" rel="noopener"&gt;short code&lt;/A&gt;. In the case of a short code or A2P&amp;nbsp;&lt;A href="https://www.sinch.com/products/apis/messaging/numbers/long-numbers/" target="_blank" rel="noopener"&gt;long number&lt;/A&gt;, the SMSC will pass the message to the aggregator, and the aggregator will pass it onto the enterprise who has leased that number. An acknowledgement (delivery notification) is also sent back to the originating handset once the message is delivered to the enterprise.&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 17 Dec 2025 20:02:28 GMT</pubDate>
    <dc:creator>Shahzad_Ismail</dc:creator>
    <dc:date>2025-12-17T20:02:28Z</dc:date>
    <item>
      <title>MO (Mobile Originated)</title>
      <link>https://community.sinch.com/t5/Glossary/MO-Mobile-Originated/ta-p/7618</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;A message (for example, an&amp;nbsp;&lt;A href="https://www.sinch.com/products/apis/messaging/sms/" target="_blank" rel="noopener"&gt;SMS&lt;/A&gt;&amp;nbsp;message) sent from a mobile handset to an application is referred to as an MO message. In the context of SMS, the term describes the process and flow of a handset sending a short message submission to its home network SMSC utilizing the mo-ForwardSM transaction, which will store and forward to the destination mobile number or&amp;nbsp;&lt;A href="https://www.sinch.com/products/apis/messaging/numbers/short-codes/" target="_blank" rel="noopener"&gt;short code&lt;/A&gt;. In the case of a short code or A2P&amp;nbsp;&lt;A href="https://www.sinch.com/products/apis/messaging/numbers/long-numbers/" target="_blank" rel="noopener"&gt;long number&lt;/A&gt;, the SMSC will pass the message to the aggregator, and the aggregator will pass it onto the enterprise who has leased that number. An acknowledgement (delivery notification) is also sent back to the originating handset once the message is delivered to the enterprise.&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 17 Dec 2025 20:02:28 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Glossary/MO-Mobile-Originated/ta-p/7618</guid>
      <dc:creator>Shahzad_Ismail</dc:creator>
      <dc:date>2025-12-17T20:02:28Z</dc:date>
    </item>
  </channel>
</rss>

