Merge pull request #4455 from ovh/smpp-spec-npi-ton

OVH-Team-Guides · web-flow · commit b12e6ba5254d · 2023-03-31T13:15:20.000+02:00
Fix SMPP spec
diff --git a/pages/telecom/sms/smpp-specification/guide.en-gb.md b/pages/telecom/sms/smpp-specification/guide.en-gb.md
@@ -4,10 +4,10 @@ slug: smpp-specifications
 excerpt: 'Discover the technical specifications of the OVHcloud SMPP solution'
 section: SMPP
 order: 02
-updated: 2023-02-09
+updated: 2023-03-31
 ---
 
-**Last updated 9th February 2023**
+**Last updated 31st March 2023**
 
 ## Objective
 
@@ -136,11 +136,18 @@ The `submit_sm` is used by an ESME to submit an SMS to the SMSC for transmission
 | short_message          | 5.2.22   | Yes |
 
 - `source_addr` can be an international number, an alphanumeric number or a shortcode number:
-    - international: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. +33601020304). They should have `source_addr_ton` = 1 and `source_addr_npi` = 1.
-    - alphanumeric: those phone numbers are composed of letters and numbers (e.g. ovh123). They should have `source_addr_ton` = 3 and `source_addr_npi` = 1.
-    - shortcode: those phone numbers contain between 3 and 8 numbers (e.g. 38069). They should have `source_addr_ton` = 5 and `source_addr_npi` = 1. The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
-
-- `destination_addr` must be an international number (`source_addr_ton` = 1 and `source_addr_npi` = 1).
+    - **alphanumeric**: those phone numbers are composed of letters and numbers (e.g. ovh123).
+        - `source_addr_ton` = 5
+        - `source_addr_npi` = 0
+    - **shortcode**: those phone numbers contain between 3 and 8 numbers (e.g. 38069). The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
+        - `source_addr_ton` = 3
+        - `source_addr_npi` = 1
+    - **international**: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. 33601020304).
+        - `source_addr_ton` = 1
+        - `source_addr_npi` = 1
+- `destination_addr` must be an international number (e.g. 33600000001).
+    - `source_addr_ton` = 1
+    - `source_addr_npi` = 1
 
 **Optional settings:**
 
diff --git a/pages/telecom/sms/smpp-specification/guide.en-ie.md b/pages/telecom/sms/smpp-specification/guide.en-ie.md
@@ -4,10 +4,10 @@ slug: smpp-specifications
 excerpt: 'Discover the technical specifications of the OVHcloud SMPP solution'
 section: SMPP
 order: 02
-updated: 2023-02-09
+updated: 2023-03-31
 ---
 
-**Last updated 9th February 2023**
+**Last updated 31st March 2023**
 
 ## Objective
 
@@ -136,11 +136,18 @@ The `submit_sm` is used by an ESME to submit an SMS to the SMSC for transmission
 | short_message          | 5.2.22   | Yes |
 
 - `source_addr` can be an international number, an alphanumeric number or a shortcode number:
-    - international: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. +33601020304). They should have `source_addr_ton` = 1 and `source_addr_npi` = 1.
-    - alphanumeric: those phone numbers are composed of letters and numbers (e.g. ovh123). They should have `source_addr_ton` = 3 and `source_addr_npi` = 1.
-    - shortcode: those phone numbers contain between 3 and 8 numbers (e.g. 38069). They should have `source_addr_ton` = 5 and `source_addr_npi` = 1. The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
-
-- `destination_addr` must be an international number (`source_addr_ton` = 1 and `source_addr_npi` = 1).
+    - **alphanumeric**: those phone numbers are composed of letters and numbers (e.g. ovh123).
+        - `source_addr_ton` = 5
+        - `source_addr_npi` = 0
+    - **shortcode**: those phone numbers contain between 3 and 8 numbers (e.g. 38069). The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
+        - `source_addr_ton` = 3
+        - `source_addr_npi` = 1
+    - **international**: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. 33601020304).
+        - `source_addr_ton` = 1
+        - `source_addr_npi` = 1
+- `destination_addr` must be an international number (e.g. 33600000001).
+    - `source_addr_ton` = 1
+    - `source_addr_npi` = 1
 
 **Optional settings:**
 
