All the tests that you issue will be visible in the Results section, at the bottom of Live number testing. 

 

Columns and explanations

ID

The unique ID given to each test issued on our platform. This should not be confused with the Test ID Text.

 

Date

Date and time of the test request being issued (more accurately, date and time when the Test ID Text was issued for your test request). Please note that the timestamp in html is always the browser’s timezone.

 

Country(MCC)/Network(MNC)

The destination you selected for testing

 

DLR/Rec. status: This column has 2 important values which we will explain below:

► DLR: represents the delivery report that you receive from your supplier and you forward to us in order to be processed. In some specific cases, we return an “internal” DLR status (No DLR received, Partially delivered, submit_sm failed). More details on the Icon status of the DLRs can be found in Help, as well as by hovering with the mouse over the icon in Results:

► Rec. status: represents the Receipt status which is the answer given by our test number to your test request. More details on the Icon status of the Receipt Status can be found in Help, as well as by hovering with the mouse over the icon in Results:

Please note that ‘Test number not available’ is a temporary status. We update our test numbers’ availability constantly and in rare cases it’s possible that the test number selected for your test will no longer be available in which case we will disable it if it does not communicate with our system for 4 minutes. Therefore, you will receive ‘Test number not available’ as Receipt status. It is a temporary status, which means that our system will wait for the test number to come back online during the TTL value (the validity time of the Test ID Text).

You may find the TTL feature in Settings (the button below the Sender ID Text) in Live number testing or in Account settings, where you can update how long you would like to wait for the final receipt status. The minimum TTL is 1 min, however, we recommend you to set it to at least 5 mins, to account for the possibility of the test number not being available as mentioned above.

 

If there is any alternative and available test number for the same MCC MNC at that moment, a back-up test will be issued, if enabled (you may change the setting by modifying the value of “Back-up tests” from My account. More information on this can be found in Back-up tests.)

If our test number does not come back online during the TTL value, the Receipt status will change to ‘Test number offline’. If no back-up test was issued, we will return the credit consumed for this test back to your balance. (The credit will also be returned if the back-up test’s Receipt status is “Test number offline” too).

Fake DLR

You may spot a Fake DLR when the value on DLR/Rec. status column is like this: 

 As you can see in the screenshot, the DLR report sent by your supplier confirms that the SMS was delivered, but the Receipt status sent by our test number is saying that the SMS did not reach the handset.

Please note that escalation of our test numbers to your vendors in case of Fake DLR is strictly forbidden. By escalating our test number to your suppliers, you will only announce the quality testing to your vendors and they will whitelist the test number. This will make it useless for your own purpose of performing quality testing on their routes and useless for us as we will have to replace our test numbers more frequently, and therefore drive a price increase of our services. 

Sender ID: The displayed value is:

  • black if the test did not reach our test number

  • green if the test reached our test number and the Sender ID submitted was identical to the Sender ID received

  • and it’s red if the test reached our test number but the Sender ID received by our test number was different from the Sender ID submitted.

Please feel free to click on the value in this column to see more information:

Text: The displayed value is:

  • blue to indicate the Test ID Text,

  • black if the test did not reach our test number,

  • green if the test reached our test number and the text submitted was identical to the text received

  • and it’s red if the test reached our test number but the text received by our test number is different from the text submitted.

Please feel free to click on the value in this column to see more information:

Phone/SMSC:  In this column you can see the test number allocated to your test request and, in case the test was received by our test number, the SMSC that delivered the message. Please note that the SMSC information is provided by the mobile network operator and in case the MNO did not provide this information when delivering the message, we cannot retrieve the SMSC info and therefore it will not be displayed.
The SMSC value will be:

  • green if the SMSC country code matches the country code of the destination tested,

  • red if it does not match.

If you click on the value in Phone/SMSC column you will be able to get more information:

If the test is successfully received by our test number and the SMSC value is shared by the MNO in the PDU, we automatically and free of charge run an HLR query on it in order to retrieve more information about it: MCC, MNC and provider for that particular SMSC value.

This information should assist you in detecting if your vendor is using a direct route or to identify the SMSC owner.

Supplier: This column indicates the supplier chosen for the test. 

DLR/Rec. delay: This column indicates the values of the delay in getting the SMPP DLR status and the delay in delivery for the Receipt status. The Receipt delay is the delay between when the test was created and when our system received the information from the test number that the message was delivered. The values in this column are interactive and you can check the SMPP Latency Details by clicking on them:

For each timestamp, we also present the time interval between each other. This is what the bar colors in the chart represent:

Currently we provide you with 3 different timestamps from our SMPP System for DLR delays. Here is a short explanation of the blue color bar:

  • Position 0 in the chart - test creation - the timestamp when our backend system saved the Test information to our database, after you clicked Run and Confirm on our web app.

  • submit_sm - SMS submitted to your SMS platform - timestamp captures the instant when our SMPP System scheduled the submit_sm PDU through the SMPP Session.

  • submit_sm response - SMS accepted/rejected by your SMS platform - timestamp captures the moment when our SMPP System gets notified of the submit_sm_response PDU arriving.

  • deliver_sm timestamp - DLR received from your SMS platform - captures the instant when our SMPP System receives the deliver_sm PDU.

Please note that these timestamps will also naturally differ a bit from your system timestamps, since depending on the location, load and bandwidth of your systems with respect to ours, there will inevitably exist a certain amount of network latency. This new feature could be useful to assess such latency.

