[HLR9820] Error 3100 is frequently generated on the SMU client after the HLR9820
|
Error 3100 may be caused if the database is updated, but the network is not updated. Error 3100 occurs in the following cases: - The data of an undefined subscriber is added. - Subscriber data is deleted. - The CancelLocation message is not responded within the specified time, the message resend function is enabled on the HLR, and error 3100 is generated at the same time. fact that the HLR fails to send the message or that the MSC fails to send a response. Two subscribers are selected from the subscribers for whom error 3100 is repeatedly generated from July 25th to September. The messages of the two subscribers are traced. The traced messages of the two subscribers show that the MSC responds with the mp unidentified sub error. It indicates that the MSC does not store the data of the subscribers. The subscription data, however, is normal on the HLR. Because error 3100 is generated for a large number of subscribers, another 11 subscribers are selected for the message tracing. Analyses show that the MSC does not store or purge the data of the 11 subscribers. In the previous MSC cutover, the dynamic data of purged subscribers is not copied to the new MSC, and 420 thousand out of the 1.2 million subscribers are in Purged state. Therefore, the fault is resulted from the cutover. %%LST DYNSUB: IMSI="XXXXXXXXXXXXX";%% SUCCESS0001:Operation is successful IMSI = XXXXXXXXXXXXXXXX ISDN = YYYYYYYYYYYYY "Dynamic Status Information For GSM" VlrNum = ZZZZZZZZZZZZ MscNum = ZZZZZZZZZZZ MsPurgedForNonGprs = FALSE After the subscribers switch off and then on their MSs, a location update is |
|
very much informative and useful doc. thanks |

Favorite (0)