SMS Verify - SMPP TLVs

📘

NOTE:

To add this product to your account, contact a Telesign expert. This product is available for full-service accounts only.

These TLVs are supported only when using SMPP to query Telesign SMS Verify. They are grouped according to which product feature they are related to.

If you haven't already, first review SMPP protocol to learn our general SMPP requirements before reading this page.

Score check

These TLVs are related to Score, the Telesign product which returns a risk score to help determine how likely it is that the number is associated with fraudulent activities. Ask the Telesign Customer Support Team if you would like to enable this feature for SMS Verify.

phone_type

The type of the phone number in the request. May be included in the deliver_sm PDU sent in response to a Score request.

FieldOctets SizeTypeDescription
Parameter Tag2Integer0x1407
Length2IntegerLength of Value field in octets
Value2Octet-StringContains these sub-fields:
code (phone type code)
description (the phone type)

Example: "code:2; description:MOBILE"

risk_score

The score and associated data for the phone number in the request. May be included in the deliver_sm PDU sent in response to a Score request.

FieldOctets SizeTypeDescription
Parameter Tag2Integer0x1408
Length2IntegerLength of Value field in octets
Value2C-Octet StringContains these sub-fields:
level (a description of the severity of the risk)
score (the risk score itself)
recommendation (the action TeleSign recommends you take based on the risk score)

Example: "level:low; score:1; recommendation:allow"

risk_insights

Contains reason code sub-fields with additional info related to the risk score. Score API - Insights reason code mappings provides the meaning of these reason codes.

FieldOctets SizeTypeDescription
Parameter Tag2Integer0x140A
Length2IntegerLength of Value field in octets
Value2C-Octet StringContains these sub-fields:
status (The processing status of the risk insights package for this request.)
category (Reason codes related to the category of the phone number.)
a2p (Reason codes specific to application-to-person communication (A2P). These are automated communications sent to a human, like verification codes, appointment reminders, etc.)
p2p (Reason codes specific to person-to-person communication (P2P). This is two-way communication between two humans, like one friend texting another.)
numberType (Reason codes related to the phone number’s type.)

Example: "status:800; category:[10040]; a2p:[22001, 20012, 20101]; p2p:[30201]; numberType:[40004, 40013]"

numbering

The original phone number from the request, along with some additional details.

FieldSize OctetsTypeDescription
Parameter Tag2Integer0x1409
Length2IntegerLength of Value field in octets
Value2C-Octet StringContains these sub-fields:
phone_number (the phone number without the country dialing code)
min_length (the minimum number of digits allowed for phone numbers with this country dialing code)
max_length (the maximum number of digits allowed for phone numbers with this country dialing code)
country_code (a 1, 2, or 3-digit number representing the country dialing code for this phone number)

Example: "phone_number:5558675309; min_length:5; max_length:15; country_code:1"