[superuser2]

Yep. VoIP contractors (I was one) are usually required to call 911 from every location in a PBX system to make sure that the E911 data shows up correctly.

There is usually a script for this, and the first words out of your mouth should be "This is a non-emergency call. I am testing <insert short description>. Is this a good time?"

It tells the call-taker that they don't need to worry about you, and that you are being careful not to tie up resources. If they need to hang up and focus on priority calls, they will. Most likely, they'll be happy to help.

[Aloha]

You only need to do that if you're stupid frankly, all you need to do is insert dialing rules that if 911 call send the BTN/main number, if for all other calls send station DID - often this is done on the carrier side - so you should only need to place calls from one phone for the whole site. It's wholly impractical to do this as well for any site with more than 20 phones, I had customers with sites that has over 1000 stations on them.

[superuser2]

Sorry, by "location" I meant site, not station. Yes.

[Aloha]

That makes more sense, yes :-D - 911 routing issues were always vexing, usually it was a to the wrong PSAP.

[MichaelGG]

One of the big players had a lovely-insane policy. They'd use your last MSAG-validated[1] address, regardless what new address you had provisioned.

So, user's in Texas, gets an MSAG-validated address, everything's good. They move to Kentucky, change addresses. The new address would have some MSAG issue, and could take days or longer to resolve.

This company thought the best thing to do was to route the call to Texas.

(MSAG is the street addressing system that the PSAPs use. It can be considerably different from the postal address.)

[Aloha]

That sounds vaguely like the normal intrado bullshit.

[MichaelGG]

Hey, using Microsoft Streets and Trips is a great way to charge $85/hr to correct addresses.