Originally, the HLR9820 is configured with 14 CSUs. The configuration in the
hdunet.cfg file is as follows:
1:HLR:101:129.9.101.193: 1:HLRAddr:6001:03fd0fee0c0a0011031234333333333f0000:101:
1:Module:7001:129.9.101.22:0:29999:6001:
1:Module:7002:129.9.101.23:30000:59999:6001:
1:Module:7003:129.9.101.24:60000:89999:6001:
1:Module:7004:129.9.101.25:90000:119999:6001:
1:Module:7005:129.9.101.26:120000:149999:6001:
1:Module:7006:129.9.101.27:150000:179999:6001:
1:Module:7007:129.9.101.28:180000:209999:6001:
1:Module:7008:129.9.101.29:210000:239999:6001:
1:Module:7009:129.9.101.30:240000:269999:6001:
1:Module:7010:129.9.101.31:270000:299999:6001:
1:Module:7011:129.9.101.32:300000:329999:6001:
1:Module:7012:129.9.101.33:330000:359999:6001:
1:Module:7013:129.9.101.34:360000:389999:6001:
1:Module:7014:129.9.101.35:390000:419999:6001:
Later, CSUs 22 and 23 are replaced with EMAs. To ensure that sessions are numbered from 0, the operator changes the hdunet.cfg files to the following:
1:HLR:101:129.9.101.193:
1:HLRAddr:6001:03fd0fee0c0a0011031234333333333f0000:101:
1:Module:7001:129.9.101.24:0:29999:6001:
1:Module:7002:129.9.101.25:30000:59999:6001:
1:Module:7003:129.9.101.26:60000:89999:6001:
1:Module:7004:129.9.101.27:90000:119999:6001:
1:Module:7005:129.9.101.28:120000:149999:6001:
1:Module:7006:129.9.101.29:150000:179999:6001:
1:Module:7007:129.9.101.30:180000:209999:6001:
1:Module:7008:129.9.101.31:210000:239999:6001:
1:Module:7009:129.9.101.32:240000:269999:6001:
1:Module:7010:129.9.101.33:270000:299999:6001: 1:Module:7011:129.9.101.34:300000:329999:6001:
1:Module:7012:129.9.101.35:330000:359999:6001:
After the services are started on the HLR9820, subscribers served by the HLR9820
are unable to receive calls.
The failure occurs after the hdunet.cfg file is modified. Therefore, it is quite possibly
caused by the data configuration in the hdunet.cfg file.
Trace signaling messages. For details, see the Trace Signaling Messages on Call
Receiving Failure. In the MAP layer, the HLR sends the Provide Roaming Number
(PRN) request message to the MSC. In the SCCP layer, however, the MSC does not
respond to the PRN request message. This indicates that the HDU has constructed
the PRN request message incorrectly. The causes of the failure in the SCCP layer
are as follows:
1. SAUs allocate dialog IDs to messages sent to the HLR. Before the task related to
a message is complete, the HLR uses the dialog ID to communicate with the network
element (NE) that sends the message. For a location update request, for example,
the SAU allocates a dialog ID. Then, the HLR and the originating MSC communicate
by using this dialog ID, and the location update is successful.
Similarly, when the originating MSC sends a Send Routing Information (SRI) request
message to the HLR, the SAU allocates a dialog ID to the message. This enables the
HLR and the originating MSC to communicate normally. The MSC does not respond
to the PRN request message. Thus, on the originating MSC, the timer for waiting the
HLR to send the SRI_ACK message expires.
2. HDUs allocate dialog IDs to messages sent from the HLR. The HDU responsible
for allocating a dialog ID for the PRN request message sent from the HLR to the
MSC mentioned in this case, however, is not found. Therefore, communication
between the HLR and the MSC is abnormal.
The relation between HDUs and dialog IDs are as follows:
Each HDU allocates 30 thousand dialog IDs. The relation between an HDU and
dialog IDs is predefined in the system and cannot be modified. The module number
of the first HDU must be 22. The following configuration is correct:
1:Module:7001:129.9.101.22:0:29999:6001:
1:Module:7002:129.9.101.23:30000:59999:6001:
1:Module:7003:129.9.101.24:60000:89999:6001:
The following configuration is incorrect:
1:Module:7001:129.9.101.24:0:29999:6001:
1:Module:7002:129.9.101.25:30000:59999:6001:
1:Module:7003:129.9.101.26:60000:89999:6001:
That is, module 22 corresponds to dialog IDs 0 to 29999, and module 23
corresponds to dialog IDs 30000 to 59999. If a module is missing, the corresponding
Change the configuration in the hdunet.cfg file to the following:
1:HLR:101:129.9.101.193:
1:HLRAddr:6001:03fd0fee0c0a0011031234333333333f0000:101:
1:Module:7003:129.9.101.24:60000:89999:6001:
1:Module:7004:129.9.101.25:90000:119999:6001:
1:Module:7005:129.9.101.26:120000:149999:6001:
1:Module:7006:129.9.101.27:150000:179999:6001:
1:Module:7007:129.9.101.28:180000:209999:6001:
1:Module:7008:129.9.101.29:210000:239999:6001:
1:Module:7009:129.9.101.30:240000:269999:6001:
1:Module:7010:129.9.101.31:270000:299999:6001:
1:Module:7011:129.9.101.32:300000:329999:6001:
1:Module:7012:129.9.101.33:330000:359999:6001:
1:Module:7013:129.9.101.34:360000:389999:6001:
1:Module:7014:129.9.101.35:390000:419999:6001:
Restart the services on the HLR9820. Now, the failure does not occur.
The following FAQs are provided for understanding the configuration in the
hdunet.cfg file.
Q1:
What is the hdunet.cfg file used for?
A1:
The hdunet.cfg file can be used for the following tasks:
1. For communication between a CCU on an SAU and the HDU
1:Module:7001:129.9.101.22:0:29999:6001:
2. For configuration of relation between SAUs and dialog IDs
1:Module:7001:129.9.101.22:0:29999:6001:
Q2:
Is the relation between HDUs and dialog IDs defined in hdunet.cfg useful? Why does
module 24 not work for dialogs 0 to 29999 even though the relation between module
24 and dialog IDs 0 to 29999 is defined in the file?
A2:
The relation between HDUs and dialog IDs cannot be modified.
Q3:
If HDU modules 22 and 23 must be removed, is it necessary to delete the
configuration of these modules from the hdunet.cfg file?
A3:
No. You can retain the configuration in the file.
Q4:
If SAU modules 24 and 25 must be removed, is it necessary to configure dialog IDs
for these modules in the hdunet.cfg file?
A4:
No. You need not configure dialog IDs for these modules. The relation between the
available modules and dialog IDs cannot be modified.
Q5:
If SAU modules 24 and 25 are unavailable and the configuration of these modules
exists in the hdunet.cfg file, does the HLR9820 generate any alarm when services
are started?
A5:
No. The HLR9820 can read the hdunet.cfg file normally.
Q6:
SAU modules 24 and 25 are unavailable, and the configuration of these modules
exists in the hdunet.cfg file. If the HDU allocates dialog 70000, which corresponds to
SAU module 24, does the message sending fail?
A6:
If BAM Manager detects that SAU modules 24 and 25 are unavailable, the BAM
Manager sends the detection result to the SCDF, which writes the value 0 to the
connection status of the modules in the hdunet.cfg file. The HDU reads the
connection status of the SAU modules from the hdunet.cfg file. If the value of the
connection status of an SAU module is 0, the HDU does not allocate dialog IDs that
correspond to the SAU module.
| 
Favorite (0)
Reply
