# Emergency Services - DID Routing Conditions

- If you change the directory number of a set or a user in the User and Services Configuration form, you must manually update the Destination Number in the Direct Inward Dialing Service form (if the DID Type is Emergency DID).

- If multiple users make an emergency call at the same time sharing the same CESID, then the last user to make the 911 call will be the user that is called back.

- The Emergency DID Routing feature is supported for Personal Ring Group (PRG) and Multi-Device User Group (MDUG) members as registration DNs. PRG and MDUG members as hot desk users are also supported. In both cases, the PRG or MDUG prime member’s DN is used as the Emergency DID Destination Number.

- This feature is supported for Hospitality Suite and Multi-Device Suite members as registration DNs. Suite members and Multi-Device Suite members as hot desk users are also supported. In both cases, the Suite or Multi-Device Suite pilot number is used as the Emergency DID Destination Number.

NOTE: The Suite pilot number is used as the Destination Number even if the member’s call delivery type is None.

- It is not recommended that the System Administrator configure Call Forward Follow Me (CFFM) and Call Rerouting for DNs that have the Emergency DID Routing feature enabled.

- After placing an emergency call, it is not recommended that the caller (hot desk user) log out of the set; the caller must wait for the PSAP callback.

- If a logged-in hot desk user is forcibly logged out by another hot desk user (log over) after the former placed an emergency call that was not answered by the PSAP, then the PSAP callback will encounter OOS handling or go to the original emergency caller’s Voicemail.

- A PSAP emergency callback that occurs during an SDS sync (master or slave) fails. It is recommended that the System Administrator perform SDS sync during MiVoice Business maintenance windows at scheduled times only.

- If there is a complete or partial match on a Whitelisted CgPN or a complete match on a Blacklisted CgPN, then the corresponding actions will take precedence over both Emergency and Standard DID services.

- If you are using local-only DNs within a MiVoice Business cluster, then do not use the Emergency DID Routing feature.

- The Location Based Routing (LBR) feature does not affect the operation of Emergency DID Routing: when a hot desk user based in a certain location (say, Chicago) logs in to a registration telephone in another location (say, New York) and places an emergency call, the call is routed to the New York PSAP using Location Based Routing. If the emergency call could not be answered by the PSAP, then the callback is routed to the hot desk user's DN (in New York).

- Telephones configured with the Class Of Service (CoS) option Non DID Extension cannot be called by DID trunks; this configuration will block PSAP callbacks.

- If a customer implements one of the NG911 Vendor solutions to support Ray Baum Act compliance, the DID routing feature is no longer required and should be disabled.

Related Topics

- Emergency Services - DID Routing Description

- Emergency Services - DID Routing Programming

- Emergency Services - DID Routing Maintenance