New Requirements: https://community.freepbx.org/t/freepbx-new-e911-compliance-features/64569

New Requirements: https://wiki.freepbx.org/display/FOP/Set+up+Emergency+Service%28E911%29+calling+requirements

http://wiki.freepbx.org/display/FPG/Outbound+Routes+Configuration+Examples

https://www.voip-info.org/asterisk-dialplan-patterns/

In simple situations, you can just add 911 to the Dial Patterns that will use this Route on the default outbound route and specify the caller ID for the outbound trunk or route.

You will need:

• At least one DID
• e911 service for that DID
• e911 service properly configured with local address
• Outbound CID specified and working
• 911 dial pattern added/permitted/matched on the default outbound route

When you have multiple physical locations, you will need:

• At least two DIDs
  • DID #1 is used for location #1
  • DID #2 is used for location #2
• e911 service for the two DIDs
  • e911 location #1 physical address configured for DID #1
  • e911 location #2 physical address configured for DID #2
• An separate outbound route named Emergency just for emergency calls
  • 911 dial pattern added/permitted/matched on the Emergency outbound route
    • But not on the default outbound route
  • Emergency flag enabled on the Emergency outbound route
    • But not on the default outbound route
• Configure the Route CID on the Emergency outbound route
  • Use DID #1 assuming location #1 is the primary or has the most extensions
  • Select to Override Extension CID
    • In case any extensions have their own CID defined
• Modify all extension definitions for extensions at location #2
  • Specify the Emergency CID as the DID for location #2
  • This will override the outbound Route CID when dialing from extensions at location #2