We provide 3 different timestamps regarding SMS reception. Here is a short explanation of the green color bar:

  • Position 0 in the chart - test creation - the timestamp when our backend system saved the Test information to our database, after you clicked Run and Confirm on our web app.

  • SMSC Timestamp* - Indicates the smsc submission timestamp, contained on the GSM SMS PDU received on the phone.

  • Received on Phone* - Marks the instant the SMS was delivered to the user (mobile app). This value could be unreliable in some rare cases when the time/timezone settings of the phone are incorrect.

  • Received on Server - The moment when our backend server receives the notification of SMS reception from the mobile phone. This is the only timestamp we can guarantee as correct so it’s the one used officially for SMS Received timestamp, as well as for calculating the Rec. Delay of a test.

* It is important to note that SMSC Timestamp and Received on Phone can be affected by incorrect time and timezone settings on the SMSC or mobile phone, and as such TelQ can’t guarantee its precision in 100% of cases. If we detect the delays are off by more than 15 minutes or if they don’t match the expected order of reception (For example, it should always be first SMSC timestamp, second phone timestamp, and last server timestamp) then we don’t display the graph for it, since an error on the time / timezone settings of the remote devices might exist and the values would be unreliable.

User: In this column you will see the user that created the test.

Actions column has multiple buttons which are detailed below:

is the action button you can use to leave an individual comment for each test in your TelQ account, visible to all team members who see the test entry. Aside from leaving a comment in the Settings section before you test, by clicking on this button, you will be able to leave one even after you have submitted your batch.

Please note that the comment cannot be edited or deleted once saved. The comment will also be included in the exported test results.

is the button to Repeat the test batch that included the test for which you pressed this button. Please keep in mind that by pressing this button, the repeat of the tests will not be done automatically. By selecting this action, the fields for creation of tests in Live number testing will be populated as per your initial test batch (Sender IDs, Texts, Advanced settings, Destinations and Suppliers) but you will still have to press Run and Confirm in order to repeat the test batch.

Furthermore, please note that all the input selected in your initial test batch (Sender IDs, Texts, Advanced settings, Destinations and Suppliers) will be populated, not just the unique combination (1 Sender ID, 1 Text, 1 Destination and 1 Supplier) for which you pressed the Repeat button.

is the button to report a malfunction of the test number. If you click on it, a pop-up window will appear and you may select the suitable issue you suspect to be the problem for that particular test number. Here is a screenshot of the pop-up window:

 is the action button for displaying all the details of your test. If you click on this icon, a pop-up window will open, presenting you the Test Case. An example of it can be found in the screenshot below.

As you can see in the screenshot, in this section you may find more details about your test.

Results table information (detailed explanations above):

ID: The value that is present in the 1st column of Results table.

Date: The value that is present in the 2nd column of Results table.

Country: The value that is present in the 3rd column of Results table.

Receipt Status: The interpretation of the graphical representation of Rec. Status in the 4th column of Results table.

Receipt delay: The value that is present in the 9th column of Results table for Rec. Status.

Sender ID sent: The Sender ID submitted for the test.

Sender delivered: The Sender ID received by our test number for the test.

Text sent: The text submitted for the test.

Text delivered: The text received by our test number for the test.

Test ID text type: the type of Test ID Text you selected in the Test ID Text Settings.

Test ID text length: the number of characters you selected in the Test ID Text Settings.

SMSC: The value that is present in the 7th column of Results table as SMSC.

Phone: The test number allocated to your test request.

Supplier: The supplier you chose for your test request.

 

Settings information (the values you set up in Settings):

Protocol ID

Source TON

Source NPI

Data Coding

TTL

 

SMPP PACKET #1: There will be 1 SMPP Packet displayed for each SMS. This means that if you submit a concatenated message as a test request, you will have 1 SMPP Packet for each SMS.

Status: The DLR status

Message ID: This value is the answer that your platform sends to us upon acknowledgment that the test issued from our platform has been successfully accepted by your platform. A missing Message ID indicates that the test did not reach your platform/ was not accepted by your platform.

Sent at: Timestamp of submitting the test request

Delivered at: Timestamp of receipt (retrieved from our test number)

PDU: The value that we retrieve from our test number in case the receipt of the test request was successful (the test was successfully received by our test number), as well as the decoded version of it.

  

On the right, below Suppliers, you can find the button Search. You may use this button in order to Search for specific tests:

 

As you can see in the screenshot above, you may choose the following as parameters for searching among the Results:

  • Test ID

  • Test ID Text

  • Sender ID

  • Submitted text (without “Test ID Text“) - you can search by parts of the text that was sent, or the whole text without the Test ID Text

  • Date

  • Comment

  • Comment Date

  • User (Main account, deputy or subaccount that issued the tests)

  • TLV

  • DLR Status

  • Receipt Status

  • Destination(s): limited to 100 entries

  • Supplier(s)

  • After you input the desired parameters, click on Search again and the results in the table below should update based on your criteria.

“Show only my tests” option will overwrite the Select users menu. If you need a quick filter on your own test results, you may use this option. This value will be cleared after refresh of the page or selection of another menu page.

“Save user search” will save the “Users” and/or “Show only my tests” values and will keep that filter for the test results until you unselect it or log out. 

 

Export

 

In the bottom right corner of the Live number testing page, you can see the button Export as xlsx. This button can be used for you to export the Results into an excel file. Please note that the timestamp of the results in the excel is always GMT.

The extracted excel file will contain all the information related to your tests.

 

Results count on the page when using Search

0-x/y

x = number of visible elements/rows on screen

y = number of tests that match the search criteria