<?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 DB99 – Unknown or Ported Number in SMS 365, enterprise service</title>
    <link>https://community.sinch.com/t5/SMS-365-enterprise-service/DB99-Unknown-or-Ported-Number/ta-p/1049</link>
    <description>&lt;P&gt;&lt;STRONG&gt;DB99&lt;/STRONG&gt;&amp;nbsp;&lt;SPAN style="border: none windowtext 1.0pt; padding: 0cm;"&gt;i&lt;/SPAN&gt;&lt;STRONG style="font-style: normal; font-weight: bold; color: #000000; font-family: Arial, sans-serif; font-size: 13.3333330154419px; font-variant: normal; letter-spacing: normal; line-height: 14.5454540252686px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff;"&gt;&lt;SPAN style="border: none windowtext 1.0pt; padding: 0cm;"&gt;&lt;SPAN style="color: #000000; font-family: Arial; font-size: 13.3333330154419px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.5px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: #ffffff;"&gt;s a SMS 365, enterprise service status&amp;nbsp;code, which&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt; indicates that the MSISDN is an ‘&lt;EM&gt;Unknown&lt;/EM&gt;’ or ‘&lt;EM&gt;Ported’ Number&lt;/EM&gt;’.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Possible Reasons for a DB99 response&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are a number of reasons why the DB99 response is returned, some of which along with the actions which should be taken, are detailed below:&lt;/P&gt;
&lt;P style="margin-left: 0cm;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE style="margin-left: 5.4pt;" width="643"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD style="background-color: #f0ab00;"&gt;
&lt;P&gt;&lt;STRONG&gt;Category&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271" style="background-color: #f0ab00;"&gt;
&lt;P&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301" style="background-color: #f0ab00;"&gt;
&lt;P&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;MNP&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The operator is in the process of porting the MSISDN to another operator.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;During this time the MSISDN is neither on the originating Operator Network, nor on the New Destination Operator Network.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;The porting process must complete before the MSISDN is available on the new operator network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The time taken to complete this process varies from operator to operator and country to country.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;MNP&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The end-user has ported from one operator network to another.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The porting has not been correctly registered on the home location register (HLR), which means that the new operator is not reflected correctly against the MSISDN in the HLR.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ‘look-up’ against, or data extracted from, this information will return the old operator details, until the HLR is correctly updated.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;The end-user should be contacted to confirm their MSISDN with full international prefix and operator details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A ticket can be raised using the collected details, to the SMS 365, enterprise service, Service Desk to verify that the lookup against this MSISDN is returning the correct operator.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Service Desk will check and escalate the issue further as required.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;Customer&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The MSISDN provided by the end-user has been incorrectly stored in the database&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;This is a data quality issue. The end-user should be contacted to confirm their MSISDN with full international prefix details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The correct MSISDN details should be captured as well as the operator to which the MSISDN is registered.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;Customer&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The MSISDN is taken from a ‘paper’ form, and transcribed incorrectly due to handwriting misinterpretations.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;This is a data quality issue. The end-user should be contacted to confirm their MSISDN with full international prefix details, and recorded accurately.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;End-user&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The end-user providing the MSISDN does not conform to the form template, leaves out the international prefix or transposes part of the MSISDN.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;The end-user should ensure that the MSISDN is correctly provided in any form (online or otherwise) which captures the MSISDN.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 02 Dec 2020 11:18:20 GMT</pubDate>
    <dc:creator>Shahzad_Ismail</dc:creator>
    <dc:date>2020-12-02T11:18:20Z</dc:date>
    <item>
      <title>DB99 – Unknown or Ported Number</title>
      <link>https://community.sinch.com/t5/SMS-365-enterprise-service/DB99-Unknown-or-Ported-Number/ta-p/1049</link>
      <description>&lt;P&gt;&lt;STRONG&gt;DB99&lt;/STRONG&gt;&amp;nbsp;&lt;SPAN style="border: none windowtext 1.0pt; padding: 0cm;"&gt;i&lt;/SPAN&gt;&lt;STRONG style="font-style: normal; font-weight: bold; color: #000000; font-family: Arial, sans-serif; font-size: 13.3333330154419px; font-variant: normal; letter-spacing: normal; line-height: 14.5454540252686px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff;"&gt;&lt;SPAN style="border: none windowtext 1.0pt; padding: 0cm;"&gt;&lt;SPAN style="color: #000000; font-family: Arial; font-size: 13.3333330154419px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.5px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: #ffffff;"&gt;s a SMS 365, enterprise service status&amp;nbsp;code, which&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt; indicates that the MSISDN is an ‘&lt;EM&gt;Unknown&lt;/EM&gt;’ or ‘&lt;EM&gt;Ported’ Number&lt;/EM&gt;’.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Possible Reasons for a DB99 response&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are a number of reasons why the DB99 response is returned, some of which along with the actions which should be taken, are detailed below:&lt;/P&gt;
&lt;P style="margin-left: 0cm;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE style="margin-left: 5.4pt;" width="643"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD style="background-color: #f0ab00;"&gt;
&lt;P&gt;&lt;STRONG&gt;Category&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271" style="background-color: #f0ab00;"&gt;
&lt;P&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301" style="background-color: #f0ab00;"&gt;
&lt;P&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;MNP&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The operator is in the process of porting the MSISDN to another operator.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;During this time the MSISDN is neither on the originating Operator Network, nor on the New Destination Operator Network.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;The porting process must complete before the MSISDN is available on the new operator network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The time taken to complete this process varies from operator to operator and country to country.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;MNP&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The end-user has ported from one operator network to another.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The porting has not been correctly registered on the home location register (HLR), which means that the new operator is not reflected correctly against the MSISDN in the HLR.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ‘look-up’ against, or data extracted from, this information will return the old operator details, until the HLR is correctly updated.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;The end-user should be contacted to confirm their MSISDN with full international prefix and operator details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A ticket can be raised using the collected details, to the SMS 365, enterprise service, Service Desk to verify that the lookup against this MSISDN is returning the correct operator.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Service Desk will check and escalate the issue further as required.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;Customer&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The MSISDN provided by the end-user has been incorrectly stored in the database&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;This is a data quality issue. The end-user should be contacted to confirm their MSISDN with full international prefix details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The correct MSISDN details should be captured as well as the operator to which the MSISDN is registered.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;Customer&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The MSISDN is taken from a ‘paper’ form, and transcribed incorrectly due to handwriting misinterpretations.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;This is a data quality issue. The end-user should be contacted to confirm their MSISDN with full international prefix details, and recorded accurately.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;&lt;STRONG&gt;End-user&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="271"&gt;
&lt;P&gt;The end-user providing the MSISDN does not conform to the form template, leaves out the international prefix or transposes part of the MSISDN.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="301"&gt;
&lt;P&gt;The end-user should ensure that the MSISDN is correctly provided in any form (online or otherwise) which captures the MSISDN.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 11:18:20 GMT</pubDate>
      <guid>https://community.sinch.com/t5/SMS-365-enterprise-service/DB99-Unknown-or-Ported-Number/ta-p/1049</guid>
      <dc:creator>Shahzad_Ismail</dc:creator>
      <dc:date>2020-12-02T11:18:20Z</dc:date>
    </item>
  </channel>
</rss>

