In the EDR analysis, in order to identify the HLR/MNP-related issues (the terms HLR and MNP are used interchangeably in this article), it is important to correctly interpret the meaning of the corresponding columns. The most convenient way to download the necessary columns is via the SMS/EDR management/EDR export tool interface by clicking on the EDR fields to export button and choosing the corresponding columns.
You may need the following columns:
Is HLR depicts the value "1" in one of the following cases:
- a successful response (containing the HLR MCCMNC) from the HLR provider was received;
- a timeout from the HLR provider was reached (not the HLR module timeout); note the difference: if the timeout of the HLR module itself is triggered (for example, the System was waiting for a response from hlr_provider_1, then the request went to hlr_provider_2), then the Is HLR value will be 0.
In all other cases, this column has value "0", including cases when an unsuccessful response was received from the HLR provider, or when the HLR module timeout was reached (the provider did not respond in a given time). If you need to check whether HLR dipping happened or not, it is better to check hlrResponseFlag and hlrCached (see below).
Technical details, the following parameters are important:
- "hlrPorted" depicts portability status as returned from the HLR provider;
- "hlrCached" depicts "1" if HLR results were taken from cache;
- "hlrSourceType" depicts the HLR provider's source type, it should correspond to the Product notes value of the HLR product for correct HLR billing;
- "hlrSourceName" depicts the HLR provider's name as set in the inner HLR module configuration, it should correspond to the Product name value of the HLR product for correct HLR billing;
- "hlrDelay" depicts the waiting time before the HLR provider's response, in seconds;
- "hlrResponseFlag" depicts "1" if there was any response received from the HLR provider (both, successful or unsuccessful), however it does not always necessarily mean that there was a direct HLR dipping, since the results from that response could have been taken from cache.
HLR MCCMNC depicts MCCMNC as received from the HLR provider.
HLR net depicts the country and network of the MCCMNC returned by the HLR provider (the country and network themselves are taken from the System reference book, even if they are returned from the HLR provider).
HLR product depicts the names of the corresponding HLR carrier + HLR product (if any HLR product is created for HLR billing).
HLR rate depicts the corresponding rate from the HLR product (if any).
HLR response code depicts the hlrResponseCode value as returned from the HLR provider.
HLR source name depicts the HLR provider's name as set in the inner HLR module configuration, it should correspond to the Product name value of the HLR product.
Also, kindly note that HLR-related issues troubleshooting can additionally be done through the SMS/Routing/Simulation interface by creating a simulation with the appropriate parameters and checking its log, you should look for the following lines:
You can also check the general article on EDR column values in our manual.
If you have any remaining questions, you can contact the support team by describing the issue and providing the data for analysis: EDRs, Simulation ID, etc.
AKBSMS - Alaris Knowledge Base
Related Questions:
1) Issues with MNP.
2) Analyzing HLR issues.
3) HLR-related EDR columns.
4) HLR data in EDRs.
5) How to identify the HLR/MNP-related issues in the EDRs.
Link to this Article: https://helpdesk.alarislabs.com/en/knowledge_base/article/275/category/134/