diff --git a/pages/telecom/sms/smpp-specification/guide.es-es.md b/pages/telecom/sms/smpp-specification/guide.es-es.md
@@ -6,10 +6,10 @@ routes:
 excerpt: 'Discover the technical specifications of the OVHcloud SMPP solution'
 section: SMPP
 order: 02
-updated: 2023-02-09
+updated: 2023-03-31
 ---
 
-**Last updated 9th February 2023**
+**Last updated 31st March 2023**
 
 ## Objective
 
@@ -138,11 +138,18 @@ The `submit_sm` is used by an ESME to submit an SMS to the SMSC for transmission
 | short_message          | 5.2.22   | Yes |
 
 - `source_addr` can be an international number, an alphanumeric number or a shortcode number:
-    - international: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. +33601020304). They should have `source_addr_ton` = 1 and `source_addr_npi` = 1.
-    - alphanumeric: those phone numbers are composed of letters and numbers (e.g. ovh123). They should have `source_addr_ton` = 3 and `source_addr_npi` = 1.
-    - shortcode: those phone numbers contain between 3 and 8 numbers (e.g. 38069). They should have `source_addr_ton` = 5 and `source_addr_npi` = 1. The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
-
-- `destination_addr` must be an international number (`source_addr_ton` = 1 and `source_addr_npi` = 1).
+    - **alphanumeric**: those phone numbers are composed of letters and numbers (e.g. ovh123).
+        - `source_addr_ton` = 5
+        - `source_addr_npi` = 0
+    - **shortcode**: those phone numbers contain between 3 and 8 numbers (e.g. 38069). The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
+        - `source_addr_ton` = 3
+        - `source_addr_npi` = 1
+    - **international**: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. 33601020304).
+        - `source_addr_ton` = 1
+        - `source_addr_npi` = 1
+- `destination_addr` must be an international number (e.g. 33600000001).
+    - `source_addr_ton` = 1
+    - `source_addr_npi` = 1
 
 **Optional settings:**
 
diff --git a/pages/telecom/sms/smpp-specification/guide.fr-fr.md b/pages/telecom/sms/smpp-specification/guide.fr-fr.md
@@ -4,10 +4,10 @@ slug: smpp-specifications
 excerpt: 'Découvrez les spécifications techniques du SMPP'
 section: SMPP
 order: 02
-updated: 2023-02-09
+updated: 2023-03-31
 ---
 
-**Dernière mise à jour le 09/02/2023**
+**Dernière mise à jour le 31/03/2023**
 
 ## Objectif
 
@@ -136,10 +136,18 @@ Le `submit_sm` est utilisée par un ESME pour soumettre un SMS au SMSC pour tran
 | short_message          | 5.2.22   | Oui |
 
 - `source_addr` peut être un numéro international, un numéro alphanumérique ou un numéro shortcode :
