ALL outbound CallerID strings that are configured to be sent to E-MetroTel's Emergency Public Services Answering Point (PSAP) for 911 calls MUST be associated with an E-MetroTel SIP Trunk DID and have location information completed for 911 Registration on the E-MetroTel Partner Portal. Failure to do so will result in the emergency call center not having an address for dispatching the responders and will cause delays in their response time. The reseller will be liable and billed $500 for any call arriving at the PSAP with an unregistered CallerID and may also be in violation of the local emergency response regulations.
The CallerID format required by the E-MetroTel SIP Trunk PSAP provider is 10 digits - i.e. NPANXXXXXX (digits only).
E-MetroTel SIP Trunks may be used with UCX software running on any of the E-MetroTel provided platforms (Galaxy appliances, virtualized, or cloud offerings). Proper configuration of outbound DID information is critical to ensure that all emergency (i.e. 911) calls arrive at the Public Safety Answering Point (PSAP) with a DID that is properly registered and corresponds to a valid/desired address for the emergency response team notification.
DID Registration for Emergency Response
First DID from E-MetroTel
When SIP trunks are initially provisioned for a customer, E-MetroTel automatically provides a new unique DID associated with the SIP trunk for that customer. This is to ensure that customers can make and receive calls even if there are delays in the porting of any of the customer’s existing DIDs from the existing PSTN provider(s). This new DID is automatically registered with our 911 PSAP and associated with the customer address entered in the Partner Portal. However it is still a requirement to make sure the UCX programming is configured to use this number on outbound 911/Emergency calls based the overall Emergency dialing structure for the customer.
Additional Customer DIDs Ported to E-MetroTel SIP Trunks
If the customer intends to use any additional DIDs from their ported numbers to be sent as CallerID on outbound emergency calls, then each of these DIDs and their associated address/location information must be registered with associated address information via the E-MetroTel Partner Portal. These DID entries can be configured on the outbound emergency route on the UCX as soon as they are registered in the Partner Portal.
Validating Emergency CIDs for E-MetroTel SIP Trunks
After registering the location information for E-MetroTel DIDs and any additional CallerID strings in the Partner Portal, E-MetroTel advises to test the outbound accuracy of your Emergency Dialing configurations. E-MetroTel’s SIP Trunk service allows you to easily verify the Caller ID information that is sent to the Emergency Service Provider facility by dialing 933 from each user’s phone. When a call from an extension is placed to 933, a automated response will be provided indicating the CallerID information received and confirming the address information on record for that number or indicating that no information is available.
Programming for DIDs Registered with E-MetroTel’s PSAP Provider
UCX software provides significant flexibility in which DID is sent to the PSAP provider, ranging from sending a single DID for all calls to using unique DIDs for each individual user (if available).
If the customer has only a single location and does not have any additional trunks or DIDs other than the first one provided through the E-MetroTel SIP Trunk purchase, then standard programming to use that DID on all outbound calls is sufficient, as the E-MetroTel SIP trunks will have that initial DID registered with the PSAP provider.
For all other scenarios such as cases where a customer may have more than one address being served by the same SIP trunks, a campus environment where the customer may want to be able to have emergency response teams arrive at different buildings within the campus, or where remote users have their own DIDs, specific UCX configuration is required and registration of those DIDs with the PSAP provider via E-MetroTel is also required. Requirements for these scenarios may be governed by local regulations such as Kari’s Law and the Ray Baum Act, which can place the responsibility and liability for proper configuration and registration with the reseller.
Reference the following E-MetroTel documentation for configuring these scenarios: