There's no substitute for actually calling and testing toward the end of your install. If you're having trouble with say, an Emergency Responder install and you need to make a lot of calls, you could play with route patterns to redirect the calls somewhere else. However, this is just for development and troubleshooting things like the ANI you're sending, and is NOT a substitute for a real test. If you don't call the PSAP and ask them what shows up on their screen, you've not tested huge portions of the call path and verified that they have the right address and name in their database.
The first thing out of your mouth needs to be something like "This is a test call, do you have time for a number and address check?" If you need to make one or more followup test calls, ask if it's okay to do so on your first test call. If they have a lot going on, they'll tell you and you can get out of their way. This has always worked for me making one or two test calls at the end of each install. After the install, especially for larger multisite installs, we recommend the customer test at least quarterly and talk with the local fire and safety folks about their preferences for exactly when and how that's done. Nobody objects to testing, it needs to be done. You just try to be minimally intrusive on their time and their real jobs and get out of their way immediately if they're busy.