-    - **international** : ces numéros de téléphone se composent de l'identifiant du pays et du numéro habituel sans le premier 0 (par exemple +33601020304). Ils doivent avoir `source_addr_ton` = 1 et `source_addr_npi` = 1.
-    - alphanumérique : ces numéros de téléphone sont composés de lettres et de chiffres (ex : ovh123). Ils doivent avoir `source_addr_ton` = 3 et `source_addr_npi` = 1.
-    - shortcode: ces numéros de téléphone contiennent entre 3 et 8 numéros (ex : 38069). Ils doivent avoir `source_addr_ton` = 5 et `source_addr_npi` = 1. Le shortcode est seulement là pour avertir notre service que nous allons devoir en utiliser un. Le shortcode réel utilisé pour envoyer le sms sera défini par l'opérateur télécom.
-- `destination_addr` doit être un numéro international (`source_addr_ton` = 1 et `source_addr_npi` = 1).
+    - **alphanumérique** : ces numéros de téléphone sont composés de lettres et de chiffres (ex : ovh123).
+        - `source_addr_ton` = 5
+        - `source_addr_npi` = 0
+    - **shortcode** : ces numéros de téléphone contiennent entre 3 et 8 numéros (ex : 38069). Le shortcode est seulement là pour avertir notre service que nous allons devoir en utiliser un. Le shortcode réel utilisé pour envoyer le sms sera défini par l'opérateur télécom.
+        - `source_addr_ton` = 3
+        - `source_addr_npi` = 1
+    - **international** : ces numéros de téléphone se composent de l'identifiant du pays et du numéro habituel sans le premier 0 (par exemple 33601020304).
+        - `source_addr_ton` = 1
+        - `source_addr_npi` = 1
+- `destination_addr` doit être un numéro international (ex : 33600000001)
+    - `source_addr_ton` = 1
+    - `source_addr_npi` = 1
 
 **Paramètres optionnels :**
 
diff --git a/pages/telecom/sms/smpp-specification/guide.it-it.md b/pages/telecom/sms/smpp-specification/guide.it-it.md
@@ -6,10 +6,10 @@ routes:
 excerpt: 'Discover the technical specifications of the OVHcloud SMPP solution'
 section: SMPP
 order: 02
-updated: 2023-02-09
+updated: 2023-03-31
 ---
 
-**Last updated 9th February 2023**
+**Last updated 31st March 2023**
 
 ## Objective
 
@@ -138,11 +138,18 @@ The `submit_sm` is used by an ESME to submit an SMS to the SMSC for transmission
 | short_message          | 5.2.22   | Yes |
 
 - `source_addr` can be an international number, an alphanumeric number or a shortcode number:
-    - international: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. +33601020304). They should have `source_addr_ton` = 1 and `source_addr_npi` = 1.
-    - alphanumeric: those phone numbers are composed of letters and numbers (e.g. ovh123). They should have `source_addr_ton` = 3 and `source_addr_npi` = 1.
-    - shortcode: those phone numbers contain between 3 and 8 numbers (e.g. 38069). They should have `source_addr_ton` = 5 and `source_addr_npi` = 1. The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
-
-- `destination_addr` must be an international number (`source_addr_ton` = 1 and `source_addr_npi` = 1).
+    - **alphanumeric**: those phone numbers are composed of letters and numbers (e.g. ovh123).
+        - `source_addr_ton` = 5
+        - `source_addr_npi` = 0
+    - **shortcode**: those phone numbers contain between 3 and 8 numbers (e.g. 38069). The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
+        - `source_addr_ton` = 3
+        - `source_addr_npi` = 1
+    - **international**: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. 33601020304).
+        - `source_addr_ton` = 1
+        - `source_addr_npi` = 1
+- `destination_addr` must be an international number (e.g. 33600000001).
+    - `source_addr_ton` = 1
+    - `source_addr_npi` = 1
 
 **Optional settings:**
 
diff --git a/pages/telecom/sms/smpp-specification/guide.pl-pl.md b/pages/telecom/sms/smpp-specification/guide.pl-pl.md
@@ -6,10 +6,10 @@ routes:
 excerpt: 'Discover the technical specifications of the OVHcloud SMPP solution'
 section: SMPP
 order: 02
-updated: 2023-02-09
+updated: 2023-03-31
 ---
 
-**Last updated 9th February 2023**
+**Last updated 31st March 2023**
 
 ## Objective
 
@@ -138,11 +138,18 @@ The `submit_sm` is used by an ESME to submit an SMS to the SMSC for transmission
 | short_message          | 5.2.22   | Yes |
 
 - `source_addr` can be an international number, an alphanumeric number or a shortcode number:
