Quote:
Originally Posted by sfhub
HLR reload is the most likely solution to the roaming problem OP described.
The VLR is temporary and automatically created from the HLR through a forwarding process. If the HLR is messed up, the VLR won't get created properly and your roaming services won't work.
|
If his HLR tables are messed up then how is he able to authenticate on Sprints own network? Refreshing the VLR still seems more likely and is less of a hassle to do than an HLR reload. The VLR may be temporary, but it is not like it updates daily (or even weekly). Granted, if refreshing the VLR doesn't fix it then an HLR reload may be prudent. If you wanna crack a nut, you don't start with the sledgehammer (unless that is ALL you want to do with the nut of course hehehe). It still seems odd to me that he is getting an "authentication" error with VZW. Even if the VLR/HLR is screwed, VZW shouldn't be "trying" to authenticate the phone since it isn't even on it's switch. I would sooner expect a regular routing issue/message like "...unable to complete your call..." or a fast busy signal. Please let us know what you find out.