The North American Numbering Plan (NANP) is a telephone numbering plan for World Zone 1, which comprises twenty-five distinct regions in twenty countries primarily in North America, including the Caribbean. Some North American countries, most notably Mexico, do not participate in the NANP.
A Name Authority Pointer (NAPTR) is a type of resource record in the Domain Name System of the Internet. NAPTR records are most commonly used for applications in Internet telephony, for example, in the mapping of servers and user addresses in the Session Initiation Protocol (SIP).
Network Address Translation (NAT) is a method of remapping one IP address space into another by modifying network address information in Internet Protocol (IP) datagram packet headers while they are in transit across a traffic routing device.
A NNID (NetNumber ID) is a unique number assigned by NetNumber (the leading organisation for telecommunications standards), which defines which carrier a number belongs to. The NNID has a number of important benefits:
Uniquely identifies the service provider for a particular dialled number
Supports global portability correction, meaning that a number can be dialled from anywhere in the world.
Supports global code-range data
Supports North American MVNO-OTT override data for text messaging.
An NNID is a 6 digit number which is split into two segments:
digits 1-3 digits represent country code
digits 4-6 are sequentially assigned service provider ID.
NNIDs are maintained by the NetNumber Global Data Services team. They were originally created to ensure mobile networks had a common global standard to refer to Communication Service Providers.
Since its inception, the NNID naming convention has shot up in popularity to become the industry gold standard. Netnumber GDS maintains the Global Carrier Mapping Registry (GCMR). As one of the world’s most widely utilized carrier identification databases, its job is to store data on communications service providers in over 240 countries globally.
NNID at Sinch
For developers working with Sinch API, NNIDs come in useful when importing numbers. The Sinch platform assigns a new NNID to each imported number. This enables you to retain information such as which Service Provider the number belongs to.
Customers who are importing numbers (i.e. want to use their own NNID) to text enable their numbers, will need to complete the NNID provisioning process to support proper message routing with the carriers. To learn more, refer to the article Importing Numbers. The Numbers API has a range of API resources to enable Sinch developers to use their existing NNID numbers.
Visit the Sinch 10DLC Product Page to learn more or if you need more help with 10DLC or have any questions, contact Sinch, who will be happy help!
Common Mobile Radio System or traditional cellular networks consists of traffic from our SMS-enabled non-mobile carrier customers (AKA SMS-enabled OTT). We call these solution providers: NUVOs for Network Unaffiliated Virtual Operators as they provide mobile-operator like services such as voice and messaging and interwork with the legacy ecosystem. These are also called Cloud-based Messaging providers. These are primarily based in the United States. Key providers include: Twilio, Bandwidth, Nexmo (Vonage), Pinger, TextNow, and Google Voice.
Some SMSCs are able to provide a proof of delivery notification (similar to the concept of email COD), once the message has reached the subscriber’s handset. However, this does not mean the message is actually viewed; it has just arrived on the handset. Some Digital Interconnect customer’s use the notification feature (where available) to trigger their billing process and charge the subscriber for the service.
Number Resolution System – this is the Digital Interconnect global phone numbering database that is distributed to all Digital Interconnect data centers and accessible to all of Digital Interconnect messaging hubs. It utilizes data feeds from over 2 dozen authoritative sources around the world to populate the phone numbering information. One of the primary missions of NRS is to maintain up to date MNP (Mobile Number Portability) data in supported countries around the world.
Null values in the Sinch APIs can be omitted in requests and will be omitted in responses. In some cases, explicitly setting null will overwrite a previously set value with null. See Update a group for an example.
New features might result in additional request and response parameters. New request parameters will either have a default value or be considered optional to retain backwards compatibility. It's highly recommended to ignore any unexpected parameters when reading JSON in API responses and in callback handlers.
The requirement set forth by federal legislation that allows consumers of mobile communication services to retain their mobile phone numbers for as long as they wish, even if/when they change mobile service providers. Legislation was passed to stop the requirements by carriers to change phone numbers each time the consumer switched carriers.