-    - international: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. +33601020304). They should have `source_addr_ton` = 1 and `source_addr_npi` = 1.
-    - alphanumeric: those phone numbers are composed of letters and numbers (e.g. ovh123). They should have `source_addr_ton` = 3 and `source_addr_npi` = 1.
-    - shortcode: those phone numbers contain between 3 and 8 numbers (e.g. 38069). They should have `source_addr_ton` = 5 and `source_addr_npi` = 1. The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
-
-- `destination_addr` must be an international number (`source_addr_ton` = 1 and `source_addr_npi` = 1).
+    - **alphanumeric**: those phone numbers are composed of letters and numbers (e.g. ovh123).
+        - `source_addr_ton` = 5
+        - `source_addr_npi` = 0
+    - **shortcode**: those phone numbers contain between 3 and 8 numbers (e.g. 38069). The shortcode is only set to notify our service that we will have to use one, the real shortcode used to send the sms will be set by the telecom operator.
+        - `source_addr_ton` = 3
+        - `source_addr_npi` = 1
+    - **international**: those phone numbers are composed of the country identifier and usual number without the first 0 (e.g. 33601020304).
+        - `source_addr_ton` = 1
+        - `source_addr_npi` = 1
+- `destination_addr` must be an international number (e.g. 33600000001).
+    - `source_addr_ton` = 1
+    - `source_addr_npi` = 1
 
 **Optional settings:**
 
diff --git a/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.en-gb.md b/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.en-gb.md
@@ -7,7 +7,7 @@ section: 'Managing your solution'
 updated: 2022-08-05
 ---
 
-**Last updated 5th August 2022** 
+**Last updated 5th August 2022**
 
 ## Objective
 
@@ -35,7 +35,7 @@ An API user who sends SMS messages in an abusive manner can then be detected by
 - An API user can also be subject to restrictions (quotas) for SMS credits.
 This way, the SMS account holder can divide their credits between different API user accounts.
 
-To better manage credit for your SMS accounts, you can set a limit and quota for your API users. 
+To better manage credit for your SMS accounts, you can set a limit and quota for your API users.
 
 - The **quota** is the number of available SMS credits for each API user.
 
