<?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 Common mistakes in SMPP in SMS</title>
    <link>https://community.sinch.com/t5/SMS/Common-mistakes-in-SMPP/ta-p/8899</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;DIV class=""&gt;
&lt;P&gt;This article outlines some of the more common mistakes when using SMPP and can serve as a checklist of common misconfigurations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Bind_Transmitter/Bind_Receiver/Bind_Transceiver&lt;/STRONG&gt;:&lt;/P&gt;
&lt;P&gt;The interface_version, must be declared, most often &lt;STRONG&gt;0x34&lt;/STRONG&gt; if your ESME supports SMPP version 3.4.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Submit_SM&lt;/STRONG&gt;:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;source_addr_ton&lt;/STRONG&gt;, Type of number needs to match the &lt;STRONG&gt;source_addr&lt;/STRONG&gt;:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;TABLE border="1" width="50%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;TON&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;Value&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;
&lt;P&gt;Unknown&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x00&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;International&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x01&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;National&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x02&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;Network Specific&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x03&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="30px"&gt;Subscriber Number&lt;/TD&gt;
&lt;TD height="30px"&gt;0x04&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="30px"&gt;Alphanumeric&lt;/TD&gt;
&lt;TD height="30px"&gt;0x05&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;source_addr_npi&lt;/STRONG&gt;, Numeric Plan Indicator needs to match the &lt;STRONG&gt;source_addr&lt;/STRONG&gt;:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class=""&gt;
&lt;TABLE border="1" width="40%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;NPI&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;Value&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;Unknown&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x00&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;MSISDN&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x01&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;For example, the sender ID Sinch requires &lt;STRONG&gt;0x05/0x00&lt;/STRONG&gt; while &lt;STRONG&gt;467012345678&lt;/STRONG&gt; requires &lt;STRONG&gt;0x01/0x01&lt;/STRONG&gt;.&lt;/DIV&gt;
&lt;DIV class=""&gt;&lt;STRONG&gt;dest_addr_ton&lt;/STRONG&gt; and &lt;STRONG&gt;dest_addr_npi&lt;/STRONG&gt; should be set to &lt;STRONG&gt;0x01/0x01&lt;/STRONG&gt; as the receiving address is always an International MSISDN.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;&lt;STRONG&gt;data_coding&lt;/STRONG&gt;, commonly referred to as the DCS-value. Most often 0x00 for SMSC Default alphabet (GSM-7) or 0x08 for Unicode/UCS2.&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Thu, 20 Jan 2022 15:48:00 GMT</pubDate>
    <dc:creator>Victor_R</dc:creator>
    <dc:date>2022-01-20T15:48:00Z</dc:date>
    <item>
      <title>Common mistakes in SMPP</title>
      <link>https://community.sinch.com/t5/SMS/Common-mistakes-in-SMPP/ta-p/8899</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;DIV class=""&gt;
&lt;P&gt;This article outlines some of the more common mistakes when using SMPP and can serve as a checklist of common misconfigurations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Bind_Transmitter/Bind_Receiver/Bind_Transceiver&lt;/STRONG&gt;:&lt;/P&gt;
&lt;P&gt;The interface_version, must be declared, most often &lt;STRONG&gt;0x34&lt;/STRONG&gt; if your ESME supports SMPP version 3.4.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Submit_SM&lt;/STRONG&gt;:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;source_addr_ton&lt;/STRONG&gt;, Type of number needs to match the &lt;STRONG&gt;source_addr&lt;/STRONG&gt;:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;TABLE border="1" width="50%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;TON&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;Value&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;
&lt;P&gt;Unknown&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x00&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;International&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x01&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;National&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x02&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;Network Specific&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x03&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="30px"&gt;Subscriber Number&lt;/TD&gt;
&lt;TD height="30px"&gt;0x04&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="30px"&gt;Alphanumeric&lt;/TD&gt;
&lt;TD height="30px"&gt;0x05&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;source_addr_npi&lt;/STRONG&gt;, Numeric Plan Indicator needs to match the &lt;STRONG&gt;source_addr&lt;/STRONG&gt;:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class=""&gt;
&lt;TABLE border="1" width="40%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;NPI&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;Value&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;Unknown&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x00&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="50%" height="30px"&gt;MSISDN&lt;/TD&gt;
&lt;TD width="50%" height="30px"&gt;0x01&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;For example, the sender ID Sinch requires &lt;STRONG&gt;0x05/0x00&lt;/STRONG&gt; while &lt;STRONG&gt;467012345678&lt;/STRONG&gt; requires &lt;STRONG&gt;0x01/0x01&lt;/STRONG&gt;.&lt;/DIV&gt;
&lt;DIV class=""&gt;&lt;STRONG&gt;dest_addr_ton&lt;/STRONG&gt; and &lt;STRONG&gt;dest_addr_npi&lt;/STRONG&gt; should be set to &lt;STRONG&gt;0x01/0x01&lt;/STRONG&gt; as the receiving address is always an International MSISDN.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;&lt;STRONG&gt;data_coding&lt;/STRONG&gt;, commonly referred to as the DCS-value. Most often 0x00 for SMSC Default alphabet (GSM-7) or 0x08 for Unicode/UCS2.&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 20 Jan 2022 15:48:00 GMT</pubDate>
      <guid>https://community.sinch.com/t5/SMS/Common-mistakes-in-SMPP/ta-p/8899</guid>
      <dc:creator>Victor_R</dc:creator>
      <dc:date>2022-01-20T15:48:00Z</dc:date>
    </item>
  </channel>
</rss>

