Configuring URN map based routing for NG911 calls

Last Updated : May 02, 2023 |

About this task

The support required for Next Generation 911 (NG911) is different than Enterprise 911. Avaya SBC supports the mapping of a Uniform Resource Name (URN) to one or more dialed strings that connects users to an emergency Public-Safety Answering Point (PSAP). The mapping must be done on a location-by-location basis. Also, multimedia for voice and video is passed through the SBC server. A third-party vendor splits the multimedia stream in the PSAP. URN mapping is administered on an SBC server at the edge of an NG911 PSAP.

To administer URN mapping, you must create a new unique URN profile and then enable that profile in a new unique session policy.

With Avaya SBC Release 8.1.0, the URN mapping for NG911 calls feature supports the following functions:

  • URN mapping support for all NG911 calls coming into an NG911 PSAP using Avaya SBC.

  • Hold and unhold for all of the supported calls.

  • Secure Real-Time Transport Protocol (SRTP) and Real-Time Transport Protocol (RTP) media interworking.

  • Multimedia support for audio and video.

  • Support for other calls to the Public Switched Telephone Network (PSTN) using Avaya SBC without going through an NG911 CS and without the support of the URN mapping.

With Avaya SBC Release 8.1.2, the URN mapping for NG911 calls feature is enhanced to support the following functions:

  • Subscription (SUBSCRIBE) and notification (NOTIFY) of states and events between Avaya SBC at the NG911 Public-Safety Answering Point (PSAP) and Emergency Services Routing Proxy (ESRP) at the NG911 Core Services (CS) per Bell Canada NG911 specifications.

  • Support for adhoc conferencing.

  • Support for a call transfer.

Procedure

  1. Log in to the EMS web interface with administrator credentials.
  2. From the Device menu, click the SBC name to administer.
  3. Navigate to Configuration Profiles > URN Profile.
  4. Click Add.

    The system displays the URN Profile window.

  5. Enter a name for the URN profile in the Policy Name field.
  6. Click Next.

    The system displays the URN Mapping window.

  7. Enter a appropriate value for the URN Map.

    The following are some examples of URN map formats:

    urn:nena:service:sos.fire

    urn:nena:service:sos.police

    urn:nena:service:sos.ambulance

    urn:nena:service:responder.police

    urn:nena:service:responder.fire

    urn:nena:service:responder.ambulance

    urn:service:counseling

  8. Enter the digits to be dialed in the Dial Digit field. These are the actual digits that are dialed when the system software runs the URN Map.
  9. Optional Click Add to create additional URN maps within the same URN profile.
  10. Click Finish.

    The system displays the list of administered URN profiles.

  11. Repeat these steps to create additional URN profiles.
    Note:

    Use Edit to change existing profiles, use Rename to change the profile name, and use Delete to delete the profile.

  12. Navigate to Domain Policies > Session Policies.

    The system displays the administered session policies.

  13. Click Add to create a new unique session policy to associate with the URN mapping profile. For the complete procedures to administer session policies, refer Session policies.
  14. Select the URN Profile tab for the emergency session policy.
  15. Click Edit.

    The system displays the URN Mapping window.

  16. Enable the Enable URN Mapping option.
  17. Select a profile from the URN Mapping Profile drop-down list.
  18. Click Finish.

Next Steps

After you create URN mapping policies and session policies, you must review and administer the following options:

  • Attach the session policy created for URN mapping with a session flow. For more information, refer About administering end-point flows and session flows and Creating a new session flow.

  • For Adhoc Conferencing support, you must enable the NG911 Support option as described in About SIP server configuration profile management.

  • Disable the Refer Handling feature for the Server Interworking profile that is used for any NG911 CS trunk server. This is required for Call Transfer and Adhoc Conferencing support.

  • Enable the NATing for 301/302 Redirection option in the Server Interworking profile that is applied to the PSAP server. The default setting is Yes. This is required in Adhoc conferencing.