@@ -125,7 +125,7 @@ To get a description of a specific ptt code, you can use the following API:
 
 For more information on using OVHcloud APIs, please refer to our guide [Getting started with OVHcloud APIs](https://docs.ovh.com/gb/en/api/first-steps-with-ovh-api/).
 
-The table below provides a non-exhaustive list of the main ptt codes.
+The table below provides a **non-exhaustive** list of the main ptt codes.
 
 |Code|Description|
 |---|---|
diff --git a/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.en-ie.md b/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.en-ie.md
@@ -7,7 +7,7 @@ section: 'Managing your solution'
 updated: 2022-08-05
 ---
 
-**Last updated 5th August 2022** 
+**Last updated 5th August 2022**
 
 ## Objective
 
@@ -35,7 +35,7 @@ An API user who sends SMS messages in an abusive manner can then be detected by
 - An API user can also be subject to restrictions (quotas) for SMS credits.
 This way, the SMS account holder can divide their credits between different API user accounts.
 
-To better manage credit for your SMS accounts, you can set a limit and quota for your API users. 
+To better manage credit for your SMS accounts, you can set a limit and quota for your API users.
 
 - The **quota** is the number of available SMS credits for each API user.
 
@@ -125,7 +125,7 @@ To get a description of a specific ptt code, you can use the following API:
 
 For more information on using OVHcloud APIs, please refer to our guide [Getting started with OVHcloud APIs](https://docs.ovh.com/ie/en/api/first-steps-with-ovh-api/).
 
-The table below provides a non-exhaustive list of the main ptt codes.
+The table below provides a **non-exhaustive** list of the main ptt codes.
 
 |Code|Description|
 |---|---|
diff --git a/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.es-es.md b/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.es-es.md
@@ -11,7 +11,7 @@ updated: 2022-08-05
 > Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
 >
 
-**Última actualización: 05/08/2022** 
+**Última actualización: 05/08/2022**
 
 ## Objetivo
 
@@ -38,7 +38,7 @@ y poder identificar el origen en caso de que un usuario de la API envíe SMS de
 - Es posible imponer restricciones (cuotas) a los créditos de SMS de un usuario de la API.
 De este modo, el propietario de la cuenta de SMS puede repartir sus créditos entre las diferentes cuentas de usuarios de la API.
 
-Para gestionar mejor el saldo de su cuenta de SMS, es posible aplicar un límite y una cuota a los usuarios de la API. 
+Para gestionar mejor el saldo de su cuenta de SMS, es posible aplicar un límite y una cuota a los usuarios de la API.
 
 - La **cuota** es la cantidad de créditos de SMS asignada a un usuario de la API.
 
@@ -128,7 +128,7 @@ Para obtener la descripción de un código ptt específico, puede utilizar la si
 
 Para más información sobre el uso de las API de OVHcloud, consulte nuestra guía [Primeros pasos con la API de OVHcloud](https://docs.ovh.com/es/api/first-steps-with-ovh-api/).
 
-En la siguiente tabla encontrará una lista no exhaustiva de los códigos ptt principales.
+En la siguiente tabla encontrará una lista **no exhaustiva** de los códigos ptt principales.
 
 |Código|Descripción|
 |---|---|
diff --git a/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.fr-fr.md b/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.fr-fr.md
@@ -7,7 +7,7 @@ section: 'Gérer mon offre'
 updated: 2022-08-05
 ---
 
-**Dernière mise à jour le 05/08/2022** 
+**Dernière mise à jour le 05/08/2022**
 
 ## Objectif
 
@@ -125,7 +125,7 @@ Pour obtenir la description d'un code ptt spécifique, vous pouvez utiliser l'AP
 
 Pour plus d'informations sur l'utilisation des API OVHcloud, consultez notre guide [Premiers pas avec les API OVHcloud](https://docs.ovh.com/fr/api/first-steps-with-ovh-api/).
 
-Vous retrouverez dans le tableau ci-dessous une liste non-exhaustive des codes ptt principaux.
+Vous retrouverez dans le tableau ci-dessous une liste **non-exhaustive** des codes ptt principaux.
 
 |Code|Description|
 |---|---|
diff --git a/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.it-it.md b/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.it-it.md
@@ -10,7 +10,7 @@ updated: 2022-08-05
 > Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Modifica" di questa pagina.
 >
 
-**Ultimo aggiornamento: 05/08/2022** 
+**Ultimo aggiornamento: 05/08/2022**
 
 ## Obiettivo
 
@@ -38,7 +38,7 @@ Un utente API che invia SMS in modo abusivo può essere immediatamente identific
 - I crediti SMS di un utente API possono essere soggetti a restrizioni (quote).
 In questo modo, il proprietario dell’account SMS può ripartire i suoi crediti tra i diversi account di utenti API.
 
-Per gestire al meglio il saldo del tuo account SMS, puoi fissare un limite e una quota agli utenti API. 
+Per gestire al meglio il saldo del tuo account SMS, puoi fissare un limite e una quota agli utenti API.
 
 - La **quota** è la quantità di crediti SMS a disposizione dell’utente API.
 
@@ -128,7 +128,7 @@ Per ottenere la descrizione di un codice ptt specifico, utilizza questa API:
 
 Per maggiori informazioni sull'utilizzo delle API OVHcloud, consulta la nostra guida [Iniziare a utilizzare le API OVHcloud](https://docs.ovh.com/it/api/first-steps-with-ovh-api/).
 
-Nella tabella seguente è riportato un elenco non esaustivo dei codici ptt principali.
+Nella tabella seguente è riportato un elenco **non esaustivo** dei codici ptt principali.
 
 |Codici|Descrizione|
 |---|---|
diff --git a/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.pl-pl.md b/pages/telecom/sms/tout_savoir_sur_les_utilisateurs_sms/guide.pl-pl.md
