This is good. Side note: If you have _any_ responsibility for your office's phone system, do a 911 Test once a quarter. http://karl.kornel.us/2014/10/the-911-

This is good. Side note: If you have _any_ responsibility for your office's phone system, do a 911 Test once a quarter. http://karl.kornel.us/2014/10/the-911-test/ http://karl.kornel.us/2014/10/the-911-test/ (Shameless Plug!) At my previous company (which got bought by another company, and so no longer exists), we had a Cisco Unified Communication Manager (CUCM) 6.5 system. When I started, we had three voice T1s at HQ: Two were AT&T ISDN voice T1s, and had our 4000-DID block assigned to it. The second voice T1 was a Verizon CAS voice T1, and was used for outbound calls only. We could make 911 calls out through either provider, and that was how it was set up: Prefer AT&T outbound; fall back to Verizon if the AT&T lines were full or down. In both cases, the local 911 dispatch would receive out street address when the call came through (I tested this). Later on, as part of a move to AT&T Gigabit fiber, we replaced the two T1s with SIP. Among all of the other issues we had, the 911 center suddenly stopped getting our address information: The appropriate fields on their end were just blank. Talking to AT&T, the impression I got was that it was our problem to deal with. In the end, and with the merger looming, I switched our 911 config to the Verizon backup (which I insisted we keep), so that 911 dispatch would get our address. So, again: Find out who at your $WORK is responsible for phones, and make sure they do a 911 test every quarter!